A contact form can show a cheerful “Thanks” message whilst the enquiry never reaches your team. To test website contact form performance before launch, follow a real submission all the way to the person responsible for replying.
Form testing means checking what visitors see, where their details go, and what happens when something fails. For contact forms, the whole enquiry route matters more than a working submit button.
Key takeaways
- During form testing, send a genuine enquiry and confirm it reaches the right inbox, customer record or booking system.
- Test missing and invalid details, mobile use, accessibility, spam controls and failure messages.
- Check both the visitor’s confirmation and your team’s notification. They’re separate parts of the process.
- Repeat the test after launch and whenever you change the form, email service or lead-routing rules.
How to test a website contact form end to end
Start form testing on the live landing page, or on a staging site whose email and integrations match the planned launch setup. Use the inquiry form as a prospective customer would. A preview in the form builder, even one based on form templates, isn’t a substitute for testing the planned setup.
Send an identifiable test enquiry
Enter realistic details and put a clear test reference in the message. Use an email address you can check, preferably outside the domain that sends your form notifications. If the form accepts a phone number, check that its format works too.
After the form submission, confirm that the page shows an unmistakable success message or thank-you page. It should say what happens next and give an honest response timeframe. An urgent-service form might also offer a phone number for time-sensitive requests.
Then find the submission in every intended destination: the nominated inbox, any stored form entries, the customer relationship management (CRM) system and assigned staff alerts. Match the reference, contact details and message against what each destination records, checking that data collection is accurate.
Follow the lead to its owner
As part of form testing, follow the enquiry through to its owner, not just the inbox it reaches. Check forwarding rules, shared inbox access and which customer support staff receive enquiries outside working hours. Where routing depends on service type or location, submit a separate test for each route.
If an automated acknowledgement is enabled, inspect the message received by the visitor. Confirm its reply address works and its promised response time matches your team’s capacity. Mark test records clearly so they don’t trigger a genuine sales call or booking.
Check required fields, validation and confirmation
A successful submission proves little about the experience of someone who makes a mistake. Good form testing checks whether visitors can recover without starting again.
Try empty, incorrect and unusual entries
During form testing, submit with every field blank. Required fields should be clearly identified, and the form should prevent an incomplete submission. Next, enter an invalid email address, leave one required field empty at a time, and try a longer message or punctuation in names.
Clear error messages should sit beside each affected field and explain what to fix. “Enter a valid email address” is more useful than “Invalid entry”. The form should retain correctly entered details after an error.
Browser checks help visitors correct mistakes, but the server must validate submissions too. MDN’s form validation guide explains how client-side validation works and where its limits lie.
Check the promise after submission
Submit corrected details and make sure the success message appears only when the form has accepted them. If an acknowledgement email is part of the process, check its delivery separately. An on-screen confirmation doesn’t prove an email was sent.
Keep data collection proportionate to the enquiry. A callback request through an inquiry form may need a name, contact method and brief description. A detailed project request may reasonably ask about scope and timing. For conversion optimisation, compare conversion rates with useful enquiries, not submission totals alone.
Verify email delivery and the right destination
If form testing records an entry but the notification is missing, the problem may sit in notification settings or email delivery. If there’s no entry and no success message, investigate form processing first. Separating those paths saves time.
Check routing before changing email settings
Confirm the recipient address is correct and active. Check the inbox, spam folder and quarantine, and review any spam filter reports. Then check forwarding, shared mailbox or CRM rules. Send a test email for each notification template, particularly if different teams receive different services.
Ask the site or email administrator to inspect available form and mail logs. A recorded submission, a successful mail hand-off and an email in the recipient’s inbox are three different checkpoints. If messages reach one address but not another, compare what the receiving systems report.
On WordPress, an SMTP plugin can send form notifications through a configured mail service instead of relying on the server’s default mail function. Check its sender address, connection and test results. Other platforms offer different mail settings, but the same delivery checks apply.
Check sender authentication
During form testing, confirm that emails come from an address your sending service is authorised to use. Put the visitor’s address in Reply-To when staff need to reply directly; don’t assume it belongs in From.
Ask whoever manages your domain and email service to check the published dns records for SPF, DKIM and DMARC against that service’s instructions. SPF identifies permitted senders, DKIM adds a verifiable signature, and DMARC helps receiving systems handle messages that fail authentication. Gmail’s sender guidelines explain the importance of authentication and domain alignment.
Where available, inspect a received message’s authentication results and spam placement. These checks help diagnose email deliverability, but correct records can’t guarantee that every inbox will accept a message.
Test on a phone and with assistive technology
Open the actual contact page on a phone, not just a narrow desktop browser window, as part of your form testing. Check that labels stay visible when the on-screen keyboard opens, fields don’t run off the screen, and the submit button is easy to tap. Check device compatibility with autofill, dropdowns, date controls and any upload field you offer.
Then complete an inquiry form using a keyboard, and test web forms with a screen reader where possible. Can you reach each control in a sensible order, see where focus is, submit, and find the success or error message? Persistent, descriptive labels and visible focus improve the user experience; placeholder text disappears as people type.
The WAI forms tutorial covers labels, errors and completion messages. These checks matter for a mobile-responsive site because an accessible form also helps people working quickly on small screens.
Check spam protection, security and privacy
Spam controls should prevent abuse without turning away customers. Form testing can reveal whether a control that works on desktop blocks genuine enquiries on a slower phone.
Test the controls as a customer
If you use a honeypot, CAPTCHA or challenge, complete the form on mobile and by keyboard. Check that legitimate submissions are accepted and blocked submissions receive a sensible response. After changing rules, review spam logs and submissions quarantined by your spam filter, especially if filtering becomes stricter.
For forms that attract repeated abuse, ask your developer about server-side rate limits. If customers can upload photos or documents, restrict file types and sizes to what the team needs. Test both an allowed file and a rejected one.
Protect the details you collect
Client-side checks are easy to bypass, so developers should validate data on the server and protect forms against common attacks. OWASP’s input validation guidance is a useful reference for that review.
Use HTTPS, limit access to stored submissions and keep data collection to the details your team needs. Avoid putting personal details in page URLs or analytics events. Explain why you collect information and how you’ll use it in your privacy policy. An enquiry acknowledgement doesn’t give permission to add someone to email marketing; handle any marketing consent separately.
Plan for failures and measure useful enquiries
During form testing, check what happens when a submission can’t finish. An interrupted connection or unavailable integration shouldn’t trigger a misleading thank-you message. Show a clear error, offer a chance to retry and provide another contact route. Prevent duplicate records if someone submits twice.
For an agency managing several client sites, record the form owner, destination, fallback contact and person responsible for fixes. Heroic’s website care plans include ongoing monitoring and support, but each business still needs someone accountable for customer support and replying to leads.
Count confirmed contact form submissions, not clicks on a landing page’s calls to action or the submit button. Use data collection to compare enquiry quality, conversion rates, response time and booked work from local SEO, a Google Business Profile or social media. A clear lead generation path connects the form to follow-up, not just an analytics event.
Pre-launch contact form test checklist
Run this form testing checklist on every contact, quote, inquiry form, campaign form and feedback form before publishing. Forms made with form templates or a form builder still need checks on the actual launch setup.
- Submit a valid test enquiry on desktop and phone; check the success message.
- Match submitted details in the correct inbox, stored entries and CRM. Measure conversion rates by completed enquiries, not clicks alone.
- Check staff alerts, visitor acknowledgements and any automated lead assignment.
- Leave required fields blank, enter invalid details and confirm clear, recoverable errors.
- Complete the form by keyboard; check labels, focus, touch controls, spam challenges and whether the spam filter blocks valid submissions.
- Test rejected uploads or other limits, privacy wording and the response to a failed submission.
Record the result and assign any fix to one person. After making changes, repeat the affected test and one full submission through the route. Schedule a fresh check each month and after major site, email or integration updates.
Frequently asked questions
Why do test submissions appear in the form but not my inbox?
First check the notification recipient, spam folder, quarantine and forwarding rules. Then review mail logs and sender settings. If the form stores the submission, investigate email delivery without assuming the visitor saw an error.
Does an SMTP plugin guarantee delivery?
No. On WordPress, it can provide a configured way to send mail, but recipient filtering and incorrect notification settings can still prevent an alert from arriving. Include delivery checks in your form testing and test the destination inbox after configuration.
How many fields should a contact form have?
A contact form or inquiry form should ask for enough information to respond usefully, and no more. A quick callback needs less detail than a commercial project brief. Test whether people can complete it easily and whether your team has enough context to provide customer support.
A working form reaches a real person
The submit button is only the start of form testing. A reliable enquiry reaches the right person, gives the visitor a clear response and remains usable when they make a mistake.
Follow a test lead all the way through before launch. Then repeat the check after changes, as an unnoticed routing issue can make a working website look unexpectedly quiet.
