channel: "phone".
Why it is not self-serve
A phone number is not a credential a merchant pastes. It is inventory somebody buys, in a specific country, against a regulatory identity.- Procurement. Numbers are bought per country from carriers, with stock that runs out and prices that differ by city.
- KYC. India, the UAE and most of the EU require verified business documents before a number can be assigned, reviewed by the carrier, taking days.
- Porting. A merchant who wants to keep the number already on their storefront is a manual process with a cutover window.
Enabling it for a merchant
Voice is enabled per account rather than sold on a plan. A merchant without it is shown a request form, not an upgrade prompt — there is no tier that grants it, so “upgrade” would send them somewhere that cannot help. Talk to us with the merchant, the country and the expected call volume, and we provision the number and enable the channel on that tenant. Everything after that — the assistant, its knowledge, its tools, and the transcript your CRM reads — is the API you already use.What you can do today
An assistant configured through Assistants serves voice as well as chat once the channel is enabled on the tenant. Its conversations appear alongside every other channel in Conversations, withchannel: "phone" and no channel.message_id — a call has turns, not message
ids.
Voice conversations produce
conversation.created and message.received /
message.sent for each turn, on the same
webhook endpoint as every other channel. Delivery status
events are WhatsApp-only; a phone call has no equivalent.
