Topic · 3 features
Incident communication
Incident communication is how you tell customers what is wrong, what you are doing about it and when it is over. Autessa Status Page makes it three moves: report it, update it, resolve it.
In short
Autessa Status Page turns incident communication into three moves: report it, post updates, resolve it, with component status kept in step automatically.
Autessa Status Page includes incident communication from a staff console. Reporting an incident takes one form, with a title, impact, starting status, each affected component and its own severity, and the first public update.
From there, every update moves the incident through Investigating, Identified, Monitoring and Resolved. Past updates can be corrected in place, and the incident's details can be edited as you learn more.
Component status follows along: affected components change when you report, and go back to Operational when you resolve, unless another open incident or maintenance still affects them.
- Incident statuses
- Investigating, Identified, Monitoring, Resolved
- Impact levels
- None, Minor, Major, Critical
- Per-component severity
- Degraded, Partial, Major
- Restore on resolve
- Overlap-aware
Subtopics
Everything in incident communication
Report an incident
Autessa Status Page lets staff report an incident from one form: title, impact, status, affected components with their own severity, and the first public update.
Read more →Incident updates and lifecycle
Autessa Status Page moves each incident through Investigating, Identified, Monitoring and Resolved, with a public update at every step and wording you can correct later.
Read more →Smart component restore
Autessa Status Page puts components back to Operational when an incident is resolved, but keeps any component that another open incident or maintenance still affects.
Read more →A closer look
What each feature looks like
Report an incident. Autessa Status Page lets your team report an incident from a single form in Status Admin: a customer-friendly title, the impact, the starting status, each affected component with its own severity, and the first update customers will read.
Incident updates and lifecycle. Autessa Status Page moves every incident through a clear lifecycle, Investigating, Identified, Monitoring and Resolved, with a public update at each step.
- Resolved update postedAffected: API, Notifications. Restore box ticked.
- Other open events checked"Database upgrade" is in progress and affects API.
- Notifications → OperationalNothing else affects it.
- API stays Under maintenanceStill affected by the open maintenance window.
- Confirmation"Update posted. 1 component(s) stay affected by another open event."
Smart component restore. When you resolve an incident, Autessa Status Page sets its components back to Operational for you, except any component that another open incident or maintenance window still affects.
Other topics
100% customizable, code and all
Make Autessa Status Page fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours