Customer & OpsIntermediate 2 to 3 hours

Manage Internal Incident Comms

Write the internal Slack updates and executive summary during a data breach.

The Scenario

A third-party marketing tool was compromised, and 5,000 of your customers' email addresses were leaked. It's an active Sev1 incident. The CEO is panicking, the support team is confused, and engineering is trying to lock down the system.

The Brief

Act as the Incident Commander for communications. Draft the internal updates to keep the company aligned without distracting the engineers.

Deliverables

  • An initial `@channel` Slack blast to the whole company explaining the situation and declaring a code red
  • A strict instruction to the Support Team on exactly what to tell customers right now (an interim macro)
  • A 3-bullet executive summary to be sent to the CEO and Legal team detailing the known scope of the breach

Submission Guidance

Internal incident comms are about control. You must stop sales reps from tweeting, stop support agents from guessing, and give executives just enough info so they don't barge into the war room.

Submit Your Work

Your submission is graded against the rubric on the right. If you pass, you get a public Badge URL you can share on LinkedIn. There is no draft save, so work offline first and paste your finished response here.

This appears on your public Badge.

0/20000 charactersMarkdown supported

One per line or comma separated. Up to 5 links.

By submitting, you agree your submission text, name, and evaluation will appear on a public Badge URL.