Requesting a connector

DialSplice ships with supported connectors for RingCentral, HighLevel, Zenoti, the major clouds, Teams, and Slack. Many other systems are listed as On request: Dialpad, 8x8, Aircall, Twilio, Zoom Phone, HubSpot, Salesforce, Zoho CRM, Pipedrive, Nextech, Boulevard, athenahealth, eClinicalWorks, Dentrix, and SendBlue for iMessage and FaceTime Audio. If your system is on that list, or not on any list, you request it. Onboarding builds the connector when the vendor exposes an API, and we confirm feasibility in the demo before you commit.

Steps

1. Open the Integrations page and find the dashed Request a connector tile, or open any On request connector page.
2. Click it. The demo form opens with the system-of-record field focused.
3. Enter the name of the system and what it does for you: telephony, CRM, EHR or system of record, data platform, notifications, or messaging.
4. Add the names of the other systems in your stack. A connector is built to fit the whole splice, not in isolation.
5. Submit. You will hear back with whether the vendor’s API supports what DialSplice needs and a written quote if the work is outside the platform fee.

What a connector needs from the vendor

For each category, DialSplice needs a small, specific set of reads and writes. For telephony: call and SMS events, number inventory, and a click-to-call handoff. For a CRM: contacts, opportunities, consent flags, and inbound events. For an EHR: record lookup, availability, booking, and appointment outcomes. If the vendor’s API cannot provide these, we say so before work starts.

What you’ll see

• The connector page shows its status as On request with the note “Built during onboarding when the vendor exposes an API.”
• Once built, the status changes to Supported and the reads / writes / never lists are published on its page.
• The build goes through the same discovery, build, and activate steps as any connector, with a synthetic sandbox before live data.

If something looks wrong

• You are unsure which category fits. Say what the system owns. If it owns the appointment, it is a system of record.
• You need two systems in one category. Tell us. A migration between CRMs is a common case and has its own notes.
• The form did not submit. Book a demo directly and mention the connector in the reason.

Related

• Connector status and credentials
• CRM migration notes
• Data platform export