A website lead can disappear without a single system going offline: the form succeeds, the email arrives, and nobody owns the next step. This checklist traces the handoff from consent and validation to CRM assignment, so a small team can find the gaps before adding more automation.
Agree what a valid lead means
List required fields and the reason each one is needed. Normalize phone numbers, preserve the visitor’s original message, and distinguish required consent from optional marketing permission. Do not make a CRM field mandatory just because it exists; unnecessary friction creates incomplete or fabricated submissions. Power Automate approvals.
Make the form’s success state explicit and accessible. Test keyboard use, validation messages, mobile layouts, and what the visitor sees if the network request fails.
Define the mapping before connecting tools
Create a field map from form input to CRM property, including format, default, and fallback behavior. Decide whether a new submission creates a lead, updates an existing contact, or attaches a note. A reliable duplicate strategy should use a stable identifier and a documented rule; matching only on a person’s name is unsafe.
Send source page, campaign data, consent record, and submission timestamp with the payload when those values are legitimately collected. Keep data minimization in mind and document which system is authoritative for each field.
Make ownership and failure visible
Choose assignment rules for geography, service, or round-robin distribution and specify what happens when no rule matches. Route ambiguous cases to a monitored queue instead of silently dropping them. Ensure the CRM record shows the original request and a clear next action. See also OpenAI evaluation best practices.
Log a correlation ID or submission reference across the form and integration. Alert on rejected requests, rate limits, and credential failures; retry only transient errors and guard against creating duplicate records on a replay.
Test the whole journey
Use a matrix: valid submission, missing required value, malformed email, duplicate contact, special characters, consent declined, CRM unavailable, and notification unavailable. Verify both sides of every handoff and confirm that recovery does not send an unintended second acknowledgement.
Run a real-world rehearsal with the people who receive leads. Check the CRM on desktop and mobile, verify assignment and notifications, and record who owns monitoring after launch.
What would you do?
Where have you seen a lead handoff fail: consent, duplicate records, routing, or follow-up—and what check caught it? Share your experience in the comments.
Have a related project in mind? Talk with Acorn.
Share your perspective