> ## Documentation Index
> Fetch the complete documentation index at: https://docs.photon.codes/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use Stable documentation by default. Honor an explicit Beta request or a URL under /docs/beta/. If the requested version conflicts with the installed CLI package or API origin, clarify the target before writing integration code.
> Pages under /docs/beta/ document Beta; other product pages document Stable. Keep the CLI package, commands, API origin, and credentials within the selected version. State the documentation version in your answer.
> For MCP search, always pass version: Stable or version: Beta. Unfiltered search mixes both versions. For filesystem reads, keep Beta queries under /beta/ and exclude /beta/ from Stable queries; discover paths before reading them.
> The public docs base is https://photon.codes/docs. Convert MCP page paths to public URLs under that base, preserving /beta/ when present. Read https://photon.codes/docs/skill.md for version selection and https://photon.codes/docs/llms.txt for the version indexes.

# Describe how people opt in

> Fill in the How people opt in and out field of a 10DLC campaign, with a template for web forms, verbal consent, paper forms, and text keywords.

The **How people opt in and out** field of a campaign tells reviewers how a
person agrees to receive your texts before you send the first one. Reviewers
follow your description and check each step. Review findings call this field
the message flow, the opt-in workflow, or the call to action (CTA).

## What to include

* **The opt-in method:** a web form, verbal consent, a paper form, or a text
  message to your number. One method is enough. If you use more than one,
  describe each.
* **Where it happens:** the exact URL and the place on the page, the keyword
  and the phone number, or the situation in which your staff ask for consent.
* **The consent text:** the exact words that people see or hear when they opt in.
* **A screenshot link:** if reviewers can't open the opt-in themselves, link
  to a public screenshot or photo of it. Use this for a pop-up, a page behind a
  sign-in, a mobile app, or a paper form.
* **A privacy policy link:** the URL of your privacy policy.
* **How to opt out:** for example, "Reply STOP at any time to opt out."

The field can be up to 2,048 characters long.

## Templates

Choose the template for your opt-in method and replace each part in brackets.

**Web form**

```text wrap theme={null}
People opt in on [page URL], in the [form name] form at [where the form is on the page]. The form has an optional SMS consent checkbox that is unchecked by default, with this text: "By checking this box, you agree to receive [types of messages] by text from [Brand name]. Message frequency may vary. Message and data rates may apply. Reply STOP to opt out. Reply HELP for help. We will not share mobile information with third parties for promotional or marketing purposes." Screenshot of the form: [public screenshot link]. Privacy policy: [privacy policy URL]. People can reply STOP at any time to opt out.
```

The form itself must meet the [opt-in form requirements](https://docs.photon.codes/docs/beta/messaging/sms/10dlc/opt-in-form.md).

**Verbal consent**

```text wrap theme={null}
When a customer [calls us / visits our office], our staff read this statement: "By providing your phone number, you agree to receive [types of messages] by text from [Brand name]. Message frequency may vary. Message and data rates may apply. Reply STOP to opt out. Reply HELP for help. We will not share mobile information with third parties for promotional or marketing purposes." When the customer agrees, staff record the phone number, and we send this text: "[Brand name]: You agreed to receive [types of messages]. Msg frequency varies. Msg & data rates may apply. Reply STOP to opt out, HELP for help." Privacy policy: [privacy policy URL].
```

For marketing, political, or charity messages, verbal consent needs a
second confirmation. See [Double opt-in](#double-opt-in).

**Paper form**

```text wrap theme={null}
During [an appointment / sign-up / renewal], customers fill in a paper form. They write their phone number and sign below this text: "By signing this form and providing your phone number, you agree to receive [types of messages] by text from [Brand name]. Message frequency may vary. Message and data rates may apply. Reply STOP to opt out. Reply HELP for help. Consent is not a condition of purchase. We will not share mobile information with third parties for promotional or marketing purposes." Photo of the form: [public link]. Privacy policy: [privacy policy URL].
```

**Text a keyword**

```text wrap theme={null}
We show the keyword [KEYWORD] and the number [phone number] on [our website / flyers / a QR code / receipts]: [public link or screenshot]. When a person texts [KEYWORD] to [phone number], we reply: "[Brand name]: Thanks for subscribing to [types of messages]! Msg frequency varies. Msg & data rates may apply. Reply HELP for help, STOP to opt out. We will not share or sell your mobile information for marketing or promotional purposes." Privacy policy: [privacy policy URL].
```

If people opt in by sending any first message to your number, not a
keyword, describe where they find the number, and use your reply to their
first message as the confirmation.

## Double opt-in

When people opt in by phone or in person, marketing, political, and charity
messages need a second confirmation by text:

1. After the person agrees, send a confirmation that asks them to reply YES to
   also receive the marketing, political, or charity messages.
2. Send those messages only to people who reply YES. Everyone else receives
   only the other message types that they agreed to.

Describe both texts in **How people opt in and out**. For example:

```text wrap theme={null}
[Brand name]: You agreed to receive [types of messages]. Msg frequency varies. Msg & data rates may apply. Reply STOP to opt out, HELP for help. To also receive marketing messages, reply YES.
```

## Rules for every method

* **Name marketing:** if the campaign sends marketing, the consent must say so,
  for example: "You are opting in to receive marketing texts from \[Brand name]."
* **Donations:** political campaigns must say whether donations will be
  solicited, for example: "Donations will not be solicited."
* **Lending:** campaigns about any type of lending can only use a web form or a
  paper form. Verbal and text opt-in are not accepted for lending.
* **Timing:** collect consent before you send the first message.

## Example

This description is too vague, and reviewers reject it:

```text wrap theme={null}
Users opt in on our website.
```

This description lets the reviewer find and check the opt-in:

```text wrap theme={null}
People opt in on https://example.com/signup, in the account sign-up form below the email field. The form has an optional SMS consent checkbox that is unchecked by default, with this text: "By checking this box, you agree to receive order updates and delivery alerts by text from Example Co. Message frequency may vary. Message and data rates may apply. Reply STOP to opt out. Reply HELP for help. We will not share mobile information with third parties for promotional or marketing purposes." Screenshot of the form: https://imgur.com/a/example. Privacy policy: https://example.com/privacy. People can reply STOP at any time to opt out.
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.