List each form, what should happen after submission, and who owns the result. For every test, specify the expected CRM record, assigned person or queue, notification, follow-up task, and source information. This makes a failed test actionable: the team can identify where actual behavior differs from the agreed workflow.

Include both routine cases and edge cases. For example, test a complete submission, a missing optional field, a repeated email address, a special character in a name, and a submission from a mobile device. Use test data that is clearly identified and remove or close it afterward so it cannot be mistaken for a real prospect.

Submit a value in each field and compare it with the corresponding CRM field. Confirm that the name, email, phone, company, message, campaign details, and any qualification information arrive in the intended place and retain their meaning. Pay special attention to dropdown values, checkboxes, dates, and fields that have different labels in the form and CRM.

Check what happens when a field is blank, when an answer is longer than expected, or when a value contains punctuation or non-English characters. Review the CRM lead-capture field-mapping example if the website and CRM use different field names.

Confirm that the record is assigned according to the agreed rules, such as a product, region, or team selection. Test each branch deliberately; do not assume that a successful submission proves that routing works. Verify that internal alerts go to the correct person and include enough context to act without exposing more information than necessary.

Check the visitor-facing confirmation as well. Make sure it appears only after a successful submission and tells the person what happens next in plain language. If the CRM is unavailable or the form fails, the user should not see a false success message.

Submit the same test contact twice and observe whether the CRM updates an existing record, creates another record, or follows a defined review path. Confirm that deduplication behavior matches the company’s CRM rules and that it does not merge distinct people simply because they share a company domain or phone number.

If source tracking is part of the workflow, test how the system records the landing page, campaign parameters, referrer, and first-touch or latest-touch fields. Verify that those values persist through the CRM process and are not overwritten unexpectedly by a later visit. Keep the attribution terms and reporting definitions documented for the people who will interpret the data.

Check that any consent or preference field selected on the form is mapped and retained as intended. Make sure the form explains what information is collected and that access to submitted data follows the organization’s policies. Do not put sensitive or unnecessary data into open notifications or unprotected spreadsheets.

Test validation and failure states: missing required data, a declined submission, timeout, CRM rejection, and a repeat attempt. Confirm who is alerted when integration errors occur and how a failed record can be recovered. A useful process records enough technical detail for diagnosis while keeping customer information appropriately protected.

Have a representative from marketing, sales, and the technical owner complete the same scenario and confirm the result. Check the CRM record, activity timeline, assignment, notification, and follow-up action. Repeat the test on desktop and mobile, then keep a brief record of the form tested, date, expected outcome, actual result, and issue owner.

After launch, monitor real submissions and compare form counts with CRM-created records. If leads stop arriving, the website leads not reaching CRM troubleshooting guide can help organize the investigation. For implementation scope, see CRM lead-capture integration.