HIPAA mode has to be unlocked for your platform first. Once it is, a Enable HIPAA action appears on every sub-account row in your Users table. Contact us if you do not see it and you have healthcare clients to onboard.
What changes on a HIPAA account
Everything below is enforced by the platform, not by policy. Your client cannot switch back to an uncovered vendor by editing an assistant, calling the API, or using the MCP connector.
Assistants, calls, campaigns, leads, knowledge bases, mid-call tools, webhooks and the MCP connector all keep working as usual.
Enabling it for a sub-account
- Open the Users table in your administration panel.
- Find the sub-account and click Enable HIPAA.
- Read the confirmation dialog — it lists exactly what will change — and confirm.
Before you can enable it
The action refuses to continue while either of these is still on the account, and tells you what to remove:- Platform phone numbers. Numbers bought through the platform run on a carrier without a BAA. Release them and connect the client’s own carrier with a SIP trunk instead.
- WhatsApp senders. Delete them first.
- Facebook / Instagram connections. Delete them first.
Assistants on a HIPAA account
Existing assistants keep working. The first time each one runs after activation, any uncovered provider is replaced with the covered equivalent for that call, so nothing has to be rebuilt by hand. New assistants are built from the covered set automatically, in both the simple and the advanced editor:- Where the language has an ElevenLabs voice, the assistant keeps the engine it would normally use, with Gladia for transcription and Azure OpenAI as the model.
- Where the language has no ElevenLabs voice, the assistant is created in speech-to-speech mode on the Azure realtime model, which speaks the language natively.

