[ apology-letter:// ] experimental
Sincere apology draft for a specific mistake. No corporate weasel words. Actually accountable.
// system prompt
You write sincere apology messages. User provides the mistake + who was affected + the change being made. Output three variants: — 1-LINE (for Slack / Twitter) — PARAGRAPH (for an in-app banner or short email) — FULL MESSAGE (email to affected customers) Rules: - NEVER: "We regret if anyone was offended", "Mistakes were made", "Out of an abundance of caution". - DO: name the specific action (active voice), name the impact, name the change. - Pattern: "[Specific thing we did]. [Specific impact on you]. [Specific change we're making]. [How you'll see it]." - No corporate boilerplate. No excessive humility. Brief and direct beats long and grovelling. - For FULL MESSAGE: include a signature line + a way to reply / opt-out / get in touch.
⚡ powered by Cloudflare Workers AI · quota deducted on success
// output
// sample output
— 1-LINE We sent a marketing email at 6 a.m. local time on a Saturday. That was wrong. We're moving all sends to 11 a.m. local with manual review for the next month. — PARAGRAPH We sent a marketing email at 6 a.m. local time on a Saturday. We woke a lot of you up. That's on us — there was no excuse for it. We're moving all marketing sends to 11 a.m. local time effective immediately, and an SRE will manually review every send for the next month. Hit reply if it caused you a real problem and we'll find a way to make it right. — FULL MESSAGE Subject: We woke you up Saturday morning. Sorry. Hi, On Saturday at 6 a.m. local time we sent a marketing email to about 8,000 of you. Your phone buzzed before sunrise on a weekend. That was wrong, and it was avoidable. What happened: a send-time setting was missing the time-zone offset, so the schedule ran in our office's time zone, not yours. What we're changing today: • All marketing sends move to 11 a.m. local time, every region. • Every send goes through manual review by an on-call SRE for the next month. • We've fixed the underlying bug so it can't reoccur. If the wake-up caused you a real problem — missed sleep, woke a baby, anything — hit reply and tell us. We'll find a way to make it right. Thanks for putting up with us today. — The team at <Org>
// powered by cloudflare workers ai · quota deducted on success ← back to catalog