Skip to main content

Campaign registration: Setting up your use case in Aloware

Register your Aloware lines for A2P 10DLC compliance. Choose a use case, fill out the form, and get approved to send business SMS.

Written by Laarni D

If you haven't completed brand registration yet, start there first. This guide covers Step 3, which only works after Steps 1 and 2 are done, click here.

What this step is and why it matters

When you send business text messages in the U.S., phone carriers need to know who you are and what kind of messages you're sending. This is called A2P 10DLC compliance (Application-to-Person, 10-Digit Long Code). Without it, your messages may be blocked, delayed, or filtered as spam.

Registration does two things:

  1. It tells carriers your messages are legitimate, which helps them get delivered.

  2. It determines how many messages you're allowed to send per day (your "throughput").

The use case you select describes the kind of messages you'll be sending, such as customer support replies versus marketing promotions. This is the most important choice you'll make in this step, because it's tied directly to your brand approval and your sending limits.

Each use case allows up to 50 campaigns, but it's usually best to use as few as possible and group your lines together. This makes campaigns easier to manage and helps keep fees lower.


Recommended way to group your lines

Before you click anything, plan how you'll group your lines. Two common groupings cover most businesses:

  • Customer care campaign - your agent lines used for inbound and outbound calls and texts, including personal lines and inbound support lines.

  • Marketing campaign - any line that sends promotional SMS, including lines used for Bulk SMS broadcasts.

If a line does both, you'll typically place it under a Mixed campaign (explained below).


Two ways to register: Quick setup vs. Advanced setup

Aloware gives you two paths depending on what your messages are for.

Use Quick setup if your messages fall under Customer Care, Marketing, or Mixed. Most businesses use one of these three.

Use Advanced setup if your messages fall under a more specialized category, such as two-factor authentication codes, delivery notifications, fraud alerts, or messages from a school or university. The full list is further down this guide.


Quick setup: The three common use cases

  1. Click Quick Setup to start. You'll be asked to choose a use case. Here's what each one means and when to pick it.

    1. Customer Care

      Pick this if you're using SMS to talk with customers, such as answering questions, following up on accounts, handling support issues, or sending appointment reminders.

      Example message: "Hi Sam, this is a reminder of your appointment with Dr. Lee tomorrow at 2:00 PM. Reply C to confirm or R to reschedule. Reply STOP to opt out."

    2. Marketing

      Pick this if you're sending promotional content, such as sales, discounts, new product announcements, or limited-time offers.

      Example message: "Hi Sam, our spring sale starts today! Get 20% off select items through Sunday. Shop now: [link]. Reply STOP to opt out."

    3. Mixed

      Pick this if a single campaign will be used for more than one purpose, like both customer care and marketing, or customer care and delivery updates.

      A few things to know before choosing Mixed:

      • Daily sending limit is lower (typically under 2,000 messages per day).

      • Cost per message is higher.

      • Approval can be slower because carriers scrutinize Mixed campaigns more closely.

If you can split your messages into a dedicated Customer Care campaign and a dedicated Marketing campaign instead, that's usually the better choice.

Example Mixed message: "Hi Sam, your meal kit is on the way and will arrive by 6 PM today. Need help? Just reply here. Reply STOP to opt out."


Advanced setup: Specialized use cases

If none of the three above fit, click Advanced Setup. You'll see additional options:

Use Case

Description

2FA

Any authentication or account verification such as OTP.

Account notifications

Notifications about the status of an account or related to being a part of an account.

Delivery notifications

Information about the status of a delivery.

Fraud alert messaging

Messaging about potentially fraudulent activity, such as spending alerts.

Low volume mixed

Low-volume standard Brands can be used for mixed messaging campaigns with multiple use cases and multiple numbers per campaign. Low volume is generally defined as less than 2,000 SMS/MMS per day with low throughput requirements.

Higher education

Message campaigns from colleges, universities, and other educational institutions.

Polling and voting

For conducting polling and voting, such as customer surveys. Not for political use.

Public service announcement

PSAs raise audience awareness about a given topic.

Security alert

Notification of a compromised system (software or hardware related).

By default, Aloware will include all your unregistered lines, but you can select specific lines for your campaign.


