Turn Slack incidents
into clean timelines
Start in Slack, assign owners, score severity from real inputs, and export the record your postmortem needs.
From Slack alert to incident record.
Tellagen fits around the tools your responders already use. The output is a timeline your team can trust after the incident ends.
Start from Slack
Type /incident in Slack. Tellagen opens a war room with the incident title, owner, severity, and service context.
Build the timeline
Keep working in Slack. Alerts, decisions, deploys, and useful messages become suggested timeline events.
Close with a record
Close the incident with a structured record: timeline, severity changes, participants, and follow-up actions.
Visible timeline, clear ownership.
Tellagen turns useful Slack messages into timeline suggestions while responders stay in channel. The incident commander reviews each entry before it becomes part of the record.
- Suggested entries stay in review until a responder accepts them
- Slack messages, deploys, alerts, and decisions in one record
- Workstreams for detection, mitigation, comms, and customer impact
Severity follows the facts.
Use the same formula every time instead of arguing over SEV levels in the war room. Tellagen combines technical signals with business context so priority is visible and auditable.
Every incident gets a consistent score based on affected users, revenue risk, duration, and service context.
- Custom formulas by service, region, or team
- Inputs from affected users, customer tier, MRR, duration, and custom fields
- Threshold changes stay visible in the incident record
Investigations run where your data lives.
Tellagen can start an investigation from the incident record, then keep the work visible as tools run. Use local MCP for hands-on analysis, or deploy the agent when investigations need to run automatically in your environment.
- Local-only LLM mode with your own AI client and @tellagen/mcp-server
- On-premise tellagen-agent for automatic dispatch inside customer infrastructure
- Progress, trace steps, and findings stream back to Tellagen over WebSocket
Run Claude Code or another local client with the Tellagen MCP server.
npx -y @tellagen/mcp-serverRun tellagen-agent near logs, metrics, and private services.
/v1/agent/connectinvestigation_requestIncident context sent to agentqueuedinvestigation_trace_eventquery_grafana_logs returned 18 matching errorsliveinvestigation_resultLikely cause and evidence ready for reviewdoneWhat the incident record contains.
Tellagen keeps the evidence your team needs after the channel quiets down. The record is assembled as responders work, then reviewed before it is shared.
Timeline
Accepted Slack messages, alerts, deploys, and decisions in chronological order.
Severity
The score, inputs, thresholds, and every change made during the response.
Ownership
Incident commander, service owners, responders, workstreams, and follow-up actions.
Export
A clean incident record ready for postmortems, audits, and customer updates.
Fair pricing. No hidden costs.
Simple per-user plans for approved events, severity formulas, and postmortem-ready export.
Compare all pricing details ->
Incident timelines, severity scoring, and Slack setup for small teams.
- Up to 7 users
- Slack & PagerDuty integrations
- 30-day incident history
- Timeline and record export
For growing engineering teams with regular on-call rotations and postmortems.
- Unlimited users & history
- Timeline suggestions
- Severity analytics
- Postmortem export
For scaled orgs with compliance, audit, and support requirements.
- SSO (SAML, OIDC)
- Audit log
- Priority support (4h SLA)
- Everything in Team
- How does severity scoring work? Can we customize the formula?
- Severity scores are computed from CEL expressions you write — referencing custom fields like affected users, service tier, MRR impact, and SLA ratios. Scores map to severity levels via configurable thresholds. A built-in preview calculator lets you test any formula against sample data before deploying.
- How does the timeline capture Slack messages?
- Tellagen suggests timeline events from Slack messages by prefilling title, description, tags, and workstream. A responder reviews and can accept, edit, or skip each suggestion before it is added to the incident record.
- Does Tellagen write the post-incident record?
- Tellagen assembles the record while the incident is active: accepted timeline entries, severity changes, owners, workstreams, and follow-ups. Your team reviews it before exporting or sharing it.
- Does this replace PagerDuty or our alerting platform?
- No. Alerting tools still page responders. Tellagen handles what happens after the alert fires: severity scoring, Slack-based coordination, timeline capture, and the structured incident record.
- How quickly can we start using it?
- Install the Slack app, connect your alerting source, and start capturing events. Teams typically get value on day one with Slack integration and a basic severity formula, then add custom fields and workstream conventions over time.
Your next incident is coming.
Be ready with Tellagen.
Connect Slack before the next alert fires. Keep the timeline, severity, owners, and decisions ready for the post-incident record.