Identity
Name, appearance, voice, 20+ languages, register and boundaries.
Surfaces
One capacity layer.
Every touchpoint.
A surge is not absorbed by adding headcount. It is absorbed by the same Persona being present in more places at once — carrying the same knowledge, the same purpose and the same memory of the conversation it already had.
01 / The Persona pack
Configure once.
Deploy everywhere.
A Persona is not a deployment. It is a package — identity, knowledge, purpose and memory — that is authored once and then licensed onto whichever surfaces a venue needs. Surfaces are a distribution decision, not a rebuild.
Aira — Property Persona
One pack. Six surfaces. When the developer launches project #2, Aira is cloned, re-pointed at the new inventory and price book, and re-licensed — the identity, journey, qualification rules and handoff logic travel with her.
HoloboxFull-height physical presence
DisplayKiosk, lobby, front desk
WebProject site, remote buyer
WhatsAppAfter the visit, in their pocket
Mobile & tabletRoaming staff, expo floor
Knowledge
Inventory, pricing, policies — connected per project, versioned per surface.
Purpose
What a good interaction looks like here, and which outcomes count.
Memory
Who this visitor is, what they have already been told, what they asked for.
02 / Physical surfaces
Presence you can
walk up to.
This is the part nobody else is doing. A conversation held in the room, at human scale, by something a visitor physically approaches — which is a different act from opening a chat window.
- It is approached, not opened. A visitor who walks up has already self-selected. That is a materially higher-intent interaction than an unsolicited chat prompt.
- It holds the room. Presence mode works because something is visibly there — which is exactly the job a salaried person is currently doing by standing still.
- It carries the brand. In a flagship gallery or a government pavilion, the frontline is the brand. A screen in a corner is not the same asset as a considered physical presence.
- It is optional. Hardware is included where a venue needs it and omitted where it does not. The product being bought is availability, not a box.
Deployed in GCC public venues, where the interaction happens in front of the customer's own visitors.
Full-height unit for galleries, pavilions and booths — physical presence that anchors a venue.
Lobby, front desk, secondary zone. Lower cost per point of presence, useful for covering a venue rather than anchoring it.
Carried by staff on an expo floor or through a gallery — Ananta as a second pair of hands rather than a fixed station.
03 / Digital surfaces
The same Persona,
after they leave the room.
Most of the value in a physical visit is destroyed in the days after it. The visitor goes home, the advisor is busy, the follow-up is a generic message. Digital surfaces exist so the conversation simply continues.
Web
The project website
The remote buyer — often an NRI in the GCC — meets the same Persona that stands in the gallery, with the same inventory and the same qualification rules. A web enquiry becomes a real discovery conversation rather than a form submission.
WhatsApp
After the visit
The channel the buyer actually lives in. The Persona resumes with everything from the gallery visit intact — no re-introduction, no repeated questions, and no cold callback that starts from nothing.
Campaign
Mobile & expo
A GCC campaign push or a property expo runs the identical pack on a tablet or a booth screen. The surge that a campaign creates is met by capacity that was already configured.
The point: a surge is absorbed without headcount because the same Persona can be in the gallery, on the website and in a WhatsApp thread simultaneously — and treats all three as one conversation.
04 / Continuity
One buyer. One thread.
Five surfaces.
Continuity is the whole reason surfaces belong to a pack rather than being separate products. Below is the same person, moving through a purchase, never repeating themselves.
Illustrative journey · An NRI buyer, over eleven days · One Persona, one memory
Day 1Project website
Presence
Browsing from Dubai at 23:40. Aira answers on layout, price band and payment plan, and captures that this is a rental-yield buyer, not an end-user.
Day 4WhatsApp
Assist
Follow-up in the buyer's own channel. Aira already knows the yield question — she opens with the numbers rather than asking what they are looking for.
Day 9Sales gallery holobox
Surge
Weekend visit, gallery full, every advisor engaged. Aira recognises the returning buyer and continues the same conversation instead of starting a new one.
Day 9Advisor, in person
Handoff
Routed to the advisor who owns this account in CRM, with eleven days of context in one object — budget, yield expectation, the two units shortlisted and the objection still open.
Without continuity this is four disconnected touchpoints and one cold conversation. With it, it is a single qualified buyer arriving at the right advisor.
05 / Redeployment
Project #2 in days,
not months.
Deployment #3 is dramatically faster and cheaper than deployment #1, because the pack — not the project — is the unit of work.
- Identity and voice authored, reviewed and signed off
- Knowledge sources located, connected and verified
- Discovery journey and qualification rules defined with the customer
- Handoff targets mapped into their CRM
- Surfaces provisioned and physically installed
- Reused — identity, voice, journey structure, qualification logic, handoff shape
- Re-pointed — inventory, price book and policies for the new project
- Re-mapped — advisor ownership and routing targets for the new team
- Re-licensed — the surfaces this site actually needs
- Carried forward — everything learned about how buyers arrive
Why this compounds: every deployment sharpens the pack it came from. Common intents, qualification structures, handoff patterns and integration maps accumulate per vertical — which is what makes the fiftieth site a benchmark rather than a rebuild.
06 / Choosing surfaces
Which surface solves
which loss.
| Surface | Primary mode | The loss it closes | Typical venue |
|---|---|---|---|
| Holobox | Presence · Surge | Idle presence cost, and unattended visitors at peak | Flagship gallery, pavilion, exhibition stand |
| Display / kiosk | Presence · Assist | Unattended zones and secondary areas of a venue | Lobby, front desk, branch floor |
| Web | Assist | Remote intent that never converts into a visit | Project website, campaign landing page |
| Assist · Handoff | Post-visit decay — the follow-up that never happens well | Anywhere, after the visitor leaves | |
| Mobile / tablet | Surge | Overflow during a known spike, without adding staff | Expo floor, launch weekend, roadshow |
Configure once. Deploy everywhere.
Book a demo