Automating Appointment Reminders: Before the First Text
The automation is an afternoon's work. What stops it is elsewhere: a 10DLC registration your business is not allowed to file itself, and an opt-out rule written in business days that most reminder builds put in the wrong place.
The automation part of an appointment reminder is the easy part. A trigger on the calendar, a delay, a message with two merge fields. An afternoon's work in any of the platforms we cover. Then it does not arrive, or it arrives for three weeks and then stops, and the reason is never in the automation tool. It is in two places outside that tool: a registration your business is not allowed to file itself, and a consent rule written in business days.
This article is about those two. The vendor pages and the regulation text below were read on November 4, 2026.
The number you send from decides the rules
A reminder sent from a normal ten-digit US phone number is application-to-person traffic, and the carriers treat it as a category of its own. Twilio's documentation puts the scope plainly: "Anyone sending SMS/MMS messages over a 10DLC number from an application to the US must register for A2P 10DLC." It also closes the obvious escape route, because the test is not whether a human pressed send: "Carriers consider all SMS traffic from Twilio to be sent from an application."
There are other kinds of number. The same page notes that "Toll-Free numbers and short code numbers aren't part of the A2P 10DLC system and can also be used for messaging end-users in the United States." That is a real fork in the road and it belongs at the start of the project, not after the first registration is rejected. It is also not a loophole: toll-free messaging has its own verification process, which this page does not describe and we have not read.
You cannot register yourself
This is the part that reorders a project plan. Registration happens through The Campaign Registry, and its own site says who may do it: "Currently, direct registration with TCR is not available for Brands. Instead, you must work with one of the registered messaging service providers (CSP) who will handle your registration process on your behalf."
So a dental practice does not file anything. It picks a messaging provider first, and the provider registers the Brand and the Campaign on its behalf. TCR describes the model as verification before sending: "10DLC is an A2P messaging channel in which Brands and Campaign Service Providers (CSPs) are verified prior to being allowed to send messages."
Choosing the messaging provider stops being a late, swappable decision. It is the step that unlocks registration, and registration is what the carriers check. Build the workflow second.
Two limits from the same Twilio page are worth knowing before anyone promises a send volume. A Sole Proprietor brand is capped at "1,000 SMS segments and MMS per day to T-Mobile", and registration is not open-ended: "Each Brand may register up to five Campaigns, unless a clear and valid business reason is provided". A clinic sending reminders, confirmations, and a separate review request is already spending three of those five.
What unregistered traffic actually costs, as the vendor describes it
Here the published text is narrower than the warnings around it, and the difference matters if you are deciding how urgent this is. Twilio's page describes two consequences, and neither of them is the word "blocked": "Registering for A2P 10DLC results in lower message filtering and higher messaging throughput", and "customers who send messages from a Twilio 10DLC number but do not register will receive additional carrier fees for sending unregistered traffic".
Read that as written. More filtering and lower throughput is a reminder that reaches some patients and not others, which is worse than an outage, because a filtered message leaves no error for the system to show you. But a page that says filtering and fees is not a page that says a carrier will drop your traffic, and we have not read any carrier's own documentation on that. If a provider tells you unregistered messages are blocked outright, ask them which carrier publishes that, and read it.
The opt-out rule, in the regulation's own numbers
The second wall is consent, and specifically what happens when someone wants out. The FCC's rules sit in 47 CFR 64.1200, and three paragraphs decide how a reminder system has to be built.
Any reasonable method counts. Paragraph (a)(10): "A called party may revoke prior express consent, including prior express written consent, to receive calls or text messages made pursuant to paragraphs (a)(1) through (3) and (c)(2) of this section by using any reasonable method to clearly express a desire not to receive further calls or text messages from the caller or sender." Replying with words like stop, quit, end, revoke, opt out, cancel or unsubscribe, using an automated opt-out mechanism on a call, or using a website or phone number set up to process opt-outs each "constitutes a reasonable means per se to revoke consent", and where one of those is used, "that consent is considered definitively revoked and the caller may not send additional robocalls and robotexts".
You may not pick one channel and ignore the rest. The same paragraph: "Callers or senders of text messages covered by paragraphs (a)(1) through (3) and (c)(2) of this section may not designate an exclusive means to request revocation of consent." And under (a)(11), a request made some other way — the examples given are "a voicemail or email to any telephone number or email address intended to reach the caller" — "creates a rebuttable presumption that the consumer has revoked consent" once the called party produces evidence that the request was made.
That is the sentence that breaks most reminder builds, and it breaks them architecturally rather than legally. If the opt-out list lives inside the texting tool, a patient who replies STOP is handled and a patient who emails the office is not, because the email never reaches the list.
Ten business days. Paragraph (a)(10) again: "All requests to revoke prior express consent or prior express written consent made in any reasonable manner must be honored within a reasonable time not to exceed ten business days from receipt of such request." Business days, not calendar days, and it is a ceiling rather than a target.
The confirmation message is allowed, with conditions
Sending a single confirmation text after a STOP is explicitly permitted, and the permission comes with a list. Paragraph (a)(12): "A one-time text message confirming a request to revoke consent from receiving any further calls or text messages does not violate paragraphs (a)(1) and (2) of this section as long as the confirmation text merely confirms the text recipient's revocation request and does not include any marketing or promotional information, and is the only additional message sent to the called party after receipt of the revocation request." There is also a clock on it: "If the confirmation text is sent within five minutes of receipt, it will be presumed to fall within the consumer's prior express consent."
Ten business days to honor an opt-out. Five minutes for the confirmation message to carry the presumption. One confirmation message, not two. Zero marketing content inside it.
The practical trap in that paragraph is the last clause rather than the clock. A confirmation that also invites the patient back, or tells them how to resubscribe to an offer, is carrying promotional content, and the exemption is written around a message that merely confirms.
What this means for the build
Four consequences follow from the text above, and none of them are features you will find in a reminder template.
Keep the suppression list outside the messaging tool. It has to be reachable by every channel a patient might use, which means the front desk inbox and the voicemail line feed it too. A list that only the SMS platform can write to cannot satisfy a rule that forbids an exclusive channel.
Make the scheduler check it, not the sender. If the check happens at send time inside the texting tool, every other system that can trigger a message — the booking page, the recall campaign, the no-show follow-up — is a separate hole. Check once, at the point where the reminder is created.
Log when the request arrived, not when you processed it. The ten business days run from receipt. A log that only records the processing date cannot show the gap was inside the limit.
Decide in advance what a reminder is to you. The categories a patient consented to matter, and (a)(12) contemplates a recipient who consented to more than one and may be revoking only some. Appointment reminders and promotions are different things, and a system that treats them as one list will eventually send the wrong one to someone who opted out of the other.
Our article on who is liable when your automation makes a mistake covers what happens after the wrong message goes out, and the US rules that apply to customer data covers the data side of the same workflow.
What we have not done here
We have not read any carrier's own documentation about blocking unregistered traffic, so this article does not say traffic is blocked. We have not read Twilio's A2P fee schedule, so there are no dollar amounts here; the page we did read links to a separate support article for pricing. We have not covered toll-free verification or short codes beyond noting that they sit outside 10DLC. And the throughput figures above are the ones Twilio publishes for brand types, read on its A2P 10DLC page, whose metadata showed a modification date of October 30, 2026.
The Bot Desk publishes information, not legal advice. We are not a law firm and nothing here creates an attorney-client relationship. Consent, revocation and the question of which messages count as marketing turn on facts specific to your business, and you should consult a qualified attorney licensed in your state before relying on any of this for a decision.