An AI voice agent for a Medicare or insurance agency screens leads, checks eligibility, and books appointments for roughly $0.05 to $0.35 a minute on top of a $59 to $500 monthly platform fee. Suvysoft builds these on leading frontier models. The gap vendor pages skip: CMS requires every Medicare marketing and sales call recorded and retained for six years, a Scope of Appointment rule just changed for 2027, and the AI itself cannot hold the insurance license the sale legally requires.
Every voice AI vendor selling into Medicare and insurance agencies leads with the same pitch: after-hours lead capture, faster qualification, lower cost per call than a human agent. None of the vendor pages checked for this post name the actual federal recordkeeping rule that governs those calls, the appointment-scheduling paperwork CMS just rewrote for the 2027 plan year, or the plain fact that a voice bot cannot be the one who is legally allowed to sell the policy. Getting the call flow right is a compliance question before it is a conversion-rate question.
What can an AI voice agent actually do on a Medicare or insurance call?
The honest answer is: screen, not sell. An agent can confirm someone is Medicare-eligible, capture their ZIP code and current coverage, answer general questions about how Medicare Advantage or Part D works, and hand a qualified, consented lead to a licensed producer for the plan-specific conversation. Every state requires a person who sells, solicits, or negotiates insurance to hold a producer license, and an AI system cannot hold one. The vendor pages for Regal, SunFire, and several other Medicare-focused platforms describe screening and qualification in detail but stop short of saying the voice agent completes a sale on its own, because it structurally cannot under state insurance law.
What that means for the call flow: the AI branch and the licensed-agent branch need a clean, documented handoff point, not a blurry line where the bot starts quoting premiums or comparing specific plans. That handoff is also where most of the compliance exposure below actually attaches.
What does CMS require you to record, and for how long?
Every Medicare Advantage and Part D marketing, sales, and enrollment call has to be recorded in full under 42 CFR 422.2274(g)(2)(ii) and its Part D counterpart at 423.2274. The retention period is six years: the first three years in audio format, years four through six in either audio or a complete transcript. That six-year figure is itself a 2026 change, down from the ten-year retention CMS previously expected for marketing and sales calls, though enrollment records still carry the full ten-year retention separately.
The rule applies to Third-Party Marketing Organizations, a category that explicitly covers independent agents, brokers, and lead-generation firms working on a plan's behalf, not just the health plan itself. An agency running an AI voice agent for outbound Medicare calls is a TPMO under this definition, and the recording obligation attaches to every call the bot places or answers, not just the calls a licensed human eventually closes.
What changed with the Scope of Appointment rule for 2027?
CMS finalized a change to the Scope of Appointment requirement on April 6, 2026, as part of the Contract Year 2027 final rule, eliminating the 48-hour waiting period that previously had to sit between when a beneficiary agreed to a personal marketing appointment and when that appointment could happen. The change is codified at 42 CFR 422.2264(c)(3)(i) and its Part D counterpart, and applies to marketing and communications beginning October 1, 2026, the traditional start of the Medicare Annual Enrollment Period.
The SOA itself still has to be completed before the appointment starts. For a virtual or phone appointment, CMS accepts an audio or video recording of the SOA discussion, or an electronic record, in place of a signed paper form. That detail matters directly for a voice agent build: an AI-run intake call can capture a compliant SOA on the spot, in the same call where it screens the lead, as long as the recording and retention requirements above are wired into the call flow rather than assumed.
Does an AI voice agent need an insurance license to make these calls?
The system does not, and cannot, hold a producer license, and none of the compliance pages checked for this post frame it that way directly, most describe AI use in terms of HIPAA and data security rather than producer licensing. But the underlying rule has not moved: a person who sells, solicits, or negotiates an insurance contract needs a state producer license, and an automated system replacing that person's script does not remove the licensing requirement, it just relocates where the license has to sit in the call flow. The agency, not the AI vendor, stays on the hook for making sure a licensed human is the one actually selling.
State insurance regulators have also started layering AI-specific oversight on top of that baseline. The NAIC's Model Bulletin on the Use of Artificial Intelligence Systems by Insurers, adopted in December 2023, tells insurers that decisions supported by AI still have to comply with every applicable insurance law, and requires a written AI governance program covering third-party tools an agency did not build itself. The NAIC itself said in December 2025 that over half of all states had adopted the bulletin or substantially similar guidance, which means an agency's AI vendor contract is now something a state insurance examiner can ask to see.
| Task | Can the AI voice agent do it alone? | Who has to be involved |
|---|---|---|
| Eligibility screening, ZIP code, current coverage | Yes | AI agent only |
| General Medicare education (how Parts A-D work) | Yes | AI agent only |
| Scope of Appointment intake for a scheduled call | Yes, if recorded per CMS format rules | AI agent, with the recording retained |
| Comparing or recommending specific plans | No | Licensed producer |
| Completing enrollment | No | Licensed producer |
What does an AI voice agent cost for a Medicare or insurance agency?
Pricing splits into general-purpose voice infrastructure and insurance-specific packaged tools. General voice AI platforms run roughly $0.05 to $0.35 a minute in per-minute fees once telephony, transcription, and the voice model are all counted, with monthly platform costs layered on top depending on the vendor. Aloware's own published example for an insurance outbound-qualification use case shows 800 minutes of connected conversation at $0.20 a minute, for $160 in usage cost on top of its base plan, with separate flat-rate voicemail drops billed at $0.02 each instead of by the minute.
A single-location agency testing lead qualification on a few hundred calls a month fits comfortably inside a low-hundreds monthly budget. An agency running Medicare AEP volume across multiple states, with SOA capture, call-frequency tracking, and CMS-format recording retention built into the call flow rather than bolted on afterward, needs the higher end of that range plus the engineering time to wire the compliance logic in, which is exactly the part a generic voice AI subscription does not include out of the box.
What does getting this wrong actually cost?
CMS can impose a civil money penalty of up to $25,000 per determination, adjusted annually for inflation, under 42 CFR 422.760 and the underlying authority at 422.752. A single marketing campaign that reaches a large list can generate multiple separate determinations rather than one flat fine, and a pattern of violations tied to an unrecorded or improperly retained set of calls is the kind of finding a CMS program audit is specifically built to surface. Losing the underlying recordings themselves, whether from a vendor contract that never specified retention or a platform that only keeps 90 days of call history by default, removes the agency's own evidence that a disputed call went the way it says it did.
Frequently asked questions
Can an AI voice agent legally sell a Medicare Advantage plan?
No. Selling, soliciting, or negotiating insurance requires a state producer license, and an AI system cannot hold one. A voice agent can screen eligibility, answer general questions, and capture a Scope of Appointment, then hand the plan-specific conversation to a licensed human producer, who stays legally responsible for the sale itself.
How long do Medicare marketing calls have to be recorded and kept?
Six years under 42 CFR 422.2274(g)(2)(ii): the first three years as full audio, years four through six as audio or a complete transcript. That is down from the ten-year retention CMS previously expected for marketing and sales calls specifically, though enrollment records are still kept for a full ten years.
What is the Scope of Appointment, and did it change for 2026?
The Scope of Appointment is the required documentation confirming a beneficiary agreed to discuss specific insurance products before a sales appointment starts. CMS eliminated the 48-hour waiting period between agreeing to an appointment and holding it, effective for marketing beginning October 1, 2026, under the Contract Year 2027 final rule finalized April 6, 2026.
Does an AI voice agent count as a Third-Party Marketing Organization?
An agency using an AI voice agent to place or answer Medicare marketing, sales, or enrollment calls on a plan's behalf fits CMS's TPMO definition, which explicitly covers independent agents, brokers, and lead-generation firms, not only the health plan itself. That means the call recording and retention rules apply to the agency running the bot.
How much does an AI voice agent cost for an insurance agency?
General-purpose voice AI platforms run roughly $0.05 to $0.35 a minute, with a published insurance-specific example from Aloware showing $160 in usage cost for 800 connected minutes at $0.20 a minute. Monthly platform fees run from roughly $59 for a small setup into the low hundreds for higher volume with compliance features built in.
What happens if an agency's AI voice calls are not recorded properly?
CMS can impose a civil money penalty of up to $25,000 per determination under 42 CFR 422.760, adjusted annually for inflation, and a single campaign can generate multiple determinations rather than one fine. A program audit that turns up missing or improperly retained recordings also removes the agency's own record of what was actually said on a disputed call.
Deciding where the AI branch ends and the licensed producer branch starts is a call-flow design question as much as a compliance one. Suvysoft builds voice agents and custom agent systems with CMS-format call recording, retention, and Scope of Appointment capture wired into the logic rather than left to a generic script, checked with evals and guardrails built for regulated call flows. Contact Suvysoft to talk through what your call volume and state mix actually require.