๐Ÿ”ฅ
Developer Documentation
  • ๐Ÿ‘‹Welcome to Pagerly
  • How To Work With Pagerly
    • Get Started
    • ๐Ÿค‘Create Round Robin Rotations
      • ๐Ÿ“–How To Add Rotation in Pagerly
    • ๐Ÿ› ๏ธSetup Team
      • ๐Ÿ“–Retrieving Schedule Id for PagerDuty
      • ๐Ÿ“–Schedule for JSM Operations
      • ๐Ÿ“–Retrieving Schedule Id for OpsGenie
      • ๐ŸคFind Sheet Id from Google Sheets
      • ๐ŸคRetrieve Calendar Id from Google Calendar
    • ๐Ÿค‘Round-Robin Rotations for Tasks / Picking
      • ๐Ÿ“–How To Add Rotation for Picking Tasks in Pagerly
    • ๐Ÿค‘Round Robin Oncall without Schedule
      • ๐Ÿ“–How To Add Round Robin Rotation for Oncall without Schedule in Pagerly
    • ๐Ÿ˜ŽPlaying with Pagerly
      • ๐Ÿ‘€Mention Current Oncall on any Slack Conversation
      • ๐Ÿ•–Fetch your team's oncall schedule
      • ๐ŸŒ€Overriding Team's Schedule
      • ๐Ÿ—ฃ๏ธLet everyone know who is the Current Oncall of your Team
    • โฐReminders for Upcoming Rotation
    • Pagerduty Sync Slack and Workflows
    • ๐Ÿ”‘Setup Team Access
    • ๐Ÿ› ๏ธIntegrating with Your Paging Tool
      • ๐Ÿ“Retrieving PagerDuty API Key
      • ๐Ÿ“Connect JSM Operations
      • ๐Ÿ“Retrieving OpsGenie API Key
    • Escalations
    • ๐Ÿ—’๏ธIntegration with Jira
      • ๐ŸคAdd Your JIRA Account
      • ๐ŸžCreate a Ticket via Emoji and Follow on Slack Channel
      • ๐ŸงตPost Ticket created on Jira to Slack Thread
      • ๐Ÿš๏ธPost Ticket created on Jira to on Slack Channel
      • ๐Ÿ‘€Create Ticket via Slack Emoji and Follow on Slack Thread
      • ๐Ÿ“œCreate Jira Ticket/Incident using Form
      • ๐Ÿ”„Round Robin Assignment of Jira Issues/Tickets
    • ๐Ÿ“ŸSet Slack Status Automatically
    • ๐Ÿ“†Sync Schedule with Google Calendar
    • Creating Ticket via Emojis
    • ๐Ÿ”„Rotate & Assign Requests
    • ๐Ÿ”„Round Robin Assignment of Jira Issues/Tickets
    • ๐Ÿ”„Round Robin Assignment of Alerts/Incidents (Opsgenie/JSM Ops)
    • Instant Status Pages
    • ๐ŸคMention/Group Multiple Oncals
      • Configure MultiMention Team
    • ๐Ÿ› ๏ธLinear Integration
      • Connect Linear Account
      • Connect Pagerly Team and Linear Team
    • Create Swap on Oncall / Rotations
    • ๐Ÿ”„Custom Change Notification on Slack
    • ๐Ÿ“†Google Calendar with Slack
      • ๐ŸคRetrieve Calendar Id from Google Calendar
    • ๐Ÿ‘จGoogle Groups To Slack Usergroups
      • ๐ŸคFind Sheet Id from Google Sheets
    • Google Sheets with Slack
      • ๐ŸคFind Sheet Id from Google Sheets
    • ๐Ÿ“’Manage Tasks within Slack
    • Microsoft Team Setup
    • Discord App
    • ๐Ÿ‘ฉโ€โš•๏ธHelp and Support
    • ๐Ÿ Self Hosted
    • ๐Ÿ“ŠDaily Oncall Standup
    • ๐Ÿ’ฐCloud Cost App
      • ๐Ÿ› ๏ธSetup IAM Role for Temporary Access
      • ๐Ÿ› ๏ธConfiguring Team for Cloud Cost
  • ๐Ÿ‘จโ€๐Ÿš’Incidence Response
    • ๐ŸงฏPagerly Incidence Response
    • ๐Ÿ“–Overview
      • ๐ŸŽฅVideo Demo
    • ๐Ÿ˜Customization & Workflow
    • โš’๏ธIntegrations
    • ๐Ÿ Self Hosted
    • ๐Ÿ‘ฉโ€๐Ÿ’ผContact Us
Powered by GitBook
On this page

Was this helpful?

  1. How To Work With Pagerly

Mention/Group Multiple Oncals

PreviousInstant Status PagesNextConfigure MultiMention Team

Last updated 1 year ago

Was this helpful?

With Pagerly, you can configure MultiMention Teams, with which you can mention multiple oncalls together

In today's complex and interconnected systems, incidents can arise from various parts of your organization. Pagerly's "Mention Multiple On-Calls" feature equips you with the ability to notify all relevant on-call teams simultaneously, ensuring that the right experts are informed promptly,

Here are some of the use cases of Multi Mention Team

  • Cross-Functional

Some incidents require the expertise of multiple teams to be resolved effectively. With this feature, you can bring together developers, operations, and support teams in one go, enabling faster and more coordinated incident resolution.

Ex : Use @frontend-oncall mentions @andriod-oncall, @ios-oncall, @web-oncall

  • Scheduled Maintenance or Upgrades

Scheduled Maintenance or Upgrades: Even planned activities can encounter unexpected challenges. By mentioning all relevant on-call teams, you can ensure a rapid response in case any issues arise during maintenance or upgrades.

  • Geographically Distributed Teams

If your organization has teams spread across different time zones, mentioning multiple on-calls ensures that incidents get immediate attention, regardless of the hour.

  • Escalation Pathways

For critical incidents that need immediate attention, you can set up escalation pathways. If the initial on-call team doesn't respond within a specified time, the system can automatically notify additional teams, ensuring that incidents are addressed promptly.

  • Product Launches

Product Launches or Updates: During product launches or updates, multiple teams are involved in ensuring a smooth release. Coordinating these efforts is vital, and this feature enables you to keep everyone on the same page.

๐Ÿค