Skip to content
← All guides

Guide · Beginner · 4 min

Prompt for a difficult client email

Bad news emails fail on tone. Tone comes from constraints, not from asking for a tone.

Asking for 'professional' gets you grovelling

Models over-apologise when told to be professional about bad news. You get four sentences of regret before the reader learns what happened. The fix is not a better adjective — it is a rule: 'no more than one sentence of apology'. Rules survive; adjectives get interpreted.

State the facts the reader will check

The old date, the new date, and the real reason. A model given 'there is a delay' invents a vague cause that will not survive contact with the client. Give it the actual one, and say what you are doing to protect what the client cares about.

Lead with the change, not the context

Ask for the subject line to carry the new date. People triage bad news in the inbox list, and a subject that says 'quick update' makes them open it expecting nothing.

Try it

Give it the facts and one hard rule about apology. Aim for a score of 85+.

52structure

Target: 85. Keep working the prompt — the score moves as you type.

  • Role / persona: Open with a persona, e.g. "You are a senior backend engineer."
  • Context: Front-load all context the model needs: inputs, audience, goal, and constraints — so it can answer in one shot.
  • Constraints: State limits and do/don't rules, e.g. "Keep it under 200 words. Do not invent APIs."