The Pulse
The FCC's revoke-all consent requirement is now scheduled for January 31, 2027.
The requirement would treat an opt-out sent to one program as revocation of consent across that sender's automated messages, purposes and channels.
It was originally set for April 2026. The FCC pushed it in January, and the date has now moved once already, so treat it as a planning marker rather than a promise.
Until it lands, a healthcare limited waiver applies: when a patient opts out of a treatment-related informational text, you only have to stop that same type of message, not everything else you send them.
The window between now and that date is the cheapest time you will ever get to fix how consent is stored.
The DEA's permanent telemedicine rule entered OMB review on August 25.
The Special Registrations for Telemedicine and Limited State Telemedicine Registrations rule is now under White House review, with a Justice Department forecast pointing to November.
Nothing about its content is settled and no date is committed. The current flexibilities still expire December 31.
What changed is the shape of the problem. A cliff with no replacement in sight is now a cliff with a replacement in the pipeline, arriving late.
Healthcare services private equity deal count is tracking toward a nine-year low.
Fierce Healthcare projected 674 healthcare services private-equity deals for 2026, reported on September 8. That is the lowest count since 2017, against a 2018 to 2024 average of 903.
Fewer deals means longer diligence and more scrutiny per deal, not just fewer buyers.
If an exit is anywhere in your three-year plan, the retention data you cannot produce today is the diligence question you answer badly later.
The Deep Dive
A patient texts STOP to a promo about your new peptide line. Nine days later their refill reminder does not send. Six weeks after that they cancel, and the exit survey says it just was not for them.
Nothing in that sequence shows up as a compliance problem. It shows up as churn.
1. Most telehealth SMS setups have one consent field, not two.
Promotional sends and operational sends read the same subscription state. One STOP switches both off.
And the messages that carry the retention weight are the operational ones:
Refill due and refill shipped
Dose escalation reminders
Lab result ready
Payment method expiring
A patient who opted out of a discount offer did not ask to stop hearing that their medication is on the way. Your database cannot tell the difference, so it makes the safe choice and silences everything.
2. Right now the rules let you separate them. That is the part scheduled to change.
Under the current healthcare limited waiver, an opt-out from a treatment-related informational text only obligates you to stop that same type of message. Other categories can continue.
The FCC's revoke-all requirement would collapse that. An opt-out in one place gets treated as revocation across purposes and channels for that sender.
It moved from April 2026 to January 31, 2027, and it could move again. That is not a reason to wait, because the patients being silently dropped by a single shared field are already being dropped today.
Worth being clear about what the deadline actually costs you. It does not create the problem. It removes the workaround you would otherwise reach for once you notice it.
3. The work is data architecture, not legal review.
Three specific things, in order:
Two properties, not one. Separate
sms_marketing_consentfromsms_transactional_consent, each with its own timestamp and capture source. If your promo campaigns and your refill reminders both check the same field, you have one property with two names.Every send keyed to the right property. This is where most setups fail quietly, because the field exists but the operational campaigns were built before it did and still reference the old one.
Spend the clarifying reply properly. Current rules allow exactly one message after a revocation to clarify what the patient meant. Most brands spend it on "You have been unsubscribed." Ask which one they wanted to stop instead.
Takeaway: The compliance date will probably move again. The silent churn from one shared consent field will not, because it is already running.
Quick Takes
Fewer buyers means deeper diligence, not just lower multiples.
A thinner deal market does not simply reprice companies. It changes what gets asked.
The first artifact a buyer wants is a cohort retention curve by acquisition month. Most telehealth brands can produce a CAC chart in ten minutes and cannot produce that curve at all.
Build it while nobody is asking. It is a much worse project under a deadline set by someone else.
Six weeks is not enough time to build a flow.
If the DEA's permanent rule really does arrive in November and the current flexibilities really do expire December 31, that is roughly six weeks between knowing the rules and living under them.
Writing patient comms, getting clinical and legal sign-off, building the branches and testing them does not fit in six weeks at most companies.
Draft the messaging now against the scenarios rather than the final text. The parts that depend on the actual rule are smaller than they look.
One Thing to Try
Open your ESP and find the field your SMS sends actually check before they fire.
Then build one segment: patients with an active subscription who are opted out of SMS.
Count how many of them received a refill or shipping text in the last 30 days. If that number is zero, every patient on that list is running on your product with no operational messaging at all, and none of them chose that.
Sort the list by subscription start date and you will see how long this has been happening.
The field split comes after. The count takes about twenty minutes and it is the number that gets the project approved.
If retention is your biggest revenue leak, that’s what we fix. growthtrigger.xyz
Reply to this with your biggest retention challenge. I read and respond to every single one.