Getting started
What Voicebot is, where it sits between your telephony and your systems, and the shortest path to a first automated call.
Voicebot documentation
Automated voice conversations, wired into the systems you already run. Voicebot places and answers the calls; your systems decide who to call and what happens with the result.
Integration guide
The route from an empty tenant to a running automation, split into three phases by who performs each step.
Concepts
The object model and the vocabulary the rest of the documentation relies on.
Product guide
How each part of the product behaves. The guide opens with the bricks a call flow is built from.
API reference
Two surfaces: the Tenant API for provisioning, the Account API for everyday work.
Two API surfaces
Section titled “Two API surfaces”Voicebot splits provisioning from everyday work. The Tenant API creates tenants, accounts, trunks and API keys, and is reachable only from the internal network. The Account API carries what your application does every day: scenarios, agents, communications, SMS.
Which of the two answers you depends on the credential you hold. Identity and access pairs keys with surfaces and covers how your users sign in.