We’ve just launched Round Robin Alerting—a smarter way to distribute incidents fairly when multiple people are on-call at the same time.

How It Works

Round Robin ensures that no single person is overwhelmed by consecutive incidents. Instead of notifying all on-call users at once, incidents are assigned in a rotating order. This keeps the load balanced while ensuring everyone stays informed.

🔹 Rotations vs. Round Robin?

• Rotations cycle who is on-call week over week.

• Round Robin cycles who gets assigned when multiple people are on-call at the same time.

How to Enable Round Robin

You can activate Round Robin for each schedule separately:

1️⃣ Click the “No Round Robin” button in your schedule settings.

2️⃣ Enable Round Robin and define the number of users per incident.

3️⃣ Save your settings—incidents will now be evenly distributed.

Example in Action

Let’s say Peer, Sandra, and Nick are on-call at the same time, and Round Robin is set to 2 users per incident. Here’s how it plays out:

Incident | Notified On-Call Members

Incident 1 Peer, Sandra

Incident 2 Peer, Nick

Incident 3 Sandra, Nick

Incident 4 Peer, Sandra

This ensures that:

✅ No one is overloaded with back-to-back incidents.

✅ Every on-call member stays engaged without unnecessary noise.

Ready to try it out? Head over to your schedule settings and enable Round Robin Alerting today! 🚀

“Why isn’t this incident getting resolved?”

“How do I make sure the right person sees this - without spamming everyone?”

“What if someone specific needs to be involved, even if they’re not on-call?”

We’ve all faced incidents where a specific person needs to step in - whether to take ownership or provide critical input. But until now, incident assignment has been rigid, often relying only on on-call schedules.

That’s why we built precise incident assignments in All Quiet.

With our new Assign to User feature, you can:

✅ Directly assign an incident to the right person - even if they’re not on-call.

✅ Include key individuals in the resolution process, ensuring no critical knowledge is missed.

✅ Prevent unnecessary escalations by making ownership crystal clear.

No more chasing people down or hoping the right team picks it up. Just faster resolution with the right people involved.

Try it now and keep your incident response focused and efficient. 🚀

Here's how it works: https://docs.allquiet.app/essentials/incident#/essentials/incident#assign-to-user

Are you experiencing a cascade of connected alerts for certain incidents that occur in your system? Our incident grouping feature helps cut through the noise, keeping your team focused on resolving the issue.

Easily consolidate multiple related incidents into a single event by matching key attributes, streamlining collaboration and speeding up resolution.

To enable this functionality, you must first configure grouping in the payload mapping section of your integration, using isGroupingKey attribute key.

Once set up, incidents with matching values for the defined attributes will be grouped.

The screenshot above shows an example for the incident details view of an incident group:

1. You can view the overall state of the entire incident group. The group remains open until all incidents within it are resolved or until it is manually resolved.

2. Grouping is determined by the criteria set using isGroupingKey in the incident mapping of the integration. As long as the incident group remains open, any new incidents matching the defined criteria (e.g., attribute UTM = 333) will be added to the group.

3. You can see all single incidents that are part of the group with their status & attributes.

4. The history of the incident group. The first incident with a grouping attribute creates the groupt and starts auto-escalations. All collaboration takes part on group level, no seperate alerting for new incidents - this reduces the noise and keeps the focus on resolution. After the group is resolved, the next matching incident will create a new incident group. Exception: When using groupingWindowInSeconds , new incidents that come in during the window will reopen a previously resolved group.

Here's how to set this up via the isGroupingKey in your integration: https://docs.allquiet.app/essentials/inbound#optional%2C-additional-attribute-keys

1. You can now set time restrictions for the snooze window, allowing you to snooze only during specific periods, such as working hours, to maintain focus.

2. Introducing “Absolute” snooze mode, enabling you to snooze incidents not just for a set duration but until a specific point in time.

Here's how it works: https://docs.allquiet.app/essentials/inbound#receiving-payloads

Is your integration sometimes flaky and trigger incidents that auto-resolve just minutes later? Reduce noise and minimize stress for your on-call colleagues by activating the new "Snooze" feature.

With Snooze activated..

• newly created incidents will only alert on-call members once the snooze window ends.

