Use cases
What changed before the customer reported a problem?
Check recent support and engineering activity together to decide what to investigate next.
Connected activity
4 events from 4 sourcesZendesk · GitHub · Linear · Stripe
- ZendeskZendesk ticket priority changedRecorded
Event from this source
- GitHubGitHub pull request mergedMerged
Event from this source
- LinearLinear bug createdCreated
Event from this source
- StripeStripe payment failedAttention
Event from this source
Connected sources
5 sources connectedThe situation
A support ticket describes the problem. Recent code or issue updates may give you somewhere to start investigating.
Check recent support and engineering activity together to decide what to investigate next.
The workflow
Try it before your next update
- 01
Configure the sources you want to follow. Free includes two integrations.
- 02
Find the ticket and review recent engineering activity. Compare timestamps and follow source links when you need more detail; nearby events do not establish a cause.
- 03
Check recent tickets and code activity together.
What you see
Examples of recorded activity
Available events depend on your source configuration.
- 10m agoZendesk
Zendesk ticket priority changed
- 2h agoGitHub
GitHub pull request merged
- 4h agoLinear
Linear bug created
- YesterdayStripe
Stripe payment failed
- 2d agoGranola
Meeting note available
The outcome
Check recent tickets and code activity together.
Choose which changes need investigation.
Verify the details before replying to the customer.
Questions
Before you get started
Will the feed identify the cause of a customer problem?
It can show recent tickets and engineering activity to investigate. Follow the source links and reproduce the issue before drawing a conclusion.
Which plan do I need?
Start with two built-in sources and seven days of searchable history on Free. Starter includes five sources and 60 days; Pro includes eight sources, 365 days, and custom integrations.
Get started