Why Follow-Up Breaks Down at Multi-Branch Lenders

Follow-up at a multi-branch lender almost never breaks in one place. It breaks at the handoffs.

The lead lands in a CRM nobody is watching in real time. It gets assigned by territory, not to whoever can call right now. The first call happens. The second one doesn't. Nobody owns the lead that didn't answer. And the branch and corporate are looking at two different pictures of the same week.

None of that is lazy staff. It's capacity and process. Which is good news, because process can be fixed.

You're probably thinking your team does follow up. They do. The question is what happens to the leads that fall between the steps.

It breaks between steps, not inside them

Walk one lead through a normal week.

It's Tuesday, 10:40 a.m. An online application comes in. It lands in the CRM, tagged to the branch closest to the applicant's ZIP code.

At that branch, someone is at the counter making a payment. Someone else is asking about a renewal. The manager is working collections. Nobody opens the queue until after lunch.

At 2:30 the loan officer calls. Voicemail. She leaves a message and marks "attempted."

Wednesday the branch is short one person. Thursday there are new applications on top of the old ones. The Tuesday lead is now on page two.

Friday, a regional manager asks how applications are converting. Corporate sees a number in a report. The branch sees a queue. Neither can say what happened to the Tuesday applicant.

Look closely and every person did their job. The lead still got lost. It got lost between the jobs.

The lead lands where nobody is looking

Most CRMs are built to store leads, not to announce them. A new record doesn't ring a bell at the branch. It sits in a list that someone checks when they get a minute.

At a branch, "when they get a minute" is the problem. The customer in front of the counter will always come first, and honestly they should.

So the first handoff, from the form to a human, depends on someone remembering to look. That's why "we call applications the same day" often means hours later. We wrote about why those hours matter in how fast a lender should call a new applicant.

It's assigned by territory, not by who can call now

Routing by territory makes sense for the loan. The borrower should end up at the branch they'll walk into.

It makes less sense for the first call. The branch that owns the ZIP code might be the busiest one in the region that morning. Another person could call in two minutes. The lead waits for the territory anyway.

There's some research on this, with caveats. In 2007, James Oldroyd, then at MIT, and the sales software company InsideSales.com published a survey of 495 companies about how they handle web leads. Handing leads to the first available rep was linked to higher qualification rates. Handing them out by geography or territory was linked to lower ones, though that result fell just short of their bar for statistical significance.

Take it for what it is. It's self-reported, it's correlation, it's across many industries, and it was co-authored by a company that sold calling software. But it matches what you can see in any branch network: the lead waits for the right person when it could have gone to the available one.

The fix isn't to drop territory. It's to separate the first call from the branch assignment. Whoever can call now makes the first contact. The interested borrower still lands at their own branch.

The first call happens. The second one doesn't.

Almost every lender makes the first attempt. Far fewer make the second, third and fourth on a schedule.

It's not because anyone decided to stop. It's because nobody decided when to try again, or who does it. The voicemail gets marked "attempted," and "attempted" looks like progress in a report.

That's the lead nobody owns: the one that didn't answer.

The same 2007 survey found something telling here. Companies that didn't know or didn't measure how many attempts their reps should make before giving up reported lower qualification rates than the companies that did. The same was true for companies that didn't know how long it took to reach a lead the first time. The authors couldn't say that measuring caused the better results. But not knowing went with worse ones.

Ask your team a simple question: "How many times do we call an applicant who doesn't answer, over how many days, and who makes those calls?" If you get three different answers, you've found the gap.

The same thing happens after a good call. Someone is interested, and then the next step belongs to nobody. We walk through that stretch in what happens after the AI call.

The branch and corporate see different pictures

The branch sees today's queue and today's walk-ins. Corporate sees last week's totals in a report. Neither sees the path of a single lead.

So when a region falls behind, the conversation turns into opinions. Corporate thinks the branch isn't calling. The branch thinks corporate is sending bad leads. Both might be partly right, and nobody can prove it.

What's missing is a shared view by branch: how many leads came in, how many got a first call, how fast, how many were reached, how many got a second attempt, and how many are still sitting. We covered what that weekly view should include in branch-level reporting for lenders, and why regional managers need it in the branch you can't see.

Fix ownership and process before any tool

It's tempting to buy something. A new CRM view, a dialer, an AI agent. Any of them can help. None of them can decide who owns a lead.

Our Academy module on human handoff makes the case that the thing you're really building is consistency. People are great at the conversations that need trust. They're not great at doing the same repetitive step, the same way, every day, while the counter is full. That's not a character flaw. It's what a busy branch looks like.

So start on paper.

First, name an owner for every step. Not a person, a role. Who makes the first call? Who makes the second? Who owns the no-answer after day three? Who owns an interested borrower until someone at the branch picks up?

Then, write the rules. How fast the first call goes out. How many attempts, over how many days, at what times. When a lead gets closed out. When a problem gets escalated, and to whom. The person who owns a queue should know they own it and how fast they're expected to act.

Then, make the handoff carry the story. When a lead moves from one person to another, the next person should see who it is, why they came in and what was already said. A borrower who has to repeat everything to the branch has a worse experience than if nobody had called.

Finally, measure each handoff on its own. Not just "applications in, loans out." Time to first call. Second attempts made. No-answers still open. When the total looks bad, you'll know which step broke.

Once that's written down, the repetitive steps are exactly what software does well: the first call within minutes, the fourth attempt on Thursday, the log entry every single time. The judgment, the trust and the loan stay with your branch.

Every week the handoffs stay unowned

Your applicants are told to shop around. The Consumer Financial Protection Bureau's page on personal installment loans advises borrowers to compare offers from multiple lenders before committing. So the applicant nobody called back a second time didn't stop looking. They just stopped hearing from you.

Every week the process stays the same, the gaps fill with the same kind of lead: the one that didn't answer once and never heard from you again.

If you want to hear what a well-run first call sounds like, the AI will call you. Leave your number and we'll set up time with our team.