Spaces

Delay and change notices for users when a fix, feature or access slips

These notices help a software company tell a user about a late fix, a changed feature or something unavailable, honestly and without false promises, to people who asked about it.

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

Before you start

Software teams slip dates. A bug fix takes longer, a feature changes shape, an integration is paused. The user who asked about it is waiting, and the worst thing you can do is say nothing. A short, honest notice shows respect and often earns more patience than you expect.

Fill in what is delayed and when you will next update them. Send these to users who asked about the item or reported the problem, not to your whole list. Do not promise a new date unless you are quite sure, and say clearly what the user can do in the meantime.

Fix is taking longer

A quick update from [business]: the work on [item] is taking longer than we hoped. I do not want to give you a date I cannot keep. We will write again [next update].

Feature changed

You asked about [item], so I wanted you to hear this from us first. We have changed how it works at [business]. I can explain what is different and how it affects you, if you like.

Temporarily unavailable

Just to let you know, [item] is switched off for now while we make improvements. Sorry for the trouble. We will tell you here [next update], and I can suggest a workaround today.

Cannot do it

I looked into [item] for you, and I am sorry to say we cannot offer it right now. I would rather tell you straight than keep you waiting. Here is what I can do instead for [business] users.

Bad news, told early

Bad news does not improve with age. Tell the user as soon as you know, say what has changed and explain what they can do now. Offer a workaround where there is one, even if it is clumsy.

Avoid soft promises like 'soon' or 'in the next release'. If you do not have a date, say so, and name the day you will next update them. Then do it, even if the news is still no news.

  • Say what changed in one sentence.
  • Offer a workaround when you have one.
  • Name the day of the next update and keep to it.

FAQ

Should we give a new date for a late fix?

Only if you are fairly sure of it. A second missed date does more harm than the first. If unsure, promise an update on a given day instead of a fix on a given day.

Who should receive a delay notice?

People who asked about the item or reported the problem. Do not message users who never raised it, as that creates worry about something they did not know about.

Can the agent send these without a person checking?

It can pass on facts your team has confirmed. A person should write or check any notice about lost data, a security issue or a change that affects what customers pay.

More free tools for software companies

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