Skip to help content
All help guides

Lead setup

Configure a website lead capture form

Choose intake defaults, connect a form, and verify captured records before publishing.

Define how incoming leads should enter the CRM

Settings → Lead Capture stores a form name, Lead Source, Initial Lead Status, Job Type, Assign To, notification users, and success/error redirect URLs. Separate forms are useful when different campaigns need different attribution.

Production availability depends on the migrated capture endpoint and notification services being configured and tested. The existence of a generated form example alone does not prove intake is live.

Connect and test the form

The screen supplies the API Endpoint, API Key, and example HTML. Use the generated example as the field reference rather than inventing a different endpoint. The intake fields support contact information and notes; keep unnecessary sensitive information out of the form.

  1. Create a named form with a source and initial stage.
  2. Set the default job type and assignment where appropriate.
  3. Choose your success and error pages.
  4. Copy the example into your website implementation, preserving the form identifier.
  5. Submit one clearly labeled test prospect.
  6. Confirm its name, contact details, source, status, assignment, and interaction history.
  7. Test the error path and check that the visitor sees a useful response.

Consent and integration limits

SMS permission should come from an explicit customer choice; a captured lead is not automatically permission to text. Preserve the opt-in context and avoid a preselected consent checkbox.

Form identifiers are for intake, not full CRM access. Never expose administrator credentials or an AI connection key in public website code. Notification settings require a working delivery service and should be tested independently.