What is an AI incident timeline summary?
An AI incident timeline summary is a short account of an incident written by software from what was said and done: the alert, the page, the call and the channel. It tells a person who joins late what happened, in order, so they do not have to scroll the whole thread or ask someone to repeat it.
What is an AI incident timeline summary?
Every incident produces a long trail: the alert that fired, the page, a call, and many messages in a channel. The trail is the timeline. A summary reads the trail and says, in a few sentences, what happened and in what order. Software writes it, so it keeps up while the incident is still moving, and a person who joins late starts from the same account as everyone else.
What should a good summary contain?
A summary is only useful if it can be checked against the timeline behind it. Look for these:
- What fired. The alert, and the service it concerns.
- Who was paged, and how. The person, the channel and the time.
- What has been found. The findings so far, stated as findings and not as conclusions.
- What was decided and done. Actions taken and by whom, in order.
- What is still open. The question nobody has answered yet.
Each item should point back to a timeline entry. A summary with no trail behind it is a guess a tired person has to trust.
How does Noci AI write one?
Noci AI’s AI voice agent phones the on-call engineer and briefs them on the incident. The transcript, the outcome and an AI summary land on the incident timeline, next to the alert and the page.
When an incident is declared, Noci opens a Slack channel for it with the incident’s context and a meeting link. In that channel Noci runs the bridge, summary and status drafts. The drafts are for a person to read and post, and the agents’ findings land on the same timeline. How the call works has the detail.
How is a summary different from a timeline or a transcript?
They are three records of the same incident, and each answers a different question.
| Record | What it is | Use it for |
|---|---|---|
| Timeline | Every alert, page, call and message, in order | Evidence, and the review afterwards |
| Transcript | The words of a call | Checking exactly what was said |
| Summary | A short account of the timeline and the call | Catching up in a minute |
The summary is the one a person reads first and the timeline is the one they check it against.
What can go wrong with an AI summary?
It can leave out a detail, or state a guess as if it were settled. Neither is a reason to avoid one, and both are reasons to keep the summary tied to the entries behind it. Read the entry before you act on a line you are unsure of, and treat a finding as a lead until a person has confirmed it.
Who needs the summary?
- The person who joins late. They read one account instead of the whole thread.
- The person who takes over. A handoff starts from what is open, not from what happened an hour ago.
- The person who writes the review afterwards. The summary is a starting point, and the timeline behind it is the evidence. See MTTA vs MTTR for which times to look at.
Questions
Does the summary replace the incident timeline?
No. The timeline is the record: every alert, page, call and message in order. The summary is a short reading of it, so a person can catch up without reading each entry.
Where does Noci AI's summary appear?
On the incident timeline. The transcript of the AI incident call, its outcome and an AI summary land there, next to the alert and the page.
What opens when an incident is declared in Noci AI?
Noci AI opens a Slack channel for each declared incident, with the incident's context and a meeting link. The alert, the page and the agents' findings sit on the same timeline.
Does Noci AI post status updates for me?
It drafts them. A person reads a draft and decides whether to post it.
How is a timeline summary different from the review afterwards?
A summary says what has happened so far, while the incident is under way. A review written afterwards looks for causes and changes. The summary is an input to that review, not a replacement for it.