Test a mobile enquiry from the page where a visitor starts through to the message arriving with the right person. Check navigation, readable content, form fields, errors and confirmation on a real phone. A button that looks correct is only one part of a working route to contact.
Agree a safe test before submitting anything
Tell the person receiving enquiries that you are testing. Use clearly labelled test information and agree how test records will be removed from reports. If the form triggers bookings, payments or automated messages, use an appropriate test environment and an agreed procedure.
Start by inspecting the page without sending anything. You can check menu operation, labels, telephone links and layout before making a controlled submission.
Keep a simple record of the device, browser, starting URL, test time and result. A note saying “form broken” is difficult to investigate. A repeatable description of the exact failure is much more useful.
Start where a visitor would start
Do not open the contact page directly for every test. Begin on a relevant service page, article or campaign destination. Can you understand the offer and find a suitable action?
Open and close the mobile menu. Expand any service dropdown and return to the content. Check whether sticky buttons, cookie controls or chat widgets cover the next action.
Then rotate the phone or change the text size. Content should remain understandable, and important controls should still be reachable. If the page depends on a wide table or image, check how its essential information survives.
Complete the form as an ordinary visitor would
Use the phone keyboard rather than copying all the answers from a document. Check whether email and telephone fields offer appropriate input controls and whether labels remain visible after typing begins.
Try a name with an apostrophe, a longer business name and a message containing paragraph breaks. These are normal inputs, not exotic edge cases.
If there is a file upload, test the permitted type and size through the agreed test process. Check the instructions before selecting a file. A visitor should not have to discover a restriction through repeated failure.
Make a mistake deliberately
Leave a required field empty or enter an incomplete email address. The form should identify the problem, explain how to correct it and keep the valid information already entered.
W3C’s guidance on form validation describes how validation can help people avoid and correct mistakes. A red outline on its own does not explain what went wrong.
Check where the page moves after an error. If the problem is above the visible area, the visitor needs a clear way to find it. Also check that correcting one error does not introduce another or erase the message.
Follow the submission beyond the screen
During an authorised test, submit once and wait for the result. A useful confirmation states that the request was received and explains the next step. It should not imply an appointment is booked when someone has only requested a time.
Check the actual destination: the inbox, CRM or other agreed system. Compare the received record with what you entered. Look for missing line breaks, truncated messages, incorrect service selections or enquiries assigned to the wrong person.
If more than one destination is expected, verify each one separately. A copy reaching the inbox does not establish that the CRM record was created. Similarly, a success message on the website does not establish that an email arrived.
Record problems by their effect
Separate a complete blocker from a minor inconvenience. A submission that never arrives needs attention before a slightly awkward gap between fields.
- Blocked: the visitor cannot complete the action or the enquiry is lost.
- Misleading: the page reports something that has not happened.
- Difficult: the action works but errors, layout or wording make it hard.
- Cosmetic: the issue does not change understanding or completion.
Give each issue an owner and a repeatable check. After a fix, rerun the affected path and confirm the receiving system again. Do not close a delivery issue using only a screenshot of the form.
For the questions themselves, see which fields a contact form needs. Use this test alongside the wider website launch checklist. Our website design service includes planning how people move from interest to an enquiry.