Emergencies and routine work arrive on the same line
"There's a little water in the basement" and "water is coming through the ceiling" open identically.
Use case · Plumbing
Plumbing calls split hard between genuine emergencies and work that can safely wait until Tuesday. Getting that split wrong in either direction is expensive — one way you wake a technician for a dripping faucet, the other way water runs across a finished floor all night.
What it costs you now
"There's a little water in the basement" and "water is coming through the ceiling" open identically.
Whether the customer can isolate the water changes the entire response, and voicemail never asks.
Emergency rates and replacement jobs cluster in exactly the hours nobody is at the desk.
Rotating the phone through the crew means calls get missed, taken badly, or written on a scrap of drywall.
Crawlspace access, tenant approval, gate codes — discovered on arrival instead of at intake.
By 8 AM the caller has already paid someone else's emergency rate.
On the call
Asked in the same order every time, at any hour, and attached to the job before anyone drives anywhere.
Is water actively running or leaking right now?
The single question that separates emergency from bookable
Can you safely reach and shut off the main supply?
Contains the damage and changes the urgency tier
Is water near any electrical panel, outlet, or fixture?
Converts a plumbing call into a hazard call
Is there sewage entering living space?
Health exposure — escalates regardless of hour
Is the property occupied, tenant-occupied, or vacant?
Decides who can authorize work and grant access
Which fixture or area, and when did it start?
Determines the tech, the parts, and the time on site
Books without you
Never automated
What changes
Bookings are written back into the system you already run, with the full intake and the transcript attached to the job.
Writes into
Other trades