Yes. It classifies visitor intent from the first message, then routes prospects into a qualification flow and customers into first-line resolution — both pulling from the same shared knowledge base. This guide covers how that intent-routing works, the five visitor types your agent needs to catch, and the rare cases where two separate agents beat one.
of B2B buyers already used AI while making a recent purchase
of B2B companies never respond to a demo request at all
median cost of an assisted service contact, versus $1.84 for self-service
Before You Scroll
Intent is the router.
The first message tells you whether a visitor is buying or stuck — classify it before doing anything else.
Two flows, one brain.
Prospects and customers follow different paths, but both paths should draw on the same shared knowledge base.
Never one metric.
The lead flow answers to qualified pipeline; the support flow answers to resolution rate — a blended average hides failure in both.
Splitting is the exception.
Two separate agents make sense at high volume or under strict compliance — not as a default architecture.
Why Are Leads and Support Still Two Separate Funnels on Your Site?
Most websites are built around a guess: that visitors will sort themselves into the right lane. Prospects find the contact form; customers dig up the help widget buried in the app or the docs. Then reality hits — a paying customer lands on the pricing page from a Google search, and a ready-to-buy evaluator clicks “Support” because it’s the only visible way to reach a human.
The structural problem: the split forces visitors to classify themselves — decide, unprompted, whether they’re a lead or a support case — before you’ve earned that effort. Every misroute costs you in a different currency: a prospect stuck in a ticket queue goes cold inside the response window, while a customer pushed through a lead form burns loyalty proving they already pay you. Skip intent routing, and the problem doesn’t disappear — it lands on your most impatient audience, while you’re still paying for two tools and two teams to reconcile them.
| Approach | What prospects get | What customers get | The structural gap |
|---|---|---|---|
| Static forms + contact email | A form and “we’ll be in touch” | A ticket queue measured in days | No qualification, no instant answers, no routing |
| Human-staffed live chat | Fast answers during staffed hours | The same queue, the same hours | Does not scale; coverage gaps kill off-hours conversions |
| Separate lead tool + help widget | A scripted capture flow | A deflection-first widget | Two data silos; visitors must self-classify |
One dual-purpose AI agent (the approach Landbot takes) Best fit | Instant lead qualification, routed to the CRM | First-line resolution, logged to the helpdesk | Closed: intent routing from message one, one shared knowledge base |
The last row isn’t a bigger tool — it’s a different architecture. The classification step moves from the visitor’s guesswork to the conversation itself. For the deeper structural breakdown of why SaaS sites lose leads this way, see our guide on the six structural lead-generation problems every SaaS site has.
What Is a Dual-purpose AI Agent?
A dual-purpose AI agent is conversational AI for websites that classifies each visitor’s intent at the start of the conversation, then runs one of two flows from a shared knowledge base: lead capture and qualification for prospects, or first-line issue resolution for existing customers. It replaces the separate capture tool and support widget most sites operate in parallel, and it hands off to a human — with full context — whenever confidence drops or stakes rise.
How It’s Different From Live Chat and Forms
Live chat is a channel: it still needs a person on the other end, which means business hours and a “leave a message” fallback right when high-intent traffic shows up. An agent is a worker on that channel — it holds the conversation, takes actions like creating a CRM record or opening a ticket, and treats human handoff as its escalation path rather than its default.
Forms are quieter but just as costly: they collect fields but can’t notice a churn risk in the message box, or that someone asking about integrations is an onboarding customer, not a lead. Every form field is a question you ask without listening to the answer. A dual-purpose agent asks the same questions conversationally and routes the result to the right system instead of a shared inbox. For more on why forms specifically fall short here, see can an AI agent replace forms on your website?.
Running two agents just recreates this split — a second knowledge base to keep in sync, and a second set of blind spots wherever a visitor doesn’t fit neatly into either box.
What Conversations Does Your AI Agent Actually Need to Handle?
Every conversation your website starts falls into one of five buckets. The agent does not need fifty intents — it needs these five classified reliably, because each one has a different right answer, a different destination system, and a different definition of success.
They don’t want a demo — they want to know whether you solve their problem.
Early-stage prospects open with capability questions: does it integrate with their stack, how does pricing scale, what does setup involve. The agent’s job here is to answer substantively from the knowledge base and capture light context — use case, company size — without deploying the full qualification battery. Over-eager lead qualification is the fastest way to lose this bucket; the visitor came to learn, and the agent that teaches earns the follow-up question a form never gets.
- Typical openers: “Does this work with…?”, “How does pricing work?”
- Right ask: one or two context questions, never a five-field interrogation
- Exit: tagged in the CRM as early-stage, or a genuinely self-served answer
This is the conversation your pipeline depends on — and the one slow responses lose.
Evaluators arrive with vendor shortlists, migration questions, and timelines. This is where full lead qualification runs: company size, use case, timeline — enough to route accurately, nothing more. Speed is the whole game — most companies don’t even reply to a demo request, let alone reply fast, and an agent makes instant the default. The exit should be concrete: a CRM record created, a trial started, or a conversation routed to sales while intent is hot. For the full playbook on qualifying and routing these visitors, see our AI agent for lead generation guide.
- Signals: pricing-page entry, “migrating from…”, team-size and timeline mentions
- Qualify on three dimensions — company size, use case, timeline
- Exit: routed to sales or into a trial, with the CRM record already created
Every minute a customer spends proving they’re a customer is loyalty burned.
Customers announce themselves through signals, not declarations: an account email, a logged-in session, product vocabulary a prospect would never use. Once detected, the flow flips from capture to resolution — answer from the shared knowledge base first, because that is where ticket deflection actually happens, and escalate to the helpdesk with the transcript attached when the issue needs a human. What must never happen is the default many split-tool sites ship: a paying customer being asked for their company size.
- Detect via account email, login state, or product-specific vocabulary
- Resolve from the shared knowledge base before creating a ticket
- Exit: resolved and logged, or escalated with the full transcript
High stakes, low complexity — the flow where accuracy beats cleverness.
Invoices, seats, renewals, cancellations: most of these resolve with a link to the right document or a precise policy answer, which makes them ideal for automation — and dangerous to improvise. The rule set is strict: verify identity before surfacing anything account-specific, answer policy questions only from documented sources, and route payment disputes and cancellation requests to a human by design, not as a failure state. Handled this way, billing becomes the highest-deflection, lowest-risk lane in the whole setup.
- Verify identity before surfacing anything account-specific
- Answer from documented policy — never improvise on money
- Exit: self-served, or routed to the billing queue with details attached
The bucket that decides whether your routing gets trusted or resented.
Some visitors open with “hi”, “question”, or a paragraph that could be either flow. The discipline here is restraint: ask one clarifying question — two at most — and if confidence stays low, hand off to a human with whatever context exists rather than looping through menus. A fallback that fails gracefully is what makes the other four intents safe to automate aggressively; visitors forgive an agent that says “let me get you a person” and never forgive one that traps them.
- One clarifying question, never an interrogation loop
- Low classification confidence → human handoff, transcript attached
- Exit: reclassified into one of the four intents, or escalated with context
Three Things to Get Right
Getting a dual-purpose agent live is the easy part — getting it to route reliably takes deliberate setup. These three practices separate the teams who scale both flows cleanly from the teams patching a mess of misrouted conversations six months in.
Map both journeys first
Sketch both paths on paper before building anything — entry pages, questions asked, exit destinations. If you can’t draw the routing logic by hand, the agent can’t automate it.
Connect CRM and helpdesk on day one
A qualified lead that never reaches your CRM and a resolved issue that never logs to your helpdesk are both invisible work. Treat the integrations as the product, not the follow-up task.
Treat v1 routing as a hypothesis
Your first intent categories will be wrong in ways only real transcripts reveal. Review misclassifications weekly and expect two or three rounds before accuracy holds.
How the Routing Actually Works
The sweet spot is a single classification step followed by two purpose-built flows. Everything below is the minimum viable architecture — resist adding branches until transcripts prove you need them.
The intent-routing framework
First-message intent classification
Classify prospect, customer, or unclear from the opening exchange, using message content plus page context — before any menu or form field.
Prospect path
Qualify on company size, use case, and timeline, then create or update the CRM record while intent is still hot.
Customer path
Attempt first-line resolution from the shared knowledge base; log the outcome to the helpdesk whether it resolves or escalates.
Fallback to human with context
On low confidence or explicit request, hand off with the transcript, the detected intent, and every captured field attached.
One classification, four exits
Every conversation ends in the CRM, the helpdesk, a human’s queue, or a self-served answer.
The framework produces four outcomes. A qualified lead exits into the CRM with company size, use case, and timeline already structured. A resolved issue closes in the conversation and still logs to the helpdesk — deflected volume you can’t see is volume you can’t defend at budget time. Billing disputes and low-confidence cases route to a person by design; the savings come from what you safely deflect, not from removing humans entirely. A human handoff arrives in an agent’s queue with the detected intent and full history attached, so the customer never repeats themselves and the rep never cold-starts. And a self-served answer — the early-stage prospect who learned what they needed, the customer who found the setting — exits with nothing demanded in return, which is precisely why both come back. If a conversation cannot end in one of these four places, the flow has a leak; fix the destination before adding another branch.
Start with your highest-traffic page: one AI agent for your website, wired to your CRM and helpdesk. Measure both flows for two weeks, then expand.
Frequently Asked Questions
What is an AI agent for a website?
An AI agent for a website is conversational software that understands what visitors write and carries a goal-directed conversation instead of following a rigid script — it also takes actions like looking up documentation, creating a CRM record, or opening a ticket. Unlike a form, which only collects fields, or live chat, which still needs a person on the other end, a dual-purpose agent classifies visitor intent at the start of the conversation and routes leads and support to their own destination system. The result: the website becomes a working member of both the sales and support teams, not a brochure with two inboxes behind it.
What is the difference between a dual-purpose AI agent and a live chat widget?
Live chat is a channel; an agent is a worker on that channel. A chat widget inherits every constraint of the team behind it — staffed hours, queue depth, one conversation at a time — so off-hours visitors still hit a “leave a message” form. A dual-purpose agent runs lead qualification and first-line resolution autonomously, around the clock, and treats human conversation as its escalation path, not its default. The two complement each other: the agent handles the repeatable middle of both flows, and humans get only the conversations that need them, transcript and intent already attached.
How does intent detection work at the start of a conversation?
The agent classifies the first exchange using two signals: what the visitor writes, and the context around them. Message content carries most of the weight — “does it integrate with…” reads prospect, “my dashboard stopped loading” reads customer — while page context, login state, and account match sharpen the call without overriding it, since customers do land on pricing pages too. When confidence is low, the agent asks one clarifying question rather than guessing; if that doesn’t settle it, the conversation routes to a human with everything captured so far. Classification accuracy is then audited against real transcripts, not assumed.
Should the lead gen flow and the support flow share one knowledge base?
Yes — one source of truth, two behavior policies. Prospects ask support-flavored questions and customers ask sales-flavored ones, so a split knowledge base guarantees each flow fails on the other’s questions, and two knowledge bases inevitably drift out of sync. What should differ per flow is behavior, not knowledge: the prospect path qualifies and routes to the CRM, the customer path verifies identity and routes to the helpdesk, while both draw from the same maintained source.
When should a company split into two separate agents instead of one?
Split when ownership, not convenience, demands it. Three signals justify it: support volume grows large enough that the team needs to iterate on flows daily without coordinating with marketing; compliance or identity-verification requirements diverge sharply, as in fintech or healthcare; or the two audiences live on genuinely different properties, like an authenticated app versus a public marketing site. Even then, keep one shared knowledge base and a common intent taxonomy. Most teams start with a single dual-purpose agent and split only once transcript volume proves dedicated ownership beats shared simplicity.
How do you measure whether a dual-purpose agent is working?
Measure each flow against its own job, plus the router that feeds them. The lead flow answers to pipeline: qualification completion rate, qualified leads created, and speed from first message to CRM record. The support flow answers to resolution: first-contact resolution rate, ticket deflection rate, and escalation rate. On top of both sits classification accuracy — audited against a weekly transcript sample — and the fallback rate, since a rising “unclear” share means the intent categories need redrawing. Never blend the average across flows; a great support quarter can hide a broken lead flow inside it, and vice versa.
A full resource on resolving more tickets at lower cost with AI agents.