Service communication
Write an outage status update customers can understand
A repeatable structure for outage updates that states the impact, the known facts, the next update time, and the action customers should take.
Start with repeatable IT work that has a clear owner, clear access limits, and a review cadence. Keep risky technical decisions with the manager or provider who owns the system.
Delegation playbook
On this pageJump to section
During an outage, customers do not need a full incident report. They need to know whether the problem affects them, what they should do right now, and when they will hear more. A status update that leads with those answers reduces repeat contacts and gives the support team a single approved message. The structure below can be reused for a payment failure, a login problem, or a scheduled service that stopped responding.
Lead with what is affected
Open with the service and the customer action that is failing, such as signing in, uploading a file, or receiving a confirmation email. Avoid a headline that says the team is aware of an issue without naming the issue. A reader should be able to decide in one line whether the outage explains their problem. If the scope is still unknown, say which services are confirmed and which are still being checked.
State the start time in the customer's time zone and say whether the impact is partial or complete. Name the regions or plans that are affected if the service has them. A precise scope prevents customers in unaffected areas from opening a ticket. Update the scope as soon as the team learns more rather than waiting for a complete picture.
Say what you know and what you do not
Separate confirmed facts from working theories with plain labels. A sentence such as we have confirmed the failure is in the login service is different from we are investigating whether a recent change caused it. Customers can tolerate uncertainty when it is named. They lose confidence when an early guess is presented as a fact and then reversed.
Avoid internal jargon, vendor blame, and speculation about cause while the incident is active. Give the next update time instead of estimating a fix that the team cannot yet support. If a workaround exists, put it before the explanation. The update should help the reader act, not demonstrate how much the team knows.
Give a time you can defend
Promise the next update, not a resolution, when the fix is still uncertain. A specific time such as the next update at 14:30 gives customers a reason to check back instead of calling. Choose an interval the team can meet even during a difficult incident. A missed update time damages trust more than a longer interval announced in advance.
When the team can give an estimated restoration time, label it as an estimate and explain what must happen first. Do not repeat the same estimate after it has passed. Publish a revised time with the reason for the change, even if the reason is still under investigation. Customers plan around the most recent number they saw.
Keep one update thread
Use one status page entry, one email thread, and one pinned chat message, and link the others to the canonical version. Post every update to the same place so a customer who returns later can read the sequence. Number the updates or add a timestamp in the heading. A thread that restarts with each shift loses the history customers need.
Give the support team the approved text before it is published so their replies match the status page. Tell them which questions to route to the incident owner and which they can answer directly. If a customer reports a different symptom, record it as a separate signal rather than dismissing it. The support queue is often the first place a new symptom appears.
Write for the reader who is not technical
Replace terms such as latency, failover, and database replica with the effect the customer experiences. Say the dashboard is slow to load rather than describing a query queue. Keep sentences short and put the action in its own line. A customer reading on a phone during a workday should not have to parse the architecture.
Ask someone outside the technical team to read the draft before it is published. If they cannot explain the impact back to you, rewrite the opening. Check that links work on a phone and that the status page loads without the affected service. A notice hosted on the system that is down is not a notice.
Keep a record of what customers were told
Save every published update in the incident record with the time it was sent and the channel it used. Note which customer groups received it and whether any group was left out. The record is the only way to answer a question about what was promised three weeks later. A screenshot of the status page is useful, but the text and timestamp are what an account manager needs.
Compare the customer-facing record with the internal incident log after the outage. If an internal update was never published, note why and whether customers were waiting on information the team already had. Use the gap to improve the next notice rather than to assign blame. The record also gives the support team a consistent answer when a customer asks for a timeline.
Review the updates after the incident
Collect every update in one document and compare the first estimate with the actual timeline. Note where the scope changed, where the update time slipped, and which questions the support team received most. Ask two customers or account managers which message was clearest. The review is about the communication, not only the technical cause.
Turn the findings into a short template with approved openings for confirmed, partial, and unknown scope. Add the next update time and the support routing to the template. Assign one owner to keep it current. The next incident should start with a tested message rather than a blank page.
Sources and next step
Use the CISA Cross-Sector Cybersecurity Performance Goals and the NIST Cybersecurity Framework 2.0 as primary references for the helpdesk intake, change communication, asset return, outage update, and patch pilot practices discussed in these guides. The NIST patch management planning guidance supports the pilot hold and stop-signal steps, and NIST configuration management guidance supports the equipment and deployment records. Apply your own policies, contracts, and system documentation to the workflow. Compare this guide with the contractor equipment return checklist and the outage status update guide before changing a live process.
Keep decisions, approvals, and evidence in systems the business already controls. If the coordination is recurring and your technical owner can define the boundaries, review the IT virtual assistant service areas and contact ITVirtualAssistant to discuss a limited pilot.
Operating brief
What this guide should help you decide
Routine intake, status updates, records, screenshots, and documentation upkeep.
Approvals, risky system changes, security decisions, and final technical judgment.
How to use this guide
Use this page to decide what an IT virtual assistant should handle first. If the task is recurring, documented, and easy to review, it is usually a better first delegation candidate than work that requires live technical judgment.
Treat the article as an operating brief, not just a topic overview. The goal is to turn loose IT work into a named workflow with inputs, outputs, permissions, review cadence, and a handoff rule that protects the business while reducing manager load.
Workflow
Recommended operating workflow
Define the request
Write what write an outage status update customers can understand means in your company, where requests enter, and what finished work looks like.
Limit the access
Give the assistant only the tool permissions needed for intake, records, status updates, or documentation.
Run a pilot
Use a two-week sample period so the manager can review accuracy before expanding the workflow.
Review patterns
Summarize repeat issues, blocked requests, and escalation volume so the technical owner can improve the process.
Decision rules
| Question | VA fit signal | Escalate when |
|---|---|---|
| Is the work repeatable? | The same request appears weekly and can be described in steps. | The request changes business policy or system design. |
| Can quality be reviewed? | The manager can inspect the output without redoing the work. | Only a senior technical person can judge correctness. |
| Is access contained? | The assistant can work with read-only or role-limited access. | Admin rights, customer data, or security settings are involved. |
Delegation checklist
- Write the intake source, expected output, and manager review cadence.
- Confirm the assistant has only the permissions needed for the workflow.
- List the events that require escalation before work continues.
- Track examples for two weeks before changing the workflow.
- Save examples of good and bad outputs so the assistant has concrete references.
- Review the workflow monthly and remove permissions that are no longer needed.
Example first-week agenda
Day one should cover the workflow owner, tools, allowed actions, forbidden actions, and escalation language. By the end of week one, the assistant should have produced a small sample of completed work, a list of unclear requests, and a manager-reviewed improvement note.
What to review before delegating
Confirm the owner, access level, review cadence, and escalation path before assigning any recurring IT workflow to a remote assistant.
What should an IT virtual assistant handle first?
Start with repeatable, reviewable work such as ticket summaries, account records, documentation updates, and checklist follow up.
Get free IT support review