Conversation stages
Stages turn an agent from one large prompt into a controlled conversation workflow. Use them when a call needs deterministic steps, branching logic, tool calls, data collection, or a specific retry point.
Stage types
Design a stage flow
Start with the caller outcome
Define the final disposition you need: qualified lead, resolved support request, payment promise, appointment booked, transfer required, or no-answer follow-up.
Map the key turns
Split the conversation into small stages such as greeting, identity check, need discovery, tool lookup, confirmation, and close.
Attach tools only where needed
Keep tool access scoped to the stages that need live data or side effects.
Retry context
Retry context can resume a follow-up call with previous state, a custom opening message, language, collected data, or a stage ID. Use it when a second attempt should continue the workflow instead of starting from scratch.
Keep stage names stable and descriptive. They become operational handles for QA, debugging, and retry behavior.