Incident, Problem, Change, and Request — on one record model.
The four ITIL processes your team runs every day, linked to each other and to your assets, so you can see cause, impact, and history in one place.
From the first alert to the post-incident review, on one record.
One model for human- and system-reported work
A ticket raised by a colleague through the portal and an alert pushed in by Datadog land on the same record model — one of five reporter kinds: user, on-behalf, system, webhook, and email. The detail view adapts to who reported it.
Change enablement with approval built in
Standard, Normal, and Emergency change types. A CAB approval workflow with segregation of duties enforced in code — the person who submits a change can't be the one who approves it.
Problems and known errors
Link recurring incidents to a problem, record the known error and its workaround, and propose the change that fixes the root cause — with the trail connecting all three.
Service requests that don't reinvent the wheel
A request-type builder defines each catalog item once — typed input fields, approval steps with quorums, and an ordered fulfillment checklist. Published models are versioned and immutable, so an open request always matches the form it was submitted on.
Routing that finds the right person
A new incident without a team goes to the team mapped to its category (mappings are maintained through the API today). Routing policies suggest or auto-assign an agent within a load threshold, and an escalation ladder climbs role by role when an SLA breaches.
Intake from every channel
Agents raise incidents on a problem-first form. Employees report through the portal or live chat, and the chat transcript comes with the conversion. Inbound email creates or threads into incidents, and signed webhooks from Datadog, PagerDuty, Grafana or any generic source raise system-reported ones.
Priority from a versioned matrix
Impact and urgency derive P1 to P4 from a published matrix, and each incident records which matrix version set its priority. Authorised users can override it with a mandatory reason; the incident shows an Overridden badge and the worklog keeps both values.
Major incidents, coordinated
A war room opens automatically on a DORA-major or severity-1 customer-impacting incident, with live streams for investigation, communication, decisions and action items. External posts to the status page, customer email or stakeholders need a preview of the masked text, and the incident's assignee cannot send them. The post-incident review is drafted from the room and the timeline.
Regulatory classification and deadlines
Ordinary incidents show nothing regulatory. When DORA or NIS-2 is on, authorised managers classify an incident against the regime's criteria, and the classification starts the reporting cascade with each deadline in view. Every filing is immutable and bound to the audit chain.
How this connects to regulation
Where this connects
What service desk leads ask.
See TENSOR running on your own estate.
30 minutes, screen-shared, no slides. Bring the process you are least sure we handle and we will start there.