How to use the Service Outage Email Generator.
An outage message should distinguish known facts from investigation. Promise an update time only when the team can meet it.
Make the workflow fit your task.
State the affected function and known customer impact, separating confirmed facts from investigation. Include a verified workaround or next-update time only when the team can support it, then revise as evidence changes.
- What you provide
- Known incident facts and update schedule.
- What you get
- Transparent status message without unsupported resolution promises.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Exports are failing; engineers are investigating; next update at 16:00 UTC.
Completed example
Exports are currently unavailable. The team is investigating. We will share the next update at 16:00 UTC.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should an outage message give an estimated fix time immediately?
Provide one only when the responsible team has a defensible estimate. A clear next-update commitment may be more appropriate during investigation.
Why did the message create a promise the team cannot keep?
Remove speculative resolution timing and align updates with the incident owner's confirmed information.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