Speed to Lead: The One Thing a Service Business Can Fix This Week

The pattern is simple, and the posts below show it in trades and in legal intake. Someone with an urgent problem starts working down a list of providers. If you cannot answer, the enquiry is still live for whoever does. You are two metres up a ladder with your hands in a wall. The complaint turns up in odd places. On r/Plumbing, a developer pitching an AI back-office product for trades opened his post by recounting a conversation with his brother-in-law, who runs a plumbing business in Birmingham: "I asked him how business was going. He said it was fine but he reckoned he was losing two or three enquiries a week just because he couldn't answer his phone on a job and was getting fed up of all the paper admin which went with it which got me thinking." Treat that for what it is. A second-hand figure inside a product pitch, not something measured. It is still the shape of complaint operators recognise, but the number came out of a conversation over a beer. The second half of the problem is that the enquiry has nowhere to sit. A missed call is a number in a call log. A text is in one thread. A form fill is in an inbox that also has supplier invoices in it. By Thursday you cannot reconstruct who asked for what. On r/smallbusiness, an operator put it this way: "I run a small home services business and it's so hard to keep up with calls while out on the job. Missed calls during jobs, voicemails piling up, customers asking the same questions over and over." Note what is being described. Not a lack of AI. A lack of a place for the thread to live. The underlying research is stronger than most of what gets quoted from it. Oldroyd, McElheran and Elkington audited 2,241 US companies and found firms that tried to contact a lead within an hour were nearly seven times as likely to qualify it as those that waited an hour longer, and more than 60 times as likely as those that waited 24 hours or more (The Short Life of Online Sales Leads, Harvard Business Review 89(3), March 2011). The response times in the same audit are the part worth sitting with. Of those 2,241 companies, 37% responded within an hour, 16% within one to 24 hours, 24% took longer than a day, and 23% never responded at all. Among those that did respond within 30 days, the average was 42 hours. Two caveats before you apply this: it is United States data, and it measures B2B and B2C web leads rather than Australian trade enquiries. The direction is well evidenced. The exact multipliers are not yours until you measure your own.

This distinction matters because the two numbers get blended in sales material, and the blended number is what convinces people to buy a voice agent they do not need. | Claim type | Typical framing | What it is actually based on | | - | - | - | | Vendor claim | Sounds like: you are losing X% of revenue to missed calls | A modelled figure applied to your business, usually not measured in it | | Operator report | Sounds like: a rough weekly count of enquiries that went unanswered | A tally kept in the head of the person who owns the phone | | Your real number | Unknown until you count it | Your own call log, your own quote list, over two to four weeks | Only the third row can justify spending money. The accounts quoted here are a handful of individual posts. They suggest the pain is real for the people describing it. They are not evidence of how common it is, they are not evidence of the size of the loss in your business, and nobody outside your business can tell you that. A useful thing to notice is that whether a missed call converts to a lost job is genuinely an open question. On r/Plumbing, someone researching the market put it to plumbing business owners directly: "Most plumbing jobs seem urgent. Burst pipes, clogged drains, water heaters. If someone calls and you do not answer, do they usually leave a voicemail or just move on?" That question is the whole article. If most of your missed callers ring back within the hour, your leak is small and an expensive answering system is a bad buy. If they never ring back, your leak is large. You do not know which one you are until you count.

Two weeks. A spreadsheet. No purchase. 1. Export your call log. Most mobiles let you see missed calls with times. Record every missed call from an unknown number during working hours. 2. Mark the ones that called back. If the same number rang again, or texted, or turned up in your inbox, that lead recovered itself. Those are not losses. 3. Ring the rest back once. Ask one question: did you get this sorted? Their answer tells you whether they waited or moved on. 4. Do the same for form fills and emails. Log the time the enquiry arrived and the time you first replied. Response gap is the metric. 5. Tally at the end of the fortnight. Missed calls, calls that self-recovered, calls that went to a competitor, and your median first-response time. Now you have three numbers no vendor can give you: how many enquiries you actually miss, what share of them are genuinely lost, and how long you take to respond when you do respond. If the loss number is small, stop here and keep your money. If it is meaningful, you now know exactly how much a fix is worth, which is the only sane basis for choosing one. The response gap is often the surprise. In an r/automation post promoting a legal intake build, the author describes a client firm reaching its leads two or three days after they arrived, by which point they had already hired someone else. That is a sales anecdote rather than a measured figure, so weigh it accordingly, but the shape is familiar. Days, not minutes. That gap is usually fixable without any voice technology at all.

