Microsoft Fabric / OneLake
DialSplice exports content-free facts — call aggregates, work-state transitions, appointment outcomes, analytics — into Microsoft Fabric / OneLake, under your governance.
Content-free facts, delivered to Microsoft Fabric / OneLake.
Content-free facts
Aggregates, transitions, and outcomes; never identity, message bodies, or recordings.
Governed and journaled
Every export batch is a ledger event with a hash; a failed batch is held for reconciliation, not silently retried.
Analytics source of truth
The same rows behind speed to lead and show rate land in Microsoft Fabric / OneLake for your own models.
Versioned mapping
The export schema is part of the location configuration: approved, activated, reversible.
Connecting now at Options Wellness. Ask us where it stands in the demo.
Reads, writes, and never returns.
- Connection health and schema version only
- Call aggregates per location and view
- Work-state transitions with timestamps
- Appointment outcomes: kept, cancelled, no-show
- Analytics facts: speed to lead, connection, schedule, show rate
- Export batch manifests with hashes
- Contact identity
- Message bodies or recordings
- Provider tokens
- Anything outside the allowlisted attributes
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 Microsoft Fabric / OneLake is usually spliced with.
One connector per category. These are the systems we most often see beside Microsoft Fabric / OneLake; any of them can be swapped for the one you run.
Other Data platform connectors.
Microsoft Fabric / OneLake and DialSplice.
Who it is for, and what to ask before the demo.
Does DialSplice replace Microsoft Fabric / OneLake?
No. Microsoft Fabric / OneLake stays your data platform, under your governance. DialSplice adds the queue, the contactability preflight, and the audit ledger on top, and hands work back to Microsoft Fabric / OneLake where it belongs.
What does DialSplice store from Microsoft Fabric / OneLake?
Work items, scope, timestamps, dispositions, event hashes, and operational telemetry. Identity is read from Microsoft Fabric / OneLake under your scopes and is not copied into the ledger.
Is the Microsoft Fabric / OneLake connector available today?
It is connecting now at our first deployment; we will share status in the demo.
Where do the Microsoft Fabric / OneLake 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 Microsoft Fabric / OneLake spliced in.
Bring the rest of your stack; we will show you the workspace with every system named.