Why your Slack @oncall mention reaches the wrong person
Start with the group’s actual members. A schedule saying “Sam is on call” does not prove that Slack’s @oncall group contains Sam. If membership is right, check the mention itself, channel access and notification settings—in that order.
There are three separate things to verify: who should be responsible, who the Slack group currently contains, and whether the recipient sees a notification. Treating all three as “the rotation” makes a missed handoff harder to diagnose.
1. Compare the schedule with the real group
In Slack, open Directories → User Groups, choose the on-call group and inspect its members. A workspace user group requires a paid Slack plan; your administrator controls who can manage it. A group mention addresses its members, so a roster containing the whole team will not select one person for you. See Slack’s user-group guide.
Compare that list with the schedule at the same instant. Check the date, timezone and handoff time, then any temporary coverage. Write down both values before changing anything: “Schedule: Sam at 09:02; Slack group: Alex at 09:02.” That tells you whether to investigate the schedule or its synchronization.
For a manually maintained group, an authorized member can use Edit members to make the correction. If an app manages it, first check the app’s last successful update and errors. A manual change may be replaced at the next sync. Avoid changing a group used for unrelated access or announcements.
2. Confirm you mentioned a group, not a lookalike
Type @ in the message composer and select the intended user group from Slack’s picker. Check the handle carefully: @dev-oncall and@dev-on-call could refer to different groups. Open the mention to confirm the group and members rather than relying on its visual resemblance.
A bot named “Oncall,” a typed label and a user group are different objects. A scheduling app’s slash command may only return a private answer about the owner; that is not evidence that it contacted them. Agree on one handle for the team to use.
3. Separate a correct recipient from a visible alert
Ask the intended recipient to check Slack’s Activity view as well as the channel. Slack documents that a direct mention in a public channel can appear in Activity even before the person joins; a private-channel mention cannot reach someone who lacks access. For a controlled group test, use a channel both participants have joined. See how Slack mentions work.
Then inspect paused notifications, the notification schedule, channel preferences and device permissions. Slack’s pause setting suppresses notifications until they resume. A correct group member and a message visible in Slack do not establish that a phone sounded or a desktop banner appeared.
If the job requires waking somebody and escalating when they do not respond, use an incident paging process designed for that requirement. A rotating Slack mention is useful for routing team requests, but it is not proof of an emergency alert.
4. Test the boundary with two people
Use a dedicated test group and a channel both participants can access. The following is an illustrative test, not a claim about a customer incident. Alex is scheduled until 09:00; Sam takes over at 09:00 in the schedule’s timezone.
- Before the handoff: confirm the group contains Alex. Send a clearly labeled test mention and have Alex check Activity.
- After the handoff: wait for the scheduling system to confirm its update. Inspect Slack membership again; it should now contain Sam.
- Send a new mention: have Sam check Activity and Alex check whether they were addressed. Old messages are not a test of new membership.
- Record the result: note the schedule timezone, sync time, actual members, message time and each recipient’s observation. Record device alerts separately if you tested them.
Repeat with temporary cover. For example, Alex covers Sam from 10:00 until 10:30. Check membership after cover starts and after it ends. If a regular handoff falls inside that window, inspect who the underlying schedule says should resume; do not assume it is always the person who held the previous shift.
When maintaining the group becomes the problem
A manual group can work when changes are infrequent and someone owns each update. If daily handoffs and temporary cover are becoming a recurring chore, Ternly—the app we build—can update a dedicated Slack group from a rotation and finite coverage windows. It shows the last confirmed sync so you can verify the change.
Ternly requires a paid Slack workspace and permission to manage user groups. It supports one primary person per rotation, checks due changes about once a minute, and does not provide emergency paging or bypass Slack notification settings.