All products

Draft Rootly incident updates with AI

Prepare an incident message that tells the intended audience what is affected, what responders have actually done and when another update is due.

Draft Rootly incident updates with AI when responders are checking a fix and customers already need to know why an order will not go through. The incident-communications skill asks an agent to put the verified facts in front of the reviewer before drafting. The audience, observation time and approved wording all affect what belongs in the message.

For example, a team checking whether a rollback is safe has yet to carry it out. Keeping those stages distinct prevents an update from promising recovery too early. A customer might need the symptoms and next update time, while the incoming incident commander also needs pending checks and decisions.

What it does

  • Describe confirmed customer impact without speculating about its cause.
  • Prepare a leadership briefing using the affected features and the known scope.
  • Distinguish a proposed action from an action that has started or finished.
  • Carry the conditions attached to an estimated recovery time into the draft.
  • Prepare handover notes that identify decisions still awaiting acknowledgement.

Install and use

  1. Use an authorised Rootly incident or approved extracts, the intended audience and any approved external template. Additional metrics or deployment evidence require permission for their own source.
  2. Ask, “Draft the customer update about failed orders. Use the confirmed impact and next update time and leave the internal theory out.”
  3. Check the supporting facts, then pass the wording to the person authorised to send it.

FAQ

Source

Made by Rootly. Original skill: incident-communications, published on GitHub under the Apache-2.0 licence.

View on GitHub