
If your healthcare app texts patients in the US from a regular 10-digit phone number, you need A2P 10DLC registration. Carriers expect every business sending automated texts over standard long codes to register its brand and its use case first. Skip it, and your appointment reminders get blocked: Twilio, for one, stops US-bound texts from unregistered 10DLC numbers outright.
Registration takes three steps with your SMS provider: a business profile, a brand, and a campaign. Twilio's posted review times add up to at least one to three weeks, depending on whether your brand goes to manual review, and longer if your tax ID is new or a reviewer sends something back. The campaign is where healthcare teams need the most care: every sample text you submit has to satisfy the reviewer and stay free of protected health information (PHI).
A2P means application-to-person: texts your software sends, like reminders, alerts, and verification codes. 10DLC means 10-digit long code, the same kind of local number a person uses. A2P 10DLC is the carrier standard for that traffic, and registration is how carriers learn who's sending and why.
Twilio puts the rule plainly: "Anyone sending SMS/MMS messages over a 10DLC number from an application to the US must register for A2P 10DLC" (Twilio). It doesn't matter how small your volume is or whether the texts are purely transactional. A clinic sending 40 reminders a day needs it as much as a telehealth platform sending 40,000.
Registration also helps you. Twilio says registered senders get "lower message filtering and higher messaging throughput" than unregistered ones.
Unregistered texts don't fail loudly. Your app calls the API, the send is accepted, and the message then fails with error 30034 instead of reaching the patient.
On Twilio, the failure shows up as error 30034: "Twilio blocks messages to U.S. numbers when you send from a +1 10DLC number that is not associated with an approved A2P 10DLC Campaign." This isn't new. Twilio started a gradual increase in blocking on July 5, 2023, and moved to a "full block of all unregistered U.S.-bound messages sent after August 31, 2023" (Twilio changelog).
For a healthcare sender, that means a missed-appointment problem you can't see from your send logs. If you're seeing 30034 in delivery status callbacks, registration is the fix, not a retry.
Registration has three parts, and on Twilio you complete them in order. The Customer Profile is your business identity with the provider. The brand is the company carriers check, so they can "verify who is sending." The campaign covers what you're texting and how people opt in, opt out, and get help.
| Step | What you provide | Twilio's review time |
|---|---|---|
| Customer Profile | Business details, address, authorized representative | 72 hours or more |
| Brand | EIN, legal business name, business type, website | Seven business days or more for manual review |
| Campaign | Use case, description, opt-in flow, sample messages | Up to 5 business days for standard use cases |
Review times come from Twilio's direct standard onboarding guide. Other providers run the same registration with their own console and timing.
The brand step is where tax paperwork bites. Twilio asks for the "exact legal business name as registered with the EIN," which is the name on your IRS CP 575 confirmation letter, not a trade name or the name on a W-9 (Twilio). A health system that operates as "Northside Health" but is registered as "Northside Regional Medical Group LLC" uses the second one.
If your EIN is new, budget for it. Twilio notes that a new tax ID can take 30 to 90 days to validate, so a practice that incorporated last month may hit a mismatch even with every field correct.
Your website matters here too. Twilio's guidance says it has to work and relate to the business name. A parked domain, a login wall, or a redirect to another brand gets turned down.
There's no dedicated healthcare use case to pick. Healthcare texts like appointment reminders typically fit standard use cases such as account notifications or customer care. Check the current use case list in your provider's console and choose the one that matches what you actually send.
Fees vary by provider and campaign, so check your provider's pricing page before you budget.
The campaign is the part a human reviewer reads, and it's where most of the back-and-forth happens. Reviewers want to see three things: who's sending, how people agreed to it, and what the texts will look like.
The opt-in description (Twilio calls it the message flow) explains every way someone signs up. Be specific: where the form is and exactly what the consent language says. If the opt-in happens on a website, Twilio expects that site to have a privacy policy and terms of service.
Twilio's guidance on consent language lists what it should cover: your brand name, the type of messages, how often they come, "Message and data rates may apply," "Reply STOP to unsubscribe," and "Reply HELP for help." Here's an opt-in description for a clinic:
Patients opt in on the online booking form at northsidehealth.example/book by checking an optional box labeled: "Text me appointment reminders from Northside Health. Up to 3 msgs/week. Message and data rates may apply. Reply HELP for help. Reply STOP to unsubscribe." Checking the box is not required to book. Privacy policy and terms are linked below the box.Twilio asks for two to five sample messages that identify your brand and match the campaign. For healthcare, write them the way you'll actually send them: date, time, and a way to act, with no diagnosis, specialty, test name, or result. Keep conditions out of the samples for the same reason you keep them out of production: texts land on lock screens and shared phones.
The opt-in confirmation is the first text a patient gets, so it carries the full disclosure:
Northside Health: you're signed up for appointment reminders. Up to 3 msgs/week. Message and data rates may apply. Reply HELP for help, STOP to unsubscribe.A reminder names the practice, gives the time, and offers a way to change it:
Northside Health: your appointment is Tue, Mar 3 at 9:30 AM. To reschedule, call 312-555-0142. Reply STOP to unsubscribe.A results nudge says something is ready and sends the patient to sign in:
Northside Health: you have a new message in your patient portal. Sign in to view it at northsidehealth.example. Reply STOP to unsubscribe.Every sample above fits in a single 160-character GSM-7 segment. Check your own templates with real values in the SMS segment counter, and see appointment reminder templates for a full set.
Your campaign covers opt-out and HELP handling too. Twilio can handle the keywords for you with its default or Advanced Opt-out features. If you handle them yourself, you submit your own responses. Either way, keep them short:
Northside Health appointment texts. For help, call 312-555-0142. Up to 3 msgs/week. Message and data rates may apply. Reply STOP to unsubscribe.Northside Health: you're unsubscribed and won't get more appointment texts. For help, call 312-555-0142.A2P 10DLC is the carriers' gate. The Telephone Consumer Protection Act (TCPA) is a separate, legal one. The TCPA has a healthcare exemption for texts like appointment reminders, but it comes with strict limits: 160 characters or fewer, no more than one text a day and three a week, no billing or marketing content, and free to the patient. Most teams collect consent anyway. The details are in is texting patients a HIPAA violation? and TCPA SMS rules for 2026.
The opt-out rules change too. Under FCC 26-67, effective November 25, 2026, you can make a keyword like STOP the exclusive way to opt out, as long as you disclose it clearly, and you have ten business days at most to honor a request. Your campaign's opt-out wording and your TCPA disclosures should say the same thing.
Twilio names a few causes that come up again and again (Twilio):
The fix for all three is the same: make what the reviewer sees match what a patient sees. If you resubmit, change the specific thing that failed rather than rewording the whole campaign.
10DLC isn't the only way to text in the US. Toll-free numbers and short codes have their own registration, and both are worth a look if 10DLC review is holding up a launch.
| Sender | Registration | Time to approval (Twilio) |
|---|---|---|
| 10DLC (local number) | A2P 10DLC: profile, brand, and campaign | At least one to three weeks across the three steps |
| Toll-free number | Toll-free verification | Twilio reviews within three business days |
| Short code | Short code application to the carriers | About 4 to 8 weeks from payment to approval |
Toll-free verification isn't optional either. Per Twilio, you can't send messages from an unverified toll-free number. Short codes take the longest to set up (Twilio short code guidelines), so they make sense when you've planned for the wait. A local 10DLC number has one advantage for a clinic: patients see a familiar area code.
A solo practitioner without an EIN can register as a sole proprietor brand, but the limits are tight. You get one campaign per brand and 1,000 SMS segments per day to T-Mobile (Twilio). If your practice has an EIN, Twilio says you must not register as a sole proprietor. Use a standard brand instead.
Courier sends through the SMS provider you connect, like Twilio. Registration happens with that provider: your brand, your campaign, and your numbers live in your provider account, and approved numbers work the same whether your app calls Twilio directly or sends through Courier.
What Courier adds is the layer around the send. Templates live in one place per notification type, so the PHI-free review you did for your campaign samples holds for every service that triggers a reminder. Preferences let a patient opt out of a category, like appointment reminders, across SMS, email, push, and the in-app inbox, and Courier checks those preferences before each send. Routing lets a reminder fall back to email or push when a patient has no mobile number on file.
Courier maintains a HIPAA compliance program and signs BAAs with Enterprise customers. See HIPAA compliance and BAAs for the details. On the provider side, Twilio signs a BAA on its Security and Enterprise Editions that covers Programmable SMS (is Twilio HIPAA compliant?). Either way, keep PHI out of the text itself.
A2P 10DLC registration is paperwork, but it decides whether your texts arrive. Before you submit:
For how Courier supports healthcare teams, see Courier for healthcare.
A2P 10DLC is the US carrier standard for application-to-person texts sent from standard 10-digit phone numbers. Businesses register a brand and a campaign so carriers know who's sending and why. Registered traffic gets lower filtering and higher throughput, and unregistered traffic gets blocked.
Appointment reminders need 10DLC registration if your app sends them to US numbers from a 10-digit long code. Registration applies to any SMS or MMS an application sends over 10DLC, including transactional texts. If you send from a toll-free number instead, you need toll-free verification.
10DLC registration takes at least one to three weeks on Twilio, based on its posted minimum review times. The Customer Profile takes 72 hours or more, a manually reviewed brand takes seven business days or more, and a standard campaign takes up to 5 business days. A new EIN can add 30 to 90 days before it validates.
10DLC campaigns are most often rejected for an incomplete or missing opt-in description. A business website that reviewers can't validate, or one that's still under development, also leads to rejection. Fix the specific issue and resubmit.
Unregistered SMS from a US 10DLC number gets blocked. On Twilio, the message fails with error 30034, and Twilio has blocked all unregistered US-bound 10DLC traffic sent after August 31, 2023.
Toll-free verification is an alternative if you send from a toll-free number instead of a local one. It's still a registration: Twilio won't send from an unverified toll-free number, and it reviews verification requests within three business days.

Is Twilio HIPAA compliant? BAAs for your whole stack
Twilio signs a BAA on its Security and Enterprise Editions, for products on its HIPAA-eligible list. What that list covers, what it leaves out (SendGrid, WhatsApp, Notify), and which other notification vendors sign BAAs.

Appointment reminder templates for text and email
35 copy-ready appointment reminder templates for text and email, from booking confirmations to no-show follow-ups, with sets for primary care, dental, behavioral health, and more. Every text fits one SMS segment, includes opt-out wording, and keeps clinical details out.

HIPAA-compliant email: what patient notifications need
HIPAA allows email with patients. What makes it compliant is what's in the message. Which email APIs sign a BAA, why TLS isn't the whole answer, where PHI leaks in an email stack, and how to keep notification email PHI-free.