Salesforce
Salesforce stays the complete customer-interaction record. DialSplice reads contacts and opportunities under your scopes, routes inbound events into the queue, and writes dispositions and bookings back.
Salesforce stays the record. The queue moves here.
Contacts, opportunities, pipelines
Read under organization and location scope; Salesforce remains the system that owns the lead.
Inbound routed events
A new form fill or inbound message in Salesforce becomes a work item with its location and window attached.
Repeat-lead rule
A returning contact updates the open opportunity in Salesforce; a new one is created only after close or abandonment.
Dispositions written back
Every outcome lands on the Salesforce record from the same event that updated the queue.
Built during onboarding when the vendor exposes an API. We confirm feasibility in the demo before you commit.
Reads, writes, and never returns.
- Contacts and identity fields under scope
- Opportunities, pipeline stage, and owner
- Tags and fields used for routing
- Consent and do-not-contact flags
- Inbound events: form fills, messages, missed-call webhooks
- Dispositions and call outcomes on the contact timeline
- Opportunity stage updates
- Callback scheduled and kept events
- Booking confirmations
- Outcome notes, never transcripts
- Message bodies or recordings from the telephony adapter
- Records outside the requesting scope
- Credentials 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 Salesforce is usually spliced with.
One connector per category. These are the systems we most often see beside Salesforce; any of them can be swapped for the one you run.
Other CRM connectors.
Salesforce and DialSplice.
Who it is for, and what to ask before the demo.
Does DialSplice replace Salesforce?
No. Salesforce stays your CRM and the complete customer-interaction record. DialSplice adds the queue, the contactability preflight, and the audit ledger on top, and hands work back to Salesforce where it belongs.
What does DialSplice store from Salesforce?
Work items, scope, timestamps, dispositions, event hashes, and operational telemetry. Identity is read from Salesforce under your scopes and is not copied into the ledger.
Is the Salesforce connector available today?
It is built on request during onboarding, when Salesforce exposes the API surface we need. We confirm feasibility in the demo before you commit, and quote it in writing.
Where do the Salesforce 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 Salesforce spliced in.
Bring the rest of your stack; we will show you the workspace with every system named.