A good enquiry form asks for enough information to start a useful conversation without making the visitor complete a full project specification. Clear labels, practical validation and honest delivery feedback matter as much as visual styling.
Ask only what helps the next step
Start with contact details and the service needed. A short project message can provide context, while budget and timing may be optional if they are not essential to the first response. Explain why more detailed information is requested when the reason is not obvious.
Use persistent, specific labels
Placeholders disappear as people type, so they should not be the only labels. Distinguish a required email address from an optional phone number, and explain expected formats where needed. Error messages should identify the field and how to correct it.
Make mobile input practical
Use appropriate input types and autocomplete values. Give controls enough room to tap and allow long text to wrap without pushing the page sideways. Test whether browser autofill, the on-screen keyboard and validation messages leave the submit action usable.
Be honest about what happened
Do not display a success message before the server confirms acceptance. If delivery fails, preserve the entered details and offer another contact route. Opening an email application or WhatsApp is a draft action, not proof that the enquiry has been sent.
Keep alternatives visible
Some visitors prefer a call or a conversation. Provide clear contact links alongside the form, particularly when the project is hard to explain in a few fields. State what happens next without promising a response time that the business has not committed to.
Measure without exposing the message
Track that a contact method was used or a submission succeeded, rather than sending the visitor’s name, email address or project text to analytics. Review abandonment and recurring errors in aggregate, then adjust fields that create unnecessary friction.
Your project checklist
- A clear purpose for each field
- Persistent labels and useful errors
- Mobile-friendly controls
- Confirmed success and honest failure states
- Alternative contact routes
A common question
Should every enquiry field be required?
No. Require only what is necessary to process the enquiry. Optional context can help qualify a lead without blocking someone who does not yet have every detail.
Put the guide into practice
Explore our ui/ux design services for the process, possible deliverables and enquiry options. Share your context so the proposal reflects your business.