Difficult messages
Apologize Before You Know the Cause
Send a first response that acknowledges the problem and states the next step, without admitting a cause you have not confirmed.
The first reply is not the investigation
Something went wrong and the customer is waiting. The pressure is to explain why — but you do not know why yet. Guessing a cause in the first message creates a second problem: when the real cause turns out to be different, you have to correct yourself, and the correction is what people remember.
A first response has one job: show the person that this is being handled, and tell them when they will hear more.
Four parts, in this order
- Acknowledge what they experienced — the fact of the trouble, not your theory about it.
- Say what is confirmed — only what you have actually verified in your records.
- Say what is not yet confirmed — plainly. “We are still checking the cause” is a complete sentence.
- Give a next contact point — when you will follow up, and who will do it.
A prompt for the shape, not the content
Build an empty first-response template with these five fields: acknowledgement, confirmed facts, not yet confirmed, next update time, contact person. Leave every field blank. Do not write a cause, a compensation offer, a deadline, or an apology for a specific mistake. Add a note that each field must be filled from official records by a person.
Words that commit you before you are ready
“This was caused by…”, “We will refund…”, “This will never happen again.” Each one is a commitment about something you have not verified. Compensation, liability, and prevention belong in a later message, after the facts are known and the responsible person has decided.
When to stop writing and escalate
If the situation involves safety, health, legal exposure, money already taken, or personal data, the first response is not a writing task. Follow your workplace's incident procedure and bring in the person who is authorised to decide.