“We’ll be back soon” tells a customer very little when they are halfway through an order. A useful maintenance notice answers the question that brought them to the site: what can they do now, and when should they check again?
Name the affected service
Say whether the whole website, checkout, account area or a particular feature is unavailable. If browsing still works but payments do not, make that distinction clear. Avoid describing internal server components when the customer needs to know whether an order can be completed.
Give the planned window with a date and time zone. For an international audience, an unqualified “tonight” can refer to different days. If the finish time is uncertain, state when you will provide the next update instead of turning an estimate into a promise.
A short example
Checkout will be unavailable on 12 November from 02:00 to 03:00 UTC while we carry out planned maintenance. Product browsing will remain available. We will update this notice by 03:00 UTC if checkout has not reopened.
This is an invented example. Replace every detail with your confirmed operating plan, including what happens to an in-progress transaction. Do not claim that a cart or payment is preserved unless that behaviour has been checked.
Provide a working support route that does not depend on the unavailable feature. If an alternative order method exists, explain its limitations and keep payment information within the approved process.
- Assign someone to publish and remove the notice.
- Check the message on mobile.
- Test the support link before maintenance begins.
- Keep a dated update if the window changes.
After restoration, verify the customer task before announcing completion. A homepage loading successfully does not prove checkout works. Remove stale banners and publish a brief completion update where people were told to look. The notice should close the communication loop as carefully as it opened it.