Discovery Call Pre-Qualification
Four questions decide who gets into your calendar: current situation, urgency, scope, decision authority. Anyone who has answered them arrives at the call prepared, and anyone who cannot answer them never gets in. Here is what order to ask them in, what to base your thresholds on, and why the rejection exit is the most important of the three.
Why your calendar is full and still nothing closes
You sell through the first call, so you make booking as easy as possible: “just grab a slot”, link in the bio, link under the ad, link in your signature. The calendar fills up and that feels like progress.
Ten minutes of small talk later you find out what is really going on. The budget is somewhere else, the timing is a year out, or the person on the call is not the one who decides. The call itself is the smaller loss. What actually costs you is the prep, the context switch and the slot taken by someone who was never going to buy, while someone who was ready sits in next week. And the fact that some of those inquiries were never inquiries is not a hunch: Chili Piper analysed close to four million demo form submissions and 14.1 percent of them were not real leads at all.
A booking is not a call yet either. RevenueHero’s no-show benchmark across 6,428 booked B2B meetings sits at 6.5 percent on average and runs as high as 18.1 percent depending on the industry. A full calendar is a claim, not a result.
So the sorting belongs earlier, and it belongs where your contact is already typing. That is also how buying works now: 67 percent of B2B buyers prefer a rep-free buying process, according to Gartner. For those buyers, four questions in chat are not an extra hurdle, they are exactly the self-service they were looking for. They answer whenever it suits them, and in doing so they work out for themselves whether a call makes sense. For that to work, the sequence needs an exit where the path to a booking simply ends. A funnel that never says no is not sorting anything, it just moves the rejection into your calendar.
How the sequence is built
Entry with opt-in
The trigger is an ad, the link in your bio or a QR code. The first message is an approved template with a clear opt-in, because only your contact’s reply opens the free window. That is why this first message asks for nothing, it only collects a response. Everything you try to learn before that response costs you contacts who would never have replied.
Context first, questions second
Before the first question there is a short message explaining who the call is for and what happens in it. Two lines, and they decide whether the questions that follow feel like advice or like an interrogation. Anyone who does not recognise themselves here leaves on their own, and that voluntary exit is the cheapest sorting you will ever get: it costs you no rejection and your contact no disappointment.
Four questions, and the order is half the work
You cover four dimensions: current situation, urgency, scope, decision authority. Current situation comes first because it can be answered without disclosing anything, your contact simply describes what they have today and how they handle it today. Urgency comes next, because it separates interest from pressure, and pressure is the most reliable sign that someone will decide anything at all in the near term. Scope follows: size, volume, timeframe. The question about who else decides comes last, because it is the most personal one and only gets an honest answer once your contact has already invested three replies. You can tell a good question by how the answers spread out. A question everyone answers the same way has three options and still sorts nothing. One question per message, at most three answer options, so it stays readable at a glance in chat. That format carries: across 2.6 million forms analysed by Typeform, one question per step averaged a 47.3 percent completion rate against 21.5 percent for classic forms.
Ask about scope, not about budget
A direct budget question in chat gets either no answer or an invented one. Your contact often has no number yet, and if they do, they suspect it will be used against them. Scope gives you the same information by a route that can actually be answered: how many locations, how many people, how many inquiries a month, by when it needs to be running. You derive the budget from that order of magnitude yourself, and your contact never has to commit to a figure. The same thinking applies to authority: you do not ask “are you the one who decides”, you ask who else is at the table. Same information, and the question costs nobody face.
Thresholds are a decision, not a formula
A condition node reads the variables and assigns the contact to one of three segments: a fit, a fit later, not a fit. The work is not in the node, it is in deciding which combination of answers goes where. Two guidelines help. Urgency beats scope, because someone with a problem today tends to find the means more readily than someone who might start next year. And missing authority is not a disqualifier, it is a different invitation, because in that case you do not need the call, you need the document your contact can pass on internally. Where exactly you draw the line depends on how full your calendar is: the scarcer your time, the stricter the threshold for “a fit”.
Three exits, and the third one carries the other two
A fit: your booking link as the single action button, plus a handover of every answer to your CRM. The real effect shows up in the call itself. Your contact answered four questions and sorted out their own situation while doing it, so they arrive with an expectation. You know the current situation and the urgency before the call begins. That removes the inventory-taking that normally eats the first fifteen minutes, and you start at the topic. A fit later: a tag and a turn into the follow-up track instead of a slot. Not a fit: a friendly exit with a real alternative, a pointer, a referral or the smaller offer that actually suits them. That third exit feels like a loss and is the reason the other two work. Every no in the chat frees up a slot for someone who can decide. And because the no arrives immediately instead of two weeks later by email, the contact stays on good terms with you.
Example scenario: a consultancy that sells through a first call
A consultancy gets inquiries from ads and a link in bio. Every inquiry lands straight on the booking page. Budget, timing and authority get sorted out during the call itself.
Everyone who clicks gets a slot. Tuesday morning: four calls, one with someone who has budget next year, one with someone who has to ask their boss first. The no goes out by email afterwards, often not at all, and the contact lingers on a list as “maybe someday”. Anyone who is genuinely ready finds nothing free next week.
Four questions sit in the chat in front of the calendar. The booking link only appears in the “fit” branch, together with the answers in the CRM. Anyone who is early gets a tag and a scheduled follow-up instead of a slot. Anyone who is not a fit gets a clear answer and an alternative, right there in the chat, without waiting for a callback. Fewer calls end up in the calendar, and every one of them starts somewhere else: not at “so, tell me what this is about”, but at what your contact already wrote down. And because the sequence continues past the booking, the reminders 24 hours and 1 hour before are part of the same plan.
What you get
The blueprint with all three exits
The full sequence laid out visually: entry, the four questions, the condition node, the three branches, goal and reminders. You can see at a glance where the sorting happens and where each contact comes out. Every node carries its purpose and the information it has to collect or deliver. You write the messages yourself, the frame for them is already there.
The qualification logic as a written rule set
Which dimension each question covers, what order it comes in, and how the three answer options need to be cut so they actually separate people instead of just keeping them busy. Plus the thresholds: which combination of answers lands in “a fit”, which in “a fit later”, which in “not a fit”. It is written as a rule you can tighten or loosen as your calendar fills up or empties out. You also decide what sits at the end of the rejection branch: the exit with an alternative, or the turn into nurture. Both versions are drawn out for you.
A buyer persona with over 50 data points
Buying motives, objections, reasons for hesitation and how decisions actually get made in your market. That is what tells you which questions genuinely separate people, because a question everyone answers the same way sorts nothing. The same material tells you which alternative in the rejection branch is genuinely useful to the person receiving it, rather than merely polite.
The timeline after the booking
Two reminders, 24 hours and 1 hour before, each with two buttons: confirm or reschedule. The reschedule button is the actual lever, because a cancellation 20 hours out is a free slot while an empty slot is lost time. Anyone who does not react at all runs into a branch of their own. Your booking link sits in the right place, and your booking tool reporting back is planned in as a signal.
The starting list for the build
Booking link, the signal from your booking tool, the CRM fields for the handover and a real alternative offer for the rejection branch. You know what needs to be on the table before the first click, not halfway through the build.
More funnel blueprints
Sort before the calendar, not during the call
You get the whole sequence as a blueprint: structure, branching logic, the thresholds for all three exits, buyer persona and asset list. You write the messages yourself, and the core takes under six hours to rebuild in your messenger tool. One-time payment, no subscription.
Build my funnel blueprintOne-time payment, no subscription. You get the complete strategy and overview first.