Incident Alert with Full Context
“Not just an alarm — a root cause analysis delivered to your phone.”
📖 The Scene
When Press #3's vibration crossed the threshold, NayaCore didn't blast a generic alert to everyone. It checked the live shift roster and routed the full diagnostic only to Siti (on-duty dispatcher) and a condensed summary to Pak Hendra (always-on executive). Ahmad, who was off-duty, slept through it.
Ahmad
Shift Supervisor (T2)
Incident Notification & Severity Routing
NayaCore routes each alert to the right person based on severity, shift status, and tier—eliminating alert fatigue.
Sev-2 Alert (Full Detail)
A vibration anomaly occurs at Press #3. Since it's Severity 2, NayaCore routes the full diagnostic and AI recommendation only to Siti (T2.5) because she is currently on-duty. Ahmad, who is off-duty, is intentionally skipped.
Sev-2 Alert (Condensed)
Simultaneously, Pak Hendra (T3) receives a condensed 3-line version. He is 'always_on' but doesn't need to see the FFT analysis or approve the workflow—he just needs to know Siti is handling it.
Sev-1 Critical Alert & Escalation
A critical pressure drop (Sev-1) bypasses shift tier restrictions. It blasts to all T2 and T2.5 on-duty staff. After 5 minutes of no response, an automatic reminder is sent. At 10 minutes, NayaCore would place a WhatsApp phone call.
📊 Before vs. After
Traditional Operations vs. NayaCore
| Metric | Traditional | NayaCore |
|---|---|---|
| Alert Routing | All-or-nothing (broadcast) | Role × shift × severity filtered |
| Off-duty wake-ups (non-critical) | 5–10/week | 0 (shifts are respected) |
| Critical alert response time | Unknown (no tracking) | Median < 3 minutes (with escalation timer) |