Outborn Agent Platform · Manual
Voice & telephony
Understand voice runtime, telephony providers, numbers, routing, regulatory requirements, and usage responsibility.
Applied guidance
Best practices for voice & telephony
Recommended
- Verify number ownership, inbound or outbound routing, and provider requirements before going live.
- Trial the call path and human handoff with realistic failure cases.
Avoid
- Do not merge telephony charges with model usage or assume one country's provider rules apply everywhere.
How it fits together
01
Voice runtime
Voice combines a real-time conversational runtime with the same agent sources, permissions, and tool boundaries used elsewhere.
02
Telephony providers
A supported telephony provider supplies calling infrastructure and provider-specific configuration.
03
Phone numbers
Numbers are provider resources and may require purchase, verification, assignment, or country-specific eligibility.
04
Routing
Route incoming or outgoing calls to the intended agent and organization context.
05
Country and regulatory requirements
Telephony rules vary by country and provider. Complete the provider's exact regulatory and identity requirements before enabling production calling.
06
Usage and cost responsibility
Telephony provider charges and AI runtime usage may be billed separately. Do not merge provider telephony charges with Outborn Hosted AI credits.
Related documentation