- July 26,2026
- 24 days ago

Getting a 10DLC campaign approved for marketing SMS requires more than selecting "Marketing" as the use case and submitting a few promotional message examples.
Marketing traffic receives closer attention because recipients are being contacted for promotions, offers, sales, or other commercial purposes. Reviewers need to understand who is sending the messages, how consumers agreed to receive marketing texts, what those messages will contain, and whether the website and consent flow support the campaign being registered. Current Bandwidth and Twilio guidance puts particular emphasis on the campaign description, call-to-action or message flow, opt-in evidence, sample messages, and related website information.
For businesses using TextTorrent's guided A2P 10DLC setup, the safest approach is to prepare the marketing program before submitting the registration. Teams planning bulk SMS campaigns should know exactly where contacts come from, what those contacts agreed to receive, and what messages will be sent after approval.
That becomes especially important in industries such as insurance, where promotional messaging may exist alongside policy servicing and customer support, or MCA, where a campaign must clearly distinguish consented funding-related follow-up from unexplained cold outreach.
Businesses that are still learning the registration process should first understand why 10DLC registration is required. The Campaign Registry describes 10DLC as an A2P channel in which brands and messaging providers are verified before business messaging is enabled.
For marketing campaigns, one operating rule matters more than almost anything else:
Your registration must clearly demonstrate that people knowingly agreed to receive the type of promotional messages you intend to send.
Marketing SMS generally includes messages designed to promote products, services, sales, discounts, offers, fundraising activity, or other commercial opportunities.
Examples include:
Acme Home: Save 20% on selected patio furniture through Sunday. Shop at [URL]. Reply STOP to opt out.
or:
Northstar Auto: Summer service specials are available through [Date]. Schedule at [URL]. Reply STOP to opt out.
The important issue is not whether the message contains the word "sale."
It is the purpose of the communication.
A company might send both transactional and promotional messages to the same customer, but those messages represent different purposes.
For example:
Your appointment is confirmed for Friday at 2 PM.
is operational.
Book another service this week and receive 15% off.
is promotional.
Do not classify a marketing campaign as customer care or account notifications simply because those categories appear easier to explain.
The campaign use case should represent the traffic you actually intend to send.
Before opening the registration form, document how the campaign will work.
You should be able to answer:
Where do contacts come from?
How do they provide their phone number?
Where do they agree to marketing SMS?
What disclosure do they see?
What promotional content will they receive?
How frequently might they receive messages?
How can they opt out?
This exercise prevents a common registration problem: different teams describing different versions of the same program.
Marketing may think contacts come from a landing-page form.
Sales may manually import phone numbers.
Operations may use an existing CRM list.
The registration then describes only the cleanest workflow.
That creates a verification gap.
Register the program you actually operate, not the version that sounds easiest to approve.
Consent is the central issue for marketing SMS.
Twilio's current campaign approval guidance distinguishes marketing messages from transactional communication and says marketing campaigns require documented evidence such as a checkbox, form, or keyword opt-in rather than relying on verbal permission.
Bandwidth's current vetting guidance likewise provides marketing opt-in examples that explicitly tell consumers they are agreeing to receive marketing text messages.
That means the consent mechanism should not merely collect a phone number.
It should make the messaging purpose understandable.
Phone Number: __________
Submit
Nothing tells the visitor that submitting the number enrolls them in promotional messaging.
[ ] I agree to receive promotional text messages from Acme Home at the number provided. Message frequency varies. Message and data rates may apply. Reply STOP to opt out and HELP for help. See Privacy Policy and Terms.
The exact disclosure should match the business's actual messaging practices and applicable requirements.
Do not blindly copy another company's consent language.
A consent checkbox should represent an affirmative consumer action.
If the box is already selected when the page loads, the consumer is being asked to remove consent rather than provide it.
TextMagic's current consent guidance specifically advises against pre-checked boxes, while provider vetting guidance commonly treats improperly implemented opt-in mechanisms as a registration problem.
So this:
☑ Send me promotional text messages.
should normally start as:
☐ Send me promotional text messages.
Also review whether marketing SMS consent is unnecessarily bundled into another required action.
If a customer must agree to promotional texts simply to request unrelated information, the consent flow may not clearly demonstrate voluntary marketing enrollment.
One of the weakest campaign-registration answers is:
Customers opt in on our website.
That does not explain enough.
Bandwidth identifies incomplete call-to-action information as a common campaign-vetting issue and provides detailed examples of how opt-in workflows should be described.
Your CTA description should explain the actual journey.
For example:
Customers visit example.com/offers and enter their name and mobile number. Beneath the phone-number field, an unchecked checkbox allows customers to separately agree to receive promotional SMS from Acme Home. The disclosure includes message-frequency information, message and data rate language, STOP and HELP instructions, and links to our Privacy Policy and Terms. Customers must select the checkbox before being added to the marketing SMS list.
That description gives the reviewer something concrete to evaluate.
If someone reading only your CTA description cannot reproduce the consumer journey, add more detail.
Your consent process may be excellent and still create problems if nobody can verify it.
If registration says:
Users subscribe at example.com/sms
but that URL returns a 404 page, requires an employee login, or redirects somewhere unrelated, the evidence does not support the submission.
TextMagic currently recommends providing a direct link or screenshot when opt-in occurs behind a login or on a paper form.
For public forms, test the complete flow before submitting.
Check:
The exact URL loads.
The form is visible.
SMS disclosure appears near the relevant field.
The checkbox works.
Privacy Policy and Terms links work.
The page works on mobile.
No staging password is required.
Do not assume the reviewer will search your site to find the correct form.
Give them the shortest path to the evidence.
A marketing campaign description should not hide behind vague language.
Weak:
We communicate with customers about our services.
Better:
Customers who explicitly opt in through our website receive promotional SMS about seasonal discounts, product offers, new services, and limited-time sales from Acme Home.
The second version communicates the actual purpose.
Bandwidth's current registration best practices state that campaign descriptions and other campaign details are reviewed and that insufficient information can delay approval.
Do not make reviewers infer that the campaign is promotional.
If it is marketing, describe it as marketing.
Message samples are evidence of what production traffic will look like.
Twilio's current registration documentation requires samples to reflect the content of the campaign and align with the campaign description. It also instructs applicants to identify the sender and represent variable information appropriately.
Hello! Check out our latest deal.
Who is sending it?
What kind of campaign is this?
Better sample:
Acme Home: Hi [First Name], save 15% on selected outdoor furniture through [Date]. Shop at [URL]. Reply STOP to opt out.
The second message reveals:
Brand
Promotional purpose
Variables
Link usage
Opt-out instruction
If your campaign will send links, represent links realistically.
If you will include phone numbers, show those where appropriate.
If you send different kinds of promotions, use samples that demonstrate meaningful variation.
Marketing registrations are easier to evaluate when every field supports the others.
Use this sequence:
Marketing Use Case → Campaign Description → Opt-In → Sample Messages
Imagine this submission:
Campaign description: Seasonal product discounts.
Opt-in disclosure: Receive account and order updates.
Sample message: Apply today for financing.
Nothing matches.
The problem cannot be fixed by polishing one sentence.
The entire campaign needs to represent one messaging program.
Twilio's troubleshooting documentation specifically shows campaign rejections where descriptions and samples need to be rewritten because they do not represent the designated marketing purpose.
Ask:
If a reviewer saw our opt-in page first and our message samples second, would the messages look like something the customer knowingly signed up to receive?
If the answer is uncertain, fix the campaign before submission.
Your website policies should not contradict your registration.
Bandwidth includes privacy-policy and Terms & Conditions problems among campaign-vetting concerns.
Review whether your policies accurately address the SMS program and actual data practices.
Depending on the program and provider requirements, relevant information may include:
Brand or program identity
Types of messages
Message-frequency language
Message and data rate disclosure
STOP instructions
HELP instructions
Privacy practices
Contact information
Do not paste a generic SMS policy onto the website simply to satisfy registration.
If your consent form promises one thing and your Terms describe something else, the inconsistency can create another review problem.
Having a phone number is not the same as having consent for marketing SMS.
This distinction becomes operationally important when a company obtains contacts through:
Purchased lists
Lead vendors
Shared databases
Old CRM exports
Event attendee lists
Business directories
A marketing registration needs to accurately explain how the intended recipients agreed to receive the messages.
A statement such as:
We have a list of potential customers.
does not establish a consent workflow.
TextMagic's current messaging guidance emphasizes retaining proof of consent, particularly for marketing and promotional communication.
If you cannot explain where the marketing consent came from, solve that issue before registering the campaign.
11. Make STOP and HELP Handling Operational, Not Decorative
Your registration may say:
Reply STOP to opt out.
Your production system must then honor STOP.
Bandwidth's vetting documentation includes requirements around opt-out messaging and expects the opt-out confirmation to make clear that additional messages will no longer be sent.
The same principle applies to HELP.
Do not treat those statements as registration copy disconnected from the messaging application.
For marketing campaigns especially, suppression needs to be reliable across scheduled campaigns, bulk sends, automations, and future contact imports.
An opted-out number should not accidentally re-enter the marketing audience because a team uploads another spreadsheet later.
10DLC approval and message deliverability are related, but they are not the same thing.
Bandwidth explicitly notes that campaign registration and vetting do not systematically eliminate spam blocking.
After approval, production traffic can still create problems if it differs materially from the registered program or generates negative carrier signals.
For example:
You register clean, consent-based retail promotions.
Then production traffic uses unrelated domains, materially different content, or audiences that did not follow the registered opt-in process.
Approval does not make that traffic automatically acceptable.
Teams scaling promotional campaigns should therefore combine registration discipline with practical carrier-filtering controls.
A Marketing 10DLC Approval Checklist
Before submitting, verify:
Legal business information is accurate.
Website clearly represents the registered business.
Marketing is the correct campaign purpose.
Campaign description explicitly explains promotional traffic.
Contacts actively consent to marketing SMS.
Consent is not hidden inside a generic phone-number form.
Marketing checkbox is not preselected.
CTA description explains the complete enrollment process.
Public opt-in URLs work.
Non-public consent methods have appropriate supporting evidence.
Privacy Policy is accessible.
Terms are accessible where required.
Sample messages clearly identify the brand.
Samples look like real marketing traffic.
Samples match the campaign description.
Links and phone numbers are represented appropriately.
Opt-out instructions are included appropriately.
STOP requests can actually be honored in production.
The opt-in language and messages describe the same program.
Do this before submitting, not after the first rejection.
Start with the rejection reason.
Do not immediately rewrite every field.
If the issue is the CTA, inspect the real opt-in page.
If message samples are rejected, compare them with the campaign description.
If the website is the problem, open the submitted URL anonymously.
If consent cannot be verified, improve the evidence rather than simply writing a longer paragraph claiming that consent exists.
Current ClickSend guidance summarizes the same underlying principle: provide accurate brand and campaign information, clearly explain how users opt in, and submit samples that match the actual use case.
Fix the evidence that caused the rejection.
Then review the entire campaign again before resubmitting.
Final Takeaway
Getting 10DLC approval for marketing SMS is primarily an exercise in proving consistency and consent.
The reviewer should be able to understand:
Who is sending the marketing messages?
What promotions will be sent?
Where did recipients sign up?
Did they knowingly agree to promotional SMS?
Can that consent process be verified?
Do the sample messages match what they agreed to receive?
Can recipients easily opt out?
The strongest marketing submissions do not try to make promotional traffic look transactional.
They describe the marketing program accurately.
They show a clear consent path.
They use realistic message samples.
And the website, policies, registration fields, and production plan all tell the same story.
Before submitting, walk through the campaign as a customer and then review it as a stranger.
If both perspectives lead to the same conclusion—this person clearly requested these marketing messages from this business—the campaign is much easier to evaluate and approve.