Configure the end node

The end node finishes the call. It executes the final instructions and processes every action attached to it before terminating the conversation.

Warning: Once the end node runs, the conversation will be over. Do not use the end node if you’re expecting further user feedback. To avoid frustrating users, do not ask questions (for example, “Do you need anything else?”) in your End node.

Configure the end node

In your Flow Designer, click and select End.

Enter your final instructions for the agent in this flow. You can attach custom actions to your End node (enter a # sign and select the action from the dropdown list or type its name), as well as reference results of previously executed actions (type the < sign and select the result).

Tips

If you want to either continue or end the conversation depending on a condition, use a branch node instead.
The End node will fully follow the prompt before terminating the call. You can use the End node for any final or cleanup actions, such as archiving chat history or logging the session as finished.
Keep the message short, to-the-point and polite. It should be clear for the customer that the conversation is over and the agent isn’t listening to their input. If you need to add more information, consider including an extra step node before the end node.
Consider including several end nodes to account for context. For example, you can have separate end nodes for successful calls (“I’m glad I could help, bye!”) and calls that result in errors (“I’m sorry, bye!”).
For contextual endings, pair the end node with branch or jump nodes. For example:
- Branch node + End node. You can have a separate end node for every possible outcome. For example, Branch A End Call (Success); Branch B End Call (Technical error); Branch C End Call (No Access).
- Branch node + Jump node. You can create just one End call (Fallback) node and use the Jump node to reroute the conversation there for every flow that needs a fallback.