Your team is spread across the globe, so at almost any hour someone is at their desk. When an alert fires at 3 AM for the engineer on the rota, AlertKick asks the shift that is actually awake to take it first - in Slack, with an Acknowledge button - and only wakes the rota engineer if nobody picks it up. The rotation itself stays a plain, boring rota.
Hatched stretches are gap hours - nobody on shift. You decide whether those page immediately or nudge with a shorter wait.
A disk fills up at 10:00 UTC. The rota says Kai is on call - but Kai is in Sydney, where it is 3 AM. Meanwhile the EMEA half of the team is sitting in Slack, coffee in hand, perfectly capable of restarting that consumer. Every on-call tool still wakes Kai, because the schedule is the only thing it knows. The awake teammates find out the next morning, along with an apology channel full of "sorry, I could have grabbed that".
On-call platforms have always answered follow the sun with homework: one schedule per region, stacked in layers, glued together with time-of-day routing rules that you maintain forever and that quietly break when the clocks change. AlertKick makes follow the sun a schedule type you pick when you create the roster. The rotation stays exactly what it was - daily or weekly, with overrides, swaps, and calendar feeds - and you add your shifts to it: EMEA works 08:00 to 16:00 London time, APAC works 22:00 to 06:00 Sydney time, each shift with its own members and its own Slack channel. Your existing rosters are untouched.
When an escalation level targets a follow-the-sun roster, the algorithm checks one thing before paging: is the rota engineer inside their working shift right now? If yes, they are paged normally and nothing is different. If it is their night, the alert is posted to the awake shift's Slack channel with an Acknowledge button and a plain statement of the stakes: this person will be paged in 5 minutes unless someone takes it. One click acknowledges the alert everywhere and the page never fires. No click, and the rota engineer is woken exactly as the escalation policy says - the nudge adds one bounded wait, never an unbounded silence.
Weekends and coverage gaps are explicit, not accidents. If an alert fires when no shift is on the clock, you choose the behavior per roster: page immediately, or nudge the roster's default channel with a shorter wait and a message that says plainly that nobody is in working hours. There is also a per-roster switch to let critical-severity alerts bypass the nudge entirely - some pages should never wait five minutes, and that is your call, not ours.
The schedule timeline shows each shift's working window as a tinted band behind the rotation bars, so "Kai's bar outside Kai's band" is visible at a glance before any alert ever fires. A 24-hour coverage strip shows the handovers and the gaps in your own local time. And every nudge is recorded on the alert's activity timeline - who was asleep, which channel was nudged, how long the wait was, and whether the page fired or was acknowledged away.
Install one agent. Get security monitoring, infrastructure alerts, and on-call management - all included with every host.