Start with your own response promise
A fast response should move the customer forward. The right target depends on channel, buying urgency, operating hours and whether the first reply can answer the real question. Do not borrow a universal five-minute benchmark and call it strategy. Define what a useful response means for your business, by channel, and when the clock should reasonably be running.
A useful response might be a conversation, a confirmed call-back time, a request for the missing information needed to quote, or a booking step. An automated acknowledgement can reduce uncertainty, but it is not the same thing as progress if the customer still does not know what happens next.
The Australian field-service clue
Response leakage is especially relevant where phone calls, messages and quoting compete with the work itself. hipages’ February 2024 Tradie Trends research reported that 77% of surveyed Australian tradies used phone calls as their most common customer communication method, 34% used three or more communication platforms, and 31% said that made conversations easy to lose track of. The same research reported 66% had experienced lost work or jobs because of the amount of time spent on business administration.
Treat those figures as directional vendor-commissioned research, not a benchmark for your business. The practical point is simpler: if enquiries arrive through several channels while the owner or team is also delivering work, response coverage becomes an operating-system question as much as a marketing question.
Build a baseline you can trust
For one working week, count total new enquiries and how many were missed or did not receive a useful response inside your own stated target. Then record who owned the next step and whether the opportunity stayed visible until it progressed or was deliberately closed.
Three measures are usually enough to start: response coverage, median time to first useful response, and progression to a useful next step such as conversation, quote or booking. ServiceM8’s current phone-reporting guidance uses the same operational idea: separate answered and missed calls, business-hours and after-hours demand, then investigate coverage when calls are being missed. You do not need ServiceM8 to use the principle.
Separate exposure from guaranteed lost revenue
A missed or late enquiry is not automatically a lost sale. Lead quality varies, customers contact more than one provider, some people call back, and capacity may mean the business should not accept every job anyway. That is why HaddadStuff treats missed enquiries as opportunity exposure rather than revenue already lost.
If you know your normal conversion rate for suitably handled enquiries and a typical first-job or first-sale value, you can build an illustrative scenario. Multiply the enquiries that missed your response target by your own conversion assumption and typical value. Use that number to size the problem, not to claim certainty.
Fix coverage before buying more demand
If the baseline shows enquiries disappearing between arrival and a useful next step, give every new enquiry one visible queue and a named owner before increasing advertising. Check notifications, call routing, forms, inboxes and after-hours expectations. Then repeat the baseline and see whether progression improves.
If response coverage is already reliable but suitable enquiry volume is still too low, demand generation becomes a cleaner hypothesis. If response is reliable but conversion remains weak, investigate qualification, quoting, price, trust and follow-up instead.
Make the next move falsifiable
Run the response change as a short test. Write down the target, owner, baseline and the result that would count as better before changing tools. If the leak is phone-heavy, inspect missed calls and call-back ownership. If it is form or message-heavy, inspect routing and visibility.
The point is not maximum responsiveness. It is a response system that matches customer intent and business capacity, with enough evidence to know whether the change improved commercial progression.