When the cool room alarms at 2am, who actually gets called?

The alert is worthless if nobody answers it

Most cool room failures do not happen at a convenient hour. A compressor trips after the last person leaves, a door is nudged open on a long weekend, or the power drops at 2am. The temperature climbs quietly for hours. Whether you lose the stock or save it comes down to one thing: did the alarm reach a person who could act, in time to act?

A sensor that sends a single notification and then goes quiet has done its job on paper and failed you in practice. The message lands on a phone that is face-down, on mute, charging in another room. Nobody sees it. Morning comes, and so does the bin run. The fix is not a louder sensor. It is a chain of people, in order, that keeps trying until one of them says, "I have got it."

Build the chain: first, second, third person

An escalation chain is just an ordered list of who to reach and in what order. The order matters more than the names. Put the person most likely to answer and act at the top, not the most senior person on the org chart.

• First person, the fastest responder. Usually the duty manager or the closest on-site staff member during trading, and an on-call lead or the owner overnight. This is whoever can either attend the room or immediately phone someone who can.
• Second person, the backup. When the first person does not answer within a set window, the alarm moves on without waiting around. A missed call should never be the end of the line.
• Third person, the catch-all. Often the owner or a senior manager who would rather be woken than lose a room of stock. This is the safety net that ensures the alarm always lands somewhere.

Three names is a sensible baseline. Fewer, and a single unanswered phone leaves the room unwatched. Many more, without a clear order, and everyone quietly assumes someone else is handling it. Short, ordered, and made up of people who can genuinely respond overnight beats a long list of names who cannot.

Acknowledge before loss

Here is the principle that separates a real escalation system from a notification: the alarm keeps climbing until a person confirms they have seen it and are dealing with it. That confirmation is the acknowledgement. Until it happens, the system does not assume the message got through. It moves to the next person.

Sent is not the same as seen, and seen is not the same as handled. A chain built around acknowledgement treats every unanswered step as a failure to escalate past, not a task completed. In practice that looks like this:

• Push first, for the moments someone is already looking at their phone.
• Then SMS, which cuts through where an app badge sits unnoticed.
• Then a phone call, which is genuinely hard to sleep through.
• Then the next person, and the next, until someone acknowledges and the escalation stops.

The reason this matters is timing. Acknowledging at 2:15am while the room is still cold means you attend, find the tripped compressor, and reset it before anything is lost. Discovering an unread notification at 7am means the decision was already made for you, hours ago, by a phone on silent.

Give people a window, then move on

A good chain does not wait forever on any one person. Each step gets a short window, a couple of minutes, to acknowledge before the alarm escalates to the next name. That window is a balance. Too short and a first responder who is genuinely on their way gets skipped needlessly. Too long and the stock keeps warming while the system politely waits.

The other half of the pattern is what happens when the list runs out. A well built chain never falls silent after the last name. It loops, repeats, or keeps re-alerting so the problem stays in front of someone. An alarm that gives up quietly is the same as no alarm at all.

The real enemy: alarm fatigue

There is a failure mode that quietly undoes every carefully built chain, and it is not a technical one. It is human. If people get woken by alarms that turn out to be nothing, a door opened for thirty seconds, a sensor twitching at the edge of a threshold, they learn to ignore the alarm. The next call, the real one, gets silenced half asleep. This is alarm fatigue, and it is how good systems fail.

The whole point of escalation is that a call at 2am always means something. Protect that. Every alert that reaches a person overnight should be worth getting out of bed for. You keep it that way by tuning the system, not by asking people to try harder.

• Set thresholds with a margin, so a room drifting a fraction above target does not trigger a call the moment it does. Alert on a genuine, sustained excursion, not on noise.
• Add a short delay before escalating, so a brief door opening during a late delivery settles on its own instead of waking the owner.
• Separate urgent from informational. A trend warning that a room is slowly climbing can be a quiet daytime message. A room already in the danger zone at night is a call. Do not send both down the same wire.
• Review what fired and why. If a particular sensor or room keeps crying wolf, fix the cause, a failing door seal, a badly placed probe, rather than letting people learn to tune it out.

A quiet alarm is a trusted alarm. The fewer false calls it makes, the more seriously every real one is taken.

Match escalation to who is actually awake

Escalation is not one fixed list. The right people to call at 3pm on a Tuesday are rarely the right people to call at 3am on a Sunday. A daytime chain might run through floor staff and a manager who are all on site. An overnight or long-weekend chain needs people who are genuinely reachable and willing to act when nobody is at the venue.

It is worth walking through your worst case out loud. Power drops on a public holiday Saturday night. Who is first? Do they have signal where they sleep? If they do not answer, who is second, and can that person reach the venue or send someone? If the honest answer is that nobody would realistically respond, the chain needs different names, not a louder ringtone.

Set it up right, or have it set up for you

You can configure an escalation chain yourself if your monitoring supports it, and for a single room with a clear on-call person that may be all you need. The reason most hospitality and food businesses hand it over is the detail that self-setup leaves to you: the order tested against real overnight scenarios, the thresholds tuned so calls are trustworthy, the acknowledgement flow confirmed to actually loop, and someone keeping the list current as staff change. Coolroom Alarm is part of our wider temperature monitoring work, and if you would prefer the hardware only you can buy the kit and set up the chain yourself.

An escalation system is a safety and wellbeing aid for your stock and your business, not a guarantee. No system detects every event, and no chain can promise that a person will always answer. What a well ordered, well tuned chain does is stack the odds firmly in your favour: the right person, reached the right way, in time to still do something about it.

Common questions