Skip to main content

End call actions

End call actions let your agent hang up the call gracefully — for example, after a successful handoff, when the caller has confirmed everything is done, or after the agent has read out a closing line.

Name and description​

  • Name: A clear identifier (e.g., end_call_politely, wrap_up_after_confirmation).
  • Description: Explain when the agent should end the call. The agent uses the description to decide.

Be specific. "Ends the call after the caller has confirmed they're satisfied and said goodbye" is far more useful than "Ends the call."

Name: end_call_after_confirmation
Description: Hangs up after the caller has confirmed they have nothing else and said goodbye.
Use only after a clear closing exchange — don't end the call while the caller may still have questions.

Parameters schema​

End call actions have no required fields. You can optionally define a parameters schema if you want the agent to record context about why the call ended (e.g., a reason or outcome parameter that's logged with the conversation).

Phase restriction​

End call is in-call only. It can't be enabled for the post-call phase, since the call has already ended by then. The Conversation phases selector will only let you choose In call.

Pair with state restrictions​

End call actions are easy to misuse if every state can call them. In an agent with strict state separation, restrict end call to the states where ending the conversation is appropriate — for example, a "Wrap up" or "Goodbye" state at the end of your flow — and leave it unavailable from intake or troubleshooting states where premature hang-ups would be jarring.

What happens at runtime​

When the agent calls an end call action, Stellar disconnects the line. Any post-conversation wrap-up tasks configured on the agent run afterwards.

Next steps​