Lead Capture

Overview

When the chatbot cannot answer — or the visitor asks for a person — a short form appears in the widget. You get the name, phone, email, and a note. An email goes out. An optional webhook can hit your CRM. The lead sits on the Leads page.

Available on: Smart and Professional. Industry starters turn this on by default.

This is a callback request, not a live diary. The bot does not check availability or reserve a slot.

When the form shows

• The visitor asks for a human, or
• The bot misses twice (your fallback setting).

You choose which fields are required. Home-services defaults to phone required.

What you get

• Email on every new lead (addresses you set on the Leads settings card).
• Optional public https webhook, signed with X-AIInSync-Signature: sha256=… so you can trust the payload.
• Statuses, notes, and CSV export on the Leads page.
• Monthly count on the Outcomes report.

Localhost and private IPs are rejected for the webhook (SSRF protection). Slack and Teams are not built in yet — point the webhook at a tool that already routes alerts.

How to turn it on

1. Open the project → Leads. 2. Enable lead capture and pick required fields. 3. Add notify emails. Optionally add a webhook URL and send a test. 4. Embed the chatbot. Ask “can someone call me?” on a test page.

Next steps

• Industry Starters — start with lead capture already on.
• Outcomes — how many leads you took this month.