Escalations that reach a supervisor before the guest complains

What escalation means in TaskLoop

In TaskLoop, escalation means that a task still open after its deadline goes up to a supervisor automatically. Nobody has to notice it, remember it or raise it. This is the safety net under the whole loop. Even when a shift is chaotic, a late job does not stay hidden in someone’s pocket.

An SLA (service level agreement) is the promise behind the deadline, for example “urgent faults attended within 30 minutes”. Escalation is what happens when that promise is about to be broken.

The workflow, step by step

1. A deadline is set at assignment

When a supervisor or reception assigns a task on the admin dashboard, they give it a priority and a deadline. Here the SLA becomes concrete for that one job. “No hot water in 1508” might get 30 minutes, while “replace the bathroom shelf” might get the end of the day.

2. The owner works the task

The assignee accepts the task on the staff app and gets on with it. In most cases it is done before the deadline and nothing more happens.

3. Missed deadline, automatic escalation

If the task is still not complete when the deadline passes, it escalates to a supervisor. The supervisor sees which task is late, who owns it and what was asked.

4. The supervisor acts

The supervisor then decides what to do: reassign it to someone free, call the owner to find out what is blocking them, or move the deadline if there is a good reason, such as a part arriving tomorrow. The task stays tracked until it is completed, and the guest still rates it at the end.

Who uses it

What the screen shows

On the dashboard, overdue tasks stand out from the open list with their owner, original deadline and status. The supervisor can act on them from the same screen. In the reports, the effect of late tasks shows in response and completion times and staff performance, so repeat problems become patterns you can fix rather than anecdotes.

Writing SLA rules your team will actually keep

Start simple. Define two or three priority levels with a target time for each, apply them consistently when you set deadlines, and review late tasks every week. Avoid rules that nobody can meet, because they cause so many escalations that supervisors start ignoring them. Our guide to SLA and escalation rules for operations teams goes through a workable starting set.

A night shift example

At 11:40 pm a guest in room 905 reports that the toilet will not stop running. Reception logs it and assigns it to the maintenance department with high priority and a 30-minute deadline. The only technician on shift accepts it from the staff app but is called to a tripped breaker in the kitchen on the way. At 12:10 am the deadline passes and the task escalates to the night manager.

The night manager sees the task, its owner and the original request on the dashboard. They call the technician, learn about the breaker, and send a houseman with basic instructions to shut off the valve to the cistern. The technician closes the task properly once the kitchen is safe. Next morning, the guest rates the service and the late task appears in the reports. The chief engineer can then decide whether nights need a second technician.

Without escalation, the same story ends with the guest calling reception at 12:30 am, and nobody quite sure who had the job.

SLA timers and export

• Configurable SLA timers. Response and resolution timers are set per category and priority, for example every urgent “plumbing” job getting 45 minutes automatically.
• SLA reporting for outside parties. SLA reports export to PDF and CSV for owners or clients.

What it doesn’t do

• Multi-level escalation chains. The confirmed behaviour is escalation of overdue tasks to supervisors. Do not plan around further levels, such as automatically notifying the GM, until we confirm them in a demo.