The reply that sets the tone.
WHAT IT MUST DO
Acknowledge the specific problem Show you understood it State what happens next Give a timeframe
WHAT IT MUST NOT BE
A generic acknowledgement with no content.
WHY
It reads as an automated brush-off, even when a person wrote it.
WHAT TO DO FIRST
Restate the problem in your own words.
WHY
It proves you read it, and it surfaces misunderstandings immediately.
WHAT TO AVOID IN THE OPENING
Apologising before understanding Promising a resolution you cannot guarantee Asking for information already provided
WHY THAT LAST ONE MATTERS
It is the fastest way to frustrate someone.
WHAT TO CHECK BEFORE ASKING ANYTHING
Whether the answer is already in the message or the account.
WHAT TO ASK FOR IF YOU MUST
Everything you need, at once.
WHY
Each round trip costs hours, and several feel like obstruction.
WHAT TO INCLUDE
The ticket reference.
WHAT TONE TO USE
Plain, direct, and human.
WHAT TO AVOID
Corporate phrasing Excessive formality Excessive familiarity
WHAT TO END WITH
What you will do, and when they will hear from you.
