Phone System · 2 min read
A2P 10DLC Campaign Approval Best Practices
What campaign vetting checks
Campaign approval depends on whether your registration clearly explains who is sending messages, what recipients will receive, why they receive them, and how they agreed. Following these practices improves your chances, but the final decision is made by the carriers and registration partners.
A complete submission clearly establishes:
- Brand: who is sending the messages.
- Use case: why messages are being sent.
- Campaign description: who receives the messages, what they receive, and how they opt in.
- Sample messages: what real messages will look like.
- Opt-in flow: how recipients give consent.
- Website: a working site that represents the registered business.
- Privacy Policy and Terms & Conditions: public pages that support the messaging program.
Campaign approval checklist
Before you submit, confirm that:
- The use case matches the messages you plan to send.
- The description names the sender, the recipients, the purpose and the consent method.
- Sample messages look like messages you'll actually send, include your business name and include opt-out language such as "Reply STOP to unsubscribe."
- Your website is live and public, and isn't behind a login or under construction.
- A reviewer can see your opt-in step, such as a public form with a consent checkbox.
- Consent language says what messages people agree to receive, how often, that message and data rates may apply, and how to opt out.
- Your Privacy Policy states that mobile information won't be shared with third parties for marketing.
Common mistakes to avoid
- Using a public link shortener in sample messages. Use your own domain.
- Describing marketing messages but choosing a non-marketing use case.
- Pointing to a website that doesn't match the brand name.
- Making the SMS consent checkbox required to submit a form.