# What is speed to lead? URL: https://ergostrat.com/en/automations/speed-to-lead.html Language: [Български](https://ergostrat.com/automations/speed-to-lead.html) · [English](https://ergostrat.com/en/automations/speed-to-lead.html) · [Français](https://ergostrat.com/fr/automations/speed-to-lead.html) · [Deutsch](https://ergostrat.com/de/automations/speed-to-lead.html) Speed to lead is the time between an enquiry arriving and the first meaningful response. Define what that response means before measuring it. An automatic receipt, an attempt to call, a conversation and a qualified opportunity are different milestones. Automating a receipt can shorten one interval without shortening the wait for a useful answer. ## What do historical studies actually measure? A 2007 InsideSales.com report compared calls at 5 and 30 minutes. It reported 100-fold lower contact odds and 21-fold lower qualification odds with the delay. Those are historical call outcomes, not a promised sales increase. Keep the outcome attached to any quoted ratio. Contact is not the same event as qualification, and neither is a completed sale. A study of calls does not establish what an automated email receipt will do for your business. Use evidence to decide what to test, then measure your own process. A reply that only says “received” can still be useful. It tells the person the enquiry has arrived and what should happen next. It should not be counted as a completed conversation or described as a human reply if it is automatic. ## How should you measure the wait today? Record when the enquiry arrives, when it is assigned, when someone first tries to respond and when a meaningful exchange begins. Keep automatic acknowledgements in their own field. Define the time zone and whether your reporting uses elapsed time, working hours or both. Look at the cases behind an average. A quick acknowledgement can hide a long wait for an owner; a few enquiries left overnight can disappear inside a single mean. Review the slow and unanswered cases alongside the typical interval. Include the source of the enquiry so a failing form does not look like a quiet sales channel. Choose the response target from the service you can actually staff. Specify what happens outside working hours and during absence. Do not put an instant automated message in front of a promised conversation that nobody has agreed to deliver. ## What would the automation do? - Capture the enquiry from an agreed source and record its arrival time. - Send an acknowledgement that identifies itself as automatic and explains the next step. - Assign a named person and notify them through the agreed channel. - Keep the enquiry, owner and status in one place so an inbox and a spreadsheet do not become competing lists. - Escalate or use a fallback route when delivery, assignment or a later step fails. The trigger depends on the source system. A webhook may be appropriate where the system supports it; it is not a capability every form necessarily has. Confirm that the enquiry is received and retained before treating a trigger event as a completed handover. Agree a test before acceptance. Check the normal path, a failed notification, an absent owner and a repeat submission. Decide how to handle duplicates without silently discarding a real enquiry. A fallback must reach a person who knows what to do; a second unattended inbox does not settle responsibility. After the change, compare the same milestones and reporting hours with the baseline. Check whether the wait for a meaningful answer improved, not just whether the receipt was faster. Also review missing, duplicate and misrouted enquiries. No improvement percentage should be claimed from a successful demonstration alone. ## Questions ### Is this relevant to business enquiries as well as consumer enquiries? You can define and measure the response path for either. The useful milestones depend on your process: a booking request, a technical question and a purchasing enquiry may need different owners. A historical study does not give a ready-made sales prediction for either audience. ### Does a faster automatic reply guarantee more sales? No. Acknowledgement, successful contact, qualification and sale are separate outcomes. Speed can be measured without treating one as proof of another. Record what happened after the reply, including cases that never became a conversation. ### Should we choose the tool with the fastest advertised reply? Ask what that advertised interval measures and how it was tested. Then check assignment, delivery, working-hours coverage and fallback. A software response-time claim does not establish the time to a useful answer from your team or an independently measured outcome. ## Source [InsideSales.com: historical lead response report, 2007](https://content.marketingsherpa.com/heap/DG07SFSlides/LeadResponseManagementReport.pdf) ## Related reading - [Contact form not sending emails: what to check](https://ergostrat.com/en/monitoring/contact-form-not-sending.html) - [How do you choose an automation partner?](https://ergostrat.com/en/automations/choose-automation-partner.html) ## Measure today’s response before automating it. A fast reply is one process like any other: measured before, built, proved with a signed test. Write to us about where your enquiries come from and who answers them today. [Book a call about one process](mailto:contact@ergostrat.com?subject=Question%20after%20the%20Speed%20to%20Lead%20article)