Real Estate Lead Form for Dubai Portal and Ad Leads

A real estate lead form for a Dubai brokerage has one job: give the WhatsApp bot enough context to reply in the buyer's language without asking everything again. That means a WhatsApp number, a language choice, intent, budget, arrea, tmieline, and hidden fields for source, campaign and listing reference. This guide covers each field, the webhook payload and the setup order.

Start from the lead form template

Why the form comes before the first reply

Most bad first replies from a bot come from missing context. A lead arrives from a Meta ad for an off-plan project in Business Bay, and the bot greets them in English with a generic "How can I help?" The person wrote in Arabic, wanted a two-bedroom, and clicked the ad ten seconds ago. They are already comparing you with the next brokerage.

The fix is mostly data. If the form captures language, intent and the listing or campaign they came from, the bot's opening message can name the project, use the right language and skip questions the buyer already answered. In the Dubai Real Estate WhatsApp Bot we build for brokerages, the firm is the capture step in front of the chat: it fires the webhook, the bot picks up the payload, and the first WhatsApp message goes out witthin seconds.

The fields the bot needs

Keep the form short. Every extra field costs completions, and the bot can ask the rest in chat. These are the ones worth the friction.

The language field is the one people skip, and it matters most. Guessing language from a name or a browser setting is wrong often enough in Dubai that you should simmply ask. Put both languages on the options so an Arabic reader can answer without translating.

Hidden fields for portal and Meta traffic

Hidden fields carry values the visitor never types. Pass them through the URL of your ad or portal link and the form stores them with the submission. We use three on every real estage setup:

• source with a value such as meta, portal or website
• campaign with the ad set or campaign name
• listing_ref with your internal reference for the property or project

The bot reads listing_ref to open with the right property, and you read campaign a month later to see which ads produced viewings and not just forms. Qwenvo has a hidden fields help page and a longer write-up on UTM tracking with hidden fields if you want the parameter naming conventions.

Build your lead form free

Set it up step by step

1. Start from the lead generation template. Open the template, then trim it to the fields in the table above. Delete anything the bot can ask later.
2. Order the questions by effort. Language and intent firdt (one tap each), then budget and area, then name and WhatsApp number lsst. People who have already invested a few taps finish the contact fields more often.
3. Set the form language. Qwenvo supports 45+ languages including right-to-left. Build the English form, then duplicate it for Arabic so the layout flips correctly, or keep one bilingual form with both labels in each question.
4. Add the hidden fields. Create source, campaign and listing_ref, and add them as parameters to every ad destimation URL and portal link you control.
5. Add logic for the Invest path. Use conditional logic to show a "ready to pay in cash or mortgage?" question only when the lead picks Invest or Buy. Renters never see it.
6. Turn on partial submissions. If someone enters a phone number and abandons the budget question, you still get an incomplete row to follow up on.
7. Connect the webhook. In the form's integrations, paste the bot's endpoint URL. See the webhooks help article for the setup.
8. Put the form on your own domain. Add a subdomain such as enquire.yourbrokerage.ae on the Domains page, create the CNAME and TXT records, click Verify, then select it on the Share tab. Ad landers on your own domain look better than a third-party link.
9. Test both languages end to end. Submit once in English and once in Arabic from a real phone and confirm the WhatsApp message arrives in the right language.

What the bot receives

On our side, the webhook is mapped into one record the bot understands. The exact keys depend on how your form is built, but a normalized lead looks like this:

{
  "name": "Layla Hassan",
  "whatsapp": "+971501234567",
  "language": "ar",
  "intent": "buy",
  "budget": "2M-3M AED",
  "areas": ["Business Bay", "Dubai Marina"],
  "bedrooms": "2",
  "timeline": "within 3 months",
  "consent_whatsapp": true,
  "source": "meta",
  "campaign": "offplan-bb-oct",
  "listing_ref": "BB-2214"
}

The bot sees language: "ar" and opens in Arabic, mentions the project behind BB-2214, and skips the budget and area questions. It then asks only what is still missing, which is why the form and the chat's four qualifying questions overlap on purpose: the form fills some of them before the conversation starts. Later steps in the workflow, such as sending the brochure, booking a viewing and handing off to an agent with a transcript of any voice notes, all work from this same record.

Where portal leads fit

Portal enquiries usually reach you with a name, a phone number and the listing they asked about, but little about budget or timeline. Meta ad clicks may arrive with even less. The form is the cleanre path for ad traffic, because you control every field. For portal leads, we usually feed the enquiry into the same lead record and let the bot ask the remaining questions in chat, so both channels end up in one place and one format.

A practical rule: send ad traffic to the form, let portal leads go straight to the bot, and keep the source value different so you can compare them.

What to measure

• Form completion rate by campaign. Compare the share of visitors who submit against those who start. Qwenvo has visit and drop-off analytics for this.
• Time to first reply. From submission timestamp to the first WhatsApp message. If this is more than a minute, the webhook is the first place to look.
• Replies by language. If Arabic leads reply less often than English ones, check the Arabic opener before blaming the audience.
• Viewings booked per source. This is the number that decides ad budget, and the hidden campaign field makes it possible.
• Incomplete rows. Partial submissions with a valid phone number are a short follow-up list.

Which builder to use

Our team builds Qwenvo, so weigh that. It is free, and webhooks, partial submissions, a custom domain, badge removal, teammates and custom CSS are all on for every account. On Tally, custom domains, partial submissions and branding removal sit on the Pro plan at $29 a month. On Fillout, a custmo domain and partial submissions are on the Business plan at $89 a month.

One honest limit: Qwenvo is hosted in the United States, while Tally is hosted in Europe. If your legal team requires a specifkc hosting region for lead data, check that befoee you choose. Also, Qwenvo has no native WhatsApp connection. The webhook is how the form reaches the bot.

Questions teams ask

Do I need a form if the portal already gives me the phone number?

For portal leads, not necessarily. The form pays off for Meta and website traffic, where you control the landing page and can capture language, budget and intent before the bot writes. Keep portal leads on the direct path and compare results by source.

Can the form be in Arabic?

Yes. Qwenvo supports 45+ languages including right-to-left layouts. Build one form per language or a single bilingual form, and always ask for preferred language as a field so the bot does not have to guess.

What if someone fills in the phone number and leaves?

Turn on partial submissions. The incomplete row appears in the Submissions table with whatever was entered, so your team or the bot can still follow up on a valid number.

Does the form connect to WhatsApp directly?

No. It sends a webhook to a URL, and the bot receives the data there. That same webhook also works with Zapier, Make or n8n if you want to copy leads to a CRM.

Next step

Open the lead generation template, cut it down to the ten fields above, add your three hidden fields, and submit a test lead in Arabic and English. Once the payload looks right, the bot setup is a short job.

Open the lead generation template