Why Website Leads Don’t Reach Your CRM: A Troubleshooting Guide
When a website enquiry is missing from the CRM, check each handoff in order: the form submission, integration, field mapping, CRM rules, assignment, and notification. This process helps isolate the failure point instead of changing several settings at once.
Start here: Submit a clearly labeled test enquiry, note the time and email used, then follow that test through the form confirmation, integration log, CRM record, routing, and notification. Use a test account and avoid putting real sensitive information into troubleshooting records.
Step 1: Confirm the website form actually submits
Open the page on desktop and mobile, complete the form, and check what happens after pressing submit. Look for a confirmation message, redirect, or error. If the browser reports a validation error, note which field causes it. Check whether spam protection, required fields, or a script conflict is blocking the submission.
Do not use a real customer’s private details for tests. Use a designated test address and mark the submission as a test so it cannot be mistaken for a sales opportunity.
Step 2: Check whether the integration received the submission
Review the form plugin’s entry list and the integration or automation log for the timestamp. If the form has an entry but the integration does not, inspect the connection status, trigger conditions, authentication, rate limits, and recent configuration changes. If neither the form nor integration recorded it, focus first on the form itself and any validation or delivery error.
Step 3: Verify field mapping and required CRM fields
A transfer may fail when the form sends a value the CRM rejects or when a required CRM property is empty. Compare the submitted values with the mapping table. Check email formatting, dropdown values, date formats, field length limits, and whether CRM property names or accepted options have changed. Make sure optional website fields are not mapped to required CRM fields without a deliberate fallback.
Step 4: Check duplicates, filters, and automation rules
Duplicate handling
The CRM may update an existing contact rather than create a new one. Search by the test email and inspect recent activity.
Filters and validation
Automation may skip records that do not meet a condition, such as a selected service or valid region.
Ownership rules
Routing may assign the record to a queue or owner that is not being monitored.
Notifications
The CRM record may exist even if an alert is filtered, sent to an old address, or disabled.
Step 5: Search the CRM in the right places
Look for the test record by email, submission time, name, and any external form identifier. Check contacts, leads, unassigned records, imports, and recently updated records. Review activity history for a failed workflow, merged duplicate, or reassignment. Confirm that the user troubleshooting the issue has permission to see the relevant records and queues.
Step 6: Find the break in the handoff
- Form has no entry: investigate the form, page scripts, validation, spam filter, and submission response.
- Form entry exists but no integration event: inspect the connector, trigger conditions, credentials, and logs.
- Integration event failed: read the error, then check mapping, required properties, accepted values, and CRM limits.
- CRM record exists but is hard to find: inspect duplicate matching, list views, filters, queue assignment, and permissions.
- Record exists but no one was alerted: check notification recipients, workflow status, delivery logs, and fallback ownership.
Test the fix and prevent a repeat
After changing one issue, submit a fresh test and verify the whole journey again. Check the confirmation, CRM record, field values, owner, notification, and follow-up task. Record what failed, what changed, and how it was verified. Set a periodic test cadence appropriate to the importance of the form, and repeat after changes to the website, CRM, integration, or routing rules.
For important lead paths, define a fallback: who checks integration failures, how the team is alerted, and where enquiries go if the normal assignment rule cannot run. A backup mailbox or monitored queue only helps if a person owns it.
Frequently asked questions
The form says submitted, but the CRM has no record. What should I check first?
Check whether the form stored an entry and whether an integration event was logged at the same time. That separates a form issue from a handoff issue.
Could the CRM have merged the lead?
Yes. Search using the test email and inspect existing records and activity history before assuming a new record should have been created.
How can we catch failures earlier?
Assign an owner for integration errors, retain useful logs, use a fallback queue, and periodically submit a test through the live form.
Related lead capture resources
Review CRM Lead Capture Integration, the educational Lead Capture System guide, and Lead Capture Automation Services.