Most operators run lead distribution in one vendor and call tracking in another, with two sets of buyers, filters, caps, and schedules that drift apart. Lead Router treats a call as a lead that rings: one contract engine evaluates both, using the same filters, caps, and schedule windows to pick the buyer. These three pages cover each surface in depth.
Three Surfaces
Every page below describes the same routing engine from a different entry point — a submitted form, a tracked number, or a ringing call.
The form-lead side: ping-post auctions, waterfall routing, exclusive and multisell modes, cross-partner dedup, atomic caps, and real-time parallel contract evaluation.
The attribution side of calls: dynamic number insertion, tracking-number pools, IVR, recording, real-time bidding and ping-tree routing, and pay-per-call billing.
Where an inbound call goes: priority, weight, geography, time-of-day windows, caps, and fallback — the same rules that route a form lead.
Go Deeper
The mechanics live on the feature pages; the business shapes live on the use-case and industry pages.
Ping-post, waterfall, dedup, caps, the API, AI, messaging, and reporting in detail.
Lead generators, affiliate networks, pay-per-call networks, and call centers.
Insurance, mortgage, solar, legal, and healthcare routing specifics.
Lead Router against Ringba, Phonexa, LeadConduit, and four more platforms.
One Platform
One buyer record, one set of filters, one cap counter, one set of reports — whether the lead arrived through a form or a phone number.
No feature tiers — metered usage billed as you go.