Tenant boundaries
The data model scopes contacts, conversations, appointments, and revenue events to the business that owns them. Server-side requests must resolve that scope rather than trust a browser-supplied business ID.
Security approach
Revenue recovery needs a clear security boundary.
Kembora is being built to protect sensitive business communications while giving teams the controls needed to supervise every automated next step.
Designed into the workflow
Secrets stay server-side
Provider credentials and access tokens belong in encrypted environment configuration. They are never included in client-side application code.
Verified integrations
Messaging webhooks are designed to validate the provider signature, use idempotency keys, and retain an audit trail before a recovery workflow continues.
Human control
Automation is constrained by business context, consent and suppression rules, quiet hours, and human-takeover states.
Before beta activation
Controls that must be live before customer data flows.
1
Production database provisioning, encryption configuration, and tested backups.
2
Identity, session management, and role-based permissions for every user-facing workspace.
3
Twilio signature verification, sender registration, consent policy, and outbound delivery monitoring.
4
Rate limiting, alerting, incident response, and a legal review of privacy and messaging practices.
Security questions before you start?
We’ll share the relevant implementation details and activation plan as the beta environment is configured.