The missed call: where the job is lost before it starts

The boiler has failed. The customer searches, and works down the results. They are not picking the best firm, or the cheapest one: they are picking whoever answers.

Meanwhile you are standing in gloves in front of a dismantled unit. The phone rings in your pocket and you cannot take it. You call back in the evening, and by then someone else has already been out.

This is not disorganisation. It is the nature of the trade: the person doing the work is the same person who would answer the phone.

Why this is hard

The problem is not the callback. It is the timing.

Breakdown work is urgent. With a burst pipe or a flat with no heating, nobody waits three hours for a reply. Two or three calls in, they find someone available.

While working, the phone physically cannot be answered. In a loft, in a service shaft, at a live consumer unit, you do not stop halfway through what you are doing.

At five to ten calls a day, nobody holds in their head who wanted what. In the evening, tired, you try to reconstruct it from the call log — and whatever left no trace is gone.

Not every call is the same. One is an emergency, one is a quote for next week, one dialled the wrong number. Without calling back, you cannot tell which is which.

And the worst part: you do not know what you lost. Someone who leaves no message appears nowhere.

What the system does

It does not answer the call for you. It steps in a few seconds afterwards.

A missed call triggers a message — not generic text, but a question: what is the problem, at which address, how urgent. The customer replies in writing, which in that moment suits them too, because they do not have to make another call.

From the replies the system assembles the enquiry: name, address, the fault, how urgent. If your calendar has a slot, it offers one.

You still accept every job yourself. The system commits to nothing on your behalf, quotes no price, and books no appointment without your approval. It prepares, and puts it in front of you.

Whatever is unclear, it flags rather than guesses. "This caller did not reply" or "the fault was not established" is also a result — at least you know somebody was there.

How it decides

It tries to establish three things: who called, what they want, and how urgent it is.

From the number it knows whether this is an existing customer. If so, it brings up what was done last time and which equipment is installed.

From the reply it extracts the nature of the fault and the address. Anything missing, it asks for — once, not three times.

Urgency it estimates from what the customer wrote. "Water is pouring out" and "I'd like air conditioning next month" are not the same line on your list.

Here precision matters more than completeness. A wrongly flagged emergency makes you abandon a job for nothing — which is worse than the system admitting it cannot tell, and leaving the call to you.

The edge cases you meet daily

The caller does not reply to the message. They may have found someone else, or they may be driving. The enquiry stays open rather than vanishing.

The customer would rather call back than type. That is entirely fine — the system offers writing, it does not insist on it.

An older customer who does not text. That is a real limit and not worth glossing over. There the callback remains, except now you at least know who called and when.

Wrong numbers, cold callers, suppliers. The system filters these out so they do not clutter your list.

The same customer calls four times in an hour. That becomes one enquiry, not four.

Which mistake actually costs money

Not the one you got wrong. The one you never knew happened.

Other mistakes announce themselves: an unhappy customer complains, a wrong invoice surfaces. A missed call is silent. No complaint, no trace, nothing learned — simply no job.

Work it out with your own figures. One unanswered call a day is twenty a month. If one in five of those would have become work, that is four jobs. Multiply by the value of an average job, and you have the cost of not being able to answer the phone.

That number appears in no report, because there was never an invoice behind it.

What changes

• Response time: from hours to seconds — not in picking up, but in the customer knowing they are being dealt with
• Evening admin: a list of prepared enquiries instead of reverse-engineering the call log
• Visibility: how many enquiries actually arrive, and how many become work
• Order of play: urgent cases rise by what they contain, not by when they rang

A realistic expectation: in the first weeks you will correct more enquiries by hand. After a few weeks, as the system learns your returning customers and the typical faults, far less intervention remains.

What implementation needs

A phone number that receives the calls, and access to your calendar if you want it to offer appointments.

More important than either: somewhere for enquiries to accumulate. At many smaller firms that place does not exist today — part of an enquiry is in the phone, part in a message, part on paper in the van. If there is no such place, it has to be created first. That is the opening phase of implementation, and it is not a technology question.

Setup is typically one to two weeks. Most of that time goes not on the system but on deciding what counts as urgent, and what a weekend call should be told.

Where it runs

The system connects to your existing phone number and calendar, and runs in your own EU cloud environment.

Your customers' data — names, addresses, phone numbers, the equipment in their homes — is not used to train a third party's general models. In a trade where you know whose house is empty and when, that is not a small point.

What it doesn't solve

It does not do the work for you. If you are needed in two places at once, the system does not help with that — beyond telling you which one is more urgent.

It does not hold on to a customer who has already found the next firm. Replying within minutes is a good chance, not a guarantee.

And it does not set prices. What you take the job for is a commercial and professional judgement, not data processing.

Common questions

Won't this feel impersonal to the customer?
Experience points the other way: a fast, specific reply reads better than a callback six hours later. The tone stays yours — the system uses what you set.

What if it misunderstands something?
That is why it commits to nothing. Every enquiry becomes a job only with your approval, and a misunderstanding surfaces in your first sentence.

I work alone. Is it worth it for me?
For one person the gain is not time saved but enquiries not lost. At five to ten calls a day, yes. At one or two, probably not.

What happens at weekends and on holiday?
Whatever you set. The system can know when you are not working and reply accordingly — which on its own beats a silent phone.

Do I need a new phone number?
No. It works from calls to your existing number.

If you do not know how many enquiries reach you in a month, that is where to start. For one month, note against every missed call whether you ever found out what they wanted. The number that comes out of that tells you more than any proposal.