Product guide

The reference tells you what an endpoint accepts; the integration guide tells you what to do first. This section sits between them and describes what each part of the product is, and how it behaves once you are past the first call.

Read it when you know the sequence and need the detail: which brick to reach for, what a scenario version freezes, what deleting an agent releases.

In this section

• Agents — the object that binds a scenario to a gateway: what an inbound call resolves to, and what an outbound dispatch runs through. Putting an agent into service sets one up in order, with a check at every step.
• Numbers and pools — the SIP identities an account owns, how a pool groups them, and why a pool answers calls but places none.
• Trunks — the SIP path itself: one record per agreed path, resolved per call and carried to the telephony edge as a routing name.
• Calls — the communication: one recipient, one run, one row, and the two status axes that describe it. Call history covers the saved execution trace, the recordings, and how to read a call to find where it diverged.
• Scenarios — the call flow itself: its published versions and its one draft, what a version freezes, and which content a call runs. The constructor describes the shape of the graph.
• Scenario bricks — the 28 building blocks a call flow is made of: what each does to the call, its properties and its exits.

Other parts of the product arrive here as we write them up: calling strategies and audio assets.