A UK mortgage brokerage, rebuilt end to end in GoHighLevel

The situation

Mortgage brokering is a long sale. An enquiry can sit for weeks, sometimes months, between first contact and a lender decision, passing through advisors, admin, document checks, and solicitors. Every handoff is a place where a case goes quiet and nobody notices.

This brokerage had the process in people's heads. Advisors knew what to do next; there was just nothing holding them to it. Four problems came up on the first call, and every one of them cost money:

Nobody could see where a client stood. A client would ring and ask about their case, and answering meant checking an inbox, a spreadsheet, and an advisor's memory.

Appointments were booked but not protected. No structured reminder sequence, so no-shows were common. When someone didn't turn up, there was no process to get them rebooked. That slot was just lost.

Documents were the real bottleneck. Paperwork arrived by email and sat there until an advisor happened to look. Nobody chased. Cases stalled at document collection more than anywhere else in the funnel.

Nothing survived a handover. Onboarding a new team member meant weeks of shadowing, because the process lived in individual heads rather than in a system.

What I found

Before building anything, I mapped the process the team followed, not the one on the website.

The most useful thing that came out of that mapping was where the funnel genuinely broke. They assumed leads were lost early, at first contact. The numbers said otherwise: 67% of leads got contacted, and 61% booked an appointment. But of the leads asked for documents, only about half sent them back. The collapse wasn't at the pitch. It was at paperwork.

That reframed the whole build. Chasing documents automatically wasn't a nice-to-have feature at the end of the list. It was the highest-value thing in the system.

The second finding was structural: remortgage cases don't behave like new purchases. Different timeline, different urgency, different conversation. Running both through one pipeline meant neither set of numbers meant anything.

What I built

An end-to-end system inside GoHighLevel, designed around one rule: every stage tells the person responsible exactly what to do next.

Two pipelines, not one

Separate pipelines for mortgage and remortgage, each mapped to its real client journey. Ten stages on the mortgage side, from first enquiry through admin contact, appointment, document collection, advisor recommendation, solicitor prep, application submission, and lender processing.

Splitting them meant that for the first time, a glance at the board answered the question "where does this client stand?" For the client, for the advisor, for the owner looking at the numbers.

One stage was deliberate: Interested / Not Ready. Mortgage enquiries arrive months before someone can act. This keeps them visible without distorting the reporting.

Lead capture straight from the website

Forms and surveys connected directly to the site, so an enquiry lands in the CRM the moment it's submitted. No re-typing, no copy-paste from an inbox.

On arrival, every lead is tagged, assigned to an advisor, and sent a welcome email and SMS within seconds. A lead-to-admin handover fires next.

A task-based system instead of tribal knowledge

At every stage, the system generates a task for the right person with a clear instruction about what happens next.

Someone who understands the GoHighLevel interface can manage this operation from day one. No shadowing, no "ask Sarah how we usually do this." The next action is on screen.

26-week nurture journey

Mortgage buyers move on their own timeline, not the broker's. A 26-week nurture sequence keeps the brokerage present for the long tail, the enquiries that aren't ready now but will be in four months, without an advisor having to remember to follow up.

Multi-channel communication

Email, SMS, and WhatsApp, all running from the same workflows. WhatsApp gets the fastest replies, especially for document requests.

Appointment protection

Booking is only the start. The system runs the full lifecycle from one unified engine:

• Confirmation on booking
• Reminder sequence before the appointment
• No-show handler — reschedules the slot automatically
• Cancellation handler — routes back into rebooking, not out of the pipeline

Document collection and chasing

The bottleneck, given the most attention.

• Collection — auto-requested at the right stage
• Handler — incoming paperwork routes itself, assigns the owner, notifies admin, moves the opportunity
• Approved and rejected paths — different documents, different conversations
• Chase sequence — runs until the documents arrive

Reporting

Full funnel visibility from first enquiry to application submitted, with stage-by-stage conversion and pipeline value in one view. 376 opportunities in the system: 244 open, 15 won, 111 abandoned.

The hard part

The technically awkward piece wasn't any single workflow. It was time.

A mortgage system runs on business hours, but leads don't. An enquiry arriving at 9pm on a Saturday can't generate a task that lands on an advisor's Saturday evening, and it also can't wait unattended until Monday morning while the client wonders whether anyone read it.

So the system splits the two. Client-facing communication fires immediately, any hour, any day. The welcome email and SMS go out within seconds, which is what keeps first response under a minute. Internal task assignment respects working hours, with a weekend check running before any task is assigned so that work lands on a working day and reaches someone who is there to do it.

The same check sits inside the intake, document, and calendar workflows. Small piece. Big consequence. Without it the whole task-based model falls apart the first weekend. Either tasks pile up unseen, or the team gets notified on their days off and stops trusting the notifications.

Results

• +31% more opportunities compared to the previous 31-day period
• Under 1 minute average first response to a new enquiry
• ~20 hours per week of manual admin removed (client estimate)
• 376 opportunities tracked end to end, versus no central tracking before
• Document collection automated and chased, closing the biggest leak in the funnel
• No-show and cancellation handling now automatic, protecting booked appointments
• A new team member can run the system from day one

Stack

GoHighLevel — Pipelines & Opportunities · Workflow Builder · Calendars · Forms & Surveys · Conversations (Email, SMS, WhatsApp) · Tasks · Dashboards & Reporting