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

# Sample messages and keyword responses

> Write 10DLC sample messages and START, STOP, and HELP responses that match your brand and the campaign's use cases.

Reviewers read a campaign's sample messages and keyword responses to check
what you will send. Both must match the brand, the use cases, and the
description of the campaign.

## Sample messages

* **How many:** add at least one sample for each use case under **Messages are
  for**, and never fewer than two. You can add up to five.
* **Brand name:** start each sample with the brand name, so that the recipient
  knows who is texting.
* **Match the use cases:** each sample must be a message that the campaign's use
  cases allow. For example, a campaign for appointment reminders can't have a
  sample that is a discount offer.
* **Opt-out:** at least one sample must tell people how to opt out, for
  example: "Reply STOP to opt out."
* **Links and phone numbers:** if **Messages contain links** is on, include a
  link like the ones you will send. If **Messages contain phone numbers** is on,
  include a phone number.
* **Realistic:** write the messages that you will really send, with realistic
  values in place of personal details. Keep each sample under 160 characters
  where you can.

### Examples

```text wrap theme={null}
Example Co: Your order #1042 has shipped and arrives Thursday. Track it at https://example.com/orders/1042. Reply STOP to opt out.
```

```text wrap theme={null}
Example Co: Reminder: your appointment is on March 5 at 2:00 PM. Call (555) 010-0100 to reschedule. Reply HELP for help, STOP to opt out.
```

## Keyword responses

Each campaign has a response for each of three keywords. You enter them under
**Keyword responses**. Each response can be up to 320 characters long.

| Keyword | When it is sent | Template |
| - | - | - |
| START | A person opts in by text. | \[Brand name]: Thanks for subscribing to \[types of messages]! Reply HELP for help. Message frequency may vary. Msg & data rates may apply. Consent is not a condition of purchase. Reply STOP to opt out. |
| STOP | A person opts out. | \[Brand name]: You are unsubscribed and will receive no further messages. |
| HELP | A person asks for help. | \[Brand name]: For help, contact us at \[email address, phone number, or support page URL]. Reply STOP to opt out. |

The HELP response can link to a website, but that page must show clear contact
details.


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