Connectors

Your stack, spliced. Not replaced.

DialSplice connects to the systems that already own your voice, your record, and your booking — whichever vendors they are — and adds the layer they were missing. When you want the facts in your own warehouse, it exports to your data platform on AWS, Microsoft, or Google Cloud.

01Supported connectors

Multiple systems. One layer.

Telephony

Voice, SMS, transfer

TelephonyServer-side credentialsSupported
  • Click-to-call into the agent's own app
  • SMS and voicemail outcomes · transfer handoff
  • Inventory and aggregate metrics (no parties, numbers, or recordings returned)

Bring your own provider · ● supported today · others built on request

RingCentralDialpad8x8AircallTwilioZoom Phone

CRM

Leads, opportunities, pipelines

CRMServer-side credentialsSupported
  • Contacts, opportunities, pipelines
  • Inbound routed events
  • The CRM stays the complete customer-interaction record

● supported today · others built on request

HighLevelHubSpotSalesforceZoho CRMPipedrive

EHR / system of record

Booking, patient record, identity

System of recordServer-side credentialsSupported
  • In-person booking and appointment outcomes
  • Identity and demographics authority · existing patient record lookup across locations
  • Payments and card on file, from the workspace

● supported today · others built on request

ZenotiNextechBoulevardathenahealtheClinicalWorksDentrix

Data platform

Your warehouse, your governance

Data planeServer-side credentialsSupported
  • Governed export of content-free facts
  • Call aggregates, work-state transitions, appointment outcomes, analytics
  • Your own architecture on AWS, Microsoft, or Google Cloud

● supported architectures · ● connecting at Options Wellness

Microsoft Fabric / OneLakeMicrosoft AzureAWSGoogle Cloud

Notifications

Automated, content-minimal alerts

ChannelsServer-side credentialsSupported
  • Queue health, SLA risk, holds, and batch reviews posted to the channel
  • Browser and mobile push, SMS, and email alongside
  • Location, time, and work type only; never the contact

● supported today

Microsoft TeamsSlack

Messaging

iMessage and FaceTime Audio, through SendBlue

ChannelServer-side credentialsOn request
  • iMessage as its own channel in the contactability preflight
  • FaceTime Audio click-to-call on the agent's device
  • Delivery and read outcomes; message bodies stay out of the ledger

Built on request

Request a connectorTell us the system. Onboarding builds the connector when the vendor exposes an API.
02What a splice is

Three sources in. One screen out.

Telephony
CRM
EHR / system of record
scope · policy · queue · ledger
Agent screen
Your data platformContent-free facts · AWS · Microsoft · Google Cloud
Scope

Every record carries organization and location; unknown scope fails closed.

Policy

Consent, quiet hours, attempt caps, holidays — evaluated per channel, re-validated at execution time.

Queue

One canonical work item, many views; no duplicates.

Ledger

Every effect journaled with idempotency; an ambiguous provider outcome enters reconciliation, never a retry.

03Onboarding builds the connector

Discovery. Build. Activate.

Step 1

Discovery

We inventory your systems, locations, roles, and consent rules.

Step 2

Build

Pipelines and mappings, reviewed in a synthetic sandbox before any live data.

Step 3

Activate

Versioned configuration, approval, readiness checks, rollback.

04Migration note

Moving from HubSpot to HighLevel? DialSplice consumes routed events from whichever system is live and never decides the split. In-flight nurture sequences are not restarted.

05Book a demo

See your stack, spliced.

Bring the names of your phone system, CRM, and system of record; we'll show you the workspace your agents would use.

Book a DemoSee it work