Skip to content

Guides

Tell customers about a security incident

After a security incident, trust depends on how clearly and quickly you speak. Support is on the front line, so it needs facts, approved wording and a way to reach the people who know more.

Last reviewed

Agree who speaks and what is approved

Before anything goes out, decide who approves wording and who is the single source of facts. Agents should never improvise about what was affected.

Say what happened in plain words

Describe what occurred, when, what data was involved and what is not affected. Avoid jargon and avoid guessing.

Tell customers what to do

Give clear steps, such as changing a password or checking an account, and say when they should do it. Action is what people want most.

Prepare replies for the likely questions

Write saved replies for am I affected, what was taken and what are you doing. Update them as the facts become clearer.

Send updates on a schedule

Even when there is little new, say so on a promised date. Silence feels like hiding something.

Review and learn afterwards

Once things settle, check which questions came up most and what was unclear. Improve the next response and the prevention work.

Questions

How soon should we tell customers?

As soon as you know enough to say something true and useful, and within any legal deadline that applies to you.

What if we do not know yet what was affected?

Say so, explain what you are checking and give a time for the next update. Do not guess.

Should agents answer technical questions?

Only with approved wording. Pass anything else to the security lead and tell the customer when they will hear back.

Written by Flatdesk, a help desk for small support teams at one flat price per agent. Try it free for 14 days, no card.