Skip to main content
A 10DLC campaign is reviewed before it can send SMS to US numbers. It first goes through a compliance review, and then the carriers review it. If either review rejects the campaign, its status changes to Action required. The campaign page then lists what the reviewer found. This page shows you how to read the findings, fix them, and resubmit the campaign. Each requirement has its own guide:

​
Find the review findings

1

Open the campaign

Open Organization settings. Under Compliance, select 10DLC registration. In Campaigns, select the campaign marked Action required.
2

Read the latest review

Review history lists each review step, with the newest first. A failed step, such as Compliance review failed or Carrier review failed, shows the reviewer’s findings under its date.

​
Read the findings

One rejection can contain several findings. Each finding describes one problem. Fix all of them before you resubmit, because the reviewer checks the whole campaign again.
  • Links: a finding can end with a link to a page in these docs. That page explains the requirement and shows how to meet it.
  • Reviewer notes: a finding can be followed by a note that starts with Note:. The note tells you what the reviewer saw on your campaign, for example a sign-up page with no SMS consent text. Fix the problem in the note as well as the general finding.

​
Common findings

The use cases you select under Messages are for can’t change after you submit the campaign. Reviewers check that the consent text people agree to names each of these use cases. For example, a campaign registered for account notifications and marketing needs consent text that mentions both. To fix this finding, do one of the following:
  • Change the consent text on your opt-in form, and in How people opt in and out, so that it names every use case. Name marketing explicitly, for example: “You agree to receive marketing texts from Example Co.”
  • If the campaign will not send some of these message types, register a new campaign with only the use cases that your consent covers.

​
The sender must be the registered brand

Recipients must be able to tell which business is texting them. That business must be the brand that the campaign is registered under. Reviewers compare the brand with the campaign description, the sample messages, the website, and the opt-in form.
  • Use the brand name in the consent text, the sample messages, and the keyword responses.
  • If the description or the sample messages mention a product or business name that is not the brand name, explain in the description how it belongs to the brand. For example: “Example App is a product of Example Co.”
  • If you send messages for other businesses, such as the customers of your platform, register a brand and a campaign for each of those businesses. One brand’s campaign can’t send another business’s messages.
  • The brand’s website must work and must identify the business. It must show the business name, what the business does, and how to contact it.

​
Fix and resubmit

1

Fix what is outside Photon

Update your website, opt-in form, privacy policy, or terms first, and publish the changes. Reviewers open these pages, so they must be public and must not require a sign-in.
2

Edit the campaign

On the campaign page, under What to do now, select Edit the campaign. Change the fields that the findings name, and then select Save. Saving is free. Nothing goes to the reviewers until you resubmit.
3

Resubmit for review

Under Resubmit for review, use What changed to describe the fixes you made outside Photon, such as the URL of your updated opt-in form. This field is required if you did not change the campaign in Photon. Then resubmit the campaign.
The registration fee is charged again each time you resubmit. It isn’t refunded if the campaign is rejected again, so fix every finding before you resubmit.

​
Check before you resubmit

  • The opt-in form is at a public URL, or How people opt in and out has a public link to a screenshot of it.
  • The consent text names the brand and every use case. It also gives the message frequency, says that message and data rates may apply, and tells people to reply STOP to opt out and HELP for help.
  • The SMS consent checkbox is optional and unchecked by default.
  • The privacy policy says that mobile information is not sold or shared with third parties for marketing. The opt-in form links to the privacy policy and to the terms.
  • Every sample message names the brand and matches a use case. At least one sample message tells people how to opt out.
  • Every link in the campaign opens without a sign-in.

​
Guides

Opt-in form

The phone number field, the consent checkbox, and the full consent text a web form must show.

Message flow

Templates for web forms, verbal consent, paper forms, and text keywords.

Privacy policy and terms

The privacy statement reviewers look for, and how to keep your terms consistent with it.

Sample messages and keywords

Sample messages and START, STOP, and HELP responses that pass review.

Use cases and consistency

Choose the right use cases and keep every part of the campaign consistent with them.

Prohibited content

Content and business types that carriers don’t accept on 10DLC numbers.

Brand verification

Brand details carriers can verify, and how to fix the ones they flag.

Rejection codes

What each carrier rejection code means and what to change.