> For the complete documentation index, see [llms.txt](https://docs.3dolphins.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.3dolphins.ai/customer-service/unit-management/unit-transfer-ticket.md).

# Unit Transfer Ticket

Sometimes your agent meets certain conditions for handling tickets from other channels but has no access or rule to manage them. This feature will fulfill your needs. Why? Because using unit transfer doesn't require access or rules to receive a ticket from another unit channel.

For example, unit A only exclusive to channel A whereas unit B belongs to channel B. Because there are tickets in unit A that must be handled by unit B, these tickets must be transferred immediately to unit B for resolution. With the unit transfer, unit B can receive tickets without rules or access channels from unit A.

You can set the unit transfer type as the default ticket transfer system in the system settings by selecting "Default Transfer Type - By Unit." Then, the pop-up transfer ticket window will first display the unit transfer tab.

<figure><img src="/files/MM95tUwqxlM3Oh2lW4vI" alt=""><figcaption><p>System Setting - Default Transfer Type</p></figcaption></figure>

To set unit transfer, go to the **Unit Management** menu. On the unit management page, you can set units that can receive tickets in the **Allowed Transfer to Unit** field for each unit that has been created or will be created in the future in the future as shown below.

<figure><img src="/files/Id8CSRMFdh3D7MT6mOdA" alt=""><figcaption><p>Allowed Transfer to Unit</p></figcaption></figure>

For example, you will add a social media unit to receive ticket transfers from product units. Eventually, groups part of the LOB channel on the Social Media Unit are eligible to obtain tickets from Product Unit channels.&#x20;

<figure><img src="/files/BdJmQvKxkwCVZm636bIo" alt=""><figcaption><p>Unit Transfer</p></figcaption></figure>


---

# 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://docs.3dolphins.ai/customer-service/unit-management/unit-transfer-ticket.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.