Fail closed. Log everything. Show your work.
The questions you will ask, answered in the order you will ask them, with the exhibit to check.
Stored, passed through, never returned.
Six answers before the demo, and a security page with the rest.
What do you store?
Work items, scope, timestamps, dispositions, event hashes, and operational telemetry. Contact identity is read from your systems under your scopes.
Where do credentials live?
Server-side, always. Click-to-call hands a number to the agent's own authenticated phone app; tokens never reach the browser.
How do we verify the ledger?
Every row links to the previous by SHA-256. Changed, missing, or reordered history is detectable from the chain alone.
How is scope enforced?
Organization and location on every request; an unknown or ambiguous scope fails closed and never inherits credentials or data.
What does onboarding need from IT?
API access to each system, a location list, roles, and your consent and quiet-hours rules. Configuration is versioned, approved, and reversible.
Who maintains the connectors?
We do. Ongoing billing covers modifications, updates, troubleshooting, and repaired connections; a new integration is quoted separately.
HIPAA-ready. BAA signed. SOC 2 in progress.
Compliance is shared; we document our controls and your responsibilities, and we walk your lead through the architecture before you sign.
Bring your questions.
Twenty minutes with the architecture, the ledger, and the data classes on screen.