Compliance May 16, 2026

Telephonic Enrollment SOPs Every Insurance Agency Should Have Documented

Rachel Nguyen
Sr. Compliance Analyst

A written telephonic-enrollment SOP used to be a nice-to-have. Under the current TPMO regulatory environment, it is an audit prerequisite. CMS reviewers expect to see it. Carrier compliance teams ask for it during onboarding. State DOI inquiries reference it. Agencies that cannot produce a current, dated, version-controlled telephonic SOP within 24 hours of an audit notice are signaling their compliance posture before the auditor reads a single page. The good news: the document is not long. The bad news: most agencies do not have one — or they have one written by their carrier, which is not a substitute for an agency-side SOP.

What CMS Expects In Writing

42 CFR
422.2274 / 423.2274 govern TPMO conduct, including telephonic enrollment SOPs
10 yrs
recordings and enrollment artifacts must be retained per CMS
~6 sections
core sections in a defensible telephonic enrollment SOP
Annually
minimum review cadence; CMS rule changes can trigger sub-cycle updates

Why You Cannot Use Your Carrier's SOP

Carriers publish their own telephonic-enrollment guides. They are well-intentioned and frequently better-written than what most agencies produce. They are also not your SOP. Your SOP must reflect how your agency handles inbound versus outbound calls, your supervisor coverage, your call recording and retention practice, your script library, your QA process, and your remediation pathway. A CMS auditor opening a binder full of UnitedHealthcare and Humana branded materials will note the absence of an agency-level document — and that absence colors how the rest of the audit reads.

The applicable federal rules sit at 42 CFR 422.2274 for MA and 423.2274 for Part D, with broader marketing-conduct expectations in the Medicare Communications and Marketing Guidelines.

The Six Sections an Agency-Grade SOP Must Contain

Build the document around six sections. Each should be one or two pages — long enough to be specific, short enough that a producer can read the whole thing in a sitting.

Telephonic enrollment SOP — required sections

1
Scope and applicability — who at the agency is covered (W-2 producers, 1099 producers, screeners, supervisors); inbound vs outbound coverage; product lines.
2
Required disclosures and order — TPMO disclaimer, recording disclosure, agent identification, "we do not offer every plan available."
3
SOA and authorization — when SOA is required, how it is obtained, retention, third-party authorization for caregivers/POAs.
4
Plan presentation and comparison — what the agent must cover; the comparison artifacts; the "do not disparage Original Medicare" rule.
5
Application capture and verification — read-back of demographic and plan info, verbal attestation, e-signature workflow, application transmission.
6
QA, supervision, and remediation — call sampling rate, scoring rubric, escalation pathway, failure-to-comply remediation.

Disclosure Order: The First Three Minutes

Auditors read the first three minutes of telephonic-enrollment recordings the same way every time. They are looking for: (1) the recording disclosure, (2) the TPMO disclaimer, (3) the agent's name and license context, and (4) the limitation language ("we do not offer every plan available in your area"). The SOP should specify the order, the verbatim language for each, and the timing target. Most agencies underweight #4 — the limitation language — and CMS underscores it explicitly in current marketing guidance. Our broader piece on CMS recording requirements covers the disclosure stack in more detail.

"Read it verbatim" is a load-bearing instruction

Paraphrased TPMO disclaimer language is a recurring CMS audit finding. Your SOP should specify the exact text and require it to be read from the script library — not delivered from agent memory.

SOA and Telephonic Authorization

Telephonic SOAs are permissible under CMS rules and have been a major source of audit findings as agencies adapted to telephonic-only enrollment workflows. The SOP must specify: how the SOA is recorded (verbal, written, electronic), the products covered by each SOA, the timing relative to the appointment (with carve-outs for beneficiary-initiated contact), the storage, and the retention. Our piece on telephonic scope of appointment covers this in depth; the SOP is the binding agency-level document on top of it.

