A lead qualification chatbot for SaaS demos: team size, use case, timeline

Updated 2026-09-19 · 5 min read · By the Convo360 team

Why generic contact forms underperform

A plain "Contact Us" form on a SaaS website tells you almost nothing about fit until someone on sales manually reviews it, often a day later. A qualification chatbot asks the right questions immediately, while the visitor is still on the page and interested.

The delay itself is the bigger cost, a visitor who filled a form with genuine intent to buy this quarter has usually moved on to evaluate two other tools by the time a day-old form submission gets reviewed and a callback gets scheduled.

A generic form also treats every submission the same, whether it's a 5-person startup exploring options or a 200-person team ready to buy this month, both get the same "someone will reach out" auto-reply and land in the same undifferentiated queue for a rep to sort through manually.

Pricing-page and demo-page visitors in particular are showing strong intent just by being there, routing them through the exact same generic form as someone reading a blog post wastes that signal instead of acting on it immediately with a targeted conversation.

The three qualifying questions

A List Menu or Ask a Question sequence covers team size, primary use case, and rough timeline to buy. These three, more than company name or job title alone, tell you whether this is a demo-ready lead or an early-stage browser.

• Team size: under 10, 10-50, 50+
• Primary use case: pick from your product's known top use cases
• Timeline: this month, this quarter, just exploring

Phrase the use-case question as a menu of your product's actual top use cases rather than an open text box, a visitor picking from options like "Automating customer onboarding" or "Managing sales pipeline" gives you a cleaner signal than free text, and it's also faster for the visitor to answer with a single tap.

Scoring and branching automatically

Condition blocks evaluate the combination of answers, larger team plus near-term timeline scores as sales-ready, smaller team plus "just exploring" scores as nurture. The branch decides what happens next without a human reviewing each response first.

Booking the demo in chat

For sales-ready leads, the flow offers available demo slots directly, confirming the booking in the same conversation. This immediacy, booking while intent is highest, converts noticeably better than sending a scheduling link to check later.

If your team can support it, add an option for an immediate live chat handoff instead of only a scheduled slot, a visitor who's ready to talk right now, mid-browsing, often converts better with a real-time conversation than with a slot booked for three days out, by which point their attention has moved elsewhere.

Building it on Convo360

Here is how to set this up on Convo360.

1. Add the web chat widget to your site and trigger the flow on new conversation.
2. Use List Menu and Ask a Question blocks for team size, use case and timeline, storing each with Set Variable.
3. Add a Condition block scoring the combination into sales-ready or nurture.
4. For sales-ready, offer demo slots and confirm the booking directly in chat.
5. For nurture leads, use Save CRM lead and a Wait / Delay sequence for follow-up content over the following weeks.

See web widget docs and CRM docs.

Trigger the widget to open the qualification flow proactively on high-intent pages, pricing, a specific feature page, rather than waiting passively for the visitor to click the chat icon themselves. A gentle, well-timed prompt on these pages converts noticeably more browsing visitors into an actual qualifying conversation than a widget that only reacts when clicked.

Mistakes to avoid

Asking too many qualifying questions before offering any value is the most common mistake, visitors will drop off partway through a five- or six-question interrogation. Three focused questions, as above, is usually the right ceiling; anything a rep needs beyond that can be asked live once the demo is actually booked.

A second mistake is a nurture path that goes silent after the first message. "Just exploring" visitors are still a real pipeline, a short, spaced-out sequence of genuinely useful content (not repeated demo pitches) over a few weeks keeps the door open without feeling like a hard sell they already declined.

A third, subtler mistake is scoring purely on company size and ignoring intent signals the visitor already gave, someone who came from a comparison-page search and asked a specific integration question is often more sales-ready than a larger team just casually browsing the homepage, even if the size-based score alone would rank them lower.

What it costs

This runs on the Starter plan (₹999/month, ex-GST) for the widget, flow builder and CRM pipeline. Business plan (₹7,999/month, ex-GST) is worth it once you want the REST API to sync qualified leads into a separate sales CRM automatically. Whichever plan you start on, track two numbers weekly in analytics: what share of chat visitors complete all three qualifying questions, and what share of sales-ready leads actually book a demo slot. A drop between those two numbers usually means the demo-slot offer itself needs a clearer call-to-action, not that the qualifying questions are wrong.

Example conversation

Frequently asked questions

Related reading

Available across India — see WhatsApp & AI calling automation by state and city.