# SAC 360 - Closing Cases After a Period

In this video, you will learn an efficient strategy to automate the closing of service requests in SAC 360.\
\
With this solution, it will be possible to identify requests that remain in a specific stage for a determined period and end those interactions automatically, keeping your workflow organized and agile.

This automation is ideal for teams that deal with a large volume of requests and need to avoid build-ups in intermediate stages. I will show you how to configure this strategy step by step, ensuring your SAC operates smoothly and efficiently.

Ready to optimize your service with this practical solution? 🎥✨

{% embed url="<https://www.youtube.com/watch?feature=youtu.be&v=haQ5UB8ZtnQ>" %}

<br>


---

# Agent Instructions: 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:

```
GET https://docs.sprinthub.com/en/topics/general/sac-360/sac-360-tutorial-videos/sac-360-closing-tickets-after-a-period.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.