🎯 Lead Capture

Automatically capture, qualify, and organize leads from conversations.

Lead Capture turns your AI agent into a passive lead generation engine. As visitors chat with your agent, it naturally collects contact details and silently infers their intent from the conversation. All captured leads appear in the Leads tab of your agent dashboard, ready to export as CSV.

No forms. No pop-ups. Just a conversation.

What Gets Captured

• Email — required; used to identify and deduplicate leads
• Name — optional; configurable as required or optional per agent
• Phone — optional; configurable as required or optional per agent
• Intent — automatic; inferred from the conversation (see Intent Detection)
• Location — automatic; approximate city, region, and country from the chat session

All fields are stored automatically — no manual setup or forms required.

When to Use Lead Capture

Use this when you want to:

• Collect inbound leads from your website without a separate form
• Qualify visitors automatically based on what they discuss
• Follow up with prospects after conversations end

Enabling Lead Capture

Step 1 — Enable the tool

Go to your agent’s Tools tab and enable the Lead Capture tool. This makes the tool available to your agent at runtime.

Step 2 — Configure which fields to collect

Once enabled, you’ll see a Lead Capture Fields section. Choose which contact details your agent should collect:

• Email — required; cannot be disabled
• Name — can be toggled on/off; mark as required or optional
• Phone — can be toggled on/off; mark as required or optional

Fields marked required are collected early in the conversation before the agent moves to deeper assistance. Fields marked optional are asked naturally later, after the required fields are already captured.

Configuring Timing (via Prompt Builder)

Open the Prompt Builder (✨ Build button on the Instructions field) and navigate to the Lead Capture section. Choose when your agent should ask for contact information:

Ask upfront, before helping

The agent asks for contact details at the very start of the conversation before providing any assistance. Best for gated services where access requires registration, or high-intent landing pages where every visitor is a qualified lead.

Ask naturally after 2–3 exchanges

After a few back-and-forth messages, the agent naturally weaves in a request for contact details. This is the recommended default — it warms up the visitor before asking, which reduces drop-off.

Only when user shows intent

The agent waits until the user signals real intent — mentioning pricing, requesting a demo, describing a project, or asking about next steps. Best for content sites, support agents, or any context where most visitors are browsing and only a subset are qualified leads.

Intent Detection

Your agent automatically infers the visitor’s intent from the conversation and updates the lead record silently — no configuration needed.

Intent is classified into the following categories:

• Pricing — visitor is asking about cost, plans, or pricing tiers
• Demo — visitor wants to see the product in action or schedule a demonstration
• Sales — visitor is evaluating for a purchase decision
• Support — visitor needs help with an existing product or service
• Booking — visitor wants to schedule a call, meeting, or appointment
• General — visitor is asking general questions without a clear purchase signal
• Partnership — visitor is interested in a business collaboration
• Job Applicant — visitor is asking about open roles or career opportunities

As the conversation develops, the agent updates the lead automatically as stronger signals emerge. The agent never asks the user what their intent is — it reads the context.

Examples

Basic capture

User: “I’m interested in your pricing plans.”

Agent: “Sure — I can walk you through the options. Would you like me to send detailed pricing to your email?”

User: “Yes, it’s [email protected]”

Agent: “Great — I’ve got that. I’ll share the details with you. Let me know if you’re looking for anything specific.”

Lead saved with Email: [email protected] · Intent: Pricing

Intent progression

User: “Do you offer demos?”

Agent: “Yes, I can arrange a demo for you. What would you like to see?”

User: “We’re evaluating tools for our team.”

Agent: “Got it — I can set up a demo tailored to your use case. What’s the best email to send the invite to?”

User: “[email protected]”

Lead saved with Email: [email protected] · Intent: Demo

How Leads Are Stored

• No duplicates — leads are upserted by email per agent. If the same visitor returns and provides more information, their record is updated, not duplicated.
• Geolocation — the visitor’s approximate city, region, and country are captured automatically from their chat session.
• Real-time — leads appear in the Leads tab immediately after the agent captures them.
• Export — download all leads as a CSV from the Leads tab at any time.

Tips & Best Practices

• Use ask upfront only if your service genuinely requires contact info before access. Asking too early on informational sites will cause visitors to abandon the chat.
• A warm, friendly agent persona significantly reduces drop-off when asking for contact details. Configure tone in the Prompt Builder.
• You don’t need to collect all three fields. Email alone is often enough to qualify a lead — add name/phone only if your sales process requires them.
• Check the Leads tab regularly. Leads are captured in real time and visible immediately.
• After enabling Lead Capture or changing field settings, use the Prompt Builder to regenerate and re-apply the system prompt so the agent reflects the updated configuration.

Note: The agent automatically rejects placeholder or test email addresses (e.g. [email protected], [email protected]). If a user provides an obviously fabricated email, the lead will not be saved and the agent will ask for a valid address.