WritingSMS compliance

The 10DLC campaign description and sample messages that passed

Ours, word for word, with what each part is doing. Plus what "not qualified for this use case" actually means, which is rarely about your wording.

BrandBloom8 min read

The 10DLC campaign description and sample messages that passed. An article by BrandBloom.

The campaign description is the box most people fill in last, in about ninety seconds, using words chosen to be safe. It is also the second most common reason a submission comes back, after the privacy policy. Those two facts are connected: the safe-sounding version is the one that fails.

This is the description and the five sample messages that got BrandBloom's own campaign approved on 24 September 2026. They are here to be copied and adapted, and below each one is an explanation of what the words are doing, so you can adapt rather than paste and hope.

The description that passed

Appointment reminders and booking confirmations for website design clients who requested a consultation through the contact form at brandbloom.org, plus replies to enquiries and occasional service updates. Contacts opt in by ticking an unchecked SMS consent box on the form where they submit their phone number. Reply STOP to unsubscribe.

Sixty-odd words. Four things are in there on purpose.

Who is being messaged. Not "our customers". Website design clients who asked for a consultation. A reviewer can open the site, find that consultation form, and confirm such a person exists.

Where they came from. A named form on a named domain. This is the sentence that lets a reviewer verify the rest, because it tells them exactly which page to open. Leaving it out means they have to go looking, and a reviewer who has to go looking is a reviewer who may not find it.

How consent was given. The mechanism, in plain words, including the fact that the box starts unticked. The reviewer is going to check this anyway. Saying it first means your description and the page agree, and agreement is the thing being assessed.

What they actually receive. Reminders, confirmations, replies, occasional updates. Specific enough to check against the samples further down.

Why the vague version fails

The instinct is to write something broad enough to cover anything you might ever send. It comes out looking like this:

Text messages are used to communicate with our customers and leads about our services and offers.

Every word of that is true. It is still refused, and the reason is worth understanding because it applies to the whole submission.

The reviewer's job is not to decide whether your messaging sounds reasonable. It is to verify that what you described matches what your website shows. A description with no specifics gives them nothing to check. Nothing to check means nothing can be confirmed, and an unconfirmable claim is treated as a failed one rather than a neutral one.

Being vague feels like reducing your exposure. It actually removes the only thing that could have got you through.

The second problem with the broad version is scope. "Our services and offers" covers marketing. If you selected a use case that does not include marketing, you have just described something your campaign is not registered to do, and that contradiction is its own rejection.

"Your requested 10DLC campaign is not qualified for this use case"

If that is the message you got, this is what it means.

It is not about your wording. It is about the use case you selected sitting underneath your description. You picked a category, and something in your submission describes messaging that the category does not permit, or your business type is not eligible for the category you chose.

The usual causes, in order of how often we have seen them:

  • Marketing language under a non-marketing use case. You selected something

like Customer Care or Account Notification, then described "offers", "promotions" or "special deals" in your samples or description. Pick a mixed or marketing use case, or take the marketing out of both.

  • **A sole proprietor brand against a use case that needs a registered

business.** Sole proprietor registrations carry tighter limits, including lower throughput and a narrower set of permitted use cases. If you registered as a sole proprietor and picked a category built for registered companies, the mismatch is structural and no rewording fixes it.

  • A restricted category in disguise. Lending, debt relief, gambling,

cannabis, firearms, cryptocurrency and a few others are restricted or barred outright regardless of how carefully the description is written. If your business sits near one of these, read the restricted list before you rewrite anything.

  • A description that spans two categories. Appointment reminders and

promotional offers are different use cases. Describing both under a single non-mixed campaign puts the description outside whatever you selected.

The fix is almost always to change the use case, not the words. Resubmitting the same category with politer wording is the most common way to collect a second rejection.

The five sample messages

Five is the usual requirement. These are ours, exactly as submitted:

1. BrandBloom: Hi [First name], thanks for your enquiry. We have your details and someone will reply today. Reply STOP to unsubscribe. 2. Hi [First name], this is a reminder of your consultation with BrandBloom on [Date] at [Time]. Reply YES to confirm or NO to reschedule. 3. BrandBloom: your consultation is confirmed for [Date] at [Time]. We will send the meeting link by email shortly. 4. Hi [First name], we have sent your onboarding form by email. Reply to this message if anything on it is unclear. Reply STOP to unsubscribe. 5. BrandBloom: your website is live. Thanks for your patience through the build. Reply HELP for help or STOP to unsubscribe.

The rules those five satisfy, each one worth checking on your own:

  • At least one carries the business name. Ours carry it four times out of

five. There is no cost to it and it is the cheapest check to pass.

  • At least one carries the opt-out. Ours carry it three times. Putting STOP

in every single message is not required and makes your samples read like nobody wrote them.

  • At least one carries HELP. Often checked alongside STOP. Sample five has

both, which is enough.

  • Variables are in brackets. [First name], [Date], [Time]. A reviewer

reading Hi John, your appointment is Tuesday cannot tell a template from a one-off, and a one-off is not a campaign.

  • They match the description. Reminders, confirmations, replies, a service

update. Nothing promotional, because the description did not claim anything promotional.

  • They read like a person wrote them. This one is not in any rulebook and

it matters anyway. Samples lifted off a help page describe a business that is not yours, and the mismatch against your website is exactly what a human reviewer is looking for.

Note what is not in there: no discount, no "limited time", no emoji, no link shortener. Shortened links are worth avoiding on their own account, because carriers treat public URL shorteners as a filtering signal.

Writing your own, in order

Fill this in rather than starting from a blank box. Keep it to one paragraph.

[What you send] for [who receives it] who [how they came to be on the list] at [your domain]. Contacts opt in by [the exact mechanism, including that the box is unticked]. Reply STOP to unsubscribe.

Then, in this order:

  1. Pick the use case first, before writing a word of the description. The

category constrains what the description is allowed to say, so writing the description first means rewriting it.

  1. Write the description against your actual forms. Open the form. Describe

what it does. If the description says something the form does not do, change whichever one is wrong, and often it is the form.

  1. Write the samples from your sent messages if you already send any. Real

ones beat invented ones because they are already in your voice.

  1. Read the description and the samples together, as a stranger would. Ask

whether one contradicts the other. That contradiction is the single thing a human reviewer is most reliably good at spotting.

  1. Check both against your website one last time. The description names a

page. Open that page. Make sure the consent box is on it and unticked.

The part that trips people after approval

Approval is granted against the description and the samples you submitted. That is the boundary of what you are registered to send.

Getting a reminders campaign approved and then sending a promotional blast under it is not a grey area, it is sending outside your registration, and the consequence lands on your number rather than on your paperwork. If your plans change, the campaign changes with them.

Not written from the outside

We have taken one campaign through this, our own, including getting it wrong first. That is a smaller claim than most pages on this subject make, and it is the honest one. What is above is what we submitted and what was approved, not a summary of somebody else's guidance.

The other half of the same job is the consent wording on the page the description points at. That is covered in why GoHighLevel keeps rejecting your A2P campaign, including the automated check that reads only your checkbox labels and fails things that are plainly visible one line below.

If you would rather someone else did this, we will read your submission and your site and write down what is failing, at no charge: send us the site.


Written September 2026, from our own registration, approved 24 September 2026. Due for review March 2027. Carrier rules change without announcement.

Read next