# Messaging Channel SLA and Escalation Worksheet (Excel Export) > Source: https://netray.co/tools/messaging-channel-sla-and-escalation-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Define how fast each alert type must be acknowledged, who is escalated to and which fallback channel is used. Exports to Excel. ## Category erp-operations ## Audience - Operations manager - IT service owner - Plant manager ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Alert type **Key:** alert **Type:** text #### Severity **Key:** severity **Type:** select **Options:** - Critical - High - Medium - Low #### Primary recipient **Key:** primary **Type:** text #### Primary channel **Key:** channel **Type:** select **Options:** - Teams - WhatsApp - SMS - Email - Phone call #### Acknowledge within **Key:** ack_min **Type:** number **Unit:** min #### Escalate after (x ack) **Key:** esc_factor **Type:** number #### Escalate at **Key:** esc_min **Type:** number **Expr:** ack_min * esc_factor **Format:** minutes #### Escalation recipient **Key:** next **Type:** text #### Fallback channel **Key:** fallback **Type:** select **Options:** - Teams - WhatsApp - SMS - Email - Phone call #### Expected per day **Key:** per_day **Type:** number **Rows:** **Alert:** CNC spindle alarm on critical machine **Severity:** Critical **Primary:** Shift supervisor **Channel:** Teams **Ack min:** 5 **Esc factor:** 2 **Next:** Maintenance manager **Fallback:** Phone call **Per day:** 2 **Alert:** Quality hold on shipped lot **Severity:** High **Primary:** Quality engineer **Channel:** Teams **Ack min:** 15 **Esc factor:** 2 **Next:** Quality manager **Fallback:** SMS **Per day:** 1 **Alert:** Late supplier PO line **Severity:** Medium **Primary:** Buyer **Channel:** Teams **Ack min:** 240 **Esc factor:** 2 **Next:** Purchasing manager **Fallback:** Email **Per day:** 25 **Alert:** Approval waiting over 24 hours **Severity:** Low **Primary:** Approver **Channel:** WhatsApp **Ack min:** 480 **Esc factor:** 3 **Next:** Approver's manager **Fallback:** Email **Per day:** 12 **Totals:** #### Total alerts per day **Key:** per_day **Agg:** sum **Format:** integer #### Fastest acknowledge target **Key:** ack_min **Agg:** min **Format:** minutes **Summary:** #### Average alerts per type per day **Key:** alerts_per_type **Expr:** sum_per_day / count **Format:** decimal **Notes:** WhatsApp and SMS may involve consent and cost considerations for staff messaging. Confirm policy with HR and legal before using personal devices for critical alerts. ## Content **Intro:** Sending an alert is not the same as someone acting on it. This worksheet forces a decision for every alert type: who gets it, how quickly they must acknowledge, when it escalates and what backup channel is used if chat fails. Edit the examples, then export to Excel. **Sections:** #### How to use the worksheet **Body:** List each alert your ERP, MES or quality system will push. Assign severity, a named role as recipient and the primary channel. Set an acknowledgment target in minutes and an escalation factor. The escalate-at column multiplies them, so a 15 minute acknowledge target with a factor of 2 escalates at 30 minutes. Choose a fallback channel that does not depend on the same platform. The totals show expected daily volume so you can judge fatigue. #### Setting realistic targets **Body:** Base acknowledge times on the consequence of delay, not on what the tool can do. A machine alarm that stops a line may need five minutes, while a late purchase line can wait half a day. Count how many alerts per person per day the design produces. If one buyer receives dozens of medium alerts, consider a digest. Review actual acknowledgment times after the pilot and adjust. Critical alerts should have at least one channel that is independent of Teams or WhatsApp. **Bullets:** - Severity based on business consequence - Named role, not a shared mailbox - Fallback independent of the primary platform - Volume per person reviewed monthly #### Common mistakes **Body:** Treating every alert as critical trains people to ignore all of them. Another mistake is escalating to a person without covering holidays and shifts, so maintain an on-call roster elsewhere and reference it. Teams also forget that an alert acknowledged in chat should update the source system, or the same event will be raised again. Record in the worksheet how acknowledgment is captured, for example a button press that writes back through an approved interface. **Cta:** If you want ERP events turned into routed, acknowledged alerts with an audit trail, Netray can help design it on your own systems. **Faq:** #### What is a good escalation factor? **Answer:** Two is common for urgent alerts, giving the primary recipient one extra interval. Lower-severity alerts can use three or more. Tune it against actual acknowledgment data. #### Should critical alerts go over WhatsApp? **Answer:** Only if your policy allows messaging on personal devices and you accept the platform dependency. Pair it with an independent fallback such as an automated call or pager. #### How do I handle shift changes? **Answer:** Address alerts to a role resolved from your roster at send time, not to a fixed person. Keep the roster in one system and reference it here. #### How many alerts per person is too many? **Answer:** There is no fixed number, but if recipients start muting the channel you are over. Digest low-severity items and review volume per person monthly. ## Search terms alert escalation matrix template, notification sla worksheet, escalation matrix excel, teams alert escalation policy, erp alert response time template, on-call notification matrix --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json