Spaces

Holiday and closure notices for users of your software company

These notices tell software users about team holidays, reduced support, planned maintenance and year-end changes, with your dates filled in and a clear way to reach you if it is urgent.

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

Before you start

Software never fully closes, but your team does. Holidays, company retreats and planned maintenance all change what users can expect. A short, clear notice before the date prevents a pile of 'are you there?' messages, and shows users you plan ahead.

Enter the dates when support is slower and where urgent issues should go. Post the notice on your site, and let your agent use it when someone writes during those days. Remember to remove or update it afterwards so it does not go stale.

Team holiday

Thanks for writing to [business]. Our team is on a break from [dates], so replies will be slower than usual. Your message is saved and we will answer as soon as we are back.

Urgent during a break

Our team at [business] is away from [dates]. If something is badly broken, check [urgent route]. For anything else, leave your message here and we will reply when we return.

Planned maintenance

A heads-up for [business] users: we are doing planned maintenance during [dates]. The product may be unavailable for short periods. We will post updates at [urgent route].

Back from a break

We are back at [business] after our break, and working through the messages that came in during [dates]. Thank you for waiting. We will reply to yours as quickly as we can.

Say it early, say it once

Tell users a week before, and again on the first day of the break. Give exact dates, not 'over the holidays', and say what still works, such as your status page and help articles.

Decide who is on call for real emergencies, even on a skeleton team. A user with lost data on Christmas Eve will remember how you handled it for years.

  • Give exact dates and time zone.
  • Say what still works while you are away.
  • Name the route for real emergencies.

FAQ

Should the agent keep answering during our break?

It can answer how-to questions and share your notice. Anything about money, security or lost data should be held for a person, or sent to your on-call route if urgent.

How far ahead should we announce a break?

About a week is good, with a reminder on the first day. Planned maintenance deserves a little more notice, especially if the product will be unavailable for a period.

Do we need a notice if support is only slightly slower?

A short line is still worthwhile. Users are patient when they know why, and a single sentence at the start of the chat can save you many repeated questions.

More free tools for software companies

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