If your website gets visits but few enquiries, audit the form before you blame the traffic. Ask only for what the next step needs, make every remaining field easy on a phone, and always offer WhatsApp as the low-effort alternative. Most UAE service businesses need a shorter interview, kinder errors, and a second door for visitors who will never type into a form at all.
The short answer: ask only for what the next step needs — and always offer the message instead
A good form usually needs a name, one reliable way to reply, and enough about the request to respond usefully. Everything else must earn its place. Keep fields that change what you do next, make nice-to-have fields optional, and ask the rest after you reply. Place a WhatsApp option beside the form, with equal prominence, for visitors whose enquiry is a question, not a document.
The problem: your form is an interview the visitor never agreed to
Look at a typical UAE service form through the visitor's eyes. Before any trust exists, it asks for name, email, phone, company, budget, service and a written message. Each field seems reasonable alone; together they feel like an application. The failure is silent: the visitor closes the tab, and the business concludes it needs more traffic. Friction also hides inside the form: labels that vanish, errors that blame, dropdowns that fight a thumb. For bilingual sites, our guide to Arabic form design covers the Arabic layer; this article covers the English form itself.
The field audit: keep it, make it optional, or ask it after the reply (table)
Take every field and write beside it the decision it lets you make in the next 48 hours. That test sorts most forms quickly.
| Typical field | Ruling | Why |
|---|---|---|
| Name | Keep, required | You need to address the reply personally |
| Phone or email | Keep one required contact route | You need a reliable way to reply; requiring both doubles the ask |
| Service needed | Keep, as simple choices | It routes the enquiry and shapes the first reply |
| Message | Keep, short and welcoming | It lets visitors describe their situation in their own words |
| Company name | Optional or ask later | Rarely changes the first reply for a small-business enquiry |
| Budget range | Ask later for most services | It frightens early visitors; ask once the conversation exists |
| Preferred date or location | Keep only where it changes the booking | Essential for a site visit, noise for a general quote |
| How did you hear about us? | Remove from the form | Attribution never justifies friction at the point of enquiry |
Notice what the audit protects: the message box. Documented tests include a case where cutting fields reduced completions because the removed fields were ones visitors wanted. Deleting the wrong fields is as harmful as keeping them.
How many fields is too many? What the evidence actually supports
You will see precise field-count conversion figures repeated across agency blogs, including claims that three fields convert at one fixed rate and six at another. Those figures are recycled from secondary sources, rarely tied to a primary study you can inspect, and they do not describe your visitors. Do not design to them.
What the evidence does support is narrower. Perceived effort matters: a form that looks long deters people before they start. Each required field is a trust request, and sensitive fields weigh more than neutral ones. Removing fields you cannot act on helps; removing fields visitors value can hurt. Nielsen Norman Group and Baymard Institute research points the same way: reduce unnecessary effort, explain why information is needed, and test on your own form. Your baseline, split by device and source, is the only benchmark that matters.
Friction beyond field count: labels, errors, keyboards and tap targets on mobile
Keep labels visible above each field, never as placeholder text alone, because a label that disappears leaves the visitor guessing during corrections. Write button copy that names what the visitor gets, such as Request my callback, rather than Submit, with one honest line about what happens next.
Validate inline, as the visitor leaves each field, instead of rejecting the whole form after submission. A helpful error states what is wrong and what correct looks like, without blame and never with a red border alone. Preserve everything already typed.
On mobile, follow Google's web.dev form guidance: use correct input types so a phone field opens a numeric keypad, set correct autocomplete values such as name, email and tel, and make tap targets large enough for thumbs, at least 48 pixels in web.dev's guidance. Single column avoids skipped fields.
One long form or several short steps? Choosing by enquiry type
Choose by enquiry shape, not fashion. A simple callback belongs in one short form: splitting three questions across three screens adds clicks without clarity. Multi-step works when the enquiry genuinely branches, or a booking needs service, then time, then details. Each step should ask one kind of thing, show progress, and let people go back without losing answers. Never use steps to disguise a long form. Test against qualified enquiries, not raw submissions. For a structured estimate, a quote calculator can carry detail a short form should not.
The WhatsApp fallback: which enquiries should skip the form entirely
Some enquiries should never start as a form. A quick availability question, a price check, a reschedule, or a visitor with two minutes will message happily and type reluctantly. For UAE customers, WhatsApp is the familiar front door; refusing it pushes visitors to a competitor, not into your form. Route conversational, urgent or uncertain enquiries to WhatsApp, including visitors who need to send a photo of the problem. Keep the form for detailed briefs, files, or records the team must file. Meta's click-to-chat mechanics are simple: a wa.me link opens a chat, optionally with a pre-filled message naming the service page. Our notes on WhatsApp click-to-chat setup and our WhatsApp Business API setup service cover the plumbing; the design decision is which enquiries each channel owns.
Designing the pair: form and WhatsApp side by side without cannibalising either
Present both routes with honest labels: Send an enquiry for a detailed request, or Message us on WhatsApp for a quick question. Equal visual weight matters; a giant form beside a tiny link is not a real choice, and a floating bubble hiding the submit button helps nobody. Send both channels into one tracked place so no lead lives only on a personal phone, and pre-fill the WhatsApp message with the service name. Judge the pair on total qualified enquiries. A fall in form completions alongside better WhatsApp conversations is the system working, not cannibalisation.
After submit: confirmation, expectations and the thank-you page that keeps the lead warm
The thank-you page is part of the form. Confirm the enquiry arrived, name what happens next, and give a realistic timeframe; never promise a reply speed the team cannot staff. Repeat the contact details submitted so typos can be spotted, and offer WhatsApp here too. Use the page to ask the questions the audit removed, such as budget or timing. A blank confirmation leaves your warmest lead wondering whether anything happened. For wider contact details, follow our contact page pattern: one clear route per need.
Common mistakes
The commonest mistake is copying a field list from a CRM, so the form serves internal reporting. Close behind: requiring both email and phone, hiding the phone field's purpose, clearing the form after an error, and placeholder-only labels. Other errors include burying WhatsApp, letting a chat bubble cover the form on mobile, promising a response time nobody staffs, and celebrating submissions while qualified enquiries fall. Treating recycled statistics as law, and cutting the message box, turns an audit into damage.
FAQ
How many fields should an enquiry form have?
Only the fields the next step needs: typically a name, one reliable contact route, the service needed and a short message. Audit every extra field by asking what decision it changes within 48 hours; make it optional or ask it later if the answer is none.
Is a multi-step form better than a single-step form?
Only when the enquiry genuinely branches or a booking needs stages such as service, time, then details. For a simple callback or quote, one short form is clearer. Splitting a few questions across screens adds clicks without reducing real effort.
Should I offer WhatsApp instead of a contact form?
Offer both, with divided jobs. WhatsApp suits quick, urgent or uncertain questions, especially on mobile. The form suits detailed briefs that need structure or files. Judge success on total qualified enquiries across both channels, not form submissions alone.
How should form error messages be written?
Validate each field as the visitor leaves it, say what is wrong and what correct looks like, and preserve everything already typed. Avoid blame, vague warnings and red borders with no explanation, and never reject the whole form only after submission.
What should a thank-you page include?
Confirm the enquiry arrived, state what happens next and a realistic reply timeframe, and repeat the contact details submitted so typos can be spotted. Use it to ask optional qualifying questions the form deliberately left out, and offer WhatsApp for anything forgotten.
Get an enquiry flow designed around how UAE customers actually contact you (CTA)
If your form asks questions your first reply never uses, the flow needs redesign, not more traffic. WebStackRank's web design team in Dubai designs forms and WhatsApp routes as one system, as our wider web design in the UAE work does across every page. Send us your form and tell us which fields your team reads; we will show you what to keep, what to ask later, and what to let a message handle.
