Write an apology email without unconfirmed compensation

Autor: AILesson4 Min. EinrichtungszeitGetestet mit:ChatGPTGeprüft am: 2026-08-28

Schnelle Antwort

Acknowledge impact and known responsibility while keeping remedies within confirmed authority. Angeben: Verified incident facts, Confirmed response, Recipient and boundaries. Erwartetes Ergebnis: An accountable apology, factual update, approved next steps, and escalation path.

1

Kontext hinzufügen

Dein Text bleibt in diesem Browser. AILesson Prompts sendet ihn nicht an ein Modell oder einen Server.

2

Dein Prompt

Nicht ausgefüllte Felder bleiben als Platzhalter sichtbar, sodass du den Prompt weiterhin kopieren und bearbeiten kannst.

Write an apology email based only on verified facts and confirmed authority.

Incident, impact, timing, cause status, and uncertainty:
[incident]

Completed actions, planned actions, owners, updates, and approved remedies:
[response]

Recipient, tone, authority limits, and contact route:
[recipient]

Acknowledge the recipient's concrete impact, apologize directly, and distinguish known facts from ongoing investigation. Do not speculate about cause or fault. State only actions and timelines that are confirmed. Do not promise refunds, credits, replacement, reimbursement, prevention, or outcomes unless explicitly approved. If compensation is requested but unresolved, explain the review path and expected update without implying approval. Return: subject, send-ready email, commitment audit, and facts requiring confirmation.
Im Playground ausprobieren
Standardmäßig privatDer Prompt wird lokal in deinem Browser zusammengestellt. Gib keine vertraulichen Informationen in einen KI-Dienst ein, es sei denn, deine Organisation erlaubt dies.

Von der Eingabe zum Ergebnis

Ein ausgearbeitetes Beispiel

Sieh dir an, wie konkreter Kontext dieses Rezept in ein nutzbares Ergebnis verwandelt.

Tatsächliche Eingabe

Verified incident facts
A duplicate billing job charged Northwind twice for invoice INV-2048 on 6 August. The duplicate amount was £840. Finance confirmed the duplicate; the technical cause is still under investigation. Northwind says the charge affected its available balance.
Confirmed response
Billing was paused at 10:20 BST. Finance submitted a reversal at 11:05 BST; the bank's posting time is unknown. Engineering will provide an investigation update by 8 August 16:00 BST. A service credit was requested but has not been approved; Account Operations will review it by 9 August.
Recipient and boundaries
Northwind finance manager. Calm and accountable. Sender cannot approve credits or promise bank timing. Direct replies go to billing@example.test.

Beispielausgabe

Subject: Apology and update on duplicate charge for INV-2048

Hello,

I’m sorry that invoice INV-2048 was charged twice on 6 August and that the duplicate £840 charge affected your available balance. Finance has confirmed the duplicate. We are still investigating the technical cause and will provide an update by 8 August at 16:00 BST.

We paused billing at 10:20 BST and Finance submitted a reversal at 11:05 BST. The bank controls when it appears, so I cannot yet give a posting time. Account Operations is reviewing the requested service credit and will provide its decision by 9 August; the credit is not yet approved.

Please reply to billing@example.test with questions.

Commitment audit: promises only investigation update and credit decision dates; does not promise credit approval, bank timing, or recurrence prevention. Confirm the sender name before sending.

Warum das funktioniert

  1. 1

    Separating apology from remedy authority allows accountability without unauthorized promises.

  2. 2

    A commitment audit makes operational and financial promises visible before sending.

Ergebnis prüfen

  • Does the email acknowledge the specific impact without speculating about cause?

  • Is every action, deadline, and remedy confirmed and authorized?

  • Is any unresolved compensation request described as a review rather than a promise?

Sicher nutzen

Häufig gestellte Fragen

Praktische Antworten dazu, wann du dieses Rezept verwenden solltest, was du bereitstellen solltest und wo menschliche Prüfung weiterhin wichtig ist.

What should I prepare before using “Write an apology email without unconfirmed compensation”?

For “Write an apology email without unconfirmed compensation,” prepare Verified incident facts, Confirmed response, and Recipient and boundaries. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.

When is the “Write an apology email without unconfirmed compensation” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—An accountable apology, factual update, approved next steps, and escalation path—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.

Which AI tools have recorded tests for “Write an apology email without unconfirmed compensation”?

The published test record for “Write an apology email without unconfirmed compensation” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.

Weitere Möglichkeiten zum Entdecken

Wo dieses Rezept hineinpasst

Bring die Arbeit voran