Insurance lead routing has hard constraints: TCPA one-to-one consent, state licensure, multi-carrier distribution, and time-of-day calling rules. Lead Router handles all of them on one contract-based engine, built for auto, home, life, health, and Medicare operators.
Sub-100ms
Routing decision
One-to-one
Consent model
Per contract
State filtering
BAA on request
Health operations
The Constraints
Routing an insurance lead is not the same as routing a solar lead or a home-services lead. The rules that apply are specific, written, and enforced by regulators and class-action lawyers.
TCPA (47 U.S.C. § 227). Statutory damages run $500 to $1,500 per violation, per contact. Consent has to be prior, express, written, and traceable back to a specific consumer action with specific disclosure language.
FCC 23-107 one-to-one consent. The consumer has to agree to be contacted by each specific seller by name. A lead sold to four carriers needs four distinct consent capture events, each tied to that carrier. Generic "our partners" checkboxes no longer stand up.
State licensure. Carriers are licensed per state. A Florida lead cannot go to a carrier that does not hold a Florida resident-line license. The routing system filters by licensed state before the buyer is asked to bid.
Multi-carrier distribution. Auto and home run multisell (three to five carriers per lead). Life and final expense run exclusive. Medicare runs hybrid. The engine has to handle all three models with accurate per-sale billing.
Age, health, and time-of-day. Life and Medicare need age-band filtering. All phone outreach must respect the TCPA 8am to 9pm local window based on consumer zip. Medicare and health leads are PHI-adjacent, which pulls HIPAA into scope.
How Lead Router Solves It
Each capability maps back to a specific insurance-industry constraint. Nothing is generic.
Every lead stores consent language, timestamp, IP, user agent, campaign, and the specific buyer name the consumer agreed to be contacted by. A TCPA demand letter can be answered with the exact consent payload in minutes. Architected for FCC 23-107 one-to-one.
Each contract carries an allowed-states list and optional zip allow-list. A carrier licensed in 32 states only receives leads from those 32 states. The filter runs before the buyer is asked to bid, so unlicensed-state leads never reach the carrier.
Offers define one winner (exclusive), multiple winners up to a cap (multisell), or a primary plus backups (hybrid). Distribution rules: price, priority, weight, round-robin. Same ruleset across auto, home, life, health, and Medicare.
Every contract can set a daily, weekly, or monthly cap on lead count or spend. Caps evaluate in-flight on every routing decision. Carriers pacing out of budget get skipped and the next eligible buyer takes the sale. No oversell, no manual 3pm throttling.
Contract schedules are enforced per buyer based on the consumer time zone (resolved from state and zip). Calls and live transfers are blocked outside the 8am to 9pm local window defined by TCPA. Holiday and day-of-week rules are configurable per contract.
Lead Router is architected for HIPAA: AES-256-GCM encryption at rest, pseudo-ID separation for PII, audit logging on every PHI access. HIPAA audit is in progress. BAA is available on request before a Medicare or health contract goes live.
Coverage
The same engine powers every insurance product line. Filters, caps, and schedules change per contract, not per platform.
Integration
Every carrier has its own endpoint spec. Lead Router meets them where they are.
Lead Router POSTs leads to carrier APIs over HTTP. Standard JSON and XML payloads are supported out of the box. Per-buyer field-mapping lets you rename or reformat fields without touching ingest. Common targets include Progressive Marketplace, GEICO lead APIs, direct carrier endpoints on Salesforce and HubSpot, and NAIC-compliant lead formats.
TrustedForm and Jornaya. Cert URLs are accepted as custom fields at submission and forwarded to the buyer in the outbound POST. The buyer pulls the cert independently.
DNC scrubbing. Integration points at intake run the consumer phone through a DNC service before the lead is accepted. Rejected leads are logged with the scrub result.
Posting log. Every POST to a carrier is recorded with request, response, HTTP status, latency, and error body. Attribution (campaign, partner, offer, contract, buyer) rides on every lead and sale for end-of-month reconciliation.
Frequently Asked
The questions insurance operators ask during vendor review.
Does Lead Router handle TCPA one-to-one consent?
Yes. Architected for FCC 23-107. Consent metadata (timestamp, IP, user agent, campaign, specific buyer name, consent language) is captured per buyer at form submission and stored with the lead record.
Can Lead Router filter insurance leads by licensed state?
Yes. Every contract carries its own state allow-list and zip allow-list. A carrier licensed in 32 states only receives leads from those 32 states. The filter runs before the buyer is asked to bid.
Does Lead Router support Medicare and health leads with HIPAA architecture?
Architected for HIPAA: AES-256-GCM encryption at rest, pseudo-ID separation for PII, audit logging on every PHI access. HIPAA audit is in progress. BAA is available on request for Medicare, final expense, and health operations.
Can I route auto insurance leads to multiple carriers?
Yes. Offers support exclusive (one winner), multisell (N buyers up to a cap), and hybrid (primary plus backups). Distribution rule: price, priority, weight, or round-robin. One engine across auto, home, life, and health.
Does Lead Router integrate with TrustedForm?
Yes. TrustedForm cert URLs are accepted as custom fields at submission and stored with the lead. The cert URL is forwarded to the buyer in the posting payload so the buyer can pull the cert independently.
Built for Insurance
Consent, licensure, caps, carrier distribution, calling windows. All on one platform. Start a trial or talk to a human about your specific carrier mix.
No credit card required. All features included from day one.