📆 🎉 On-Call Scheduling, Alert Lifecycle & Routing are now Available inside Slack

Hi there! I’m happy to announce a new major update of our In-Slack Incident Management App Amixr.IO. It’s already live for all users and available in all subscription plans 🎉

Alert Lifecycle

Now you could configure exact steps you want your Incidents to follow.

Menu->Workspace Settings->Integrations -> Edit Alert Lifecycle

Alert Lifecycle in Amixr interface.

Alert Routing

Menu->Workspace Settings->Integrations -> Edit Alert Lifecycle

You could configure routing based on alert content. For example, any alert containing “MySQL” will go to #dba team.

Alert routing based on alert content.

On-Call Scheduling

Menu->Workspace Settings->Integrations -> Edit Alert Lifecycle -> Choose “notify” and channel name.

On-Call scheduling is a practical feature for our clients because it helps to distribute duty based on time to lower distraction and bring order in incident management. Since our goal is to bring first grade UI inside Slack, we’ve performed dozens of customer interviews to define the best UI to configure Schedule inside Slack. The huge screenshot you see in the left is a 3'rd variant of scheduling UI tested and verified internally. It works incredibly for teams distributed around the globe, teams consisting of 2 or even ten on-call engineers.

To invoke the On-Call Scheduling menu, go to “Edit Alert Lifecycle” menu, choose “notify” step and select channel which will be a central place for incident-triggered discussions inside your team.

Waiting for your feedback!

We work hard to build the best incident management experience inside Slack. Please help us! Share your feedback, ask questions and suggest more features: matvey@amixr.io

Never used Amixr before? Try now!

Stay tuned!

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store