Write a Temporary Service Outage Audio Message
Updated: Nov 8
An outage message should say what is affected, what still works and when the next update is due. If restoration is uncertain, promise only the next update you can deliver. A concise audio version can support an existing status notice or phone greeting while staff handle the incident.
Confirm the scope before writing
Ask the incident owner to provide the affected action, audience, verified workaround, time zone and next update time. Atlassian’s Statuspage documentation distinguishes incident updates from scheduled maintenance; use the distinction to avoid telling callers a surprise outage was planned. The source of truth should be a maintained incident record, not the audio file.
Avoid “all systems are down” if the fault affects only account sign-in. Avoid an unverified workaround that routes people to a channel already under pressure. If the service handles sensitive details, direct users to an approved channel and never request payment information in the recording.
Template 1 — initial outage
“Online appointment booking is currently unavailable. Existing appointments are unchanged. If you need to change a booking today, use the contact form on our website. We will post our next update at three p.m. Eastern time.” This fictional message is about 36 words, or 18 seconds at 120 words per minute before pauses. Use the real affected function and only the alternatives that have been tested.
Read any times as words and say the time zone. Put the affected action at the front so a caller can recognise it immediately. For a worldwide audience, keep the complete time conversion in the written status notice and use the most relevant market’s time zone in the recording.

Template 2 — extended outage
Online appointment booking is still unavailable. Existing appointments are unchanged. Our next update will be at [verified time and time zone]. For urgent booking changes, use [approved working channel].
Template 3 — resolved
Online appointment booking is available again. You can now make or change bookings on our website. If a previous request failed, check its status before submitting it again.
These are fictional templates. Replace every bracketed field and obtain the incident owner’s approval before recording. Keep the same voice, name files by scope and update time, and assign one person to switch the initial, extended and resolved clips. Play each version against the current written status. Add the approved audio in your own phone system or player; the voice workspace does not operate your incident channel.
FAQ
Should I say when the service will be fixed?
Only use a confirmed estimate. A firm time for the next update is clearer than a guess about restoration.
Is this the same as an on-hold script?
No. The outage message gives specific current impact and a next update; a regular hold script covers routine waiting.
Create your approved narration
Create an audio update from your verified outage script. An MP3 notice can support this task; telephony, status page and incident updates require separate handling. Review the plan and current order details before paid creation.
Related preparation
Sources and review
Reviewed 5 November 2026. Examples, scripts and timing calculations are original illustrations, not measured results or customer tests. External references inform the stated scope; they do not describe features of our workspace.
Atlassian Support — What is Statuspage?