> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/general/sac-360/sac-360o-automations/sac-360o-automation-transferring-service/sac-360-service-transfer.md).

# SAC 360° - Service Transfer

In SprintHub, it is possible to transfer services, allowing the centralization of sales, support, and other areas, resulting in greater efficiency in both service and the team.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FItHtQGg2fcFuM81kPXOw%2Fgm2.png?alt=media&amp;token=33704c84-d8f0-4b6c-b4ee-3590f97908b4" alt=""><figcaption></figcaption></figure>

In day-to-day customer support, ensuring that each request is routed to the correct department is essential to maintain agility, organization, and the quality of the customer experience. With that in mind, the **SAC 360** allows you to automate the transfer of support cases between departments, streamlining the team’s workflow and avoiding manual rework.

In this article, you will learn how to set up an automation to route conversations directly to the responsible department, according to criteria defined in the operation.&#x20;

It is worth noting that this tutorial focuses on transfer to departments; however, the platform also offers the possibility of routing the support request to a specific user, depending on the needs of your workflow. This practice contributes to more strategic support, ensuring that each demand is handled by the most suitable team.\
\
Below, check out the full step-by-step guide to implement this automation and improve the management of your support tickets.

{% embed url="<https://youtu.be/CUyx-yPl6vI>" %}

**Attention:** after running this automation, it is important to use the filter within the SAC, always keeping the corresponding department selected. In this way, you will be able to correctly view the support tickets that were routed to it, avoiding the impression that the conversations were not transferred or were lost in the process.