What a Medicare Broker's Intake Actually Needs: T65, AEP, and Consent Without Breaking Compliance

Four federal windows set the rhythm of the whole book. T65 is the month a person turns 65 and first becomes eligible. AEP runs October 15 to December 7. The scope-of-appointment agreement has to be in place 48 hours before a sales meeting. The annual notice of change lands September 30.

Four federal windows set the rhythm of the entire book. Intake either knows them cold or spends the year fighting them.

None of this is abstract. A lead who reaches the office two weeks into December has narrower options than the same lead in October, and intake either tracks that difference per person or quietly loses money on it.

Paper is genuinely fast while you are on the phone, and capture is the part it does well. Everything after is where it breaks: re-entering the lead, classifying it against the right enrollment window, and remembering who needs a call back and when. In a business where timing is the product, follow-up that runs on memory is the whole exposure.

Every inbound call at the agency started on a paper lead sheet, and here is the honest part: that works. Paper is fast when you are on the phone, and a lot of good brokers live on it. The capture is the part paper does well. Everything after it is where paper breaks: re-entering the lead, classifying it against the right enrollment window, and remembering who needs a call back and when. Lead status lived across paper, memory, and scattered notes.

In a business where timing is the product, follow-up that depends on memory is the whole exposure. And unlike most industries, the stress test is scheduled: AEP volume arrives on a date you can see on a calendar a year in advance. The system we built moved every lead from paper to a structured record the same day, classified it against its real enrollment timeline, T65, AEP, open enrollment, dual-eligible status, and started the correct follow-up path immediately. Paper could still exist. It stopped being the only place the lead lived.

One rule came out of this build and now runs on every CRM we touch: search first, never blind-write. You find the existing person before you change a single field.

Purchased lead lists are a fact of life in this vertical, and they carry a danger nobody talks about. On the book we rebuilt, 4,742 purchased contacts carried a do-not-contact flag. Deduplication, merging one person's multiple records into a single contact, is normally a hygiene chore. Here, dropping even one of those flags in a careless merge crosses from hygiene into compliance, and that is a different order of mistake.

So the priority was set deliberately: protecting that flag mattered more than resolving every last duplicate. The system proposed merges and a person approved them, and designing with that priority is the line between automation that helps a regulated business and automation that quietly builds its next violation.

When a broker tells you what they are afraid of, that is not resistance to technology. That is the requirements document.

The owner was genuinely afraid that dispositioning a test lead would fire a real thanks-for-enrolling email to a live client, so he seeded his test records with fake email addresses. He was right to be careful. He had also flagged the risk of pushing Social Security and Medicare numbers through generic automation before we raised it ourselves.

Both fears turned into hard constraints. A lead disposition could never trigger an outbound message. The instant an appointment booked, every sequence attached to that lead stopped, so nobody got chased for something they had already done. And sensitive identifiers stayed out of the automation path completely, no Social Security number and no Medicare number, at any point.

Every plan recommendation and every enrollment belonged to the licensed agent, in the agent's own enrollment system. The automation never recommended a plan, never enrolled anyone, and never ran a benefit conversation. In a regulated vertical that separation is the only version that survives an audit.

Every plan recommendation and every enrollment belonged to the licensed agent, in the agent's own enrollment system. The automation never recommended a plan, never enrolled anyone, and never ran a benefit conversation. That separation was the design from day one, and in a regulated vertical it is the only version that survives an audit.

He trusted his own close rate, and he was right to. The hard part sat upstream of the close: getting a qualified person onto his calendar on the correct day of a window that shuts. He wanted the record pushed to his enrollment system the instant it booked, with the real outcome recorded after, and he was right about that too.

Five questions tell you fast whether a vendor has worked this vertical. Does the system know your compliance calendar? Can dispositioning a lead ever fire a message? What happens to a do-not-contact flag during a merge? Where do Social Security and Medicare numbers travel? When an appointment books, does everything that should stop actually stop?

If you run a Medicare book and you are weighing intake automation, forget the AI feature list. Five questions actually matter, and how a vendor answers them tells you fast whether they have worked in this vertical.

• Does the system know your compliance calendar, or does it treat a T65 lead like a generic funnel stage?
• Can dispositioning a lead ever fire an automated message, under any condition?
• What actually happens to a do-not-contact flag during a merge?
• Where do Social Security and Medicare numbers travel, and where are they kept out?
• When an appointment books, does everything that should stop actually stop?

A vendor who cannot answer those five in specifics has not run this kind of book. The insurance industry page covers how we think about the whole operating loop, and the full case study shows what this looked like in production.

The system ran live for months: 61 workflows and 116 tags audited and rebuilt, every inbound lead captured and routed digitally the same day. The agency has since moved to a different CRM and the engagement ended with it. We say so because the alternative is an article that quietly implies a client we do not have.

The system ran live for months: 61 workflows and 116 tags audited and rebuilt, every inbound lead captured and routed digitally the same day, and an automated nurture engine running from first contact through enrollment season. The agency has since moved to a different CRM, and the engagement ended with it.

We are telling you that because the alternative is an article that quietly implies a client we do not have. What the work produced is still real, and the compliance vocabulary in this piece came out of that build, not out of a content calendar.