Combine multiple rotations into a single @mentionable user group for follow‑the‑sun and split‑shift schedules.
-
All Slack workspace users.
To post updates in a private channel, add Rotation App to that channel first.
What is a Rotation Cluster?
A Rotation Cluster lets you combine multiple rotations and manage them as a single, easy‑to‑mention Slack user group. Give the cluster a name (for example, On‑call engineer) and Rotation App will automatically create and maintain a corresponding user group handle (for example, @on-call-engineer).
When the on‑call user changes in any included rotation, the cluster’s user group is updated automatically and the change is announced in the selected channel.
Why use a cluster instead of one big rotation?
- Keep separate pools of users with different schedules (time zones, teams, products).
- Tailor intervals and durations per pool, while still having one handle to mention.
- Swap or substitute users inside each pool without affecting the others.
How it works
- Name: Used to generate the Slack user group handle for the cluster.
- Rotations to include: Select two or more existing rotations. The cluster reflects whoever is on call across those rotations at any moment.
- Reminder channel (optional): Rotation App announces changes to the cluster’s assignment here.
If two included rotations overlap in time, the cluster will contain multiple users. Mentioning the cluster will notify all current assignees.
Step‑by‑step: Create a Rotation Cluster
- Go to Rotation App’s Home tab: Find the Home tab.
- Open the Rotation Cluster creation dialog.
- Enter a cluster name (this generates the
@handle). - Select the rotations you want to combine.
- Pick the reminder channel (optional).
- Create.
You can edit the list of included rotations later by opening the cluster settings.
Use cases
Follow‑the‑sun on‑call coverage
Have regional rotations (e.g., North America, EMEA, APAC) and combine them so @mentions reach the current region’s assignee. Read the full guide →
Cross‑timezone support shifts (East/West)
Split coverage into East/West rotations and cluster them under a single handle (e.g., @star-of-the-day).
Read the full guide →
24/7 on‑call coverage (8‑8‑8 shifts)
Run three daily 8‑hour blocks and cluster them under a single handle for continuous coverage. Read the full guide →
Day vs. overnight staffing (separate pools)
Keep separate day and overnight pools in distinct rotations, then cluster so @oncall always reaches the right person.
Read the full guide →
Primary/secondary escalation pairing
Pair a primary rotation with a secondary backup and mention one handle to reach whoever is active. Read the full guide →
FAQs
Do included rotations need to be in the same Slack workspace? Yes.
Can clusters be nested? No. Clusters include rotations, not other clusters.
What happens if two included rotations overlap? The cluster will have multiple members at that time, and mentioning the cluster will notify all current assignees.
Can I post updates in a private channel? Yes, add Rotation App to the channel first.
Do the source rotations need user groups? No. The cluster manages its own user group.
How do I handle holidays or exceptions? Make changes in the individual rotations (e.g. cancel a week, reorder the queue); the cluster updates automatically.
Is there a limit to the number of rotations in a cluster? There’s no strict limit, but we recommend keeping it small for clarity (for example, ≤ 10 rotations).