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 sentence states the default. Routes never replace it: every owner and administrator still gets each alert that Alert Rules set to notify, or the storm incident that groups it. Routes add recipients and webhooks for anyone else who needs to hear about an alert. 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. Review the customer, check filter, severity, resolution setting and destinations together. Add route would save the route and change notification behavior. We do not press it here. Cedar Valley Dental and Harborline Logistics need their own planned coverage if they should receive different notifications. Recent webhook attempts provides evidence about attempted webhook requests. Read the recorded status and time. Provider accepted describes the provider response, and does not by itself prove that a person saw the message. An empty history does not demonstrate successful delivery. Reopen Alert Routing to discard the unsaved example. For an authorized rollout, save the reviewed route, reopen it to verify the stored configuration, and exercise both a matching and a nonmatching alert in a test environment. Confirm the intended destination receives the matching notification and verify resolution behavior separately.