Pathways
Pathways are the conversation flows that guide how your agents interact with users. They define the logic, branching, and actions that occur during a conversation.What Are Pathways?
A Pathway is a visual or code-defined flow that determines:- What questions the agent asks
- How it responds to user input
- When to take actions (book appointment, transfer call)
- When to escalate to a human
Pathway Components
Nodes
Nodes are the building blocks of pathways:| Node Type | Description |
|---|---|
| Start | Entry point of the conversation |
| Message | Agent speaks or sends text |
| Listen | Waits for user input |
| Condition | Branches based on logic |
| Action | Triggers external action |
| Transfer | Routes to human or another agent |
| End | Terminates the conversation |
Conditions
Conditions control conversation branching:Actions
Actions trigger external operations:- API Call — Send data to external systems
- Book Appointment — Create calendar entries
- Send SMS — Dispatch text messages
- Update CRM — Modify customer records
- Transfer Call — Route to human agents
Creating Pathways
Visual Builder
The visual builder provides a drag-and-drop interface:1
Open Pathway Editor
Navigate to your Crew and select Pathways
2
Add Start Node
Every pathway begins with a Start node
3
Build Flow
Drag nodes onto the canvas and connect them
4
Configure Nodes
Set messages, conditions, and actions for each node
5
Test
Use the simulator to test your pathway
Code Definition
For complex logic, define pathways in code:Common Patterns
Intent Classification
Route conversations based on user intent:Information Collection
Gather required data before taking action:Escalation Flow
Gracefully hand off to humans:FAQ Handling
Search and respond from knowledge base:Variables and Context
Pathways maintain conversation context:Built-in Variables
| Variable | Description |
|---|---|
caller_number | Phone number of the caller |
call_duration | How long the call has lasted |
current_time | Current timestamp |
agent_name | Name of the active agent |
transfer_count | Number of transfers in this call |
Testing Pathways
Simulator
Test pathways without making real calls:- Open the Pathway Editor
- Click Simulate
- Type responses as if you were the user
- Verify the agent follows expected paths
Staging Environment
Deploy pathways to a staging Crew before production:Best Practices
Start with the happy path
Start with the happy path
Design the ideal conversation first, then add error handling.
Keep it shallow
Keep it shallow
Avoid deeply nested pathways. If a branch is complex, create a sub-pathway.
Always provide exits
Always provide exits
Users should always be able to reach a human or end the call.
Handle the unexpected
Handle the unexpected
Add catch-all nodes for unrecognized input.
Test with real users
Test with real users
Simulate real scenarios, including edge cases and mistakes.
Pathway Limits
| Plan | Pathways | Nodes per Pathway |
|---|---|---|
| Starter | 5 | 50 |
| Professional | 25 | 200 |
| Enterprise | Unlimited | Unlimited |
Next Steps
- AI Receptionist — Apply pathways to voice agents
- Custom Code Nodes — Add custom logic
- Webhooks — Trigger external actions