Spaces

Holiday and closure notices for software support

These notices help software publishers tell customers about holiday closures, reduced support hours and release freezes. They give clear dates and say what the agent can still help with.

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

Before you start

Software teams are often small, and holidays can leave one person covering support. Customers on a different holiday calendar will keep writing, so a clear notice avoids the feeling of being ignored. It also reduces repeat messages from people wondering if anyone is there.

Fill in the two boxes and choose the notice that fits. State the dates, what still works and when the full team returns. If you plan to freeze new releases over the break, say so, because that is a promise customers value.

Full closure

Hello from [business]. Our team is away from [dates]. I can still help with downloads, licences and common questions. For anything urgent, [urgent route]. We will reply to all other messages when we return.

Reduced hours

Hi, [business] here. From [dates] our support hours are shorter, so replies may take a little longer. I can help with most install and licence questions now, and a person will answer the rest.

Release freeze

A note from [business]: we will not ship new versions from [dates], so your current setup will stay stable. If something breaks, [urgent route], and we will check as soon as we can.

Back to normal

We are back. [business] support is fully staffed again after [dates]. Thank you for your patience. If you wrote while we were away, we are working through those chats now.

Set expectations before the break

Post the notice a week before, not on the day. Customers planning their own work, especially business users with year-end deadlines, need time to ask anything urgent before you close.

Tell the agent what it may do during the break and what it must hand over. It can still explain steps and look up licences, while refunds, security reports and lost data wait for a person.

Holiday habits that help

A few small steps before you log off prevent angry messages.

  • Update the known-issue list before the break.
  • Name one person who checks urgent chats once a day.
  • Test your download and licence systems the day before you leave.
  • Avoid shipping a risky update just before the break.

FAQ

Should I tell customers I will not ship updates over a break?

Yes, if it is true. A release freeze reassures business users that nothing will change under them, and it gives your team a real rest without surprises.

How do I handle urgent problems during a closure?

Choose a simple route, such as a keyword, and name one person who checks it. Be clear what counts as urgent, so the route is used for real problems and not for every question.

Do I need a notice for short closures?

For a single day, a short note in the agent's notes is enough. For a week or more, post a clear notice early and update it if the dates change.

More free tools for software publishers and app makers

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