> 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-360-tutorial-videos/sac-roulette-no-restrictions-on-leads-tickets.md).

# SAC Roulette - No Restrictions on Leads/Tickets

In customer service operations, especially in SAC teams, it is common for tickets to remain for long periods in the “Waiting” stage, depending on manual triage or distribution. This bottleneck reduces service agility, harms the customer experience, and can create an unequal distribution of workload among agents

To eliminate this problem, an effective solution is the implementation of a SAC roulette: an automated mechanism that distributes service cases sequentially and evenly among agents. This way, no ticket is left without initiation and all are handled fairly and in an organized manner.

In this article, you will learn how to configure an efficient SAC roulette, capable of starting services automatically and keeping the queue always moving, optimizing your team's workflow.

Check the tutorial below.<br>

{% embed url="<https://youtu.be/PKAWODvhK18>" %}


---

# 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.sprinthub.com/en/topics/general/sac-360/sac-360-tutorial-videos/sac-roulette-no-restrictions-on-leads-tickets.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.