An AI phone agent is the most visible product in this category, so it is the one people buy first. It is rarely the highest-return move, for three reasons. It solves the smallest part of the problem. A lost job can just as easily die in the gap between the enquiry and the quote as in the first ten seconds of a phone call. An agent that answers politely and then drops the thread into the same void has moved the problem, not removed it. It fails loudly. A wrong quote, a wrong availability, a booking on a day you are interstate. Trades operators are reasonably wary of anything customer-facing that speaks on their behalf before they have seen it behave for a month. It is the hardest thing to own. When a voice agent misroutes a job, someone has to work out why. If that person is not in your business, you are on a retainer forever. The counter-argument is real and worth conceding. If you are a genuine emergency trade, after hours, and callers never leave voicemail, a live answering capability does earn its keep. Some operators are exactly in that position. The point is not that voice agents are useless. It is that you should be able to name your measured number before you buy one.

Two parts, both cheap, both buildable in a week. Part one: the acknowledgement. Every missed call and every form fill triggers an immediate reply. Text for calls, email for forms. Three things in it: you have the enquiry, when you will respond properly, and what they can send you in the meantime, such as a photo of the problem and their suburb. That last part does real work. It converts dead waiting time into a partly qualified job. Part two: the thread. One list where every enquiry lands with a status. Not five apps. A job management tool such as ServiceM8, Tradify or Simpro if you already run one, a shared spreadsheet if you do not. The requirement is that at any moment you can see every open enquiry and which ones have not been answered yet. The reason this can beat a receptionist is ownership. An auto-reply and a status list are things you or a staff member can read, change and fix. When the acknowledgement text says the wrong thing, you edit it that afternoon. Nothing about it requires a vendor.

The person who owns the phone should own the fix, or someone in the business who sits beside them. This is a common way small-business projects quietly die. The automation gets built by an outsider, works for six weeks, then a phone number changes or a form field gets renamed and it stops firing. Nobody inside notices, because nobody inside knows where it lives. The enquiries go back to being missed, and now there is a subscription as well. The skill worth acquiring is not node-dragging in a workflow tool. It is diagnosis: being able to open the thing, see where the message stopped, and work out why. That skill transfers to every subsequent problem in the business, which is why 13Labs runs buildAutomation as capability transfer to two or three of your own people rather than as an ongoing service. Start with the measurement. It costs nothing and it will tell you whether the rest of this is worth doing at all.

How fast do I actually need to respond to an enquiry? Fast enough to be first. In practice that means an automatic acknowledgement within a minute or two, and a real human response the same day. The acknowledgement buys you the hours you need. Measure your current median response gap before setting a target. Should I get an AI receptionist for my trade business? Only after you have measured how many callers never ring back. If most self-recover, a receptionist is an expensive fix for a small leak. If you run genuine emergency work after hours and callers move straight to the next name, live answering can be justified. What is a missed-call-to-lost-job rate? The share of your missed calls that never become work. Count missed calls during working hours over two weeks, subtract the ones that rang back or emailed, then ring the remainder once and ask if they got it sorted. The leftover figure is your real loss. Do I need a CRM, or is a spreadsheet enough? A spreadsheet is enough to start if it shows every open enquiry and its status in one view. Move to a job management tool when you need quoting, scheduling and invoicing joined up, or when more than one person has to see the same list. Why do these fixes stop working after a few months? Because nobody inside the business owns them. A changed phone number or a renamed form field breaks the trigger silently. Someone on your team needs to know where the automation lives and how to check it, which is a diagnosis skill rather than a tooling skill.

Quotes are reproduced verbatim from public Reddit discussions and attributed to the subreddit, not to individuals. r/Plumbing: https://www.reddit.com/r/Plumbing/comments/1sfc0nh/is_this_something_that_would_actually_be_useful/ r/Plumbing: https://www.reddit.com/r/Plumbing/comments/1rdpfbs/plumbing_business_owners_how_do_you_handle_missed/ r/smallbusiness: https://www.reddit.com/r/smallbusiness/comments/1pqlni4/who_has_actually_replaced_frontdesk_tasks_with_an/ r/automation: https://www.reddit.com/r/automation/comments/1m8nv4q/how_i_built_an_aipowered_personal_injury_lead/ Statistics are cited inline with their source and date. Quotes are reproduced verbatim from the public discussions listed above and attributed to the forum, not to individuals. No client results are cited. The posts above are individual reports, not a measured sample, and they are not specific to Australia. Only the r/smallbusiness post is a first-person account by an operator. The first r/Plumbing post is a product pitch by a developer, the second is a market-research question by someone outside the trade, and the r/automation post is a promotional case study.