The fast path
One prompt, on the phone today.
For FAQ lines, reception desks, and qualification calls: write the persona, pick a voice, attach your documents, publish.
Capability
02 / 11
Single-prompt agents
Where it fits
When the call is essentially one job, like answering pricing questions, taking a message, or qualifying an enquiry, a graph adds structure you never use. A single prompt gets the same models, the same voices, and the same phone numbers with far less to configure.
Same platform underneath
Single-prompt agents call the same tools, read the same knowledge base, use the same secrets store, and appear in the same call history as flow agents. The difference is who decides the branching: the model rather than your graph.
Graduate without migrating
When the journey grows past what one prompt can hold, move to a flow agent inside the same project: same numbers, same integrations, same reporting. Starting simple does not cost you a rebuild later.
The spec
| Single-prompt | Flow agent |
|---|---|
| FAQ lines, reception, qualification | Multi-step journeys with real branching |
| You write one persona prompt | You draw a graph of nodes and transitions |
| The model decides the branching | You decide it, and can see it |
| Minutes to first call | An afternoon to first call |
More capabilities
Designing the conversation
Flow Builder
Design the call as a graph: conversation, tool, router, transfer, and end-call nodes, connected by conditions you define rather than hope the model infers.
Read →Grounded answers
Knowledge base
Attach your documents and the agent answers from them rather than from general knowledge. That is the difference between a helpful agent and a liability.
Read →How the agent sounds
Voices & languages
Pick a voice per agent across 13+ Arabic dialects and four languages, or clone the voice your brand already uses.
Read →


