Duty, sos & incident response

No critical issue goes unanswered.

Mteja360 Command knows who is on duty, who is backup, who must acknowledge, when to escalate and what must happen before an incident is truly closed.

When critical response depends on phone calls, memory or WhatsApp groups, risk grows.

No certainty about who is on duty.

Backup coverage is unclear.

An alert can be delivered without anyone acknowledging ownership.

Executives chase updates
manually.

Service restoration gets confused with true closure.

Root cause and corrective actions disappear after the crisis.

Duty rosters, primary and backup coverage.

SOS reporting from supported channels.

Explicit acknowledgement.

Time- and severity- based escalation.

Incident ownership and command room.

Linked tickets and tasks.

Stakeholder updates.

Restoration, monitoring and closure.

Root cause and follow-up actions.

Audit-ready timeline.

Command works as a complete Mteja360 module
without MtejaFlow.

WhatsApp and AI can enhance the response, but they
do not own the incident.