AI lead qualification agent
Qualify website leads before they reach your team.
MadeAgentic is a voice and text website agent that answers visitor questions from your business knowledge, asks configured questions about need, fit, and timing, and captures context for follow-up. Core includes Calendly and Cal.com: after qualification, the agent opens the calendar inside the chat and the visitor chooses a time.
Workflow updated
Website qualification agent
Answer first, then decide the route
Need
Client onboarding
Timing
Before September
Fit
Supported workflow
Next step
Offer a scoped consultation with the context attached
What AI lead qualification actually does
Do more than capture an email or assign a score.
A qualified outcome is a decision with context. The visitor gets a useful answer and the business knows whether to book, follow up, share a resource, hand off, or stop the path.
Lead capture
Collects details
Useful when a person already knows they want a reply, but it does not establish fit or the right route.
Lead scoring
Assigns a value
Useful after data exists, but a score does not answer the visitor or complete the next step.
Lead qualification
Makes the next decision
Answers, checks fit and intent, then prepares an explicit outcome for the visitor and the team.
New to the product category? Start with the MadeAgentic AI website agent overview.
How website lead qualification works
The agent earns the next question, then earns the next step.
The flow starts with the visitor's reason for arriving. Qualification comes after the agent has understood and answered enough to make the questions useful.
Step 1
Answer the blocker
Resolve the pricing, fit, process, availability, or capability question that stopped the visitor.
Step 2
Understand the need
Ask what they are trying to accomplish and what is happening now before applying qualification rules.
Step 3
Check fit and intent
Ask only for the constraints, timing, and readiness signals that change the next step.
Step 4
Route deliberately
Open booking, share a resource, capture a follow-up, decline politely, or prepare a human handoff.
Step 5
Send useful context
Give the team the stated need, answers, objections, timing, and next step instead of a cold notification.
Configure the workflow
How do I qualify visitors before Calendly or Cal.com?
Use a Core agent to answer questions, collect the details that change fit, and then offer your existing calendar. Core costs $99 USD per agent per month, with a 30-day trial and no credit card required. See plans and fair-use terms.
Step 1
Add approved knowledge
Create an agent from your website. Review its knowledge and add the service scope, pricing, and exclusions that visitors need before a call.
Step 2
Set the qualification objectives
In the objective editor, use Agent task for the questions to ask and Done when for the completion criteria. For the fictional example below, collect use case, team size, and timing before offering a consultation.
Step 3
Connect your calendar and handoff
Add a Calendly URL or Cal.com link in Connections. Configure the booking objective to offer the calendar after the fit questions. Set the custom extraction fields you need in the lead summary; Core also supports Slack notifications.
Step 4
Test before embedding
Try a supported enquiry, a poor-fit enquiry, and a visitor who asks to skip the questions. Check the conversation and captured output. Test browser voice with microphone permission and text without it. Review the flow before adding the widget to your site.
The visitor selects a time in the calendar widget. Opening the calendar is not a completed booking: MadeAgentic cannot check availability or reserve a slot on the visitor's behalf. Keep a human follow-up path for unclear requests.
For a SaaS-specific conversation, see the SaaS qualification demo.
Illustrative example · fictional visitor and business
The same visitor question can create a cold inbox task or a prepared consultation.
“We need to replace a manual client onboarding process next quarter. Is that the kind of project you take on?”
Requests name, email, and a message
The visitor repeats the question without knowing whether the project is supported.
Creates a cold inbox notification
A person still has to answer, discover the current process, and establish timing later.
Answers the fit question
Confirms that workflow redesign and implementation are supported.
Asks what changes the route
Collects the use case, team size, and timing: client onboarding, eight internal users, next quarter.
Offers the right consultation
Opens the existing calendar after the scope and timing fit. The visitor selects an available time.
“Use case: client onboarding redesign. Team size: eight internal users. Timing: next quarter. Email requests and lost approvals delay setup. Consultation offered after fit check; booking not yet confirmed.”
Illustrative output, not a customer result. Review the captured fields in your dashboard; Core can also notify your team in Slack. A calendar opening does not establish a booking or a closed project.
Signals worth qualifying
Ask what changes the decision. Skip what does not.
A long questionnaire is still a form. Good qualification uses the fewest questions needed to choose a responsible next step.
Need and use case
What is the visitor trying to get done, and does it match what the business actually offers?
Fit and constraints
Check the service, location, workflow, team, technical, or eligibility constraints that affect the route.
Timing and urgency
Separate an active need from early research without treating every researcher as a bad lead.
Readiness
Understand what they have tried, what is blocking a decision, and whether a call is useful now.
Handoff context
Capture contact details only when there is a clear reason to follow up, then preserve the conversation context.
Route every outcome deliberately
Qualification should create more than one possible answer.
If every path ends at the same calendar, the agent is collecting information, not making a useful qualification decision.
Qualified and ready
Open the right booking or demo path
The visitor has a supported need, enough context, and a reason to speak now.
Qualified, not ready
Share a resource or capture follow-up
Keep the relationship useful without forcing a premature sales call.
Sensitive or unclear
Prepare a human handoff
Route questions that require judgment with the context already collected.
Not a fit
Close the path politely
Do not open a calendar when the need is unsupported or the next step would waste both sides' time.
Good fit
Use it when context changes what should happen next.
- The visitor usually has questions before they book, request a quote, or ask for a demo.
- Your team repeats the same fit and intake questions during follow-up.
- Different needs should route to different people, resources, or outcomes.
- A prepared handoff is materially more useful than a name, email, and blank message.
Poor fit
Do not add a qualification agent where a simple path is clearer.
- The site receives too little relevant traffic to learn from conversations.
- The request is purely administrative and the same form works for everyone.
- The decision requires professional judgment before any qualification questions are safe.
- The business has not defined fit, exclusions, routing, or approved answers yet.
Qualification by business model
Keep the generic workflow here. Put the real criteria on the vertical page.
SaaS buyers and coaching prospects should not receive the same questions or routes. Each agent needs the business's actual decision rules.
For SaaS
Qualify pricing-page and demo intent.
Check use case, workflow, company context, timing, and blockers before trial, demo, docs, or sales follow-up.
AI lead qualification for SaaSFor coaches
Check fit before the calendar opens.
Understand the goal, current situation, timing, readiness, and service fit before offering a discovery call.
AI lead qualification for coachesChoose the next useful page
Design the logic, inspect the current path, or compare the old default.
Lead qualification checklist
Define fit, questions, routes, handoffs, and edge-case tests.
Website lead generation audit
Find static forms, premature booking, and missing first response.
Contact form alternative
Compare passive capture with interactive lead qualification.
Demo request comparison
See the qualification layer before a SaaS demo handoff.
Protecting a coaching calendar? See how to qualify before opening Calendly.
FAQ
AI lead qualification questions
What is an AI lead qualification agent?
It is a website agent configured to answer a visitor's first question, understand the need, check the fit and intent signals that matter to the business, and route an appropriate next step. It should prepare a useful outcome, not merely label a lead.
How is lead qualification different from lead capture?
Lead capture collects contact details. Lead qualification establishes whether the need is supported, what context matters, how ready the visitor is, and what should happen next. A qualification flow may capture contact details, but only after there is a useful reason to follow up.
What qualification questions should an AI agent ask?
Ask only questions that change the route: the visitor's goal, current situation, relevant constraints, timing, and what they have already tried. Budget, authority, or company size belong in the flow only when those answers genuinely affect fit or the next step.
Does the agent replace sales or human follow-up?
No. It handles the repetitive first-response and qualification work, then gives a person better context. Humans should still handle judgment, sales conversations, professional advice, sensitive requests, and unusual edge cases.
Can qualified leads be routed to Calendly, Cal.com, a demo, or contact capture?
Yes. Core includes configured qualification objectives, Calendly and Cal.com booking, and custom data extraction for follow-up. The agent opens the calendar inside the chat; the visitor chooses the slot. MadeAgentic cannot read availability, reserve a time, or confirm a booking independently. Resource, payment, and custom API actions need separate early or advanced access.
What happens to weak-fit or not-ready leads?
Not-ready visitors can receive a useful resource or a later follow-up path. Unsupported needs can receive a clear, polite response without opening booking. The purpose is to choose the right next step, not to push every visitor into a call.
Does AI lead qualification work for SaaS, coaches, and service businesses?
Yes, when each agent uses criteria and routes that match the business. SaaS teams may qualify use case and demo intent, coaches may protect discovery-call time, and service businesses may prepare a quote, appointment, or callback with context.
Give every website lead a useful first decision.
Generate a first agent from your website, define the fit and routing rules, and test the full conversation before visitors see it.
About 60 seconds