Medicare Drops the 48-Hour Wait, and Adds a Line to Your Texts

The date that governs marketing is not the rule date#

CMS issued the contract year 2027 Medicare Advantage and Part D final rule on 2 April 2026, and it was published in the Federal Register on 6 April 2026 as document 2026-06600.

Three dates sit inside that document and industry write-ups have been mixing them up all year. Only one of the three governs what an agent may send.

Work to 1 October 2026. The Annual Election Period for 2027 opens on 15 October, so the rules change 14 days before the volume does.

• Effective date of the regulations: 1 June 2026. Applicability date for coverage: 1 January 2027 (Federal Register 2026-06600, read 15 September 2026).
• The sentence that matters: the new marketing and communications policies in the rule are applicable for all contract year 2027 marketing and communications, beginning 1 October 2026.
• CMS summarized its own intent as removing restrictions on the time and manner by which beneficiaries can have conversations with licensed agents and brokers (cms.gov fact sheet, read 15 September 2026).
• None of this is legal advice. Confirm every script change with your carrier compliance team and your upline before 1 October.

The 48-hour clock is gone#

CMS has changed its mind on the Scope of Appointment wait four times since 2011, and the phrase at issue is short. The April 2023 rule inserted the words at least 48 hours into the requirement.

The 2027 rule takes those words back out. The amended text reads that prior to the personal marketing appointment, the plan or agent or broker must agree upon and record the Scope of Appointment with the beneficiary.

So the form survives and the waiting period does not. An SOA signed at 10am supports a benefits conversation at 10:05.

• Amended sections: 422.2264(c)(3)(i) and 423.2264(c)(3)(i) (Federal Register 2026-06600, read 15 September 2026).
• The two old carve-outs are now moot: SOAs completed in the last four days of a valid election period, and unscheduled beneficiary-initiated walk-ins. Nothing needs a carve-out when nothing has to wait.
• An SOA stays valid for 12 months from the beneficiary signature date, or from the date of an initial request for information.
• What did not change: the SOA is still mandatory, it still has to name the product types to be discussed, and you still may not go beyond what it names.

The paperwork trigger got wider, not narrower#

Reading only the headline leaves an agent with the wrong picture, because the rule loosens the clock and widens the trigger in the same document.

An SOA is required for plan, agent or broker-initiated outbound contact, and for beneficiary-initiated inbound contact, as long as the contact is tailored to an individual or small group for discussing marketing topics.

Inbound is the part that catches teams out. A lead who fills in a form and asks a plan question has started something that needs an SOA before benefits get discussed.

• CMS names the inbound forms explicitly: walk-ins, unscheduled calls, web-based chats and web-based forms (Federal Register 2026-06600, read 15 September 2026).
• CMS permits check boxes on the SOA form for the product types to be discussed, including an online form that asks an agent to make contact.
• Net effect on a text sequence: the SOA moves out of the calendar invite and into the conversation, because the conversation is now where it is triggered.
• Practical read: your first reply to an inbound lead can capture the SOA, and your second can discuss benefits, in the same thread and the same hour.

A text message is an electronic means of communication#

Buried in the same rule is the change that lands hardest on messaging copy, and it concerns the third-party marketing organization disclaimer rather than the SOA.

A TPMO selling plans for more than one carrier must convey the disclaimer through email, online chat or other electronic means of communication, show it prominently on its website, and include it in marketing materials.

CMS also moved the timing on calls. The disclaimer now has to come before any discussion of benefits, replacing the old requirement to say it in the first minute.

• The revised timing sits at 422.2267(e)(41)(ii). Commenters told CMS the first minute of a call was not the most effective place for it (Federal Register 2026-06600, read 15 September 2026).
• Apply the same before-benefits logic to a thread and the disclaimer belongs in the message that precedes your first plan answer, not at the end of the sequence.
• Disclaimer text costs characters, and characters are the unit that metered vendors bill: read how a message credit gets counted before you decide where the sentence goes.
• Blue Reacher bills a flat $249 per line per month, so a longer required disclaimer changes your copy and never changes the invoice.

Two permission systems, and only one of them moved#

Every conflation of these two rules ends the same way, with a team that believes a looser CMS clock means a looser consent standard. It does not.

An SOA governs what you may discuss once a conversation is underway. Consent under the Telephone Consumer Protection Act governs whether you may send the message at all.

CMS did not touch the second one. A marketing text to a Medicare beneficiary still needs prior express written consent, and a revocation still has to be honored.

• Our TCPA compliance guide covers the consent standard, the record you need to keep, and the state laws that sit on top of it.
• The federal opt-out rules are moving separately at the FCC, and that proceeding is where your revocation handling changes: see the exclusive opt-out order.
• Do-not-call obligations reach the entity making the contact, the entity it is made on behalf of, and affiliates a consumer would reasonably expect to be included.
• One practical consequence: an SOA is not consent, and a signed SOA on a number you have no consent record for buys you nothing.

Educational events lose their buffer too#

Field teams get two more changes on the same date, and both remove a delay that had been shaping event schedules since 2023.

A marketing event may now take place directly after an educational event in the same location, provided attendees are told clearly and given the chance to leave first.

SOA forms may also be handed out and collected at educational events. CMS reversed its own April 2023 ban, reasoning that the statute bars sales activity at those events but not the collection of a form.

• The 12-hour delay requirement between an educational event and a marketing event is removed (Federal Register 2026-06600, read 15 September 2026).
• CMS cited transportation barriers for dually eligible, low-income and disabled beneficiaries as a reason the delay was doing more harm than good.
• The SOA change sits at 422.2264(c)(1)(ii)(D), permitting plans and agents to make available and receive SOA forms at those same educational events.
• Follow-up angle worth planning now: a room that signs an SOA on the day can be texted the same afternoon rather than two days later.

Ten years of recordings becomes six#

Record retention moves on 1 October as well, and the reduction is real money for any agency storing audio.

Marketing and sales call recordings drop from a 10-year retention requirement to six years. Years one through three must be audio, and years four through six may be audio or transcripts.

Enrollment documentation is a separate obligation and it did not change. Do not let a storage cleanup take the enrollment records with it.

• CMS set the change at 1 October 2026 to coincide with the start of 2027 plan year marketing (Federal Register 2026-06600, read 15 September 2026).
• The recording obligation itself is unchanged. Marketing, sales and enrollment calls are still recorded in their entirety.
• Transcripts being acceptable in years four through six is the part worth acting on, because text costs a fraction of audio to keep.
• A messaging thread is already its own record, which is one reason a written channel is cheaper to defend than a call.

What to do in the next two weeks#

Nothing here rewards waiting until 1 October, because every task on this list is a script change or a form change that takes a day.

Five jobs, in the order that saves the most work. The disclaimer placement is first because it touches every outbound message you have written.

Then fix the SOA trigger, then the sequence timing, then the retention policy, then the consent audit that none of this replaced.

• Put the TPMO disclaimer in the message that precedes your first benefits answer, and check it renders in full rather than truncating.
• Add an SOA step to every inbound path, including web forms and chat, not only to scheduled appointments.
• Collapse the two-day gap out of your sequences. A thread that used to wait 48 hours for the appointment can now run same day.
• Write the six-year retention split into your storage policy, and ring-fence enrollment records so a cleanup cannot reach them.
• Re-verify your consent records for every Medicare number on the list, because the CMS change moved none of that.

Frequently asked questions