Prepare customer alert notification routing Fictional staging demonstration. No route is saved, no webhook is entered and no email or notification is sent. Open Administration, General, Alert Routing in the fictional Summit Managed IT staging workspace. This page chooses notification destinations for matching alerts. We will prepare a Northwind Traders route without saving it. No email or webhook delivery is attempted in this walkthrough. The highlighted warning is out of date: routes never replace the default. Owners and administrators still get every notifying alert, or the storm incident that groups it. Routes add recipients and webhooks. Plan coverage for every customer and alert category before activating a routing setup. Use a name that describes the customer and purpose. Select Northwind Traders as the customer. Leave Any check selected for this draft so we can focus on customer and severity. In a real setup, review the check filter together with your intended coverage. Minimum severity offers warning plus critical, or critical only. Select critical only for this example. Notify on resolve requests a follow-up when a matching alert resolves. Check this choice with your on-call process so the team can distinguish a new problem from its recovery. The Emails field accepts comma-separated destinations. We enter a reserved example address for this draft. The webhook field is optional; keep real webhook URLs private because they can act as credentials. We leave it blank and do not send a test notification. Reopen Alert Routing to discard the unsaved example. Before activating a real route, verify the saved settings, test matching and nonmatching alerts, and confirm delivery to the intended destination.