Last updated: September 12, 2026
This page describes federal regulation and is not legal advice. Read the current CMS text and put your script in front of your own counsel before you train anyone on it.
What a compliant Medicare sales call script contains
A compliant Medicare sales call script carries the recording notice, the TPMO disclaimer before any benefit is named, the Scope of Appointment capture, and benefit language taken from approved plan materials. Order decides more than wording does here, because the disclaimer trigger moves with the conversation instead of sitting at a fixed time.
Here is an opener that reads fine on paper.
"Hi, this is [agent] with [agency], on a recorded line. Good news, there is a zero dollar premium plan available in your county this year. Before we go any further I need to read you a quick disclaimer."
Three of those four sentences hold up. She identifies herself, names the agency, and puts the recording notice at the top, and her disclaimer is next, word for word from the approved language.
The phrase "zero dollar premium plan" is a benefit. Once it is out of her mouth the disclaimer is late, because 42 CFR 422.2267(e)(41)(ii) puts it before the discussion of any benefits. Nothing about her wording is wrong and the call fails anyway.
Every requirement here attaches to a moment rather than to a paragraph, so a script holding all the right paragraphs in the wrong sequence turns out non compliant calls at volume. Repairing it is a sequencing job.
The running order, and what triggers each line
Seven positions. The trigger column is what moves a line, and the last says whether a recording settles it.
| Sequence | Script section | Compliance trigger | Source citation | Scored from audio |
|---|---|---|---|---|
| 1 | Greeting and identification | Before anything substantive | Agency and plan partner policy | Yes |
| 2 | Recording or monitoring notice | Consent law in every state on the call | State consent statutes | Yes |
| 3 | TPMO disclaimer | Before any discussion of plan benefits | 42 CFR 422.2267(e)(41)(ii) | Yes |
| 4 | Permission to contact | Before an outbound call, for the products discussed | TCPA consent posture | No |
| 5 | Scope of Appointment capture | Before plan specific discussion | 42 CFR 422.2264 | Yes |
| 6 | Benefit statements | Any coverage, cost, or comparison claim | 42 CFR 422.2262 | Yes |
| 7 | Enrollment confirmation and close | Before an enrollment is submitted | Agency enrollment procedures | Yes |
The same rows download as a script skeleton CSV.
Rewriting it, pass by pass
Each pass changes one part and leaves the rest alone. They run in call order below, which is how a script gets written and a poor order to repair one in. The last section sorts them by risk.
The greeting and the recording notice
The notice at the top of the call has nothing to do with CMS. It comes from consent law in each state on the line, so an agency dialing thirty states writes to the strictest one and uses that everywhere. Wording lives on your recording disclosure script.
Two obligations sit seconds apart and get confused constantly. A state notice says the line is recorded, while the federal disclaimer says which plans you represent. This pass is short: keep the notice above the first substantive exchange, on its own line rather than bolted onto the front of the disclaimer.
The disclaimer moves above the first benefit line
The wording belongs to CMS and this page does not reproduce it. Both versions and the timing change that superseded the first minute standard sit on the TPMO disclaimer wording and timing.
The knock on effect is what nobody warns a sales manager about. Scripts written against the old standard open with a hook, because something interesting at second five keeps a caller on the line. Move the disclaimer above the hook and the first half minute of every call belongs to a regulator. Most agencies will not love that, and no reading of the current text hands the half minute back. The notice has to move above it too, so two compliance openers run back to back before the call reaches anything a human cares about.
Where agents get caught is the beneficiary who names a benefit first. Somebody asking whether the plan covers their dentist has started the discussion, and the agent still owes the disclaimer before answering. Write that line out and keep it outside the running order, because an agent improvising on call thirty of a Tuesday answers the question instead.
Consent, and the part a recording cannot show
Prior express written consent belongs to the outbound call and lives in a record created before it started. Your script's job is narrower: confirm the agent reached the person the consent names, and confirm the product about to be discussed sits inside the scope it covers.
Consent captured on a final expense form does not obviously stretch to a Medicare Advantage conversation, and whether it does is a question for counsel. This is also the one row a transcript cannot settle, since a recording shows what got discussed and says nothing about what somebody signed three weeks earlier. The audit for this line runs against your CRM.
Where the Scope of Appointment gets captured
A Scope of Appointment records which product types the beneficiary agreed to discuss. The CY2027 rule removed the 48 hour waiting period and left the form in place, so agencies that responded by dropping the SOA made the more expensive mistake, and Scope of Appointment rules covers where it stands now.
On a call the failure mode is drift. The SOA covers Medicare Advantage, the beneficiary asks about a standalone drug plan, and the agent answers because answering is what a good agent does. Write out the sentence that stops there and captures a new SOA, then put it beside the dentist line.
Benefit language, and where it comes from
Every benefit sentence traces back to approved plan materials for the plan year on the call. Put the plan year and the effective date in the script as their own line, since agents drop them first when speaking quickly and a beneficiary enrolled into the wrong year notices in January.
Prohibitions on comparisons and unsupported superlatives sit at 42 CFR 422.2262, which is why a benefit section drafted by a sales manager needs a compliance read before it reaches the floor. A comparison the carrier supports and one an agent invented look identical in a transcript.
Most of the scored criteria in the call live here, and this section gets the least attention in September because it is the hardest to rewrite. A Medicare sales call scorecard holds benefit accuracy at 12 points as an auto fail with the unapproved comparison criterion beside it at 7.
Confirming understanding before you submit
The close is the shortest pass and the most often missing. Confirm the beneficiary understands what they are enrolling in, say what happens next, and give confirmation details they can repeat back. All of it scores cleanly from the audio, and none of it is where an agency's exposure sits.
Which lines a machine can check and which it cannot
Fixed phrases score reliably. The disclaimer, the notice, the plan year, the effective date, and the order the sections arrived in are each present or absent in a transcript with a second attached, which Aircall and StackAI both call the dependable end of automated scoring.
Tone works differently. Whether an agent leaned on somebody, or moved too fast for a beneficiary who had stopped following the comparison, needs a person who listened to the call.
Behind both sits a limit worth saying plainly. A scorecard measures adherence to the script and has no opinion about whether the script is right. An agency running 26,000 calls against last season's wording gets a clean report on a sentence that stopped being compliant on October 1.
Scoring the script you just wrote
Every row in that table becomes a criterion, so the script and the scorecard end up as one document read two ways. Which calls have to exist at all is a separate question, answered at CMS call recording requirements under 42 CFR 422.2274.
Say you run 12 agents at about 40 calls a day. Across the 54 days of enrollment that is roughly 26,000 recorded calls, with week one alone at about 3,400. Two scored calls per agent that week gives you 24 reviews, and 24 reviews cannot tell you whether the three lines you moved on Monday reached the floor.
Scoring the whole week answers it by Friday. CallSniper ingests recordings after the calls end, transcribes them with speaker separation, then scores against the scorecard your team defines, with the disclaimer held as a phrase set in the vocabulary library. Searchable transcripts with timestamps mean a flag opens at the second that produced it. Manual upload takes last season's folder without touching your dialer, and Trinsic's private model runs on its own infrastructure, so call audio never reaches a public model provider.
The report worth having runs per line rather than per agent: which of the seven positions the floor is hitting, and where the median call puts the disclaimer against the first benefit mention. Two supervisors disagreeing about whether a disclaimer was delivered means the phrase set needs rewriting before any agent does, so watch calibration variance there first.
Agencies running this rewrite across a downline rather than a single desk will find the same criteria laid out for that structure on the Medicare agency page.
Frequently asked questions
What should be in a Medicare sales call script?
Greeting and identification, the state recording notice, the TPMO disclaimer, a permission to contact confirmation, the Scope of Appointment capture, benefit language drawn from approved plan materials, and the enrollment confirmation. Sequence carries more compliance risk than wording, since the disclaimer has to land ahead of the first benefit.
Where does the TPMO disclaimer go in the script?
Above the first line that touches a benefit. 42 CFR 422.2267(e)(41)(ii) requires delivery during sales calls prior to the discussion of any benefits, so its position depends on where your own script names a plan or a dollar figure. The TPMO disclaimer wording and timing carries both versions of the language.
Can you use your own wording for the Medicare disclaimer?
Standardized content is the term the regulation uses, and in practice it means the wording does not get adapted to the agent or the call. A paraphrase is obvious in a transcript after the fact. Whether yours passes is a question for your counsel and your plan partners rather than for a QA vendor.
Do Medicare agents have to record every call?
TPMOs record marketing and sales calls in their entirety under 42 CFR 422.2274, with enrollment records carrying their own retention period. CMS call recording requirements has the current math.
The order to rewrite in, if you have a week
Working down the call is how a script gets written and a slow way to repair one. Sort by what voids a call instead.
- Move the disclaimer above the first line that names a plan, a premium, or a dollar figure, then write the separate line for the beneficiary who gets there first. Only this one fails a call on its own.
- Put the recording notice above the first substantive exchange, with wording checked against the strictest state you dial.
- Write out the sentence that stops a conversation drifting off the Scope of Appointment.
- Walk the benefit section against current approved materials, checking the plan year, the effective date, and every comparison.
- Confirm your consent records cover the products the script discusses, which your compliance lead can run in parallel.
- Fix the close last. A weak next steps line costs you a callback.
Train the changes and score week one of AEP against the new script, which an AEP call QA checklist carries into the rest of the season. Schedule a demo if you want last October's calls scored against the script you are about to train.
Either way, the disclaimer line is the one to move tonight.
Sources
- Disclaimer timing trigger, verbally conveyed during sales calls prior to the discussion of any benefits. 42 CFR 422.2267(e)(41)(ii), read via Cornell LII on 2026-09-09. Verified against a primary text mirror. Read it again on eCFR before publishing.
- Recording obligation for marketing and sales calls. 42 CFR 422.2274, read via Cornell LII on 2026-09-09. Verified against a primary text mirror. Retention detail belongs to the recording requirements page.
- Scope of Appointment requirement, elements, and product type scope. 42 CFR 422.2264. Not read against primary text. Unverified.
- Marketing prohibitions on comparisons and unsupported superlatives. 42 CFR 422.2262. Not read against primary text. Unverified.
- Federal one party consent baseline behind the recording notice. 18 USC 2511(2)(d). Not read. Unverified, and state law governs the notice in any case.
- TCPA prior express written consent and the scope it covers. General industry posture, no primary text read. Unverified, kept general and routed to counsel.
- Removal of the 48 hour Scope of Appointment waiting period, and the October 1, 2026 effective date for the CY2027 marketing provisions (CMS-4208-F3). Agent facing summaries gathered 2026-09-08. Secondary, unverified.
- Annual Enrollment Period opening October 15. Standard CMS enrollment calendar. Confirm on cms.gov or medicare.gov before publishing.
- Aircall and StackAI, on automated scoring holding up better on rule based criteria than on subjective tone. Third party, gathered 2026-09-08. Unverified.
- The seven position running order and the reading of what counts as a benefit mention. Editorial interpretation for this page, labeled as such in the body.
- Transcript timestamps, speaker separation, vocabulary library phrase sets, manual upload, and the model hosted in Trinsic's own cloud. CallSniper product documentation. Verified.