Incident workspace

Run the response from one operational record

Give responders the context and next move in one scan. Tellagen keeps incident identity, scope, customer impact, ownership, open work, timeline highlights, and the last meaningful update tied to one operational record.

Tellagen incident Overview showing stable incident identity, severity, response status, owner, customer-impact assessment, next operational step, timeline highlights, and open work.

Static product preview

Open the same fictional incident and inspect its Overview, ownership, open work, and latest update.

Continue in INC-1423 (opens in a new tab)

Orient

See identity, scope, and impact without tab hunting

The persistent incident chrome keeps the immutable reference, editable title, severity, status, affected service, regions, and Customer impact separate. Missing critical context appears as an explicit Set or Assess action.

Coordinate

Keep ownership and the next move visible

Commander, responders, the Next operational step, and the Last meaningful update share one operational summary. Open work and response signals point directly to unresolved impact, evidence, questions, and actions.

Tellagen incident queue showing case identity, severity and stage, owner, age, last activity, and the next action for each ongoing incident.

Retain

Carry response context into the final review

Timeline highlights, diagnosis findings, customer evidence, actions, activity, and postmortem versions remain views of the same incident record. The queue and workspace share that state without duplicating the source of truth.

What stays connected through the incident

The queue, Overview, response workspaces, and final review use the same incident record instead of becoming separate status documents.

Identity and scope

Incident reference, title, service, regions, severity, status, and Customer impact retain distinct meanings.

Ownership and next action

Commander, responders, next operational step, and Last meaningful update remain visible together.

Response signals

Open questions, evidence, events, risks, and actions surface the work that still needs attention.

Durable history

Timeline, diagnosis, impact, activity, and postmortem revisions stay tied to the original record.

Frequently asked questions

Can I customize the workspace stages?

Yes. Workspaces can define stage names, order, colors, end stages, and an optional ticket-promotion threshold. End stages remove cases from the ongoing scope; they do not silently close the incident.

Can I add custom columns to the table view?

Yes. Workspace custom fields can be selected as table columns and used as filters, keeping business-specific context in the operational queue.

Does Tellagen replace my alerting tool?

No. Tellagen is the coordination and incident-record workspace after the alert. PagerDuty, Opsgenie, and other alerting systems can continue to page responders.

Ready for the record

Run your next incident from one record

Keep identity, ownership, open work, customer impact, and the next operational step visible from declaration through review.