Overview
Use End Call nodes to:- Gracefully conclude conversations
- Deliver closing messages
- Mark successful or unsuccessful call outcomes
End Call nodes are colored red to indicate they’re terminal points in your flow.
Configuration
Farewell Message
The final message spoken before the call ends. Examples:End Condition Prompt
An optional LLM-evaluated condition for when to end. This is useful when the End Call node is reachable through multiple paths and you want additional validation.Multiple End Call Nodes
You can have multiple End Call nodes in a flow for different outcomes:- Successful vs. unsuccessful resolutions
- Different farewell messages for different paths
- Tracking call outcomes in analytics
Example Configurations
Standard Farewell
Standard Farewell
Post-Booking Confirmation
Post-Booking Confirmation
Unresolved Issue
Unresolved Issue
After-Hours
After-Hours
Best Practices
Keep It Brief
Long farewell messages feel unnatural. Aim for 1-2 sentences.
Match the Outcome
Successful calls deserve positive messages. Failed resolutions should acknowledge the issue.
Include Next Steps
If applicable, tell the caller what happens next (email confirmation, callback, etc.).
Brand Consistency
Use farewell messages that match your brand voice and the rest of the conversation.
Transitions to End Call
Common transitions that lead to End Call:| From | Condition |
|---|---|
| Conversation | ”Customer says goodbye or indicates they’re done” |
| Data Extraction | ”All required information collected successfully” |
| Human Transfer | ”Transfer failed and no fallback available” |
| Calendar Booking | ”Appointment booked successfully” |