A marketing operations manager fills out a demo form at 2:10 on a Tuesday afternoon. In the free-text box, she asks whether the product can sync call notes into custom CRM fields. The round-robin hands her to an SDR who dials four minutes later, and the speed to lead tile turns green.
He never opened the form, so he launches into the same qualification script he runs on every inbound call. Team size and budget come first, and she answers politely for six minutes before she raises the custom fields herself. He tells her an account executive will follow up with the details. Two days later she books a demo with a vendor whose rep answered her question on the first call.
The minutes did matter, because she probably had another vendor open in the next tab that afternoon. But most advice on inbound response stops at the dial, which is exactly where the real work starts. The SDR wins or loses this call on whether he read why she asked and can answer her before he asks anything of his own.
Speed to lead is the time between a buyer's request for contact and a rep's first response. The clock starts when someone submits a demo form or asks for a callback in chat, and every team argues about where it stops. That argument deserves more attention than it gets, because the stop point decides what the number can tell you.
If the clock stops at the first dial or email, you are measuring how fast the SDR reacts. Stopping it at the first live conversation measures how fast the buyer actually hears a person, and that version is much harder to game. Under the dial definition, an SDR who leaves one quick voicemail posts a perfect number and then forgets the lead until after lunch.
Pick the live-conversation version, and argue for it in the next ops review if you have to. Even that version says nothing about the call, since a fast call that confuses her looks exactly like one that books the meeting. So treat speed to lead as two numbers: how fast the SDR reached her, and how well the call answered the reason she asked.
None of this is an argument for slowing down the queue. An inbound request goes stale within hours, because she filled out the form while the problem was on her mind. Once her afternoon fills up with back-to-back meetings, that urgency fades, and by morning she may have talked to someone else.
Response time is also the first thing she learns about how your company runs. A callback within minutes tells her someone watches the queue, and a two-day wait tells her nobody does. Marketing paid to put that form in front of her, and nobody wants to explain a slow follow-up to the CFO.
That said, a fast dial only buys the SDR the right to talk. If she hears the same script every other vendor runs, she has as much reason to keep shopping as a buyer who waited a day.
By the time she fills out the form, she has done most of her homework alone. Gartner's buyer research shows how far that homework goes and what buyers want from a rep once they finish it.
In a May 2026 press release, Gartner shared results from a survey of 645 B2B buyers that it ran in August and September 2025. According to the release, 45% of buyers used generative AI for vendor research. In the same group, 69% prefer to validate AI-generated insights with a sales rep, so an inbound call often starts with something the buyer already read.
Gartner released a second finding from the same survey wave two months earlier. In a March 2026 press release, the firm reported that 67% of B2B buyers prefer a rep-free experience. Taken together, the two releases describe a buyer who would prefer to buy alone but has hit a question her research could not settle.
That should change how teams run the first call, and in most shops it has not. She wants help with one or two doubts left over from her research, and the form usually tells you what they are. A standard discovery opener like "tell me a little about your business" asks her to repeat work she already did at her desk.
We looked at how these buyers skip vendor websites entirely in our piece on the AI-researched buyer. For many of them, the inbound call is their first conversation with anyone at your company.
Fast calls fail in the same few ways on most SDR teams, usually because the team treats leads as interchangeable. Teams that measure only response time build their habits around the dial, so these show up early and stay:
She notices every one of these, usually within the first two minutes of the call. When she stops replying, the SDR finishes his follow-up sequence and marks the lead as unresponsive. The opportunity then sits in the CRM until someone closes it out at quarter end. Meanwhile his response time still looks great, so when the VP asks in the pipeline review why inbound meetings are light, the dashboard has no answer.
A useful pre-call check takes about two minutes, and its only job is to find out why she reached out before the SDR has to ask. Work through it in this order:
Two minutes covers most leads, and SDR leaders can build that time into the response target. A team that aims for five minutes still hits it if the SDR spends two of them reading. What blows up the target is a research habit that runs long, like scrolling through the buyer's entire LinkedIn history before every inbound call. A rep who dials a bit later with the form in front of him wins more of these calls than one who dials blind.
Some requests show up with almost nothing, like a form with only a name and an email address. In that case the SDR should call anyway and let the first question do the research, since her company's website and job title still support a sensible opening guess.
Name the reason she reached out in the first sentence after hello, and the rest of the call gets easier. Reps resist this at first because the script taught them to earn the right to ask, so expect a few role plays.
A line like "You asked whether we can sync call notes into custom CRM fields, so let's start there" proves somebody read her request. It also tells her whose agenda the call is on. If the form had no free text, he can name the page she viewed right before she submitted it.
Next, he asks what she already knows, because plenty of buyers show up with an AI summary or a shortlist from a peer. A plain question works, such as what she has seen so far and what is still unclear. Her answer tells the SDR which facts to confirm and which ones to correct before they end up in her business case.
Most SDR teams train reps to hand anything technical to the AE, and on inbound calls that habit does more damage than a slow dial. Integration questions and pricing tiers usually have short answers that a new SDR can learn during ramp. For the hard ones, he gives her the short version and puts the AE on her calendar before hanging up.
Only after answering does the SDR move to qualification, and her question usually opens the door. A buyer who asked about custom CRM fields has already named her CRM and told you someone on her team worries about data quality. From there, he asks who else cares about that sync and when they plan to decide, which covers authority and timing.
BANT and SPICED still work on an inbound call, but the order most teams drill into new hires is wrong for inbound. She already showed intent by filling out the form, so the SDR mostly needs to confirm fit and urgency, starting from her reason.
With SPICED, her question usually gives away her situation and part of the pain before the SDR asks anything. He fills in impact by asking what happens if the problem is still there at the end of the quarter. Critical event and decision questions come last, once she trusts that the call is about her.
Every SDR manager has heard the pushback from reps who worry that dropping the script order means missed fields and deals that ops will flag. The rep still covers every field, just in the order her story brings them up. A manager who reviews the call can check coverage, and any missing field becomes next week's coaching point.
A relevant first call also makes disqualifying faster and more honest. If her question shows she needs something the product does not do, the SDR can say so in the first five minutes. She leaves with a straight answer, and the AE keeps that calendar slot for a buyer who actually fits.
Both calls below can hit the same response target, and both turn the dashboard tile green. What separates them is how the SDR spends the first ten minutes after she picks up.
| Part of the call | Speed-first call | Prepared first call |
|---|---|---|
| Before dialing | Dial as soon as the alert fires | Two-minute read of the form and CRM |
| Opening line | "I saw you were on our website" | The buyer's own question, in her words |
| First five minutes | Team size and budget | Answer to the buyer's question |
| Technical questions | Deferred to the account executive | Short answer now, detail on the next call |
| Qualification | Fixed order from the script | Follows the buyer's reason for reaching out |
| Handoff to the AE | Form fields and a meeting time | The buyer's question and the SDR's answer |
| What the dashboard shows | Fast response | Fast response and a scored first call |
A response-time chart tells you who dialed fast, and only the recordings tell you what she heard. Plenty of SDR leaders check that chart every morning and almost never listen to an inbound call, which gets the priorities backward.
The review itself is small and fits in a Friday afternoon. Pick two calls from every rep each week and listen to the first five minutes of each one. Teams that record calls on a conversation intelligence platform can search the recordings for last week's inbound first calls. From there, the leader scores each call on five behaviors:
After two or three weeks of this, each rep's pattern becomes obvious. One rep answers questions well and never asks what the buyer found, while another opens strong and slides back into the script a few minutes in. Frontline managers can then give each rep one behavior to practice for the next two weeks. A rep who leaves a one-on-one with a long list of fixes usually works on none of them.
Practice with real material from the team's own queue. A manager can read last week's actual form submission aloud and have the rep open the call cold, then repeat it with a different form. After three or four rounds, most reps start naming the buyer's reason without thinking about it.
If response time is the only inbound number on the dashboard, it will be the only habit your SDRs build. RevOps leaders can add four measures next to it:
Watch the last measure most closely, because it shows whether the first call helped anyone after the SDR hung up. We covered where buyer context goes missing between the two roles in our guide to the SDR-to-AE handoff. When the AE opens discovery with the same question she typed on the form, she starts to wonder whether your team talks to each other.
Then fix the incentive, because this is where most inbound programs quietly break. If comp pays on response time alone and the routing rule reassigns any lead left undialed, reps will skip the pre-call check. Set a response target and a review-score target side by side, and reps finally have a reason to keep both habits.
For inbound teams, Rafiki AI adds an intelligence layer to the callback, so the buyer's reason outlasts the SDR's memory. Rafiki AI records callbacks through its native Aircall and OpenPhone integrations and transcribes them in more than 60 languages. That covers most inbound first calls, because the callback usually happens on the dialer.
Smart Call Scoring scores every call against any methodology or custom criteria. That means an SDR leader can turn the five review behaviors into a scorecard for every inbound first call. The weekly review then starts with the low-scoring calls, and the manager stops spending Friday afternoon hunting for examples.
After each call, Smart Call Summary summarizes the conversation, so the notes show what the buyer asked and how the SDR answered. Smart CRM Sync fills in the qualification fields the team chooses, including custom ones, so the AE sees the buyer's reason. For the written reply, Smart Follow Up drafts the follow-up email, and the SDR checks it against her form question.
Before dialing, an SDR can use Gen AI Search to look through past calls for the buyer's company name. Once a month, the SDR leader can use Gen AI Reports to look at the questions inbound buyers raised and share them with marketing. For practice, sales enablement teams can use AI Role Play so new SDRs rehearse the opening with an AI buyer first.
This week, pull ten inbound first calls from the last month, spread across every SDR on the team. For each call, write down the response time and whether the SDR named the buyer's reason in the first minute. Then note whether she heard an answer to her question before anyone asked about budget.
Next week, roll out the two-minute check and ask every SDR to open with the buyer's reason. At the end of October, pull ten new calls and put the two sets side by side. Fall campaign leads are landing now, so an October audit gives the team a tested routine before January targets and the new comp plan arrive.
Rafiki AI's conversation intelligence platform starts at $19 per seat per month, and a small inbound team buys only as many seats as it has SDRs. Start a free trial and score this week's inbound callbacks. To see it on your own queue before signing up, book a demo and ask to see it on a recent inbound call.
No single target fits every team, because lead volume and SDR headcount vary so much. Most teams set a goal in minutes during business hours and track how often SDRs hit it. The better test is whether the fast calls also book meetings, since a quick generic call wastes the response.
After a short hello, the SDR should name the buyer's reason for reaching out, in her own words. If the form had no free text, the page she came from is a fine place to start. From there, he can ask what she has already found in her own research.
Measure the time from the buyer's request to the first dial, and separately to the first live conversation. Track both numbers next to meeting-booked rates and first-call review scores. Together they show whether the team responds quickly and also uses the call well.
Yes, because a buyer who asks for a call has usually hit a question her own research could not answer. She wants that answer soon, and she will ask another vendor if nobody responds. Speed gets the SDR into the conversation, and preparation decides whether she books the next meeting.
Start for free — no credit card, no seat minimums, no long contracts. Just better sales intelligence.
