Mortgage progression is the stretch between submitting an application and completion, and the thing clients and introducers mind most during it is silence, not slowness. The fix is a short set of client-facing stages mapped to the lender's milestones, one plain message at each, a scheduled "no change yet" note during long gaps, and a phone call from the adviser whenever the news is bad. This article sets out that routine and builds it on the levelpartner.ai platform, so updates go out on time even when the case handler is buried in other files.
Why clients chase for updates
Ask any case handler what fills their phone between submission and offer, and the answer is the same: "any update?" calls from clients, and a slightly sharper version from estate agents. People search for phrases like "mortgage broker not getting back to me" precisely in this window. Most of those calls come in the gaps between milestones, when nothing visible has happened for a week and the client starts to worry that something has gone wrong.
The view this article takes is that this is a communication design problem, not a staffing one. The lender's process takes the time it takes, and you cannot speed up a valuation by answering the phone faster. What you can control is whether the client knows where the case is, what happens next and roughly when. A client who has that information rarely calls. A client who does not will call every few days, and so will their estate agent.
Map the lender's milestones to stages clients understand
Lender portals track many internal steps. Clients need five to seven they can follow. In the UK, a typical purchase runs like this:
- Application submitted to the lender.
- Valuation booked.
- Valuation completed.
- Underwriting and affordability checks.
- Mortgage offer issued.
- Legal work between the solicitors, through to exchange of contracts.
- Completion, when the funds are released.
In the US the vocabulary differs: application, appraisal ordered and received, conditional approval, conditions cleared, clear to close, and closing. US rules also fix part of the timeline. Under the CFPB's TILA-RESPA integrated disclosure rule, the borrower must receive the Closing Disclosure at least three business days before closing, which is worth naming in your updates so the client is not surprised by the wait.
Remortgages are shorter, with no exchange and often no physical valuation, so give them their own shorter stage list rather than forcing them through the purchase one.
How the platform carries it
Three pieces carry the routine: pipeline stages that mirror the client-facing milestones, a workflow that sends the right message when a case moves, and a stale-case alert for the long quiet stretches.
The platform does not read lender portals. Your case handler checks the portal, as they do now, and moves the opportunity to the matching stage. That single drag is what triggers the update, so the handler's job shrinks from writing and sending messages to keeping the stage accurate. The general logic of stage design is in CRM pipeline stages, and the stages before application are covered in mortgage lead management.
- Go to Opportunities, open Pipelines and add progression stages after Application: Valuation booked, Valuation completed, Underwriting, Offer issued, Legal work and Completed.
- Open Automation, then Workflows, and build a workflow from scratch.
- Add a Pipeline Stage Changed trigger filtered to your residential pipeline.
- Add an If/Else branch on the new stage, with one branch per progression stage.
- In each branch, add a Send SMS and a Send Email action with that stage's message from the case handler.
- In each branch, add an internal notification so the adviser sees the change in the case's timeline.
- Build a second workflow with the Stale Opportunities trigger, filtered to the progression stages and a duration of about a week.
- Give it a short "no change yet" message to the client and a task for the case handler to check the lender portal.
Because any update to the opportunity resets the stale count, a case that moves keeps its normal messages, and only cases that sit still get the "no change yet" note. Test the full route on a dummy case before it goes live, moving it through every stage and checking each message reads correctly.
What each update should say
Every progression message answers four questions in a few lines:
- What just happened: "Your valuation has been booked."
- What happens next: "The surveyor's report goes to the lender, who then completes their checks."
- Roughly when: a range, never a promise. "This usually takes a few working days."
- Whether the client needs to do anything: "Nothing needed from you right now."
The "no change yet" note matters as much as the milestone messages. A line such as "Your application is still with the lender's underwriter. Nothing is needed from you, and we will be in touch as soon as it moves" prevents the calls that come from silence. Send from the case handler by name, and let replies land in the unified inbox against the client's record so whoever answers sees the full thread. For the mechanics of text updates that inform rather than market, see automated SMS messages.
Suppose each case currently generates two inbound "any update?" calls a week across clients and introducers, at about six minutes each. That would be 240 calls and 24 hours of case-handler time every week. If stage-triggered updates and a weekly "no change yet" note halved those calls, the team would have around 12 hours a week back for the files that need attention. These figures are illustrative.
Bad news is always a phone call
Automated updates should only ever carry good or neutral news. When a valuation comes back lower than the purchase price, the underwriter adds a condition, or the lender declines, the adviser phones the client first and the introducer second. Build this into the stage design: a Needs adviser call stage with no client message attached, and an alert to the adviser when a case lands there.
The same rule protects your relationships with estate agents. A partner who hears about a problem from you directly, with a plan, stays a partner. The full approach to introducers, including consent before any update is shared, is in managing mortgage broker referral partners. Only send updates to an introducer where the client has agreed, and keep those updates to where the case is, never why.
Promising dates the brokerage does not control. "Your offer will be with you on Friday" turns a lender delay into your broken promise. Give typical ranges, say what the case is waiting on, and update the moment it moves.
Keeping it accurate
The routine only works if stages reflect reality. Three habits keep it honest:
- Check portals at a fixed time each day and move every case that changed in one pass.
- If a lender asks for something extra, move the case to a waiting stage and send a specific request for that item. Mortgage document collection covers how to ask for one item without resending the whole checklist.
- Review the stale-case alerts every morning. A case that has not moved for two weeks needs a call to the lender, not another note to the client.
In the UK, the FCA's Consumer Duty includes a consumer understanding outcome, which expects firms to communicate in a way that helps customers understand what is happening. Clear, timely progression updates fit that expectation, though your compliance lead decides how your communications meet it.
When not to automate updates
- Complex or sensitive cases, such as a client going through a separation or a case with adverse credit, where every update needs a personal touch.
- Cases where the client has asked for phone contact only. Record the preference and route their updates to a task instead of a message.
- Commercial or bridging cases with bespoke timelines that do not fit standard stages.
Frequently asked questions
How often should a broker update clients during a mortgage application?
At every milestone, and at least weekly during quiet stretches with a short "no change yet" note. Clients worry most in the gaps, so a predictable weekly touch prevents most chasing calls.
Can the platform pull status updates from lender portals?
No. A case handler checks the portal and moves the case to the matching stage, and that stage change triggers the client message. It keeps a person in control of what the client is told.
Should introducers receive the same updates as clients?
Only with the client's consent, and in a shorter form that says where the case is without personal detail. Bad news goes to the introducer by phone, after the client has heard it from the adviser.
What should we do when a case stalls with the lender?
Chase the lender, move the case to a waiting stage, and tell the client plainly what it is waiting on. If the delay will affect a moving date, the adviser should call the client and, with consent, their estate agent.