Website Forms UAE Visitors Actually Complete
Most UAE enquiry forms fail because they behave like a job application. Fourteen fields, a +1 phone default, a box that says “message” as if the visitor owed you an essay, and a red error that does not explain what broke. People do not complete that on a phone in Dubai traffic. They tap out and WhatsApp someone whose site asked for a name and a number.
I design forms as a conversation starter, not a CRM dumping ground. The CRM can grow up after you have a mobile number you can actually call. If the page is paid traffic, this matters even more — see landing pages that convert UAE ad traffic. A slow, nosy form is how you pay Google for clicks you never speak to.
Ask for less than you think you need
For a first enquiry I almost always use three fields: name, mobile, and an optional one-line “what do you need?” Email is optional. Company name is optional unless you only sell to companies. Budget dropdowns that start at “select” and include ranges nobody believes get skipped or lied to. You can qualify on the call.
Every extra field is a reason to abandon, and it is more personal data you must look after. That is both UX and the UAE PDPL point: collect what you will use this week. Emirates ID, passport scans, and open file uploads that accept anything do not belong on a first contact form for a typical service business.
| Field | First enquiry | After they reply |
|---|---|---|
| Name | Yes | — |
| Mobile (+971) | Yes | — |
| Optional | If you need to send a proposal file | |
| One-line need | Optional | Scope on the call or chat |
| Drawings / licence copy | No | When the job is real |
The phone field is not a US toy
Default country code +971. Allow spaces and leading zero the way people actually type. Do not reject 0501234567 because your plugin wanted +971501234567 only. Do not use a pattern that assumes a US nine-digit number. I have watched otherwise careful sites throw away valid UAE mobiles and then wonder why the sheet was empty.
Show the format under the field in small type: “05X or +971.” Keep the keyboard numeric on mobile. If you serve other GCC numbers, say so and allow them — do not silently strip a Kuwaiti or Saudi code because the developer hardcoded Dubai.
WhatsApp is the other form
Put click-to-chat next to the submit button, not as a secret in the footer. Same offer, two doors. Prefill a short line so you know which page they were on. The longer how-to is in WhatsApp buttons that get leads. A form-only contact page in 2026 is a museum piece in this market.
Do not run a chatbot that asks five qualifying questions and then says “leave your number.” That is a form with extra steps and a worse keyboard. If a human cannot answer after hours, say the hours. A dead chatbot on Friday afternoon is ruder than a form that emails you.
Fourteen fields and a broken +1 phone box? I can cut it down this week.
Show me the form on WhatsAppErrors, success, and the “message” box
If something is wrong, say what, next to the field, in language a person uses. “Enter a UAE mobile” is a sentence. A red border with no text is not. Do not clear the whole form on a failed submit. Do not rely on browser-native bubbles that sit under a sticky header. Test on iPhone and on a small Android, on mobile data, the same way you would test any Dubai website.
Success is a promise
After submit, tell them what happens next: “We usually reply the same working day on WhatsApp.” A generic “thank you” page with a stock balloon is how people submit twice. Send the lead to a mailbox you control, not a plugin account nobody can log into after the freelancer left. The contact page should repeat the number so they can still call if the form quietly fails.
Kill the essay
“Tell us about your project” as a required textarea is how you lose people who wanted to send a photo. Make it optional, or replace it with a file field that only accepts images and PDFs, with a size cap. Many visitors would rather WhatsApp the photo. Let them.
One PDPL sentence, not a wall
Under the button: “We use this to reply about your enquiry. We do not sell it.” Link the privacy page. Never pre-tick consent. Never copy a UK ICO template that mentions London. The full implementation notes are in the PDPL article linked above. The form’s job is to match that page: if you say you only collect name and mobile, do not secretly add twelve marketing fields in the HTML.
Spam protection should be invisible to humans — a honeypot or a quiet server check — not a puzzle that blocks a parent in a pickup queue. If you are drowning in bot mail, we fix that without adding a 12-second wait to every real lead.
That is the whole form brief: fewer fields, a UAE phone, WhatsApp beside submit, errors that speak, and a privacy line that is true. Pretty labels can wait. Completions cannot.
Frequently asked questions
How many fields should a UAE enquiry form have?
For a first contact: name, mobile, and one optional line about the job. Email is optional. Extra fields belong after they have said hello.
Should the form replace WhatsApp?
No. Offer both. Many UAE visitors will not type a form in a car. A click-to-chat next to the form catches them.
Do I need a long privacy policy under the button?
You need one honest sentence and a link. A GDPR novel copied from a UK template is not a substitute for collecting less.
I’ll rebuild the form so people finish it — and so the privacy line matches the fields.
WhatsApp +971 52 486 7767