Skip to content
Log in

Incident Communication to Customers

Writes the outage or breach update that tells people what they need to know, at the moment they need it, without overcommitting.

0

Share this prompt

Free — no card needed

Create a free account

to open Incident Communication to Customers — and the other 364 prompts across 21 categories.

We store your email address to send these. We never sell it or pass it to advertisers. Withdraw at any time. Privacy Policy.

Already have an account?

CategoryCustomer ServiceForOperators, Founders, Sales TeamsTested onClaudeChatGPT

Running it, start to finish

  1. Establish whether personal data was affected before drafting anything.
  2. Publish the first update with a next-update time.
  3. Keep the interval even when there is nothing new.

What you get back

The output this produces, every time.

  • Determines first whether this is a regulated data-breach disclosure with statutory timelines.
  • Commits to a next-update time, which is the element that keeps customers from refreshing anxiously.
  • Drafts the nothing-new update, since silence between updates is what actually damages trust.

Getting better results

Where this usually goes wrong, and how to avoid it.

  • Publish before you know the cause. The first update's job is to say you know. Waiting until you can explain is how a one-hour outage becomes a trust problem.
  • Send the empty update. Section 3 exists because teams skip the update when there is nothing to report, which is exactly when customers most need to see one.
  • Stop at section 1 if data is involved. Breach notification has legal content and timing requirements. That message goes through counsel, not through this prompt.

More Customer Service prompts

All Customer Service

Written for The AI University. Every prompt in this library is original work — authored, tested and revised here, not collected from elsewhere. 365 of them, free with an account.