Tenant issues, on the owner's record
Tenants report by phone in under a minute. Every request becomes a work order you can see — with a status, an assignee, and a clock. Nothing lives in a manager's inbox.
Tenant signs in by SMS
+1 (312) ••• 4417 verified with a 6-digit code · Suite 210, Meridian Office.
Request submitted
REQ-1187 · HVAC · description and 2 photos attached from the phone.
Work order created
WO-2240 lands in Facilities — status, priority, and aging clock started.
Resolved & tenant notified
AI-drafted status update approved and sent by SMS. History kept on the record.
From a tenant's phone to your work-order queue
One record, two views. The tenant watches their request; you watch the work order it created. Neither side wonders what happened.
No cooling in Suite 210 since this morning — thermostat reads 78°.
Submitted in the app
Category, description, photos — one form, SMS-verified.
Work order created
The request lands in Facilities as WO-2240, priority set.
Team posts updates
Every staff update joins the activity feed — name, role, timestamp.
Tenant notified
AI drafts the SMS status update; it goes out once approved.
The same row your aging board watches — SLA timers included.
You're not buying a tenant app. You're closing the gap between "a tenant reported it" and "the owner can see it."
Tenant issues used to enter the record only if a manager typed them in — after the call, maybe, eventually. The Tenant Requests app moves that entry point to the tenant's phone, so the issue exists in your trusted data layer from minute one. Your managers still do the work. You just stop depending on their inbox for the truth.
Friction low enough that tenants actually use it
A reporting channel only works if it beats calling the office. Sign-in is a text message; a request takes a category, a sentence, and a photo.
SMS sign-in, no passwords
A phone number and a 6-digit code. Sessions persist, and tenants with multiple units pick the unit first.
Eight categories, not a blank box
Photos tell the story
Up to 5 photos per request, straight from the phone's library — thumbnails right on the request card.
An activity feed, not a void
Chronological updates from the property team — author, role, and timestamp on every entry.
Every request is a work order you can inspect
Requests don't go to a tenant portal you'll never open. They land in the same Facilities queue as everything else — aging, status, and response time per manager, on the record.
- Aging clocks start at submission — not when a manager gets around to logging it.
- AI-drafted tenant updates go out by SMS once approved — the black hole is closed from both ends.
- Response times feed manager accountability — measured, not remembered.
See your portfolio in one trusted owner view.