client_complaint_response_email
Write professional email responses to client complaints with three approaches: acknowledge and fix, dispute fairly, or follow up after resolution. Protects client relationships without over-apologizing or getting defensive.
Instructions
Write a professional email responding to a client complaint or serious dissatisfaction — distinct from creative feedback on deliverables. This is for relationship-level issues: missed expectations, process frustrations, quality concerns, or a client who is genuinely upset. The hardest email to write under pressure — most freelancers either over-apologise (which signals guilt and invites further demands) or get defensive (which escalates). Three routes: acknowledge (own what's warranted, propose a concrete fix — the default for most complaints), dispute (professionally push back on a complaint you don't agree is fair, without burning the relationship), resolve (follow-up once the issue has been addressed, closing the loop and resetting the tone). Required: client_name, complaint_summary. Optional: project_name, what_went_wrong (for acknowledge), proposed_fix, your_response (for dispute — your position in 1-2 sentences), resolution_summary (for resolve), route, your_name. Does not count against your monthly draft limit.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| client_name | Yes | The client's first name | |
| complaint_summary | Yes | A brief description of what the client is unhappy about (e.g. 'missed the agreed deadline by four days', 'the final design didn't match the brief', 'communication was slow during the project', 'the invoice was higher than expected') | |
| project_name | No | Optional: the project name — helps ground the email (e.g. 'the brand identity project', 'the website build') | |
| what_went_wrong | No | Optional (used with route=acknowledge): a brief honest explanation of what happened — not an excuse, but context that shows you understand the issue (e.g. 'a dependency on the third-party API took longer than anticipated', 'I misread the brief on the colour palette'). If omitted, the email acknowledges without detailed explanation. | |
| proposed_fix | No | Optional (used with route=acknowledge): the concrete step you're taking or proposing to resolve it (e.g. 'an additional revision round at no charge', 'a partial refund of $200', 'a call this week to realign'). If omitted, the email offers to discuss the best path forward. | |
| your_response | No | Optional (used with route=dispute): your position in 1-2 sentences — what you disagree with and why, framed as clarification not confrontation (e.g. 'the timeline was extended at your request on March 12', 'the brief specified a dark background and the design followed that exactly'). Keep factual. | |
| resolution_summary | No | Optional (used with route=resolve): what was done to resolve the issue (e.g. 'delivered the revised designs', 'applied the partial credit to the invoice', 'we got on a call and realigned on the scope'). If omitted, the email references the resolution generically. | |
| route | No | acknowledge: own what's warranted and propose a fix (default — right for most complaints). dispute: professionally push back on a complaint you disagree with. resolve: follow-up once the issue has been resolved, resetting the relationship. | |
| your_name | No | Optional: your name for the sign-off |