Accountable Client Issue Message
Draft a calm, direct client message that acknowledges an issue, explains the impact, and sets the next step.
Customise & copy
Add the context you have. The prompt updates as you work.
Enter the client's name, team, or professional title.
State exactly what went wrong, using factual and concise language.
Describe the measurable or practical effect on the client's work, timing, cost, or expectations.
Describe the specific action already taken or now being implemented to resolve the issue.
State what happens next, who owns it, and when the client should expect it.
Live prompt
5 fieldsDraft a ready-to-send client message about the issue below. Return exactly two parts: a concise subject line or opening, followed by the message body. Client: {{client_name_or_title}} What went wrong: {{mistake_description}} Impact on the client: {{client_impact}} Immediate fix: {{immediate_fix}} Next step or timeline: {{next_step_or_timeline}} Acknowledge the mistake directly without excuses, external blame, or defensiveness. Explain the impact from the client's perspective, state the concrete corrective action, and make the next step or timeline unmistakable. Keep the language professional, direct, calm, and accountable. Avoid hype, excessive apology, vague assurances, and invented details. Write for one light edit and do not ask follow-up questions.
Proof before you use it
A real example
Tested on gpt-5.6-luna on 2026-09-09
{
"client_impact": "Your customer success team missed two planned notification windows and had to reschedule communications with 180 customers.",
"immediate_fix": "We corrected the regional settings, reviewed the notification schedule, and paused further automated sends until the configuration passed a second verification.",
"mistake_description": "The onboarding configuration for your new workspace was applied with the wrong regional settings, so several automated notifications were sent at the incorrect time.",
"client_name_or_title": "Maya Chen, Director of Customer Success",
"next_step_or_timeline": "We will provide the corrected send report by 2:00 p.m. today and confirm the final configuration with you before automation resumes."
}A small ritual that works
How to use it
- 01Enter the client name or title.
- 02Describe what went wrong and its concrete impact.
- 03State the immediate fix being implemented.
- 04Add the next step, owner, or timeline.
Why it works
The prompt turns a difficult client communication into a defined sequence: identify the mistake, explain the client's impact, state the corrective action, and clarify the next step or timeline. Its required fields guide the writer toward concrete information, while the tone rules reduce defensiveness, vague reassurance, hype, and invented details. The instruction to return a subject line or opening followed by a message body also gives the final message a clear, ready-to-send shape.
Where it fails
The prompt is less suitable when the situation requires investigation before responsibility can be stated, legal or regulatory review, negotiation over liability, or a detailed recovery plan. Its instruction not to ask follow-up questions also means the supplied fields must contain enough accurate context for the message to be specific and safe.
Customisation tips
Adjust the client field guidance if messages are intended for a named individual, a team, or an executive audience. Add a separate variable for ownership when the next-step field should not carry both the action and the responsible person. If the communication needs a formal sign-off, deadline, support contact, or compensation proposal, add those as explicit inputs and corresponding instructions rather than relying on the writer to infer them. You can also refine the tone guidance for industries that require highly formal, technical, or regulated language.
Watch-outs
- Use factual, confirmed descriptions for the mistake and impact; the prompt explicitly discourages invented details.
- Make the corrective action distinct from the future timeline so the reader can tell what has already happened and what remains pending.
- Include an owner and a concrete time or date in the next-step field when accountability matters.
- Avoid placing speculation, internal debate, or blame in the input fields, since the requested message is designed to be direct and client-facing.
Works in
Was this useful?
Submit your variation
If your version helps, it may be published with your name and a link back to you.
Related prompts
Want to make AI useful across your team? Explore Atul's training.