Spaces

Apology replies for bugs, outages and billing mistakes at your software company

These apology replies help a software company respond calmly to a user who is upset about a bug, an outage or a billing error, before a person on the team takes over.

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

Before you start

Users get angry at software for good reasons: lost work, a broken export, a charge they did not expect. The first reply matters more than the fix. A user who feels listened to will wait for a solution. A user who gets a canned line will tell their team to switch.

Fill in the name of the person who will follow up and how quickly they will reply. Each message below is a calm first response, not the final answer. For billing and data problems, a person should always take over and decide on any refund or credit.

Bug or error

I am sorry about this, I know it is getting in your way. I have passed the details to our team at [business], and [owner name] will reply [follow up time] with what we found.

Outage

I am sorry, and thank you for telling us. We know about the problem and the team at [business] is working on it. [owner name] will write to you [follow up time] with an update.

Wrong charge

I am sorry about the charge, that should not have happened, and I understand why you are upset. I have asked [owner name] to look at your invoice, and they will reply [follow up time].

Lost or missing data

I am sorry, I know how worrying this is. I have marked it as urgent for [business]. [owner name] will take this personally and contact you [follow up time]. Please avoid changing anything for now.

An apology has three parts

A good apology says sorry once, names the problem in the user's own words and says what happens next. That is all. Avoid long explanations, excuses or technical detail in the first message. People want to know someone has picked it up.

Do not promise a fix, a refund or a credit in the first reply. Those decisions belong to a person. The agent's job is to calm the moment and hand over cleanly, with a short note so the user does not have to explain everything again.

  • Say sorry once, not three times.
  • Use the user's words for the problem.
  • Name a person and a time for the next message.

FAQ

Should an AI agent apologise at all?

Yes, a short and sincere apology is fine and helps. The agent should then hand the chat to a person, especially when money, lost data or a long outage is involved.

Should we offer a refund in the first reply?

Usually not. Acknowledge the problem first, and let a person decide on any refund or credit once they have seen the facts. This keeps your decisions fair and consistent.

What if the user is rude?

Stay calm and kind, and hand over to a person. Rudeness often comes from lost work or a missed deadline. A steady human reply usually turns the conversation around.

More free tools for software companies

Read the guide: Answer your users' messages with an AI agent.