Test a website-builder form as a complete customer journey, from entering information to the business receiving and responding to it. The form, sending service, spam filter and destination mailbox can each affect the result.
01 Run a complete form test
- Identify the live form URL, intended recipient, sending method and any dashboard that stores submissions. Confirm who should receive or access each type of enquiry.
- Review field labels and instructions. Request only necessary information and explain what happens after submission.
- Submit a clearly labelled test using a unique subject and a non-sensitive message. Record the time and the result displayed in the browser.
- Check the builder's submission record if provided, the recipient's inbox and quarantine. Confirm that all necessary fields arrived and that replying reaches the intended address.
- Test missing required information, an invalid address and a longer message. Check that errors identify the problem without erasing everything the visitor entered.
- Repeat on a phone and with keyboard navigation. Review spam protection without making it impossible for a legitimate visitor to finish.
- Document the result and the responsible owner. Retest after changing domains, mail providers, SMTP credentials or the form widget.
Common questions
Why did the form show success but no email arrived?
The page may have accepted the submission before the notification reached its destination. Trace the stored submission and delivery logs, then check filtering and the recipient address.
Should the visitor's email be the sender?
Use an address authorised for the site's sending service and the supported reply-to setting for the visitor. This avoids presenting the form as if it were sent by someone else's domain.
Should I ask visitors to submit passwords?
No. Design enquiries around the information needed for the task and provide an appropriate secure process if account verification or sensitive files are required.