Priority-Based Escalation Policies: Because Not All Notifications Burn the Same

Let's face it – not all notifications are created equal. That paper cut of a CSS bug probably doesn't need the same response as your production database doing its best impression of a black hole. Today, we're thrilled to announce Priority-Based Escalation Policies, a powerful new way to ensure your team's response matches the notification severity.

The Problem with One-Size-Fits-All

We've all been there. It's 3 AM, and you're jolted awake by a high-priority notification... only to discover it's that non-critical monitoring check that someone accidentally tagged as "CRITICAL." Or worse, a genuinely critical issue gets lost in the noise because it's following the same escalation path as everything else.

Your notifications have priorities for a reason. Shouldn't your escalation policies respect that?

Introducing Priority-Based Escalation Policies

Priority-Based Escalation Policies let you configure different notification paths based on notification priority. It's like having a smart traffic controller for your alerts, ensuring they take the right route to the right people at the right time.

Here's what you can do with the new feature:

🎯 Priority-Specific Targeting

• Configure different notification targets for High, Medium, and Low priority notifications

• Route notifications to the most appropriate teams and channels

• Keep your Slack channels focused with priority-based routing

⏰ Smart Timing Controls

• Set aggressive notification schedules for high-priority alerts

• Give breathing room for lower-priority notifications

• Configure priority-specific repeat intervals and hand-off timing

🔄 Intelligent Escalation Flows

• Define separate hand-off chains for each priority level

• Configure flexible response paths based on notification urgency

How It Works

Setting up Priority-Based Escalation Policies is straightforward. Under Policy Strategy, choose Dynamic, and you'll be able to configure unique notification settings for High, Medium, and Low priorities.

Each priority level can have its own timing, targets, and hand-off rules.

You can customize everything from initial notification delays to repeat intervals, and even set up automatic hand-offs to different teams – all based on the notification's priority level.

Available Today

Priority-Based Escalation Policies are available today for all FireHydrant customers. Head over to your Escalation Policies settings to start configuring priority-specific notification paths.

We can't wait to see how you use Priority-Based Escalation Policies to make your notification response more efficient. As always, we'd love to hear your feedback and suggestions.

Stay tuned for more updates, and keep those notifications under control! 🚒