The hotel's faults, finally in order.
The room attendant reports a fault from her phone, maintenance fixes it with a photo and management sees where the time goes. No WhatsApp groups, no paper work orders.
- first vertical
- Hotels
- format
- iOS/Android apps + back office
- status
- launching
- Opened by Marta · Housekeeping08:12
- Assigned to Maintenance08:14
- Luis starts it08:31
- Closed with photo09:05
A fault reported over WhatsApp does not exist.
In most hotels, faults are reported out loud, by phone or in a group chat. That works right up until someone needs to know what is still open, who fixed it, or how long a leak on the third floor usually takes.
Report, assign, resolve — and be able to prove it.
Everyone sees their own, without the noise.
Permissions are granted per department, not per person: someone can report in reception and resolve in maintenance. And the housekeeper still has authority over what her attendants report, even when another department is doing the fixing.
Housekeeping and reception. They open the ticket with a photo from the phone, on the spot, and follow their own.
Maintenance. Sees its inbox and what is assigned, picks up work itself and closes with evidence.
Heads of department and management. They assign, prioritise, reopen and read the reports. Owners and auditors, read-only.
Management sees the whole hotel at a glance.
What is open, what is in progress, what was closed today and how long it takes. Without asking anyone for a report: the dashboard feeds itself from what the team does on their phones.
| Ticket | Location | Department | Priority | Status |
|---|---|---|---|---|
| #2041Leak under the sink | Room 304 · Floor 3 | Maintenance | High | In progress |
| #2040Fire extinguisher check | Basement · Plant room | Maintenance | Medium | New |
| #2038AC not cooling | Room 212 · Floor 2 | Maintenance | Medium | Assigned |
| #2036Curtain off its rail | Room 118 · Floor 1 | Housekeeping | Low | On hold |
| #2029Key card will not open | Room 401 · Floor 4 | Reception | Low | Closed |
Built so no hotel can see another's data.
It is a multi-tenant platform: every hotel shares the infrastructure, and none can see a single row belonging to another. That is not solved by being careful while coding, but in the database itself.
- 01Isolation in the database. Every row carries its tenant and the engine refuses to read it from another, even if a query is written badly.
- 02Native iOS and Android apps for field staff, with a persistent session on personal phones and PIN entry on shared devices.
- 03Photos and attachments in European storage, with signed download links that expire.
- 04Monitored from day one. Errors, metrics and an external check that the API responds, with alerts to on-call.
Do you run a hotel with the faults in your pocket?
We are opening Ordenly with our first hotels. If you want to see it with your own rooms and your own departments, get in touch.
Request a demo