Plumbing, heating, electrical, HVAC: the work happens with both hands busy and the phone in a van. The agent answers, takes the address and the symptom, sorts the emergency from the routine using your rules, and books the slot against the right skill and the right travel window.
The mix is predictable. The timing is not.
No heating, no hot water, a leak, a dead circuit. This caller will ring down a list until somebody answers, and they are not comparing prices. Answering is most of the sale.
A bathroom, a boiler swap, a rewire. Needs scoping rather than pricing, and the useful outcome of the call is a survey booked with the right information captured, not a number invented on the phone.
Services, inspections, maintenance contracts. High volume, low drama, entirely mechanical: find a slot, confirm it the day before, move it when the customer needs to.
This is the industry where the two activities are most physically incompatible.
Nobody takes a call from under a sink or up a ladder, and the customer standing in the kitchen would not thank you for it. So the call goes to voicemail, and a caller with a leak does not leave a voicemail. They ring the next number.
Out-of-hours calls are the highest-value calls of the week and the least likely to be answered. An answering service takes a message that reaches you the next morning, by which point the customer has already paid somebody else the out-of-hours rate.
The value is not that it talks. It is that what it writes down is complete enough to dispatch from.
Address, access, what the equipment is, what it is doing, how long it has been doing it, whether the water or power is off. Addresses and numbers are read back and confirmed on the call, because a van sent to the wrong street costs more than the call did.
You define what counts as an emergency and what happens then: transfer to the on-call number, book the earliest slot, or say plainly when someone can come. The agent applies the rule; it does not form its own opinion about how bad a leak is.
A slot is only real if the right engineer can physically get there. Skills, working areas, job durations and travel buffers are configured before launch, and availability is read from your live diary at the moment of the call.
How the booking works →Every one of these is a place where a confident wrong answer costs you money.
It quotes only from a fixed price list you gave it, and for anything else it books the survey and says why. A number guessed on the phone becomes a number the customer holds you to.
It records the symptom in the customer's own words and passes it on. Telling someone what is wrong with their boiler over the phone is how you arrive with the wrong part and the wrong expectation.
It offers what your diary actually has. Where the honest answer is a window rather than a time, it says a window. Anything involving gas, electrical safety or a suspected leak of something dangerous follows the escalation rule you wrote, immediately.
A job that is not in the system your engineers work from has not been booked.
The job, the address, the symptom, the transcript and the recording go into the system your office already runs. Where a system cannot be read and written programmatically, we tell you during scoping rather than after.
It sits on your existing number. Many trade businesses start with out-of-hours and overflow only, keep answering the calls they can, and widen the scope once they have read a month of transcripts.
What changes between these pages is which calls matter and what the agent has to be stopped from doing.
Reception is already serving the person at the desk. The phone is the patient you never met.
What we would build →The agent who answers first gets the viewing. Everyone else gets a callback nobody returns.
What we would build →Three questions are most of your call volume, and all three have an answer in a system.
What we would build →The service desk is with a customer at the counter. The sales enquiry arrives at nine at night.
What we would build →Every failed delivery is a phone call and a second van. Most of them are an address problem.
What we would build →These six are where inbound call volume is heaviest and the integrations are best understood, not the limit of what the agent handles. If your calls are repetitive and the answers live in a system, the shape of the work is the same.
Every industry page →