SupportSupport Leadbeginner 10 min saved

Customer Automation Failure Notification

Draft a concise, factual notification about a failed customer automation, its status, and the goodwill offer.

Customise & copy

Add the context you have. The prompt updates as you work.

Customer name or ID *

Provide the customer name or account identifier to reference in the notification.

Failed process name *

Name the bot, workflow, or automation that failed.

Root cause summary *

Explain the cause in plain language without internal jargon or blame.

Resolution status and steps taken *

State what has been done and whether the issue is fixed, being monitored, or expected to be resolved by a specific time.

Compensation or goodwill offer *

Provide the exact compensation or goodwill gesture, including limits or timing if relevant.

Live prompt

5 fields

Draft a concise, honest customer failure notification using only the facts provided. Do not invent details, blame the customer, use jargon, add hype, or include a greeting, sign-off, or politeness padding. Acknowledge the impact directly without excessive apology or defensiveness. State the root cause in plain language, describe the current resolution status and timeline exactly as provided, and include the specific goodwill offer. Return only this fixed structure:

Subject: Automation failure update for {{customer_name_or_id}}
What happened: The {{failed_process_name}} failed because {{root_cause_summary}}.
Current status: {{resolution_status_and_steps}}
Goodwill: {{goodwill_offer_details}}

Keep the notification concise and suitable for sending after one light edit. If the information does not confirm a fix or timeline, state that clearly rather than implying one.

Proof before you use it

A real example

Tested on gpt-5.6-luna on 2026-09-10

{
  "root_cause_summary": "A third-party shipping API changed its response format, so status updates could not be processed.",
  "customer_name_or_id": "Northstar Outfitters",
  "failed_process_name": "Order-status notification bot",
  "goodwill_offer_details": "We will credit one week of the automation service fee on your next invoice.",
  "resolution_status_and_steps": "We updated the integration, replayed the affected events, and are monitoring new orders. Processing is restored as of 14:30 UTC."
}

A small ritual that works

How to use it

01Enter the customer name or account ID and the failed process name.
02Describe the root cause in plain language without jargon or blame.
03State the resolution status, steps taken, and confirmed timeline.
04Add the exact compensation or goodwill offer.

Why it works

The prompt defines a narrow customer-notification task, sets clear boundaries against invention and blame, and provides a fixed four-part structure. Each section has a specific purpose: identify the failed process, explain the cause, state the current status, and present the goodwill offer. The instruction to describe an unconfirmed fix or timeline plainly helps preserve accuracy when the available facts are limited.

Where it fails

It is constrained by the quality and completeness of the facts supplied for the customer, failed process, cause, resolution status, and goodwill offer. Ambiguous or overly technical source details may still require human judgment to make them plain and customer-appropriate without adding information.

Customisation tips

Adjust the subject wording, section labels, or tone guidance if the notification must match a particular communication policy. Refine the input guidance to specify approved terminology, time-zone formatting, compensation rules, escalation language, or channel-specific length limits. Keep the fixed structure if consistent, quickly scannable notices are important.

Watch-outs

The prompt prohibits greetings, sign-offs, politeness padding, jargon, hype, and blame, so it is designed for a direct operational notice rather than a relationship-focused message.
The resolution field should distinguish clearly between a completed fix, ongoing monitoring, planned work, and an unknown timeline.
Goodwill details should include any relevant limits, eligibility conditions, or timing because the prompt asks for the specific offer rather than a general promise.
The phrase "after one light edit" signals a concise drafting aid, not a substitute for checking names, times, cause descriptions, and compensation details before sending.

Works in

Support ticketsCustomer emailIncident responseAccount management

Was this useful?

Submit your variation

If your version helps, it may be published with your name and a link back to you.

Support

Sincere Apology Email Draft

Write a clear, accountable apology email with a concrete solution and a trust-building close.

Want to make AI useful across your team? Explore Atul's training.