the front desk
is not a
routing system.
A resident has a leak at eleven at night. They call the front desk, because the front desk is the only number they have. Someone writes it in a book.
The next morning three questions have to be answered by hand. Whose job is this? Is it the building's problem or the household's? And who is paying for it?
Those three questions are where the time goes, where the arguments start, and where a service charge dispute is born. They are also completely answerable before anyone picks up a phone.
one number for everything
Every request, urgent or trivial, lands on the same desk at the same speed.
nobody knows who pays
Building or household is decided case by case, late, and often after the work is done.
the household's own people are last to know
A resident already has a maid, a driver and a cooling contract. None of them are in the loop.
four steps, in order.
every single time.
This is the part that makes Butler different from a chat window. The order is fixed, it is the same for a one-bedroom flat and a mansion, and the resident can see it.
Shared problems skip the ladder. A riser leak, a lift fault, a ceiling coming down from the flat above — these go straight to the building and the owners association pays. The resident is never asked to work out whose problem it is, and never asked to approve a cost that was never theirs.
- 01The household’s own people—
- 02Their own service contracts—
- 03The building’s in-house team—
- 04A vetted contractor—
shown before
anyone is
sent.
Every job carries two lines the moment it is created: who does the work, and who pays for it.
If a job is chargeable to the household, the resident has to tap Approve before it goes anywhere. Nothing is booked on the assumption that they will agree, and nobody receives a bill for something they never saw.
For the management company that turns a recurring dispute into a record. Every job has a payer attached to it from the start, in writing, agreed by the person who is paying.
built for the
household, not
just the lobby.
ask in plain language
- Ask for anything a home needs, at any hour
- Their own staff and contracts used first
- A price and an Approve button before any charge
- Passes for guests, deliveries and parcels
- Nothing to install for the household's own staff
see the whole community
- Every open job, who owns it and who pays
- Services switched on or off per building
- In-house team ranked ahead of outside contractors
- Shared-fault jobs separated from household jobs
- Commission on work routed to the vetted network
one flat or
a whole portfolio.
Butler is switched on per building, and each building decides which services exist for its residents. A tower with an in-house team and a villa with none run the same system with different rungs turned on.
residential towers
High unit counts, an in-house team, and a front desk that fields everything. The routing order does the triage before a person has to.
branded residences
Where the service standard is the product. A butler named for the residence rather than for the software, in English or Arabic.
villa communities
No in-house team, every household with its own contractors and contracts. Rung three is simply switched off.
languages
Built for English and Arabic households, with Hindi and Urdu planned. The butler's name is set per building, so it can carry the name of the residence rather than the name of a vendor.
your existing portal
Butler does not connect to it today. In early access it runs alongside whatever a building already uses. We would rather say that plainly than imply an integration that does not exist — connecting one is something we scope with you.
early access.
said plainly.
looopoi Butler works, and it is going into its first buildings now. It is not a finished product being sold off a shelf, and we are not going to describe it as one.
What that means for an early access building: the routing, the who-pays rules and the service list are set up with you rather than handed to you, and what gets built next is shaped by what your residents actually ask for.
There is no public price list. A residence with forty units and a villa community with four hundred are not the same job, so pricing is quoted per building after a short scoping call.
a short call
Which services the building wants, who is in-house, and what the who-pays rules should be for that community.
one building first
Set up and run in a single building, with the routing configured to how that community already works.
then the portfolio
Once it holds up in one building, the rest of the portfolio follows with its own per-building settings.
residents' data,
handled honestly.
Data sits on enterprise cloud infrastructure, currently hosted in Singapore, encrypted in transit and at rest. Each building's data is isolated to that building and is never shared between clients, never sold and never used to train external AI models.
For a UAE deployment, three things are part of scoping before anything goes live: where the data is hosted, a data processing agreement under the UAE Personal Data Protection Law, and a resident privacy notice in English and Arabic.
looopoi is an early-stage company and is not itself SOC 2 or ISO 27001 certified. Our infrastructure providers are. Full detail is on our Security page.
before you ask.
An AI butler for premium residential buildings, branded residences and villas. A resident asks for something in plain language and Butler works out who should handle it, what it costs and who pays, then arranges it. It is switched on per building and every service can be turned on or off for that building.
In a fixed order. First the household's own people — their maid, their driver, their usual plumber. Then any service contract that household already holds, including how many visits are left on it. Then the building's in-house team, where the building has one. Only then a vetted outside contractor. Shared building problems such as a riser leak or a lift fault always go straight to the building.
Every job shows who does the work and who pays before it is sent. A shared building problem is paid by the owners association. A job inside a household is paid by that household. If a job is chargeable the resident has to Approve or Decline it first, so nobody receives a bill they did not agree to.
No. It routes work to them rather than around them. Where a building has an in-house maintenance team, that team sits above any outside contractor in the routing order. Buildings without an in-house team simply skip that step.
Yes, and they are used first. A household's own staff and their existing service contracts are the first two steps in the routing order, ahead of anything looopoi would arrange. Butler is there to reach them faster, not to replace them.
It is built for English and Arabic households. Hindi and Urdu are planned. The butler's name is set per building rather than fixed, so it can match the tone of the residence.
Not today. During early access Butler runs alongside whatever portal a building already uses. We would rather say that plainly than imply an integration that does not exist. Connecting to an existing portal or access system is something we would scope with you, not something we can switch on now.
On enterprise cloud infrastructure, currently hosted in Singapore, encrypted in transit and at rest. Each building's data is isolated to that building. For a UAE deployment the hosting location, a data processing agreement under the UAE Personal Data Protection Law, and a resident privacy notice are all part of the scoping conversation before anything goes live.
Early access. looopoi Butler is working as a prototype and is being taken into its first buildings now. It is not a finished product being sold off a shelf, and early access buildings help shape what gets built next.
Send us the building details through the form on this page. We reply within one business day and start with a short scoping call covering which services the building wants switched on, who is in-house, and what the routing and who-pays rules should be for that community.
tell us about
the building.
One form. We reply within one business day, and the first conversation is a scoping call, not a pitch.
We’ll be in touch within one business day.
Check your spam folder if nothing lands.
or just email us.
If you would rather start with a conversation than a form, that is completely fine.
hello@looopoi.com