Conversation stages

View as Markdown

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

Stage typeUse when
startThe call needs a clear entry point and opening behavior.
dialogueThe agent should ask, listen, reason, and respond naturally.
verbatimThe agent must say approved language exactly.
toolThe flow should call an external tool or internal function.
internalThe agent needs routing or hidden state that should not be spoken.
endThe call should close, summarize, transfer, or hang up.

Design a stage flow

1

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.

2

Map the key turns

Split the conversation into small stages such as greeting, identity check, need discovery, tool lookup, confirmation, and close.

3

Attach tools only where needed

Keep tool access scoped to the stages that need live data or side effects.

4

Define transitions

Route on collected fields, caller intent, tool results, retry context, or language.

5

Test edge cases

Test silence, interruptions, incorrect data, tool failures, transfer requests, and early hangups.

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.