What should a website say when a service is temporarily unavailable?

Put the status where people make the decision

When a service is unavailable, visitors should not have to discover it after completing a form or choosing a time. Place the message on the relevant service page, booking step and other high-intent routes. If the change affects the whole business, use the home page and contact page as well, but keep the detailed explanation close to the affected service.

Start with a direct sentence: “New installation appointments are temporarily unavailable.” Avoid soft wording that makes people guess whether the service still exists. Include the date or time the status began when it helps explain the situation.

A clear status is not an admission of failure. It is a way to prevent wasted effort and show that the business is managing expectations.

Explain the reason without creating noise

People need enough context to decide what to do. The reason might be staff capacity, a supplier delay, a safety review or a temporary technical problem. Use plain language and disclose only what is useful and appropriate. Internal blame, uncertain speculation and sensitive operational detail rarely help a visitor.

Do not say “back soon” if nobody knows what that means. If the duration is unknown, say so honestly: “We do not yet have a reliable reopening date.” This is more credible than a date that changes repeatedly. If there is a condition, explain it: “We will update this page after the next supplier confirmation.”

Keep the message accessible. Use a heading, short paragraphs and strong contrast. Do not rely on colour alone or hide the status in a rotating banner that disappears before someone can read it.

Give people a useful next step

An unavailable service does not always mean there is nothing to offer. Suggest a related service, a waiting list, an alternative location, a trusted partner or a future notification. Make sure the alternative is real and that staff know how to handle the resulting contact.

If people can ask a question, provide a form, phone route or shared inbox. Tell them what to include so the team can respond efficiently. If the service is unavailable only for new customers, say whether existing customers have a different route.

Do not keep a normal booking button active below a warning unless the button truly works for an accepted alternative. A contradiction between message and action damages trust more than a temporary closure does.

Set the next update carefully

A next update is not always a reopening date. It can be a date when the business will review the situation, receive information or publish a new status. Choose a time the owner can meet. “We will update this page by Friday” is useful only if someone is responsible for checking it.

Use an absolute date rather than “next week”. When the page is reused across languages or time zones, include enough context to avoid confusion. If no date is possible, explain what event will trigger the next update.

Do not ask visitors to keep refreshing the page without giving them a way to hear from the business. A notification list or direct contact can help, but only collect details for a clear purpose and explain the choice.

Coordinate the message with real operations

Update the systems that create customer expectations: booking tools, product listings, staff scripts, advertisements, social profiles and automated emails. A service page saying “unavailable” is not enough if the booking calendar still offers times.

Give staff a short answer they can reuse. It should match the website and say what alternative to offer. Check forms and integrations so enquiries are not routed to an absent team. If the business uses analytics, mark the change so a later traffic or conversion shift has context.

Assign one owner for the status message and one backup. Store the reason, start date, next review and return condition in an internal note. This prevents a temporary notice from becoming a permanent part of the site.

Close the loop when availability returns

The return is also a communication moment. Tell staff which message to use, check that the alternative is removed, and confirm that the team can answer questions about the restored service. This prevents the website from saying one thing while a confirmation email or calendar still says another.

Use the reopening to check the complete customer promise. A restored button should lead to a working page, a restored booking option should create the expected record, and a restored payment path should end with a reliable confirmation. If any part remains limited, say so next to the action instead of hiding the limitation in a general notice. This final check protects trust after the technical issue has ended.

Remove the warning promptly when the service returns, but check the full journey first. Test booking, payment, contact, confirmation and staff visibility. If availability returns with limits, replace the old message with the new conditions instead of simply deleting it.

Consider a short update for people who contacted the business during the interruption. Do not promise to contact everyone if that is not possible, but give the team a method for following up where it is appropriate.

Review what the interruption taught you. Were visitors confused about alternatives? Did staff receive repeated questions? The next status message can be clearer because the business has learned where the information gap was. Record those lessons with the owner and review date so the next update is not written from memory. A short incident note can also show which links, forms and automated messages need checking first.

Sources

• Error Messages · Nielsen Norman Group
• Status Messages · W3C
• Helpful content · Google Search Central

Frequently asked

Should we explain exactly why a service is unavailable?

Explain the reason when it helps visitors decide, but avoid speculation, blame or sensitive internal detail. Accuracy and usefulness matter more than a long story.

What if we do not know when the service returns?

Say that the date is unknown and name the next review or event that will produce an update. Do not invent a reopening date.

Should the unavailable page remain indexed?

Usually keep a useful, updated service page so existing links have somewhere accurate to go. Avoid thin or contradictory pages, and update the page when availability changes.