An AI receptionist for plumbing services should distinguish a routine quote request from a caller who needs a person quickly. It can capture the problem and route the call, but it should not improvise technical instructions or promise that a plumber has been dispatched.
Write the urgent-call process with the person who manages your roster. Test it while someone is available to receive the handoff.
Ask the short questions first
Start with the service location, callback number and a brief description in the caller’s own words. Establish whether the request concerns an existing job. Your approved flow can ask whether a problem is ongoing, but should avoid an extended troubleshooting interview that delays a needed handoff.
For routine work, record the type of service, access arrangements and preferred inspection time. For urgent enquiries, use the business’s defined escalation rules and the current duty contact.
Answering is different from dispatch
A full calendar, an unavailable technician or a property outside your service area can make an immediate visit impossible. The receptionist must say whether it has requested a callback, reserved an assessment slot or actually received an authorised dispatch confirmation.
Do not let “we handle emergencies” become “a plumber will arrive in thirty minutes.” Response commitments need live operational support. If a transfer fails, provide the approved fallback rather than cycling through the same unanswered number.
Keep technical and price promises controlled
Use approved callout terms only when the quoted amount and conditions are current. A callout fee should not be described as the complete repair price. Avoid giving advice about gas, electrical hazards or repairs beyond your approved reception script.
A sample handoff line is: “I’ve recorded the address and your description. I’m trying the duty contact now; a visit is not confirmed until the team accepts the job.”
Rehearse the calls that expose weak routing
Test an after-hours request, a caller outside the area, a change of address and a failed transfer. Check the duty person receives a usable message and that the caller is told the correct status. Review escalation delivery and unsupported promises as carefully as bookings. A technically clear message is valuable only if someone owns the next action.
Keep routine intake and duty calls distinct
- Location and verified callback number first.
- Caller’s description and whether the problem is ongoing.
- Existing job or new request.
- Duty-contact handoff result, including failed attempts.
- The exact status communicated: callback, assessment or authorised dispatch.
Illustrative example: A caller reports an active leak outside normal hours. The assistant records the location and contacts the duty person under the approved flow. If nobody accepts the job, the record must say so; “urgent” is not a dispatch confirmation.
Common questions
Can it promise an arrival window?
Only when an authorised scheduling or dispatch process confirms it. Otherwise describe the next action accurately and avoid converting a preferred time into a commitment.
Should every urgent-sounding call bypass the queue?
Use rules agreed with the duty team and a human escalation path for uncertainty. Do not rely on an automated guess about emotion as the only basis for routing.
To assess this workflow for your business, request a Wattle demonstration using a typical enquiry and a difficult handoff from your own operation.
Sources and further reading
Sources reviewed 27 October 2026.