A2P Campaign Use Cases Explained: Which One Should You Pick? (2026)

The right A2P campaign use case is the one that matches what you actually send — Customer Care, Account Notifications, Mixed, or Marketing. Picking the wrong use case at Campaign registration is one of the more common — and more consequential — A2P 10DLC mistakes, since it can cause an immediate rejection or, worse, approval followed by scrutiny once your real traffic doesn’t match what you registered. This guide breaks down every common use case, what it actually covers, and how to pick correctly for your business.

Most guides on A2P 10DLC treat use case selection as a quick dropdown decision buried in the middle of the registration form. It deserves more attention than that — it’s the single field that most directly determines both your initial approval odds and how much scrutiny your campaign faces on an ongoing basis after approval, which makes it worth genuinely understanding rather than guessing at.

What are the main A2P 10DLC campaign use cases?

The main A2P 10DLC campaign use cases are Customer Care, Account Notifications, Mixed, and Marketing, plus Low-Volume Mixed for Low-Volume Standard brands.

Customer Care

This covers support-oriented, service-oriented messaging — responding to inquiries, providing account or service updates, and general two-way conversational texting tied to an existing customer relationship. It’s one of the lowest-scrutiny categories because it’s tied directly to an existing relationship rather than outbound acquisition or promotion.

Good fit for: businesses whose SMS is primarily reactive/conversational — answering questions, confirming details, following up on an existing job or booking.

Account Notifications

Covers transactional, expected messaging tied to a specific account or transaction: appointment reminders, order confirmations, service status updates, billing reminders. This is generally viewed favorably by carriers, since recipients have an obvious, direct reason to expect the message.

Good fit for: service businesses running automated appointment reminder sequences and workflows, e-commerce order/shipping updates, or similar transactional workflows.

Mixed

Covers a genuine blend of transactional/customer-care content and occasional promotional messaging under one registered campaign. This is the most commonly appropriate use case for small service businesses whose SMS mostly consists of appointment reminders and follow-ups, with occasional promotional content (a seasonal offer, a referral request) mixed in.

Good fit for: the majority of single-location service businesses — plumbers, salons, dental practices, contractors — whose messaging isn’t purely one type or the other.

Marketing

For campaigns that are primarily or exclusively promotional — sales announcements, discount offers, event promotions. This category carries the highest carrier scrutiny and typically the highest monthly campaign fee, reflecting its historical association with higher-volume, higher-complaint-risk sending.

Good fit for: businesses whose SMS program is genuinely marketing-first — e-commerce promotional campaigns, event-driven announcement sequences, businesses running dedicated promotional SMS lists (such as GoHighLevel database reactivation campaigns) distinct from their transactional messaging.

How use cases work differently on the Chat Widget (Pre-Built) registration path

Everything above describes the traditional Manual Setup flow, where you can select from the full range of use cases (Customer Care, Account Notifications, Mixed, Marketing) and write your own sample messages. GoHighLevel’s newer Chat Widget (Pre-Built) registration path — now the default flow presented after Brand approval — works differently and deliberately simplifies this decision down to three message types, then sets the registered use case for you:

The system also runs a conflict blocker that prevents registering Marketing content alongside financial-services content in the same widget-based campaign, and auto-enforces a mandatory Date of Birth field whenever your questionnaire answers indicate age-gated or financial content — neither of which you have to configure manually; both trigger automatically based on how you answer the setup questionnaire. Our step-by-step GoHighLevel registration guide covers the full widget-path setup flow and the main A2P 10DLC guide covers the approval-speed trade-off in more depth.

Manual Setup — common categories 4

Specialized TCR categories (2FA, Delivery, Political, Charity) 4

Chat Widget (Pre-Built) path message types 3

Number of use case options covered in this guide, by category group

Item	Value
Manual Setup — common categories	4
Specialized TCR categories (2FA, Delivery, Political, Charity)	4
Chat Widget (Pre-Built) path message types	3

How do you choose the right A2P campaign use case?

Choose the right A2P campaign use case by asking whether most of your SMS is tied to an existing transaction or relationship, and whether you regularly send both transactional and promotional content.

Rather than treating this as an abstract classification exercise, ask two concrete questions about your real, planned messaging:

Question 1: Is the majority of your SMS content tied to an existing transaction or relationship (appointment, order, service call), or is it primarily aimed at driving a new purchase or booking? If the former, Customer Care or Account Notifications; if the latter, Marketing.

Question 2: Do you send both types regularly, or is one type rare/occasional? If you send a genuine, regular mix of both, Mixed is the more accurate registration than trying to force everything into one narrow category and hoping the occasional off-category message doesn’t cause problems.

