Ask a sales team how fast they answer a web lead and you’ll hear “pretty quick.” Ask for the actual number and nobody has it. That’s not a criticism. Most CRMs don’t show it by default, and the honest answer depends on the hour and on who’s in that day. This guide is a one-week test you can run yourself. You submit your own form, time the reply, write down where the delay happened, and fix the slowest step. No new software needed.
What you need
- Access to your own website form and a way to submit it as a stranger. That means a personal email address and a phone number the team won’t recognize. A spare mobile or a free calling app works.
- A simple log. A spreadsheet with these columns: test #, day/time submitted, first automated reply (time), first human reply (time), channel (call/email/text), who replied, and notes.
- One colleague in on it, usually the owner or office manager. Nobody else should know, or the test measures how fast people respond when they know they’re being tested.
- About 2 hours spread over a week. No cost.
A benchmark, if you want one: Close’s inbound lead response guide sets a target of a first call within 5 minutes during business hours, with 1 hour as the outer limit. It cites research by MIT/InsideSales and Harvard Business Review. Treat those as targets to aim at, not promises about your results.
Step by step
1. Plan five submissions across the week
Spread them out so you see the real pattern, not the best case:
| Test | When |
|---|---|
| 1 | Tuesday, 10:00 AM |
| 2 | Wednesday, 12:30 PM (lunch) |
| 3 | Thursday, 4:45 PM (end of day) |
| 4 | Friday, 2:00 PM |
| 5 | Saturday morning, or a weekday at 7:30 PM |
Use a slightly different made-up company name and request each time. Keep the requests plausible but specific, for example: “We’re a 12-person firm looking to replace our spreadsheet quoting. Can someone call me this week?” Use real-looking details, but nothing that belongs to a real company.
2. Submit and start the clock
Note the exact submit time, to the minute, in your log. Then do nothing. Don’t reply to any autoresponder, because the test is about your team’s first move.
3. Record three timestamps
For each test, write down:
- Automated acknowledgement. Did you get a “thanks, we got it” email or text? How many minutes after submitting? If it came in under a minute, your form and CRM are connected. If it never came, that’s finding number one.
- First human touch. A call, a personal email or a text from a real person. Note the minutes from submission and which channel.
- Second touch, if the first was a missed call or voicemail. Did anyone follow up, and when?
Stop waiting after 2 business days, and log it as “no human reply.”
4. Trace each delay back through the chain
For every slow test, follow the lead’s path and find where the minutes went. Ask the colleague who’s in on it to check the CRM with you:
- Form to CRM: When was the record created? If it’s 15 minutes after submission, the form connection is polling, not instant. This often happens with Zapier on the free plan, which checks every 15 minutes.
- CRM to a person: When was an owner assigned? When did a notification or task appear? If the record sat with no owner, your routing is the problem.
- Notification to action: The rep got the alert at 10:01 and called at 11:40. That’s a process and staffing problem, not a software one.
- Wrong channel: The lead left a mobile number and asked for a call, and got an email two hours later.
Put the delay for each step in your notes. After five tests you’ll usually see the same step causing most of it.
5. Fix the slowest link first
Match what you found to the fix:
- No acknowledgement at all. Add an instant autoresponder from the form or the CRM: “Thanks, {first name}. {Rep name} will call you from {number} within the hour during business hours (Mon–Fri, 8–5).” Give a real time window and keep it.
- Form to CRM is slow. Switch to an instant trigger or webhook, or to the CRM’s native form. A polling interval is a delay you build in yourself.
- No owner assigned. Set up automatic assignment with a fallback person. If you use Pipedrive, Zoho CRM or Close, there are separate guides for each in this section.
- Alert sent, nobody acts. Make the alert harder to miss: a text or chat message to the owner, not only an email. Name a backup who gets it after 10 minutes if the task isn’t done. Agree on a “who covers inbound” rota for lunch and the last hour of the day.
- After-hours leads wait until noon the next day. Make the first task of the morning “call every lead from overnight, oldest first,” before email.
- One attempt and done. Add at least a second call and an email over the next two days. Close’s guide suggests 6–8 attempts before calling a lead unreachable. For a small team, 4 attempts in 7 days is a reasonable floor.
6. Re-test in two weeks
Run the same five-slot schedule again after the fixes. Compare the two logs side by side. Look at the median first-human-touch time and the number of tests with no human reply, not only the best result. Then repeat it once a quarter, because response time slips when staff change.
7. Turn the test into a number you track
Once it’s fixed, most CRMs let you report on it. Two options:
- Create a date field called “First contacted at” that a rep or workflow fills in, and report the average gap from “Created at.”
- Use your CRM’s built-in response reporting if it has one. Close, for example, has Workflow Reporting with average response time.
Whichever you use, look at it every month.
Common mistakes
- Telling the team. Response times improve for exactly one week and you learn nothing.
- Only testing at 10 AM on a Tuesday. Your worst gaps are at lunch, end of day and weekends.
- Counting the autoresponder as a reply. It’s useful, but it isn’t a conversation.
- Blaming the software first. The slowest step is often the gap between “alert received” and “phone picked up.” No tool fixes that without a clear owner and a backup.
- Fixing everything at once. Change the slowest step, re-test, then move to the next. Otherwise you won’t know what worked.
When it’s worth getting help
You can run the test and most of the fixes yourself. It’s worth getting help when the trace in step 4 shows the delay sits in the plumbing: forms connecting through several tools, leads arriving without owners, alerts going to the wrong person. Rebuilding that once is usually faster than patching it test after test. My B2B CRM page describes how I work on this. The cost calculator helps you put a monthly figure on slow follow-up, using your own lead volume and close rate.