Under a sink at 2pm.
A flooded kitchen calls at 2:05. Answered.
An AI receptionist for plumbers: answers every call, sorts the burst pipe from the dripping tap, and books both into your diary properly.
Emergencies sorted from drips.
A flood gets your emergency process: out-of-hours rate quoted, you alerted immediately. A weekend tap gets booked for Tuesday. Your rules, applied on every call.
Every job captured.
Address, access, what’s leaking, photos requested by text if you want them. Into the calendar and your job list, not a soggy notepad.
Follow-ups that happen.
Quotes chased, bathroom-refit enquiries nudged, no-answers called back. The revenue that leaks away while you’re mid-job stops leaking.
We learn how you take work: what counts as an emergency, your rates, your patch, what you won’t touch. Then we build the receptionist around it, test it on real calls, and switch it on. Same build we did for an electrician in 48 hours, tuned to plumbing work.
We build these fast and publish the honest version: our electrician build went live in 48 hours and we wrote up everything that broke on the way.
Asked before booking. Answered straight.
A flooded house can’t talk to a robot.
A flooded house can’t talk to voicemail either, and that’s the current alternative. It answers instantly, quotes your emergency rate, and gets you on the phone or on the way. The caller gets action, not a beep.
Every job is different. It can’t price plumbing.
It doesn’t price what you haven’t told it. It quotes your call-out and your hourly like you would, and books an assessment for anything bigger. The moment it’s unsure, it says so and hands over.
My diary is already chaos.
That’s the point. It books into the calendar you already use with the travel buffers you set. If the diary itself is the mess, we fix that as part of the build.