• auto-escalations are on-hold

• incidents that resolve during the snooze window remains snoozed and do not alert your team

Once unsnoozed, Tier 1 on-call members are alerted and any potential auto-escalations begin.

Now, you can reduce even more noise with us and keep you on-call colleagues calm!

Learn how to set this up: https://docs.allquiet.app/essentials/inbound#receiving-payloads

In the past, you've already been able to create All Quiet incidents by creating Linear issues matching certain criteria.

Now, you can also create All Quiet incidents by updating existing Linear issues.

This is great if you want to e.g. create an incident after checking an existing Linear issue in Triage. You can simply add a label like "Incident" to your Linear. If it matches the criteria, we'll create an All Quiet incident and inform your on-call team about it.

Of course, incidents created by updating Linear issues also support the synchronization of All Quiet and Linear states.

More on this: https://docs.allquiet.app/integrations/outbound/linear#create-all-quiet-incidents-from-linear

We've all been there. You acknowledge an incident, something even more important comes in.. aaaaaand you lost track of it and forget about it as there are no further reminders.

That's why we've added more functionality to our escalations. You can now auto-escalate, auto-assign or auto-repeat you escalation even if an incident has been acknowledged, but not resolved. With this seeting, you will still get alerted, even if your team has reacted to the incident, making sure it's not getting lost.

We got you covered!

Learn more: https://docs.allquiet.app/essentials/escalations#escalation-tiers

Our schedules just got even more flexible!

Now, you can include several on-call times in one schedule. This is great to create e.g. weekend schedules.

In the example above, we've created a schedule that is active from Friday 5 p.m. until Monday 8 a.m.

Of course, it is still possible to set up your schedules as simple as before - we've simply added more flexibility!

Here's how you set it up: https://docs.allquiet.app/essentials/escalations#schedules

We're consistently adding functionality to our Escalations

1. We've added a time filter for auto-escalations. E.g. you can now filter escalations to only happen during the weekend from Friday 5 p.m. to Monday 8.am. (s. screenshot above

2. ℹ️ Applicable for Pro and Enterprise customers with organizations: We've added the auto-assign feature to the escalations. You can now autmatically add other teams to your escalations. Just like auto-escalations, auto-assign can be filtered for severity, weekdays & times.

In your organization, we've added a tab called "Users".
This tab shows all your users with their current team & organization roles.

Also, Organization Owners can delete users via this view.
This removes users from the organization and all it's teams, and, if it's their only organization, deletes them completely from All Quiet.

Users provisioned via Terraform or SCIM cannot be deleted via this view, nor can you delete yourself or the current Billable User of the organization.

ℹ️ Applicable for Pro and Enterprise customers with organizations

More: https://docs.allquiet.app/advanced/organizations#users

If you're using SCIM provisioning, you can now provision organization roles for your SCIM user groups.

• Auto-Provisioning: Add a default organization role for all provisioned users (see above)

• Manual Provsioning: For each provisioned user group, you can add a default organization role

Learn more: https://docs.allquiet.app/miscellaneous/sso#step-by-step-guide-2

These users have implicit member rights in all teams and, therefore, can also interact with incidents that are currently in other teams than their own - a great additional role for users that shouldn't have any admin rights, but should be able to help other teams with their incidents if necessary.

ℹ️ Applicable for Pro and Enterprise customers with organizations

Learn more: https://docs.allquiet.app/advanced/organizations#key-features-of-organizations

Want to add or modify incident attributes based on specific conditions?

With our latest update in the Routing & Workflows section, you can now do exactly that.

For example, you can link different runbooks based on the incident title and integration (see the example above).

Incident attributes can also be adjusted in the payload mapping section of most inbound integrations.

Learn more about Routing Actions: https://docs.allquiet.app/advanced/routing#configure-actions

Want to map runbooks or other incident attributes via the integrations' payload mapping section? This blog article can help: https://allquiet.app/blog/map-incidents-to-runbooks

We've added further improvements to the Team Escalations.
______________________________________________________________________________________

Want to re-alert your Tier 1 users before auto-escalation to Tier 2?

Here's how it works:
https://docs.allquiet.app/essentials/escalations#repeat-escalation-tier

______________________________________________________________________________________

