Practical technology
A mobile enquiry form should not feel like paperwork
A form can fit a phone screen and still be awkward to use. A visitor may not know which fields are mandatory, lose a long message after an error, or wonder whether tapping Send did anything. Review the complete journey before choosing a new plugin or redesigning the page. Start by observing a real phone with a realistic, non-sensitive test enquiry.
Reduce the first conversation
Imagine a fictional repair business asking for a postal address, invoice number, budget, product model and preferred appointment before it knows what the customer needs. Some information may become useful later, but the first form could instead collect a contact route and a short description. The owner can ask focused follow-up questions after reading it.
The right number of fields depends on the work. A quotation needing measurements will differ from a general question. Explain why an unusual required field is needed and keep optional details clearly optional.
Make each field understandable
Use visible labels that remain available during typing. Give concise instructions where a format matters. Suitable autocomplete values can let the browser offer stored name, email or telephone information; they are aids, not a guarantee that every browser behaves identically.
Check whether the keyboard suits the requested information and whether the Send button stays reachable. Test with longer names and messages, not just a two-word dummy entry. Where phone numbers are collected, avoid assuming that every visitor uses the same national format.
Review errors and the final result
A correction should explain what needs attention near the relevant field. Keep valid answers so a small mistake does not erase the whole enquiry. Client-side feedback can help the visitor, but the server must still validate submitted data.
Finally, distinguish waiting, accepted and failed states. A spinner that never resolves and an immediate success message before acceptance both undermine confidence. Use a controlled test route and agreed test data; do not send repeated fake enquiries into a client’s working inbox.
Your next step
A practical checklist
- Complete the form on a phone without zooming.
- Check visible labels, required fields and useful autofill.
- Try an invalid entry and confirm other answers remain.
- Check slow-network feedback and the accepted state.
- Review who receives and follows up the enquiry.