Twilio Error 30538: Message Sample Missing for a Use Case
Updated
Short answer: Error 30538 means your registration was rejected because you selected more than one use case, such as marketing and account notifications, but gave a sample message for only one of them. Write a separate sample for each use case you selected, then resubmit. The code applies to A2P 10DLC campaigns and to toll-free verification.
What error 30538 means
Twilio's title for this code is "30538: A message sample is missing for a selected use case". The error page says "This error applies to both Toll-Free Verification and A2P 10DLC registration" and explains:
"You selected multiple use cases but provided a sample message for only one. Each selected use case needs its own sample."
Twilio gives one cause: "The selected use cases mix content types, such as marketing and informational, but only one sample message was provided." And one fix: "Provide a unique message sample for each use case you selected, then resubmit."
Where you select more than one use case
- A2P 10DLC Mixed campaigns. Twilio describes Mixed as "A campaign that covers multiple use cases such as Customer Care and Delivery Notifications." The Campaign Registry (TCR) says Mixed is "For brands that have multiple use cases and want to run them on the same campaign. Minimum of 2 sub use cases and a maximum of 5 sub use cases."
- A2P 10DLC Low-Volume Mixed campaigns. Twilio: "A campaign that covers multiple use cases, but has a lower monthly fee than the MIXED Use Case (above) and is fixed at the lowest throughput tier." TCR allows a "Maximum of 5 sub Standard use cases."
- Toll-free verification. Use case categories are a list. Twilio's API reference says: "List as many categories as applicable."
How to fix error 30538
- List the use cases you selected. Read them off the rejected campaign or toll-free verification.
- Write one sample for each. A marketing sample should promote something. An account notification sample should be about the account. Each one should look like a message you will really send.
- Follow Twilio's sample rules. For A2P 10DLC, Twilio asks for a "Minimum of two messages. Maximum of five messages." It also says "The Brand must be identified by name and/or website in each message" and "Use square brackets
[]to indicate variable content." Its fix for error 30893 adds: "At least one of the sample messages should include your business name and opt-out message." - Write each sample fresh. Twilio's error 30911 covers registrations that reuse "the same or nearly identical text across multiple registration fields."
- If a use case is wrong, you may need a new campaign. TCR says "once a campaign has been created the use-case cannot be changed." HighLevel says that if the selected use case is incorrect, "it may not be editable during resubmission and you may need to create a new Campaign."
- Resubmit, do not start over. For A2P 10DLC, Twilio says: "If your Campaign fails review, edit and resubmit it rather than deleting it and creating a new one. The vetting fee is only charged once per Campaign, at its first vetting decision, and resubmitting keeps that fee from being charged twice." For toll-free, Twilio's console guide points to Edit & resubmit on the rejected verification, under the Registrations tab in Trust Hub.
An example
A made-up dental office registers a Mixed campaign with two sub use cases, Marketing and Account Notifications. It needs one sample for each:
- Marketing:
Acme Dental: Teeth whitening is 20% off through [Date]. Book at https://acmedental.example/whitening Reply STOP to opt out. - Account notification:
Acme Dental: Hi [First Name], your balance of [Amount] is due on [Date]. Pay at https://acmedental.example/pay Reply STOP to opt out.
Both name the brand, mark the parts that change with square brackets, use a full HTTPS link on the brand's own domain and include opt-out wording.
If you use HighLevel
HighLevel's Chat Widget Setup offers Marketing / Promotional, Informational / Non-Marketing and Mixed. HighLevel says to "Select Mixed when one messaging program genuinely includes both promotional and informational messages", and "When Mixed is selected, HighLevel automatically sets the Campaign Use Case to Low Volume Mixed." The setup then fills in Sample Message #1 and Sample Message #2 for you, along with other fields.
For sample message rejections (error 30893), HighLevel's fix is specific:
- "Use Sample Message #1 for Promotional/Marketing content."
- "Use Sample Message #2 for Transactional/Informational content."
- "For mixed messaging, include at least one sample in each category."
It also warns: "Do not select Mixed simply because you are unsure which use case applies."
Related codes
| Code | Twilio title | What it means |
|---|---|---|
| 30893 | "Campaign vetting rejection - Inconsistency between Sample Message and Use-case" | Samples are missing, unclear or do not match the use case. See A2P sample messages |
| 30911 | "Campaign rejected: Duplicate template text; each field must be unique" | The same or nearly identical text appears in several fields |
| 30916 | "Campaign rejected: Use case mismatch between lead generation and lead nurture" | The use case, description and samples do not describe "a single, consistent use case" |
| 30886 | "Campaign vetting rejection - Invalid Campaign Description" | The description does not explain the program. See Twilio error 30886 |
How to avoid it next time
- Choose Mixed only when one program really sends several kinds of messages.
- Before you submit, write each selected use case next to the sample that shows it.
- Paste your samples into Precheckly's 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 does not know which use cases you selected, so match those yourself.
For other reasons campaigns fail, see why A2P 10DLC campaigns get rejected and the list of A2P 10DLC error codes.
Sources
- 30538: A message sample is missing for a selected use case, Twilio
- A2P 10DLC - Gather the Required Business Information, Twilio
- Troubleshooting and rectifying Campaigns, Twilio
- Toll-free verification console onboarding guide, Twilio
- Toll-free verification resource, Twilio
- 30893: Campaign vetting rejection - Inconsistency between Sample Message and Use-case, Twilio
- 30911: Campaign rejected: Duplicate template text; each field must be unique, Twilio
- 30916: Campaign rejected: Use case mismatch between lead generation and lead nurture, Twilio
- CSP User Guide, April 2026, The Campaign Registry
- A2P Campaign Registration: Step by Step Guide and FAQs, HighLevel
- A2P Campaign Rejections, Required Fixes & Vetting Errors, HighLevel
- A2P 10DLC Campaign Use Cases, HighLevel
Not legal advice. Carrier rules and provider documentation change, so check the linked sources before you rely on them.