Speed to lead for mortgage brokers

Ask a broker how quickly their firm responds to a new enquiry and you will usually get an estimate based on the best case: the one that came in while somebody was sitting at a desk with nothing else happening. The real number is dragged down by the enquiry that arrived at 4.55pm on a Friday, the one that landed in an inbox belonging to an adviser on annual leave, and the one that was answered promptly by two people who did not know about each other.

Improving response speed is almost never about wanting it more. It is about fixing the plumbing between the moment an enquiry exists and the moment a human being who can help is dialling.

Trace one enquiry end to end

Take a real enquiry from last week and follow it. Where did it first appear: a web form, a directory notification, a missed call, a WhatsApp message, an introducer's email? What system did it enter? Who was told, and by what mechanism? Was that a push notification on a phone, an email among ninety others, or a row in a report someone reads each morning?

Most firms find one or two joints where the delay lives. Common ones are a form that emails a shared address nobody owns, a portal that requires someone to log in to discover there is anything waiting, an introducer who sends details in the body of a message that gets buried, and a mobile number that rings a phone left on a desk.

Give every arrival route a named owner

The single highest-value change in most brokerages is boring: for each route in, name the person responsible during each part of the working day, and make sure that person is told automatically rather than having to check.

That usually means a duty rota. One adviser or administrator owns new arrivals for a defined block, picks up whatever lands, and either makes the first attempt themselves or hands it to the right person with a note. The block should be short enough that nobody is in back-to-back appointments for the whole of it.

Write down what happens when the duty person is unexpectedly unavailable. Escalation after a set number of minutes to a named second person is enough. Without it, the rota fails silently on exactly the days it matters.

Decide your coverage honestly

Enquiries about mortgages cluster in evenings and at weekends, because that is when people look at property. You do not have to cover those hours, but you should decide deliberately rather than by accident.

The options are limited and each has a cost. Rotate evening cover among advisers. Use an answering service that can take details properly and confirm when you will call. Set an automatic acknowledgement that gives a genuine, specific time rather than a vague promise. Or accept that Saturday morning enquiries get called Monday and make sure the acknowledgement says so, so the person is not left wondering.

An acknowledgement that promises a call within the hour and does not deliver is worse than one that promises Monday and arrives Monday.

Instrument it, then look at the distribution

You cannot manage this from memory. You need two timestamps for every enquiry: when it arrived, and when a human first attempted contact. Most CRMs will hold both if someone decides they matter.

Do not look at the average. Averages hide the cases that cost you money. Sort your last two months of enquiries by response gap and read the slowest twenty individually. There will be a pattern, and it will usually be structural: one lead source that feeds into a channel nobody watches, one day of the week with thin staffing, one adviser whose notifications are switched off.

Fix the pattern rather than exhorting the team to be quicker.

Remove the steps before the call

Once you are watching the number, the improvements are mundane. Cut the fields on your enquiry form to the ones you need to make a useful first call. Have the notification carry the person's name, number, situation and source in the alert itself, so nobody has to open three tabs before dialling. Pre-write nothing about the conversation, but do pre-write the text message that goes out if the call is not answered, so it takes ten seconds rather than five minutes.

If a lender portal, a sourcing tool or a fact-find sits between the enquiry and the call, move it after the call. The first contact does not need any of it.

Know when speed stops being the constraint

Faster response has a ceiling. Once you are reliably making a first attempt within a short window during your working hours, more speed adds little, and the next gain comes from somewhere else: the quality of the first conversation, the number of attempts you make before giving up, or the enquiries you are attracting in the first place.

There is also a floor on courtesy. Calling within seconds of a form submission can feel invasive, and calling at half past nine at night is not diligence. Speed is a service to the client, not a race for its own sake, and the point is to reach them while the question is still live.

Keep the compliance side straight while you speed up

Faster processes have a habit of skipping steps that exist for a reason. Whatever you build, keep the record of where the enquiry came from and what the person agreed to when they submitted it, because that is what supports your basis for contacting them. Keep your initial disclosure obligations intact. And make sure an automated acknowledgement is written to the same standard as any other promotion: it is a communication about a regulated service, so it must be fair, clear and not misleading, and it should not imply an outcome you cannot guarantee.

Speed to lead is a systems problem with a service purpose. Fix the joints, name the owners, watch the slowest cases, and the average takes care of itself.