Zoom Phone
DialSplice sits on top of Zoom Phone. Calls, SMS, and transfers still happen in Zoom Phone; DialSplice decides what to do next and records what happened.
Your calls stay in Zoom Phone. The decisions move here.
Click-to-call into the agent's own app
The number opens in the agent's own Zoom Phone app. DialSplice never originates the call and never holds the audio.
SMS and voicemail outcomes
Delivery and voicemail outcomes come back as events; message bodies stay in Zoom Phone.
Transfer handoff
A transfer hands off inside Zoom Phone; DialSplice journals both legs and keeps the work item with its owner.
Inventory and aggregate metrics
Number inventory and call aggregates for coverage and analytics. No parties, numbers, or recordings are returned.
Built during onboarding when the vendor exposes an API. We confirm feasibility in the demo before you commit.
Reads, writes, and never returns.
- Number inventory and caller IDs per location
- Call events: ringing, answered, missed, duration
- SMS delivery and receipt events
- Voicemail-left events
- Aggregate call metrics for coverage and analytics
- Click-to-call intents to the agent's own app
- Outbound SMS under policy: consent, quiet hours, caps
- Transfer handoff requests
- The location's caller ID for outbound work
- Call audio or recordings
- Transcripts
- Message bodies
- Call parties or numbers from metrics endpoints
- Provider tokens to the browser
Credentials never reach the browser
Provider tokens live server-side; the agent's browser only ever sees a work item.
Scope on every request
Organization and location travel with each call to the connector; an unknown scope fails closed.
Idempotent, journaled, reconciled
Every effect is journaled once; an ambiguous outcome enters reconciliation instead of a retry.
What Zoom Phone is usually spliced with.
One connector per category. These are the systems we most often see beside Zoom Phone; any of them can be swapped for the one you run.
Zoom Phone and DialSplice.
Who it is for, and what to ask before the demo.
Does DialSplice replace Zoom Phone?
No. Zoom Phone stays your phone system. DialSplice adds the queue, the contactability preflight, and the audit ledger on top, and hands work back to Zoom Phone where it belongs.
What does DialSplice store from Zoom Phone?
Work items, scope, timestamps, dispositions, event hashes, and operational telemetry. Identity is read from Zoom Phone under your scopes and is not copied into the ledger.
Is the Zoom Phone connector available today?
It is built on request during onboarding, when Zoom Phone exposes the API surface we need. We confirm feasibility in the demo before you commit, and quote it in writing.
Where do the Zoom Phone credentials live?
Server-side, always. The agent's browser only receives a work item; provider tokens never reach it, and every request carries organization and location scope.
See Zoom Phone spliced in.
Bring the rest of your stack; we will show you the workspace with every system named.