Connector status and credentials

A connector is the pipeline between DialSplice and one of your systems: telephony, CRM, EHR or system of record, data platform, notifications, or messaging. Each connector has a status and a set of server-side credentials. Agents never see or enter provider tokens; they sign in to their own phone app, and DialSplice talks to the provider from the server under your organization and location scope.

Connector status

• Supported — built and running today. RingCentral, HighLevel, Zenoti, Microsoft Azure, AWS, Google Cloud, Microsoft Teams, and Slack are supported.
• Connecting — being brought up now for a customer. Microsoft Fabric / OneLake is connecting at Options Wellness.
• On request — built during onboarding when the vendor exposes an API. Feasibility is confirmed in the demo before you commit.

What you’ll see

The Connectors card in the admin area lists each connector with its category, a “Server-side credentials” chip, and its status. Each supported connector shows what DialSplice reads, what it writes, and what it never returns. For telephony, for example, it reads call events and number inventory, writes click-to-call intents and outbound SMS under policy, and never returns call audio, transcripts, message bodies, or provider tokens to the browser.

Steps to check a connector

1. Open Connectors in the admin area.
2. Read the status chip. Connection health is reported per connector.
3. If a connector is degraded, look at the manager desk. Pending sync states, growing reconciliation holds, or missing history are the usual symptoms.
4. Rotate or replace credentials from the server-side connector settings. Credentials are part of the location configuration and go through a revision like any change.
5. After a credential change, confirm the connector returns to healthy and that Pending rows in the call log clear.

What credentials are used for

• Reading contacts, opportunities, and consent flags from the CRM under scope.
• Checking for existing patient records and booking into the EHR with identity resolved first.
• Posting content-minimal alerts to Teams or Slack.
• Writing content-free facts to your data platform.

If something looks wrong

• Agents cannot click to call. That is the agent’s phone app, not a DialSplice credential. Check the agent is signed in to the app.
• History is missing for a system. The connector is likely degraded. Check its status before assuming data loss.
• A vendor asked for a browser token. Decline. DialSplice never places provider credentials in client code.

Related

• Requesting a connector
• Data platform export
• Exporting the call log