Spaces

Apology replies for bugs, outages and bad updates

These apology replies help a software publisher respond to an angry customer after a bug, a bad update or an outage. They say sorry plainly, collect facts and pass the chat to a person.

Runs in your browser. Nothing you enter is sent anywhere or saved.

Before you start

Software failures feel personal. A customer loses an hour of work to a crash, or a renewal fails on the morning of a deadline, and the message that arrives is often sharp. The first reply decides whether they cool down or write a one-star review.

Choose the reply that fits and fill in the two boxes. Each one apologises for the specific problem, asks for the facts and says a person will follow up. Do not argue, explain at length or promise compensation in the first message.

Bug after an update

I am sorry about [problem]. That is not the experience we want you to have with [business]. Could you tell me your version and system? [person] will look at it with you today.

Lost work

I am really sorry about [problem], especially if it cost you work. Please do not reinstall or delete anything yet. I have passed your details to [person] at [business], who will contact you soon.

Outage or sign-in failure

Sorry about [problem]. We know it is stopping you from working. The team at [business] is on it, and [person] will post here as soon as there is news. Thank you for your patience.

Charge or renewal problem

I am sorry about [problem]. Money questions need a person to check, so I have asked [person] at [business] to look at your account. They will write to you here with an answer.

Feature removed or changed

Thanks for telling us about [problem]. I understand the change got in your way. I have noted your feedback for the [business] team, and [person] can talk through options with you.

What a good apology contains

Say sorry for the specific thing, in one sentence. Then ask for the details you need, and name a real person who will follow up. That is the whole structure, and it works because it treats the customer as a capable adult.

Leave out phrases such as we apologise for any inconvenience. They sound like a form letter, and angry customers can smell one from the first line.

Things the agent should not say

Apologies go wrong when they promise or blame.

  • Do not promise a refund, a credit or a fix date.
  • Do not suggest the customer caused the problem.
  • Do not argue about whether the bug is serious.
  • Do not paste a long list of technical steps into an angry chat.

FAQ

Should the agent offer compensation?

No. Money decisions belong to a person who can look at the account and your policy. The agent should say sorry, gather facts and name who will decide.

What if the customer is rude?

Stay calm and short. Apologise for the problem, not for the tone, and hand the chat to a person. Most customers soften once they see a real human is on it.

Can the agent apologise for a bug it cannot confirm?

Yes, it can say sorry that the customer is having trouble without saying the product is faulty. That is honest and kind, and it leaves the facts to your engineers.

More free tools for software publishers and app makers

Read the guide: Answer software customer messages before they become tickets.