The client-facing message says there is a technical issue and the team is working hard. The client still does not know whether to resend its request, delay a meeting or contact somebody else.
A service-disruption update should explain the known effect, what the business is doing, what the client should do and when the next update is due. Keep a forecast separate from a confirmed recovery, and do not fill missing evidence with a reassuring promise.
Photo by Vitaly Gariev on Unsplash.
Say what is affected in the client’s terms
Describe the unavailable service or delayed outcome, not an internal component the client cannot interpret. Limit the statement to what is known. If some cases remain under review, say so rather than implying the interruption affects everyone.
Atlassian's incident-communication templates provide examples of acknowledging an issue and issuing updates. The small-service message structure below is an editorial recommendation, not a requirement to adopt an enterprise incident platform.
A message structure to adapt
Current position: the service or outcome affected.
Known scope: who or what is affected, with any uncertainty.
Action: the investigation or approved workaround underway.
Client step: wait, use an approved alternative or provide a specific input.
Next update: a realistic time and communication channel.
Contact route: where urgent relevant questions should go.
Ask an appropriate owner to check the wording before sending. Consequential statements about data, liability or technical safety need the relevant authorised review rather than an optimistic generalisation.
An illustrative client-report delay
A service firm cannot produce several scheduled reporting packs. Its message identifies the affected pack, confirms that the delivery owner is reviewing an alternative and asks the client not to send duplicate requests.
The next update is promised at an owned time. The team does not announce a recovery deadline until it has evidence and authority to do so. If the update time arrives without a solution, it communicates the current position rather than remaining silent.
Keep one current message across channels
Link internal staff to the approved update and note who can amend it. If a phone conversation gives a client a different commitment, record and reconcile it. The authoritative-record principle applies to the current incident position too.
Separate general information from client-specific decisions. Your escalation route should handle a case whose impact needs a different response, without asking every customer to repeat the same problem.
Close with the remaining action
When service resumes, state what has been restored and what clients should check or expect next. If a backlog remains, do not imply every delayed output is already complete. Carry unresolved cases into normal delivery with named owners.
If disruption messages create more questions than they answer, Hili Consulting can help connect incident facts, authority and client communication.