What happens if you pick the wrong A2P use case?

If your registered A2P use case doesn’t match what you actually send, you risk an immediate rejection or, after approval, renewed scrutiny, throttling, or even suspension of the campaign.

This is worth taking seriously, since it’s a common source of trouble that shows up after approval rather than at registration (if yours was rejected outright, our A2P rejection reasons and exact fixes guide walks through the fix). A campaign registered as “Customer Care” that starts consistently sending promotional blasts creates a growing mismatch between what carriers approved and what’s actually being sent — this can trigger renewed scrutiny, throttling, or in more serious cases, suspension of a previously approved campaign, even though nothing about the individual messages themselves might be non-compliant in isolation.

The practical fix, if your business’s messaging needs have genuinely evolved since you first registered, is to register an additional, correctly-scoped campaign for the new content type rather than letting an existing campaign’s real traffic drift from what it was approved for.

Registering multiple campaigns for genuinely distinct use cases

For Standard brands (not Sole Proprietor, which is limited to one campaign), registering more than one campaign is often the right structural answer when a business genuinely runs two very different kinds of SMS programs rather than trying to force both under one label. A multi-location retail chain, for example, might run one campaign for order/shipping transactional updates (Account Notifications) and a separate campaign for its email-list-style promotional SMS program (Marketing) — each accurately described, each reviewed on its own terms, and each able to scale or adjust independently of the other.

The trade-off is straightforward: each additional campaign carries its own one-time vetting fee and its own recurring monthly fee, so this only makes sense once your actual traffic volume in each category justifies the administrative and cost overhead of managing separate campaigns, rather than as a default starting structure for every business.

Use cases and Sole Proprietor registration

Sole Proprietor brands are limited to a single campaign, which makes the content decision even more consequential — you don’t have the option of registering a second, narrower campaign for a distinct content type the way a Standard brand does. Sole Proprietor campaigns are registered under a dedicated Sole Proprietor use case, so the practical job is making sure that one campaign’s description and sample messages honestly cover the realistic blend of transactional and occasional promotional content a single-person operation tends to send, without forcing an artificially narrow description that doesn’t match real behavior. Our Sole Proprietor registration guide covers the full registration process for this brand type.

One more thing worth flagging explicitly for Sole Proprietors: the Chat Widget (Pre-Built) path covered above is available to you. GoHighLevel detects a Sole Proprietor account automatically, pre-selects the Sole Proprietor use case, and lets you pick the message type, including Mixed — as long as the chat widget can be your only SMS consent point. If it can’t, Manual Setup remains the route.

Industry-specific use case guidance

These are starting points based on typical patterns, not fixed rules — the correct use case for your specific business always depends on what you actually send, not what’s typical for your general industry category. If you’re in one of these industries and still building out the website your opt-in form will live on, see our home contractor website design and dental practice website design pages.

Other use case categories you may encounter

Beyond the four most common categories covered above, The Campaign Registry’s full taxonomy includes several more specific use cases worth knowing about if your business’s messaging falls into one of these narrower categories:

2FA / Account Verification — one-time passcodes and login verification codes. This is a distinct, narrowly scoped use case with its own registration path, generally treated favorably by carriers given its low spam-risk profile and clear consumer benefit.

Delivery Notifications — a narrower subset of Account Notifications specifically for shipping/delivery status, sometimes broken out separately by platforms handling significant e-commerce volume.

Political — campaigns run by or on behalf of political candidates or committees, subject to distinct regulatory requirements (including FCC/TCPA rules specific to political messaging) beyond standard A2P 10DLC review.

Charity — nonprofit fundraising and outreach messaging, which can qualify for reduced fees and different vetting treatment given 501(c)(3) status, following the government/nonprofit onboarding path covered in our Twilio registration guide.

Specialized A2P 10DLC use case categories in The Campaign Registry's taxonomy

Use case	What it covers	What to know
2FA / Account Verification	One-time passcodes and login verification codes	Narrowly scoped; generally treated favorably by carriers
Delivery Notifications	Shipping and delivery status updates	A narrower subset of Account Notifications
Political	Messaging by or for political candidates or committees	Subject to distinct FCC/TCPA political messaging rules
Charity	Nonprofit fundraising and outreach	Can qualify for reduced fees with 501(c)(3) status

Most GoHighLevel service businesses won’t need these more specialized categories, but it’s worth confirming your actual use case isn’t a closer match to one of these than to the four general categories, particularly for 2FA-style verification codes, which are sometimes miscategorized under Customer Care when a dedicated verification use case would be more accurate and often faces less scrutiny.

