What L&H and Medicare Agents Should Actually Look For in a CRM

A compliance-first guide from a working Ohio agent. Most “best CRM” articles weren’t written by anyone who’s been through AEP. This one was.

It was the second week of October, and the phone hadn’t stopped ringing since 8 a.m. A client in Centerville had questions about her new doctor not being in-network. Another wanted to talk about a Part D plan she’d seen advertised on TV. Three more had left voicemails. Somewhere in that mess, I needed to find a Scope of Appointment I’d captured back in August for an appointment that had finally been rescheduled for tomorrow.

The CRM I was using couldn’t tell me where it was. Not lost, exactly. Just buried in a notes field I couldn’t search.

That’s the moment, multiplied across thousands of agents every Annual Enrollment Period, when you find out whether your CRM is actually built for what you do.

Most aren’t.

If you’re getting your life and health license, picking up Medicare for the first time, or already a few AEPs in and tired of fighting your software, this article is for you. I’ve been a licensed life, health, and Medicare agent in Ohio for a couple of years, and I’ve used or evaluated most of what’s on the market. What follows isn’t a vendor’s top-ten list. It’s what I wish someone had handed me before I bought my first agency tool: a clear picture of what L&H and Medicare CRMs actually need to do, why the compliance layer changes everything, and which platforms are worth a serious look.

Why insurance CRMs are different

Most “CRM” articles you read were written for B2B sales teams. The implicit picture is a software rep trying to close a $40,000 annual contract with a logo prospect, moving them through stages on a Kanban board. Helpful for that audience. Not for ours.

Life, health, and Medicare insurance is a different animal. Three things make it different.

First, the relationships are long. A Medicare client today is potentially your client for fifteen or twenty years. The CRM’s job is not to push them through a funnel. It’s to keep their record current, surface them at the right moment (birthday, AEP, life event), and not lose anything important in the meantime.

Second, the revenue model is renewal-driven. New business is the spike. Renewals are the foundation. Generic sales CRMs don’t think about renewals as a workflow stage; insurance-specific tools do. If your software treats a five-year client the same as a cold lead, you’re going to miss things.

Third, and this is the big one, every interaction with a Medicare beneficiary is regulated. Calls, emails, websites, business cards, even the chat widget on your site. The federal government has rules about what you can say, when you can say it, and how long you have to keep proof. Most general CRMs were not built with any of that in mind. You can bolt compliance on, but bolting it on is what gets agents in trouble.

Worth noting here: insurance agencies often need both a CRM (relationship and pipeline management) and an AMS, an Agency Management System (policies, carriers, commissions, back-office). The best L&H tools combine both functions. The worst force you to run two systems that don’t talk to each other.

The compliance non-negotiables for L&H/Medicare

This is the section the generic CRM articles skip. It’s also the most important one. If you sell Medicare Advantage, MAPD, or Part D plans, the rules below are not suggestions.

Call recording

Since October 1, 2022, every agent or broker selling Medicare Advantage or Part D plans must record every sales, marketing, or enrollment call with a beneficiary. Inbound or outbound. Entirety of the call, not just the application portion. Recordings must be stored securely for 10 years.

The rule lives in 42 CFR 422.2274 and 423.2274. It applies to captive agents and independent agents equally. There is no agency-size exemption. If a beneficiary refuses to be recorded, you must end the call.

In-person meetings are not subject to the recording rule. Virtual meetings (Zoom, Teams, phone) are.

What this means for your CRM choice: the platform either records calls in a CMS-compliant way and stores them with the client record, or it doesn’t. If it doesn’t, you need a separate tool, and now you’re managing two systems and two sets of audit trails. Verify with the vendor that recordings are stored for the full 10 years, that storage isn’t a separate per-gigabyte charge that balloons at scale, and that you can pull a specific recording on demand if a carrier or CMS asks for it.

TPMO disclaimer

