> For the complete documentation index, see [llms.txt](https://docs.zipchat.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zipchat.ai/ai-training-and-rules/forward-request.md).

# Human Escalation

Set up the Escalate conversation skill so Zipchat hands conversations to your team, with in-app or email alerts, Zendesk tickets and the customer's context.

The **Escalate conversation** skill hands a conversation to your team when the AI agent can't help or the customer asks for a person.

## Set it up

1. Go to **Rules & skills**.
2. Find **Escalate conversation** and click **Set up**.
3. Choose how your team is notified:
   * **In-app only:** escalated conversations appear in **Conversations**, marked with a red diamond with an exclamation mark.
   * **In-app and email:** also enter the email addresses that should receive escalations. Separate several addresses with commas, or use a team distribution list.
4. Save and test the flow in Test Chat.

To tell the agent when to escalate, for example on certain topics or for wholesale requests, add a [Rule](https://docs.zipchat.ai/ai-training-and-rules/custom-rules.md).

## What happens

1. The agent asks for the customer's email address.
2. The agent escalates the conversation with a short summary for your team: what the customer needs, the details that matter and what it already tried.
3. It appears in the **Escalated** tab of **Conversations**, and your team is notified as configured.

While a conversation is escalated and not yet resolved, the agent does not escalate it again, so you do not get duplicate notifications.

The skill always asks for an email address, also on WhatsApp where the phone number is known.

## What the escalation email contains

Each escalation email gives your team what it needs to reply:

* A title that says who is waiting, for example "Anna is waiting for your reply".
* The customer's name, email and phone number (phone on WhatsApp).
* The channel.
* An AI summary of the problem and what was already tried.
* The full conversation transcript.
* The customer's attachments. When the files add up to 13 MB or less, they are attached to the email. Above that, they arrive as links.
* A **Reply in Zipchat** button that opens the conversation.
* On WhatsApp, the time until which you can still reply from Zipchat, in your store's time zone.

The email's Reply-To is the customer. When you reply to the email, you answer the customer directly.

## Get escalation alerts in Slack

Zipchat has no native Slack integration. To get alerts in Slack, you have two options:

* Enter the Slack channel's own email address as an escalation email. In Slack, you find it under **Send emails to this channel**.
* Use Zapier.

## After an escalation

Escalating does not stop the AI. The conversation stays open, and the agent can keep answering new messages. To stop the AI and reply yourself, take over the conversation from the inbox. When you are done, give it back to the AI.

An escalation does not turn on draft mode and does not assign the conversation to a teammate.

## Escalating into Zendesk

* **Zendesk channel connected:** install the **Zendesk: escalate to human** skill. Zipchat adds an internal note and unassigns the ticket for your team. See [Zendesk](https://docs.zipchat.ai/channels/email-channel/zendesk.md).
* **Email notifications only:** enter the email address connected to your Zendesk account. Escalated chats arrive there as regular tickets.

## Escalating into other helpdesks

* **Freshdesk:** install the **Freshdesk - Create ticket** skill. It creates a ticket with a summary and the full chat transcript.
* **Gorgias:** a ready-made integration is in beta, available on request from <support@zipchat.ai>.
* **Any helpdesk that turns emails into tickets:** choose **In-app and email** and enter your helpdesk's support address.
* **Other helpdesks:** connect them with a custom skill. See [Agentic Skills](https://docs.zipchat.ai/ai-training-and-rules/agentic-skills.md).

If you also use the [Email channel](https://docs.zipchat.ai/channels/email-channel.md), Zipchat ignores its own escalation emails that reach your Zipchat email address, so they do not start new conversations.

## Other ways to hand over

Any teammate can take over a conversation from the inbox. See [Managing Conversations](https://docs.zipchat.ai/inbox-and-team-collaboration/managing-conversations.md).

## FAQ

### Does the AI stop replying after an escalation?

No. The agent can keep answering until a teammate takes over the conversation from the inbox.

### What if the customer doesn't share an email?

The agent keeps helping with anything it can answer.

### Can escalation alerts go to several people?

Yes. Enter several email addresses separated by commas, or use a team distribution list.

### Can I get escalation alerts in Slack?

There is no native Slack integration. Enter the Slack channel's email address (**Send emails to this channel**) as an escalation email, or use Zapier.

### What is in the escalation email?

The customer's contact details, the channel, an AI summary, the full transcript, attachments and a **Reply in Zipchat** button. On WhatsApp, it also shows the time until which you can still reply from Zipchat.

### Can I reply to the customer from the escalation email?

Yes. The email's Reply-To is the customer, so your reply goes straight to them.

### Can escalations go to Freshdesk or Gorgias?

Yes. Freshdesk has a ready-made skill, and Gorgias has a beta integration on request. Any helpdesk that creates tickets from emails can receive escalation emails.

### Does resolving an escalation archive the conversation?

No. Resolving and archiving are separate actions.

### What is the difference between escalation and the Email channel?

Escalation notifies your team about a conversation that started in chat, WhatsApp or social. The [Email channel](https://docs.zipchat.ai/channels/email-channel.md) answers emails your customers send.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zipchat.ai/ai-training-and-rules/forward-request.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
