> 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-360-automation-for-restricting-tickets-and-opportunities.md).

# SAC 360 - Automation for Restricting Tickets and Opportunities

The automation for restricting service cases and opportunities aims to ensure that only the agent who starts the service is responsible for managing that case. This not only increases the team's efficiency, but also ensures that each service is handled with due attention, without interference from other professionals. In addition, the automation minimizes the risk of lack of follow-up, promoting faster and more focused service, keeping each salesperson with their lead.

In this tutorial you will see: 

* User Access Permissions
* Customer Service Automation

Check out the step-by-step:

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

<br>


---

# 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-360-automation-for-restricting-tickets-and-opportunities.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.