Assess
Make the unknown state explicit
When impact is not set, the workspace says Assessment required instead of showing an empty dashboard. Imported narrative remains marked for review until a responder decides what the incident record can support.
Customer impact
State customer impact without pretending certainty
Say what customers are experiencing without turning an unknown into a number. Tellagen keeps assessment state, source readiness, affected customers, and reviewed evidence beside the technical response.
Public demo · Fictional data · Read-only
Static product preview
See the fictional affected customers, source readiness, support evidence, and reviewed assessment together.
Connect
See which customer evidence is actually available
Source readiness keeps revenue enrichment and support conversations honest. Configured, unavailable, and incomplete states stay visible, so responders know whether account and conversation context can support the assessment.
Review
Publish a backed-by-evidence assessment
Affected customers, account context, and linked support evidence remain beside the reviewed narrative. The incident overview receives the assessment state without replacing missing customer evidence with a fabricated metric.
What the impact assessment keeps connected
The assessment remains useful because its state, source readiness, customer evidence, and incident-wide handoff are visible together.
Assessment state
Not set, assessment required, and reviewed states communicate confidence without inventing precision.
Source readiness
Revenue enrichment and support conversation availability show which evidence can be consulted now.
Customer evidence
Affected-customer records, account context, and linked conversations support the reviewed narrative.
Overview handoff
The incident Overview reflects the current assessment so technical and customer responders share one state.
Frequently asked questions
Do I need a billing integration to track impact?
No. You can add affected customers directly. Billing and workspace resolvers enrich those records when connected, but the incident impact workflow does not depend on them.
Can I add many customers at once?
Yes. The impact workspace supports bulk customer identifiers or email addresses and avoids creating duplicate incident records for the same customer.
How does Intercom fit into the workflow?
Relevant Intercom conversations can be linked to affected customers, giving responders direct access to support evidence from the incident record.
Ready for the record
Assess impact from evidence, not estimates
Give technical and customer responders one reviewed account of what is known, unknown, and supported now.
Checking workspace accessOpen customer impact (opens in a new tab)