Lead capture

Decide when the widget offers visitors a contact form, which fields it asks for, what the consent text says, and where the contact details you collect go next.

Last updated October 21, 2026

On this page

Lead capture is the short contact form the widget offers visitors, so a question your agent can't answer, or a visitor who wants to talk to a person, still reaches your team. You set it up in the Lead capture section of the dashboard's Agents page.

When the form is offered

Under Offer the contact form, choose one of three options:

Option	What visitors see
When the agent can't answer	The default. When the agent finds no answer in your knowledge, the form opens under its reply.
Always	A Leave contact details button is always available in the panel, so visitors can leave their details at any point.
Never	No contact form. The agent says when it doesn't know, without offering one.

With either of the first two options, the form also opens when a visitor asks to talk to a person, for example "Can someone call me?".

Once a visitor has sent their details, the widget doesn't offer the form to them again in that browser.

Which option to choose

When the agent can't answer suits most sites: visitors who get their answer aren't interrupted, and those who don't get a way forward.
Always suits sites where every conversation should end with a contact, such as a consultancy or a B2B site with a sales team.
Never suits sites that handle contact elsewhere, such as a support portal with its own ticket form. Mention that place in a Q&A pair or your greeting, so the agent can point visitors to it.

Fields

The form always asks for an email address; it is the one required field. Under Also ask for, tick the extra fields you want: Name, Company and Phone. Extra fields are optional for the visitor.

Each extra field makes the form a little longer. Ask only for what your team uses to follow up: for most B2B sites that is name and company; add phone only if you actually call people back.

Before sending, the visitor ticks a checkbox next to the Consent text. The default is "I agree that [your site name] may contact me about my request." You can rewrite it, up to 300 characters, for example to match the wording your lawyer prefers.

Add your Privacy policy link, the full address starting with https://, and the consent text links to it. Leave it empty for no link.

Your company decides what happens with the contact details visitors leave: for the visitor's data, your company is the controller and ASDK processes it on your behalf. Describe the chat and the form in your own privacy policy. ASDK's Data processing addendum covers our side.

What visitors see

The form's heading is "Leave your contact details", with "We'll reply by email." under it. It has the fields you chose, the consent checkbox and a Send button, plus Not now to close it. After sending, the visitor sees "Thanks! We'll be in touch soon."

The form's own labels follow the visitor's language in the widget's eight interface languages. Your consent text is shown as you wrote it.

Where leads go

Each form sent creates a lead with the visitor's details, the page they were on and a link to the conversation.

Leads page. Leads are listed on the dashboard's Leads page, with statuses and a CSV export. See Leads and CSV export.
Email and Slack. Each new lead is emailed to owners and admins and can be posted to a Slack channel. See Notifications.
Your own code. The widget raises a lead event in the visitor's browser, so you can pass leads to your analytics or tag manager:

HTML

<script>
  window.asdk = window.asdk || function () { (asdk.q = asdk.q || []).push(arguments); };
  asdk("on", "lead", function (lead) {
    window.dataLayer = window.dataLayer || [];
    window.dataLayer.push({ event: "asdk_lead", leadId: lead.leadId });
  });
</script>

The event carries leadId, email, name, company, phone and conversationId. Avoid sending email addresses or phone numbers to analytics tools: pass the lead ID instead. See JavaScript API.

The Sales agent, included from the Pro plan, can also qualify leads, book meetings and send leads to a CRM. See the Sales agent.

Prefill for signed-in visitors

If visitors sign in to your site, pass their details with asdk("identify", { email, name }) and the form is prefilled for them. See Identity verification.