01Who this is for
- Founders of SaaS companies, need to classify authentication and billing alerts to meet carrier rules.
- Small retailers, must label promotional texts correctly to stay compliant and keep delivery rates high.
- Non profit organizers, require the charity use case and related documentation for fundraising alerts.
02A2P 10DLC campaign use cases, explained
The use case is a required selection when you register an A2P 10DLC campaign in HighLevel. It describes the main type of messages you will send, such as two factor authentication, account notifications, marketing, or public service announcements. Carriers read this value to set throughput caps, apply spam filters and decide whether to approve the registration. HighLevel classifies use cases as Standard, Special (charity, emergency, political) or Low Volume Mixed, each with its own documentation or throughput rules. Restricted or forbidden categories, like gambling or adult content, are not allowed regardless of the chosen use case.
03How businesses use A2P 10DLC campaign use cases
- SaaS platform. Select the 2FA use case when registering a campaign that delivers login codes and password reset pins. Provide sample authentication messages and an opt in flow that shows no marketing content. The platform then sends verification texts through the registered 10DLC number.
- Ecommerce store. Choose the Marketing use case for promotional offers, product launches and abandoned cart reminders. Upload consent records and sample promotional messages, then use HighLevel’s SMS builder to send campaigns to the approved number pool.
- Community nonprofit. Pick the Charity special use case and attach tax exempt documentation during registration. After approval, the organization can send donation appeals and event notices while staying within the allowed content rules.
04The numbers and rules that matter
- 2FA messages must not include marketing content or promotional language.
05How to set up and use A2P 10DLC campaign use cases in HighLevel
Select the correct campaign use case before registration
- Identify the primary purpose of the messages you will send.
- Match that purpose to one of the standard, special or low volume use cases listed by HighLevel.
- Confirm that your sample messages, opt in flow and website content reflect the chosen use case.
- Do not select Mixed simply because you are unsure which use case applies; choose the most accurate single purpose.
- Submit the campaign registration in HighLevel with the selected use case.
06Settings that matter
- Campaign use case. Specifies the main messaging purpose for the registered 10DLC number, influencing carrier approval, throughput limits and filtering rules.
07Things to know before you rely on it
- Special use cases need additional verification documents before the campaign can be approved.
- Low Volume Mixed is limited to the lowest throughput tier regardless of Brand Trust Score.
- Mixed use cases cannot be edited after approval without a modification request to The Campaign Registry.
- Choosing a use case that does not match actual traffic can cause rejection, reduced throughput, or suspension.
08If something goes wrong
- Campaign rejected because the declared use case does not match sent messages. Review the message content, opt in flow and website to ensure they align with the selected use case, then resubmit with the correct classification.
09How it connects to the rest of HighLevel
- Step by step campaign registration guide A2P campaign registration
- Best practices for getting a campaign approved Campaign approval best practices
- Current list of prohibited message categories Forbidden categories
Michael's take

Skipping the step of matching your real messaging to the declared use case can land you in compliance trouble and hurt deliverability.
Carriers take the use case seriously; a mismatch can trigger rejection or reduced throughput.
When you pick the right category, the system works with carriers to apply the appropriate filtering and throughput limits.