Real Estate

Real Estate Operations Platform

One routed inbox for a luxury real estate operator

A boutique operator of European super-prime homes ran its portfolio on personal WhatsApp numbers, shared mailboxes, and spreadsheets, so the same issue surfaced in several chats and work landed on the owner. AE Studio designed a custom operations platform that brings every tenant, owner, and agent message into one inbox, uses AI to classify each one in two languages, and turns the ones that need action into tickets a team owns, so the owner can see everything open across the portfolio instead of chasing it.

Real Estate Operations Platform

TL;DR

  • Email from shared mailboxes, WhatsApp chats and groups, and website enquiries land in one inbox tied to the contact and the property.
  • An AI classifier reads each message in either working language and decides whether it needs action; the ones that do become tickets with an urgency and a team that owns them.
  • The owner has a top-down view of unanswered messages, open tasks, and anything running late across the portfolio, and the client owns all of the code.

The challenge

The problem.

A boutique luxury residential operator manages a portfolio of European super-prime homes, with a plan to grow and expand into commercial buildings. The service is deliberately high-touch. A small team spread across two countries and two languages handles everything from tenant requests to renovations, with an internal maintenance crew backed by vetted outside specialists. The operation ran on WhatsApp, Outlook, and spreadsheets. Tenant, owner, and agent messages arrived on personal phone numbers and across a set of shared mailboxes, the same issue spawned several parallel chats, work was misrouted, and things fell through the cracks. The owner spent her time on work that should have been caught a layer below her, and she wanted a system built around her service model, that she owned, and that would hold the team to one process.

AE Studio gave the team one place to work from. Every email, WhatsApp message, and website enquiry lands in a single inbox tied to the contact and the property, an AI classifier reads each message in either language and decides whether it needs action, and the ones that do become tickets with an urgency and a team that owns them. Requests get an immediate acknowledgement, reminders keep work moving, and the owner has a top-down view of unanswered messages, open tasks, and anything running late, so the misrouting and duplicate chats that used to reach her are handled a layer below.

The platform was delivered in stages so the team could start using it early and shape what came next. A small senior pod, one full-stack engineer with a fractional product manager and program oversight, worked directly with the client’s founder and asset-management lead, and the client owns all of the code.

The solution

What we built.

Unified Inbox Across WhatsApp, Email, and the Website

Email from the company’s shared mailboxes, WhatsApp messages and group chats, and enquiries from the website all flow into a single inbox. Every conversation is tied to the contact and, where known, the property it concerns. Replies go out from the shared mailbox that received the message, so the team presents one identity externally while working from one place internally. Messages that only need visibility, such as accounting correspondence, stay in the inbox without generating work.

AI Classification in Two Languages

An AI classifier reads each incoming message, in either of the team’s working languages, against a catalogue of issue types organized into a small set of operating categories. The catalogue was seeded from the client’s own history of real requests, so the categories match how the business already talks about its work, and the classification step decides whether a message needs resolving at all.

Ticketing That a Team Owns

When a message describes a problem that needs resolving, the platform opens a ticket, sets its urgency, and assigns it to the responsible team by country. Whoever on that team picks the ticket up first becomes its owner, so work is not waiting on one named person. Not every message becomes a task; low-stakes correspondence stays visible in the inbox without creating work.

Acknowledgement, Notifications, and Escalation

Every request gets an immediate, category-specific acknowledgement, and a person follows up. Assignees are notified in the app, by email, and on WhatsApp, and reminders escalate on a schedule tuned to urgency until an item is acknowledged, in progress, or resolved. Anything that stalls escalates up the chain.

Owner Dashboard and Internal Chat

The owner gets a top-down dashboard of unanswered messages, open tasks, and anything urgent or running late across the whole portfolio, and the team has an internal chat inside the platform instead of WhatsApp groups.

Assets, Inventory, and Turnover

The second stage turns the property list into full asset records, with rooms, documents, and lease dates, and adds a cross-portfolio inventory of furnishings so idle items in one flat can be found and reused in another instead of repurchased. Move-in preparation runs through a structured checklist with its own reminders, inspections log room-by-room findings and open follow-up tasks for anything urgent, expiring documents and notice periods are flagged ahead of time, and a reports page shows maintenance turnaround by team and by person.

Outcomes

What shipped.

AE Studio designed a custom, mobile-friendly web platform as the one system the business runs on. The first stage puts every conversation in one place and routes the work. The second extends the platform into the assets themselves.

One inbox for the team’s shared mailboxes, WhatsApp chats and groups, and website enquiries, in place of personal numbers and scattered mail

Every incoming message classified by AI in both working languages, with only the ones that need action becoming tickets

Tickets assigned to the responsible team by country, with urgency set and ownership taken by whoever picks the ticket up first

Immediate category-specific acknowledgements, with notifications in the app, by email, and on WhatsApp that escalate by urgency

A top-down owner view of unanswered messages, open tasks, and anything running late across the portfolio

Key takeaways

What we learned.

  • We agreed with the client early on a small, fixed set of operating categories and let them drive routing, acknowledgements, and reporting. Issue types can be added underneath them cheaply; changing the categories later would not be.
  • We decided that not every message should become a task. Letting classification decide what needs resolving keeps the queue meaningful and lets low-stakes correspondence stay visible without creating work.
  • We chose to acknowledge automatically and respond personally. One immediate, category-specific acknowledgement followed by a human reply keeps the premium service feel while making sure no request goes unanswered.
  • We assigned tickets to teams rather than individuals, with ownership going to whoever picks the ticket up first, so work does not stall when one person is unavailable.
  • We seeded the classification catalogue, routing rules, and escalation timings from the client’s own issue log, org structure, and response-time expectations rather than a generic template.

In summary

Bottom line.

A luxury real estate operator needed to move a spread-out, bilingual team off personal WhatsApp numbers, scattered mailboxes, and spreadsheets. AE Studio designed a custom operations platform that brings every channel into one inbox, classifies and routes issues with AI, keeps work moving with urgency-based reminders and escalation, and gives the owner a live view of everything open, with asset records, inventory, and turnover workflows following on the same platform. The client owns the code, and the platform is designed to carry the leasing and tenant-intake workflows that come next.

FAQ

Frequently asked.

Does every email or WhatsApp message create a ticket?
No. AI classification determines whether a message needs resolution. Only those open tickets; the rest stay visible in the inbox.
How does the platform handle two languages?
Classification runs in both of the team’s working languages, and acknowledgements can be sent in either.
Who owns a ticket?
Tickets are assigned to the responsible team by country, and whoever on that team picks a ticket up first becomes its owner. Reminders escalate by urgency until the item is acknowledged, in progress, or resolved.
What came after the inbox?
Full asset records, a cross-portfolio inventory of furnishings, structured move-in preparation, inspections, document and lease-date reminders, and maintenance reports, on the same platform.
How is success measured?
Against the criteria agreed at the outset with the client: the whole team operating from one platform, a sharp drop in duplicate chats on a single subject, every maintenance issue logged and assigned, and a measurable reduction in the time it takes an inbound message to reach the right team.

Let's talk

Bring us the hard problem.

We'll bring the team that ships.

Get in touch