A2P 10DLC Use Cases: Which One to Register for Reminders, Follow-Ups & Notifications

If you've already hit the wall where your texts mysteriously stop delivering, start with our full A2P 10DLC registration guide — it covers what A2P is and why US carriers block unregistered business SMS. This article picks up where that one leaves off and answers the question people actually get stuck on: for the specific messages my business sends, which use case do I register, and how do I avoid getting rejected?

Quick reset on the one thing that trips everyone up: A2P 10DLC applies to any business sending SMS to US numbers over a standard 10-digit local number — not just marketing. Appointment reminders count. Order updates count. "Thanks for reaching out, when works for a call?" counts. The carriers don't care that your message is helpful. They care that your business is registered and that what you send matches what you registered.

The use case is just "what kind of texts will you send?"

When you register a campaign, you pick a use case — a label that tells carriers the purpose of your messages. Get it right and approvals are faster and delivery is cleaner. Get it wrong and you risk rejection, filtering, or messages silently dropping. Here are the buckets that cover almost every service business:

Use case	What it's for	Example message
Customer Care	Conversations, support, and follow-up with people you're already working with	"Hi Jordan, following up on your quote — any questions before we lock in your date?"
Account Notifications	Status updates about a booking, account, or order	"Your appointment is confirmed for Thu 2pm. Reply C to cancel."
2FA / Verification	One-time codes and identity checks	"Your verification code is 654321."
Marketing	Promotions, offers, and re-engagement to people who opted in	"Spring special: 15% off bookings this month. Reply STOP to opt out."
Mixed / Low-Volume Mixed	A blend of the above — common for small businesses sending both helpful and promotional texts	Reminders + the occasional offer from the same number

Mapping your real messages to a use case

Lead follow-up sequences

The "new lead comes in, we text them within 60 seconds, then follow up over a few days" flow is the highest-value automation most service businesses run. Because it's a conversation with someone who just inquired, it usually fits Customer Care — or Mixed if your follow-ups sometimes include an offer. Make sure your intake form captures clear consent to text them.

Appointment & booking reminders

Reminders, confirmations, and reschedule notices are transactional. They map cleanly to Account Notifications (or Customer Care). These are low-risk and approve easily as long as the recipient opted in when they booked.

Service, shipping & delivery updates

"Your technician is on the way," "your order shipped," "out for delivery" — all Account Notifications. Pure status updates about something the customer is already expecting. Keep them factual and they sail through.

Loyalty programs & re-engagement

Loyalty perks, "we miss you" texts, and seasonal offers are Marketing, even when they go to past customers. This is the bucket people most often mis-file as "customer care" because the recipients are existing clients. If there's an offer in it, it's marketing — register it that way and include a clear opt-out.

Cross-sell & upsell

"Since you booked X, you might want Y" is promotional. Treat it as Marketing or fold it into a Mixed campaign alongside your service messages.

The 2026 rejection codes — and how to dodge them

Carrier vetting got stricter, and as of March 2026 the rejection reasons come with granular codes and "required fixes." These five cover the vast majority of rejections we see:

• 30886 — Campaign description doesn't match the use case. Your description is vague or describes different messages than the ones you'll send. Fix: spell out exactly what you'll send, to whom, and how often, in plain language. Don't copy example text — paraphrased boilerplate gets flagged.
• 30907 — Website URL issue. Your site is down, "under construction," or doesn't match the brand. Fix: have a live, working website that clearly belongs to the registering business before you submit.
• 30908 — No compliant privacy policy. Carriers couldn't find an accessible privacy policy. Fix: publish one on your site and link directly to it. It should state how you handle phone numbers and that you don't sell data.
• 30909 — Call-to-action / opt-in problem. They can't see how people consent to be texted. Fix: show the opt-in — a form with a clear consent checkbox and language like "Reply YES to confirm. Msg & data rates may apply. Reply STOP to opt out."
• 30903 — Wrong brand type. A business with an EIN registered as a Sole Proprietor. Fix: if you have an EIN, register as a Standard Brand; the Sole Proprietor path is only for individuals without one.

The first-try approval checklist

Before you submit a campaign, line these up. Doing so is the difference between approval in days and a rejection-resubmit loop that drags on for weeks:

1. Pick the honest use case for what you'll actually send (use the map above).
2. Write a specific description — what messages, to whom, how often — in your own words.
3. Live website that matches the business name, no broken links, no "coming soon."
4. Accessible privacy policy linked on the site, covering SMS data.
5. Visible opt-in with consent language and a clear STOP-to-opt-out.
6. Two sample messages — one promotional, one transactional — that reflect your real texts.
7. Correct brand type — Standard Brand if you have an EIN, Sole Proprietor only if you don't.

The bottom line

You don't get to opt out of A2P 10DLC just because your texts are helpful. But you also don't need to overthink it. Register the use case that honestly matches your messages, get your website, privacy policy, and opt-in in order, and pick the right brand type. Do that and most service businesses get approved without drama — and every reminder, follow-up, and update you send afterward actually reaches the phone it was meant for.