Spaces

Delay and outage notices for support teams

This tool writes honest notices for customers asking about delays, faults or outages, with the cause and your next update time filled in. It is for support teams under pressure.

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

Before you start

When something breaks, support is the first to feel it. Customers write in asking what happened and when it will be fixed. Silence makes people assume the worst, while a calm honest notice, even without an answer, gives them something to hold on to.

Say what you know in one short line and when you will update next. Choose the message for a delivery delay, an outage, a stock problem or a repair taking longer. Keep to the facts, avoid blame and only promise a time you are sure you can meet.

Delivery delayed

I am sorry, but your order from [business] is running late because of [what happened]. We are working to get it moving, and I will send you a new update [next update].

Service outage

Thank you for letting us know. We can confirm there is a problem at [business]: [what happened]. Our team is on it. We will update you here [next update], so you do not need to keep checking.

Item out of stock

I am sorry, the item you asked about is out of stock at [business] because of [what happened]. I will tell you [next update] what we can offer instead, and you can choose what suits you.

Repair taking longer

Thank you for your patience. Your repair is taking longer than we said, because of [what happened]. That is our responsibility, and we will give you a firm update [next update].

Tell people what you know

In a bad moment, honesty is the whole job. Say what you know, say what you do not know yet and say when you will speak again. Customers will accept bad news far better than a vague, everything is fine.

Use the same wording across all your channels, so a customer does not get one story from chat and another from your site. An agent can pass the notice to everyone who writes in, as long as you keep it up to date.

  • Keep the notice to three short lines.
  • Do not blame a supplier or a customer.
  • Update on time even if nothing has changed.
  • Hand compensation requests to a person.

FAQ

Should I explain the cause of a delay?

Briefly and in plain words, yes. A short honest reason feels respectful. Avoid blaming others or giving details you are not sure of, since facts can change as you learn more.

How often should I update customers in an outage?

At the time you promised, and then at regular times until it is fixed. Even a no change yet note is useful, because silence is what makes customers anxious.

What if customers ask for compensation?

Thank them, say a person will look at it fairly and pass the chat on. Do not promise anything until someone with authority has decided what you can offer.

More free tools for customer support teams

Read the guide: Answer support messages with an AI agent.