Written for the person who has to sign off.
Here is exactly what DialSplice stores, what it never touches, and how you can check.
Tenant and location isolation
Every request carries organization and location scope; unknown or ambiguous scope fails closed.
Server-side credentials only
Provider tokens never reach the browser; click-to-call hands a number to the agent's own phone app.
Content-minimal notifications and logs
Alerts carry no identity; logs store events and hashes, not message bodies or recordings.
Hash-chained append-only audit ledger
Each event links to the previous by SHA-256, so changed, missing, or reordered history is detectable.
Idempotent external effects with reconciliation
Every effect is journaled once; an ambiguous provider outcome enters reconciliation, never a retry.
Runtime-validated access policy
Capability, scope, audience, environment, auth strength, expiry, revocation, and session version are checked at execution time.
Every row links to the previous by SHA-256.
- Work items
- Scope
- Timestamps
- Dispositions
- Event hashes
- Operational telemetry
- Contact identity and history read from your CRM and system of record under your scopes
- Recordings, transcripts, message bodies from the telephony adapter
- Provider tokens to the browser
Scoped access, useful in the call.
Security that blocks the work gets worked around. These are the things an agent can do from the workspace — each inside their role and location scope, each written to the ledger.
Existing patient record lookup
Before booking, the agent sees whether the contact already has a patient record in your EHR — and at which locations — so nobody creates a duplicate.
Records at multiple locations
A contact seen at two locations shows both histories to roles scoped to both. An ambiguous match is held for a person, never guessed.
Payments and card on file
Agents can take a payment over the phone or update the card on file without leaving the workspace. The action lands in the ledger like every other.
Booking into the EHR
Bookings write to your system of record with identity resolved first; the CRM is updated from the same event, so the two never disagree.
DialSplice is built HIPAA-ready and we sign a Business Associate Agreement with every medical customer. Compliance is shared; we document our controls and your responsibilities.
In progress. Ask us where we are today — we'll share our current status and roadmap.
We'll walk your security or compliance lead through the architecture, the ledger, and the data classes above before you sign.