Incident timeline updates

An incident timeline is the running public record of an outage, from first report through resolution. When monitoring flags a degradation, a Beam agent opens or updates the matching incident, reads which components are affected, and adds a progress note in the wording your team approved for that severity. It shifts the incident state as conditions change and marks it resolved once signals recover. Cases that look unclear, such as conflicting alerts or an outage touching billing, pause for a person to confirm the customer message before it goes out.

Component status changes

Each service you display carries a status, from operational to major outage. A Beam agent reads health checks arriving from your monitoring, and when a metric crosses a threshold your team set, it moves the affected component to the matching status so the public page reflects reality. It reverts the component once readings hold steady for the agreed window. Where a single check disagrees with the others, or a component underpins a customer commitment, the agent leaves the current status in place and asks an engineer to decide what to show.

Subscriber notifications

Subscribers ask to hear about incidents by email, text, or webhook. When an incident reaches a stage your policy names as notify-worthy, a Beam agent drafts the update from your approved templates, attaches the affected components, and releases the notice to the relevant subscriber groups. It records which stage prompted each message so the history stays clean. Messages that carry legal or contractual weight, like a breach notice or a paid-tier commitment, wait for a named approver before anything leaves the system, so customers only ever receive language a person has read.