Skip to main content
The end node ends the call. It’s a terminal node — it has no outgoing edges, and the call ends the moment the agent enters it. You can add as many end nodes as you need, one for each way a call can finish. By default the agent hangs up immediately, which callers experience as abrupt. Enable Speak During Execution so the agent says a closing line first.
End node on the flow canvas with the Speak During Execution setting enabled and a closing message instruction

An end node with Speak During Execution enabled for a closing message.

For example, an appointment-booking flow can end with a static closing line — “You’re all set for Tuesday at 2 PM. Goodbye!” — after the booking succeeds, and use a second end node with a different message on the cancellation path.

​
Node settings

  • Speak During Execution: When enabled, a text box appears where you define the closing message the agent speaks before hanging up. Choose Prompt to let the LLM generate a farewell from your instruction, or Static Sentence for an exact line like Goodbye, have a nice day.
  • Global Node: Make the end node reachable from anywhere in the flow when its condition is met — for example User wants to end the call or says goodbye — so you don’t have to wire an edge to it from every node. Read more at global node.

​
End node vs End Call tool

Use an end node when the call should end at a fixed point in the flow. If instead the agent should be able to end the call mid-dialogue whenever it judges the conversation complete, attach an End Call tool to a subagent node.