Configure lead capture

What you’ll accomplish

Set up one connected CRM, one small form, and one appropriate moment to offer it. Test with synthetic data before real visitors see it.

Finish with

One consent-aware form with a verified CRM delivery

Set up the handoff

1. Map the smallest useful formIn Integrations, open the connected provider and map each retained visitor field.

   Every field needs a visitor label, internal Field ID, type (Text, Email, or Phone), and CRM destination. Save the mapping before enabling it on an agent. HubSpot defaults are firstname, email, phone, and company; Salesforce defaults are LastName, Email, Phone, and Company.

2. Choose when the agent should askIn the agent’s Lead capture tab, select the tested CRM and write one qualifying moment.

   Make it useful, not automatic: “Offer the contact form after answering a visitor who asks for a sales callback or pricing discussion.” The agent should still answer in the same turn.

3. Make the notice and consent currentSet the disclosure beside the form, its privacy-policy URL where applicable, and explicit consent when required.

   With explicit consent enabled, submission requires the checkbox and records the notice hash, policy URL, acceptance time, disclosure-settings version, and locale.

4. Prove the complete pathTest the connection, trigger the qualifying moment in a synthetic conversation, then inspect Recent deliveries.

   A connection test does not create a CRM record. Use values such as Taylor Example and taylor@example.test. A successful delivery shows a CRM record ID; an error explains the failure.

Ready for real visitors

• The mapping has complete field IDs and CRM destinations
• The agent asks only at a genuinely useful moment
• The notice, policy URL, and consent choice are current
• A synthetic delivery has been reviewed in Recent deliveries

Provider requirements and safe mapping changes

• HubSpot requires a valid email for contact delivery.
• Salesforce requires Lead last name and company.
• One provider mapping is shared by every project agent that selects it. Before changing a Field ID or CRM destination, identify affected agents, save, and repeat the synthetic submission.
• Disconnecting clears stored OAuth access and refresh tokens and stops new delivery; the mapping remains saved.

Last updated on