For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Atoms PlatformProduct OverviewDeveloper GuideAPI ReferenceMCPIntegrationsDeveloper ToolsChangelog
Atoms PlatformProduct OverviewDeveloper GuideAPI ReferenceMCPIntegrationsDeveloper ToolsChangelog
  • Get Started
    • Quick start
    • Platform overview
  • Single Prompt Agents
    • Overview
      • End Call
      • Transfer Call
      • Knowledge Base
      • Variables
      • API Calls
  • Conversational Flow Agents
    • Overview
  • Features
    • Concurrency
    • Knowledge Base
    • Webhooks
    • Widget
    • Integrations
    • Post-Call Metrics
    • Versioning
    • Variables
    • API Calls
  • Deployment
    • Phone Numbers
    • Audiences
    • Campaigns
  • Analytics & Logs
    • Overview
    • Testing
    • Conversation Logs
    • Locking
  • Integrate
    • Embed a voice agent
    • WebSocket SDK
  • Cookbooks
    • Using Cookbooks
  • Reference
    • Quick Reference
    • Glossary
  • Troubleshooting
    • Error reference
    • FAQ
    • Getting Help
LogoLogo
Voice AgentsModels
Voice AgentsModels
On this page
  • Setup
  • Configuration
  • Common End Call Functions
  • Tips
  • Related
Single Prompt AgentsConfiguration Panel

End Call

||View as Markdown|
Was this page helpful?
Previous

Voice Selection

Next

Transfer Call

Built with

End Call tells your agent when to hang up. Without proper end conditions, calls may drag on awkwardly or never conclude. Define clear triggers so conversations wrap up naturally.

Location: Config Panel (right sidebar) → End Call toggle


Setup

  1. Toggle End Call ON
  2. Click the ⚙️ icon to open settings
  3. Click + Add End Call to create a function

Configuration

Add end call

Add End Call modal

Each end call function has two fields:

FieldPurposeExample
NameIdentifier (used internally)end_call_resolved
DescriptionTells the AI when to trigger”End the call when the customer confirms their issue is resolved”

The Description is critical — it’s what the AI uses to decide when to end the call. Be specific.


Common End Call Functions

Issue Resolved
Goodbye
Transfer Complete
No Response
FieldValue
Nameend_resolved
Description”End the call when the customer confirms their issue is completely resolved and they have no additional questions.”

Tips

Be explicit about triggers
VagueSpecific
”When done""When customer confirms satisfaction"
"If goodbye""When customer says goodbye, thanks, or indicates they’re finished”
Cover edge cases

Don’t just handle the happy path:

  • Customer explicitly asks to end
  • Customer becomes unresponsive after 3 prompts
  • Customer requests callback instead
Stay consistent with your prompt

If your main prompt says “end when resolved,” your end call description should match that language.

Create multiple functions

Think through every way a call might conclude:

FunctionScenario
end_resolvedIssue fixed, customer happy
end_goodbyeCustomer says goodbye
end_transferAfter transferring
end_no_responseCaller stopped responding
end_out_of_scopeCan’t help, directed elsewhere

Related

Transfer Call

Hand off to human agents

General Settings

Configure idle timeouts