Let Staff Send Reports From Their Phone
Let staff report problems from their phone by voice or text — routed to the right manager, with clear Sent, Seen and Result phases.
Staff Reports
Let Staff Send Reports From Their Phone
A freezer is making a strange noise. A delivery arrived short by two boxes. A guest complained about the same thing for the third time this week. Your staff member notices all of it. Then the shift gets busy, and by the time they clock out, it is gone.
This is not carelessness. It is friction. If reporting a problem means finding you in person, remembering it until the end of the shift, or opening a separate app nobody installed, most small problems never get reported at all. They get reported later, as big problems.
Loopapa gives every staff member a report button on the phone they already carry. They type it or say it out loud, it lands with the right manager, and both sides can see exactly where it stands. This article shows how staff reports work, what you see as an admin, and how a report moves from sent to resolved.
How does a staff member send a report in Loopapa?
A staff member opens their dashboard and taps Send Report. They can type what happened, or hold the record button and simply say it out loud. That is the whole action. There is no form to fill in, no category to pick, and no decision about who should receive it.
Speaking is the point. A staff member with wet hands, in a noisy room, halfway through a task, is not going to type three paragraphs about a broken fridge. They will hold a button and talk for twenty seconds. Loopapa's AI takes that recording and writes it up as a clear, structured summary — so the manager reads a short, organised account instead of listening to a rambling voice note and guessing at the details.
The report finds the right person on its own
Staff never choose a recipient. When a report is sent, Loopapa routes it to that staff member's direct manager. If the staff member has no manager assigned, it goes straight to the admin. This means a new hire on their first day can report a problem correctly without knowing a single name on the org chart.
Two sides, two different views
This is the part that makes reports work in practice, and it is worth being precise about.
What staff see
A dedicated Reports screen — their own inbox, separate from their task list. Every report they have ever sent sits there with a badge showing exactly what stage it is at. Reporting a problem never clutters up the work they still have to do.
What the manager sees
A task. The report arrives in the manager's normal task dashboard as an item that needs a decision — sitting alongside everything else that needs their attention, in the same place they already look.
That asymmetry is deliberate. For the person who reported it, the job is done and they want to know what happened next. For the person receiving it, it is not information — it is work. Treating it as a task means it cannot quietly sit in a message list waiting to be noticed.
If something is unclear, ask in the report
Every report carries its own chat thread. If the manager needs more detail — which fridge, what time, was anyone else there — they ask inside the report itself and the staff member answers there. The question, the answer, and the original report stay in one place, so nothing has to be reconstructed later from memory or from a chat app.
One more thing worth knowing: reports do not require a staff member to be clocked in. Regular tasks do, because a task is work being performed on a shift. A problem is a problem whether or not someone is on the clock, so reporting is always available.
Where is my report right now?
Every report a staff member sends sits in their Reports screen with a badge showing one of three phases. They never have to ask anyone whether it arrived, whether it was read, or whether anything came of it. The badge answers all three.
-
1
Sent
The report has been delivered to the manager, but nobody has opened it yet. It is waiting.
-
2
Seen
The manager has opened it. This flips automatically the moment they read it — there is no button for the manager to press and no way to read a report without the sender knowing it was read.
-
3
Result
The report is closed and archived, with the full thread kept as a record of what was reported and what was decided.
The automatic Seen phase is small but it changes behaviour. Most people stop reporting things when they suspect nobody reads them. When a staff member can watch their report get opened, reporting stops feeling like shouting into a void.
My Reports
Walk-in freezer noise
Sent by Marta · 14:20
Delivery short by two boxes
Sent by Marta · Tuesday
ResultThe staff member's own inbox — every report, every phase, in one list.
What does the manager actually do with a report?
A report is not a message to be read and forgotten. It arrives as a task, and a task needs a decision. The manager has exactly two ways to close it, and both are one tap.
Approve
The report is valid and accepted. It closes, moves to the archive, and shows up in the staff member's Result phase as an accepted report.
Reject
The report is not accepted — a duplicate, a misunderstanding, or something already handled. It closes and archives too, marked as rejected, and the staff member sees that outcome.
Either way, the report leaves the manager's active list. This matters more than it sounds. A report that cannot be closed without a decision is a report that cannot rot quietly at the bottom of an inbox. The only two exits are both deliberate.
Ask before you decide
If the report is not clear enough to approve or reject, the manager does not have to guess. The chat thread inside the report is there for exactly this. Which walk-in was it? Did you switch it off? Was the supplier still there? The staff member answers in the same thread, and only then does the manager decide.
A staff member who disagrees with a decision is not stuck either. They send a new report. Reports are cheap to send by design — one tap and a sentence — so the right response to a bad outcome is another report, not an argument.
Changed your mind after approving?
An approved report can be revoked. It returns to the active list and the review decision opens up again, so a call made too quickly at the end of a long shift is not permanent.
The reports nobody has to send
Not every report is written by a person. When a staff member finishes a shift, Loopapa writes a shift report on its own — the date, who worked, start and end times, total duration, and every pause with its exact time and length. Nobody has to remember to file it and nobody can forget.
A real example: the Bellhaven Hotel
The Bellhaven is a forty-room hotel with eleven staff across housekeeping, front desk and maintenance. Nadia works housekeeping. On a Tuesday morning she goes into the second-floor storage room for towels and finds water pooling under the sink.
She has nine rooms left to turn over before check-in. The old version of this morning has three endings: she tells someone in the corridor and they forget, she plans to mention it at handover and the handover runs late, or she deals with it herself badly. All three end with a maintenance bill that is larger than it needed to be.
What Nadia does
She takes out her phone, taps Send Report, holds the record button and says what she sees for about twenty seconds — where the water is, roughly how much, that the floor around it is already wet. Then she goes back to her rooms. Total time: under a minute, and she never had to find anyone.
Loopapa's AI turns that recording into a written report her supervisor can read in ten seconds, and marks it Critical — water spreading across a floor is both urgent and important, which is precisely the case the AI recognises. Because Critical has its own notification category, her supervisor's phone treats it differently from routine traffic. He is not going to see it at the end of the day. He sees it now.
What her supervisor does
The report lands in his task list as something to decide on, and it is routed to him automatically because he is Nadia's manager — she never picked his name. He opens it, which flips Nadia's copy to Seen. Reading it, one thing is missing: is the water still coming, or did something spill earlier? He asks in the report's chat thread. Nadia answers between rooms. It is still coming.
Now he can act. He approves the report and raises a task for maintenance with the thread attached, so the plumber arrives already knowing what was found, where, and when. Nadia sees Result on her phone and knows it is handled. Nobody asked her again.
Water under storage room sink
Nadia · Floor 2 · 09:12
Report
Standing water under the sink in the second-floor storage room. Floor is wet around it.
Supervisor
Still leaking now, or already stopped?
Nadia
Still dripping. Getting worse than when I found it.
The question, the answer and the report stay together in one thread.
What connects to staff reports?
Reports are not a separate product bolted on the side. They reuse the same pieces the rest of Loopapa runs on, which is why a report can turn into a task, a task can turn into a conversation, and a shift can turn into a report without anyone typing anything.
The chat thread
The thread a manager uses to ask "which sink?" is the same discussion thread that lives on every task in Loopapa, with the same unread badges and the same history. See how in-task chat works.
Priorities and the Critical flag
Reports carry the same four priority levels as tasks, and Critical is the one the AI identifies on its own. The rest you set by hand. Read about task priorities.
Shift reports write themselves
The automatic end-of-shift report — hours, pauses, durations — comes straight out of clock-in and clock-out. Nobody files it. See how attendance works.
The same voice engine
Holding a button and talking is not only for reports. The same AI turns a spoken sentence into a properly written task, with a title, a deadline and an assignee. Create tasks from voice.
Who receives the report
Routing follows the manager you assign to each staff member. Set that once per person and every report they ever send goes to the right desk. Managing your people.
Making Critical sound different
Critical is its own notification category, so it does not have to arrive the same way as everything else competing for attention on a phone. Set up notifications.
Do I need a paid plan to let staff send reports?
Reporting belongs to the core of how Loopapa works, not to an add-on. Sending a report by text or by voice, the AI write-up, the chat thread inside the report, the Sent and Seen and Result phases, the approve or reject decision, and the automatic end-of-shift report are all part of the product itself. You can set up a team and start receiving reports without configuring anything special.
Plans differ in scale and in the depth of some surrounding features rather than in whether your staff can tell you something is wrong. Because plans change over time, the honest answer to what each one includes lives in one place that is always current.
For the current breakdown of what each plan includes, see the Loopapa pricing page.
Frequently asked questions
The questions operators ask most often before rolling out staff reports.
Does a staff member have to be clocked in to send a report?
Who receives a report when a staff member sends one?
How does a staff member know their report was read?
Can a manager close a report without explaining anything?
What if the staff member disagrees with the decision?
Are closed reports deleted?
Your team already sees the problems. Make it easy to tell you.
Give every staff member a report button on the phone they already carry — and find out on Tuesday what you used to find out on Friday.
Start freeNo card required.