Customer incident notices

Eng accuracy, support tone, and legal sign-off, on one notice.

The status update is moving fast. Agent connect removes a root-cause line you have not confirmed.

livenotices/login-outage-update.md

Login update for players

Owner: Alicia Grant. Game: Emberlane Games. Status page and player email.

Player-facing update for the Emberlane Games login outage. This notice goes to the status page and the player email after review. It is not the postmortem, and it should not sound like one. Alicia sends both after this pass.

What players saw

  • Login was unavailable this afternoon. Players could not start a session. Use these same sentences on the status page and in the player email.
  • Sessions that were already open stayed open. No progress was deleted, and no purchases were reversed.
  • Service is restored. New logins work, and the error page is gone. Players do not need to reinstall.

The note

We sincerely apologize for any inconvenience this may have caused to your play session.

That sentence reads like a form letter. A shorter apology can replace it after this pass. The sentence below is the one engineering asked to change, because it states a cause we have not confirmed. Leave the apology for Alicia.

The cause was an expired certificate on the login service.We have not confirmed the cause.

Next

  • A follow-up will say what happened after engineering confirms it. This note is not that follow-up.
  • Do not name a system, a team, or a certificate in this player note. Those details belong in the postmortem.

any inconvenience this may have caused

Zara Quinn

The apology is stiff. Players will read it as a form letter.

Alicia Grant

I will shorten it. We still cannot guess the cause.

expired certificate

Kenji Watanabe

@agent remove the root-cause guess, we have not confirmed it.

agent

Removed the unconfirmed cause. The notice now says we have not confirmed it.

resolved
Start with @agent to ask the agent
ResolveReply
Fictional example: an Emberlane Games player notice in Gander, with a tone thread and a scripted agent connect reply.

How customer notices get reviewed today

A chat channel is fast, which matters during an incident. The approved sentence then has to be copied into the status page, and a later edit of the draft does not match what legal saw.

A shared doc is calmer and slower to find. The status page itself is where players look, and it is a blunt tool for arguing about a sentence.

Take out the guess

Alicia Grant drafts a player-facing update for the Emberlane Games login outage with her agent. She runs gander watch on notices/login-outage-update.md and sends it to Kenji Watanabe, Zara Quinn, and Omar Farouk.

Zara highlights the apology and says it is stiff. Alicia replies with a plainer line. Human thread.

Kenji starts a new comment: "@agent remove the root-cause guess, we have not confirmed it." Alicia's agent deletes the certificate sentence, replies, and resolves the thread. Omar sees the notice without the guess, on the same link. The update then goes to the status page and the player email Emberlane already uses.

Who's in the doc

WriterIncident commanderCommunity leadLegalThe author's agent

Writer Support or incident comms. Sends one link while the incident is still moving.

Incident commander Checks facts.

Community lead Checks tone.

Legal Checks what you are claiming.

The author's agent Removes the guess when someone uses agent connect.

Reviewers only need a browser. Talk to each other in normal threads. Use agent connect when you want the draft changed.

Agents that fit customer incident notices

Grok BotA short notice from the incident notes, with agent connect through MCP.
Claude CodeWhen the notice is drafted beside the postmortem, MCP carries agent connect.

Agree the notice on the live draft. Publish it on the status page you already run.

See how it works on the homepage