Spaces

Holiday and closure notices for software and IT firms

These notices help a software or IT firm tell clients about holiday closures, reduced support hours and code freeze periods. Fill in your dates and cover details, then copy a message.

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

Before you start

Clients plan their releases and their own busy periods around yours. If your firm quietly closes for a week and a client discovers it when something breaks, you have a problem. A short, clear notice that says what is covered and what is not is a courtesy that pays back many times.

Fill in the boxes below, then pick the message that fits. Be exact about dates and about what cover exists. These are for clients who write to you or who asked to hear from you, not for mass broadcasts to people who have never contacted you.

Full holiday closure

A note from [business]. We are closed [dates]. During that time, we offer [cover]. Ordinary requests will be answered when we return. Thank you for your understanding, and happy holidays.

Reduced hours

Please note that [business] will run reduced hours [dates]. Support is limited to [cover]. If you have a release planned in that period, tell us now, so we can plan together.

Code freeze before a busy period

A heads up from [business]. We pause non-urgent changes [dates], so systems stay steady. Cover during the freeze is [cover]. Please send any requests you need before then.

Client asks if you are open over the holiday

Thanks for asking. [business] is closed [dates], with [cover]. If you expect to need help in that window, tell us the date and we will make sure someone is ready.

Back and catching up

We are back at [business] after [dates]. Thank you for waiting. We are working through the messages in the order they arrived, and urgent ones come first. Write again if yours is time sensitive.

Give notice twice

A notice a few weeks before gives clients time to plan. A short reminder a few days before catches the ones who missed it. After that, your agent can answer anyone who writes, using the same dates.

Make sure the same dates are in your agent's instructions, your out-of-hours reply and your auto-reply. Three different dates is a fast way to confuse a client.

What a good notice includes

Say all of this in a few lines.

  • The first and last day of the closure or reduced service.
  • What cover exists, and how to reach it.
  • What kinds of request will wait until you return.
  • A friendly line, so it does not sound like a warning.

FAQ

Do we need to tell every client about a closure?

Tell the ones with open projects or support contracts, in the chats they started, and answer anyone who writes. Do not message people who have never contacted you.

What if a fault happens during the closure?

Your notice should say how to reach urgent cover. If there is none, say so honestly, so clients can plan around it and keep their own backups ready.

Should we announce a code freeze?

Yes, if it affects clients, because they may have changes they want in before it. Say the dates clearly and what counts as an urgent exception.

More free tools for software and tech support firms

Read the guide: Answer client messages at your software and IT firm, from outages to scoping.