Spaces

Get your user messages ready for a launch, an outage or a year-end rush

This checklist helps a software company prepare its user messages for the busiest moments: a product launch, a price change, a renewal wave or an incident. It covers answers, staffing and hand-overs.

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

Before you start

Software has its own rush hours. A launch day brings a flood of curious questions. A price change brings worried ones. The end of a quarter brings renewals and invoice questions. An outage brings every user at once. You can see most of these coming, so prepare for them.

Pick the event you are preparing for and walk through the list a week ahead. Write the new answers, check who is on call and tell your agent what has changed. Keep the checklist and reuse it for the next event.

Tick each one as you go. 0 of 10 done.

[ ] Write down what is changing and the date, in plain words users would use.
[ ] Draft answers for the five questions users will ask first.
[ ] Update the pricing, plan and trial answers before the change goes live.
[ ] Decide who is on call for hand-overs, including the weekend.
[ ] Prepare a short notice for an incident, with a place to link to updates.
[ ] Tell your agent which topics are sensitive this time, such as a price rise.
[ ] Check your status page link and help articles work.
[ ] Plan extra time to read chats during the first two days.
[ ] Set a rule for what to do when a bug report arrives twice in an hour.
[ ] Afterwards, review the chats and keep the best new answers.

Three moments to plan for

A launch is about curiosity: what is new, who gets it, is it included in my plan. A price change is about fairness: why, when, what happens to my current price. An incident is about trust: what happened, is my data safe, when is it fixed.

Each calls for a different voice. Be cheerful about launches, clear and respectful about price changes, and plain and honest during an incident. Never promise a fix time you cannot control.

  • Launch: keep answers short and link to the announcement.
  • Price change: let a person handle anyone upset about their bill.
  • Incident: say what you know, what you do not, and when you will update.

FAQ

How early should we prepare for a launch?

A week ahead is a good rule. That gives you time to write answers, test them on a few example questions, and make sure your team knows who handles which hand-overs.

What should the agent say during an outage?

It should acknowledge the problem, point to your status page, and promise only what you know. A person should take any message about lost data or business impact.

Do we need more staff when messages spike?

Not always. Good ready answers cut the load, but keep at least one person ready for hand-overs on the days that matter. Plan their schedule before the event.

More free tools for software companies

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