Raise it from the app
Staff report an issue with a photo and the site in seconds.
Broken equipment, missing materials and pay questions arrive as trackable requests instead of five parallel chats.
Staff report an issue with a photo and the site in seconds.
Maintenance, HR or materials — each category has a named owner.
The person who raised it sees whether it is open, in progress or resolved.
Questions and answers stay on the ticket, not in a private chat.
Frequent requests show where a process or an instruction is missing.
Answers can be turned into articles so the question is asked once.
A broken device reported at 9pm in a group chat sinks below other messages and resurfaces two weeks later. As a ticket, the same issue stays visible until someone closes it.
When routine questions — payslips, leave balances, material orders — go through the help desk, the shift lead stops being the switchboard and requests reach the person who can act.
Before you commit to any workforce software, get these points in writing — from us and from every other vendor. Our answers are below; we go deeper in the demo.
Yes. We provide a DPA under Art. 28 GDPR and sign it with you before your team starts using the app.
Hosting and database run on Supabase. The exact region and the sub-processor list are set out in writing in the DPA — not only on request.
Location sharing is opt-in per person — refuse it and clock-ins still record, just without coordinates. Reporting and access scope can be restricted per role. The contested points are settings you negotiate concretely in a works agreement.
Time and absence records stay for the legal retention period, then are deleted. All core and time data exports as CSV/Excel — you take your data with you when you switch.
No, it is for requests from your own team — maintenance, materials, HR questions.
Yes, owners are set per category and site.
No, people see their own; owners see their area.
You can see how many requests are open and where they cluster.