The fault disappeared in a chat thread
Reported in chat — no queue, no status.
One queue: New, In progress, Resolved, Closed.
How the Offision ticket queue worksProblems you recognise Floor space
A dead projector is a floor problem. Most offices still run it on a chat thread, then book the same room tomorrow.
Content reviewed: September 2026
Reported in chat — no queue, no status.
One queue: New, In progress, Resolved, Closed.
How the Offision ticket queue worksTwo taps at the panel — fastest report, no follow-up.
Report from the panel as the room.
How Offision panel reporting worksSupport notified; reporter hears nothing back.
Support replies in app — reporter is told.
How Offision tells the reporterOpen tickets — room still takes bookings.
Ticketing separate from taking a room offline.
How Offision separates tickets from closing a roomThe same problem costs each group something different — and they rarely compare notes.
They lose the meeting to a dead screen, report it once, and book the same broken room next week.
They hear about faults twice — once as a shout, once as a complaint it is still broken — with no list of what is still open.
They cannot prove which rooms break most often, because the reports never became tickets against a resource.
No. Service is tea, cleaning and help attached to a booking. Ticketing is something broken, against a room or desk, with no booking required.
Hold Support staff and the app grows a Support page — that page is the queue. A ticket policy can also email a facilities role on that floor.
No. Close the resource in Booking if it should stop taking reservations. Tickets stay open until the fault is fixed.
Walk through your estate, your booking rules and your calendar setup with our team — or start free and try it on one floor.