The email arrived without enough information
The client could see that someone had used the contact form, but the notification did not include the visitor’s email address as expected. That made the form’s apparent success misleading.
A delivery test alone would have missed this. We needed to compare the submitted fields with the actual email received by the business.
Make the notification content explicit
We reviewed the form’s message pattern and configured the expected fields in the email content. The goal was a readable notification containing the information the client needed.
Field names and notification settings depend on the form configuration. The useful principle is to check the actual message, rather than assuming that a default setting includes every field in the way you expect.
Check the visitor’s confirmation too
During testing, we also found that the confirmation message was difficult to read against the page background. We adjusted the presentation so the visitor could see that the form had been submitted.
The visitor and the business have different needs. One needs a clear acknowledgement; the other needs accurate details and a practical way to follow up.
Test an enquiry from both sides
Use test details that make each field easy to recognise. Submit the form on desktop and mobile, read the confirmation and inspect the email that arrives. Check required fields and any alternate enquiry routes too.
These small details affect whether a website enquiry turns into a conversation. If notifications are incomplete or confirmations are unclear, the right task is to review the whole contact process, not simply redesign the form.
Need a hand with something similar?
Tell us what you are trying to achieve or what is not working. We will help you work out the next step.
Explore the service Contact us
