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

# 12. Ending

> End, the non-interruptible farewell and the exception to this rule.

# Ending: End and the "interruptible farewell"

> [!NOTE]
>
> **Module goal:** end the conversation so that the farewell is spoken to the end — and know the exception to this rule.

![End node inspector: farewell phrase](https://mintcdn.com/hubtalk/UuNkjJ26eB-xpPwv/images/tutorial/tut-21-node-end_en.webp?fit=max\&auto=format\&n=UuNkjJ26eB-xpPwv\&q=85\&s=44f5f1e43766f1745bb6e8a281da8194)

End — a regular ending: a farewell phrase with variables. By default it cannot be interrupted: the call is hung up only after the phrase has been played in full.

> [accordion] Show the full panel
>
> ![End node inspector: farewell phrase](https://mintcdn.com/hubtalk/UuNkjJ26eB-xpPwv/images/tutorial/tut-21-node-end_en.webp?fit=max\&auto=format\&n=UuNkjJ26eB-xpPwv\&q=85\&s=44f5f1e43766f1745bb6e8a281da8194)

The farewell phrase is added to End with the **+ Farewell phrase** button and is set the same way as a conversation node reply: **Static** is a fixed text with `{{variables}}` substituted, **Prompt** is an instruction from which the model words the farewell itself. An End without a phrase ends the call silently.

> [!TIP]
>
> **Tip: the language of the farewell.** A fixed phrase is spoken in the language you wrote it in. If the agent speaks two languages — for example, Kazakh and Russian (`kk`/`ru`) or English and Spanish (`en`/`es`) — choose **Prompt**: the farewell is worded in the customer's language if it is known, otherwise in the agent's language. An example of a fixed phrase for an English-speaking agent under the US profile (`us_tcpa`): "Thank you, we'll see you tomorrow at 10 AM. Goodbye!"; for a Russian-speaking agent: «Спасибо, ждём вас завтра в 10:00. До свидания!»

![End inspector with interruption enabled and an exit on interruption](https://mintcdn.com/hubtalk/UuNkjJ26eB-xpPwv/images/tutorial/tut-22-node-end-exit_en.webp?fit=max\&auto=format\&n=UuNkjJ26eB-xpPwv\&q=85\&s=c667d9fe5af03876799992b10b915071)

End with an exit — the exception: interruption is allowed and an exit is set. The customer managed to say “wait!” — the ending is cancelled and the dialogue continues from the selected node.

> [accordion] Show the full panel
>
> ![End inspector with interruption enabled and an exit on interruption](https://mintcdn.com/hubtalk/UuNkjJ26eB-xpPwv/images/tutorial/tut-22-node-end-exit_en.webp?fit=max\&auto=format\&n=UuNkjJ26eB-xpPwv\&q=85\&s=c667d9fe5af03876799992b10b915071)

The exception is turned on with the **Allow interrupting the farewell phrase** toggle. Next to it you set **Exit on interruption** — the node the dialogue continues from if the customer speaks during the farewell. The exit is required: without it the **Issues** tab shows an error, and publishing is blocked. The farewell can be interrupted only in a voice call: in a text chat the conversation ends right after the phrase, so test the exit by voice.

Tip: the second option is needed where we say goodbye *on our own initiative*: "not a good time to talk — I'll call back later". Customers often change their mind at the last second, and cutting the conversation off at that moment is the worst impression of the whole call.

## How the call ends in the history

A call does not end only in End. The end reason is visible in the call history:

| How the call ended | Reason in the history |
| - | - |
| The agent reached End and finished the farewell | **Agent hung up (flow completed)** |
| The customer hung up | **Caller hung up** |
| The customer stayed silent longer than the auto-end threshold | **Silence (auto-end)** |

Reminders on silence ("Are you still there?") and the silence auto-end threshold are configured in the [Call control](https://docs.hubtalk.ai/v4/tutorial/call-control.md) lesson (lesson 15).

**Agent hung up (flow completed)** means that the conversation reached the end of the scenario, not that the call was successful: any End gives this reason. Success is determined by post-call analytics — **Call success evaluation** and a **Success criterion** in your own words, see [Analytics](https://docs.hubtalk.ai/v4/platform/agent-settings/analytics.md#what-to-compute) and the [Post-call analytics](https://docs.hubtalk.ai/v4/tutorial/post-call-analysis.md) lesson (lesson 18).

> [!NOTE]
>
> **Why an agent usually has several End nodes**
>
> Different endings mean different farewells and different behavior on interruption: "visit confirmed" says goodbye calmly and hangs up, "asked to call back later" leaves the customer a chance to change their mind. The transcript trace shows which node the conversation ended in.
>
> Campaign retry rules do not distinguish End nodes: they look at the end reason and at the success criterion. So that "asked to call back later" does not count as a success, describe this in the success criterion — then the **Goal not achieved** condition in the dialing rules returns such a contact to the calling list (see [Campaign launch](https://docs.hubtalk.ai/v4/platform/campaign-launch.md#step-3-dialing)). A request not to be called at all is not "we'll call back later" but an opt-out from calls: it is covered in [module 25, Do not call](https://docs.hubtalk.ai/v4/tutorial/dnc.md).

> [!TIP]
>
> **Practice**
>
> Add to your agent a global node "asks for a human" → Transfer with a phrase before the transfer → a node "receptionist is busy" and two End nodes: a successful one and "we'll call back later" with an interruptible farewell and an exit on interruption. Open the **Issues** tab — there should be no dead-end warnings and no errors about the exit on interruption.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.