Lead capture
Understand how an agent asks for contact details and delivers qualified leads to a connected CRM.
1 min read
- Project
- Assistant
- Lead capture
Open an assistant’s Lead capture tab to see the visitor form controls; use Integrations to connect the CRM that receives approved submissions.
Lead capture turns a helpful conversation into a respectful handoff. The agent answers first, then shows an inline form only when its configured “When to ask” guidance fits the visitor’s request or intent.
Set up the handoff
Follow the one route that matches your next decision.
Set up the project’s HubSpot or Salesforce destination first.
ConfigureConfigure and test lead captureMap fields, choose the moment to ask, set consent, and prove a synthetic delivery.
DeliveryUnderstand provider-specific deliverySee current HubSpot and Salesforce requirements and recovery paths.
Keep the visitor experience respectful
- Ask after answering the visitor’s question, not instead of answering it.
- Describe visitor situations in “When to ask”; do not put implementation instructions there.
- Check CRM-required fields: HubSpot needs email; Salesforce Lead needs last name and company.
- If explicit consent is required, verify the checkbox, privacy notice, and destination before publishing.
After successful CRM delivery, Chat4U scrubs lead PII from its lead record; delivery logs contain no visitor PII and the CRM is the system of record. This does not replace your own privacy obligations.
Last updated on