A Customer Opens Their Package and Finds the Wrong Item

They ordered a blue ceramic vase for their mother's birthday. Inside the box: a set of silicone kitchen spatulas. They're not angry yet, but the apology email you send in the next 2 hours will determine whether they stay a customer or leave a 1-star review. And the email you'd send for this situation should sound nothing like the one you'd send for a data breach.

Every apology template on the internet uses the same formula: express empathy, take responsibility, offer a fix. That's fine as a framework. But a billing error apology and a data breach notification require completely different tones, urgency levels, and structures. Here are 7 templates built for specific situations.

Scenario 1: Data Breach Notification

Tone: Serious, transparent, zero fluff. This is a legal and trust situation. People are scared.

Subject: Security Notice: Action Required on Your [Company] Account

We're writing to inform you that on [date], we identified unauthorized access to our systems that may have affected your account information. The potentially exposed data includes [specific data types: email address, hashed password, last four digits of payment card].

Here's what we know so far. The unauthorized access occurred between [date range]. We identified the breach on [date] and closed the vulnerability within [timeframe]. We've engaged [security firm name] to conduct a full forensic investigation.

What you should do right now: Change your [Company] password at [direct link]. If you used the same password on other services, change those too. Monitor your [bank/credit card] statements for unfamiliar charges over the next 90 days.

What we're doing: We've forced a password reset for all affected accounts. We're offering 12 months of free credit monitoring through [provider] at [enrollment link]. We'll send updates every 48 hours as the investigation progresses.

I know this is unsettling. You trusted us with your information and we fell short. If you have questions, our dedicated security response team is available at [email] or [phone number] from [hours].

[CEO/CTO name and title]

Scenario 2: Billing Error

Tone: Quick, accountable, slightly casual. The customer wants their money back and a clear explanation. They don't want a paragraph about your values.

Subject: We charged you incorrectly. Here's the fix.

You were charged $[wrong amount] on [date] when it should have been $[correct amount]. We caught this on our end and a refund of $[difference] has already been submitted. It'll show on your statement within 3-5 business days depending on your bank.

What happened: [one sentence explanation, e.g., "A pricing update was applied retroactively to existing subscriptions instead of only new signups"]. We've corrected the underlying issue so it won't recur.

If the refund doesn't appear by [specific date], reply to this email and we'll escalate it with our payment processor directly. Sorry about the hassle.

Scenario 3: Extended Service Outage (4+ Hours)

Tone: Technical enough to be credible, human enough to acknowledge frustration. Time-specific.

Subject: [Service Name] is back online. Here's what happened.

[Service/Feature] was down for [X hours and Y minutes], from [start time with timezone] to [end time]. If you tried to [specific action affected, e.g., "send messages" or "process payments"] during that window, those actions failed.

The cause was [honest one-sentence explanation, e.g., "a database migration that locked a critical table longer than expected" or "a cascading failure in our payment processing queue"]. Our engineering team deployed a fix at [time] and we've been monitoring stability since.

Anything that failed during the outage: [specific recovery info, e.g., "Queued messages have been sent. Failed payments will need to be retried manually. Check your dashboard at (link) to verify."]

We know [X hours] of downtime is unacceptable for a tool you depend on. We're implementing [specific preventive measure, e.g., "staged rollouts for database migrations" or "redundant payment processing paths"] to prevent this specific failure mode from recurring.

Our status page at [link] has the full technical timeline.

Scenario 4: Lost or Damaged Shipment

Tone: Empathetic and action-oriented. Skip the corporate speak. Just fix it fast.

Subject: Your order #[number] - replacement shipping today

Your package either didn't arrive or arrived damaged, and that's on us to fix regardless of what happened in transit.

Here's what's happening right now: We're shipping a replacement today via [carrier] with [expedited/express] shipping at no cost. Your new tracking number is [number] and estimated delivery is [date].

You don't need to return the damaged item. If it arrived broken, feel free to dispose of it however you'd like.

If the replacement doesn't arrive by [date], email us back and we'll refund the full order amount immediately. No additional back-and-forth needed.

Sorry your first experience with the order went sideways.

Scenario 5: Wrong Product Sent

Tone: Lighthearted acknowledgment that this is a weird situation, but fast resolution.

Subject: That's definitely not what you ordered (fixing it now)

You ordered [correct item] and received [wrong item]. Not exactly interchangeable. We're shipping the correct item today with [express] delivery, and it should arrive by [date]. Tracking number: [number].

For the item you received: keep it, donate it, or we can send a prepaid return label if you'd prefer. Just reply and let us know. Either way, the correct item is already on its way.

We flagged your order in our warehouse system so the fulfillment team can trace where the mix-up happened. Appreciate your patience with this.

Scenario 6: Delayed Order (Shipping/Fulfillment Delay)

Tone: Honest about the timeline. No vague "shipping soon" language. Customers can handle bad news; they can't handle uncertainty.

Subject: Your order #[number] is delayed - new delivery estimate inside

Your order was supposed to arrive by [original date]. It won't make that window. The updated delivery estimate is [new date range].

The delay is caused by [honest reason: "a supplier backorder on [component]" or "higher than expected demand that exceeded our warehouse capacity" or "a carrier delay at the regional sorting facility"]. We should have flagged this sooner and we didn't.

Your options: Wait for the updated delivery at no change in cost. We've upgraded your shipping to [expedited] for free, which is reflected in the new estimate. Or cancel for a full refund, processed within 24 hours. Reply with "cancel" and we'll handle it.

We've applied a $[amount] credit to your account for the next order regardless of which option you choose.

Scenario 7: Poor Support Experience

Tone: This is the hardest one. The customer had a bad interaction with your team. Don't throw the agent under the bus. Don't be defensive. Be specific about what went wrong.

Subject: Following up on your support experience

I reviewed the conversation you had with our team on [date] and you're right that it didn't meet the standard we aim for. Specifically, [acknowledge the actual issue: "you were asked to repeat your problem three times across different agents" or "the workaround you were given didn't address your actual question" or "the tone of the response was dismissive and that's not acceptable"].

The resolution you should have received: [provide the actual correct answer or solution now]. If this is still unresolved, reply here and I'll personally see it through.

On our end, I've shared this conversation with the team as a coaching example. Not to single anyone out, but because we can't fix patterns we don't examine.

If you want to discuss this further, I'm available at [direct email or calendar link]. This isn't a form response and I'll be the one replying.

[Manager/lead name]

Using Templates Without Sounding Like Templates

The templates above are starting points. Before sending any of them, replace every bracket with real information. Add one sentence that references something specific to the customer's situation. Change the phrasing to match how your team actually talks.

If you're handling high volumes, a classification tool like Supp ($0.20 per classification) can automatically detect the scenario type and pull up the right template for your agent. That saves the 2-3 minutes per ticket of figuring out "which apology does this situation need?" and lets the agent focus on personalizing it. At 50 apology-worthy tickets per month, that's $10 in classification costs versus 2.5 hours of agent decision time.

The worst apology email is one that sounds like it was written for a different situation. A customer who received the wrong product doesn't need four paragraphs about your company values. A customer whose data was breached doesn't want a lighthearted tone. Match the severity, be specific, and fix the problem.