Missed calls: catching the ones worth catching, and filtering the rest

A tradesperson with their hands inside a boiler cannot answer the phone, and the caller will try somebody else within a few minutes. That much is uncontroversial, and it is why every article on this subject stops there and recommends answering faster.

The part worth thinking about is that not all of those calls are jobs you want. Some are out of your area, some are work you do not do, some are price-shopping across six firms, and one of them is an emergency that needs a person in the next twenty minutes. Answering all of them equally fast is an improvement. Sorting them is the thing that actually changes a week.

What we'll cover

• Why the call goes unanswered in the first place
• The four kinds of missed call
• The emergency has to come out first
• What a first reply should collect
• Building it with CodeWords
• What a first reply must not say
• Declining well, which is most of the value
• The out-of-hours question
• Following up the ones who went quiet
• Making it survive
• Limits worth knowing about
• What to build first
• Frequently asked questions

Why the call goes unanswered in the first place

Worth separating, because the fixes differ.

Hands busy. Under a sink, in a loft, on a ladder. Unfixable and the largest category.

Driving. Between jobs, which is a meaningful share of the working day.

Already on a call. One line, one person.

Out of hours. Evenings and weekends, when a good share of domestic enquiries are made.

Deliberately. Because answering would cost the job in front of you more than the call is worth.

The last one matters. A tradesperson who answers every call during a job is being paid for one thing and doing another, and the quality cost of that is real. The aim is not to answer everything, it is to lose nothing by not answering.

The four kinds of missed call

An automated reply that treats all of them identically is a modest improvement. One that sorts them is a different business.

The emergency. Water coming through a ceiling, no heating with a baby in the house, a smell of gas. Needs a person now, and needs to be identified in the first exchange.

The real job. Something is broken, they want it fixed, they are in your area. This is the one worth recovering and it is what everybody is imagining.

The wrong fit. Outside your patch, work you do not take, a landlord wanting a certificate you cannot issue. Worth ten seconds and a clean no.

The price check. Ringing round for a number. Some convert, most do not, and treating them like a real job consumes an evening.

Sorting these is the whole exercise. An automated first reply that collects enough to tell them apart is worth more than one that simply apologises for the missed call.

The emergency has to come out first

Before any booking logic, any qualification, any quoting, the system needs one question that pulls the genuine emergency out of the queue.

That means a plainly worded check at the top: is anybody in danger, is there a gas smell, is water actively coming in, is there no heating for somebody vulnerable. If the answer is yes, the automation stops being a booking system and becomes two things: safety instructions where they are appropriate and unambiguous, and an alert to a human, immediately.

Two rules that are not negotiable. Where a gas smell is reported, the advice is to leave the property and call the national gas emergency service, and that advice goes out before anything else. And no automated exchange should ever attempt to assess whether a situation is dangerous. It can ask, escalate, and repeat standard safety guidance. It cannot judge.

Everything else in this article is a commercial convenience. This part is not.

What a first reply should collect

For non-urgent enquiries, the aim is to gather enough that you can triage from a driveway in ninety seconds.

What is wrong, in their words. Do not force it into categories at this stage.

Where. Postcode, which answers the in-or-out-of-area question instantly.

What it is. Make and model for an appliance, boiler and age for heating, fuse board for electrical. Photographs are better than descriptions and customers send them willingly.

How urgent, in their view. Distinguishes tomorrow from next fortnight.

Whether they own the property, which decides who authorises and who pays.

When they can be in. Access is the constraint that decides whether you can help.

That is six short questions, answerable in a couple of minutes on a phone, and it turns a missed call into a job you can price without a site visit.

Building it with CodeWords

CodeWords connects to more than 3,000 integrations, and the connection is made once and reused.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody, the automation builder: the safety check first, then what to collect, which enquiries are declined outright, and what reaches you immediately.
3. Authorize the connections to your calendar, wherever jobs are recorded, and your WhatsApp Business Platform account.
4. Describe the exceptions: anything urgent or unsafe, an existing customer, a landlord or agent, a job you do not take, an area you do not cover.
5. Read every conversation yourself for the first fortnight, because that is where you find out which enquiries the rules are sorting wrongly.

You describe the outcome; Cody builds it, connects it, and deploys it. The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows; details are on the pricing page.

What a first reply must not say

A price. A figure given before seeing the job becomes a quote in the customer's mind, and the conversation at the door is then about why it is more.

A diagnosis. Describing a symptom is not enough to say what is wrong, and a wrong guess sent in writing is hard to walk back.

A time you cannot hold. "Someone can be with you this afternoon" said automatically, when nobody can, is worse than no reply.

Anything implying it is a person. A customer who believes they are talking to you and then finds out otherwise feels handled. Say plainly that it is an automated assistant taking details.