Don't want to auto-escalate Minor incidents? You can now filter escalations by severity.

Here's how it works:

https://docs.allquiet.app/essentials/escalations#automatic-escalation

Available for Pro and Enterpris Plan

You can now connect one outbound integration with multiple teams. This feature brings several advantages.

1. It saves time during the setup

2. It simplifies keeping track of your current integrations when you're working across several teams.

3. It allows your to interact with incidents across mutiple teams, all from your favourite outbound integration channels.

Want to try it out? Manage your outbound integrations' teams via the integrations' detail pages.

With Auto Rotations, your team’s on-call duties rotate automatically, eliminating the need for manual setup.

In the example above, a team of five members rotates on-call duty weekly in pairs:

• Week 1: Nick (1), Mads (2)

• Week 2: Svenja (3), Til (4)

• Week 3: Sandra (5), Nick (1)

• Week 4: Mads (2), Svenja (3)

• Week 5: Til (4), Sandra (5)

• …and so on.

New schedule members are automatically added to the rotation, and the system adjusts seamlessly when someone leaves.

Here's how you set it up:
https://docs.allquiet.app/essentials/escalations#rotations

• Allow more complex Rotation handling

Need to involve colleagues from other teams to resolve an incident? Or want to reassign it to a totally different team?

The “Assign to Team” feature, available on Pro and Enterprise plans, makes it easy to reassign incidents to the appropriate teams. It enables you to escalate incidents across various teams within your organization.

You can use it to

1. create automated routing rules for smooth auto-escalations across several teams

2. manually reassign incidents to other teams when additional support is needed

Here's how it works: https://docs.allquiet.app/essentials/incident#assign-to-team

We’re excited to announce that All Quiet now integrates with Microsoft Teams, making it easier than ever to keep your team connected and informed.

What Does This Mean for Your Team?

With this integration, you can now receive real-time alerts and updates from All Quiet directly in your Microsoft Teams workspace. Whether it’s an a critical alert or a status update, your team will get the information they need where they’re already collaborating - without switching between tools.

Why This Matters

This integration helps streamline workflows by reducing the friction of jumping between platforms. It ensures your team stays aligned and on top of updates, all within the same tool you use for daily communication. No more missed alerts or delays in acting on critical information.

Setting it up is straightforward. Visit the integrations page on All Quiet to link Microsoft Teams to your account and start routing notifications to the appropriate channels.

We’re focused on building tools that work where you do - and this is just another step in making sure All Quiet fits seamlessly into your team’s day-to-day.

Check it out and let us know what you think!

https://docs.allquiet.app/integrations/common/microsoft-teams

We've extended the functionality of our Linear and Jira integrations.
Now, you can also use them as an inbound integration and create All Quiet incidents by creating issues in you Jira & Linear board.

To use the new extension, simply go to you Jira or Linear outbound integration page and configure your inbound integration on the same page:

Jira: https://docs.allquiet.app/integrations/inbound/jira
Linear: https://docs.allquiet.app/integrations/inbound/linear

We just release our integration for Elastic Observability.
Now, you can create All Quiet incidents from alerts in your Elastic Observability Project.

Here's how you setup the integration in 5min, making sure recovering in Elastic also resolves the issue in All Quiet: https://docs.allquiet.app/integrations/inbound/elastic-observability

We just released the leanest Status pages on the market. Update your customers in real-time, whether it's to show your uptime, or if something is going wrong. Share incident updates with a view clicks, from the same place you're tackling incident from.

Lose no time - use our Status Pages for the most efficient incident communication.

More: https://allquiet.app/status-pages

🤔 Sometimes, you know there's something wrong but your observability tools are silent. For these cases, we added the option to manually create incidents in All Quiet.

Simply open the Incident Overview and create a new incident if necessary.

Manually created incidents have the same functionalities as automatically created incidents. Creating an incident will alert your on-call team members and you can perform all types of actions, like pre-defining workflows and routing rules for manually created incidents.

More: https://docs.allquiet.app/essentials/incident#manually-create-an-incident

If you want to clean up your incidents overview, you can now archive incidents. Archiving incidents does not change their resolution state, only moves them from the incidents overview to the archive.

1. Archive Intent

