> For the complete documentation index, see [llms.txt](https://manuals.dialox.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manuals.dialox.ai/studio/flows/nodes/escalate-default.md).

# Escalate: default

When a Bot hands over a conversation to an operator or agent, it is called escalation. Escalation needs to be an explicit step in the flow in order for the conversation to reach the Inbox.

The **Escalate: Default** node will hand the conversation over to the inbox while passing on a message.

<figure><img src="/files/f9EqzH31mmJmvCtkTneY" alt=""><figcaption></figcaption></figure>

In the above example, the \_\_unknown\_\_ dialog [trigger](/studio/flows/triggers.md) will catch any user responses that aren't covered in the Flow. It announces the fact that the message will be forwarded to the team, and then escalates.

<figure><img src="/files/gIPSCdPCmmv3QMy9VOMp" alt=""><figcaption></figcaption></figure>

| Property     | Description                                   | Explanation                                                                                                                                                                         |
| ------------ | --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Help message | The message that is presented to the operator | The variable `last_message` contains the message that caused the escalation                                                                                                         |
| To           | The inbox to escalate to.                     | Optional. Only use when more than one inbox is configured, see [inbox tags](https://gitlab.com/botsquad/gitbook-manuals/-/blob/docs/studio/flows/nodes/broken-reference/README.md). |
| Remember     | To also store the variable in the user object | The variable name in the Assign to will be used to store the value in the user object.                                                                                              |

## Continue or wait

This Escalate: default node will not wait for an operator to join, it will simply continue the conversation. That means that, when an Iterate node preceeded this escalation for instance, it will fall back into the prompt of that iterate and reprompt the user for another action.&#x20;

If you want to prevent the bot from continuing, please use an [Escalate: smart](/studio/flows/nodes/escalate-smart.md) node instead.

## Resources

* [Chat flows](/store/skills/chat-flows.md)
* [Triggers](/studio/flows/triggers.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://manuals.dialox.ai/studio/flows/nodes/escalate-default.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.