Skip to main content

Major Cases quick start: for the MSO team

The short version: run an incident from promote to Reason For Outage in six steps.

Written by Nick Kewney

This page is for people with the MSO Team or MSO Manager role, who run Major Cases. It's the short version. Each step links to the full guide.


An incident, start to finish

  1. Promote. On the first affected customer's case, open Major Incident in the side panel and click Promote to Major Case. Give the reason and the outage type. More

  2. Link the other affected cases. On the Major Case, in Associated Cases, add each affected customer's case as Parent Of. This needs the Allow Manage Case Link role. More

  3. Keep customers updated. Click Send customer update. Start from a template if your company has them, check who it goes to, and send. More

  4. Record what happened. Fill in the Structured Review as you go, then click Finalise review. More

  5. Close. Click Close Major Case and send the resolution note. Every affected customer's case closes with it. More

  6. Publish the Reason For Outage. Write the five sections on the Reason For Outage tab and submit them. Once approved, it goes to every affected customer. More


Keep track

  • A case work stack with Show Major Cases only lists every incident, with its state, review and RFO progress under each subject.

  • The Overdue RFOs dashboard tile shows every Reason For Outage that's past its target date.


Good to know

  • Work on the Case Management Screen. Linking cases and copying notes to child cases are only there.

  • When you add a note to a Major Case, Cascade to child cases is ticked by default. If you also tick Visible to customer, every affected customer sees it.

  • Only an MSO Manager can decouple a case from its Major Case.

Did this answer your question?