← All scenariosILLUSTRATIVE RESPONSE WALKTHROUGH · SERVICE OUTAGE

When your customers cannot sign in.

The issue is technical. The response involves everyone.

Support is hearing from customers, engineers are tracing authentication failures and leadership needs a reliable update. The shared incident record connects the people and the evidence without pretending the platform fixed the outage.

THE SITUATIONCustomer sign-in disruptedPEOPLE INVOLVEDIncident commander · Technical lead · Communications leadTYPE OF EXAMPLEInvented example · no live incident
FROM THE FIRST FACT TO THE FINAL REVIEW

Here is what a shared response can look like.

Every stage shows the real-world problem beside the Criticl record that helps the people in the room. These are example workflows, not claims of automated threat monitoring, dispatch or external execution.

  1. 01

    Recognise the disruption

    Sign-in errors are reported by support and confirmed in the primary authentication path.

    IN THE CRITICL RECORD

    Declare a severity and capture the initial impact statement.

  2. 02

    Establish command

    Multiple teams need to respond without duplicating work.

    IN THE CRITICL RECORD

    Assign a commander and response roles; make the next owner visible.

  3. 03

    Coordinate and communicate

    Evidence is still developing. Customers want a reliable update.

    IN THE CRITICL RECORD

    Record observations and follow-ups, link the relevant playbook and prepare a factual draft update.

  4. 04

    Hand over without losing context

    The outage spans a shift change.

    IN THE CRITICL RECORD

    Freeze a handover snapshot of the operational picture for the incoming team.

  5. 05

    Learn from the incident

    The service has recovered; the causes and response still need review.

    IN THE CRITICL RECORD

    Preserve a structured audit export and postmortem workspace.

A PRACTICAL QUESTION FOR YOUR TEAM

Could your response team answer who is in charge, what is known and what happens next?

Open the related, read-only customer sign-in example. It is invented and has no live identity or provider integration.