The 1:1 consent shift
Consent now has to name the specific company that will contact the consumer, captured clearly at submission, not buried in a long partner list. So the buyer a lead can go to is determined partly by who the consumer actually consented to.
How I build compliant Medicare flows
- Per-buyer 1:1 consent capture at the form, with TrustedForm + Jornaya proof
- Routing logic that only sends a lead to a buyer the consumer consented to
- Handling AEP volume spikes without dropping or mis-routing leads
On the platform I built, verticals like Medicare run as their own flow, with vertical-specific forms, TCPA content, and consent (TrustedForm and Jornaya) captured per lead and preserved through to the buyer.
Concretely, the Medicare flow captures consent as a signed Scope of Appointment. The consumer picks the plan types they want to discuss, answers the healthcare-decision questions, and signs, and the TCPA disclosure at the signature step is recorded with a Jornaya LeadiD and a TrustedForm certificate. Each lead ends up with its own consent record, the disclosure language it agreed to, the certificate, and the token, not a blanket opt-in.
On delivery, each Medicare buyer integration is scoped to a specific carrier or brand, and every lead carries the Scope of Appointment and TCPA proof that authorizes the contact. Before a lead is sold, a pre-ping duplicate check runs against the buyer's platform on phone and email, and a lead that isn't fresh is suppressed. A fresh lead is pinged with its consent attached, the TrustedForm certificate id, the Jornaya LeadiD, and the consent language all ride in the ping, the buyer bids, and full data is posted to the winning buyer using that ping's id.
FAQ
- Can you distribute Medicare leads with 1:1 consent?
- Yes. Per-buyer consent is captured and enforced at routing time.
- How do you stay compliant routing to multiple buyers?
- Each lead only routes to a buyer the consumer specifically consented to, with TrustedForm/Jornaya proof attached.