Configure multi‑timezone on‑call coverage (NA/EMEA/APAC) with one @mention using Rotation Clusters.
Overview
This guide shows how to build a follow‑the‑sun on‑call schedule in Slack using Rotation Clusters so your team can mention a single handle (for example, @on-call-engineer) while coverage moves across regions. If you need a multi‑timezone on‑call rotation across NA, EMEA, and APAC, this is the standard “follow the sun” approach to a Slack on‑call schedule.
Prerequisites
- You know how to create a rotation.
- Optional: a channel where Rotation App will post reminders and changes.
Steps
- Create three regional rotations with local users and timezones:
- On‑call engineer North America — daily, starts 09:00 in the NA timezone (for example, UTC-5); duration 8h.
- On‑call engineer EMEA — daily, starts 09:00 in the regional timezone (for example, UTC+1); duration 8h.
- On‑call engineer APAC — daily, starts 09:00 in the regional timezone (for example, UTC+9); duration 8h.
- Create a Rotation Cluster named On‑call engineer and include the three rotations.
- Pick a reminder channel (optional). For private channels, add Rotation App as a member first.
Now @on-call-engineer always mentions the person on duty in the active region.
Variations
- Different shift lengths per region (6h/10h/8h) still work; the cluster reflects the current assignee(s).
- Overlaps at hand‑off time are fine; the cluster will include both people briefly so @mentions notify both.
FAQs
Can we start regional shifts at different local times? Yes. Configure each rotation’s timezone and start time independently.
How do we pause a region for holidays? Make changes in that region’s rotation; the cluster updates automatically.
Can we include a backup per region? Yes—add a second rotation per region (for example, EMEA‑backup) and include it in the same cluster.
What timezone should we use? Choose the timezone that matches the team’s working hours for that region. For fixed handoff times, specify them in UTC.