CRM lead setup

Goal

Configure lead sources, statuses, scoring, web forms, assignment, and duplicate/convert policies.

Admin with crm.admin (stage/catalog edits that clerks need may also use crm.manage where API allows).

Open CRM → Setup → CRM setup.
Options: assignment mode (unassigned / creator / round-robin team), convert rules (create opportunity; require email/phone/company), duplicate policy (allow / warn / block + match fields).
Lead sources: manage Website, Referral, Trade show, Cold call, Partner, Web, Email, CSV import (and custom).
Lead statuses: display names/colors mapped to lifecycle keys new, contacted, qualified, unqualified, converted, merged — do not invent new lifecycle keys in Help or product logic.
Lead scoring, Web forms, Email inbox (IMAP import), Teams, Tags, Email templates as needed.
- Web forms: build fields (text, email, phone, number, URL, date, dropdown, single/multiple choice), preview the visitor form, then copy the hosted form URL, public schema GET, HTML snippet, or JSON example from Embed and integrate. Add the website origin to Allowed origins for third-party embeds; the hosted page posts same-origin. Ingest always requires a name (the hosted page and public schema add that field when the stored schema omits it). The hosted page includes Cloudflare Turnstile when TURNSTILE_SITE_KEY is set. The marketing contact form uses the same site key via VITE_TURNSTILE_SITE_KEY; the API fail-closes when TURNSTILE_SECRET_KEY is set, so both keys and the marketing publish must go live together.
Workflows: automate on CRM events (follow-up / notify).

Capture, qualify, and convert behave according to tenant policy.