A 3-Day Auto-Repool Rule for Mortgage Lead Routing: Sub-Accounts and Readiness Scores
By Alex Regueiro · October 25, 2026 · 5 min read
On a team with several loan officers, a lead that sits untouched with one person is a lead nobody else is working. A mortgage branch leader building a multi-loan-officer team needed a rule that moves stalled leads along automatically, without a manager checking every inbox.
60-second check
Take the 2-minute AI readiness survey →
Talk it through
Book a call with the Reshape team →
This is the architecture we mapped on a working call, before the build. The decisions are concrete even though nothing was live yet, and they are the ones a growing team of loan officers has to make before it scales.
The situation
The branch leader runs a team of loan officers and wanted lead routing and follow-up discipline built into the CRM. The risk with any shared lead flow is that responsibility blurs. A lead lands with one loan officer, that person gets busy, and there is no rule that says when the lead should go to someone else.
What we mapped
We laid out the full CRM architecture in one pass.
- Loan officer readiness scores, which sit in the design next to the sub-account strategy.
- A sub-account strategy, which decides how the team's work is organized inside GoHighLevel.
- Pipeline stages, so every lead sits in a defined position.
- Re-pooling service levels, which are the time limits for moving a lead back to a shared pool.
- Integration triggers, which are the events that start each automation.
What we built, and what is still to build
The central rule is a 3-day auto-repool. After a three-day window, an automation moves the lead into a shared re-pool hotlist pipeline. The name of that shared pipeline was still to be decided.
The build list from the call was specific. We stand up the sub-accounts. We build the 3-day auto-repool automation and point it at the shared hotlist pipeline. Each loan officer supplies a personal application link, and the automations send that link, so a message always carries the right person's link.
The shared hotlist has a second purpose. It gives a new loan officer something to work on the first day, a day-one win, so onboarding does not start with an empty pipeline.
What changed
The architecture was agreed and the build was still pending, so no results exist yet. What changed is that the questions that usually cause friction on a lending team now have answers on paper: when a lead leaves one person, where it goes, who sees it next, and what link goes out in the message.
Write your own repool rule
You can draft a rule like this in an hour. Decide what counts as worked, such as a call, a text or a stage change. Pick the time limit that means a lead has stalled. Name the shared place a stalled lead goes, and decide who is allowed to claim from it.
Then write the rule where everyone can see it, and let the automation enforce it so no manager has to. A rule that depends on someone noticing is the same as no rule. After the first few weeks, look at how many leads reached the shared pool and how quickly someone claimed them. If leads sit in the pool, the time limit or the claiming rule needs another look.
Frequently asked questions
What is a lead re-pool in a mortgage CRM?
It is a rule that takes a lead back from the loan officer who holds it and puts it into a shared pool after a set window. In this design the window is three days and the pool is a shared hotlist pipeline.
Why give each loan officer a personal application link?
The automations send the link in their messages, so each message carries the link of the loan officer it comes from, with no one editing messages by hand.
What does a sub-account strategy decide?
It decides how work is organized inside GoHighLevel, so contacts, pipelines and automations have a defined home. We mapped the strategy before building so the build follows a plan.
How does a shared hotlist help a new loan officer?
It gives a new loan officer something to work on from the first day. The goal in this design was a day-one win for each loan officer during onboarding.
If leads on your team stall with one person, book a 30-minute AI follow-up and reporting audit. We help you write the repool rule, the stages and the automation triggers before anything is built.