These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Incident Response Platform
- Process
- Event intake
Event intake
An external monitoring tool can send an alert or event. An Integration Receipt records which provider sent it, its external identifier, when it arrived, a payload hash and its handling status. The receipt helps the team separate event arrival from the decision to open an incident.
Step by step
-
Receive event Finance Officer
Record the provider, external event identifier, arrival time and hash with Received status.
- Preserve provider identity and arrival
- Updates Integration receipts
-
Review handling Finance Officer
Identify whether the event was Applied, Rejected or Failed after the connection processes it.
- Distinguish applied from exception
- Updates Integration receipts
-
Reconcile exception Finance Officer
Compare a rejected or failed receipt with the provider's original event and decide the correction path.
- Investigate rejected or failed arrivals
- Updates Integration receipts
-
Open response work Service Manager
When the signal represents a disruption, the Service Manager creates an incident for the affected service and asset.
- Establish disruption and owner
- Updates Incidents, Services, Assets
-
Check the result Service Manager
Compare receipt handling with the incident queue and document any unresolved exception.
- Compare intake with actual response
- Updates Integration receipts, Incidents
Who does what
Roles and permissions- Finance Officer
- Manages Integration Receipts.
- Service Manager
- Reviews them and opens Incidents when response is needed.
Set up Incident Response Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.