Sync a Slack User Group with Your On-Call Schedule

A Slack user group like @oncall-backend is the easiest way for the rest of the company to reach whoever is on call: no one has to look up a schedule, they just mention the group. It only works if the group always contains the current on-call engineer. This guide covers why manual updates fail, what an automatic Slack user group sync with your on-call schedule should do, and how to set one up.

Why Sync a Slack User Group with the On-Call Schedule

• One handle for the role, not the person. Support, sales and other teams mention @oncall-payments instead of guessing who is on call this week.
• Nobody pings the person who just went off call. The group changes at the handoff, so the previous engineer stops getting mentions.
• Works in workflows and bots. Alert bots, Slack workflows and runbooks can mention the group and always reach the right person.

The Manual Way, and Why It Breaks

Without automation, someone edits the user group at every handoff: open Directories, then User groups, pick the group, remove last week's engineer and add this week's. It looks simple, but in practice:

• Handoffs happen on Mondays at 9:00, and whoever is supposed to update the group forgets or is in a meeting.
• Swaps and overrides happen mid-week and never reach the group.
• Only admins can edit user groups in many workspaces, so the person who knows about the swap often cannot make the change.
• An out-of-date @oncall during an incident sends the first page to the wrong person.

What a Good User Group Sync Should Do

• Follow the real schedule, including overrides and swaps, not just the base rotation.
• Change at the handoff time, in the team's time zone.
• Read from where the schedule lives: a rotation built in Slack, or PagerDuty, Opsgenie, Jira Service Management, Datadog or Google Calendar.
• Handle several groups, one per team, plus optional primary and secondary groups.
• Tell people. Update the channel topic with the current on-call and post a reminder before each handoff.

How to Sync a Slack User Group with Pagerly

1. Add Pagerly to Slack and create a team for the rotation.
2. Choose the schedule source. Build the rotation in Slack, or connect your PagerDuty, Opsgenie, JSM, Datadog or Google Calendar schedule so Pagerly follows it.
3. Pick the Slack user group to keep in sync, for example @oncall-backend.
4. Optionally pick a channel whose topic should show the current on-call, and turn on reminders before each handoff.

From then on, Pagerly moves the user group to the next person at every handoff and applies overrides as they happen. See create rotations on Slack for building a rotation from scratch, or the guides for PagerDuty and Slack and Opsgenie and Slack if your schedule already lives there.

Best Practices for On-Call User Groups

• Name groups by role and team: @oncall-payments, @oncall-platform, @support-today.
• Keep the group to the people actually on call. A group of the whole team turns every mention into noise.
• Add a secondary group (for example @oncall-payments-backup) for escalations.
• Pin how to reach on-call in your help channels so other teams use the group instead of DMs.
• Remember the plan requirement: Slack user groups need a paid Slack plan.

FAQ

Can Slack update a user group automatically from a schedule?

Not natively. Slack has no schedule-based user group updates, so teams use an app such as Pagerly or a custom script calling the Slack API.

Does PagerDuty sync Slack user groups?

PagerDuty's own Slack integration focuses on incident notifications and actions. Pagerly can read PagerDuty schedules and keep Slack user groups in step with them while PagerDuty continues to page.

How many user groups can I sync?

As many as you have rotations. Each Pagerly team keeps its own group, and you can combine rotations into one group if several teams share an on-call handle.

Want an @oncall that is always right? Pagerly keeps Slack user groups in step with your rotation, including swaps and overrides. Get started free