Filling out the registration form

Once you've picked a use case, you'll be taken to the campaign details form. By default, Aloware adds all your unregistered lines to this campaign. You can leave it that way or pick specific lines manually.

Here's what each field is asking for and how to fill it in.

Campaign description

Describe what this campaign is for in one or two sentences. Focus on what you do for your customers, not on selling them.

Example for Customer Care: "Provide assistance to our current customers, mainly conversational communication."

Example for Marketing: "Send seasonal offers and product announcements to subscribers who opted in through our website."

How Do End-Users Consent to Receive Messages?

This is one of the most important fields. Carriers want proof that the people you're texting actually agreed to be texted. You need to explain every way someone can opt in to your messages.

This explanation must be between 40 and 2,048 characters. List each opt-in method, even if you have several.

Example: "Customers opt in by checking a consent box during checkout on our website, by texting JOIN to our number, or by signing a paper form at our retail location. The consent language clearly states that they agree to receive transactional and promotional SMS from [your company]."

Message sample #1 and message sample #2

You need to provide two real-looking sample messages that match the use case. These show carriers what kind of content you'll actually send.

Important: Both samples must include opt-out language, like "Reply STOP to opt out." Leaving this out is one of the most common reasons campaigns get rejected.

You can click the refresh button to have Aloware pull random examples from your actual outbound SMS history, then edit them.

Sample 1 example: "Hi [lead name], this is [rep name] from [your company]. Following up on your inquiry about our service. Let me know if you have any questions. Reply STOP to opt out."

Sample 2 example: "Hi [lead name], thanks for reaching out to [your company]. Your account has been updated as requested. Reply STOP to opt out."

You will also be asked for:

  1. Link to privacy policy

  2. Link to terms and conditions

Message contents

Tell the carrier whether your messages will contain links or phone numbers. Be honest here. If you say no and then send links, your campaign can be flagged later.

Message restrictions

Confirm whether your messages contain certain regulated content. Be honest here. Misrepresenting your content is a fast way to get a campaign suspended.

  • Direct lending or loan arrangement content. Some lending content is allowed, but high-risk loans, indirect loans, and debt collection are prohibited under A2P 10DLC guidelines.

  • Age-gated content. Anything related to Sex, Hate, Alcohol, Firearms, or Tobacco (collectively known as SHAFT), as well as cannabis, is prohibited.


Compliance rules to keep in mind

These rules apply to every message you send, not just during registration. They affect whether your campaign gets approved and stays in good standing.

Sender identifier

Every initial message, and any follow-up that isn't part of an active conversation, must clearly say who you are. Include your name and your company name.

The only exception is when you're already in a back-and-forth with the recipient. You don't need to identify yourself in every reply during a live conversation.

Opt-out Language

Every initial message must include a clear way to unsubscribe, such as "Reply STOP to opt out." This isn't optional. It's a regulatory requirement.

For ongoing conversations, you must include the opt-out reminder again at least every 30 days when starting a new initial message thread. This makes sure recipients can leave at any point, even if they engaged with you previously.

One-Time Campaign Fee

Each use case has a one-time fee that covers carrier processing costs. This is separate from your Aloware subscription. For a full breakdown, see A2P 10DLC fees: Brand and campaign costs.

Terms and Conditions

You'll need to agree to the Terms and Conditions before submitting. Read these carefully so you understand your responsibilities as a sender.


Submitting and what happens next

Click Finish to submit your campaign for review.

That's it for your part. Approval typically takes a few business days, though it can be longer for Mixed and Advanced use cases.

A note on rejections: If your campaign is rejected or comes back with a brand score of 0, your billing admin will receive an email notification. The most common reasons for rejection are missing opt-out language in the samples, vague campaign descriptions, or an opt-in explanation that doesn't clearly show consent.

After approval

Once your campaign is approved, the next step is to add your phone lines to it so they can start sending under the registered use case.


A helpful default in Aloware

When you send messages through Aloware Sequences or Broadcast, an opt-out instruction is appended to your messages automatically. You don't need to type it in manually each time.

This helps you stay compliant without extra work, but it doesn't replace the need to include opt-out language in your registration sample messages.

Did this answer your question?