To measure which plumbing enquiries become suitable booked jobs, track each distinct request from first contact to a confirmed arrangement. Record whether the location and work fit your business, whether you could accommodate the request, and what the customer agreed to. A form submission is not a booking, and a booking is not money received.
Useful plumbing lead quality tracking separates marketing relevance, operational capacity and customer acceptance. Combining them into a single lead total hides which part needs attention.
What should count as a plumbing enquiry?
Use a distinct service request as your reporting unit, rather than every call, message or form submission.
Someone might submit a form about a leaking tap, phone to check it arrived and later message about access. Those are separate interactions concerning the same opportunity, not new demand.
Apply these distinctions consistently:
- Repeat contact about the same request: update the existing enquiry.
- Existing customer with a new plumbing need: create a new enquiry, marked as returning business.
- Question about an existing booking or invoice: record it as administration, not new demand.
- Callback about recently completed work: link it to the original job for review rather than automatically count it as a new sale.
- Unrelated solicitation or obvious spam: classify it separately from genuine service requests.
Do not merge everything from the same phone number. A property manager might enquire about distinct jobs at different properties. Confirm the request before deciding whether it is a duplicate.
The broader guide to checking whether form submissions become qualified enquiries explains the qualification boundary. For plumbers, repeated contact and separate properties also need clear counting rules.
Separate suitability, capacity and progress
A label such as “bad lead” tells you little. Use separate fields for suitability and progress, plus a reason when a request stops.
Suitability: is this work you serve?
Assess the request against your actual boundaries:
- Is the property in an area you genuinely cover?
- Is the requested work within the services you offer?
- Is there enough information to understand the request?
Leave incomplete enquiries as suitability unknown until someone checks them. An unanswered callback is not proof of spam. Separately, establish whether the person can arrange access and authorise the next step, or involve whoever can.
Record capacity separately too. An in-area request for a service you offer can be suitable even when you cannot attend when needed. That is a timing or capacity mismatch, not necessarily poor targeting. See the related guide to qualifying emergency plumbing enquiries without promising availability.
Progress: what has actually been agreed?
Choose stages that reflect your process. A practical starting set is:
- Received: the request needs review.
- Clarification pending: essential information or a conversation is outstanding.
- Assessment or quote pending: the next decision depends on a visit or quotation.
- Quote sent: a proposal has been supplied, but not accepted.
- Accepted, scheduling pending: the customer has agreed to proceed, but arrangements remain outstanding.
- Booked: the customer and business have confirmed the agreed service and attendance arrangement.
- Closed without booking: no further action is planned, with a recorded reason.
Suitability remains a separate field, so a suitable request can still be awaiting a quote or closed because of capacity. Not every request must pass through every stage.
Distinguish assessment visit booked from repair work booked. Agreement to inspect a problem does not establish acceptance of a resulting repair quote. If an assessment leads to repair work for the same request, update the record rather than count another acquired enquiry. Preserve booking history, but remove cancellations from the current booked-work total.
Keep a short, usable enquiry record
A shared register may be enough initially. Record:
- A unique enquiry reference and date received.
- Contact details, suburb and a brief description of the request.
- New or returning customer.
- Original contact route and marketing source, where known.
- Suitability, current stage and any closure reason.
- Assigned owner and next action.
- Dates of quotation, acceptance and booking, where applicable.
- Booking type and a reference to the eventual job record.
Ask only for information that changes the next action. An initial form can request a name, contact method, suburb and short description. Do not request alarm codes, passwords or identity documents. Arrange necessary access details later through an appropriate operational process.
A CRM becomes worth considering when ownership, duplicates or handovers become difficult to manage. HighLevel’s guide to opportunities describes potential deals moving through customisable pipeline stages, with information such as source, value and notes. Check the exact configuration and connections in your account. An opportunity value is not evidence of payment.
Connect outcomes to sources without guessing
Keep the original marketing source separate from the channel used for conversation. Someone who arrives through an advert and then phones should not automatically become a new “telephone source” opportunity.
Google’s campaign URL guidance explains how UTM parameters identify referring campaigns in Analytics. Use consistent source, medium and campaign names. These describe campaign traffic, not whether a job was accepted or paid.
Connecting campaign information to individual enquiries requires a checked implementation. Do not assume Analytics, forms, phone records and job records already join together.
Where technical source information is unavailable, ask how the customer heard about you. Keep customer-reported and technically recorded sources distinguishable, and retain unknown rather than guessing. Keep names, addresses and problem descriptions out of campaign tags.
Illustrative example: similar activity, different outcomes
Consider a hypothetical plumber serving selected suburbs.
A homeowner submits a blocked-drain enquiry, then phones about it. The location and service fit, but the business cannot meet the requested attendance time. Record one suitable enquiry, closed because capacity did not match the need. It is neither two leads nor spam.
Another homeowner requests work outside the service area. Record a genuine but unsuitable enquiry, with unsupported area as the reason. A recurring pattern would justify reviewing geographic targeting and coverage wording.
A returning customer requests different work, receives a quote and accepts it. Record a new returning-customer enquiry. Move it to booked when the arrangement is confirmed. Record subsequent completion, invoicing and payment separately through the job and financial records.
These outcomes call for different decisions: address capacity, clarify coverage, or maintain a useful returning-customer relationship.
What should your lead-quality report show?
Group requests by when they first arrived, then follow their outcomes. Do not divide this month’s bookings by this month’s enquiries if the bookings include older requests.
For each source, show distinct genuine requests, suitability decisions, suitable repair bookings, closures and unresolved records. Keep returning business identifiable. Use clearly labelled measures:
- Suitability rate: suitable requests divided by genuine requests whose suitability has been assessed. Show the unassessed count alongside it.
- Suitable-to-booked rate: suitable requests with confirmed repair work divided by all suitable requests in the same arrival group. Show pending decisions separately because recent groups may still progress.
- Current booked work: confirmed bookings that remain active, separating assessments from repairs and showing cancellations separately.
If there are too few cases or too many missing outcomes, review the individual records rather than declare a winning source.
Before changing spend, use this decision checklist:
- Duplicates or administrative calls inflating totals? Fix counting first.
- Repeated unsupported areas or services? Review targeting and page boundaries.
- Suitable requests unanswered or unassigned? Fix response ownership.
- Suitable work declined because of timing? Review capacity and availability wording.
- Quotes stalled? Check recorded objections and follow-up before blaming acquisition.
- Accepted work not booked? Check the scheduling handover.
- Revenue claimed? Verify it against financial records, not quotes or estimated opportunity values.
To improve the customer journey before measuring it, compare plumbing landing pages for renovations versus emergency work. Separate urgent availability checks from project assessments so the recorded enquiry type has a clear meaning.
Agree the definitions before adding software
Give one person responsibility for keeping outcomes current, with a clear handover when someone else takes over. A modest register maintained consistently is more useful than a detailed pipeline nobody updates.
D4J’s lead-generation service connects traffic sources, qualification, response ownership and recorded outcomes. Implementation should follow your actual service boundaries, not treat every contact as a customer.
Prepare your coverage areas, accepted services and anonymised examples of requests that booked, stalled or proved unsuitable. Discuss your enquiry journey with D4J to agree what needs recording and which handover needs attention.