Before discussing any benefits on a Medicare-related call with a beneficiary, you must read the standardized Third-Party Marketing Organization (TPMO) disclaimer. Note that this trigger changed under the CY 2027 Final Rule: the old “within the first minute” requirement was replaced with “prior to the discussion of any benefits,” and references to State Health Insurance Assistance Programs were removed from the disclaimer language. The disclaimer also has to appear on websites, in emails, in chat windows, and on printed marketing. The wording is set by CMS and changes periodically; verify the current version with your FMO before AEP each year.

A good CRM should make the disclaimer easy to surface during a call (script field or call template) and easy to include on outbound communications.

Scope of Appointment

Before any personal marketing appointment with a Medicare beneficiary, you need a documented Scope of Appointment defining what products will be discussed. Historically that meant a 48-hour wait between SOA and appointment, with limited exceptions.

That’s changing, and in the agent’s favor. The CY 2027 Medicare Advantage and Part D Final Rule (CMS-4208-F3 and CMS-4212-F), released April 2, 2026 and effective June 1, 2026, removes the 48-hour SOA waiting period and the 12-hour educational-to-marketing event gap, and now permits collecting SOAs at educational events. This is a deregulatory rule: CMS rolled back several workflow barriers while keeping the core beneficiary protections in place. The SOA itself did not go away. You still need a signed SOA before any plan-specific discussion. What disappeared is the waiting period around it.

What this means for AEP: the timing bottleneck is gone, but the documentation duty is not. Your CRM should still generate an electronic SOA, capture an e-signature, store it in the client’s record (not a separate folder somewhere), and timestamp it for audit. The new flexibility actually raises the value of a system that makes same-day SOA capture and immediate scheduling smooth, since the old 48-hour buffer no longer forces a delay.

HIPAA

Any system holding client information that could be tied to health status, plan, or care is touching Protected Health Information. HIPAA’s Privacy and Security Rules apply. You need a signed Business Associate Agreement (BAA) with the vendor. No BAA, no usage with PHI. Period.

Many generalist CRMs only offer HIPAA features on higher-priced enterprise plans. Insurance-native platforms typically include HIPAA posture by default, but verify the specifics before signing.

TPMO data sharing consent

Less talked about but enforced: as of October 1, 2024, TPMOs must obtain prior express written consent (one-to-one for each recipient) before sharing a beneficiary’s personal data with another TPMO. If you’re buying or selling Medicare leads, the consent chain is now your problem, not the lead vendor’s. Your CRM should track the source and consent status of every lead.

Core features that actually matter

Past the compliance floor, here’s what a working agent uses week to week.

Carrier integrations and multi-carrier quoting. During AEP, you do not want to log into eight carrier portals to compare plans for one beneficiary. Native multi-carrier Medicare quoting (MA, MAPD, PDP, Med Supp) is one of the biggest time-savers an agent can buy. For life insurance, similar logic applies: the more carriers you can quote in one screen, the less you bounce between systems.

Commission tracking with carrier reconciliation. This is where money quietly leaks. Carriers occasionally miss commissions, pay the wrong amount, or charge back unexpectedly. A CRM that imports carrier statements and flags discrepancies will pay for itself in the first year. Solo agents often skip this; bigger books cannot afford to.

AEP-specific automation. Built-in T65 funnels, 90/60/30 day renewal reminders, OEP touchpoints, and birthday triggers. The point isn’t fancy. The point is that you set it up once and it runs in the background while you’re on appointments.

Drug list and provider list storage. Medicare clients change medications and doctors. The CRM should hold both per client, ideally with a way to compare against plan formularies during AEP review.

E-signature and document storage. SOAs, applications, replacement notices, beneficiary forms. All linked to the client record, all retrievable in seconds.

Mobile functionality. Real iOS and Android apps, not a phone-sized version of the website. Kitchen-table sales and in-home appointments still happen, especially in the senior market. You need the client’s record, the SOA, the quoter, and the signature pad on a phone or tablet.

Call recording integrated into the contact. When a recording lives in its own separate folder system, you’ll never find what you need under audit pressure. When it’s a tab on the client’s record next to their notes and policies, you will.

Buying considerations by agent type

Different agent setups have different priorities.

