Before adding another lead source, check what happens to the enquiries already coming in. Here’s a practical process for getting each request to a clear next action.
The practical starting point
To improve plumbing enquiry follow-up, give every open request a status, an owner and a next action. Keep an acknowledgement separate from a confirmed callback or booking. Automate a step only when you know what should happen if it fails.
Find the gap between enquiry and next action
“We need more leads” and “we keep losing track of enquiries” lead to different projects. Before buying another tool, review a manageable sample of recent requests across your website, email and phone messages. Keep customer details inside your authorised systems.
For each request, note when it arrived, when someone first responded, who owned it and what happened next. Include unanswered requests and jobs you declined. Looking only at booked jobs hides the handovers that failed.
Use separate labels for a new enquiry, an issued quote and an existing booked job. A reminder appropriate for an unanswered quote may be confusing to someone still waiting for their first callback.
Build a small handover record
You can start with fields in your existing job system or a shared register. The aim is to make the next action obvious, without creating another place for the same information to go stale.
| Field | What to record |
|---|---|
| Original request | A link to the message or authorised record, preserving the customer’s own description |
| Job context | Work requested, suburb and missing details; collect only what is needed for this step |
| Contact and timing | Preferred contact method and requested callback time, clearly marked unconfirmed |
| Status | New, waiting for details, assigned, contacted, quote issued or closed |
| Owner and next action | A named team member or staffed queue, with a review time the team can actually meet |
| Outcome | Booked, quoted, declined, no response or duplicate, with a short useful reason |
For a missed call, begin with the information the phone system actually captured. Do not treat a number as a complete job brief or assume a return call has happened because a notification was sent.
Write the response rules before the messages
Decide who covers the inbox during business hours, what happens outside those hours and who sees requests that remain unassigned. Set the review interval to your real staffing. An automatic acknowledgement can confirm receipt; it should not suggest a person has reviewed the job.
Here is a starting template for a routine request when the suburb is missing. Replace the brackets before use and check that the wording matches your process:
Thanks for contacting [business]. We’ve received your request about [work requested]. Which suburb is the job in, and what’s the best number to reach you on? Our team will review the details before confirming the next step.
For a customer asking for a price or a specific visit time, carry that request into the handover. Leave it unconfirmed until the authorised person or booking system has checked it. Route urgent or unclear messages according to an agreed escalation process; a routine follow-up queue is not emergency dispatch.
Automate one step with a visible fallback
Start with an action whose result the office can inspect: creating a draft handover from a website enquiry, for example. Fixed form fields and routing rules may be enough. AI can help interpret free-text descriptions, but its summary should remain traceable to the original message.
Before connecting systems, answer these questions:
- Which record is the source of truth if a customer changes their request?
- How will the workflow recognise a repeated submission or retry?
- Who sees a failed transfer, and where can they recover the original enquiry?
- What stops follow-up after a reply, closure or request not to be contacted again?
- What happens when the assigned person is away?
If the problem starts after a quote is issued, review your job software’s existing functionality. Our ServiceM8 guide covers native quote reminders and their stop conditions in more detail.
Test the handover before relying on it
Use fictional enquiries to try each branch before any automated customer contact. Check the destination record and the office’s next action, rather than accepting “the automation ran” as proof.
- A complete routine request: it reaches the right queue once, with its original context.
- A missing suburb: the workflow asks for the detail or flags it, without guessing.
- A repeated request: the agreed duplicate rule prevents competing follow-ups.
- A changed or closed enquiry: an old reminder does not restart the conversation.
- A disconnected tool: the failure is visible, recoverable and assigned to someone.
Our interactive plumbing handover example shows how missing information and unconfirmed availability change the next action.
Measure whether the office has less chasing to do
For a defined review period, compare the share of enquiries with an owner, time to first human response, unassigned requests at the end of the day and manual corrections. Keep response time separate from automatic acknowledgements.
Track bookings or accepted quotes as later outcomes, using the same enquiry records. A faster response alone does not establish that the workflow caused more sales. If the team spends longer correcting summaries than it previously spent writing them, narrow the scope or fix the intake first.
When you are ready to scope a connection, our AI implementation for plumbing businesses page explains the approach and the details to bring.
Practical thinking on AI, automation and the work behind a business.
