In this guide
Define What Truly Constitutes an Emergency
A meeting to convene or a copy of the budget statement don't have the same priority as a major leak or someone stuck in an elevator. The management office should publish concrete examples of emergencies, major failures, and routine requests.
Separate Your Personal Number from the Office Channel
A private number creates dependency on a single person. Better to have an official channel capable of identifying the sender and the building, collecting text and photos, classifying the problem, and alerting someone for critical cases.
Automated Responses Must Not Pretend
After hours, it's useful to confirm that the request has been received. However, it's dishonest to make people believe a technician is already intervening when it's not true. Automation should reduce uncertainty, not invent false certainties.
Create Sustainable On-Call Availability
The fundamental rule is that every after-hours repair must be logged. The following morning it should be possible to know who called, what problem was reported, what instructions were provided, and whether the matter is still open.
Reduce Calls Without Closing the Door
Many nighttime calls don't stem from a new failure, but from the lack of updates on an already known issue. A status system—received, assigned, scheduled, in progress, closed—reduces anxiety and interruptions.
Ready-Made Policy for Your Office
Publish a page with regular hours, official channel, definition of emergency, public emergency numbers, indicative timeframes for routine requests, and update procedures.
Frequently asked questions
Sources and further reading
Want to turn WhatsApp into a workflow?
See how qb-Domus turns reports, photos and voice notes into trackable tasks.
REQUEST EARLY ACCESS