Skip to main content
The end-call definition describes when an agent should finish a conversation. Make the completion condition specific so an ordinary pause or an unanswered question is not mistaken for the end of the task.
The system-tool configuration can be edited and saved in an agent draft. This does not establish a working hangup action or an available phone channel. Voice publication and documented conversation-start paths remain gated.

Configure the definition

1

Define the ending condition

Write a condition such as: the request has been addressed, the user has no remaining questions, and a brief closing has been given. Define what should happen when the task cannot be completed instead of treating every failure as a reason to end immediately.
2

Enable End Call

Open the agent’s Tools page and find System tools. Enable End Call, then open its settings. Use Description (optional) to describe when the action is appropriate.
3

Review and save

Review Advanced > Interruptions if needed, then select Save. This updates the agent working copy. For API persistence, include the reviewed definition in a complete server draft and read it back.

Stored shape

The tool belongs at conversation_config.agent.prompt.built_in_tools.end_call. Its tool-specific params object contains only the discriminator:
This is a tool-definition fragment, not a complete agent-draft request. Do not add an invented delay or termination callback inside params. Shared tool settings belong at the outer level of the definition. Prepare examples for a clear goodbye, a mid-task pause, an unresolved action, and a user asking another question during the closing. A read-back verifies the configuration, not those runtime outcomes.

Frequently asked questions

No. The tool-specific parameters do not contain a duration limit. Review conversation duration settings separately rather than treating this definition as a timer.
No. Review telephony availability independently. The definition does not create a number, trunk, or live call.