A lead comes in from a form, an ad, or a message. Someone has to answer, ask enough to know if the request fits, and put a real time on a calendar if it does. Those are three different steps. Answering is not qualifying. Qualifying is not a booked demo.
The first reply can be a chat or a call. It asks a short set of questions the team defined. The answers decide whether this person is ready for a demo, worth a later follow-up, or a poor fit. A demo is offered only in the first case, and only from times that are actually open.
Key takeaways
A lead is a person who asked to be contacted, asked for a price, or asked for a demo.
Qualification is a fixed set of questions: what they need, the budget, the timeline, and whether they can decide.
Hot, warm, and cold are labels from rules the team set. They are not a score the model invents.
A demo is booked only for a hot lead, and only into an open time on the connected calendar.
The answers and the booked time should land on the lead record, with the transcript.
Response time, conversion counts, and demo show rates are not results this article is reporting.
What the first reply is for
The first reply tells the person their request was received and asks what they want. It should not open with a pitch or a price. A support question is not a lead. If they only needed a known answer, that path stays in support, which is covered in What an AI Chatbot Handles in Support and Lead Capture.
The same questions can run in a chat, on WhatsApp, or on a call. The channel changes where the person answers. It does not change the rules.
The questions that qualify
Ask only what sales needs before it spends a meeting. Four answers are enough for most teams:
What they want help with.
Whether a budget exists, or the range they can name.
When they want to start or to talk.
Whether they can decide, or who else has to agree.
Stop when those are answered or when the person declines one. A longer list makes a warm lead leave. A missing answer is an incomplete lead, not a hot one.
The team can change the list for a source. A demo request from a pricing page can start at timeline. A vague “tell me more” should start at what they need. Do not ask every visitor for a phone number before you know which path they are on.
Hot, warm, and cold
The label comes from the answers, using rules the team wrote down.
Label | What the answers show | What happens next |
|---|---|---|
Hot | A clear need, a budget they can name, a near-term timeline, and a person who can decide | Alert sales and offer an open demo time |
Warm | Interest, but the budget, the timeline, or the need is still unclear | Store the lead and hand it to sales without booking |
Cold | Browsing, no budget, no timeline, or a request that does not fit | Store the lead and do not book a demo |
A warm lead can become hot on a later reply. Do not book the demo early to force the label. A cold lead is still a record. It is not a meeting.
How a demo gets booked
Offer times only after the lead is hot, and only times the calendar has opened.
Confirm the label out loud or in the chat: they want a demo, and the answers fit.
Offer a few open times. Do not invent a slot.
Book the one they accept.
Write the time, the answers, and the transcript to the calendar and the CRM the business has connected.
Send the confirmation to the address or number they gave.
If no time is open, or the calendar is not connected, the lead stays hot and a person books it. An unwritten time is not a demo. A reminder before the meeting is a later message the team has set up. It does not, by itself, mean the person will attend.
What the lead record should hold
Every finished qualification needs an outcome.
Hot, and a demo booked, with the time.
Hot, and waiting on a person because no time was open.
Warm, with the missing answer named.
Cold, with the reason it did not fit.
Left before the questions ended.
Sales should be able to open that record and see the transcript without asking the lead to repeat it.
Where a person steps in
The questions and the calendar handle a clean hot lead. A person takes over when:
The answers do not fit the categories the team set.
The lead asks for a person, or disputes the label.
The calendar has no open time, or the booking did not write.
The request is a complaint, or it is really a support issue.
The person gets the answers already collected. They do not restart the form.
What this is not
Qualifying a lead and booking a demo does not, by itself, prove a faster reply, more qualified leads, or a higher chance the person shows up. Those depend on the questions, the list, and whether the time was real. Treat this as a way to sort requests and to put a fitting lead on an open calendar, not as a measured conversion rate.
The same limit applies to “no lead missed” and to a demo that was only offered, not written to a calendar. An unanswered question is an incomplete record. A time that was never saved is not a meeting.
This is also not a support chat and not a keypad menu. Support answers a known question. A voice menu sorts callers by a key. Here the person has already asked for a conversation with sales, and the job is to decide whether that conversation should be a demo.
Explore Fonada
Lead generation for qualifying a request and booking a demo
What an AI chatbot handles in support and lead capture for separating a support question from a lead
WhatsApp for asking the questions in a chat thread
Voice AI for asking the same questions on a call