Solo independent agents. Cost matters. Simplicity matters. You don’t have time for a six-month implementation. Look at AgencyBloc’s lower tiers, Insureio (especially if you’re life-heavy), Agent CRM, or MedicareCENTER if you’re contracted through Integrity. A budget-conscious agent with patience for setup can also build something workable in Zoho, but plan for real customization time.

Agency owners with downline. Now you need agent permission tiers, commission split tracking, pipeline visibility across the team, and onboarding workflows. AgencyBloc Plus Suite or Salesforce Financial Services Cloud (with implementation help) are the serious options. Maximizer is a respectable middle path.

Captive agents. The carrier may dictate what you use for your captive book, but two things still apply. First, captives are TPMOs under CMS rules. The recording and disclaimer requirements do not exempt you. Second, if you have a personal Medicare side-business or a carve-out for cross-carrier work, you may need a supplemental tool. Verify your captive contract before adding any outside system.

New agents (first license, first AEP). Don’t overbuy. Start with the cheapest compliant option that handles SOA, call recording, and basic client management. Reassess after your first AEP, when you actually know what you do and don’t use.

The platforms worth knowing

These are the names that come up repeatedly. I’m not ranking them; the right one depends on your line, size, and budget.

AgencyBloc. Industry-native, strongest single fit for L&H/Medicare, full AMS plus CRM. Higher cost. Most reviewers’ pick for serious life and health agencies.

Insureio. Built for life agents. Carrier underwriter filtering and quoting. Less suited to Medicare-heavy books.

MedicareCENTER. Owned by Integrity Marketing. Free if you contract through Integrity, which is also the catch. Built-in compliant call recording, SOA capture, and Medicare quoting. Worth understanding the data ownership terms before relying on it long-term.

Agent CRM. Marketing automation focus. Pre-built AEP and T65 funnels. Active blog content on CMS rules suggests they’re paying attention.

Quotit. Quoting engine first, CRM second. Strong if your workflow is quote-heavy during AEP.

Salesforce Financial Services Cloud. Enterprise-grade, infinitely customizable, infinitely expensive. Implementation runs five to six figures. Right answer for a multi-state agency, wrong answer for a solo agent.

Zoho CRM. Generalist, cheap, customizable. The compliance plumbing is on you. Doable, not turnkey.

HubSpot. Marketing-led. Free tier is tempting. Not built for insurance compliance; HIPAA features sit behind expensive add-ons.

Nutshell, monday.com, Maximizer. Generalists with serviceable interfaces. Insurance use is a customization, not a default.

How to actually evaluate

Vendors are very good at showing demos. Demos are misleading. Here’s how to test a CRM before you sign.

Demo with your real workflow, not theirs. Walk through a real prospect intake, a real SOA capture, a real recorded call, a real renewal. Don’t let the rep drive.

Test the call recording end-to-end. Make a recording, save it, log out, log back in a week later, and pull it. If the platform can’t do that smoothly, it can’t do an audit smoothly.

Ask about 10-year storage cost. Some vendors include it; some bill it separately as your data grows. Get the answer in writing.

Get references from agents in your line, not their marketing list. Ask the vendor for two solo agents and two agency owners using the platform actively. Then call them. Ask what they hate.

Run one full cycle before committing. SOA to enrollment to commission posting. If you can do it in a 30 or 60 day trial, do.

Read the BAA. Get a HIPAA Business Associate Agreement before you put a single client in the system. If the vendor balks, that’s your answer.

Closing

A CRM is plumbing, not strategy. The right one disappears into your workflow. The wrong one becomes the second job you didn’t sign up for, and during AEP you do not have time for a second job.

For L&H and Medicare agents, the bar is higher than for other industries because the federal government audits the plumbing. Compliance isn’t a feature; it’s the foundation. Pick the tool that takes that seriously, learn it well before October, and protect both your license and your time.

The right CRM won’t make you a better agent. The wrong one can absolutely make you a worse one.

— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —

The Working Agent is written by Steve Bitsko, a licensed life, health, and Medicare agent in Ohio. More articles like this are available at The Working Agent