> For the complete documentation index, see [llms.txt](https://documentation.proto.cx/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.proto.cx/docs/modules/ai-agents/workflows-and-actions/external-handoff.md).

# External Handoff

{% hint style="info" %}
Zendesk integration requires the Total plan, and Bitrix24 the Enterprise plan.
{% endhint %}

The External Handoff action is similar to [Human Handoff](/docs/modules/ai-agents/workflows-and-actions/human-handoff.md), except instead of transferring the chat to a user in Proto, it's transferred to a third party platform. Current platforms supported are:

* [**Bitrix24**](/docs/modules/ai-agents/publishing/bitrix24.md) — where the chat is transferred to another chat user in the Bitrix24 dashboard.
* [**Zendesk**](/docs/modules/ai-agents/publishing/zendesk.md) — where the chat is transferred to a live agent in the Zendesk helpdesk platform.

***

## Configuration

Select an **External Handoff** action from the tree to configure it.

Select the **Platform** to transfer chats to. See the [Bitrix24](/docs/modules/ai-agents/publishing/bitrix24.md) and [Zendesk](/docs/modules/ai-agents/publishing/zendesk.md) articles for their respective setup guides.

Press **Save** to confirm edits.

***

## Handoff

When the AI agent triggers an external handoff, the chat session will automatically end on Proto's side and be permanently transferred to the new platform. Proto has no access to the subsequent external chat, and only historic messages prior to handoff will be visible in the Inbox dashboard.


---

# 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://documentation.proto.cx/docs/modules/ai-agents/workflows-and-actions/external-handoff.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.