PagerDuty
Tellspin can follow a PagerDuty on-call schedule you already use. PagerDuty remains the source of truth for the rotation. Tellspin reads who is currently on-call and keeps a Slack contact method (usually a user group such as @dev-on-call) pointed at that person.
This gives your team a non-incident way to reach the on-call engineer without opening PagerDuty.
How it works
- Tellspin re-syncs every minute, so handoffs and PagerDuty overrides show up in Slack almost immediately.
- The App Home lists the handle, current on-call user, Pagerduty sync schedule name, upcoming shifts, and a Syncs every minute note.
- You can combine several PagerDuty-linked schedules into one handle with Schedule Triage.
Requirements
- The PagerDuty schedule must be attached to an escalation policy. PagerDuty only reports who is on-call for schedules that are used by one.
- Tellspin needs read access to schedules, users, and escalation policies.
- Users are matched to Slack by email. Addresses that differ have to be mapped under Edit → Change User Mappings → Edit Users.
Reminders and overrides
Optionally add a reminder when you create the link so a channel is notified when a PagerDuty shift begins. Overrides made in PagerDuty flow into Tellspin on the next sync. Overrides made in Tellspin change who Slack reaches; they are not written back to PagerDuty.