Glossary

Note

This page is the public projection of the platform’s internal binding vocabulary. Terms here mean exactly this in every other page, in the API reference, and in support conversations.

Calls

communication. One dialable unit: one recipient, one scenario run, one row. Not a campaign, not a contact.

recipient. The external party of a communication. Always a non-Voicebot number.

caller / callee. The two parties by SIP role, relative to direction. Inbound, the external party is the caller and our gateway is the callee; outbound it is the other way round. These words do not pin to a fixed party. They swap with direction.

dialing. The call has been accepted for origination and is being established; the callee has not answered yet.

in progress. The call really started: connected and the scenario is running.

outcome. The terminal result of one call. Produced exactly once per accepted call.

reason. The free-text “why” accompanying a status: carrier reason, bounce cause, cancellation cause.

bounce. A transport-level failure to hand the call over at all: rejected or timed out before acceptance. Retried with backoff. Distinct from business outcomes like busy or no answer, which are retry-policy concerns, not transport failures.

drifted. A row stuck in a live state with no events for longer than the threshold, marked by the reconciler. The row stays visible.

two-axis status. Lifecycle status and call outcome are independent axes. The two failed values mean different things: bounce-exhausted versus broke mid-call.

Scheduling and delivery

calling window. The recurring allowed dialling period, schedule plus timezone. Distinct from a one-shot “not before T” intent.

result delivery. Pushing a persisted outcome to your webhook targets. Delivery is replayable.

Structure

tenant. The top-level container; you, as our customer. Isolated from every other tenant on the installation.

account. A unit inside your organisation. The isolation boundary for scenarios, numbers and call data.

scenario. The call-flow definition. A write publishes the next version unless it asks for a draft.

brick. One building block of a scenario: it does a single thing to the call and hands control on through one of its exits. The API name, carried in constructor.bricks. Elsewhere in the industry the same idea is called a node, a block or a step.

scenario version. An immutable published snapshot. An agent runs one; a test call may name the draft instead, which is frozen at dispatch.

agent. A scenario bound to a gateway: one number, or a pool of them.

trunk. The SIP path between Voicebot and your telephony. Not a number.

number. A SIP identity an account owns: the gateway an agent answers on and calls from. Its identifier is the dialable string.

number pool. A named group of numbers an agent may use as its gateway instead of binding a single one. A number belongs to at most one pool.