> ## Documentation Index
> Fetch the complete documentation index at: https://docs.retoneai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# End Call Stage

> Gracefully terminate conversations

The **End Call** stage terminates the conversation with a farewell message. It's a terminal node with no outgoing connections.

## Overview

Use End Call nodes to:

* Gracefully conclude conversations
* Deliver closing messages
* Mark successful or unsuccessful call outcomes

<Info>
  End Call nodes are colored **red** to indicate they're terminal points in your flow.
</Info>

## Configuration

### Farewell Message

The final message spoken before the call ends.

**Examples:**

```
// Standard
"Thank you for calling Acme Corp. Have a great day!"

// After successful resolution
"I'm glad I could help today. Thanks for calling, and have a wonderful day!"

// After appointment booking
"Your appointment is confirmed. We look forward to seeing you. Goodbye!"

// Professional
"Thank you for contacting us. If you have any further questions,
please don't hesitate to call back. Goodbye."
```

### End Condition Prompt

An optional LLM-evaluated condition for when to end. This is useful when the End Call node is reachable through multiple paths and you want additional validation.

```
End the call when the customer has confirmed they have no more questions
and has said goodbye.
```

## Multiple End Call Nodes

You can have multiple End Call nodes in a flow for different outcomes:

```
┌─────────────────┐
│   Conversation  │
└────────┬────────┘
         │
    ┌────┴────┐
    │         │
    ▼         ▼
┌────────┐ ┌────────┐
│End Call│ │End Call│
│Success │ │ Failed │
└────────┘ └────────┘
```

**Use cases:**

* Successful vs. unsuccessful resolutions
* Different farewell messages for different paths
* Tracking call outcomes in analytics

## Example Configurations

<AccordionGroup>
  <Accordion title="Standard Farewell">
    ```yaml theme={null}
    Farewell Message: |
      Thank you for calling. Have a great day!
    ```
  </Accordion>

  <Accordion title="Post-Booking Confirmation">
    ```yaml theme={null}
    Farewell Message: |
      Your appointment has been scheduled for {{appointment_date}}
      at {{appointment_time}}. We've sent a confirmation to your email.
      See you then! Goodbye.
    ```
  </Accordion>

  <Accordion title="Unresolved Issue">
    ```yaml theme={null}
    Farewell Message: |
      I apologize we couldn't fully resolve your issue today.
      A support specialist will follow up within 24 hours.
      Thank you for your patience.
    ```
  </Accordion>

  <Accordion title="After-Hours">
    ```yaml theme={null}
    Farewell Message: |
      Our office is currently closed. Our business hours are
      Monday through Friday, 9 AM to 5 PM.
      Please call back during business hours. Goodbye.
    ```
  </Accordion>
</AccordionGroup>

## Best Practices

<CardGroup cols={2}>
  <Card title="Keep It Brief" icon="clock">
    Long farewell messages feel unnatural. Aim for 1-2 sentences.
  </Card>

  <Card title="Match the Outcome" icon="scale-balanced">
    Successful calls deserve positive messages. Failed resolutions should acknowledge the issue.
  </Card>

  <Card title="Include Next Steps" icon="list-check">
    If applicable, tell the caller what happens next (email confirmation, callback, etc.).
  </Card>

  <Card title="Brand Consistency" icon="building">
    Use farewell messages that match your brand voice and the rest of the conversation.
  </Card>
</CardGroup>

## Transitions to End Call

Common transitions that lead to End Call:

| From             | Condition                                         |
| ---------------- | ------------------------------------------------- |
| Conversation     | "Customer says goodbye or indicates they're done" |
| Data Extraction  | "All required information collected successfully" |
| Human Transfer   | "Transfer failed and no fallback available"       |
| Calendar Booking | "Appointment booked successfully"                 |

## Related

<CardGroup cols={2}>
  <Card title="Start Stage" icon="play" href="/agent-builder/stages/start">
    The beginning of your flow
  </Card>

  <Card title="Human Transfer" icon="user" href="/agent-builder/stages/human-transfer">
    Alternative to ending: transfer to human
  </Card>

  <Card title="Transitions" icon="arrow-right" href="/agent-builder/transitions">
    Configure when to end the call
  </Card>
</CardGroup>