Public status page · Autessa Status Page
Incident pages
Every incident and maintenance window on Autessa Status Page gets its own public incident page: the title, impact, current status, when it ran and how long it lasted, which components were affected and how, and every update in order. It is the link your support team pastes into replies.
The problem it solves
Support should send one link, not retype the story
During an incident, support, sales and success all get the same question a hundred times. Without one page to point to, everyone writes their own version and the details drift. A dedicated incident page keeps one authoritative account that updates itself as your team posts.
What you get
- A badge for the impact (No impact, Minor, Major, Critical) or Maintenance.
- The current status, such as Monitoring or Completed, and when it started and ended.
- "Lasted 2 hours 15 minutes" on resolved incidents.
- An Affected list with each component and how it was affected.
- Every update, newest first, each with its status and time.
- Updates support simple formatting: headings, lists, bold, italic, code and links.
- A friendly "We couldn't find that incident" page for a broken or removed link.
How it works
How does incident pages work?
An incident is posted
It gets its own address on your status site the moment it is created.
Everyone links to it
The status page, the 14-day list and the monthly history all link to the same page.
Updates appear as they are posted
Each update from Status Admin is added to the top of the timeline with its status and time.
It becomes the record
Once resolved, it shows how long it lasted and stays in the history for anyone who asks later.
Every option
What an incident page shows
| Option | What it does |
|---|---|
| Title | The customer-facing name you gave the incident. |
| Badge | Impact for incidents (No impact, Minor, Major, Critical), or Maintenance. |
| Status | Investigating, Identified, Monitoring, Resolved; or Scheduled, In progress, Completed, Canceled for maintenance. |
| When | Start to end in the visitor's time zone. Same-day ends show only the time; open incidents show "Since". |
| Lasted | Duration in hours and minutes, for resolved incidents. |
| Affected | Each component with its status on this incident, or "Under maintenance". |
| Updates | Newest first. Staff names are never shown publicly. |
| Breadcrumb | Back to Status and History. |
Permissions
Who can do what?
| Who | Can |
|---|---|
| Visitors | Open and share any incident page. |
| Staff in Status Admin | Post updates, fix the wording of past updates and edit the incident's title, impact and affected components. |
Connected
How it connects to the rest of Status Page
FAQ
Questions about incident pages
Does every incident get its own page?
Yes. Incidents and maintenance windows each have a public page with their full update timeline.
Are staff names shown on incident pages?
No. Status Admin records who posted each update, but the public page shows only the status, time and message.
Can updates include links?
Yes. Updates support headings, lists, bold, italic, inline code and web links. Raw HTML is never rendered.
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