Course resource

Difficult Reply Templates

The messages people put off writing. Each has the structure that works, a prompt, and the mistake that makes it worse.

The angry customer

Structure: name the specific problem → what you will do → by when → one line of warmth.

Here is an angry message:
[PASTE]

First tell me, separately: what are they actually upset about, as
distinct from what they are shouting about? What outcome do they want?

Then draft a reply that:
- Names the specific thing that went wrong, not "any inconvenience"
- States what I will do and by when
- Does not admit fault that has not been established
- Does not match their tone or their volume
- Is under 120 words

Do not open with an apology paragraph.

The mistake: generic apology. "We apologise for any inconvenience caused" reads as a form letter and escalates the anger.

The mistake you made

Structure: what happened → impact → fix → prevention → no excuses.

I made this mistake: [WHAT]
Who it affected and how: [IMPACT]
What I am doing about it: [FIX AND WHEN]
How I will stop it recurring: [PREVENTION]

Write this to [WHO]. Rules:
- Own it in the first sentence. No build-up.
- One sentence of context maximum, and only if it changes their decision
- No "mistakes were made"
- Do not over-apologise — once, sincerely, then move to the fix

The mistake: explaining at length. Every extra sentence of context reads as excuse-making, however fair it is.

Pushing back on your manager

Structure: agree with the goal → name the constraint → offer the trade → ask for the decision.

I have been asked to [REQUEST] by [WHEN].
The problem: [WHY IT IS NOT FEASIBLE AS STATED]
What I could do instead: [OPTIONS WITH TRADE-OFFS]
What I need them to decide: [THE CHOICE]

Write this so it reads as problem-solving, not refusal.
Lead by agreeing with what they are trying to achieve.
Under 120 words. End with a specific question.

The mistake: saying no without offering the trade. "I can't" starts an argument; "I can do X by Friday or Y by Wednesday — which?" gets a decision.

Chasing an overdue payment

Structure: the facts → the specific ask → the consequence, stated neutrally.

Invoice [NUMBER] for [AMOUNT] was due [DATE], now [N] days overdue.
Relationship: [ONGOING CLIENT / ONE-OFF]
Previous contact: [WHAT YOU HAVE ALREADY SENT]
Next step if unpaid: [WHAT YOU WILL ACTUALLY DO]

Write three escalating versions: friendly reminder, firm, final notice.
Facts and dates only. No apology for asking.
State the next step as a fact, not a threat.

The mistake: apologising. You are asking to be paid for work you did.

Declining an opportunity

Structure: thank → decline clearly → one reason → leave the door open if you mean it.

I am declining [OPPORTUNITY] from [WHO].
Real reason: [FOR MY CONTEXT]
What I will say: [PUBLIC REASON]
Do I want future contact? [YES / NO]

Decline in the first two sentences. One reason only.
If yes to future contact, say something specific — not "let's stay in touch".
If no, close it cleanly without implying otherwise.
Under 80 words.

The mistake: a false "maybe later" that leaves them chasing you for months.

Giving critical feedback

Structure: the specific behaviour → the effect → the ask → the offer of support.

I need to give [WHO] feedback about [BEHAVIOUR].
Specific examples: [TWO OR THREE, WITH DATES]
Effect it has: [ON THE WORK, THE TEAM, OR THE CLIENT]
What I want instead: [CONCRETE, OBSERVABLE]
Support I can offer: [WHAT]

Rules:
- Describe behaviour, never character. "The report arrived two days late
  twice" not "you're unreliable"
- No compliment sandwich
- Make the requested change concrete enough to verify
- End by asking for their view, and mean it

The mistake: the compliment sandwich. Everyone recognises it, nobody hears the middle.

Delivering bad news to a client

Structure: the news → the impact on them → what you are doing → what you need → when you will next update.

I need to tell [CLIENT] that [BAD NEWS].
Impact on them: [SPECIFIC]
What I am doing: [ACTIONS AND DATES]
What I need from them: [IF ANYTHING]
Next update: [WHEN]

The news goes in the first sentence. No warm-up paragraph.
Do not promise a recovery date I am not certain of.
Offer a call if the news is significant.

The mistake: burying it, or promising a fix date you then miss. Missing the second date is much worse than the original problem.

Before you send any of these

That last check is the most useful one on this page.

Back to dashboard