Lead forms: test the full path into your CRM
By Mrunal Walke2 min read
Validate lead capture from submission through CRM assignment and notification, including retries, missing data and failed delivery.
On this page
A lead form is working only when the enquiry reaches the intended system with enough context for someone to act. A thank-you message and an email notification are useful signals, but neither proves that the CRM record exists or has an owner.
Specify a small data contract
List the fields that must reach the CRM: contact details, the enquiry, source page, submission time and a stable submission reference. Ask only questions that help qualify or route the enquiry. Keep optional marketing preferences separate from the information needed to answer a service request.
Write the destination field for every form field. Test select options as well as free text. A newly added option can disappear if the CRM only accepts an older list of values. Preserve the original enquiry when a mapping needs review.
Follow one submission through every stage
| Stage | Evidence |
|---|---|
| Received | Submission reference and accepted payload |
| Stored | Durable record of the enquiry |
| Created | CRM record ID returned and verified |
| Assigned | Named owner or monitored queue |
| Notified | Delivery state for the notification |
Zoho CRM documents webforms and assignment rules. Whatever form platform you choose, verify the routing in your actual configuration rather than assuming that connecting an account enables every rule.
Test an uncertain CRM response
In a hypothetical test, the CRM creates the record but the network connection drops before the form service receives the response. Retrying with a new submission reference may create a duplicate. Reuse the original reference and reconcile the outcome before creating another record.
Keep CRM creation and email delivery as separate states. If the email provider rejects the notification, retain the lead and show the operational failure to the team. Do not tell the visitor that nothing was received simply because an internal email failed.
Check the visitor experience too
Test keyboard navigation, readable errors, mobile fields and a slow connection. The submit button should prevent accidental repeated clicks while the request is being handled, without trapping the visitor after a recoverable error.
Run test submissions from every page that embeds the form. Shared styling does not guarantee shared integration code. Include missing required fields, a duplicate submission, an unsupported option and a temporarily unavailable CRM.
Record the resulting CRM IDs in a QA log and clean up clearly identified test records through the normal process. The acceptance condition is an actionable enquiry with a known delivery state, not merely a successful HTTP response.
Further reading
Primary reference. The workflow examples above are illustrative implementation guidance, not customer results.
Explore the related Dood resource. To discuss your workflow, contact Dood System.
