> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/private-panels/emailing-and-sms/how-to-send-mass-sms.md).

# How to send mass SMS

{% hint style="info" %}
**Note:** Sending mass SMS is an add-on feature that you can get during the sales conversation. You can also talk to our support at <support@dscout.com> to get this feature for your subscription.
{% endhint %}

Also, you can only send SMS, whether it's an individual SMS or a mass SMS, within a study. Hence, you need to add the panelists to a study before you can send them SMS messages. Then, you can use that study like a contacts list. (Note an SMS segment is 160 characters. If your SMS is greater than 160 characters, it will count as **Num Characters in SMS** divided by **160** in terms of charge).

After you've created the study and added the panelists to it, you can follow the steps below to send them a mass email:

{% stepper %}
{% step %}
Open the created study, then go to its **Overview** sub-page.
{% endstep %}

{% step %}
Click the ticked checkbox icon beside the **Full Name** column header. Then, click **Select all** from the drop-down options.

![](/files/2faaa1ad228588bb685a74cc33aa0848a52efed7)
{% endstep %}

{% step %}
Click the **Send message** button, then select **Send SMS** from the drop-down options.
{% endstep %}

{% step %}
The **Send SMS** window will pop up. Type your message on the **Message** textbox. You can add **Merge Tags** to your message by clicking its drop-down button then selecting from the merge tag you'd like to add. It will be automatically added to your clipboard, then you can paste it on any location within the **Message** textbox.

Merge tags are dynamic fields that are automatically replaced with the recipient's details. When you're writing the message, the merge tag will be enclosed in curly brackets {} to set it apart from regular text.
{% endstep %}

{% step %}
After you've added your message, click the **Send to \[#] people** button.

![](/files/9b9c873ac41d882fa0235926482a7b9509733d29)
{% endstep %}
{% endstepper %}

## SMS Opt Out

A panelist will automatically be Opted Out of your panel by sending one of the following messages: **cancel, end, quit, unsubscribe, stop, stopall**. If this happens, the default panel property SMS Opt-In will change to False, and no further SMS can be received by the participant.

![](/files/c350c98d5e6382930559b3969e0ec6393b1851ef)

Additionally, if you try to message a participant that has opted out of SMS communications, you'll see a red error state to prevent sending the message.

![](/files/73d60617de7787c342473dc99c3bc9196a0eeeb5)

{% hint style="info" %}
**Note:** Private Panels was previously managed outside of Dscout, so you may see a different logo and URL in some places. If you have any questions, contact <support@dscout.com>.
{% 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://help.dscout.com/private-panels/emailing-and-sms/how-to-send-mass-sms.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.