The old way
|Customer reports a problem||Customer support talks to customer||Customer support reports an issue||Developer recreates environment and reproduces the problem||Developer analyses the issue||Developer fixes the issue||DevOps deploys a fix to production|
The Kuoll way
|Kuoll script detects a problem||Kuoll script captures bug report automatically||Kuoll script captures high-fidelity bug report||Kuoll replays captured report in debug mode||Developer analyses the issue with ease||Developer fixes the issue with confidence||DevOps deploys sure fix to production|
|Finds bugs before your customers do||Automated capturing saves 68% customer support time||High-fidelity capturing||High-fidelity replay||Sure fix, no refix ping-pong, saves 40% time||Much easier, spends 60% less time||Bugs fixed, HQ software is direct to market|
A developer copies Kuoll monitoring code snippet into pages of web application.
This code is monitoring js and server problems and recording user sessions. User sessions are stored on the client-side in the user web browser internal database (called IndexedDB).
When a problem detected,` Kuoll dumps the user session to the server. In case of a newly discovered problem, we send developer a link to recorded user session to Slack.
An engineer gets notification with a link where he can see the recorded user session. Each user session shows the developer
All events are connected to the cause-effect chains. A developer is able to see and analyse the bug on the record, without even reproducing it, and fix the issue xtremely fast.