A2P 10DLC use cases and SMS examples
Not sure which campaign type to choose? Compare common messaging programs, adapt realistic campaign descriptions, and check that your opt-in flow matches the messages you actually send.
What is an A2P 10DLC campaign use case?
A use case tells the registration ecosystem why a business sends application-to-person text messages to US recipients over standard 10-digit long-code numbers. Your selected use case should match your real messaging activity, sample messages, website, and documented consent method. Brand eligibility, provider options, vetting and pricing can vary.
Before copying any example
Replace the sample business name, URLs, frequency and message purpose with truthful details. Do not claim that customers opted in through a website form if consent actually comes from another channel. The examples below illustrate structure; they are not guaranteed approval wording or legal advice.
Campaign descriptions and sample SMS messages
Each example shows a plausible business workflow. Available use-case labels may differ across Twilio, GoHighLevel and other registration interfaces. Pick the closest eligible category supported by your provider.
1. Customer care / support
Best for: responding to customer service requests and continuing support conversations.
Example description: “Example Repair Co. sends customer support updates and replies to customers who request help through our support form or initiate a text conversation. Messages relate to their open support requests.”
Sample SMS: “Example Repair Co.: We received your request about ticket #1234. Our team will reply shortly. Reply STOP to opt out.”
Consent evidence: Show how customers initiate support or explicitly agree to support texts, including any applicable disclosures.
2. Appointment reminders
Best for: booking confirmations, rescheduling and appointment reminders.
Example description: “Example Dental Clinic texts appointment confirmations and reminders to patients who provide their mobile number and agree to appointment-related SMS when booking.”
Sample SMS: “Example Dental Clinic: Your appointment is booked for Oct 20 at 2:00 PM. Reply C to confirm or call us to reschedule. Reply STOP to opt out.”
Consent evidence: Document the booking form or other genuine permission process.
3. Marketing / promotional
Best for: opted-in offers, promotions, new product announcements and campaigns.
Example description: “Example Home Store sends promotional offers and product announcements to customers who separately opt in to marketing texts on our website.”
Sample SMS: “Example Home Store: Our weekend sale is live. See offers: https://example.com/sale. Reply STOP to opt out.”
Consent evidence: Use an explicit, optional marketing opt-in with required disclosures. Do not treat a purchase or ordinary contact-form submission as automatic promotional SMS consent.
4. Account notifications / alerts
Best for: account status updates, service alerts or other requested non-promotional notifications.
Example description: “Example Service Portal sends account status and service-related notifications to registered customers who choose to receive these updates by SMS.”
Sample SMS: “Example Service Portal: Your support case #1234 has been updated. Sign in to review the change. Reply STOP to opt out.”
Consent evidence: Show the account notification preference or other actual opt-in process. Avoid sending sensitive details directly by text.
5. Delivery and order updates
Best for: order confirmations, dispatch notifications and delivery-status messages.
Example description: “Example Market sends order and shipping updates to customers who request SMS order notifications at checkout.”
Sample SMS: “Example Market: Order #5678 has shipped. Track your delivery at https://example.com/track. Reply STOP to opt out.”
Consent evidence: Document the checkout SMS preference and make sure your submitted samples do not include unrelated promotions.
6. Mixed messaging / mixed use case
Best for: businesses that legitimately send more than one category of messages and whose provider and Brand eligibility support a mixed-use registration.
Example description: “Example Fitness Studio sends class reminders to members who request them and promotional class offers only to members who separately opt in to marketing SMS.”
Sample SMS A: “Example Fitness Studio: Your class starts tomorrow at 8 AM. Reply STOP to opt out.”
Sample SMS B: “Example Fitness Studio: New weekend classes are available. Book at https://example.com/classes. Reply STOP to opt out.”
Consent evidence: Clearly distinguish transactional and marketing permission. A mixed-use label does not eliminate the need for appropriate consent for each message purpose.
What a complete campaign description should explain
Who sends: The same identifiable business shown in your Brand registration and website.
Who receives: The audience that actually opts in, such as customers booking appointments or subscribers requesting offers.
Why they receive texts: The precise purpose of the messages, not vague language like “business updates.”
How they opt in: The real form, checkbox, keyword, verbal process or other permitted consent path, with accessible evidence.
What messages look like: Representative samples including the business identity, expected links where applicable, and opt-out wording as required.
A useful description is specific enough that a reviewer can compare it against your actual signup flow and samples. If you send both reminders and marketing, explain both accurately and make sure the registration category supports them.
Opt-in wording: an illustrative website example
Optional checkbox for promotional texts: “I agree to receive recurring promotional SMS messages from Example Home Store at the phone number provided. Consent is not a condition of purchase. Message frequency varies. Message and data rates may apply. Reply STOP to opt out and HELP for help. See our Privacy Policy and Terms.”
Important: This is a starting example, not a universal compliance template. Your actual disclosures, links, opt-in mechanism and consent records must meet applicable carrier, provider and legal requirements. Keep marketing consent separate from service-related consent when appropriate, and do not preselect the checkbox.
Why a campaign can be rejected even when the use case seems right
Description and samples disagree
You register appointment reminders, but the samples advertise discounts. Either align the content to the actual use case or use an eligible category that accurately represents your messaging.
Opt-in cannot be verified
The signup form is behind a login, broken, or missing SMS-specific disclosure. Provide accessible, truthful evidence of the customer journey.
Business identity differs
The business name in your Brand, website, signup form and texts should be recognizable as the same legitimate sender.
Marketing permission is bundled
A generic agreement to receive service updates is not a substitute for appropriate marketing consent. Collect and document permission that matches the actual message purpose.
How to prepare your submission in GoHighLevel or Twilio
1. Confirm the registered Brand accurately represents your business.
2. Choose an eligible campaign use case based on the messages you genuinely send.
3. Write a specific campaign description identifying recipients, message purpose and opt-in path.
4. Provide representative sample messages and any required opt-in, help and opt-out details.
5. Verify that your website, privacy policy, terms and consent evidence are accessible and consistent.
6. Review the platform's current field requirements and prohibited-content rules before submitting.
Frequently asked questions
Can I use the same campaign description for every business?
No. Describe the real sender, recipients, opt-in process and message purpose for each business. Generic copied wording can contradict your evidence.
Can I register marketing and appointment reminders together?
Only when the provider supports an eligible use case for your Brand and your submission accurately covers both activities. Appropriate consent for promotional messaging still matters.
Is a phone number entered on a form enough for SMS consent?
Not automatically. The collection process must support the actual SMS purpose and applicable consent requirements, particularly for marketing.
Do these examples guarantee campaign approval?
No. Providers, The Campaign Registry and carriers make registration decisions. Examples help organize truthful submissions but cannot guarantee an outcome.
Where can I check current provider rules?
Review Twilio's A2P 10DLC documentation and your own messaging provider's current registration instructions before submitting.
Need help choosing your A2P use case?
I help businesses review campaign descriptions, SMS samples and opt-in evidence for A2P 10DLC registration across GoHighLevel, Twilio and related platforms.