Queue by location
Cases grouped by building and by place inside it. A general manager's queue covers their own sites and nothing else; an owner sees the whole circuit in one list.
Case monitor
A complaint that lands in an inbox is a message. A complaint that lands here is work with a name on it: queued by location, dispatched, noted, timed, and finished with a history anyone can read afterwards.
A 20-minute walkthrough on your own locations. We reply within one business day, and every plan is backed by our 30-day guarantee.
Cases grouped by building and by place inside it. A general manager's queue covers their own sites and nothing else; an owner sees the whole circuit in one list.
Add notes, attach photos of the work, @-name a colleague to ask them about it. Everything stays on the case rather than in somebody's messages.
Who did what and when, in order, including everything the AI triage decided. A case that took four days can be explained after the fact.
How long each case has been open, and the age of everything waiting. Resolution statistics per site and per issue type.
Press Ask, or type @ in a note, to bring in up to five people who can already open the case. Until they answer, the case says who it is waiting on, and their next note is the answer.
Each person can add a profile picture in Settings, and it sits beside their name on every note and question they leave on a case.
A shift manager on the back-office tablet can press 'I have fixed this' and say what they did. The case then reads Awaiting sign-off until a manager signs it off, and Mark resolved starts from their sentence.
Closing a picture or sound case in an auditorium can record the swap that fixed it: tick Equipment changed, choose what was replaced and type the new serial number, and the screen's equipment record is updated as the case closes.
Tell the AI assistant what happened and it drafts a note on a case, a new case or a closure as a card. Nothing is saved until you confirm it, and the history says it came via the assistant.
Each thing an inspector asks to be put right becomes a case at that building when the visit is recorded, saying which inspection asked for it and the date it is due by.
One-step triage: unsure reports go to review. The AI Reviewer Agent reads each report as it arrives and sends the ones it is very sure are genuine straight to the people who handle that issue type at that location — automatically, the moment they land — folding a report into the open job when it is plainly the same fault. It never rejects anything, and costs nothing from the AI allowance. Anything it is unsure about is held for a person to review.
Two-step triage: unsure reports get a second, deeper look. Same automatic dispatch for clear-cut reports, but anything the first pass is unsure about gets a closer look from the AI Reviewer Agent, which applies its own verdicts with nobody confirming — genuine reports released on the spot, clear junk rejected with the AI's reason on the record and reopenable like any other rejection. Anything still unclear goes to review for a person. Two-step needs the AI assistant on and draws on the AI allowance.
In both options, every emergency — without exception — is held for a person. Every decision sits in the case history under the AI's own name, so nothing it did is invisible or unattributable.
You can also turn automatic triage off entirely — one setting for the whole account, chosen by its account admin — and confirm every report by hand. The guardrails are the feature: they are the reason an owner would let software route a guest complaint at all.
Email, SMS and web push. Web push reaches a phone's lock screen with no app store in between — built for a duty manager walking the building, not sitting at a desk.
The week in one email for the people who run the circuit: what came in, what closed, what is still open. An owner with twenty buildings does not open a dashboard every day.
It is where a guest report stops being a message and becomes work. Each report opens as a case with the site and room already attached, and carries notes with photos, a status, and a full history of who did what and when. Cases queue by location, so a general manager sees their own buildings and an owner sees the circuit.
Each case shows how long it has been open, the overview charts the age of everything waiting, and the AI assistant can list the cases open too long for their impact, so a slow one is visible before anybody has to chase it. Resolution statistics are kept per site and per issue type, so a building that is slow on one kind of problem is visible as a pattern instead of an impression.
One-step triage is the default. The AI Reviewer Agent reads each report as it arrives and sends the ones it is very sure are genuine straight to the people who handle that issue type at that location, folding a report into the open job when it is plainly the same fault. It never rejects anything: whatever it is unsure about goes to review for a person — or, on Two-step triage, gets a closer look from the agent first. You can also turn automatic triage off entirely and confirm every report by hand, if that is how your team wants to run it.
Both read every report as it arrives and send clear-cut genuine ones straight to the people who handle that issue type at that location. The difference is what happens when the AI is unsure: on One-step triage, that report goes to review for a person, and nothing is ever rejected. On Two-step triage, the AI Reviewer Agent takes a closer look first and applies its own verdicts — releasing what is real and binning clear junk with its reason on the record — and anything still unclear then goes to review for a person, same as One-step. Two-step needs the AI assistant on and draws on the AI allowance; One-step costs nothing from it.
Every verdict is recorded in the case history under the agent's own name, with its reason. A report the agent binned as junk — which only happens on Two-step — is reopenable like any other rejection, so a wrong call is a visible, reversible entry rather than a silent deletion.
No. In both One-step and Two-step triage, every emergency — without exception — is held for a person. Automatic triage speeds up the clear-cut reports; it does not remove a person from the ones that matter most.
Email, SMS and web push. Web push puts a report on a phone's lock screen with no app store in between, which matters for a duty manager who is walking the building rather than sitting at a desk.
One email at the start of the week for the people who run the circuit: what came in, what closed, and what is still open. An owner with twenty buildings does not open a dashboard every day, and the digest is written on that assumption.
Yes. Resolution statistics break down per site and per issue type, and the case queue filters to a single building, so a regional conversation can be had with the same numbers everyone else is looking at.
For admins, the rail down the left opens the Overview — tiles for what needs review, screens down, repeat issues and reports waiting over 48 hours, and charts of what is open by location and by issue type and of the age of what is waiting — then every location with its open count, one press each. Where the weather is switched on, it also has Weather ahead: each day in the next seven with rain, snow, thunder, heat, a freeze or strong wind, and what days like it have brought in reports at that cinema. A manager's case monitor only ever holds their own buildings, so it has no rail.
Yes. Under Your issue types in Settings, each admin can choose which issue types their case monitor shows. A screen that is down still comes through whatever it is filed under, Show all brings everything back until the page is next opened, and Settings warns while any issue type has nobody looking after it. It changes what the list shows, not who is notified.
Yes. Search on Home — Ctrl+K, or / — finds a case by its reference, the guest's words, the film, the place or the issue type, and for an admin it opens the case at whatever stage it has reached, including one closed months ago.
Yes, whenever there is something to say: how many inspections failed with no pass since, are overdue, are due soon or have actions past their date, how many booked visits went by with nothing recorded, and how many certificates managers handed in are waiting to be filed.
Cases start at a placard — guest issue reporting — and who can see which of them is set in roles and access. Back to all features.
A 20-minute walkthrough on your own locations. We reply within one business day, and every plan is backed by our 30-day guarantee.