Spaces

Getting your support chats ready for a software release

This checklist helps software publishers prepare their customer chats before a major release, upgrade or seasonal sale. It covers release notes, known issues and who is on call when messages spike.

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

Before you start

For a software publisher, the busy time is not a season but a release day. Within hours of a new version, the chat fills with install problems, questions about changed features and people asking whether their old licence still works. A prepared team handles it. An unprepared one drowns.

Use this list in the week before a release, a major upgrade or a seasonal sale. Tick each item, and give the finished list to whoever updates your agent's notes. Most of the work is writing things down before the first customer asks.

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

[ ] Write the release notes in plain words for the agent, not only for developers.
[ ] List every change that might confuse an existing user.
[ ] Say clearly whether old licences work with the new version.
[ ] Write the upgrade price rules and who may apply for them.
[ ] Test the install on each supported system and note any quirks.
[ ] Add a placeholder entry for known issues and update it hourly.
[ ] Plan who covers hand-overs during the first forty-eight hours.
[ ] Check that download pages and licence emails are working.
[ ] Prepare a short notice for a server or sign-in outage.
[ ] Schedule a review of the chats on day three.

The first six hours after launch

Expect install problems first, then licence questions, then feature confusion. Stay close to the chat during this time and be ready to add a known issue within minutes of a pattern appearing.

If your team is small, ask the agent to handle the first replies and keep one engineer reading what it passes on. That keeps the people who can fix bugs from being buried in simple how-to questions.

Quiet weeks matter too

Between releases, use the calm to improve your notes.

  • Move this release's answers into your permanent notes.
  • Remove known issues that were fixed.
  • Note which questions surprised you, and write a clearer help page.
  • Rehearse the hand-over rules with a colleague.

FAQ

How early should I prepare the agent for a release?

About a week before, so you have time to test it with questions about the new version. Last-minute notes written on launch day often miss obvious customer questions.

Should I switch the agent off if the release goes badly?

No, but update its notes at once with the current problem and workaround. A calm, accurate reply helps more than silence, and people stay informed while you fix things.

What about sales and discount periods?

Write down the dates, the rules and who can approve exceptions. The agent can explain the offer and take questions, and a person decides anything outside the written rules.

More free tools for software publishers and app makers

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