A patient who stops texts shouldn't have to make the same request separately in every tool a practice uses. The messaging provider, appointment scheduler, and any other sending applications need to respect that decision.
The FCC's November 25, 2026 rule change makes this a useful time to check how your systems handle opt-outs. Start with the messages already scheduled to go out.
What's changing on November 25
The published final rule allows category-specific revocation for covered informational calls and texts. Revoking consent for advertising or telemarketing still applies to future advertising or telemarketing from that caller. The effective date is November 25, 2026. Federal Register final rule
A sender may also designate a clearly disclosed exclusive way to revoke consent. If that method is replying to a text, it must recognize all seven standardized opt-out phrases, including CANCEL. Without an exclusive method, reasonable methods remain valid.
The general processing limit is a reasonable time, no more than ten business days. Some healthcare exemptions require immediate opt-outs. The limit isn't a reason to leave affected reminders running.
These options apply from the effective date and still need to match your provider's actual behavior. The companion proposal discusses further changes; those aren't requirements enacted by this final rule.
Check your appointment reply instructions
“Reply CANCEL to cancel your visit” can cause a problem: the provider may treat CANCEL as an opt-out before your scheduling code receives it.
Check the keyword behavior before putting that instruction in a reminder. Use a scheduling link or another reviewed response flow when appropriate, and confirm the change once it's recorded in the appointment system.
Keep appointment status separate from texting permission. STOP shouldn't silently cancel a visit, and booking another visit shouldn't silently turn texts back on.
Receive the opt-out
Save the request and stop affected texts.
Update the preference
Keep a record of what changed and when.
Notify sending systems
Update the scheduler and any other tools that send texts.
Check before sending
Cancel affected reminders and check permission before the next send.
Try the whole opt-out process
Send an opt-out from a test number and follow it through the systems you use. Check the provider's block, the contact preference in your application, and any reminders waiting in the scheduler.
Cancel affected scheduled messages where supported. Check permission again before sending so an older queued job can't rely on an out-of-date contact record. If an update fails to reach another system, make the failure visible and give someone responsibility for fixing it.
Keep a history of preference changes. A routine contact import or a corrected phone number mustn't overwrite a more recent opt-out. If the patient later signs up again, retain the consent evidence and follow the provider's supported re-enrollment process.
Pinnacle delivers incoming-message events to your application. We can help connect those events to your scheduler and other sending tools as part of the integration. Our opt-in guide covers disclosures and consent documentation.
Don’t miss the next guide.
Get Pinnacle’s healthcare guides in your inbox.