Plumbing Leads Die Before the Quote

Plumbing and heating leads rarely die because you were too expensive. They die because the conversation never got far enough to talk about price.

Slow reply. Vague first message. Three rounds of "can you send the postcode again?" while the customer is also messaging two other firms. By the time your office has a clear picture of the job, someone else has already offered a slot.

That is not a marketing problem. It is an operations problem dressed up as bad luck.

The first reply sets the whole job up

When a homeowner gets in touch — no hot water, a leak under the kitchen sink, a boiler showing a fault code they photographed badly — they are not looking for warmth. They are looking for competence.

The firms that win urgent work sound like they have done this before. They confirm what matters, ask one sensible next question, and make it obvious what happens next.

Your office probably already knows what to ask. The hard part is asking it consistently at 7:30pm on a Friday, when the person who knows the difference between a pressurisation fault and a pump failure is on another job.

A useful first exchange covers four things:

• What is actually wrong (in the customer's words — you can translate later)
• Whether it is urgent or can wait
• Where the property is
• Whether this is a repair, a replacement, or something new

That is enough to route the job, rough out a quote, or tell the customer honestly that they need to isolate the water and you will call in the morning. What you cannot afford is starting from zero every time someone fills in a contact form.

Let software handle the repetitive questions

There is a version of "AI for trades" that is mostly hype — chatbots that sound clever and know nothing about your patch, your pricing, or when you stop taking emergency call-outs.

The useful version is narrower. Something that handles the opening moves of the conversation: acknowledge the enquiry, ask the questions your team would ask, capture photos and addresses, and hand a complete thread to a human when it is time to book.

That is especially valuable when the customer does not speak "boiler." They know the radiators are cold and the pressure gauge looks wrong. A good assistant does not need to diagnose from that — it needs to ask the next practical question without making the customer feel like they failed a test.

Sunday evening is when heating jobs are awarded

Boiler failures do not respect office hours. Neither do burst pipes.

On a cold Sunday night, homeowners contact several firms. The ones who win are rarely the cheapest. They are the ones who made the customer feel looked after — confirmed it sounds urgent, got the address, explained what will happen next, even if the actual visit is Monday morning.

An auto-reply that says "we are closed until 9am" is honest. It is also a gift to whoever replied with a real next step.

You do not need to book every job at midnight. You do need to stay in the conversation while the customer is still choosing. A first reply that captures urgency, location, and job type keeps you in the running. Silence removes you.

The handoff is where good leads go missing

Qualifying the enquiry is only half of it. The other half is making sure the booked job still makes sense when the engineer arrives.

Too often the details live in three places: a text thread, a line in the diary, and something the customer mentioned that never made it out of someone's head. The engineer turns up expecting a tap washer and meets a concealed leak. The customer thought they booked an afternoon slot. The office thought they said morning.

The fix is boring and effective: one flow from enquiry to confirmed appointment, with the same facts visible to whoever picks up the phone next.

That means capture, qualify, book, confirm — without copying and pasting between tools. When the chain is tight, fewer jobs fall through it. When it is loose, your team compensates with phone calls and that is where margins disappear.

Your website should start conversations, not end them

Most trade sites are digital leaflets. Services listed, phone number prominent, contact form at the bottom. Then silence until someone checks the inbox.

If you are already paying for the site — or getting Google traffic — that is a waste of a perfectly good front door.

A homeowner who lands on your site at 10pm with no heating is not going to ring. They will message, or fill in a form, or click whatever looks like the fastest path to help. If that path is a black hole, they go back to the search results.

A proper booking flow gives them something to do right now and gives your business structured information instead of "boiler broken please help."

What actually improves

Measure this honestly: more enquiries reaching a confirmed appointment, with less chasing in between.

Upstream fixes matter more than almost anything else in a small plumbing or heating firm. Fewer half-formed jobs in the diary. Fewer wrong slots. Fewer customers who said yes and then went quiet because nobody confirmed the date.

When the phones are busy and the vans are out, that upstream work is what breaks first. Software earns its keep if serious enquiries stop dying in the gap between "we'll be in touch" and a slot on the calendar.

Who tends to get the most from this

Not every firm needs the same thing. Kerviqa tends to fit when:

• you are on the tools and miss enquiries while you are under a sink or in a loft
• your office is small and the same person sells, books, and chases
• handoffs between whoever answered the phone and whoever is visiting are where mistakes creep in
• you know you are losing jobs but cannot quite see where in the process

It is not about replacing your office manager. It is about stopping the office from being the bottleneck because every enquiry starts as a blank page.

Try it against real traffic

The only test that matters is your own: run it on your site, with your enquiries, for a few weeks.

Did more conversations end in booked jobs? Did your team spend less time re-asking the basics? If yes, keep it. If not, you have learned something useful about where the real problem is.

If you want to run that properly, apply for a guided beta trial of Kerviqa and see how it handles your actual flow — not a demo script.