Registration Best Practices
- 17 Oct 2024
- 2 Minutes to read
- Contributors
- Print
- DarkLight
Registration Best Practices
- Updated on 17 Oct 2024
- 2 Minutes to read
- Contributors
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Registration Best Practices
Please review the best practices below prior to submitting your registration. Failing to comply with any of these will very likely result in campaign denial and filtering or blocking of messages.
Best Practices: Consistency & Content
| Issue | Best Practice |
Do not include forbidden use cases to avoid resulting in Campaign rejection | Make sure your A2P Campaign does not involve prohibited content such as cannabis, hate speech, etc. |
Consistency in brand, website and sample messages | The brand and website need to be the same that the ones you include in your sample messages. |
| Consistency in sample messages and use cases | If you register a political campaign, but your sample messages say "Your one-time password is: 123456", your campaign will be rejected. |
| Consistency in email domain and company name | If you register a brand as Mogli , but you provide an email address with the gmail domain, your campaign will be rejected. This only applies to large corporations that should have dedicated email domains. |
| Send messages according to the brand that you registered | If you register a brand for a technology company, but end up sending messages for a different customer from a construction company, your campaign will be rejected. |
| Embedded Number or Links | If you expect to include a phone number or link within messages, provide sample messages containing that LIVE phone number or link. Without this, messages sent including phone numbers or links will likely be filtered. and not received. |
Best Practices: Opt In
| Issue | Best Practice |
| Submit only real, working websites | You must provide a website address that is accessible. If your website opt in is gated, you must provide screenshots along with an explanation of the opt in process. |
| Include the opt-out language in at least one of the sample messages included in your registration submissions | You need to include the opt out option in your sample messages, something like "Please reply STOP to opt out". |
| Call to Action (CTA) specific to text messages only | As of October 14, 2024, the call-to-action (CTA) for text messaging must be exclusive to messaging. Separate CTAs are required for email and voice communication. This means that forms must have separate opt-in checkboxes and verbiage for SMS vs email or phone opt-in. |
| Website opt-in forms cannot require phone numbers | As of October 14, 2024, website opt-in forms for collecting text messaging consent cannot have mandatory phone number fields, which is now considered a forced opt-in. The phone number field should be optional. |
| Express opt-in for text messages only | As of October 14, 2024, every text messaging CTA capturing a phone number must have opt-in language that is specific to text messaging as well as a checkbox specific to opting into SMS. A single opt-in checkbox should not include email or phone call permissions - these need to be collected separately. Opt in language must include consent and opt out instructions, as well as message frequency disclosures. Example: Message frequency varies. |
| Privacy Policy | The privacy policy CANNOT allow for the sharing/selling of end user information to their parties or affiliates. |
| Make sure consumer opt-in is collected appropriately & is provable | Ensure you send messages only to people who really want to receive them. Generally, business message senders should:
|
Want more details? Please refer to the CTIA guidelines to see detailed instructions and best practices on handling consumer consent, privacy policies, etc.
Was this article helpful?