> For the complete documentation index, see [llms.txt](https://docs.textbelt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.textbelt.com/compliance.md).

# Compliance

Textbelt is implementing changes in response to regulatory and compliance requirements.  These changes are effective January 3rd, 2023.

### Sender identification

A "sender name" is the name of the business, organization, or person you're representing when you send an SMS.  *Every SMS conversation must include the sender name*.

{% hint style="warning" %}
If an SMS message does not contain your sender name the first time you message someone, the sender name will be automatically appended to your message.
{% endhint %}

There are two ways to set the sender name:

* **Account-wide:** Set a default sender name by going to `https://textbelt.com/account?key=<your key>`
* **Per-message:** Set the `sender` parameter in your POST request.

Sender name is *not* appended if it appears elsewhere in your message, or if you are sending follow-up messages.

{% hint style="warning" %}
Sender name value is used strictly for compliance purposes.  It does *not* override the "From" number for the SMS sender.
{% endhint %}

### Opt-out

An "opt-out" is a way for the customer to block future SMS.  Textbelt handles opt-outs automatically, but regulations require senders to include opt-out information in their SMS.

The standard form of opt-out is "Reply STOP to unsubscribe".  This opt-out is appended automatically the first time you message a new user.  It is *not* appended if "STOP" appears elsewhere in your message.

#### Opt-in

To opt back in, the recipient must send "START" in reply.  There is no way to force the recipient to opt back in.  Only the original recipient can opt-in.


---

# 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.textbelt.com/compliance.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.