Help first, ask the few questions that matter, then book the meeting. A practical setup for AI lead qualification on your website.
Picture the head of finance at a 120-person logistics company on your pricing page at 8:40 on a Monday evening. She has a budget approved, a board meeting in six weeks and two other vendors on her list. Your website gives her a contact form that says "We'll be in touch within one business day."
By the time someone is in touch, she has had two demos elsewhere. Nothing about that lead was bad. The process around it was slow.
I build AI chat agents for a living, so I have a stake in this. I've already written about why the first five minutes matter and how to get every chat lead into HubSpot, so I won't repeat that here. This post is the practical part in between: how to set up an agent that qualifies a lead, books the meeting and routes it to the right person.
What buyers are telling us
Gartner surveyed 632 B2B buyers in August and September 2024. 61% said they prefer an overall rep-free buying experience. The same release reports that 73% actively avoid suppliers who send irrelevant outreach.
Put those together and you get a useful rule for lead qualification. Let people get their answers first. Ask only the questions that change what happens next. And when you do reach out, make it relevant, because you already know what they need.
Step 1: Write down what "qualified" means
Do this before you touch any software. Most teams have a definition in their heads, and everyone's is slightly different. Pick three to five things that genuinely change your next step. For a software company, that might be:
- Company size or number of users.
- The problem they're trying to solve.
- Timeline: this quarter, this year or just looking.
- Their role: decision maker, evaluator or researcher.
- Region, if different teams cover different markets.
Leave out anything sales won't use. Every extra question costs you some visitors.
Step 2: Let the agent answer first, then qualify
In AtomicX, the agent sits in an AI Chat node in your workflow, with a knowledge base of your product and pricing content. That's the help-first part. Our AI agents guide covers the basics, and the agent gallery has prebuilt starting points you can copy with Add to my agents.
For the qualifying questions, you have two good options:
- Let the agent ask conversationally. Put the questions in its instructions and let it work them in naturally.
- Offer a structured workflow. Under Callable workflows on the agent, attach a short workflow with your questions. The agent offers it when it fits, and the visitor clicks Start or Not now. Saying "yes" in chat doesn't start it. The answers come back to the agent under Fields returned to the agent, so it can carry on the conversation with them. The details are in Let an AI agent offer a workflow.
When a visitor asks for a demo or a sales follow-up, the AI can show an inline form for their missing Name and Work email, with Company (optional). Details the chat already has are reused, and visitors can keep asking questions while the form is open.
Step 3: Book the meeting in the chat
This is the step that turns an evening lead into a calendar entry. Set up the calendar first (it connects to Google or Microsoft 365), then add a Book Appointment node to the workflow. On the agent, select the Book an appointment skill so it can open the booking flow when someone asks.
The visitor picks a day and time, in their own time zone, and gives a name and email if the chat doesn't have them yet. A free employee gets a tentative event and an email with Accept and Decline buttons. The visitor gets a "Confirmed" email once it's accepted. Your team stays in charge of its own calendar.
One honest limit: callable workflows can't include appointment booking or handoff nodes. Put those in the main workflow, which is where they belong anyway. The full steps are in Appointment booking in chat.
Step 4: Route it
Not every lead needs the same treatment. A Condition node can send the conversation down different branches, and with Condition Type set to Orchestrator, the AI picks the best branch. You can also use an AI execution condition written in plain language, such as "the visitor has more than 50 users and wants to start this quarter".
For hot leads, a Handoff node passes the chat to your team straight away. Anyone can reply from Live monitor, and if you use Slack with widget sync, from Slack too. Then the lead goes to your CRM. HubSpot has a built-in integration. For other systems, the Webhook integration sends conversation events, including the answers your workflow collected.
Sample agent instructions
Here's an example for a hypothetical project-management software company. It's a starting point, not a template to paste in unchanged.
- You are the website assistant for Brightline, project-management software for construction firms.
- Answer questions from the knowledge base first. Never guess prices, discounts or contract terms.
- Once you've answered the visitor's question, and only if they seem to be evaluating, ask up to three questions: how many people would use it, what they use today, and when they want to start.
- Ask one question at a time. If the visitor doesn't want to answer, carry on helping.
- If they want a demo, a quote or to talk to sales, offer to book a meeting. To schedule a demo or meeting, always use the Book an appointment tool. Never say a meeting is booked yourself.
- If they mention more than 200 users or a security review, tell them a specialist will follow up, and collect their work email.
- Don't ask for a phone number unless they ask for a call.
The line about the booking tool comes straight from our help pages. Without it, an agent may tell a visitor "you're booked" when no request was sent.
How to measure it
Count the things that matter to sales, not just chat volume:
- Meetings requested and accepted. Every booking request goes to a person to accept or decline, so track both numbers. If many are declined, check that the hours on offer are realistic.
- Qualification rate. Under AI → Improvements, reviewers can choose Also review qualification and enter your Tenant qualification criteria. Criteria are versioned, so a change in definition doesn't muddle the numbers.
- Form completion and delivery. Recorded outcomes · last 30 days reports form completion, offer acceptance and delivery success.
- Handoffs and completion. Insights → Analytics shows Handoffs by day and the Completion Rate.
A fair caveat from our own docs: these metrics describe recorded results. They don't prove a release caused a conversion increase. Compare like with like, and talk to your sales team about lead quality.
Pitfalls
- Interrogating before helping. If the first thing a visitor sees is five questions, many will leave. Answer first.
- Two tools for one job. If the agent has both Book an appointment and Schedule a callback, it may pick the wrong one. Our docs suggest removing the callback skill.
- Handoffs nobody answers. A handed-off chat with no activity for 30 minutes is marked Abandoned. Only add a handoff where someone is watching.
- Trusting the form, not the CRM. A form shown in chat isn't proof the lead arrived. Run a test lead end to end and check the record.
- Calendar gaps. If no employee has free times, the visitor sees no slots. Check hours, notice periods and each employee's Active setting.
The bigger pattern
Lead qualification used to mean a form with eight required fields. Buyers have made it clear they'd rather research on their own. The job now is to help first, ask the few questions that matter, and get a person on the calendar while the buyer still cares.
Want to see this flow on your own site? Book a 20-minute demo, or read the booking setup guide first.