Campaign details (601–611)
| Code | What carriers found | What to do |
|---|---|---|
| 601 | The campaign settings don’t match the website or the sample messages. | Make Messages contain links and Messages contain phone numbers match your sample messages. If either is on, a sample must contain a link or a phone number. |
| 602 | The use cases don’t match the description, the consent text, or the sample messages. | Make those details consistent, and include a sample for each use case. See Use cases and consistency. |
| 603 | The brand, website, description, opt-in, and sample messages describe different businesses. | Make them describe the same sender. If a sample names another business or product, explain in the description how it belongs to the brand. See Use cases and consistency. |
| 611 | The START, STOP, or HELP response is incomplete. | Include the brand name, message frequency, rates, HELP, and STOP in the START response. See Keyword responses. |
Content and sender (701–713)
| Code | What carriers found | What to do |
|---|---|---|
| 701 | Cannabis, CBD, or hemp content. | Carriers don’t accept this content. Contact Photon support if the campaign was misclassified. See Prohibited and restricted content. |
| 702 | Firearms or ammunition content. | Contact Photon support to check whether the use case is supported. |
| 703 | Sexual content that is not permitted. | Contact Photon support if the campaign was misclassified. |
| 704 | Gambling content, such as casinos, sports betting, or lotteries. | Contact Photon support to check eligibility before you resubmit. |
| 705 | Hateful or abusive content, or profanity. | Contact Photon support if the campaign was misclassified. |
| 706 | Alcohol content without age verification. | Contact Photon support to confirm eligibility and the age checks you need. |
| 707 | Tobacco or vaping content. | Contact Photon support to check whether the use case is supported. |
| 708 | Lead generation or affiliate marketing, such as selling or sharing contacts with third parties. | Remove lead-generation activity from the campaign and the website. Contact Photon support to review the business model. |
| 709 | High-risk financial services, such as payday loans, debt relief, credit repair, crypto, or trading signals. | Contact Photon support to check whether the use case is supported. |
| 710 | The registered brand is not the business that sends the messages, for example an agency instead of its client. | Register the brand of the business that sends the messages. See The sender must be the registered brand. |
| 711 | The same tax ID (EIN) is used for several brands. | Contact Photon support to confirm the correct brand and explain why the brands share a tax ID. |
| 712 | The campaign looks like direct lending, but the registration doesn’t say so. | Contact Photon support to review the classification. |
| 713 | A large company uses an email address that is not on its own domain. | Change the brand’s contact email to an address on the company’s domain. See Brand verification. |
Verification and opt-in (801–807)
| Code | What carriers found | What to do |
|---|---|---|
| 801 | The business doesn’t qualify as a sole proprietor. | Register the brand as a business with its EIN. See Personal brands. |
| 802 | The sole proprietor is not yet authorized. | Contact Photon support. |
| 803 | The opt-in forces consent: the checkbox is missing, or both the checkbox and the phone number are required. | Add an optional SMS consent checkbox that is unchecked by default. See Opt-in form. |
| 804 | Carriers can’t verify the brand’s website: it is missing, broken, or doesn’t describe the business. | Publish a working website that shows the business name, address, phone, email, and services. See Brand verification. |
| 805 | The privacy policy doesn’t say that mobile opt-in data is not shared with third parties. | Add the statement and link the policy from the opt-in form. See Privacy policy and terms. |
| 806 | Reviewers can’t verify the opt-in: the path to the form, HELP, STOP, frequency, rates, or the privacy policy is missing. | Rewrite How people opt in and out and complete the consent text. See Message flow and Opt-in form. |
| 807 | The website is not authentic or complete enough to verify the business. | Complete the website so that reviewers can check who the business is and what it does. |
Privacy and consent text (851–861)
| Code | What carriers found | What to do |
|---|---|---|
| 851 | The privacy policy and the START response are both incomplete. | Fix the privacy policy’s sharing statement, and include the brand, opt-out instructions, and support contact in the START response. |
| 852 | The privacy policy doesn’t say that mobile opt-in data is not shared. | Add the statement and remove any text that contradicts it. See Privacy policy and terms. |
| 861 | The consent text and the keyword responses are incomplete. | Name the brand and the message types, and include frequency, rates, HELP, STOP, and policy links. Complete the START, STOP, and HELP responses. |