Investigation AgentInvestigating
Password reset links fail after release 2.14
Investigation Agent
Root cause analysis for your support queue
Kobal digs through the tickets, the accounts behind them and your latest release, then hands you the cause, who’s affected and a fix to approve. No tagging marathon. No “can you send me some examples?”
Investigation path
- Finding definedChecking…Running
- Tickets concentrate on mobileChecking…Running
- Enterprise accounts onlyChecking…Running
- Pattern begins after release 2.14Checking…Running
- Older versions unaffectedChecking…Running
Case record
An agent that argues with itself
Kobal starts with the most likely explanation, then goes looking for proof against it. The ones that don’t hold get closed, so the one you see is the one the evidence backs.
From “something’s off” to “here’s why”
The three questions you get asked about every spike, answered before anyone asks.
- 47tickets18accountsSep 12started
Is it real?
How many tickets, how many accounts, and since when.
- Likely cause · supported
Release 2.14 changed how mobile deep links pass the reset token.
App 2.14 · Sep 12First ticket 6h laterWhy is it happening?
Tickets lined up against your releases and status updates.
- Lumen HealthBusinessRenews in 12 days
- Harbor & CoProRenews Nov 3
Who’s affected?
Every account involved, with its plan and renewal date.
Fix the expensive problem first
Fifty tickets from free users and five from your biggest account aren’t the same problem. Kobal ranks every open investigation by the revenue and renewals behind it, so the one that matters goes first.
- Revenue at risk, per issue
- Renewals coming up in the affected accounts
- Fewer escalations reaching engineering without proof
Lands where your team already works
Kobal hands the problem to the people who can fix it, in Slack or in your work tracker, with the cause, the real tickets and the affected accounts already attached. When the fix ships, Kobal notices and can tell the account owners.
No more “can you send me some examples?”
Every investigation ends as one write-up you can forward as it is.
What broke, what set it off and how sure Kobal is.
Every number opens the tickets behind it, with what customers actually said.
A fix drafted for your approval: what happens, where, and who sees it.
It keeps watching after you ship
Approving the fix isn’t the end. Kobal runs the same check again and tells you whether the tickets dropped, stayed flat or came back.
- DroppedThe investigation closes with the result attached.
- Stayed flatIt comes back to you with what was tried.
- Came backIt reopens, with the full history.
Built to be checked
Kobal shows its work, so you never have to take its word for it.
Says “unknown” instead of guessing. If the evidence doesn’t prove a cause, the write-up says so and shows what’s missing. Revenue and release context only appear when those tools are connected.
Every number opens its tickets. Click any count to read the conversations behind it.
Nothing goes out without your yes. Kobal drafts. You approve. Only then does anything change.
Questions, answered
Can't find what you're looking for?
Visit our Help Center.
Stop guessing why tickets spike
Bring a spike your team already solved the hard way. We’ll show you how Kobal would have worked it, evidence and all.
Get early accessWorks on top of the helpdesk you already use. No migration.