Property maintenance
“Zone damper on floor 3. Tenant already emailed twice.”
The tenant already emailed twice. The damper is on floor 3. Nothing should live only on a personal phone. AI drafts. Dispatch assigns. The crew closes on the phone.
This is
AI field operations for multi-site requests that already arrive as email, WhatsApp, SMS, or voice.
This is not
- Not facilities-management software, and not a tenant portal.
- The model does not invent a window because a tenant wrote twice.
- There is no customer portal.
The hop
The second email is the product failing in public.
Many sites, four channels, one tired inbox on a personal phone. The tenant should not have to write twice for the work to exist.
01
Email on one phone, WhatsApp on another
The damper note is in a mailbox. The follow-up is on WhatsApp. Nobody has one operational thread.
02
Floor 3 is a guess in the van
Which building, which tenant, which access. Someone copies a fragment into a sheet. The rest stays in the email.
03
The tenant asks a third time
Done was a reply-all, a photo, or silence. The record never became a job the crew could close.
The draft
Same gate. Different sentence.
WhatsApp, SMS, email, and voice land in the same Queries inbox. The second email is still one thread the business owns, not a personal mailbox nobody else can see.
Draft
“Zone damper on floor 3. Tenant already emailed twice.”
- Service
- 87%
- Site
- 91%
- When
- 40%
- Problem
- 94%
HVAC / damper
Floor 3
Unspecified
Zone damper
The path
First message to job done.
01
They write on the channel they already use
Email from the tenant. WhatsApp or a text from the site contact. A call if they pick up the phone. They should not learn a portal to report a damper.
02
Both land in one inbox
Queries ties the thread to the business. AI drafts service, floor, and the problem. A missing window stays a missing window, 40% is visible.
03
You convert before the third email
Approve, set the window, assign. The model does not invent a slot because the tenant is impatient.
04
The crew closes on the phone
Site, notes, your checklist, photos, signature. The customer, or the tenant contact, is told it is done.
In the office
One inbox for every site that writes in.
WhatsApp, SMS, email, and voice, same Queries. You see who needs a person. Convert, link the customer, assign from the list. Many sites do not need many products. They need the thread to become a job the business owns.
Queries · one inbox
In the field
The crew member opens floor 3, not a forwarded email.
Job record: site, briefing, status, maps, checklist you configured, photos, signature. Same PWA as every other vertical. No customer portal, they already wrote.
FAQ
Straight answers for this trade.
No. They write or call. There is no end-customer web portal.
No. WhatsApp, SMS, email, and voice land in Queries, one operational inbox owned by the company, not a personal mailbox.
The draft shows it. Low confidence stays visible. You set the window when you convert. Software does not invent one.
No. Most FM tools start at the asset or the ticket form. We start at the message. Architecture stays generic.
Other trades
Same path. Different sentence.
Bring a real multi-site request to the next conversation.
Tell us how a request becomes a job today. We walk the inbox-to-job path if it fits.