How fast a purchased lead should reach your CRM
The distinction most vendors blur between delivery latency and response latency, why 'real time' alone means nothing, and the timestamp test a buyer can run before taking anyone's word for it.
As fast as the route allows, and there is no single number to promise, because the route sets the ceiling. A direct push can land a lead in seconds. A polled export, emailed file or spreadsheet cannot, whatever the delivery is called, since each runs on a schedule, not a network round trip.
Delivery latency against response latency
Delivery latency and response latency are different clocks, and vendors get graded on the wrong one. Delivery latency runs from submission to a record landing in your system, which the vendor controls. Response latency runs from that landing to a human dialing, which belongs to the buyer. The study the industry quotes, MIT/InsideSales 2007, times the call decision, not submission.
Source: Oldroyd, MIT/InsideSales lead response management study, MarketingSherpa Demand Generation Summit, 16 October 2007. content.marketingsherpa.comThe delivery routes, and why their latency differs in kind
Four routes carry a lead to a CRM, and each is bounded by something different. A direct push calls your CRM's API the instant a form submits. A polled export waits on a queue checked at an interval, so that interval is its floor. An emailed CSV rides a batch job. A spreadsheet waits on whoever sends it.
| Route | Floor | Latency | "Automated"? |
|---|---|---|---|
| Direct API push | Network | Seconds | Accurately |
| Polled export | Poll interval | Minutes-hours | Hides the wait |
| Emailed CSV | Batch schedule | Hours | Hides the wait |
| Manual spreadsheet | Whoever sends it | Hours-day+ | Rarely, claimed anyway |
The test you can run yourself
The only test that settles a vendor's real speed is one you run yourself. Note your submission time on a test inquiry, then read the timestamp your CRM assigns it. Repeat at different hours, since a batched or polled route can slow further overnight while a direct push does not.
One data point of our own: over 500 deliveries in the last 30 days, our own platform measurement rather than audited, median under one second, 97 of 100 inside ten seconds, describing the push into a client's CRM, not how fast anyone picks up a phone.
Source: VisionXLab platform delivery logs, 500+ deliveries, 30 days to 15 September 2026. First-party, not audited.No independent, audited study benchmarks delivery latency by route across the mortgage lead industry. Vendors report their own numbers, unaudited, or not at all, so the timestamp test outweighs any vendor's figure.
Questions this page answers
On its own, nothing enforceable. "Real time" is a marketing phrase with no fixed threshold behind it, applied equally to a direct push that lands in seconds and to a batch export that runs on a fixed schedule but happens to be automated end to end. The word usually just means no human retyped the record by hand somewhere in the chain, not that it arrived quickly. Ask for the mechanism, push, poll, or batch, and the interval it runs on, instead of accepting the phrase by itself.
Delivery speed is how long it takes a submitted lead to land in your CRM, a step the vendor controls end to end. Response speed is how long it then takes your team to call that lead, a step that depends on staffing, shift coverage and who is at a desk when it arrives. Vendors are frequently judged on response speed despite controlling only delivery speed, and buyers and vendors end up blaming each other for a number neither side fully owns.
Submit a test inquiry through the live form and note your own submission time. Then read the timestamp your CRM assigns that record on arrival, not a timestamp the vendor reports back to you afterward. Run it more than once and across different hours, since a polled or batched route can look fine at midday and fall apart overnight, while a direct push does not know what time it is. The gap between your two timestamps is the real number.
Buying questions rather than research ones are answered on the FAQ, and anything that is not there gets asked on a call.
More in Resources
How many mortgage leads a loan officer needs a month
There is no industry number for this, and the page says so. The arithmetic to work out your own, and the capacity ceiling almost nobody sizes for.
AnswersWhat counts as a bad mortgage lead
The line between a defect you can prove from the record itself and an outcome that only feels like one, and what to capture the moment you find the first kind.
AnswersTCPA consent on a purchased mortgage lead
What a consent record has to name before it is worth anything, and why the liability for the call sits with whoever dials rather than whoever sold the record.
AnswersWhat to look for when buying mortgage leads
Four things to check before you pay: how many other lenders got the same consumer, how fast it lands, whose criteria screened it, and whether a defective lead can be returned at all.
AnswersWhere mortgage leads come from, and what origin predicts
The routes a purchased lead travels before it reaches a loan officer, and why knowing which one it took tells you more about the first call than the price does.