By clicking on any incident, you will be taken to its dedicated incident page which shows all the details of the incident.
The incident message and number are at the top of the page. It also shows the current status, the incident description, opened time when it got first triggered, to whom it is currently assigned, at what time it got assigned to that Squad or Schedule or any individual user and the service impacted due to the incident.
Reassign option will allow you to manually reassign the incident to another User, Squad or Escalation Policy. Once this is done, the newly assigned User, Squad or Escalation Policy can choose to acknowledge and resolve the incident. The incident can be reassigned any number of times, as the need arises.
It will also have War Room at the bottom and Incident Timeline at the right.
There are four types of states an Incident can have:
When an incident is open, it will be in the triggered state. Concerned users will get notified when an incident is in triggered state. It will remain in this state until someone acknowledges it.
Incident shifts from Triggered to Acknowledged state when any user acknowledges it. The user can now look into the incident and try to solve it. If the incident is reassigned or escalated to another user, it will go back to a triggered state, until the new user takes responsibility for it and acknowledged the incident.
Incidents can be marked as Resolved to close them.
Sometimes, the incidents can be in a suppressed state - this happens when the alert notification was not meant to go out for some reason like the service was under maintenance.
Squadcast allows a maximum of 10 notifications every 15 minutes for an organization.
Any incident that crosses this limit will be automatically truncated in the platform.
Updated 25 days ago