What is lead qualification? BANT for chatbots
Lead qualification is the process of asking a few targeted questions to work out whether a prospect is genuinely worth a salesperson's time, before they get a callback. The BANT framework โ Budget, Authority, Need, Timeline โ is a common structure for these questions, and a chatbot can ask them automatically the moment someone shows interest.
- Lead qualification separates genuine buyers from casual enquiries before your sales team spends time on a call.
- BANT stands for Budget, Authority, Need and Timeline โ four quick questions that reveal how ready a lead actually is.
- Scoring leads as hot, warm or cold lets you route the best ones to sales immediately and the rest into a nurture sequence.
- Asking too many questions upfront causes drop-off; two or three well-chosen ones are usually enough.
- Answers should be saved to a CRM record automatically, not left buried in a chat transcript nobody reviews.
The definition
Lead qualification is the step between "someone showed interest" and "a salesperson calls them" โ a short set of questions designed to reveal whether this particular person is likely to actually buy, and how soon. Skipping it means every enquiry, from a serious buyer to someone idly browsing, lands on a salesperson's desk with equal priority, wasting time on the ones that were never going to convert.
Doing it well does not require a long form. A handful of well-chosen questions, asked conversationally, usually tells you most of what you need to know.
The concept predates chatbots by decades. Sales teams have always tried to sort enquiries before committing time to them. What changed with automated chat and voice is that the sorting itself can now happen instantly, the moment someone first reaches out, rather than during a scheduled callback hours or days later.
BANT, explained plainly
- Budget: can this person actually afford what you sell? A rough range is usually enough; you rarely need an exact figure.
- Authority: are they the person who decides, or do they need to check with someone else first?
- Need: do they have a real, specific problem your product solves, or are they exploring in general?
- Timeline: are they looking to buy this week, this quarter, or just researching for later?
Not every business needs all four in equal depth: a real estate enquiry usually needs Budget and Timeline most, while a B2B software lead often needs Authority and Need most.
The order you ask them in also matters. Leading with Need feels natural and non-invasive, understanding the problem first, before asking anything that might feel like probing for money or seniority, and most well-designed qualification flows follow roughly this order: Need, then Timeline, then Budget, then Authority, adjusting the exact sequence for what feels least intrusive in that particular industry.
Scoring and routing
Once you have answers, a simple scoring rule turns them into an action: a lead with budget, decision authority and a near-term timeline is hot and should reach a salesperson immediately; a lead with genuine need but a distant timeline is warm and suits a nurture sequence; a lead with no real need or budget can be politely deprioritised without wasting further sales time.
| Score | Typical pattern | Action |
|---|---|---|
| Hot | Budget confirmed, decision-maker, buying soon | Route to sales immediately |
| Warm | Real need, but timeline is months away | Add to a nurture drip sequence |
| Cold | No clear need or budget yet | Log and deprioritise, revisit later |
Worked examples across industries
A real estate enquiry bot might ask preferred budget range, whether the buyer needs a home loan, and how soon they plan to move, enough to separate a serious buyer from someone browsing listings for curiosity. A B2B SaaS lead-qualification chatbot might ask company size, current tooling, and whether they are the one evaluating options or just gathering information for someone else. Both use the same underlying BANT logic, adapted to what actually matters for that sale.
A coaching institute qualifying admission enquiries might instead focus on which course or grade level the student needs and how soon the intake closes, while an insurance renewal conversation barely needs to ask about budget at all, since the premium is usually already known. It needs Timeline and a quick confirmation of continued Need far more.
Common mistakes
- Asking everything at once: a long qualification form feels like an interrogation and increases drop-off; two or three questions, asked naturally, usually work better than five or six.
- Not routing hot leads fast enough: a well-qualified lead that then waits hours for a callback loses much of its urgency.
- Losing the answers: qualification data left buried in a chat transcript, rather than saved to a structured CRM field, is much harder for a sales team to act on or search later.
- Treating every lead the same after qualifying: the whole point of scoring is to treat hot and cold leads differently, not to route everyone into the same generic follow-up.
- Making the questions feel scripted: reading BANT questions in the same rigid order every time, regardless of what the customer has already said, feels robotic; a well-built AI agent should skip a question if the answer was already volunteered earlier in the conversation.
Building it in Convo360
On Convo360, in the Flow Builder, use an Ask a Question block for each BANT question, a Set Variable step to capture the answer, and a Condition block to branch based on the combined answers โ routing a hot lead straight to a Save CRM lead step with a notification to your sales team, or a warm lead into a drip sequence using a Wait / Delay block. The resulting lead lands in your CRM pipeline already tagged with its qualification answers, ready for a salesperson to act on without re-asking the basics. Because the qualifying questions live in the same flow as the rest of the conversation, they can also branch naturally off an AI Reply step, so the bot only starts qualifying once it has understood, in the customer's own words, that there is genuine buying interest to qualify in the first place.
Example conversation
Qualify leads automatically
Start free in minutes โ no code, no credit card. Bring your own AI keys and pay no per-message markup.
Frequently asked questions
Do I need to ask all four BANT questions every time?
No, use whichever two or three matter most for your business. Asking every question in full every time often adds unnecessary friction for leads who would answer the important ones happily but drop off at a long form.
Can lead qualification be done entirely by a chatbot, without a human?
Yes, the qualifying questions themselves can be fully automated. Most businesses still involve a human for the actual sales conversation once a lead is scored as hot, rather than trying to close the sale purely through the bot.
What is a good sign that my qualification questions are too long?
A noticeably high drop-off rate partway through the questions is the clearest signal. If most leads answer the first question but disappear by the third, the flow is likely asking for more than the moment warrants.
How is lead qualification different from lead scoring?
Qualification is the process of gathering the information (like BANT answers); scoring is the rule that turns those answers into a hot, warm or cold label used to decide what happens next.
Should qualification questions be different for WhatsApp versus a website chat widget?
The core questions are usually the same, but tone and pacing often differ โ a WhatsApp conversation tends to feel more natural asking one question per message, while a website widget can sometimes group two related questions together.
Related reading
Available across India โ see WhatsApp & AI calling automation by state and city.