2. You can open the archive from your incidents overview

Archived incidents can always be Unarchived. Then, they will be visible on the incidents overview, again.

More: https://docs.allquiet.app/essentials/incident#archiving-incidents

More improvements & fixes

• Archive Incidents

Notion is one of today`s most celebrated software tools. And for good reason. It's usability and depth make it THE all-in-one productivity solution.

With our latest integration, you can now connect Notion with our all-in-one incident management app.

The integration focuses on the post-incident phase and eases the preparation of post-mortems, retrospectives, or simply the documentation of incidents. It allows you to forward All Quiet incidents to Notion in a matter of seconds. We automatically create a page in your Notion workspace and pre-fill it with all of the incident's details & history.

Save time and get more efficient with our lates integration. We prepare all the information, so you can focus on understanding the incident's cause and prevent it from ever happening again.

Here is how you set it up in 2 minutes:
https://docs.allquiet.app/integrations/outbound/notion

Available for Organizations with Pro and Enterprise plans.

With this new report, you can get an overview of the on-call times of all of your organization's users.

You can find it in the Web App, via Organizations > On-Call Report.
The screenshot above features an example:

1. Select your preferred interval

2. Find the on-call times for each user

3. Export the report, e.g. for payroll purposes

Here's more on how on-call reports work: https://docs.allquiet.app/advanced/report#on-call-report

We started as an on-call platform, but are continously trying to help you improving your whole incident response cycle.

That's why we added an outbound integration with Atlassian's Confluence. Simply forward All Quiet incidents to Confluence and create documentations pre-filled with all the incidents' details. With our integration, Confluence documentation for incidents is a matter of seconds. We prepare, everything, so your team can focus on error analysis and prevention.

Here's how it works:

https://docs.allquiet.app/integrations/outbound/confluence

Jira is the O.G. of product development software and by far the most used tool of this kind.

Our latest integration lets you automatically generate Jira issues directly from All Quiet incidents, with all relevant details pre-filled. For improved incident management, we’ve introduced a sync feature that keeps the status of your Jira issue aligned with the associated All Quiet incident.

If you prefer to forward only select incidents to Jira, our Forwarding Feature is just for you. It allows you to send specific incidents to your preferred outbound integrations rather than forwarding everything.

Set up your Linear Jira within 5 minutes:

https://docs.allquiet.app/integrations/outbound/jira

As we love using Linear as much as many of you, we wanted to make sure to build an integration.
From now on, you can automatically create Linear issues from All Quiet incidents, pre-filled with incident details. For smarter incident management, we added a sychronization feature to match the state of your Linear issue and the related All Quiet incident.

Moreover, if you don't want send all but only specific incidents to Linear, you can make use of our new Forwarding Feature. This feature allows you to forward specific incidents to your favourite outbound integrations, instead of sending all incidents.

Set up your Linear Integration within 5 minutes: https://docs.allquiet.app/integrations/outbound/linear

Integration

• Linear Integration

SigNoz is a new open source alternative to DataDog and New Relic. From now on, you can send your SigNoz alerts to All Quiet and benefit from our on-call management and incident response features.

Set up your SigNoz integration within 2 minutes: https://docs.allquiet.app/integrations/inbound/sigNoz

We've added a website / HTTP Monitor to All Quiet, allowing you to easily check the availability and response times of their your websites. This feature helps ensure your site is up and running smoothly, giving you real-time feedback on any potential issues. If anything is wrong, we'll create an incident and immediately inform your on-call colleagues.

Last but definitely not least: Unlimited HTTP Monitors are included for users of pricing plans, without any extra charge.

Set up your monitor in 2 minutes:
https://docs.allquiet.app/integrations/inbound/website-http-monitoring

We added another inbound integration. Connect Netdata and All Quiet via webhook and create All Quiet incidents based on Netdata alerting.

Follow our integration guide to set up the integration within ~2 minutes:
https://docs.allquiet.app/integrations/inbound/netdata

We just added new inbound integrations for Checkly and Pingdom, allowing you to connect their monitoring with our end-to-end incident management.

Checkly Setup Integration: https://docs.allquiet.app/integrations/inbound/checkly
Pingdom Setup Integration: https://docs.allquiet.app/integrations/inbound/pingdom

• Checkly Integration

• pingdom integration

We are happy to announce our new AppSignal Inbound Integration. Create All Quiet incidents with AppSignal alerts and errors. Notifiy All Quiet via Webhook for any types of detected anomalies or downtimes.

Integration takes ~2minutes: https://docs.allquiet.app/integrations/inbound/appsignal

We're excited to introduce a new 3-click importer to seamlessly bring your PagerDuty setup into our platform! Here's how it works:

1. API Key: Enter your PagerDuty API key to securely connect your account.

2. Review Loaded Data: After loading the data, we will show you a preview of how the data will be imported to your All Quiet account. As our feature setup differs from PagerDuty, there will be differences. Review and confirm the data loaded from your PagerDuty setup. No worries, you can also stop and discard the import.

3. Sign Up / Log In: Complete the process by signing up for a new account or logging into your existing account and improving the import

Please note, this importer is designed for manual setups and should not be used by Terraform users, as the data imported will not be added to your Terraform configuration.

Import your PagerDuty setup, now: https://allquiet.app/pagerduty-importer

We just added our new integration for Site24x7, allowing you to create incidents in All Quiet using alerts from your Site24x7 Monitors.

Here's how you set up the integration in ~2 minutes:

https://docs.allquiet.app/integrations/inbound/site24x7

Use our new Inbound integration to connect our incident management platform with Rollbar's real-time error tracking.

Here's how you set up the integration in ~2 minutes:
https://docs.allquiet.app/integrations/inbound/rollbar

This integration allows you to forward Cisco AppDynamics alerts to All Quiet by setting up custom HTTP Requests.

Set up your integration within minutes: https://docs.allquiet.app/integrations/inbound/appdynamics

We're thrilled to announce that All Quiet now supports Dynatrace! This integration allows you to use Dynatrace alerts and notifications for performance issues and anomalies to create custom All Quiet incidents.

Here's how to set up the integration:
https://docs.allquiet.app/integrations/inbound/dynatrace

We're excited to announce All Quiet now supports Zapier! Zapier allows you to connect our platform with over 3,000 apps, automating your workflows and saving you valuable time. This means you can utilize integrations with apps that we don't directly support yet, making them usable with our platform via Zapier.

To allow you to make the most of it, we created an Inbound and an Outbound Integration.

• Outbound Triggers

  • Use the "New Incident Intent" to send All Quiet Incidents to other Zapier Integrations. You can, for example, use the Linear Integration to automatically create a new ticket in Linear once an All Quiet incident pops up. Also you can send All Quiet incidents to communication tools we don't directly support yet, like WhatsApp or Telegram.

• Inbound Actions

  • Use the "Create Incident" Action to automatically create an Incident in All Quiet based on one of your other Zapier Integrations. One of the many use cases for this is to connect observability and monitoring tools we don't support directly yet. Find the list of all our integrations attached: https://docs.allquiet.app/integrations/overview

  • Use the "Create Incident Intent" Action to automatically update the Status of All Quiet Incidents triggered by an event in other Zapier Integrations.

We are excited to announce the release of our new Terraform provider! This integration allows you to manage and automate your All Quiet resources using Terraform, the leading Infrastructure as Code (IaC) tool.

Note: Our Terraform Provider is available for Pro and Enterprise plans only.

Why This is Great

1. Simplified Resource Management:

• Use Terraform to manage your All Quiet resources declaratively. Define your infrastructure as code, and let Terraform handle the creation, update, and deletion of your All Quiet resources. This

2. Version Control:

• Keep your infrastructure changes in version control, just like your application code. This allows for easy tracking, auditing, and rollback of changes.

3. Automation and Consistency:

• Automate the provisioning and management of your resources. Ensure consistent and repeatable infrastructure deployments across multiple environments.

4. Enhanced Team Management:

• Efficient On- and Offboarding: Automatically manage team members joining or leaving your organization. Ensure all necessary permissions are granted or revoked seamlessly.

• On-Call Schedule Management: Maintain up-to-date and accurate on-call schedules. Prevent gaps in coverage by programmatically updating schedules when team changes occur.

5. Integration with Existing Workflows:

• Seamlessly integrate with your existing Terraform workflows and toolchains. Use familiar Terraform commands to manage your All Quiet resources alongside other infrastructure components.

6. Improved Efficiency:

• Reduce the manual effort required to manage your resources. Write your infrastructure configurations once and reuse them across different projects and teams.

Getting Started

Get started with our documentation: https://docs.allquiet.app/advanced/terraform

Find our latest Terraform Provider, here: https://registry.terraform.io/providers/AllQuietApp/allquiet/latest

UPDATE: Dark Mode is now also available on our mobile apps for iOS and Android.

We are thrilled to announce that All Quiet now supports Dark Mode! Developers, your requests have been heard, and we are excited to bring you a more comfortable experience.

What's New:

• Dark Mode: Switch to Dark Mode for a sleek, eye-friendly interface.

• Light Mode: Prefer a brighter workspace? Light Mode is still available to keep your interface crisp and clean.

• System Settings: Let your system settings decide! All Quiet can now follow your device's theme preference automatically.

Come to the Dark Side and experience All Quiet's full power!

We've added a new outbound integration for Google Chat.

Simplify incident management by consolidating all notifications and actions in your team's Google Chat.

The integration's set up only takes ~2 minutes: https://docs.allquiet.app/integrations/outbound/google-chat

We've added a new inbound integration for honeycomb.io, one of the best known observability tools in tech.

It enables you to connect your Honeycomb triggers with our on-call incident management. Set up your integration and use your honeycomb set-up to send to create an incident at All Quiet.

Integration Guide: https://docs.allquiet.app/integrations/inbound/honeycomb

We're excited to announce the introduction of two new plans alongside our existing STANDARD plan priced at $4.99 per user/month, including to a wider range of product features.

As before, the STANDARD plan includes SSO Login and unlimited

• Users

• Incidents

• Inbound and Outbound Integrations

• Free SMS / Phone Calls / Emails / Push Notifications

• On-call schedules

• Overrides

• Maintenance Windows

PRO plan

Priced at $9.99 per user/month, the PRO plan encompasses all features of the STANDARD plan, with the addition of advanced functionalities such as Organizations and routing to teams. These enhancements empower larger enterprises with multiple tech units to seamlessly manage and coordinate teams, optimizing resource allocation. Furthermore, the PRO Plan offers exclusive whiteglove onboarding support from our founders, ensuring a smooth setup and initial steps into our platform

ENTERPRISE plan

Our ENTERPRISE plan is a customizable solution tailored for large enterprises. It incorporates all features from the PRO plan and extends further with OIDC and SCIM authentication, simplifying the management of large teams and organizations for administrators. Additionally, we are more than happy to offer bespoke customization options for the ENTERPRISE plan. For inquiries and personalized solutions, don't hesitate to contact our Founder, Mads Quist, at [email protected].

To change your current plan, simply open the Billing & Subscription section and select "Manage Subscription". This feature is only accessible for Billable Users of Teams and Organizations.

We're committed to providing scalable solutions to meet the diverse needs of our users. Explore our new plans today and take your organizational efficiency to the next level with All Quiet.

We heard you and we are excited to announce a new feature that makes planning overnight shifts much easier than before. Now, when setting up your team's on-call schedule, you can set the end time smaller than or equal to the start time. As you can see from the screenshot above, our system will automatically recognize it as an overnight shift. This enhancement simplifies the scheduling process, ensuring seamless shift management for your development team. Say goodbye to two schedules for one night shift and hello to efficient overnight planning!

What's New:

• Overnight Shifts: Create shifts that span across two days by setting the end time to be smaller than or equal to the start time.

We hope this new feature enhances your experience and improves your team's productivity. As always, we appreciate your feedback and are here to help with any questions you may have.

What's New:

• New Logo: A fresh, modern logo to represent our brand.

• Updated Style on our website: Refined color palette, typography, and design elements.

• New App Icons: We updated the icon for our iOS and AND Apps so it matches our new logo, too.

Check-out allquiet.app to see our new look!

We've added a new inbound integration for Sentry, one of the world's most used and best known monitoring services in tech.

It enables you to connect your Sentry monitoring with our on-call incident management. Set up your integration and define which Sentries should trigger an All Quiet notification. Our on-call schedule will make sure it reaches the right person within your team.

Integration Guide: https://docs.allquiet.app/integrations/inbound/sentry

We're pleased to announce the release of a new, highly beneficial feature in All Quiet: Notification of Failed Integration Mappings.

Why is this important?

Sometimes, even well-set integration mappings encounter issues when they receive payloads that do not match expected formats or values. For example, a payload might include a severity field with a value that All Quiet doesn't recognize, since we only support "Minor," "Warning," and "Critical" as severity levels.

What's new?

With this update, whenever an integration mapping fails due to such discrepancies, all administrators of the affected integration will receive an email notification. This is crucial because:

• Prevent Missed Alerts: Ensures that critical alerts aren't missed due to invalid mappings.

• Quick Resolution: Allows admins to quickly address and rectify the issue, ensuring that all systems continue to operate smoothly.

We believe this feature will significantly enhance the reliability of your incident management workflows by reducing the chances of missed or ignored alerts due to mapping errors.

We're excited to announce the launch of a new feature in All Quiet: Organizations.

Introducing Organizations

Organizations enable a powerful new way to manage multiple teams under one umbrella, enhancing collaboration and streamlining management processes. This feature is especially beneficial for larger enterprises or groups managing numerous teams.

Key Capabilities of Organizations:

• Role-Based Access Control: Designate users as "Owners" who can edit the organization and manage membership, or "Administrators" who are automatically granted admin rights for all teams within the organization.

• Flexible Member Invitation: Easily invite new members to your organization, choosing from new users or those you are already connected with on the platform.

• Dynamic Incident Routing: Assign and reassign incidents more efficiently across different teams within your organization.

Why Use Organizations?

Organizations are not mandatory but offer advanced capabilities for users who need them. They are ideal if you're looking to:

• Centralize management across multiple teams.

• Enhance administrative coordination.

• Streamline responses and handling of incidents.

For detailed guidance on setting up and managing Organizations, check out our updated documentation: https://docs.allquiet.app/advanced/organizations

We've launched two major updates to All Quiet: a complete revamp of our documentation and the introduction of advanced incident routing.

Revamped Docs
We've completely revamped our documentation, making it more visually appealing and easier to navigate. Powered by Mintlify, our new documentation platform is not only more engaging but also features powerful search capabilities with CMD+K. We focused on refining the language to ensure clarity and accessibility for all users, aiming to make information retrieval as seamless as possible.
Check out our docs here: https://docs.allquiet.app/introduction

Advanced Incident Routing
Our new incident routing feature allows for customized handling of alerts based on specific conditions (status, severity, integration, intent & attributes) that can trigger custom actions (change severity, add interaction, discard, etc) and/or define custom channels when conditions are met. This means tech teams get more granular controls on how their incident workflow should look like.

Popular Use Cases:

• Mute Channels for TEST Environments: Reduce unnecessary noise by muting alerts from development/testing environments.

• Trigger Outbound Webhooks for Escalated Incidents: Automate workflows by triggering outbound webhooks specifically for incidents that require escalation.

Learn how you can use Incident Routing for your use case on our new Docs: https://docs.allquiet.app/advanced/routing

Other Improvements:

• UI Improvements for Incident List: Navigate your incidents with an improved user interface designed for quicker access and better clarity.

• Slack Integration Enhancements: Customize which Slack channels receive alerts from different integrations, streamlining communication and response efforts.

We've launched a new Incident page. This page not only presents incidents in a filterable and sortable list for quick access but also allows for bulk actions. Now, you can mark multiple incidents as resolved, investigated, or escalated with ease, ensuring your team remains focused and efficient.

Advanced Sorting and Filtering: Sort incidents by Urgency, Latest Interaction, Date & Time Created, or Title. Additionally, you can filter them by Status, Severity, Teams, and Integrations, making it easier to prioritize and manage incidents effectively.

Slack Inbound Integration
Enhancing our beloved Slack Outbound Integration, you can now initiate a new incident directly from Slack using the /aq new command. This update empowers your team to use Slack not only as an Outbound Integration but also as an Inbound Integration.

Other Improvements

• Datadog Inbound Integration Update: We've updated our Datadog inbound integration to comply with the Apple App Site Association standards. This enhancement allows users to seamlessly open the Datadog app directly from All Quiet.

• Bulk Import for Teams: Recognizing the needs of larger teams, we've introduced a Bulk Import feature. This allows for the swift setup of teams, including escalation policies, through a bulk import process, significantly reducing setup time and effort.

• Engagement Reports Filters: To offer deeper insights into team performance and engagement, we've added new filters to our Engagement Reports based on Status, Severity and Integrations.

At All Quiet, we're dedicated to promoting calmness to empower more productive teams. That's why we're excited about this major enhancement!

We're introducing Personal Overrides that now allow you to designate one or more replacement users ready to take over your schedule. Team members can now set their own personal offline (and online) schedules, choosing volunteers to cover their on-call shifts during those times.

For admins, the new Overrides tab simplifies managing sudden changes, like unplanned illnesses or unexpected personal emergencies, by allowing quick reassignment of on-call responsibilities. This ensures your operations run smoothly, even when life gets unpredictable.

This feature should help you to ensure smooth operations with a calm and productive team.

Other Improvements

• Enhanced Visibility for Admins: Team Admins can now view the notification channels that team members have enabled, ensuring everyone receives their incident notifications promptly.

• Bug Fixes: We've resolved an issue where time details for higher Tiers were sometimes duplicated.

Ready to take control of your on-call schedule?

Delay & Customize Notification Channels
We've adapted our notification delivery to help users make All Quiet work for them. You can now delay individual notification channels, e.g., you want to receive calls only in case you might have missed the app notification. Users can also select which notification channels they would like to receive for which kind of incident. Overall this makes All Quiet less noisy and should empower teams to stay calm and efficient 🧘🏻‍♀️

Improved Auto Fill-ups
We've improved our auto fill-up functionality: When a Tier has no member on-call, we will fill up the empty Tier with the on-call members of the higher Tier. For instance, if there is only one person on-call in Tier 1 and he/she sets up a personal offline schedule, there will be an automatic replacement from the higher Tier, and it will be displayed clearly in the team overview.

More improvements & fixes

• Fixed bugs in calendar navigation while switching months

• Improved handling of incidents and UI on Android with a new update of the mobile app

Onboarding Wizard
We've added an onboarding wizard that helps new users set up their first team, inbound integration, personal notification channels and trigger an incident. All in less than 5 minutes. Ready, steady, all set for lean incident escalation 🏎️ 🧘🏻‍♀️

Dedicated Help Section
We've also implemented a dedicated help section so that you can find what you're looking for even faster 🏎️

Incident Counter
We've introduced a new feature that displays the total number of incidents from all pages on All Quiet for immediate visibility of critical incidents.

Other improvements

• Fixed calendar UX for individuals that have teams in different time zones where in some cases the text was overlapping

• Added a pop-up window to download the app without switching your current tab

Generic Outbound Webhook
We've added a generic Webhook outbound integration, enabling our users to connect with virtually any third-party service that accepts HTTP requests. Teams can now simplify their workflow and expand their toolkit with universal connectivity - not only for inbound integrations but also for outbound ones.

New Maintenance Mode

This new feature allows you to silence messages from a selected team for a specific period. Dive into two types of silencing: 'Maintenance', to prevent incident creation, and 'Muted', to create incidents quietly without sending notifications. Tailor your alert system to fit your team's unique needs.

Other improvements

• We've made some minor improvements to our new calendar, such as sorting schedules within a day by start and end

Hi 👋🏻  welcome to our new changelog (& roadmap)!

We are excited to kick off our changelog with an update that has been requested by many customers: A brand new scheduling calendar UX

Teams can now better view their on-call rotation at a glance with a clear weekly and monthly view. This way, you’ll directly see who is when on-call and can plan accordingly without the need to scroll to the right (for larger teams). We are happy to get your feedback on this or on anything else you’d like to see within All Quiet on the roadmap tab here. Your input really helps us build a lean and modern incident escalation solution, thanks! 🙏🏻

Other improvements

• Inviting team members is now easier with the ability to choose existing users for a new team

• Weekly incident reports are now only sent to teams with an active subscription

Happy scheduling!