CX Genie Reduced Incident Investigation Time by 58% with Flashlog
CX Genie x Flashlog
CX Genie Reduced Incident Investigation Time by 58% After Implementing Flashlog
58% less time spent investigating incidents.
11 issues detected before customers reported them.
34 engineering hours saved in one month.
These were the results CX Genie observed during its first 30 days of using Flashlog to monitor technical issues that could affect customer support operations.
Previously, whenever an agent or customer encountered a problem, the team often had to begin with a long list of questions:
Which user experienced the issue?
When did it happen?
What actions did the user take?
Which request failed?
Could the issue be reproduced?
After implementing Flashlog, most of this information became available as soon as an issue was captured.
The result was not simply greater visibility into errors.
CX Genie was able to detect problems earlier, identify their causes faster, and reduce the amount of time incidents affected users.
Results After 30 Days
Over 30 days, Flashlog helped CX Genie monitor 18,420 user sessions and capture 1,286 error occurrences.
Occurrences with the same underlying cause were grouped into 37 distinct technical issues, preventing the team from having to investigate every error individually.
Metric | Result |
|---|---|
User sessions monitored | 18,420 sessions |
Error occurrences captured | 1,286 occurrences |
Distinct technical issues identified | 37 issues |
Issues detected before customer reports | 11 issues |
Average investigation time before Flashlog | 95 minutes |
Average investigation time after Flashlog | 40 minutes |
Reduction in investigation time | 58% |
Issues with enough context for immediate investigation | 78% |
Engineering time saved | 34 hours per month |
Reduction in incident resolution time | 36% |
From 95 Minutes to 40 Minutes Per Investigation
Before using Flashlog, the CX Genie team spent an average of approximately 95 minutes collecting enough information to identify the area most likely responsible for an issue.
The process often involved:
Contacting the person who reported the issue.
Identifying the affected account or workspace.
Asking the user to repeat the steps they had taken.
Collecting screenshots or screen recordings.
Searching through logs across multiple systems.
Attempting to reproduce the issue in a testing environment.
Exchanging information between Support, Product, and Engineering.
After implementing Flashlog, the average investigation time dropped to 40 minutes.
This resulted in:
A 58% reduction in investigation time.
An average saving of 55 minutes per issue.
78% of issues containing enough information for engineers to begin investigating immediately.
Fewer follow-up requests to the person who initially reported the issue.
With 37 issues captured in one month, saving an average of 55 minutes per issue amounted to approximately:
34 Engineering Hours Saved Per Month
This is time the team can spend fixing problems and improving the product instead of searching for missing information.
11 Issues Detected Before Customers Reported Them
One major limitation of relying only on support tickets is that users do not always report the problems they encounter.
When a chat widget fails to load, a visitor may simply leave the website.
When a message fails to send, an agent may refresh the page and try again.
When a workflow stops unexpectedly, the user may switch to another process without creating a ticket for the technical team.
During the 30-day period, Flashlog helped CX Genie identify 37 distinct technical issues.
Of those, 11 were detected before they were reported by a customer or agent.
That means nearly:
30% of Issues Were Detected Proactively
Without production monitoring, these problems might have remained unnoticed or might only have been discovered after affecting more users.
Proactive detection allowed CX Genie to:
Investigate issues before the number of affected users increased.
Identify errors encountered by users who never submitted reports.
Inform relevant teams earlier.
Reduce the time between an incident beginning and the team taking action.
1,286 Error Occurrences Consolidated Into 37 Actionable Issues
During the month, Flashlog captured 1,286 error occurrences.
However, the CX Genie team did not need to investigate each occurrence separately.
Errors with the same underlying cause were automatically grouped into 37 distinct issues.
On average, each issue occurred approximately:
35 Times
Grouping related errors prevented the team from reviewing hundreds of isolated error records and allowed them to focus on the actual causes that required attention.
CX Genie could quickly answer questions such as:
Was this an isolated case or a problem affecting multiple users?
Which issue occurred most frequently?
Which issue affected the most workspaces?
Did the problem begin after a particular release?
Was the occurrence rate increasing or decreasing?
Did the issue continue to occur after a fix was deployed?
This meant that issue prioritization no longer depended only on the number of support tickets received.
The team could prioritize work based on actual production impact.
78% of Issues Included Enough Context for Immediate Investigation
Previously, many issues were passed to Engineering with only a short description, such as:
“The user could not send a message.”
Or:
“The conversation page was not displaying correctly.”
These descriptions explained what the user experienced, but they did not provide enough information to identify the cause.
Engineers still needed to know:
Which user or workspace was affected?
When did the error occur?
What actions did the user take beforehand?
Which request failed?
What response did the system return?
Which device and browser were being used?
How many times had the error occurred?
After implementing Flashlog, 78% of issues contained enough context for the team to begin investigating immediately.
That context could include:
Session Replay.
User actions leading up to the error.
Console logs.
Network requests and responses.
Browser, device, and operating system information.
The environment in which the error occurred.
The total number of occurrences.
Affected users or workspaces.
This reduced the number of tickets returned because of missing information and decreased the number of exchanges required between Support, Product, and Engineering.
Incident Resolution Time Decreased by 36%
Detecting incidents earlier and identifying their causes faster also had a direct impact on overall resolution time.
After 30 days of using Flashlog, CX Genie recorded an average reduction of approximately:
36% in Incident Resolution Time
This improvement resulted from three main changes.
Earlier Detection
The team no longer had to wait until multiple users submitted reports before becoming aware of a problem.
Immediate Access to Context
Engineers could review sessions, logs, and network requests without waiting for Support to collect additional information.
Clearer Understanding of Impact
CX Genie could determine whether an issue affected only one user or was appearing across multiple workspaces.
This helped the team assign the correct priority and avoid spending too much time on isolated cases.
A Real Incident: From Nearly Two Hours to 40 Minutes
During the evaluation period, CX Genie identified an issue that prevented some agents from sending messages to customers.
Without Flashlog, the team might have needed nearly two hours to:
Identify the affected agent.
Find the exact time when the error occurred.
Collect the steps the user had taken.
Locate the relevant message request in the logs.
Review the server response.
Identify the affected browser and device.
Attempt to reproduce the incident.
With Flashlog, the team could directly review the session in which the error occurred and identify the failed message request.
Other sessions experiencing the same problem were grouped under the same issue.
This allowed the team to:
Determine the scope of the incident.
Check whether the cause was related to the frontend, API, or an external integration.
Assign the appropriate priority.
Verify the result after deploying a fix.
The investigation time dropped from approximately 95 minutes to 40 minutes.
That represented an improvement of:
58%
What Does Saving 34 Hours Per Month Mean?
Thirty-four hours is more than a productivity metric.
It represents more than four full working days for one engineer.
That time can instead be used to:
Resolve more high-priority issues.
Improve product stability.
Optimize the agent experience.
Investigate problems affecting customers.
Reduce technical debt.
Build preventive monitoring and safeguards.
Instead of having Support, Product, and Engineering repeatedly collect the same context, all three teams can begin with a shared source of production data.
From Technical Metrics to Business Impact
For a customer support platform, a technical error is not simply another line in a log.
A message that fails to send could mean a customer does not receive the support they need.
A chat widget that does not appear could cause a potential customer to leave the website.
A disrupted workflow could prevent a request from reaching the right agent.
A delayed response could cause a business to lose a sales opportunity.
After 30 days of using Flashlog, CX Genie had:
Monitored 18,420 user sessions.
Captured 1,286 error occurrences.
Grouped those occurrences into 37 actionable issues.
Detected 11 issues before customers reported them.
Reduced incident investigation time by 58%.
Reduced overall resolution time by 36%.
Saved approximately 34 engineering hours per month.
Ensured that 78% of issues contained enough context for immediate investigation.
Moving From Reactive Troubleshooting to Proactive Operations
The most significant change was not simply that CX Genie could detect more errors.
It was the way the team responded to production issues.
Previously, the process often began only after a user noticed a problem and submitted a report.
Now, the team can:
Detect an incident as soon as it occurs.
Assess how many users are affected.
Review the complete context leading up to the error.
Identify the area most likely responsible for the problem.
Prioritize issues based on their actual impact.
Monitor the results after deploying a fix.
Confirm that the issue has stopped occurring.
CX Genie helps businesses maintain conversations with their customers.
Flashlog helps the CX Genie team measure and protect the reliability of every one of those conversations.
