AI for Real Estate & Facilities · Tenant services · Facilities · Leasing and portfolio
One call from a tenant. One work order, dispatched.
- Saudi Arabic, day and night
- Read-only to building controls
- Work orders in your CAFM
- Technicians sent with a window
04 · WHERE THE WORK LANDS
Tenant services
→ Request answered
matched to the unit
Maintenance
→ WO-48812 raised
right trade, right asset
Dispatch
→ Technician sent
02:40 window given
Energy
→ Saving proposed
engineer approves
Leasing
→ Clause answered
from the lease
Portfolio
→ Expiry surfaced
before it is missed
03 · HARNESS
VOHO FACILITIES AI HARNESS
ANSWER · LOCATE · DISPATCH · PROVE
VOICE
Listen · speak · barge-in
TOOLS
BMS · CAFM · leases
MODELS
Arabic speech · LLM · faults
AGENTS
One per desk
IDENTIFICATION
Unit and lease, first
COST LIMITS
Out-of-hours needs approval
EVALUATIONS
Right trade, right priority
MODEL ROUTING · CONTEXT · RAG · GUARDRAILS · READ-ONLY CONTROLS · HUMAN APPROVALS · AUDIT TRAIL
02 · SYSTEMS OF RECORD
01 · THE ESTATE AND ITS TENANTS
Swipe the drawing sideways.
One AI layer. Every way a tenant reaches you and every system behind the building.
The Voho Facilities AI Harness
Whoever answers the phone cannot see the building.
They take a sentence about a warm office and turn it into a ticket that says warm office. The harness reads the zone, the valve and the three work orders already raised against that air handling unit, so the order names the actual fault and the technician arrives with the part.
A model on its own
- Writes down “AC not working” and stops
- Cannot tell a zone fault from a plant fault
- Sends the wrong trade at premium rates
- Promises a time nobody agreed
- Closes with no evidence for the dispute
The same model, in the harness
- Matches the caller to the unit, the lease and the zone
- Reads the BMS trend before anyone is dispatched
- Names the asset and the trade from the history
- Gives a window dispatch has actually accepted
- Attaches the trend and the sign-off to the closure
Building systems
What you already run, left in place
- BMS / BAS
- Archibus · TRIRIGA · CAFM
- SAP PM
- IoT sensors
- Energy meters
- Access control
- Lifts
- CCTV alarms
- Lease documents
- CRM
- Telephony
Voho Facilities AI Harness
The runtime between your systems and the models
- Tool calling
- Model routing
- Building connectors
- Tenant identification
- Memory
- Context
- RAG
- Workflow orchestration
- Permissions
- Cost limits
- Human approvals
- Evaluations
- Guardrails
- Audit trails
- Observability
Model layer
Routed per task, never one model for everything
- Saudi Arabic speech
- Speech synthesis
- Foundation models / LLMs
- Time-series and fault models
- Energy models
- Document models
Agent layer
Scoped to one desk each
- Tenant Agent
- Maintenance Agent
- Energy Agent
- Leasing Agent
- Access Agent
- Portfolio Agent
Where the work lands
Finished in the system that owns it
- Requests answered
- Work orders raised
- Technicians dispatched
- Faults evidenced
- Leases answered
- Visits booked
01
Answer.
Tenants and residents answered in Saudi Arabic or English at any hour, on the phone and the channels they already message you on.
02
Locate.
The unit, the lease, the asset and the BMS zone resolved before anything is raised, so a request is attached to a real place in a real building.
03
Dispatch.
A work order in Archibus, TRIRIGA or SAP PM with the right trade, priority and service level, and a technician given an actual window.
04
Prove.
The trend that showed the fault, the history it matches and the sign-off attached to the closure, so the service level is defensible.
01 · Tenant services
Two in the morning, and somebody answers.
The call that usually reaches an answering machine, taken in Arabic, matched to a unit, checked against the building and turned into a dispatched work order before it ends. The out-of-hours cost is the one thing it will not decide by itself.
Transcript
Identification
Nothing about a tenancy or a zone is discussed until the unit is matched.
Tool calls
waiting…
Policy
- Raising the work order and booking a window inside the standing limit completes in the call.
- The out-of-hours callout is above the limit, so it waited for the duty manager before dispatch.
Illustrative call · BMS read-only · trend and approval attached to the order
02 · The building twin
Why the order says valve, not thermostat.
Zones by temperature, the live trend on the air handling unit, and every work order raised against it this year in one place. The diagnosis is the part a ticket queue never has: this has happened before, on this asset, and this is what fixed it.
Zones by temperature
L10 · zone 7 is the only zone outside the band, and it is the zone the tenant just called about.
AHU-3 · work order history
WO-41180
AHU-3 chilled water valve actuator replaced
WO-43920
Zone 7 complaints, filters changed, no fault found
WO-46110
AHU-3 valve sticking reported by technician
Maintenance Agent
Zone 7 is warm with the chilled water valve near fully open and supply air rising: the valve is passing, not the thermostat. Same signature as WO-46110 in August, on the same actuator replaced in March.
Suggested: HVAC technician to AHU-3 tonight, priority 2, with the valve on the van. Out-of-hours callout is above the standing limit, so it needs an approver.
Across the portfolio
One harness. Every building and every desk.
The connectors, the identification rules and the evaluation set are built once. The next tower is configuration, not another project.
Tenant and resident services
The call at two in the morning
- Requests taken in Arabic, matched to the unit and raised in the CAFM
- Status chased and updated without the tenant calling again
- Access, parking and visitor requests handled inside your rules
- Move-in, move-out and fit-out steps explained from your own handbook
- Service charge and billing questions answered against the lease
Facilities and maintenance
The building, not the ticket queue
- Faults triaged against BMS trends before a technician is sent
- Planned maintenance scheduled and confirmed with the tenants it affects
- Asset history answered in one question: what failed, what fixed it, when
- Vendor service levels tracked and chased automatically
- Energy anomalies surfaced with the saving and the reason, for an engineer to approve
Leasing and portfolio
The paperwork behind the doors
- Leases abstracted: rent, escalation, break options, obligations, expiry
- Renewal and escalation dates surfaced before they are missed
- Arrears calls made politely, in Arabic, with the ledger in front of the agent
- Viewings booked and confirmed into the leasing calendar
- Occupancy, expiry and exposure questions answered across the portfolio
Connectors
One AI layer. Every system in the building.
Read-only where it touches plant, write access only in the systems where a work order belongs. Nothing is replaced to answer the first call.
BMS / BAS
Honeywell, Siemens, Schneider. Read-only
CAFM
Archibus, TRIRIGA, Planon and others
SAP PM
Assets, notifications, work orders
IoT sensors
Temperature, CO2, occupancy, leaks
Energy meters
Consumption by zone and by asset
Access control
Passes, visitors, parking
Lease documents
Contracts, schedules, handbooks
Telephony
Cisco, Avaya, SIP. Your numbers
Built for operating buildings
What operations and security ask, answered in the product.
A building is not a demo environment: the boundaries below are configuration your own teams set, starting with the fact that it never writes to plant.
Read-only to building controls
Voho reads the BMS, the meters and the sensors. It does not write setpoints, override schedules or touch life-safety systems. Its output is a work order for a person.
Cost limits on anything it raises
Work orders, callouts and vendor jobs run inside the limits you set. Above them, or out of hours at premium rates, the job is drafted and waits for an approver.
Identification before unit data
A caller is matched to a unit and a lease under your rules before anything about the tenancy is discussed, and contractors see only what their scope allows.
Inside your own network
On your servers or in a Saudi region. Recordings, transcripts, building data and tenant details stay where your policy says they stay.
Closures that survive a dispute
The trend, the history, the technician’s note and the sign-off are attached to the closure, so a service-level argument with a tenant or a vendor has evidence behind it.
Evaluated on your own history
Scored against real past requests and faults before go-live: what it would have raised, what trade it would have sent, and what it should have escalated.
From the library
What this would look like at companies you know.
Demonstrations, not customer work. We built five agents for each of these organisations from public knowledge of how they run; none of them asked, and none of them run this today. Open one to see this page’s argument applied to a developer or contractor you recognise.
Dar Al Arkan
Real estate
One of the Kingdom’s largest listed developers, selling homes that do not exist yet to buyers who need certainty.
Run the demos →Jabal Omar Development
Real estate
Mixed use development close to the Haram, where hotel occupancy follows a religious calendar and every operational decision is shaped by pilgrim flow.
Run the demos →Red Sea Global
Real estate
A regenerative tourism destination built on a marine environment, where an environmental commitment is a design constraint rather than a reporting line.
Run the demos →ROSHN
Real estate
A large scale community developer, where a buyer’s question about handover is a question about a construction programme they cannot see.
Run the demos →How a project runs
Start with one building. Keep the harness.
The first building proves itself on numbers you already report: answered calls, time to attend, first-time fix and service-level breaches.
01
Take one building
One tower or one estate, where the request volume is known and the service levels are already measured.
02
Connect read-only
BMS and sensor data in, the CAFM for work orders, your telephony for the calls, reviewed by your operations and security teams.
03
Replay last quarter
The agents are scored against the requests and faults that already happened: right trade, right priority, right escalation.
04
Go live after hours, then widen
Start where the alternative is an answering machine, then take the daytime queue and the next building on the same harness.
What operations, tenants and security ask first.
If your question is not here, bring it to a technical session with our engineers.
01Does it control the building?
No. It reads the BMS, meters and sensors and raises work orders for people. It does not write setpoints, override schedules or interact with life-safety systems, and energy recommendations are proposals an engineer approves.
02Which CAFM systems do you work with?
Archibus, IBM TRIRIGA, Planon, SAP PM and others. Where there is an API we use it, where there is a database we read it, and where there is neither we work through the screens your team already uses.
03Can it dispatch a technician at two in the morning?
Yes, inside your rules: the trade, the priority and the cost limit you set for out of hours. Anything above the limit is drafted and waits for an approver rather than committing spend on its own.
04How does it know which unit is calling?
From the number, the tenant record and your own verification rules. Until the unit and lease are matched, nothing about the tenancy is discussed.
05Do tenants know they are talking to an AI?
Yes, and that is configured in the greeting. Handover to your team is always available, and every call is recorded and kept under your retention policy.
06What about CCTV and personal data?
Camera alarms can be read as events. Footage and biometrics are not processed by these agents, and tenant data stays inside your network under the retention you configure.
07Can it help with leases, not just faults?
Yes. Leases are abstracted into the terms that matter, renewal and escalation dates are surfaced before they are missed, and questions across the portfolio are answered with the clause cited.