A contact form can look perfectly fine and still lose enquiries. The submit button might not respond, an error could go unnoticed, or a success message might appear without an email ever reaching you. If your website handles quote requests or appointment enquiries, test the whole journey: completing the form, submitting it, receiving the enquiry and replying. A visual check of the page is not enough.
1. Prepare a test that follows the enquiry all the way through
Start by establishing what should happen after submission. Does the form send an email notification, save the enquiry on your website, pass it to another application, or combine these actions? Check every configured stage, not just the email. If submissions are not stored anywhere, a failed notification may leave you without an easily accessible record.
Use an email address you can access and a clearly labelled test message. Avoid real customers’ personal information, and tell whoever handles enquiries that you are testing so they do not mistake it for a genuine order.
- Record the page, test time, device and browser.
- Include a recognisable label, such as “Contact form test – mobile check”.
- Identify where the enquiry should arrive and who should respond.
- Test while logged out of the website, using a private browsing window.
Private browsing helps you see the form without your administrator session affecting the experience. It does not replace testing on real devices.
2. Check every required field and error message
Begin your contact form test by trying to submit incomplete information. Press the button without entering anything, then leave each required field empty in turn. The form should clearly explain what is missing and where you need to make a correction, rather than showing a vague warning at the top of the page.
Try valid details and everyday mistakes
- Enter an incomplete email address and check the explanation.
- Enter only spaces in a required field.
- Try names and messages containing accented characters, hyphens or apostrophes.
- If there is a phone field, check common formats, including an international dialling code.
- For appointments, try a past date or unavailable slot if the form manages availability.
- If attachments are allowed, check size limits and permitted file types using harmless test files without sensitive information.
After an error, previously entered details should remain where possible. Check that you can correct the problem and submit again without rewriting the entire message. Avoid making information compulsory unless it is needed to assess the enquiry.
Errors need a written explanation, not just a change of colour. Also check keyboard navigation: the order of fields, the visibility of keyboard focus and whether you can activate the button. Browser-side validation helps visitors, but it does not replace validation on the server.
3. Distinguish an on-screen confirmation from actual delivery
A success message does not prove that an enquiry has reached your inbox. Depending on the implementation, it may only mean that the application accepted the submission or started sending it. The message could still be rejected, delayed or filtered later.
After submitting, check the on-screen confirmation, any saved enquiry record and the incoming notification separately. If the form creates an appointment, check that it also appears in the relevant system. Do not treat a booking as confirmed simply because a generic success message appeared.
- Is the confirmation visible, and does it explain what happens next?
- Does the button indicate that submission is in progress?
- Could repeated clicks create duplicate enquiries?
- If the connection fails, is there a useful explanation rather than a misleading success message?
The confirmation wording should match what actually happened. “Your request has been received” and “Your appointment is confirmed” mean different things. If someone must approve the booking manually, make that clear. If the visitor also receives an automated acknowledgement email, test that separately.
4. Follow email notifications through and check replies
Check the configured recipient address, then look for the message in the inbox, spam folder and any filtering or quarantine system. For a shared address, review forwarding settings and rules that may automatically move incoming messages. Repeat the test using another contact email address, without sending large batches of test messages.
Check the sender and reply address
As a general rule, notifications should use a sender address authorised for the sending service, rather than presenting the visitor’s address as the sender. The visitor’s email address can go in the Reply-To field so your response reaches the right person. Test this in practice by selecting “Reply”.
SPF, DKIM and DMARC settings need to align with the service sending the messages. These mechanisms support authentication and domain policies, but do not guarantee inbox delivery. If you use SMTP or a transactional email service, check its settings, authentication and available error information. Do not expose passwords in screenshots.
For a WordPress website, review your form plugin’s settings and investigate possible conflicts after updates. You can also assess whether your WordPress hosting meets the website’s requirements, but hosting does not replace correct form and email configuration. For service-related questions, consult the frequently asked questions.
5. Test the form on mobile, not just in a smaller window
A mobile contact form needs testing on an actual phone. The on-screen keyboard, autofill and fixed page elements can cause problems that do not appear on a computer. Open the page, complete the form and send a message over both Wi-Fi and mobile data if you can.
- Do labels and instructions remain visible when you start typing?
- Can you use the fields and button without manually zooming in?
- Does an appropriate keyboard appear for email addresses and phone numbers?
- Does a consent banner or another page element cover the submit button?
- Can you complete the anti-spam checks without getting stuck?
- Are errors and confirmations easy to find without confusing scrolling?
Also check longer messages, date selection and file uploads where available. If something fails, record the device, browser and exact steps. Do not permanently disable anti-spam protection simply to make the test easier.
6. Complete the journey with a reply, then test again
The test is not finished when a notification reaches you. Reply to it and confirm that your response arrives at the address entered in the form. Check that you have the information needed to prepare a quote or handle an appointment, and that the message preserves the expected accented characters, paragraphs and attachments.
Decide who monitors incoming enquiries and who covers their absence. A correctly delivered notification is of little use if nobody reads it. Keep a short checklist and repeat the test after form changes, software updates, email service changes or a website migration.
The practical takeaway: send one enquiry from a computer and another from a phone, deliberately trigger an error, check receipt and send a reply. If a stage fails, record exactly where the journey stops. For questions about GazduireOnline.ro services, use the contact page and describe the issue without including passwords or customer data.
