Calls
What the bot can do on the line
Knowledge, the CRM, your own systems and the project's connectors, all while the person is still talking.
Each bot's On calls card (on the bot's page) lists what it may do during a call. The built-ins: look up knowledge, read the lead's CRM record before saying hello and file notes and stage changes while talking, send a WhatsApp or email, schedule a follow-up, send keypad digits, and on Twilio transfer the call to a person. Everything runs through the server and the bot's allowlist, so nothing a caller says can reach a tool the bot was not given.
Your own systems: HTTP tools
Under Account → Voice → Integrations on calls, add an HTTP tool: a name (lookup_order), what it does and when to use it (the bot reads this), the URL and method, the arguments as a JSON schema, and headers. Header values are stored encrypted and never shown again. On a call the bot calls your endpoint with the arguments as JSON and speaks from the response. This is how an order lookup or a booking system joins a call with no MCP server.
Connectors: MCP servers on calls
The project's remote MCP servers (and the team's shared ones) can be allowed on calls per bot, under the same card. Servers that run on a machine's shell are left out of calls; remote (HTTP) ones work.
Follow-ups
On the line the bot can book a callback (*"call me tomorrow at 11"*) with schedule_follow_up. It lands on the lead as the next follow-up, on Call next, and as a one-time routine that fires at the time, so the promise is kept whether or not anyone remembers it.