Your building and room are already on file — you only describe the problem. If this is a life-safety emergency, call 911 first.
What are you noticing?
Pick the closest match. You don't need to know what's causing it — that's our job.
Tell us a little more
Tap what you're seeing. Skip anything you're not sure about.
Describe it in your own words
Talk or type — either works. Watch below: routing updates as you go.
Here's what we heard
Check this before it goes anywhere. Anything wrong? Fix it right here — the routing updates instantly.
Someone on your floor already reported what looks like the same issue:
Joining it means one ticket, more weight — the shop sees how many people are affected.
Request submitted
My requests
Nothing disappears into the system. Tap a request to see its full history — and only you can close it.
Where requests go
Every request lands with a specific team, on the record. Here's the full map — including why the lines are drawn where they are.
Standard tickets: if a shop doesn't acknowledge within 1 business day, the ticket auto-escalates to Tenant Relations for reassignment.
Urgent tickets: the shop is paged immediately; no movement in 2 hours escalates to the operations supervisor.
Work marked done: the ticket only closes when the person who reported it confirms the fix.
Operations report
Live from ticket data — the same numbers that feed the mayor's mandatory customer-service report. No spreadsheet assembly required.
Clean intake means fewer misroutes; fewer misroutes means fewer stagnant tickets; tenant-confirmed closure means "closed" actually means fixed. Every number here traces to a ticket event — auditable end to end.
Everything here closes from the phone, in the hallway, the moment the work is done — no trip back to a desktop, no ticket left hanging overnight.