Lead Form to CRM: A QA Checklist for Leads That Disappear
A practical way to catch enquiries lost between the website form, notifications, CRM, owner assignment and real follow-up. Start with evidence instead of assuming the dashboard is right.
Map the complete path before changing tools
A lead can disappear even when the form displays a success message. The confirmation screen, notification email, CRM record, owner assignment and reply are separate events. Draw the real sequence for each live form: visitor submits, server accepts, contact record is stored, duplicate rules run, an owner is assigned, the team is notified, and the prospect receives a useful next step.
Include website forms, embedded forms, chat enquiries, booked calls and landing pages. Note exactly which system owns each handoff and where a failed event is retained for retry. A dashboard green light is not proof a customer received a reply.
Run one end-to-end test from a real page
Start with the page a customer sees on a phone. Open it in a private browsing session, complete every required field with clearly labeled test data, submit once and capture the local time, landing URL and on-screen confirmation. Check that the form is usable with a keyboard and readable at narrow widths. Never submit a real customer's details as a test.
Trace that one record all the way through the original form storage, integration log, inbox and CRM. Confirm the email address, requested service, consent value and message were preserved. If the record appears in one system but not the next, the failure is in that handoff rather than in marketing traffic.
Audit lead ownership and response rules
A lead with no owner can sit untouched even if every automation succeeded technically. Define which person receives each service or geography, what happens outside business hours, and when an unanswered task is escalated. Test reassignment and unavailable owners without using customer accounts.
If two workflows both create contact records or send the same acknowledgement, fix the event identity and idempotency rule before enabling them together. A reliable deduplication key might use the accepted submission ID, not merely an email address that a returning customer can use twice legitimately.
Separate delivery from clicks and dashboard activity
A queued notification, API success response or sent-mail copy is not proof that a recipient saw the message. Store separately the submission accepted time, CRM create/update result, automation attempt, provider message ID, actual bounce signal and owner follow-up. Never mark an enquiry qualified because the scheduler ran.
For reporting, distinguish visitors, form opens, accepted submissions, legitimate contacts, qualified opportunities and won revenue. If a source cannot be reconciled, show the missing evidence instead of estimating results or silently marking the row complete.
Use this handoff test matrix
| Stage | Proof to inspect | What to do if it fails |
|---|---|---|
| Form submission | Accepted request and stored submission ID | Check required fields, endpoint response and spam controls |
| Notification | Provider delivery attempt ID and error response | Inspect address, provider policy, suppression and retry logs |
| CRM record | Matching contact and enquiry or opportunity ID | Fix field mapping, permissions or duplicate handling |
| Assignment | Owner and next action recorded on the lead | Repair routing criteria and fallbacks |
| Follow-up | Actual reply or scheduled human action | Escalate stale leads without sending duplicate responses |
| Reporting | Reconciled accepted and qualified counts | Correct event definitions; annotate missing source data |
Test failures on purpose in a safe environment
Use synthetic records to simulate an integration timeout, repeated webhook event, missing required field, invalid recipient, reassigned owner and delayed provider response. Verify that an unsuccessful step can be retried without creating a second lead or sending a second message. Do not trigger live outreach to real prospects to prove that a workflow works.
Document the actual recovery route: who can see the failed item, whether an automatic retry is bounded, what will alert the operator, and whether a manual retry is safe. An unattended process needs both a normal path and a failure path.
Make the mobile conversion path part of the audit
Sometimes the CRM is fine and the problem starts before submission. Test field sizes, autofill, consent language, unclear submit labels, hidden validation errors and links that send visitors to an unrelated page. A successful page load does not mean a visitor can complete the form.
Pair technical lead handling with the promise on the page. An international services enquiry may need market and service context, but asking ten qualifying questions before the first conversation can create unnecessary friction. Capture only information that the team will actually use and protect it under the applicable privacy requirements.
A weekly audit worth repeating
- Sample one real accepted submission per important source and a separately labeled synthetic test.
- Reconcile source submissions with CRM records, duplicate handling and owner assignments.
- Check unanswered enquiries against agreed response standards without inventing service-level promises.
- Review form changes, integrations, bounce reports and access-control changes.
- Prioritize issues that prevent a legitimate prospect from reaching a person, then re-test the corrected path.
For teams managing UK, European or Asian enquiries, verify time zone and routing behavior. A submission arriving overnight should not silently disappear because an owner is offline. Record market-specific requirements only when they are actually part of the service process.
What to do next
Start with one customer journey, not another disconnected software subscription. Turma helps teams connect forms, source tracking, CRM routing and follow-up through its marketing automation and CRM services. For a public-facing conversion review, see our website and landing-page services or request a five-point marketing snapshot.