End Call Node
Terminate conversations cleanly
The End Call Node is the final stop in your flow—it terminates the conversation session. Once the AI agent reaches this node, it will deliver any last scripted message, perform any final cleanup actions you’ve attached, and then close out the conversation immediately. There are no outgoing nodes: the flow terminates here.
The End Call Node:
Important: Once the End Call Node executes, the user cannot reply or continue the conversation. Any user input after this point is ignored.
In Flow Designer, click the Plus icon and select End Call
Message:
{variable_name} syntax to personalize (e.g., "Thanks, {user_name}! Have a great day.")Example:
Note: If you reference variables in your final message (e.g., {ticket_number}, {refund_amount}), ensure those variables are collected earlier in your flow. Otherwise, you’ll see the variable name literally in the message or get a runtime error.
The final message should be short, polite, and clear. Avoid long explanations or multiple sentences.
Since the conversation ends immediately, don’t ask questions in the final message. End Call Node is not a place for contingency.
Reference collected variables to make the closing message feel personal:
Examples:
"Thanks, {user_name}! Your order #{order_id} has been placed.""Perfect! I've scheduled your appointment for {appointment_date}. See you then!"Use Branch Nodes to route to different End Call Nodes based on context:
Example:
This keeps your closing messages contextually appropriate.
If you have multiple paths that should end the same way, use Jump To to route to a single End Call Node. This reduces duplication and makes updates easier.
Example:
Alternative approach: If you have multiple “end” scenarios, create a single, well-named End Call Node (e.g., “End Call – Standard”) and adjust its message dynamically with variables. Then, from other spots, Jump or route to that single node—rather than duplicating multiple end messages.
Avoid information overload. Users either hear this at the very end of a dialogue or as a fail-safe. If you need to convey more than two sentences of info, consider splitting: send a shorter closing text here, then have a final Conversation or Message node just before that to display or speak the extra details.
End the call after successfully completing the user’s request:
End the call when the user indicates they’re done:
End the call when an error occurs or the AI cannot help:
No. Once the End Call Node executes, the conversation terminates immediately. Any user input after this point is ignored.
Yes! Use {variable_name} syntax to reference variables collected during the conversation. For example: "Thanks, {user_name}! Your order #{order_id} is confirmed."
Custom Actions execute before the final message is delivered. They complete before the conversation terminates.
Yes. You can have multiple End Call Nodes for different scenarios (e.g., success vs. error). Use Branch Nodes to route to the appropriate End Call Node based on context.
End Call terminates the conversation completely. Call Transfer hands off the call to a human agent or external phone system. Use End Call when the conversation is complete. Use Call Transfer when you need human intervention.