Capture leads
Collect visitor name and email address within the chat widget and route leads to your team automatically.
How it works
The lead capture tool shows a conversational form inside the chat widget — typically asking for the visitor's name and email address. You control when it appears: before the first message, after a set number of messages, or when the visitor asks a specific question.
Captured leads are stored in DGbot and can be forwarded to an external CRM or email via a webhook.
Configure lead capture
Go to Settings → Integrations and click Lead capture.
Open Integrations in adminLead capture configuration: form fields, trigger mode, and webhook settings.
Choose which fields to collect:
| Field | Always available | Optional |
|---|---|---|
| Name | — | Yes |
| Yes | — | |
| Phone | — | Yes |
| Company | — | Yes |
You must collect at least email. All other fields are optional.
Choose when the form appears:
| Trigger | When it fires |
|---|---|
| Pre-chat gate | Before the visitor can send their first message |
| After N messages | After the visitor has sent N messages (e.g., after 2 exchanges) |
| On intent | When the bot detects the visitor is interested in a quote, demo, or purchase |
| On escalation request | When the visitor asks to speak to a human |
Write a short message shown after the visitor submits the form:
> "Thanks, [Name]! Our team will follow up at [Email] within one business day."
Use [Name] and [Email] as placeholders — they're replaced with the visitor's actual values.
Toggle Lead capture on and click Save. The form is now active.
Trigger modes
Pre-chat gate
The form appears immediately when the visitor opens the widget, before they can type. Best for: high-intent landing pages, contact pages, or when lead quality matters more than engagement rate.
After N messages
The form appears after a configurable number of visitor messages. Best for: general website deployment where you want to qualify engaged visitors but not gate access.
On intent
The bot uses AI to detect purchase or qualification intent in the conversation (e.g., "I'd like a demo", "Can I get a quote?") and shows the form at that moment. Best for: lead generation bots where the primary goal is identifying interested buyers.
View captured leads
All captured leads appear in Conversations in the admin panel — each conversation record shows the lead's name, email, and the messages they sent.
Open Conversations in adminSend leads to your CRM
To forward leads to an external system, configure a webhook URL in the lead capture settings. When a lead is captured, DGbot sends a POST request to your webhook with the lead data:
{
"event": "lead_captured",
"conversation_id": "conv_abc123",
"chatbot_id": "bot_xyz",
"lead": {
"name": "Jane Smith",
"email": "jane@example.com",
"captured_at": "2025-05-15T10:30:00Z"
}
}Most CRMs (HubSpot, Salesforce, Pipedrive) can receive webhook data directly or via Zapier.