> ## 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.

# 10DLC use cases and consistency

> Choose the right use cases for a 10DLC campaign, and keep the description, consent, website, and sample messages consistent with them.

Under **Messages are for**, you choose the types of messages the campaign
sends. Reviewers then check that every other part of the campaign matches that
choice. A mismatch is the most common reason for a rejection, with code 602
or 603.

> [!WARNING]
>
> You can't change the use cases after you submit the campaign. If they are
> wrong, register a new campaign with the right use cases.

## Use cases

Choose between one and five use cases. Choose only the types of messages you
will send.

| Use case | Use it for |
| - | - |
| Login codes | One-time passcodes and login verification. |
| Account notifications | Updates about a customer's account, such as a password reset or a low balance. |
| Customer support | Support conversations and account help. |
| Order & delivery updates | Order, shipping, and delivery status. |
| Fraud alerts | Warnings about suspicious activity on an account. |
| Higher education | Messages from colleges and universities. |
| Marketing & offers | Promotions and offers to people who opted in. |
| Polls & surveys | Surveys and polls that are not political. |
| Public service announcements | Information in the public interest. |
| Security alerts | Notices about a security event on an account. |

If any message promotes a product, a sale, or an offer, choose **Marketing &
offers**. Reviewers treat a promotion inside a notification as marketing.

## Keep the campaign consistent

Reviewers compare these parts of the campaign with each other. They must all
describe the same business and the same types of messages:

1. **Use cases:** the types you chose under **Messages are for**.
2. **Website:** the brand's website, and the page where people opt in.
3. **Description:** who sends the messages, what they are, and who receives them.
4. **Opt-in:** the consent text and **How people opt in and out**.
5. **Sample messages:** at least one sample for each use case.

Check each pair:

| If you chose | Then |
| - | - |
| Marketing & offers | The consent text and the description say that people receive marketing, and a sample is a promotion. |
| Login codes | A sample contains a code, and the consent text mentions login or verification codes. |
| Several use cases | The consent text names all of them, and each has its own sample. |
| Any use case | The website and the samples are for the registered brand. If they name another business or product, the description explains how it belongs to the brand. |

## Write the description

The description tells reviewers who sends the messages, what the messages are,
and who receives them.

```text wrap theme={null}
Example Co sends order confirmations, shipping updates, and delivery alerts to customers who buy on example.com and agree to receive texts at checkout.
```

A description like "We send notifications to our users" is too vague, because
it doesn't name the business, the message types, or the recipients.

## Examples of inconsistent campaigns

* The campaign is for **Login codes**, but the opt-in form and the description
  talk about account updates and offers.
* The description says the messages are appointment reminders for a car repair
  shop, but the website is for an accounting firm.
* The campaign is for **Order & delivery updates**, but one sample message
  offers a discount. Add **Marketing & offers** in a new campaign, or remove
  the offer.
* The samples mention a product name that appears nowhere in the brand's
  details or on its website.


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