With Kuoll dashboard see how many users are affected by specific bugs. With Kuoll, in a minutes after the new release you understand the impact of each bug.
Each Slack bug notification comes with link to a replayable user session. Each session shows both how user interacted with the web page and also how the code was running in the end user machine.
It's pretty much the same information that developers see in the web browser developer's tools. Kuoll is like a time machine that allows you to see and investigate what was wrong on the user machine in the moment she had a problem.
Web app monitoring and customer support automation is easy with Kuoll. You may also try online demo without registration. It shows the complete and hardcore overview of Kuoll features.
Create account to get your Kuoll APIKEY.
Copy code from the API introduction page. We have async, sync and npm-based version available.
Feel free to contact us if you have a smart or a silly question.
Run your new build in local development, staging and production environment.
Bugbot by Kuoll will send a notification each time it find unfamiliar js error or unfamiliar errorneoues server reply. Each notification has link to the replayable debuggable user session.
Replay user session and learn how the user event caused network request, HTML DOM changes, and JS system API calls.
When a problem detected, Kuoll dumps the user session to the server. If it's the first time this bug happened then Kuoll sends notification about the new issue. On the dashboard you can see how many time each Error happened in the web app and how many users affected by each issue.
Each user session shows the developer
All these events are connected to the cause-effect chains. This way, a developer doesn't need to reproduce bugs. The complete and authentic cause-effect chains provide all information a developer needs to analyse and fix bugs. is able to see and analyse the bug on the record, without even reproducing it, and fix the issue xtremely fast.
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|
In Kuoll we highly respect customer and end user privacy. We do not sell and do not transfer our customer's or end user's data to third parties.
To exclude private user data from the record, please list
the private XHR URLs in the parameter
ignoreUrls parameter of the Kuoll API
The ultimate solution of the privacy question is on-premise deployment. This means you can host Kuoll on your own servers in your secured environment. To get a quote about this option, please contact Kuoll on-premise sales.