Spaces

Delay and change notices for software customers

These delay and change notices help software publishers tell customers about a late release, a changed feature or an outage. They are for customers who asked, bought or are waiting for news.

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

Before you start

Software schedules slip. A release planned for Tuesday lands on Friday, a feature is cut or a new version drops support for an older system. Customers who are waiting get frustrated when they find out through a forum instead of from you.

Fill in the two boxes and choose the notice that fits. Say what changed, why in a sentence and what the customer can do. Share only dates you are sure of, and avoid hiding bad news in cheerful language.

Release delayed

Hello from [business]. A quick update for those waiting: [change]. We would rather ship it properly than quickly. Meanwhile you can [alternative]. Ask here if you have any questions.

Feature changed or removed

Hi, [business] here. We want to let you know that [change]. We know this may affect how you work. For now, you can [alternative], and a person can talk it through with you.

Old system no longer supported

Hello, [business] writing to you because you asked about your system. [change]. For now you can [alternative]. If you tell me your setup, I can explain what applies to you.

Outage or sign-in problem

Hi from [business]. We are aware that [change], and our engineers are working on it. In the meantime you can [alternative]. We will post here as soon as it is resolved.

Say it early, and say it plainly

Customers can cope with a delay if they hear it early. What damages trust is silence followed by a surprise. A short, honest note with a new date, even if the date is approximate, calms most of the worry.

Explain the reason in one sentence, not a paragraph. Say sorry once. Then give the customer something they can do today, so the notice is useful and not just an announcement.

Notices to send only on request

Keep this to people who are waiting for news.

  • Customers who asked when a feature would ship.
  • Buyers who purchased a pre-order or a pending upgrade.
  • Users with an open support chat about the affected version.
  • People who asked to be told about the outage.

FAQ

Should I give a new date if I am not sure?

Give a range or say when you will next update. A wrong firm date harms trust more than an honest we will tell you by Friday, which gives people something real to plan around.

Do I need to tell everyone about a small bug?

No, just those who are affected or have asked. A short known-issue note for the agent covers most cases, and you can reply to individual customers who raise it.

What about refunds when a release is late?

The agent should explain your policy and pass any request to a person. It should not offer or refuse a refund on its own, since the answer depends on what the customer paid for.

More free tools for software publishers and app makers

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