Get Rootly's Incident Communications Playbook

Don't let an incident catch you off guard - download our new Incident Comms Playbook for effective incident comms strategies!

By submitting this form, you agree to the Privacy Policy and Terms of Use and agree to sharing your information with Rootly and Google.

Back to Changelog
Back to Changelog

August 21, 2025

Service & Team Broadcasts: Targeted Notifications for Enterprise Scale

Service & Team Broadcasts: Targeted Notifications for Enterprise Scale

Stop the notification noise. When you're managing hundreds of services across multiple teams, broadcasting every incident and alert to a single Slack channel creates information overload. Your stakeholders don't need to see every page, they need to see the incidents that matter to their services and teams.

Service & Team Broadcasts solves this by letting you configure announcement channels at the service and team level. Now when your payment service goes down or your database team gets paged, notifications go directly to the relevant channels where the right people can respond immediately.

This is essential for enterprise incident response at scale. When you have dozens or hundreds of services and teams, targeted notifications ensure the right people respond to the right incidents without overwhelming everyone else with irrelevant alerts.

How It Works

Team-Level Configuration: Navigate to any team in Rootly and open the Channels tab. Configure two notification types:

  • Setup a default Alerts Channel
  • Setup a default Incidents Channel

Or navigate to Configuration>Slack>Team Notifications

Service-Level Configuration: Same interface, different scope. Set up channels for individual services so when your API gateway or authentication service triggers an incident, only the relevant engineers and stakeholders see the notification.

← Previous post
← Previous post
Next post →
Next post →
← Pervious guide
← Pervious guide
Next guide →
Next guide →