Quote request forms: what to check on mobile
A quote request form should be easy to complete on a phone and deliver an enquiry you can act on. Check the whole journey: finding the form, entering details, submitting, seeing confirmation and receiving the enquiry. A success message alone does not prove it reached the right destination.

Four steps to put this guide into practice
Start with a realistic visit
Open the page on your phone while logged out of WordPress. Try the main homepage button and a service-page button. Visitors should understand which service they are enquiring about before typing. Check that cookie banners and floating buttons do not cover the form.
Test portrait mode with the keyboard open. Tiny fields, an off-screen button or disappearing instructions can interrupt a motivated visitor. Keep labels visible: an example inside a field is not a replacement for its label.
Ask for what the first conversation needs
For a service enquiry, start with a name, a reply method, the service and a description of the request. A town can help qualify local work. Require only the details you actually need. If the phone number is optional, leaving it blank should not prevent submission.
Detailed qualification can suit a complex project, but the steps need to be understandable. Avoid asking for sensitive documents at first contact. If attachments are available, explain their purpose and provide another way to continue the conversation.
Check errors, confirmation and delivery
First leave a required field blank: the error should explain what to fix. Then submit a technical enquiry clearly labelled TEST to an authorised inbox, without pretending to be a customer. Check the confirmation, actual delivery and readability of the answers.
Check the recipient, spam folder and any configured tracking tool. The reply action should use the visitor’s supplied address according to the intended setup. Before repeating production tests, check which notifications and automations they trigger.
Keep a short record
Record the tested page, phone, date and outcome of each stage. Separate input problems from submission failures and email delivery issues. This gives the person fixing the site a precise brief instead of making a full redesign the default answer.
Fictional example: a Charenton tradesperson gets calls but few form enquiries. Submission works, but the main button leads to a general page where the form is hard to find. Improving that journey is worth evaluating, without promising a numerical increase in enquiries.
Frequently asked questions
Is a shorter form always better?
No. The right number of fields depends on what the first conversation needs. Every required field should have a concrete purpose.
Can I rely on the success message?
It only confirms what the interface displays. Check delivery and any configured enquiry record separately.
Discuss your project with WebSteve
WebSteve supports small businesses and independent professionals with websites, visibility and automation. Describe your situation and the relevant pages to define the next actions.
contact@websteve.fr
Leave a Reply