Customer apology that fixes the problem
Reply to an unhappy customer with a sincere, specific apology and a clear remedy, not canned phrases.
Turn your week's work into a crisp status update covering progress, blockers and next steps.
Write a status update from the raw notes below.
Reader: {{reader}}
Project or team: {{project}}
Reporting period: {{period}}
Format: {{format}}
My raw notes:
{{notes}}
Rules:
- Lead with overall status as one of: On track, At risk, Off track, with a one-line reason.
- Report results and outcomes, not activity. "Shipped X" beats "worked on X".
- Quantify progress where my notes allow. Do not invent numbers or dates.
- Make blockers specific: what is blocked, who can unblock it and by when.
- List next-period priorities in order, three at most.
- Keep it under 180 words and avoid filler like "just wanted to update you".
Output format: use the requested format, with sections Status, Done, Blockers and asks, Next. Omit empty sections.Marking an honest At risk with a named ask is what makes a status update useful. Include dates in your notes for sharper deadlines.
Licensed CC0 (public domain) Version 1 · history
Reply to an unhappy customer with a sincere, specific apology and a clear remedy, not canned phrases.
Paste an incoming email and your intent, and get a reply that answers every point in the right tone.
Say no clearly and kindly to a request or invitation, protecting the relationship and your time.
Deliver hard news or feedback clearly and kindly, without burying the point or sounding cold.
Turn a furious customer message into a reply that acknowledges the problem, takes ownership and offers a clear next step without grovelling.
Turn scattered progress notes into a status update with RAG status, risks, asks and next steps that leaders actually read.
Comments (0)
Sign in to join the discussion.
No comments yet. Be the first to share how it worked.