QR code lead capture for show units, roadshows and property events in Dubai

Why paper sheets lose people at a launch

Paper sign-in sheets fail in predictable ways. People write quickly and illegibly. Queues form, so many visitors skip it. Someone has to type the sheet in afterwards, which happens days later, if at all. And the sheet cannot say which agent met which visitor. I will not quote a percentage for how much data paper loses, because the numbers I saw on vendor pages were unsourced or borrowed from other settings. The failure is plain enough without one.

A QR code (a square pattern that a phone camera reads and opens as a web address) moves the typing to the visitor's own phone and saves the result digitally at once.

What the QR code should lead to: a five-field form

The code should open a mobile-friendly form. Keep it to about five fields:

1. Name
2. Mobile number with country code (phone-number first, because most buyers will prefer WhatsApp to email)
3. Email (optional)
4. One qualifying question, for example "Buying to live in or to invest?" or a budget band
5. Which agent or team member met you (a dropdown, or filled automatically by an agent-specific code)

Add a clear incentive in the button text, such as "Send me the brochure and payment plan on WhatsApp". A button that says "Submit" gives people no reason to tap it. Offer the form in English and Arabic at minimum, and add other languages if your visitors need them.

One code per event, project or agent (dynamic QR)

A static QR code has the web address baked in. A dynamic one points to a short address you control, so you can change the destination later, for example when a launch ends and you want the same printed brochure to point to a waiting-list page. It also lets you give each placement its own code, which tells you where scans come from.

• One code per event so that you can tag every lead with the event name.
• One code per project when you promote several at one roadshow.
• One code per agent (on a badge or business card) so the lead owner is clear from the start. This heads off the classic dispute over who met the buyer first.
• One code per property on listing boards, so you know which board produced the enquiry.

Use a short link with the event, project and agent in the tag. That tagging idea is the same one described in lead source tracking.

Consent line and where the data goes

Put one plain sentence above the button saying how you will contact the person, for example "By submitting, you agree that [company] may contact you by phone and WhatsApp about this project." Link to your privacy notice, and store the exact wording and the time with the lead.

The UAE has a personal data protection law (Federal Decree-Law 45 of 2021, the PDPL), and I explain what it means for brokerages in client data and the PDPL. Separately, the UAE telemarketing rules (Cabinet Resolution 56 of 2024) cover marketing calls and, as I read them, marketing messages sent through social media apps. They allow marketing calls only between 9am and 6pm, ban calling numbers on the national Do Not Connect Register (the official list of numbers that have opted out of marketing calls), and TDRA (the telecoms regulator) asks for prior explicit consent and an unsubscribe option for marketing text messages. Penalties are set by Cabinet Resolution 57 of 2024. A visitor who scans your code and asks for the brochure is a different case from someone you contact cold, but your consent line should still say what you plan to do. This is information, not legal advice: confirm with the relevant authority or a lawyer. For the rules around outbound calls, see cold calling rules and tools in the UAE.

A word on identity documents: do not ask for passport or Emirates ID (the UAE national identity card) details on a QR form at an event. Collect those later, inside your proper onboarding process, not on a public web page.

When the signal is bad: offline and backup options

Sales galleries, show units and basement exhibition halls often have poor mobile coverage, and a hundred visitors on one cellular tower makes it worse. Do not depend on live signal.

• Offer venue wifi with a simple password, and print it next to the code.
• Keep two or three tablets at the desk with the form already loaded, as a backup you can hand to a visitor.
• Keep a few paper sheets for emergencies, and type them in the same day.
• Test the code on both iPhone and Android, on mobile data, at the actual spot where the code will be displayed, the day before.
• Check that the form submits even when the connection is slow. If your form tool supports saving a half-finished entry or keeping the page usable offline, ask the vendor to show you; I have not verified any vendor's offline claims.

Instant WhatsApp thank-you and brochure

The moment someone submits, they should get a message with the brochure, the payment plan if the developer allows it to be shared, and the name of the agent they met. Show only the developer's current approved payment plan; an old one on a forwarded PDF causes trouble later. For wider WhatsApp follow-up and rules on messaging, see speed to lead on WhatsApp and the WhatsApp Business API. If the message is automatic, the visitor should always be able to reply and reach a human.

Event tag, owner and duplicate check in the CRM

Each submission becomes a record in the CRM with these fields filled automatically: event name, project, agent, scan time and the consent wording. Set the routing rules before the event, not during it. Test one submission end to end the day before.

Plan for duplicates:

• A visitor may scan twice, or scan at two stands. Match on mobile number and merge, adding a note rather than creating a second lead.
• The visitor may already be in your system from a portal enquiry. Link the new scan to the existing record and keep both sources.

Who owns the lead if two agents met the same person? Write the rule down before the event, for example "the agent whose code or badge was scanned first". See real estate lead management software for how CRMs handle ownership.

A 7-day follow-up routine

A simple pattern adapted from one vendor's sequence:

• Day 0: instant thank-you with the brochure (automatic). The agent gets a task to call or message.
• Day 1: personal message from the agent referring to what the visitor said at the event.
• Day 3: a useful follow-up, such as the floor plan they asked about or a map of the area.
• Day 7: a check-in and an offer of a viewing or a call.

Sooner is better, but I will not claim that a reply within two hours converts best, because that figure was a vendor anecdote. Measure your own: scan to first contact, contact to viewing, viewing to deal. See off-plan lead nurture sequence for the longer version.

How software and AI help at events (and what a person still does)

• Software: a form tool plus a QR generator that supports dynamic codes, writing straight into your CRM or a spreadsheet, tagging event and agent, and triggering the WhatsApp message. This is mostly plumbing and takes an afternoon to set up.
• Checks: an automatic rule that flags submissions with an invalid phone number, so you can fix them before the follow-up.
• AI: it can draft the Day 1 and Day 3 messages from the visitor's answers, or sort a long list of scans by the qualifying question. A person reads before anything is sent.

What stays human: the conversation at the stand, deciding which visitors deserve a call first, and checking that the payment plan sent matches the developer's current one. I set up this kind of form-to-CRM flow for brokerages, but for a first event, a good form tool and a clear routine are enough.

Try it yourself with Claude: paste an anonymised list of ten scans with their answers and the agent's notes, and ask: "Draft a short, friendly WhatsApp message for each person, in English, referring only to what they told us. Do not mention any price or payment term. Flag any entry where the information is too thin to write a useful message."

Print and placement checklist

• Print the code large enough to scan from a normal standing distance. One vendor suggests at least about 10 cm square for signs; test your own from the real distance.
• High contrast, a clear space around the code, and a line of text next to it saying what the visitor gets.
• Place it at eye level at the entrance, the reception desk, on the model table and on badges.
• Do not put a code on a curved or glossy surface that reflects the lights.
• Include the advertising permit number (issued through Trakheesi, the Dubai Land Department's permit system) wherever the print is an advertisement; confirm the rules with the Dubai Land Department (DLD, the emirate's property registry and regulator).
• For listing boards, use one code per property and change the destination once it is sold.
• Test every printed code before sending to print and again after.

How I would approach this

I would keep it small: one form, one code per agent, a consent line, a tablet backup, and an automatic thank-you. Run it at one event, count how many scans became conversations, and fix what broke before the next one. The owner needs the event tag and the scan-to-viewing number. Agents need to know that the lead they met is theirs. For the website that supports all this, see the off-plan launch landing page guide.