This chat is for people who live at Emaar Beachfront, and their families. A short check runs first. A person sends the invite.
Residents and their families
An admin still sends the invite
Photos are not kept
Simulated check
Checking…
Reading the answers
Checking the unit against the tower
Looking for brokerage or ads
Comparing with people already approved
Admin queue
The check has sorted each person. A human still decides who gets an invite.
Names marked Sample are fictional. Anyone you add from Join stays in this browser only.
Nothing in this view.
This also removes applications you added on this phone.
Message check
Paste a message from the group, or tap a sample. You get OK or Flag, the rule it breaks, and a reply an admin can paste.
How this would run on a real group
WhatsApp does not let a bot sit inside an ordinary residents' group. An admin exports the chat once a day, or whenever it gets noisy, and this check reads the text. It flags what breaks the rules and drafts a reply. Nothing is sent on its own.
Live moderation
A simulation of the residents' group. Scripted messages arrive every couple of seconds, and the same rule check reads each one. This is our own layout, not a copy of any chat app.
Scripted messages 0 of 0
How it would work for real
A resident scans a QR. A check reads their answers. A person sends the invite. The group never has a bot in it.
QR
Join page
AI check
Admin approves
Invite link
1
QR
On a restaurant table, in the welcome bag, or on the building noticeboard. It opens a join page like this one. Scanning it does not add anyone to the chat.
2
Join page
Name, mobile, tower, unit, and a yes to the rules. Proof of residence is optional: a photo of an Ejari or an access card, with the personal lines covered.
3
AI check
The same kind of check you can try on Join. A clear resident is marked approve. An unknown tower, an odd name, a duplicate home, or a hint of brokerage goes to a person. Open promotion is marked reject. On this demo the check is a transparent set of rules, not a model. It is written so a real model can take the same job later: read the answers, and return a decision, a score, and the reasons.
4
Admin approves
You, or your assistant, open the queue. Approve, ask for proof, or reject. The reasons are in plain language, so this takes a glance rather than a reread of every answer.
5
Invite link
Approve copies a welcome message with the group link. A person sends it. That link is the door. Nobody is added automatically.
Two ways to run it
Google Form + AI
The same questions can live in a Google Form, which is easy to edit and to print as a QR. Each response is read by the check, and the decision lands in a queue like this one. You keep hold of the invite link. This is the smallest step from the demo to something you can use.
WhatsApp Business, one to one
A business number answers people who message it, asks the same questions, and files a short summary for your assistant. That is a private chat with the number, for verification. It is not a bot inside the residents' group.
Petition hub
One pinned place for every community petition. Residents sign the ones that matter to them. The same resident check runs on each name.
Sample petition: replace with the real ones.
Pinned message
One note for the top of the group chat. It lists every petition, the latest count, and a link. Sample links, until you replace them in the config.
Reminder nudge
Three ways to ask again, using the counts on this phone.
For the admin
Verified residents and names that still need a look. The tower chart and the CSV use the petition you pick. Sample names are fictional.
The file downloads on this phone. Nothing is uploaded.