Pagerly is an on-call and incident management tool with Slack and Microsoft Teams as its interface, positioned as an "operations co-pilot running on Slack/Teams" that helps on-call engineers get relevant information and troubleshoot issues. Teams can complete scheduling, paging, incident response, and status page management without leaving their chat tool.
Uses
- On-call scheduling and rotations: Create and manage native rotations directly within Pagerly. Supports round-robin or custom schedules, with shifts by day, week, or custom intervals, and automatically assigns on-call responsibilities to team members. Supports overrides, swaps, and holiday handling.
- Schedule sync: Can sync schedules from Opsgenie and JSM, and Slack user groups (such as @oncall) are updated automatically.
- Reach the people who can actually fix the problem: Phone numbers can be added for paging, and on-call engineers receive phone calls, SMS, and emails. Supports connecting AWS, Datadog, or Sentry to automatically create incidents.
- Incident response: Start incident response within Slack, automatically generate Zoom links, Jira tickets, and dashboard links, assign roles and an Incident Commander, and generate timelines and handover reports.
- Status pages: Provide clear status pages for internal teams or external customers, showing status at the component and service level. Subscribers can follow along via email, RSS/Atom, or Webhook, all managed in Slack.
- Mobile and desktop alerts: Supports iPhone, Android, and the Mac menu bar. Alarms can break through "Do Not Disturb" mode, view the current shift at a glance, and acknowledge or resolve with one tap.
Key capabilities
- Paging and escalation: Phone, SMS, and email escalation.
- Automatic incident creation: From observability tools (such as Datadog, Grafana, GCP, HTTP webhook, etc.).
- Metric tracking: Track MTTA (mean time to acknowledge) and MTTR (mean time to resolve) per incident.
- Deep two-way integrations: Two-way sync with Jira, Jira Service Management, Opsgenie, Shortcut, and Google Calendar; supports AWS IAM access management, cloud cost report alerts, asynchronous standups, and other Slack workflows; and connects to others via HTTPTools.
- Third-party dependency monitoring: monitors 3000+ third-party SaaS and cloud services.
- Trust and compliance: officially stated to be ISO 27001 certified, offering SSO, scoped OAuth permissions, and data processing agreements.
How to use
- Use within Slack or Microsoft Teams: operations such as confirming pages, shift changes, opening incidents, updating the status page, and assigning incident commanders are all completed within Slack or Teams.
- Installation and migration: officially stated to take two minutes to install and can import existing on-call schedules. Existing schedules can be imported from Opsgenie and JSM, and Opsgenie customers can migrate with one click before its April 2027 shutdown.
- Paging infrastructure: paging runs on Pagerly's own infrastructure rather than Slack, so even if Slack has issues, phone calls, SMS, and emails will still be delivered (Slack itself is also one of the 3000+ services it monitors).
Use cases
- On-call scheduling, paging, and incident response for engineering teams.
- Organizations that want to centralize on-call and incident management within Slack/Teams.
- Teams that need a status page to communicate service status to customers or internal teams.
- Teams migrating from tools such as Opsgenie, Incident.io, Rootly, Splunk On-Call, Grafana OnCall, Better Stack, and Spike.sh (official comparison pages are provided).
Pricing Officially published pricing is: Starter at $39 per team per month, plus $4 per user per month for paging fees (per-call paging). The official comparison states that mainstream on-call and incident tools average about $35 per user per month. Teams can use the official savings calculator to estimate costs. Specific plans and tiers may change, subject to official publication.
Limitations and notes
- Some features (such as specific integration details and differences between plans) are not fully expanded in the official text, and more detailed information is not currently available.
- Information such as the product being ISO 27001 certified and used by 1000+ organizations comes from the official text.
- Features, platforms, prices, or effects not stated in the materials are not supplemented.
