A2P 10DLC Sample Messages: Rules and Examples

Updated

Short answer: Twilio asks for two to five sample messages that look like the texts you will really send. Each one names your brand and marks the parts that change with square brackets, and at least one includes opt-out wording such as "Reply STOP to unsubscribe". Samples that do not match your use case are a named rejection reason, error 30893.

How many samples, and how long

Twilio's registration docs: "Minimum of two messages. Maximum of five messages. Each message must be between 20 and 1024 characters in length."

The Campaign Registry (TCR) sets a lower floor for some campaign types: "All campaigns require at least 1 sample message, and some campaign types require a minimum of 2 sample messages." Its table puts Marketing, Mixed and Sole Proprietor campaigns in the two-sample group. 2FA, Account Notifications, Customer Care and Low Volume Mixed need one. Two samples meet both rules.

What every sample needs

  • Your brand. "The Brand must be identified by name and/or website in each message."
  • Brackets for variables. "Use square brackets [] to indicate variable content." Twilio's onboarding guide shows "[Name], [1234], or [Date]".
  • Opt-out wording. Twilio's tip is to include "Reply STOP to unsubscribe" in at least one sample. The fix for error 30893 says the same: "At least one of the sample messages should include your business name and opt-out message."
  • Your real links and phone numbers. "If the Campaign's messages will include links or phone numbers, include them in the sample messages." If you declare that messages include phone numbers but no sample shows one, you can get error 30889.
  • No real customer data. "Don't include real consumer names or phone numbers in your descriptions or samples. Use placeholders like [Name] or [555-555-5555] instead."
  • A match with your campaign. "Sample messages must be clearly aligned with the Campaign description given above and the us_app_to_person_usecase". See how to write the campaign description.

Official examples

An order notification from Twilio's registration docs:

This is a message from the Acme Sandwich Company. Your order for [sandwich type, other item] will be delivered by [time] on [date]. If you have questions or would like to change your order schedule, call 333-444-1212. If you would like to opt out of future notifications like this, text STOP in reply to this message.

An appointment reminder from HighLevel:

Acme Dental: Hi [First Name], your appointment is scheduled for [Date] at [Time]. Reply STOP to unsubscribe.

Twilio also shows two samples that do not work. The first is "Here is your code." with the note "No brand name, no context". The second is "Hi, is this the owner of 123 Oak St? I want to buy your house." with the note "Cold outreach isn't allowed".

Mixed campaigns

If one campaign carries both marketing and informational messages, show both. HighLevel says: "For mixed messaging, include at least one promotional/marketing example and one transactional/informational example when applicable." Its fix for error 30893 is specific: "Use Sample Message #1 for Promotional/Marketing content." and "Use Sample Message #2 for Transactional/Informational content."

Here is a set you can adapt. The brand and links are made up:

  1. Promotional: Acme Fitness: Members get 20% off personal training through [Date]. Book at https://acmefitness.example/training Reply STOP to unsubscribe.
  2. Informational: Acme Fitness: Hi [First Name], your [Class Name] class starts at [Time] on [Date]. Manage bookings at https://acmefitness.example/account Reply STOP to opt out.

Both name the brand at the start and mark variables with square brackets. Both use a full HTTPS link on the brand's own domain and include STOP wording.

Mistakes that get samples rejected

  • A sample that fits a different use case. Twilio's example is an opt-out confirmation used as a marketing sample: "This would be a reasonable opt-out message, but it is not an appropriate sample message for a Campaign whose basic use case is Marketing."
  • Public link shorteners or http:// links. Error 30892 says: "Public shorteners such as bit.ly or TinyURL can cause the campaign to be rejected." HighLevel's advice: "Use full, direct HTTPS URLs when a URL is included." See URL shorteners in SMS.
  • Custom fields in HighLevel. HighLevel says: "Do not include custom fields or values in sample messages." Its own example uses square brackets, such as [First Name].
  • Phone numbers that hide their owner. CTIA: "Messages should not contain phone numbers that are assigned to or forward to unpublished phone numbers, unless the owner (i.e., a person or legally registered business entity) of such phone numbers is unambiguously indicated in the text message."
  • Copies of the same text. Sources differ here. Twilio's sole proprietor guide allows a copy for programs that only ever send one text: "If your specific Campaign use case is such that only a single message text would ever be sent (as for example with One-Time Password messages), you may make the second message a duplicate of the first." Error 30911 and HighLevel ask for distinct samples: "Each sample message must be distinct." Distinct samples meet both.

Before you submit

Paste your samples into the free A2P 10DLC sample checker. It checks that you have at least two samples, that each names the brand and that at least one has an opt-out instruction. It flags public link shorteners, Unicode characters that cost extra segments and samples longer than 3 segments. It does not check use-case fit, opt-in, your website or your privacy policy, so read your samples against your description yourself.

These are carrier and industry rules, not legal advice. For the consent side of your campaign, see SMS opt-in language. For the full list of rejection causes, see why A2P 10DLC campaigns get rejected.

Sources

Not legal advice. Carrier rules and provider documentation change, so check the linked sources before you rely on them.