Application Verification: The Read-Back Discipline

Verbal application read-back is the single biggest preventer of post-enrollment dispute. The SOP should require, in writing, that every application be read back to the beneficiary in the recorded portion of the call: name, DOB, address, plan selection, effective date, premium, and any relevant deductible/MOOP. CMS auditors love this section. CTM disputes evaporate when the dispute can be answered with "we read this back to you on the call; here is the timestamp."

What read-back must capture

  • Beneficiary identity — full legal name, DOB, current Medicare number.
  • Plan selection — full plan name, contract/PBP if relevant, effective date.
  • Premium and out-of-pocket — monthly premium, MOOP, any plan-specific cost-sharing the beneficiary asked about.
  • Network confirmation — primary care physician name and in-network status.
  • Verbal attestation — "do you authorize this enrollment, yes or no" — and the answer must be in the recording.

Auditing the SOP, Not Just the Calls

The SOP must specify how the agency audits compliance with the SOP. We recommend: at least 2-5% of enrollment calls sampled per agent per month during the off-season; 5-10% during AEP; supervisor-driven scoring against a documented rubric; and a written remediation pathway for agents who fall below threshold. The audit cycle is a section in the SOP, not a separate document. CMS reviewers want to see that compliance is operationalized, not aspirational. We covered the broader audit-readiness pattern in our audit readiness checklist.

Versioning, Sign-Off, and Distribution

Treat the SOP like a controlled document. Every version is dated, every change is logged, every producer signs an acknowledgment when the SOP is updated. CMS auditors will ask "how do you know your producers have read the current SOP?" The answer must be a signed acknowledgment in the agent file with a date that postdates the version in question.

Updating the SOP When CMS Updates the Rules

CMS publishes updated marketing guidance roughly annually, with mid-year clarifications when significant. The SOP must have a named owner (typically the compliance director) who reviews the rules each year and runs the document through a formal update cycle. An SOP that references repealed regulations or out-of-date disclaimer language is worse than no SOP, because it actively documents your agency's failure to keep current.

Key Takeaways for Agency Operators

  • The carrier's SOP is not your SOP — agencies need an agency-level document.
  • Six sections, written specifically — scope, disclosures, SOA, presentation, application capture, QA.
  • Disclosure order is verbatim — paraphrasing the TPMO disclaimer is a recurring audit finding.
  • Verbal read-back captures everything — identity, plan, premium, network, attestation.
  • The SOP audits itself — call sampling rate and remediation pathway are sections in the SOP.
  • Version, sign, distribute — every producer signs an acknowledgment on every update.

The telephonic enrollment SOP is no longer optional documentation. It is the artifact that tells a CMS reviewer, in 30 seconds, whether the agency has internalized the regulatory environment or just memorized the carrier handouts. Build the document, version it, distribute it, and — most importantly — operate against it. The agencies that take the SOP seriously discover that audits get shorter, complaints get fewer, and carrier compliance teams stop calling for "discussions."

Keep Disclaimer Language Aligned With Your SOP

AgentTech Dialer's per-queue script library keeps the TPMO disclaimer language exactly aligned with the documented SOP — so when CMS updates the rule, you update the script library once, and every producer reads the current version on the next call.

Try AgentTech Dialer Now

References & Authoritative Sources

The information on this page is supported by the following official and authoritative sources.

  1. 1
  2. 2
  3. 3

Related Articles

March 8, 2026

T-SOA Compliance Guide

Step-by-step guide to capturing T-SOA correctly during inbound and outbound Medicare calls.

February 24, 2026

AI Compliance Monitoring

A practical guide to AI compliance monitoring in insurance call centers: what it covers, how teams operationalize it, and what to ask vendors.

April 16, 2026

AI Agents for Medicare Calls

A compliance-first framework for using AI agents in Medicare call flows: safe automation targets, escalation guardrails, and audit-ready documentation.

Last updated: