> 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/message-queue.md).

# Message Queue

At SprintHub, you can send mass messages, whether via **WhatsApp** or **Email**, providing more agility and efficiency in communication with your contacts.

{% embed url="<https://youtu.be/r73OM1Q4ZSw>" %}

### How to access the Message Queue

Access:

**Menu >> Link >> Message Queue**

Or type the function in the **Find Services**.

Then:

1. Click on **“New”**;
2. Set up your message queue.

***

### Queue Settings

When creating a new queue, define the following information:

* **Source WhatsApp**: select which number will be used to send the messages.
* **Enable queue**: select **YES** to activate the queue. If it is set as **NO**, it will remain frozen and without sends.
* **Queue name**: choose an internal name for identification.
* **Segment**: select the segment that will receive the messages.

After finishing:

1. Click on **Save & Close**;
2. Then click **Apply**.

*If you don't yet have a segment created, see the article below:*

{% content-ref url="/pages/430a797159546371edd1e2fbb2a4fe8a2e3ddca4" %}
[Segments](/en/topics/relate/segments.md)
{% endcontent-ref %}

After saving, click the name of the desired queue to start configuring the send.

***

### Message Queue Stages

When accessing the queue, you will see three stages:

* **Unpublished**
* **In Queue**
* **Sent**

To start a message, click on the **“+”** of the stage **Unpublished**.

***

### Message Setup

Choose the sending channel:

* **Email**
* **WhatsApp**
* **WhatsApp Template**

> **Tip:** Before setting up your queue, we recommend checking out our article on **Sending Methods**, where we explain the differences between **WhatsApp, Email, and WhatsApp Template**, as well as the best usage practices.\
> [WhatsApp - Ways to Send Messages and Templates](/en/strategies/whatsapp/whatsapp-ways-to-send-messages-and-templates.md)
>
> [Email Marketing - Ways to Send](/en/topics/relate/email/email-marketing-ways-to-send.md)

After choosing the desired channel, configure the message according to the type of send.

***

#### Sending via WhatsApp

Fill in the following information:

* **First name**: internal name of the message.
* **Message**: text that will be sent to contacts.
* **File**: upload files or images, if necessary.
* **Send Using**: select the source WhatsApp.
* **Schedule for**: choose whether the send will be immediate or scheduled for a specific date.

#### Attention to file sending

When adding a file, image or media to the send, it will be counted as an additional send, separate from the text message.

In other words, if an image is attached, it will be sent first and the text will be forwarded afterward, not together with the image.

#### Customization with Tokens

You can use **tokens** to automatically personalize messages.

Example:

`{contactfield=firstname}`

This token makes the system address the contact by the **first name registered**, making communication more personalized.

In addition, you can also use:

* **ChatGPT** to help modify texts before sending;
* **Quick Replies** to insert saved messages more quickly.

***

#### Sending via Email

In email sending, you will be able to:

* Define an **internal name** for the message;
* Select an **already created email**;
* Or write a **quick email**;
* Define whether the send will be **immediate** or **scheduled**.

***

#### Sending via WhatsApp Template

In sending via WhatsApp Template, configure:

1. **The message that will be sent**;
2. **The source WhatsApp number**;
3. **The send schedule**, being able to choose between:
   * Send immediately;
   * Send after minutes, hours or days;
   * Schedule a specific date and time.

***

### Publishing the Message

After saving, the message will initially remain in the column **Unpublished**.

To start sending, simply move the message to the column **In Queue**.

From that moment on, forwarding will begin automatically.

***

### How sending works

Every **5 minutes**, an automatic trigger is run to start processing and sending the queue's messages.

Tracking of sends can be done through the column **Sent**.

### Tracking and Send Status

Click on the **chart icon** to view:

* Send status;
* Detailed message information;
* Possible errors that occurred during the send.

It is also possible **to export this information** for tracking and analysis.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FqklouwLagKll45WbINdT%2Fimage.png?alt=media&amp;token=7fd832f7-3aa4-4f0a-b4d9-7bd2d1a7d628" alt=""><figcaption></figcaption></figure>

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FNn0Pow3VPiRiJnlf23Wa%2Fimage.png?alt=media&amp;token=26401fd9-9466-42b8-a151-d197377b6bd7" alt=""><figcaption></figcaption></figure>

### Reusing a Message Queue

If you want to perform a new send using a queue that has already been sent, there is no need to create a new one from scratch.

You can **make a copy of an existing queue**, allowing:

* **Resend the same message again**;
* **Edit the queue information**, such as message, segment or scheduling;
* **Perform a new send with adjustments**, without losing the original configuration.

This option is ideal for recurring campaigns, similar announcements, or actions that need to be reused with small changes.

After making the copy, just edit the desired information and follow the normal queue publishing process.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2F2FNCO4znT6yut2nbV3jH%2Fimage.png?alt=media&amp;token=a5f6095b-d732-4827-9ff7-aa2181803bcd" alt=""><figcaption></figcaption></figure>

***

### Update in the Contact History

When performing a send through **Message Queue**, the action will be automatically recorded in the **contact history**.

You will be able to view:

* Which number the send was made from;
* The name of the message queue used.

This ensures more **transparency and traceability** in the communication process.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcpSdNW6GBpuG0zxduo__sT3CvDC8LCFa0xGYpCMNah4KIiaCnhweyJSvlJm0o27C32Xyo1_hR2OJRe7BaLCfks7a_aJAYRGR6byHGCCXyc6_LMdIypgSdLrerXboCC7z9AYMG46Q?key=TQodu6M7EvA-YnBUOvys0MeB" alt=""><figcaption></figcaption></figure>

***

### Warning

We recommend following Meta's guidelines to avoid restrictions or a ban on the WhatsApp number used in sends.

**Also check:**

{% content-ref url="/pages/35bdf44a71a1bbf1687996908673e54c358418c8" %}
[Best practices with WhatsApp Web](/en/strategies/whatsapp/best-practices-with-whatsapp-web.md)
{% endcontent-ref %}

***

### Conclusion

The **Message Queue** is a feature that allows you to automate and organize bulk sends in a practical way, whether by **WhatsApp**, **Email** or **WhatsApp Template**.

With it, you can segment contacts, schedule sends, personalize messages with tokens, and track send status, ensuring more control and efficiency in communication.

If you have any questions, consult the related articles or contact SprintHub support.


---

# 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/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.