Safety advice beyond the standard guidance. Where something might be dangerous, the answer is the recognised advice and a person, not an improvised one.

Declining well, which is most of the value

A fast, honest no is worth more than a slow maybe, and almost nobody builds it.

Somebody outside your area should know within a minute, ideally with the name of somebody who does cover it. Somebody wanting work you do not take should hear that immediately rather than after two days of silence. Both will remember it, and one of them will recommend you to somebody you can actually help.

Writing down what you decline is an hour's work: areas, trades, property types, jobs below a minimum charge, work you will not take on without seeing it first. That list is the most useful thing in the whole system and it is the part that gets skipped.

The out-of-hours question

Evenings and weekends produce a large share of domestic enquiries, and a business is not obliged to answer them. What it should not do is leave them in silence.

Three positions, all defensible, and the mistake is not choosing one.

Emergency cover, priced accordingly. Say what counts and what it costs, clearly, before anybody calls.

No cover, honestly stated. "We are closed until eight tomorrow, message us and we will come back first thing." Most people are fine with that.

Collecting only. Take the details overnight, respond in the morning, with a clear statement that nothing is being actioned before then.

What fails is implying availability you do not have. A customer who thinks somebody is coming and finds at midnight that nobody is has been treated worse than one told plainly at nine.

Following up the ones who went quiet

A meaningful share of recovered enquiries stall after the first exchange. They sent the details and then nothing.

One follow-up the next day, referencing what they actually said rather than a generic nudge, recovers a share of them. A second a few days later, offering a specific time, recovers a few more. After that it stops, because a third message to somebody who has gone elsewhere is a message to somebody who has gone elsewhere.

Record why they did not proceed whenever they tell you. Price, timing, someone else got there first: that free text is the most honest market research a small trade business will get.

Making it survive

Put the safety check before everything else, and test it deliberately.

Keep the decline list current, since the areas and jobs you take change.

Alert a person immediately on anything urgent, and check that the alert actually arrives.

Never quote or diagnose automatically.

Read a sample of conversations weekly. The rules drift out of date faster than anything else here.

Limits worth knowing about

Speed does not win every job. Some customers were always going with the cheapest of five quotes.

An automated reply cannot assess danger. It can ask, escalate and repeat standard advice.

Some callers will not message back, and for them a returned call is still the process.

Capturing more enquiries does not add capacity. If the diary is full, faster capture produces more people you have to disappoint.

Collecting details is not qualification. The judgement about whether a job is worth taking is still yours.

What to build first

The safety check and the escalation behind it. Before any booking, any qualification, any commercial logic, make sure a genuinely urgent enquiry is identified and reaches a person within minutes. Everything else here can wait a week; that cannot.

Two habits make the difference. Write down what you decline and let the system say no within a minute, because the enquiries you turn away fast cost you nothing and the ones that sit in silence cost you a reputation. And never let anything quote or diagnose on your behalf, since a number sent before you have seen the job is a number you will be arguing about at the door.

Frequently asked questions

Why do tradespeople miss so many calls?

Hands busy, driving, already on a call, out of hours, and sometimes deliberately because answering would cost the job in front of them. The aim is to lose nothing by not answering rather than to answer everything.

Are all missed calls worth recovering?

No. They divide into genuine emergencies, real jobs, poor fits and price checks. Sorting them matters more than answering all of them equally fast.

How should an emergency be handled?

Identified in the first exchange with a plainly worded safety question, escalated to a person immediately, and given the recognised standard advice. Where a gas smell is reported, that means leaving the property and calling the national gas emergency service.

Can an automated assistant judge whether something is dangerous?

No. It can ask, escalate and repeat standard guidance, and it must never assess a situation or improvise safety advice.

What should the first reply collect?

What is wrong in their words, the postcode, what the appliance or system is, how urgent they think it is, whether they own the property, and when they can be in.

What should a first reply never include?

A price, a diagnosis, a time you cannot hold, any implication that it is a person, or safety advice beyond the standard guidance.

How do I turn down work without damaging my reputation?

Within a minute, honestly, and ideally with the name of somebody who does cover it. A fast no is remembered better than a slow maybe.

What should I do about out-of-hours enquiries?

Choose a position and state it: priced emergency cover, no cover honestly stated, or collecting only. The failure is implying availability you do not have.

How many times should an unconverted enquiry be followed up?

Twice. Once the next day referencing what they actually said, once a few days later with a specific time. A third message is going to somebody who has already booked elsewhere.

Does capturing more leads help if I am already busy?

Not much. It produces more people to disappoint. When the constraint is capacity, the useful work is pricing and filtering rather than capture.

Related reading

• Dispatch, routes and arrival windows
• What to know before the van moves
• Emergency and planned work are two businesses