Round Robin for Signals, ServiceNow Integration, Microsoft Teams Group Chat, Slack Enhancements

Hey there, Firefighters 🧑‍🚒 We've got some major updates for you this week!

🚨 Round Robin for Signals Escalation Policies

Balance your team's workload and reduce alert fatigue with our new Round Robin feature for Signals Escalation Policies. This feature is designed to make alert escalations smarter, fairer, and more team-friendly by allowing you to automate the sequential assignment of new alerts.

Choose between:

Distribute Evenly: Moves to the next target for each new alert and when the policy repeats – great for keeping things fair and balanced.

Distribute Consistently: With this option, alerts will always start with the first target but move on to the next target when the policy repeats.

We’ve also added the ability to add “additional targets” to your escalation policies — think Slack channels, external team members, webhooks, or even other escalation policies.

Read the blog to learn more.

🔄 ServiceNow Integration (Beta)

Our newest enterprise integration brings FireHydrant and ServiceNow together, creating a seamless bridge between engineering and the rest of your organization. Now your teams can work in their preferred platform while staying perfectly in sync.

• Create incidents bi-directionally between platforms
• Map custom and standard table fields for perfect data alignment
• Sync your CMDB with FireHydrant's Service Catalog
• Share Work Notes automatically across both platforms
• Convert Follow-Up tasks into ServiceNow problem tickets
• Keep critical incident details synchronized in real-time

Read the blog to learn more.

💬 Run Incidents From Microsoft Teams Group Chats

You can now auto-create Microsoft Teams group chats and seamlessly run your incidents within them – fully interacting with FireHydrant, just as you would from channels. Opposed to team channels that may limit who is involved in incidents, group chats allow anyone across the company to be involved in the discussion, making cross-functional collaboration easier than ever.

Read the blog to learn more.

📝 Reimagined Retrospectives (Beta)

We've completely rebuilt our Retrospectives experience to make post-incident learning more powerful, customizable, and collaborative than ever.

This new version brings:

• Custom templates – great for different teams, Incident types, or services
• Real-time collaborative editing
• A rich text editor that allows you to format and customize your answers
• Automated template attachment via a new Runbook step
• Ability to add multiple Retrospectives to Incidents
• AI-powered answer generation
• Polished export of your retros to Google Docs, Confluence, and PDF

Read the blog to learn more.

🔍 New /fh catalog Command in Slack

Search, view, and manage your catalog items directly from Slack! This new command brings the power of your FireHydrant Service Catalog right to your fingertips:

• Search Service Catalog items with real-time filtering
• View detailed item information including descriptions, ownership, and change events
• Add or remove items as incident impacts without leaving Slack
• See recent Incidents involving specific Service Catalog items
• Access ownership information and external links
• Quick links to view items in FireHydrant

⚠️ Enhanced Schedule Management

We've improved the on-call rotation schedule experience with better warnings and controls when making changes, ensuring you know exactly what is changing and when.

• Clear warnings when modifying shift rotations
• Choose when the changes will take effect – Next Handoff, Now, or Custom timing
• Side-by-side comparison of current vs new rotations
• Displays timing information for each shift

⏰ High Priority Notifications Warning

To help prevent missed critical alerts, we've added a warning that lets you know when you haven't configured immediate notifications for high-priority alerts. This ensures you're making informed decisions about your notification setup and have no delays in your response to critical issues.

🐛 Bug Fixes

• We fixed an issue with the /fh update command in Slack which sometimes made it difficult to fill out missing required fields when moving to a new milestone
• Fixed a bug in the /fh page that was preventing users from paging a service when no specific user or team was defined