# Bulk

Bulk SMS works about the same as our [bulk email](/event/planning/members/bulk-emails.md) feature.

## New

When creating a new bulk text message you are just asked to come up with a name.

### Setup

**Body**: The SMS content

{% hint style="success" %}
This text area supports [variables](/event/misc/variables.md).
{% endhint %}

{% hint style="danger" %}
The event carries the responsibility to make a guess on the length of the message and thereby how many message segments will be sent. To help calculate, use [this](https://twiliodeved.github.io/message-segment-calculator/) tutorial.
{% endhint %}

**Send at**: The actual date and hour when this message should be sent.

{% hint style="warning" %}
Every event company can send a maximum of 1 message per hour.
{% endhint %}

**Filter**: Pick the filter you want to use. Every result in that filter with a working phone number will receive this message. This feature makes it very easy to fine grain who the recipients will be.

## Sending

After you have created and finalised your message you will need to **request approval** before the platform will send it as we do not allow any marketing via our communication module. Click the green button to request approval. Our team will approve or reject the request within maximum **24 hours**. Most of the time it will be approved within the hour.

### Approved

If your message is approved it will be added to the sending queue and will automatically start sending on the hour you specified in the "**Send at**" value. This process might not start exactly on the hour (0 minutes), but can take up to 3 minutes to start sending.

### Rejected

If your message is rejected, you will receive an email at your personal email address informing you of this with a personal message why it has been rejected. You can edit the message, resolve the issues and request approval again.

## Recipients

After the message has finished sending you can see a list of recipients and the exact message they received. Open up a recipient to view more data:

**Receiver**: A link to the receiver of this message

**To phone number**: The phone number + country we've sent the message to

**Body**: The processed message content we sent

**Sent at**: The exact timestamp when the message was sent

**Status**: The delivery status of this message. The status can be <img src="/files/cLDXfEKwD93d6adU7y3O" alt="" data-size="line"> or <img src="/files/P2ng5W8uskdaHsdiUCM6" alt="" data-size="line">. When it failed there will be a **Failure message** datapoint to explain you why it failed.

Status also includes a badge <img src="/files/e5TGbxs07evTy9fdQxS7" alt="" data-size="line"> of the number of segments. Every segment is calculated as an SMS message.


---

# Agent Instructions: 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:

```
GET https://docs.eventication.com/event/communication/text-messages/bulk.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.