> 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-360-automation-action-when-resolving-service.md).

# SAC 360° Automation - Action when resolving service

How to build an automation that occurs when resolving a service. For this example, the Leads will be added to a segment.

***

## Initial settings

For this example, an automation called "**Finished without Trigger**". The purpose is to segment the Leads that have already been completed, in order to use this information in filters or other automations. For this, there will be no Triggers, but Conditions can be used if necessary.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FHVqaJrfXSd6FpRxmX4Ai%2Fautomacao-1.png?alt=media&amp;token=26a90894-8859-4e09-a51c-20903dc28ffc" alt=""><figcaption><p>Adding a title to the automation.</p></figcaption></figure>

## Configuring the action and status limitation

In Actions, *'Modify the Lead segments'*, edited to add the Lead to an instance segment — To learn how to create a segment, [*click here*](/en/topics/relate/segments.md).

In Limit to channels, only '*Completed*' can be included in Limit to statuses; in this way, the automation will occur only for completed attendances.

Click on '*Save Automation*' and it will be ready!

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FoDmg0Dq1f7ejBXGMnOhW%2Fautomacao-2.png?alt=media&amp;token=862b787a-1cee-4c24-8f69-140a86a5f564" alt=""><figcaption><p>Adding to the segment and limiting to the status '<em>Completed</em>'.</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.sprinthub.com/en/topics/general/sac-360/sac-360o-automations/sac-360-automation-action-when-resolving-service.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.