Skip to main content
A2P 10DLC (Application-to-Person 10-digit long code) is a US carrier regulation that requires businesses to register before sending bulk SMS messages from 10-digit local phone numbers. Without registration, your text messages may be blocked, heavily filtered, or rejected by carriers — preventing them from reaching your contacts at all. If you plan to send any automated or bulk SMS in the United States, completing A2P 10DLC registration is mandatory.
Do not skip this step. Unregistered SMS traffic is increasingly filtered by all major US carriers (AT&T, Verizon, T-Mobile). Even one-off automated texts (such as appointment reminders or follow-up sequences) require registration.

​
What A2P 10DLC covers

A2P 10DLC registration applies specifically to 10-digit local numbers (numbers that start with an area code). It does not apply to:
  • Toll-free numbers (TFNs) — toll-free numbers have a separate registration process called Toll-Free Verification
  • Short codes — 5 or 6-digit numbers used for high-volume messaging have their own provisioning process
If you are using a local number for SMS, you need A2P 10DLC registration.

​
What you will need before starting

Gather the following before beginning the registration form:
  • Legal business name — exactly as it appears on your EIN/tax documents
  • EIN (Employer Identification Number) — the US tax identification number for your business. Sole proprietors without an EIN may need to register as a sole proprietor or use their SSN in some cases.
  • Business address — physical address, not a PO box
  • Business type — sole proprietor, LLC, corporation, etc.
  • Business website URL — carriers require a public website where your opt-in method is documented (see below)
  • Opt-in method description — how your contacts give you consent to receive SMS (e.g., “Customers fill out a web form that includes an SMS consent checkbox”)
  • Sample messages — 2–3 example messages representing the types of SMS you will send
  • Use case description — a plain-language summary of why you are sending SMS and to whom

​
The registration process

A2P 10DLC registration in HoopAI involves two distinct steps: registering your Brand (your business identity) and then registering a Campaign (your specific use case for sending SMS).

​
Step 1 — Register your brand

1

Open the Trust Center

In HoopAI, go to Settings > Trust Center (sometimes listed as Settings > Phone > A2P Registration or Settings > Compliance).
2

Start brand registration

Click Register Brand or Start A2P Registration. Select your business type from the options provided.
3

Enter your business details

Fill in your legal business name, EIN, business address, industry, and contact information. All information must match your IRS records exactly for your EIN.
4

Submit brand registration

Click Submit. Your brand registration is sent to The Campaign Registry (TCR), the central registration authority for A2P 10DLC. Brand approval typically takes 1–2 business days.
There is a one-time Brand Registration fee charged by the carrier ecosystem (passed through from TCR). This is a standard industry fee and is not a HoopAI charge.

​
Step 2 — Register your campaign

Once your brand is approved, you can register a campaign that defines your SMS use case.
1

Create a new campaign

In the Trust Center, under your approved brand, click Add Campaign or Register Campaign.
2

Select your use case

Choose the category that best describes your SMS use case. Common options include:
  • Marketing — promotional messages, offers, and announcements
  • Notifications/Alerts — appointment reminders, order updates, account alerts
  • Customer Care — support responses and two-way conversational messaging
  • Mixed — accounts that send more than one type of message
  • 2FA / OTP — one-time passcodes for authentication
Do not select a use case that does not accurately describe your messaging. Carriers audit campaigns and misrepresentation can result in suspension.
3

Describe your campaign

Write a clear description of:
  • What you send — the type of content in your messages
  • Who you send to — who your recipients are and how they opted in
  • Sample messages — paste 2–3 representative examples of the actual messages you send
4

Document your opt-in method

Describe precisely how recipients give consent to receive SMS. Examples:
  • “Contacts fill out a web form at [URL] that includes a checkbox: ‘I agree to receive SMS messages from [Business Name].’ The checkbox is unchecked by default.”
  • “Customers text the keyword JOIN to [phone number] to opt in.”
  • “Verbal opt-in collected during a phone call, logged in the CRM.”
Your website must have a visible privacy policy and SMS terms that match your described opt-in method.
5

Link your phone numbers

Select which of your phone numbers to attach to this campaign. Each number must be linked to an approved campaign before it can send compliant A2P SMS.
6

Submit campaign registration

Click Submit. Campaign review typically takes 3–7 business days.

​
After registration is approved

Once your brand and campaign are approved:
  • The status in the Trust Center changes to Approved or Active
  • Your linked phone numbers are cleared to send compliant A2P SMS
  • You can begin sending bulk and automated SMS through workflows, campaigns, and the conversations inbox
Set up your A2P registration during the same week you configure your phone number. The 3–7 day approval window means you want to start it early so you are not waiting when you are ready to launch automations.

​
Common rejection reasons

If your brand or campaign registration is rejected, the most common causes are:
  • EIN mismatch — the business name does not exactly match IRS records for that EIN
  • Missing or inadequate website — carriers require a public website with a visible privacy policy and SMS opt-in terms
  • Vague opt-in description — “We get permission” is not sufficient; describe the exact mechanism
  • Prohibited content — certain industries are restricted from A2P 10DLC (e.g., cannabis, firearms, certain financial products). Review carrier content policies if you operate in a regulated industry.
  • Sample messages don’t match the use case — if you select “Notifications” but your samples are promotional, you will be rejected

​
Toll-free number verification (alternative)

If you use a toll-free number (800, 888, 877, 866, etc.) instead of a local number, you do not need A2P 10DLC registration. Instead, you need Toll-Free Verification, which is a separate process with its own form and timeline. Toll-free numbers tend to have higher throughput limits and simpler verification requirements than local numbers, making them a good choice for high-volume senders. Go to Settings > Trust Center > Toll-Free Verification to begin that process.

​
Frequently asked questions

In limited volumes, some one-off conversational messages (replies to inbound texts) may still be delivered during the review period. However, bulk automated sequences should not be sent until registration is approved, as unregistered traffic is subject to filtering and suspension.
No. One approved campaign can cover all SMS sent from the linked phone numbers for that use case category. You only need additional campaigns if you have genuinely different use cases (e.g., one campaign for marketing and a separate one for 2FA/OTP).
Yes. In addition to the one-time brand registration fee, there is a recurring monthly campaign fee charged by the carrier ecosystem. This is passed through as a platform charge. Check your plan for current fee amounts.
A2P 10DLC is a US-only requirement. Canadian SMS regulations differ and are managed separately. If you are sending SMS to Canadian numbers, different carrier requirements apply — contact HoopAI support for guidance on Canadian SMS compliance.
HoopAI provides the Trust Center interface and submits your registration to the carrier ecosystem (TCR) on your behalf. However, you must supply accurate business information and ensure your website and opt-in practices meet carrier requirements — HoopAI cannot correct inaccurate information after submission.
Last modified on March 5, 2026