How to use the Apology Letter Generator.
A credible apology names the action, acknowledges its effect and offers a realistic remedy. Avoid adding a defensive explanation that the facts do not support.
Make the workflow fit your task.
Name the action, acknowledge the concrete effect and offer a remedy you can deliver. Read the explanation separately to ensure it adds useful context without shifting responsibility to the recipient.
- What you provide
- Situation, responsibility and proposed remedy.
- What you get
- Specific apology without invented excuses.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
I missed our agreed review deadline; I can deliver the draft tomorrow.
Completed example
I am sorry I missed the review deadline. That delayed your planning. I will send the draft tomorrow and flag any risk earlier.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should an apology include an explanation?
Include it when it helps clarify what happened or prevent recurrence. Keep responsibility and the proposed remedy explicit.
Why does the apology sound defensive?
Remove blame-shifting phrases and conditional regret. Describe your action and its effect before discussing constraints or intentions.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