VANKPA
Start a project

Website development

Write website incident updates that help customers act.

Communicate confirmed impact and available alternatives without guessing at the cause or promising an unverified recovery time.

Illustrated scene: A support team reviews an incident status display and alternative paths.

When part of a website fails, customers need to know what they can still do. A vague apology or a technical explanation may not answer that question. A useful incident message describes the affected task, the current state, and the approved alternative.

Lead with confirmed impact

State which action is unavailable or unreliable. Avoid saying the whole service is down if only one feature is affected. Equally, do not describe the issue as minor when customers cannot complete an important task.

Use a recovery time only when it has been confirmed by the responsible team. If the timing is unknown, explain when the next update is expected only if someone has agreed to provide it.

Offer a real alternative

For a hypothetical booking outage, a staffed telephone route may be useful. An unmonitored email address is not an equivalent alternative unless its limitations are clear. Confirm that the receiving team can handle the additional requests before directing customers there.

Do not tell customers to repeatedly submit a form when the outcome is uncertain. If duplicate submissions are possible, explain the safer next step and how the team will verify receipt.

Keep sensitive details controlled

Public updates should not expose credentials, customer information, or unnecessary security details. Use the incident owner's approved wording and coordinate any communication with legal or security specialists where the situation requires it.

When the service recovers, verify the affected journey before announcing resolution. Explain any remaining backlog or customer action accurately. Remove or update old notices so the website does not continue to report a resolved problem.

Prepare a short template with fields for impact, status, alternative, and update time, then test it against a realistic example. The message should reduce uncertainty and help customers choose their next action, while keeping every claim within what the team actually knows.

Plan your next step.

Explore the related serviceDiscuss your project
Help me choose