What happens when someone calls in sick at 05:32

It is 05:32. Jacob is due in at Station Road at 07:00 and he is not well. This is what happens next.

The call

Jacob rings one number. It is the same number for every site, and it is answered 24 hours a day, 365 days a year. Nobody has to find a manager's mobile or hope a text gets read.

The call is answered and asks the same questions every time: who is calling, which site, what the reason is, which shift they will miss and when they expect to be back. The call is recorded.

Before the shift

By the time the call ends, the absence is on the dashboard with the reason, the shift and the expected return. The named manager, the backup manager and the store inbox are emailed, and Jacob gets a copy too. The manager sees it in the managers' app before the 07:00 shift, not when they arrive and find a gap on the rota.

When he comes back

When Jacob returns, the return to work is recorded against the same absence, along with any self-certification or fit note. Nothing is pieced together afterwards from texts and memory.

When it becomes a pattern

If Jacob reaches a trigger point in your absence policy, Manage opens a case with an owner and a next step, through to the outcome. Your policy sets the trigger points, not ours.

Why it matters

Anyone can answer a phone. Knowing what to ask, every time, at every site, is the part that makes the record worth having. One record means the same absence reads the same way at your first site and your sixtieth.

Book a 20-minute demo to see it with your own sites.

Jacob is a fictional employee. The questions are the ones we ask.