> 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/relate/segments/segment-delete-leads-that-do-not-have-support-in-sac-360.md).

# Segment - Delete leads that do not have support in SAC 360

### Introduction

In lead management, it is essential to maintain a clean and up-to-date database. Leads that do not receive service can take up unnecessary space and resources. In the segment, deleting these leads can be facilitated through the creation of specific segments and automation flows. 

{% hint style="danger" %}
Deleting leads will mean that you will never again have access to the leads or be able to handle them; it is recommended that you archive the leads instead of deleting them.
{% endhint %}

{% embed url="<https://docs.sprinthub.com/topicos/geral/leads/leads-como-arquivar>" %}

### Identifying Leads Without Service

Before deleting any lead, it is necessary to identify them accurately. Sprinthub offers a segment feature that allows you to group leads based on specific criteria. To identify leads that have not received service, follow the steps below:

### Creating a Segment of Leads Without Service

**Access the Segments Area**:

<figure><img src="/files/c833e4975b56f40a9814dbd4ee37d5f0774a75ce" alt=""><figcaption></figcaption></figure>

**Create a New Segment**:

* Click "Create New Segment".

<figure><img src="/files/a8604dc24f96c50cf51a269f653da5bcef403fbb" alt=""><figcaption></figcaption></figure>

* Give the segment a name, such as "Leads Without Service".

<figure><img src="/files/c0a915b56f2ed860c9b76bfe59194b4eb5deb20d" alt=""><figcaption></figcaption></figure>

**Define the Segment Criteria**:

* Configure the segment to include leads that do not have service records. Use filters such as "Does the Lead have a support ticket in SAC?" equal to "No"

<figure><img src="/files/643613b46e5c0c34f2869ab8fceb3b78803d3c50" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/3a98311ebd416508f3e8d1e43f8e861b5396e95a" alt=""><figcaption></figcaption></figure>

**Save the Segment**:

* After defining the criteria, save the segment. It will be updated automatically, adding leads that match the defined criteria.

<figure><img src="/files/b4a32405aab614e166b0f7f90f4063f77ae34507" alt=""><figcaption></figcaption></figure>

### Deleting Leads Manually

With the segment of leads without service created, you can choose to delete these leads manually. This method is straightforward and gives you full control over which leads will be deleted.

#### Steps for Manual Deletion

**Access the Created Segment**:

* Go to the "Leads Without Service" segment.

<figure><img src="/files/a0399fe3a0df7b91fb2f5e8197b8a164e31a28df" alt=""><figcaption></figcaption></figure>

**Select the Leads**:

* Check the leads you want to delete. You can select 120 at a time for deletion or choose individually.
* Click the delete option and confirm the action. The selected leads will be removed from the database.

<figure><img src="/files/008c7cfd715cfee14bf164735da5eca92f11c591" alt=""><figcaption></figcaption></figure>

### Deleting Leads by Automation Flow

For greater efficiency and time savings, lead deletion can be automated. Sprinthub allows the creation of automation flows that can include deleting leads without service.

### Deletion by automation flow

**Access the Automation Flow Area**:

<figure><img src="/files/d23bd2223fb045525d123fb4baa216c6620f128a" alt=""><figcaption></figcaption></figure>

**Create a New Automation Flow**:

* Click "Create New Flow".
* Give the flow a name, such as "Deletion of Leads Without Service" and define the segment.

<figure><img src="/files/f0b285f876f898c2a797aab301e200fcdd4e5c09" alt=""><figcaption></figcaption></figure>

**In the builder:**

* Set the condition so that the flow is triggered when a lead is in the "Leads Without Service" segment.

<figure><img src="/files/899c215f62a91e38f7e5c085017c411e6400b1bd" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/63684536b3e3469f1a1b08dca7235e186ca0f7f7" alt=""><figcaption></figcaption></figure>

* add the action "Delete Lead". Which will warn again that:

<mark style="color:red;">**Attention: Deleting a lead is an irreversible action, and all of its data will be permanently deleted.**</mark>

<figure><img src="/files/295d6336b46f60e6bd1138bf44849841e098d804" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/08fb86385fe056ba79fa67d33b55fa8734619f3b" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/3ea76402f1dcd8b6582f2740d74a9e1951e8f18f" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/76d1f3517402c5e18941d6e9971ab05c2f6da42c" alt=""><figcaption></figcaption></figure>

* **Final builder result:**

<figure><img src="/files/6e80bd3f5761deac31933dbaa2fe419a778f6017" alt=""><figcaption></figcaption></figure>

**Save and Activate the Flow**:

* Save the automation flow and publish it. From now on, any lead that is added to the segment will be automatically deleted.

{% hint style="danger" %} <mark style="color:red;">REMEMBER THAT THIS ACTION IS IRREVERSIBLE.</mark>
{% endhint %}


---

# 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/relate/segments/segment-delete-leads-that-do-not-have-support-in-sac-360.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.