A lead came in at 7:42 on a Tuesday night. Purchase, first-time buyer, a town twelve minutes from your office. Your top producer opened it at 8:20 the next morning and left a good voicemail. The borrower called back Thursday to say thanks — their agent had already walked them to somebody, and they were under contract by the weekend.
Nothing went wrong that anyone would put in an email. Nobody misquoted a rate, blew a condition, or dropped a file. You got there second. Second in this business is a free consultation you hand to somebody else's borrower.
The short version
- Track two clocks, not one: arrival to claim, and arrival to the first human attempt. They fail for different reasons and get fixed differently.
- Judge yourself on the tail. The worst ten leads of the month are your reputation; the median is just comfortable.
- Write two SLAs — a business-hours one in minutes, an honest after-hours one. An SLA the team abandons teaches them the wall is decoration.
- Escalation fires on a timer. If it depends on a manager checking a queue, it isn't escalation.
- Speed only buys the first at-bat. The pre-approval letter is what actually claims the borrower.
The race is to the pre-approval letter, not the phone call
Speed to lead sounds like a call-center metric. In mortgage it is about a document.
The first LO to reach the borrower asks the questions, hears the story, and pulls credit. Then they issue the pre-approval letter, and it lands in the agent's file. From that moment, switching lenders isn't a preference — it's a new pull, a new letter, and an awkward conversation the agent doesn't want while trying to get an offer accepted. You're no longer competing on rate. You're competing against inertia you handed somebody else.
The first conversation also sets the terms of comparison. Open with a payment that includes taxes, insurance, and MI, and every later quote gets measured against a real number. Whoever gets there first writes the scoreboard.
And you aren't only racing other lenders. A form fill is the peak of someone's intent. An hour later they're making dinner. By Thursday, answering an unknown number is a chore.
Two clocks, not one
Most branches that say "we respond fast" have never measured it, and most that measured it measured the wrong span. Keep two numbers on every lead.
- Time to claim — arrival to a named human owning it.
- Time to first attempt — arrival to an actual outbound call or personal text.
Three rules keep them honest. The clock starts when the lead hits your system, not when the LO noticed it — the arrival timestamp is the only one the borrower experiences. An autoresponder is not a response; "Thanks, we'll be in touch" stops nobody's shopping. And nights and weekends count, because internet leads arrive exactly when people have time to think about money.
Split that way, the diagnosis is automatic.
Slow claim is a plumbing problem — routing, alerts, coverage. Fast claim with a slow attempt is an accountability problem, and no software fixes it. Blend them into one average and you'll spend a quarter fixing the wrong one.
Judge the tail, not the median
Here is the arithmetic that changes how a manager reads the report. The numbers are illustrative — yours to measure, not mine to hand you.
Say your branch takes 120 internet leads in a month. Median time to first attempt: eleven minutes. That reads beautifully in a Monday meeting. Now sort the same 120 by that span and look at the bottom.
Twenty-eight leads went untouched for more than two hours, most of them overnight. Now put conversion on it. Say the ones you reach inside five minutes take an application one time in eight, and the next-day ones one time in twenty-five. Across twenty-eight tail leads a month that gap is roughly two and a half applications — thirty a year. Run thirty at a 75% pull-through and you funded about twenty-two fewer units than the branch you believed you were running.
None of that is fixed by making fast LOs faster. The tail is a coverage problem, and coverage is a schedule, not a personality.
Write two SLAs, not one heroic one
The classic failure is the heroic SLA: every lead called within five minutes, around the clock. It gets written in a sales meeting, kept for nine days, and quietly buried the first Saturday nobody was on.
An SLA nobody can keep on a Saturday is a decision to lose Saturday leads. You have just made it quietly instead of out loud.
So write two. A business-hours SLA in minutes. And an after-hours SLA that names a moment — "claimed by 8:30 the next morning," or a real on-call rotation if your volume justifies one. A modest promise you keep beats a heroic one you abandon: the abandoned one teaches the team that the wall is decoration. Keep both short enough to recite. If an LO can't state the SLA without looking it up, it isn't an SLA. It's a document.
The duty desk, and the ownership question that kills it
Coverage is a rotation, and the rotation dies on one unanswered question: who owns the loan.
- One name per block. Evenings get split into blocks. Saturday morning is a shift like any other. "The team" is not a name.
- Whoever claims it, owns it. Decide this before you build the rotation. If an LO suspects a lead they grab at 8 p.m. might get reassigned to whoever it "fits better," they won't grab it at 8 p.m. You can't patch that with a spiff — comp plans in this business don't flex file by file. You patch it with a rule, stated once and never bent.
- Assignment is the default; claim is the safety net. Round-robin routing to an LO sitting at a closing table fails through nobody's fault. Anyone on duty should be able to take it.
- On duty means reachable, not chained. Ten minutes to acknowledge is fair on a Tuesday night.
- Publish the misses, not the heroes. One weekly number: leads that hit the bottom rung.
The first ninety seconds, in actual words
Text first if the form gave you a mobile number, then call from that same number:
"Hi [first name] — this is [name] with [branch]. You just asked about a purchase in [town]. I've got a few minutes right now if you want a real payment number. Calling you from this number."
Open the call on the thing they told the form, not on yourself:
"You're looking in [town] around [price]. Is that a house you've already seen, or are you still working out what you can spend?"
Leave a voicemail every time, and keep it under fifteen seconds:
"[First name], [name] at [branch] — you asked about a purchase a few minutes ago. I'm texting you a payment estimate so you have something real to look at. Call me back at [number] anytime."
One discipline underneath all of it: don't lead with a rate. Give a payment with taxes, insurance, and MI in it. The LO who quotes a naked rate first taught that borrower to shop naked rates — and they'll practice the lesson on you.
The plumbing is boring on purpose
- One intake point. Every source — site form, aggregator, agent referral, a past client texting an LO — lands in one queue with an arrival timestamp. Three inboxes and a spreadsheet is not a claim time. It's three arguments about one.
- Context in the notification. Purchase or refi, state, price band, whatever the form captured. Ten seconds of context turns "returning your inquiry" into an opening line.
- Claim is one tap, and exclusive. A name, a timestamp, visible to everyone. That kills the pile-on and the bystander effect in the same move.
- The first attempt is logged next to the claim. This is where tooling earns its keep — in MAVYN, leads sit behind the same login as the pipeline, and MAVIS can draft that first message for the LO to review and send. The draft removes the blank-page delay; the human sending it keeps it human.
- Escalation fires without anyone watching. Unclaimed at the line means the lead goes wide automatically.
- The handoff to follow-up is explicit. Speed buys the first at-bat and nothing more. The next two weeks are a separate discipline with its own cadence and ownership — a mortgage lead follow-up system — and the claim record is where it starts.
Notice what isn't on that list: dialers, scripts, personality. Claim time is a systems number. Branches that win it aren't staffed with faster people; the queue is one place and the clock is public.
Monday morning, pull the last thirty days and write two timestamps next to every lead: when it arrived, and when a human first tried. Don't compute an average. Sort by the gap, take the worst ten, and read them out loud at your sales meeting — nothing moves a room like hearing "this one sat until Thursday." Then write the two SLAs you can keep, decide out loud what happens at the deadline, and put the clock where everyone sees it. You don't need to be the fastest branch in the country by Friday. You need the honest number, and a system that shrinks it while you're busy doing something else.