[IMAGE: End Call Settings page showing list of configured functions]
Location
Configuration Panel (right sidebar) → End CallEnabling End Call
- Find “End Call” in the Configuration Panel
- Toggle it ON
- Click the settings icon (⚙️) to configure
End Call Settings Page
| Element | Description |
|---|---|
| Header | ”← End Call Settings” |
| Add button | ”+ Add End Call” |
| Functions list | Configured end call functions with Edit/Delete |
Adding an End Call Function
Click ”+ Add End Call” to open the configuration modal.[IMAGE: Configure End Call Function modal with Name and Description fields]
Modal Fields
| Field | Type | Required | Example |
|---|---|---|---|
| Name | Text input | Yes | end_call |
| Description | Text area | Yes | Terminate the current call |
Writing Descriptions
The Description tells the AI when to trigger this function. Be clear and specific.Good Examples
Bad Examples
Common End Call Triggers
| Trigger | Description Example |
|---|---|
| Issue Resolved | ”Customer confirms their issue is resolved” |
| User Says Goodbye | ”User says goodbye, thanks, or indicates they’re done” |
| Task Complete | ”Appointment is successfully booked and confirmed” |
| Transfer Success | ”Call has been transferred to human agent” |
| No Response | ”User is unresponsive after 3 attempts to re-engage” |
| Cannot Help | ”Issue is outside scope and no transfer is available” |
Multiple End Call Functions
Create separate functions for different scenarios:| Function Name | Trigger |
|---|---|
successful_resolution | Issue resolved, customer satisfied |
customer_goodbye | Customer ends conversation |
transfer_complete | Handoff to human successful |
no_response_timeout | Caller unresponsive |
Best Practices
Be Specific
The AI uses your description to decide when to end. Specific descriptions = accurate behavior.Cover All Scenarios
Think about every way a call might end:- Happy path (resolved)
- Customer-initiated (goodbye)
- Handoff (transfer)
- Edge cases (unresponsive, can’t help)