01Questions

Including the ones we come off worse in.

If something is not built, it says so here rather than in a support thread three weeks after you started integrating.

We are not publishing a number yet, because we cannot yet measure it well enough to defend one, and a flattering number you later find to be wrong is worse than no number. What we can tell you is where the time was taken out: the agent starts speaking its first sentence while it is still working out the second, and it runs on speech engines we operate rather than ones we call out to over somebody else's network. When we can measure it properly, the number goes on this page.

02Already running agents elsewhere?

Switching costs an afternoon.

Point a number at us and your existing agent config comes across as it is — the field names and shapes your team already writes. Trying us should cost an afternoon, not a sprint of rewriting integrations, so we made sure it does.

Your agents, prompts and flows import as they are
Your numbers keep working — bring the carrier or move it
Run one agent here and the rest where they are, until you are sure
fields you already writeidentical
agent_idinbound_agent_idoutbound_agent_idsip_outbound_trunk_configbegin_message_delay_msend_call_after_silence_msmax_call_duration_msring_duration_msinterruption_sensitivityresponsivenessenable_backchannelambient_soundboosted_keywordspost_call_analysis_datageneral_tools

Where a field has no equivalent on a provider you have chosen, it is stored and reported as inert rather than silently approximated. You always know which knobs are live.

We are onboarding teams one at a time so we can watch the first real calls with you. Tell us what the agent needs to do and we will tell you honestly whether it is ready for it.