End Conversation
Explicitly terminates the current conversation session, triggering the End Conversation automation and the On conversation-stop handler.
The End Conversation node explicitly terminates the current conversation session. When this node runs, the conversation ends from the user's perspective, the End Conversation Automation fires (generating a summary/title if configured), and the On conversation-stop Handler runs.
When to Use
Use End Conversation when the flow logic determines that the session should be closed – for example:
- After the user confirms they have no further questions
- After a completed transaction or form submission
- After a human handover (the virtual being signs off and an agent takes over)
- After an inactivity timeout handled in a flow
Contrast with End Flow
| End Conversation | End Flow | |
|---|---|---|
| Ends | The entire session | Just the current flow |
| What happens next | Session terminates, cleanup runs | Returns to the calling flow |
| Triggers Automation? | ✅ Yes – End Conversation automation | ❌ No |
| Triggers Handler? | ✅ Yes – On conversation-stop | ❌ No |
Use End Conversation to close the session. Use End Flow to finish a sub-flow and return to the parent.
Effect on the User
- Web widget: The widget may close, show an end-of-chat message, or reset – depending on the widget configuration
- Kiosk: The kiosk returns to its idle state and the session is cleared
Typical Pattern
Text ("Thank you for chatting with us! Have a great day.")
│
└──► End ConversationOr after human handover:
Text ("A team member will be with you shortly.")
│
└──► Call Webhook (notify support system) ──► End ConversationAvailability
Conversational Flows only.