How carriers actually evaluate use case accuracy

It’s worth understanding the mechanism behind why use case accuracy matters, not just the rule itself. Carriers don’t just check your use case selection at initial registration and then stop monitoring — ongoing message content analysis (automated, at scale, across the network) continues to compare registered use case against actual traffic patterns for approved campaigns. This is part of why a campaign that was accurately registered at approval but drifts over time (new team member adds a marketing sequence to what was a purely transactional number, for example) can still run into trouble months later, even though nothing about the initial registration was inaccurate at the time.

This ongoing monitoring is also, in a sense, good news: it means a single, isolated off-category message is very unlikely to cause a problem on its own. It’s sustained, consistent drift — a meaningful and lasting shift in what a campaign actually sends relative to what it declared — that carriers’ systems are built to catch.

Worked examples across use cases

A dental practice (Account Notifications): “Hi [Name], this is a reminder for your cleaning appointment tomorrow at 2 PM with Dr. Smith’s office. Reply C to confirm or call to reschedule.” — clearly transactional, tied to an existing scheduled appointment.

A boutique retail store (Marketing): ”🎉 24-hour flash sale! 25% off everything in-store and online. Shop now: [link]. Reply STOP to unsubscribe.” — clearly promotional, not tied to an existing transaction.

A landscaping company (Mixed): Both “Hi [Name], your lawn service is scheduled for Thursday between 9-11 AM.” and, less frequently, “Fall cleanup special: book by [date] and save 15%. Reply STOP to opt out.” — a genuine blend under one accurately-described campaign.

A software company (Account Notifications / 2FA): “Your verification code is 482913. This code expires in 10 minutes.” — a narrowly scoped, low-risk verification message, ideally registered under a dedicated 2FA use case if your platform’s registration flow offers one distinctly from general Account Notifications.

Toll-free’s parallel but different use case system

If you’re using toll-free verification rather than A2P 10DLC (see our full comparison), the use case concept still applies conceptually — you’ll describe your messaging use case as part of toll-free verification too — but it’s evaluated under toll-free-specific review criteria rather than TCR’s A2P 10DLC categories directly. The same underlying principle holds regardless of which registration path you’re on: describe what you actually send, as specifically and accurately as possible, rather than picking whichever category sounds most permissive.

A note on how GoHighLevel presents these options

Inside GoHighLevel’s Trust Center, the use case dropdown generally mirrors The Campaign Registry’s standard category list directly, since GHL doesn’t create its own separate taxonomy — the categories and their definitions are set by TCR and apply identically whether you’re registering through GoHighLevel, directly in Twilio, or through any other platform built on the same underlying registry. This is worth knowing mainly so you don’t spend time looking for a “GoHighLevel-specific” explanation of a category that’s actually defined at the carrier/registry level and documented the same way across every platform that uses it.

Frequently asked follow-up questions

“My business genuinely does five different things — do I need five campaigns?” Not necessarily. The question isn’t how many distinct business activities you have, but how many distinct message content patterns you send via SMS. A business with five service lines that all generate similar appointment-reminder-style texts can often register one accurate campaign covering that shared pattern, rather than one campaign per service line.

“Can I register ‘Mixed’ just to be safe, even if my traffic is really just Marketing?” No — registering Mixed for what’s actually a Marketing-heavy campaign doesn’t provide meaningful protection, since carriers evaluate actual content against whatever was registered, not just the label chosen. Misclassifying toward a lower-scrutiny category to reduce fees or review intensity is more likely to cause a mismatch flag than to avoid one.

“Does my use case selection affect throughput/trust score independent of brand type?” Marketing-classified campaigns generally face somewhat more conservative default throughput treatment than Customer Care or Account Notifications, independent of your underlying brand’s trust score, reflecting the category’s inherently higher scrutiny profile.

Bringing it together

The use case you register isn’t a formality — it’s a declaration carriers hold your ongoing traffic against, both at initial review and afterward. Pick based on what you actually send, not the category that sounds least restrictive or most impressive, and choose Mixed rather than artificially forcing a blended traffic pattern into a single narrow category. Getting this right at registration avoids both an unnecessary rejection and the slower, more frustrating problem of post-approval scrutiny from a use case that no longer matches your real sending behavior.

If you’re still unsure which category fits after reading through the descriptions above, a reliable fallback exercise: write out the actual last five text messages your business sent (or plans to send), read them back as a set, and ask honestly what they have in common. The category that most naturally describes that real set of messages is almost always the right one to register — a far more reliable method than trying to reason abstractly about which label sounds best from the outside.