​

Core Concepts

​

Assistants

An Assistant is your AI voice agent. It combines:

• An LLM (the brain — GPT-4o, Llama, Claude, etc.)
• A Voice (TTS — how it sounds)
• A Transcriber (STT — how it hears)
• A System Prompt (personality and instructions)
• A Language Wrapper (optional — for African language support)

Assistants start as drafts and become published when synced to the voice engine.

​

Workflows

A Workflow is a visual call flow built with a node editor (React Flow). Instead of a single assistant, you chain together steps — subagents, API calls, conditions, transfers, and more — into a graph that defines exactly how a call progresses. Workflows support versioning: each publish creates an immutable snapshot. Phone numbers can pin a specific workflow version for routing. See the Workflows guide for details.

​

Phone Numbers

Phone numbers are how callers reach your assistant. They come from a pre-configured admin pool and are purchased with credits. A phone number can be linked to one assistant (or workflow) at a time.

​

Linking

Linking connects a published assistant or workflow to an active phone number. When linked:

• Incoming calls to that number route to your assistant
• A SIP endpoint is created behind the scenes
• The assistant or workflow handles the call end-to-end

​

Language Wrappers

Language wrappers are pre-built prompt prefixes that instruct your assistant to respond in a specific African language. They handle:

• Language preference
• Noisy transcription recovery
• Code-switching (when callers switch languages)
• Speech-friendly output

​

Publishing

Publishing syncs your assistant or workflow configuration to the voice engine. Only published resources can receive calls.

​

Tools

Tools are function definitions that assistants can call during conversations. They let your assistant:

• Look up data (order status, account info)
• Write to external systems (book appointments, update records)
• Execute server-side logic in real-time

Tools are defined with a JSON Schema for parameters and can be synced to the voice engine. See the Tools guide for details.

​

Webhooks

Webhooks deliver real-time call events to your own server. When calls start, end, or fail, the platform sends an HTTP POST to your configured URL with the event payload. This lets you:

• Log calls in your own system
• Trigger post-call workflows
• Monitor call status in real-time

See the Webhooks API reference for setup.

​

Campaigns

Campaigns are outbound calling initiatives. You define a campaign with a target list of contacts, an assistant or workflow, and scheduling rules. The platform dials out to each contact and tracks results per contact. See the Campaigns guide for details.

​

Billing & Credits

Credits are your account balance used for:

• Phone number purchases (one-time buy fee + monthly fee)
• Per-minute call usage
• Add-on features

Your Plan determines included credits, base features, and per-minute rates. When included credits are exhausted, you can purchase credit packages (PAYG) or let auto-reload top up automatically. Costs are shown in your local currency with applicable markup. See the Billing guide for details.

​

Integrations

Integrations connect the platform to external services. Currently supported:

• Google Sheets — read/write spreadsheet data in workflows
• Server Credentials — store bearer tokens, OAuth2, or HMAC secrets for authenticating API calls from tools and webhooks

See the Server Credentials API for setup.

​

Organization

Your organization is the billing and access boundary. All assistants, phone numbers, workflows, and resources belong to an organization. API keys are scoped per organization.