Why Regional Managers Can't See Which Branches Are Calling

Regional managers can't see which branches are calling because the calling happens where nobody can see it.

It happens on a branch phone. On a sticky note by the register. In a CRM that gets updated when somebody has a spare minute, which is almost never.

What reaches the regional manager is a monthly total and a gut feeling. So the branch that's behind looks fine until the month closes. By then it's a result, not a problem you can fix.

Real visibility needs one thing: every call logged the same day, by branch, in the same chain. Called, reached, interested, transferred, visited, funded. The rest of this article is why that chain almost never exists, and why it's not your people's fault.

A Thursday afternoon with 12 branches

Picture a regional manager with 12 branches. It's Thursday, 4:30 p.m.

The COO asks a simple question. "Which branches called their past customers this week?"

The honest answer is "I think most of them."

She can tell you which branches had a good month last month. She can tell you which managers are strong. She knows which branch has been short a person since spring.

What she can't tell you is what happened on the phones this week. Not with numbers.

So she does what every regional manager does. She calls around. The branch managers say what anyone would say: "We've been working the list." Some of them have. Some of them made twelve calls on Monday and then the week happened.

Nobody is lying. They just don't have a record either.

Where the calling actually lives

Follow one call at one branch and you'll see why the record doesn't exist.

First, the loan officer dials a past customer from the branch phone between two walk-ins. The phone system may keep a log, but it's a list of numbers and durations. It doesn't know who the customer is or what they said.

Then, the customer doesn't answer. The officer writes "called, no answer" on the printed list, or on a sticky note, or nowhere. They mean to try again Friday.

Then, someone answers the next call and says, "Maybe, call me next week." That goes in the officer's head. It might make it into the CRM tonight. It might not.

Finally, at the end of the month, a loan funds. Was it from the call list? From a walk-in? From a mailer? Nobody can say for sure, so it gets counted as a loan.

That's one branch on one day. Multiply by 12 branches and 20 working days.

Now you know why the monthly report only shows totals. The details were never written down in a way that could be added up.

Why "log it in the CRM" doesn't fix it

You're probably thinking: we already told everyone to log their calls. We have a CRM for exactly this.

Here's the problem. Logging is the first thing a busy branch drops.

When there's a customer at the counter and the phone is ringing, nobody finishes the call note. They're doing the right thing. The person in front of them matters more than a field in a system.

So the CRM ends up showing which branches type, not which branches call. The branch with the most logged calls might just have the most patient loan officer. The branch with the fewest might be the busiest and best-run branch you have.

There's a second problem. Even the branches that do log don't log the same way. One writes "LM." One writes "left message." One picks "Attempted" from a dropdown. One picks "Contacted" for the same thing. When you add those up across 12 branches, you're adding apples to sticky notes.

This isn't new, and it isn't unique to lending. When Harvard Business Review researchers studied how companies handle incoming leads back in 2011, their headline finding was that most companies weren't responding nearly fast enough. Think about what that means from the inside. If nobody records when a call happened, nobody can see that it happened late, or that it never happened at all.

If you want the longer version of why follow-up comes apart once you have more than a handful of locations, read why follow-up breaks down at multi-branch lenders.

The behind branch is usually the busy one

Here's the part most people get backwards.

When a branch falls behind on calling, the first instinct is to assume the team isn't trying. Usually it's the opposite.

The branch that stops calling is often the one with the most walk-ins, the most payments, the heaviest collections list. Calling past customers is the one task on their plate that nobody is standing in front of them waiting for. So it slides. First a day, then a week.

We wrote about this in why branch staff never get to the call list. It's capacity and process, not effort.

And that's exactly why a monthly total hides it. A busy branch still funds loans. Its number looks fine. What you can't see is the list of past customers it didn't call, the ones who might have come back.

What it costs while nobody can see it

The cost doesn't show up as a line on a report. That's the problem.

Every week a branch doesn't call, its list gets a little older. The borrower who paid off last month is warmer than the one who paid off last spring. A month of silence moves everyone on that list one step further from coming back.

Meanwhile, other lenders are not waiting. The FTC explains that creditors can ask a credit bureau for a list of people who meet their requirements and send them prescreened offers. Your past customer can be on that list. They may hear from a lender they've never met before they hear from the branch that already knows them.

And past customers are the ones worth keeping. A 2014 Harvard Business Review piece put acquiring a new customer at five to 25 times the cost of keeping an existing one. Your past borrowers are the existing ones.

So the question isn't whether the behind branch is losing something. It's how long before anyone notices.

What visibility actually needs

You don't need a dashboard with 40 charts. You need three things.

Every call logged the same day. Not at the end of the week. Not when someone remembers. If it happened on Tuesday, it's in the record on Tuesday. Otherwise you're always looking at last week.

By branch. One row per branch. A good network total can hide one branch that did almost nothing, and that branch is the one you need to see.

In the same chain for every branch. Every call goes through the same steps, with the same names:

When every branch uses the same six steps, you can finally compare them. You can see that one branch is calling plenty but nobody picks up, which is a list problem. You can see another reaches people but transfers nobody, which is a handoff problem. You can see a third that simply stopped calling on Wednesday.

Each of those needs a different fix. A monthly total gives you none of them.

The piece that holds the chain together is one ID per customer that follows them from the first call to the funded loan. Without it, "funded" is just a number that happened to occur in the same month. We go deeper on the weekly board, the ratio to watch and that ID in branch-level reporting for lenders.

Why this can't depend on the branch

Here's the uncomfortable conclusion.

If the record depends on branch staff typing it in, it will always have holes. Not because they're careless. Because they're busy, and the record is the first thing to go.

So the logging has to happen as a side effect of the call itself. The call is placed, and the outcome is written down automatically, with the same words, on the same day, under the right branch.

That's a process decision before it's a technology decision. Some lenders get close with a strict script and a disciplined team. Others take the dialing off the branch entirely and let the branch pick up only when someone is interested.

For what it's worth, that second route is how Sunset Finance runs its past-customer calling today, across 28 branches: every call written down, and a report by branch.

Every week it stays invisible

Right now, one of your branches is probably behind on calling. You don't know which one. Neither does your regional manager.

You'll find out when the month closes. By then, its list is a month older and some of those customers have heard from someone else.

The fix starts with a question you can ask on Monday: can we see, by branch, who was called last week and what happened? If the answer is "not really," that's the gap.

If you want to see what a same-day, by-branch record looks like for one branch, leave your number. Our AI calls you in minutes, and you hear what your borrowers would hear.