Drafting the Customer Statement
Grace, Mia, and Emma refine a customer notice that explains what happened, what customers should do, and how the company will provide updates. Emma flags wording that may confuse or alarm readers unnecessarily.
Dialogue12

Let’s keep the notice direct, but not more definitive than the evidence. We can say an unauthorized party accessed our system; we’re still determining which records were involved.
Would “customer information may have been accessed” sound too vague? People might read that as a way of dodging the question.
It could, unless we explain what we know and what we don’t. We’ve confirmed access to part of the system, but we haven’t established that anyone copied or misused the data.
Then let’s say exactly that. We shouldn’t imply the data was stolen, but we also shouldn’t reassure customers that it wasn’t. Both claims would outrun the facts.
For the next paragraph, could we tell customers what to do without suggesting their accounts are definitely at risk? Maybe advise them to watch for unusual messages and avoid unexpected links.
That’s measured. We should also say we’ll never ask for their password or verification code in response to this incident, and direct them to sign in through our usual website.
Agreed. We need a clear contact channel, too. Emma, can you check that the support address is easy to find and that customers won’t mistake it for a phishing message?
Yes. I’d put it under a heading like “What you can do,” then list the steps. A dense block of legal language will make people miss the practical advice.
Let’s avoid promising a date for the final findings. We can commit to another update by a specific date, even if the investigation is still underway.
Good distinction. We’ll say we’re notifying affected customers directly as we confirm the scope, and we’ll post an update by Friday. If the facts change sooner, we’ll communicate sooner.
One last wording question: “We take your privacy seriously” feels generic on its own. Could we follow it with what we’re actually doing—investigating, securing the system, and cooperating with the regulator?
Yes. Let’s make the actions concrete, keep the uncertainty visible, and have legal and security review the final draft before it goes out. Clear is better than comforting but unsupported.
Vocabulary8
- not more definitive than the evidence
This means not making a stronger claim than the available facts support. Use it when communicating carefully about something that is still being investigated.
- dodging the question
This means avoiding a direct answer. It can suggest that someone is being evasive or deliberately unclear.
- outrun the facts
This means go beyond what the known facts justify. Use it to warn against making claims before there is enough evidence.
- measured
Here, this means carefully judged and not extreme. A measured response gives practical advice without causing unnecessary alarm.
- underway
This means currently happening or in progress. For example, an investigation can still be underway when an update is shared.
- the scope
This means the extent or range of something, such as which people or records were affected. Use it when the full impact is not yet known.
- concrete
This means specific and practical rather than vague or general. Concrete actions make a message more credible and useful.
- unsupported
This means not backed up by evidence. Use it for claims or reassurance that cannot yet be justified by what is known.
Key Sentences8
- 1
We can say an unauthorized party accessed our system; we’re still determining which records were involved.
This sentence states a confirmed fact and clearly identifies what remains uncertain. Reuse this structure to separate what you know from what you are still investigating.
- 2
We’ve confirmed access to part of the system, but we haven’t established that anyone copied or misused the data.
This is useful for explaining evidence without implying more than it proves. You can reuse “We’ve confirmed X, but we haven’t established Y” when giving a balanced update.
- 3
Both claims would outrun the facts.
This concise sentence explains why claims that go too far in either direction are risky. Use “outrun the facts” to caution against conclusions that the evidence does not support.
- 4
We should also say we’ll never ask for their password or verification code in response to this incident, and direct them to sign in through our usual website.
This sentence gives customers specific steps to help them recognize suspicious messages. Reuse the pattern “We’ll never ask for X, and direct you to Y” for clear security guidance.
- 5
We can commit to another update by a specific date, even if the investigation is still underway.
This distinguishes a promise to communicate from a promise to finish an investigation. It is useful when you can set a reliable update date but cannot predict when all the facts will be known.
- 6
If the facts change sooner, we’ll communicate sooner.
This is a clear, reassuring commitment to share important developments promptly. Reuse it when explaining how you will handle updates if circumstances change.
- 7
Could we follow it with what we’re actually doing—investigating, securing the system, and cooperating with the regulator?
This question encourages replacing a generic statement with specific actions. Use “what we’re actually doing” to ask for concrete details that make a message more informative.
- 8
Clear is better than comforting but unsupported.
This expresses the principle that honest, evidence-based communication is more valuable than reassurance without proof. Use it when deciding how to describe uncertain or sensitive situations.