> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/form-management/campaigns/campaign/phone-sms-distribution/sms-distribution.md).

# SMS Distribution

## 📄 What is SMS distribution ?

Using the phone sms distribution features you can easily send out invitations to a list of mobile phone numbers who receive by SMS a uniquely generated code to take your survey. This unique code allows you also to restrict access to the survey and to track if the invited respondents have answered your survey or not.

{% hint style="info" %}
🧙  You may also replace the uniquely generated codes by any pre-generated code of your choice using the [token](/form-management/security/security-items/tokens.md) features. 
{% endhint %}

 Mobile phone recipients can be added 

* [Manually entered mobile phone lists](/form-management/campaigns/campaign/phone-sms-distribution/sms.md)
* [Imported using a CSV file](/form-management/campaigns/campaign/email-distribution/recipients.md)
* [Using members of panel](/form-management/campaigns/campaign/panels.md)

{% hint style="warning" %}
While automatically enabled during the campaign launch its important to note that the i[nvitation code security item](/form-management/security/security-items/invitation-code.md) must be enabled on your survey to validate the invitation codes and to link the email to the respondent.
{% endhint %}

{% hint style="danger" %}
The mobile SMS phone feature requires to have a [Twilio.com](/installation-setup/system-settings/mobile-messenging/twilio.md) account linked to your ngSurvey account.  
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ngsurvey.com/form-management/campaigns/campaign/phone-sms-distribution/sms-distribution.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.