> 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/crm/crm-automations/crm-automation-for-segmenting-opportunities-and-using-a-message-queue.md).

# CRM - Automation for Segmenting Opportunities and Using a Message Queue

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2F754E63So4lJI3ySisqQo%2Fimage.png?alt=media&amp;token=741265fd-5c46-4c6b-9fa7-b9c8a472ea12" alt=""><figcaption></figcaption></figure>

In the funnel, there are many open potential Lead opportunities and you would like to contact them? In SprintHub, you can do that. See our step-by-step guide:

First of all, if you haven't yet registered a segment for separating Leads, I'll send you the step-by-step guide for **"Segment Registration"** in our knowledge base.

{% embed url="<https://docs.sprinthub.com/~/changes/1V3HNAqEVHPWgYVQqsHc/tutoriais/relacionar/segmentos>" %}

To begin, select the desired funnel and stage. Next, we'll set up an automation to segment contacts and send messages through the Message Queue.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2Fyc5du4lcQE4VHxEcqPon%2Fimage.png?alt=media&amp;token=8dd012cb-ede6-4d02-9507-700a91f22b7a" alt=""><figcaption></figcaption></figure>

By clicking the icon, we'll create it in the Stage where you want to implement the automation.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2Fv9p8HyIPQ0NOlm0WUoS7%2Fimage.png?alt=media&amp;token=9c2699c1-2ee7-4b24-9139-fe50693ab0cc" alt=""><figcaption></figcaption></figure>

When starting the Automation setup, it is not necessary to define a **"Trigger"**, only **"Condition"** and **"Action".** Below, we'll demonstrate some alternatives for **"Conditions"**

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FS0iTBUwuJ3yc0tiXUX4G%2Fimage.png?alt=media&amp;token=4e8ba52d-cf88-4db1-865b-be02d40d9b92" alt=""><figcaption></figcaption></figure>

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FRRy5oAsDErAXzVoUt2DB%2Fimage.png?alt=media&amp;token=4cc0693e-74d4-4d38-be28-705c5ca97378" alt=""><figcaption></figcaption></figure>

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FD3QZJD18nAyOgVaPtrcQ%2Fimage.png?alt=media&amp;token=aca7b265-2f64-4de2-a85d-4c42da2794d0" alt=""><figcaption></figcaption></figure>

Now let's define the **"Action"** of the Automation, which can be **"Remove the existing Segment and include the new one"** or **"Just add a second Segment"**

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FDhmxzEopguq4G42n4Sdy%2Fimage.png?alt=media&amp;token=37c5096c-466b-4645-bb5b-5aac4703e25a" alt=""><figcaption></figcaption></figure>

In "Additional Settings", it is possible to define the triggering by opportunity

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FESBqgn9FGjdger1eMNFh%2Fimage.png?alt=media&amp;token=25474a10-d203-4184-b2bb-c991695a7ea3" alt=""><figcaption></figcaption></figure>

Just click "Save" and then activate the Automation in the Stage.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FcDkIxzAjtVMqVdkwc1tS%2Fimage.png?alt=media&amp;token=4b74346d-1c52-442e-b1e2-19fc3bc9dcd1" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Remember that the Automation can be included in the Stage along with the existing opportunities.
{% endhint %}

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FrWxDi2YO9bPG1osTrzig%2Fimage.png?alt=media&amp;token=ae812ac4-067a-49b3-b8e3-a091d9a362ec" alt=""><figcaption></figcaption></figure>

To help with setting up a **"Message Queue"**, I'll provide a step-by-step from our knowledge base. Remember that it is possible to define a **"Sending Schedule"**, if desired.

{% embed url="<https://docs.sprinthub.com/~/changes/1V3HNAqEVHPWgYVQqsHc/tutoriais/relacionar/fila-de-mensagens>" %}


---

# 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/crm/crm-automations/crm-automation-for-segmenting-opportunities-and-using-a-message-queue.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.