Spaces

Apology replies for hosting outages and processing errors

These apology replies give hosting and data processing companies calm, honest wording for customers upset by an outage, slow site or failed run. Fill in two details, copy one and let a person follow up.

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

Before you start

When a site goes down, customers lose sales and sleep. They are not looking for a long explanation first. They want to feel heard, to know someone is working and to hear the truth about what happened. An apology that is plain and specific works far better than a polished one.

Add what went wrong and the next update time below, then choose the message that fits. These replies are the start of the conversation, and a person on your team should take over for anything involving compensation, lost data or contract terms.

Outage that is ongoing

I am very sorry from [business]. We know about [problem], and our engineers are working on it now. We will send you the next update by [update], even if it is only to say we are still on it.

Outage that is fixed

Hello from [business]. I am sorry about [problem]. It is fixed now. Please check your site and tell me if anything still looks wrong, and a person on our team will look at it today.

Failed processing run

This is [business]. I am sorry that [problem]. We are rerunning your file now, and I will update you by [update]. A person from our team will contact you about any knock-on effect.

Slow service complaint

Thank you for telling us, and sorry for the trouble from [business]. We are looking into [problem]. A person on our team will come back to you by [update] with what we found.

What a good apology holds

A good apology names the problem, says what you are doing and gives a time for the next update. It does not make excuses, blame the customer or promise a cause before engineers know it. If the cause is on your side, say so.

Compensation, credits and contract questions belong to a person. The agent can say that someone will talk about it, without offering anything on your behalf.

  • Say sorry once, clearly, then move on to what you are doing.
  • Give the time of the next update and keep to it.
  • Do not copy and paste a message that mentions the wrong fault.

FAQ

Should I offer a credit in the first reply?

No. Let a person decide after the facts are known. The first reply should show you care and are fixing the problem, and then the owner can discuss anything further.

What if I do not yet know the cause?

Say so honestly and give the time of your next update. Customers handle I do not know yet much better than a guess that turns out to be wrong.

How do I reply to an angry customer?

Stay calm, acknowledge the cost to them, avoid defending yourself and move the chat to a person quickly. A human voice usually softens the mood faster than any wording.

More free tools for web hosting and data processing companies

Read the guide: Answer hosting and data processing questions without a ticket queue.