> 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-saving-the-date-of-the-last-service.md).
# SAC 360º Automation - Saving the Date of the Last Service
## Creating a Custom Field
In this example, a **custom field** to store the **date of the last contact**.\
This field will be used later to identify **idle leads** — that is, those who have not been in contact for a significant period — allowing better control over the **lead limit over time**.
Custom Fields (Lead).
Creating a Date-type field.
## Setting Up Automation
The automation must contain the following minimum settings:
1. A title, which will be displayed in the automation list.
2. The action **Update lead data**, with the token `{function=today}`, to record the current day in the lead field.
3. Limit automation execution to contacts with the status **Completed**.
Then just save the automation, and start it for the already open contacts.
360º Customer Service Automation.
Action Update lead data.
Limit to the statuses.
## Filtering leads that haven't been contacted for months
To filter all leads in the database that **haven't been contacted for more than X days** (or **for less than X days**), it is necessary to create a **segment with a filter**.\
When a segment has filters, it becomes **dynamic** — that is, all leads that meet the defined conditions will be **automatically included** in this segment. For this example, the condition **'The value of the lead field...'**.
This allows, in the future, the creation of **automations** from this group of leads, such as a **mass deletion** or the application of **follow-up strategies**.
Defining the segment name.
Filter Conditions.
---
# 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-360o-automation-saving-the-date-of-the-last-service.md?ask=&goal=
```
`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.
