Enforced, not just documented.
Tenant isolation
Every company's data is separated with database row-level security plus server-side authorization. Automated tests attack it on every build.
Least privilege
The application runs as a restricted database role. Roles: Owner, Manager, CSR/Dispatcher, Read-only, Platform admin.
Model boundaries
Claude interprets and phrases. It cannot query the database, change pricing, or book without the application's validated tools. Caller speech and uploaded documents are treated as untrusted.
Verified webhooks
Twilio signatures and Stripe signatures are validated; duplicate deliveries are ignored; replays are rejected.
Encrypted credentials
Integration credentials are encrypted at rest with versioned keys and can be revoked instantly.
Recording and consent
Call recording is off by default. Disclosure text, consent policy and retention are configured per company. STOP and do-not-contact are honored automatically.
Safety engine
Gas, carbon monoxide, smoke, burning electrical and medical triggers follow deterministic scripts and alert your team; the assistant never improvises repair instructions.
Auditability
Every high-impact action — booking, cancellation, settings change, escalation — is written to an audit log with the actor.
The platform supports compliance workflows (consent logging, quiet hours, recording controls); it does not by itself guarantee legal compliance in any jurisdiction. Consult your counsel on call-recording and outreach rules for the states you serve.
Find the revenue your current operation is leaving behind.
A complimentary Revenue Leakage Audit reviews your phone experience, after-hours coverage, booking friction and follow-up funnels — with every finding marked observed or requiring verification.