For Medicare call centers, the Telephonic Scope of Appointment (T-SOA) is often the most practical way to obtain beneficiary consent before a sales conversation. But unlike paper or electronic SOAs, the T-SOA relies entirely on a recorded verbal exchange—and CMS holds call centers to exacting standards on how that exchange is conducted, recorded, and retained. One missed scripting element, a dropped recording, or a sales discussion that starts before the SOA is documented can result in compliance violations that threaten your Medicare operation. This guide walks through the complete T-SOA process step by step, covering scripting requirements, recording rules, inbound vs. outbound differences, and how technology can automate compliance from start to finish.
What Is a Telephonic Scope of Appointment (T-SOA)?
A Telephonic Scope of Appointment is a verbal version of the standard CMS Scope of Appointment form, completed over the phone and captured on a recorded call. Instead of the beneficiary signing a physical or electronic document, they verbally confirm which Medicare product categories they agree to discuss, and the recorded call serves as the official compliance documentation.
CMS explicitly allows the T-SOA as a valid method for obtaining beneficiary consent, recognizing that many Medicare sales interactions begin with a phone call rather than an in-person visit. However, the telephonic format introduces unique compliance requirements that don't apply to paper or electronic SOAs—most notably, the obligation to record the entire T-SOA conversation and retain that recording for 10 years.
T-SOA vs. Other SOA Methods
- Paper SOA: Signed physically—impractical for phone-based sales operations
- Electronic SOA (E-SOA): Signed digitally via email or web portal—good for tech-savvy beneficiaries
- Telephonic SOA (T-SOA): Verbal confirmation on a recorded call—ideal for call centers handling high volume
For a broader overview of all SOA methods and the underlying CMS rules, see our complete Scope of Appointment rules guide.
The Step-by-Step T-SOA Capture Process
A compliant T-SOA call follows a precise sequence. Every step must be completed, captured on the recording, and verified before the call ends. Skipping any element—or performing them out of order—can invalidate the entire SOA and expose your agency to CMS enforcement actions.
T-SOA Call Sequence
Inform the beneficiary that the call is being recorded. This must happen at the very start of the call, before any SOA language is read. The recording disclosure satisfies both CMS requirements and state wiretapping laws.
The agent identifies themselves by name, states the name of the agency or plan sponsor they represent, and explains that the purpose of the call is to obtain a Scope of Appointment for a future Medicare discussion.
The agent reads the required CMS language explaining that the beneficiary is under no obligation to enroll, that the discussion will be limited to the products they select, and that they may end the appointment at any time.
The agent lists Medicare Advantage and Part D product types one at a time and asks the beneficiary to confirm or decline each one. Medicare Supplement is not a CMS SOA product. Do not treat a Medigap pitch as something the SOA authorizes.
After all product categories have been presented, the agent reads back the selected products and asks the beneficiary for a final "yes" confirming the overall Scope of Appointment.
The agent confirms when the personal marketing appointment will happen. Since October 1, 2026, that can be the rest of the same call. There is no 48-hour window to verify.
The call ends and the recording is automatically tagged as a T-SOA call, linked to the beneficiary's record, and queued for 10-year retention.
T-SOA Scripting Requirements
Unlike a casual phone conversation, the T-SOA call must follow a structured script that includes specific language mandated by CMS. Agents should read the script verbatim—paraphrasing or summarizing CMS-required language is not acceptable and can invalidate the SOA during an audit review.
Required Script Elements
- Recording disclosure: "This call is being recorded for quality assurance and compliance purposes."
- Agent identification: Full name, agency name, and the plan sponsor(s) represented
- Purpose statement: "The purpose of this call is to obtain your Scope of Appointment, which documents the types of Medicare products you would like to discuss at a future appointment."
- No obligation statement: "You are under no obligation to enroll in any plan as a result of this appointment."
- Product category listing: Each product type read individually with a pause for beneficiary confirmation
- Summary and final confirmation: "To confirm, you have agreed to discuss [products]. Is that correct?"
- Appointment: Confirm that the SOA is complete before any plan-specific discussion. Same-day and same-call appointments are allowed
Script Deviation Warning
Agents who paraphrase, skip, or rush through CMS-required language create audit risk even when the beneficiary clearly consented. CMS auditors compare recorded T-SOA calls against the required elements checklist. If the recording shows the agent summarized the no-obligation statement rather than reading it verbatim, the SOA may be deemed non-compliant—regardless of the beneficiary's intent.
Recording Requirements for T-SOA Calls
The T-SOA recording is the compliance documentation. Unlike paper or electronic SOAs where the signed document serves as proof, the T-SOA relies entirely on the audio recording to demonstrate that the beneficiary gave informed, voluntary consent. This makes recording quality and retention absolutely critical.
Full Call Capture
The recording must capture the complete T-SOA conversation from start to finish—no partial recordings, no gaps, no edits. Both sides of the conversation must be clearly audible.
Audio Clarity
The recording must be clear enough that an auditor can understand every word spoken by both the agent and the beneficiary. Background noise, poor connections, or low volume can render a T-SOA invalid.
10-Year Retention
Plan sponsors expect marketing and sales recordings to be available for 10 years. Keep the file for the period your carrier requires, and test that a supervisor can still open it. Storage does not by itself guarantee the recording will be accepted in an audit.
Record Linking
Each T-SOA recording must be linked to the beneficiary's contact record and the corresponding sales call recording, enabling instant retrieval during CMS audits.
For a comprehensive look at CMS call recording obligations beyond T-SOA, see our dedicated CMS call recording requirements guide.
Inbound vs. Outbound T-SOA: Key Differences
Inbound and outbound calls still differ for Permission to Contact and for how the beneficiary reached you. They no longer differ on a 48-hour wait. CMS removed that wait for CY 2027 marketing beginning October 1, 2026. On either type of call, complete the SOA before plan-specific discussion. Same-call sales are allowed after that.
Inbound (Beneficiary-Initiated)
- Beneficiary contacts your center first
- No 48-hour wait to waive. The wait is gone
- T-SOA and the sales conversation can happen on the same call
- Say on the recording that the beneficiary called and asked to discuss Medicare Advantage or Part D
- Still complete every T-SOA script element before the pitch
Outbound (Agent-Initiated)
- Your center contacts the beneficiary, with Permission to Contact already on file
- The old "no exceptions" 48-hour rule does not apply
- T-SOA and the sales conversation can happen on the same call
- Complete the SOA before discussing plan benefits
- Do not configure the dialer to block the sales conversation for 48 hours
Say Who Started the Call
State on the recording whether the beneficiary called you or you called them, and that they agree to discuss specific Medicare Advantage or Part D product types before you compare plans. That documents the SOA. It is not a waiver of a waiting period CMS no longer requires.
Common T-SOA Mistakes That Trigger Violations
Even experienced call centers make T-SOA errors. These are the mistakes that most frequently appear in CMS audit findings and CTM complaint investigations:
The agent starts comparing plans before the beneficiary has agreed to the product types. Same-call sales are allowed. Sales before the SOA is not.
The agent forgets or abbreviates the CMS-required statement that the beneficiary is under no obligation to enroll, rendering the T-SOA non-compliant.
The agent suggests which products the beneficiary should select—"You'll want to hear about Medicare Advantage"—instead of letting the beneficiary choose freely.
The recording starts late (missing the opening disclosure), has audio gaps, or was never saved due to a system failure. Without a complete recording, there is no valid T-SOA.
The agent reads through the product categories but never obtains a clear "yes" from the beneficiary as a final confirmation of the overall Scope of Appointment.
The recording never states which product types the beneficiary agreed to discuss, so a reviewer cannot tell whether the later plan comparison stayed in scope.
Technology Solutions for T-SOA Compliance
A script on a shared drive and a spreadsheet of appointment times do not scale. Put the script on the agent's screen, record the call, and score it against the disclosures you configured. That gives a supervisor something to review. It does not make a missed SOA impossible.
On-Screen Script Prompting
Put the T-SOA script where the agent can read it during the call. The agent still has to say the words. The screen does not stop the call if they skip a line.
No Dial-Time Hold
Do not use the dialer to block a sales call for 48 hours. That wait is no longer a CMS rule, and AgentTech does not block dials based on SOA timing.
AI Script Verification
AI scores the recording against the script and disclosures you configured and surfaces calls for a supervisor to review. The score is not a compliance determination.
Auto-Tagging and Linking
The call is recorded and can be stored with the contact. Set retention to meet your carrier's 10-year expectation. Nothing here files the SOA with CMS for you.
Building a Bulletproof T-SOA Workflow
A compliant T-SOA workflow isn't just about individual call quality—it's about building operational systems that make compliance automatic. Here's how leading Medicare call centers structure their T-SOA operations:
Operational Workflow Best Practices
- Separate T-SOA queue from sales queue
Create a dedicated call queue or disposition type for T-SOA calls. This provides clear separation between SOA and sales activities in your reporting and makes it easy to pull T-SOA calls for audit review. - Give agents the script
Put the T-SOA language in the campaign script so agents read it in order. Do not describe that as a lock that makes a skipped line impossible. - Schedule the next step in the CRM
If the sales conversation is not finished on this call, have the agent set the follow-up. Do not auto-schedule a callback 48 hours later, and do not lock the lead out of the call list. - QA every T-SOA call for the first 30 days
New agents should have 100% of their T-SOA calls reviewed by a compliance supervisor during their first month. After that, move to random sampling—but never less than 10% of all T-SOA calls. - Review a sample every week
Pull T-SOA recordings, script scores, and dispositions. Look for pitches that started before the SOA. Stop reporting a 48-hour compliance rate. That metric no longer measures a CMS rule.
For a broader view of Medicare compliance beyond T-SOA, including marketing rules and enrollment guidelines, see our comprehensive Medicare compliance guide.
Conclusion: Make T-SOA Compliance Automatic
The Telephonic Scope of Appointment is the compliance foundation for every Medicare sales call your center makes. When done right, it protects beneficiaries, protects your agency, and creates an audit trail that withstands CMS scrutiny. When done wrong—or inconsistently—it becomes the single point of failure that can unravel your entire Medicare operation.
Record the call, keep the script in front of the agent, and have a supervisor review the scores. That is how a floor finds missed SOA language. It does not make a non-compliant call impossible, and it does not enforce a 48-hour wait CMS removed on October 1, 2026.
Don't leave T-SOA compliance to manual processes. Automate it, monitor it, and make it the strongest link in your compliance chain rather than the weakest.