Right person.
Right zone.
Right shift.
Tasks route themselves to staff who are on shift, in the correct zone, and qualified for the work — checked in, location-aware, skill-tagged.
A guest sends one WhatsApp. MessageBox decomposes it into tasks, assigns them by zone and shift, schedules escalations before they're late, notifies the guest when help is on the way — and closes the loop with proof. Auto-pilot for service delivery.
Tasks route themselves to staff who are on shift, in the correct zone, and qualified for the work — checked in, location-aware, skill-tagged.
Two pre-due nudges, one alert at the deadline, one configurable matrix that lifts the task up the chain. The guest never has to be the alarm clock.
Pre-arrival amenity setup. Post-departure deep clean. Sunday brunch turnaround. Created in advance, fired on the dot.
One request fans out into multiple sibling tasks that run concurrently. Towels and pillows shouldn't queue behind each other.
For workflows that genuinely depend on order. The next step doesn't fire until the previous one closes — with proof.
Acknowledged. On the way. Delayed. Done. Auto-sent on the channel the guest used — WhatsApp, webchat, email — in their language.
Pull a second cleaner, a porter, a runner onto a task that turned out to be larger than it sounded.
From PMS in real time, or via SFTP. Loyalty tier, allergies, language, preferences. The staff sees the human, not a room number.
Staff check in to a zone for the shift. The system knows who's near what — so requests go to the closest qualified pair of hands.
Mario gets a "Not Assigned" nudge in his task chat. The guest doesn't see it. Just supervisors.
If the task hasn't been accepted, the supervisor is notified. Still pre-due.
The deadline arrives and the work hasn't closed. Supervisors are now in the chat with the original guest message attached.
From here, the property's own rules apply: GM, Resident Manager, on-call duty manager, paging tree. You wrote the matrix, we run it.
Use one or all three on the same property — in the same shift.
Different properties need different physics. We support all three.
Whatever the guest or staff member uses, MessageBox accepts.
Four escalation types, layered on every task:
Three modes, mix and match by department:
Three different physics, depending on what your operation believes about priority:
Two paths into the platform, both running side-by-side at most properties:
The data shows up identically on the mobile app and the desktop console.
Six. Whichever the guest or staff member already prefers: