Bugzio
Annotated screenshot
Pen, rectangle, arrow, emoji and blur. The blur pixelates the area first and only then softens it, so even small text — personal data, prices — is no longer readable.
Feature
Bug reporting that needs no follow-up email
The reporter presses a button on the site, circles the problem and writes one sentence. Everything else — screenshot, console, failed requests, browser, screen size and steps — the widget attaches on its own.
No payment card · Unlimited reporters · Interface in 6 languages
Why it matters
A phone screenshot is not a bug description
Before anyone can fix it, somebody has to establish which page, which browser and which step. That is what the emails are for.
How it goes today
- “The button doesn’t work” — no address, no browser, no error text.
- Three emails back and forth before anyone knows which page and which step.
- The console error is long gone by the time someone finally looks.
- The developer cannot reproduce it and closes the report with “works for me”.
With Bugzio
- One click on the site — the reporter needs no account.
- Address, browser, operating system and screen size attach themselves.
- Console and failed requests are kept from the moment the page loaded.
- Every report lands in the project with a status, a priority and an assignee.
The result: one record that answers the questions you would otherwise ask by email.
What you get
What the widget captures
Everything below is attached automatically — the reporter needs to know nothing about developer tools.
Console logs from page load
console.log, warn and error, plus uncaught exceptions with their stack trace. The hooks go in the moment the script loads, so the report also contains errors that happened before the widget was opened.
Failed requests
fetch and XMLHttpRequest with method, address, status code and duration. Only the failures are kept — status 400 and above, or a connection error — so the list stays readable.
Step timeline
Clicks with the element, its text and its tag, plus URL changes, ordered oldest to newest. It is a ready-made answer to “what did you do before that”.
The environment, without asking
Browser and version, operating system and version, screen resolution, window size, orientation, colour depth and languages — read from the browser instead of asked of the reporter.
Your own fields
In the widget builder you can add your own fields — environment, client, order number — and map them to ClickUp custom fields.
The number of reporters is unlimited
Clients and testers need no account and take up no paid panel seats. The widget speaks six languages and is style-isolated, so it does not inherit your site’s styling.
This is what an incoming report looks like
The list with statuses on the left, on the right all the context that arrived with the report.
How it works
Three steps to your first report
Setup takes five minutes and needs no code changes at all if you are on WordPress.
Add the widget
One <script> tag before </body>, or the free WordPress plugin. The project token comes from the panel.
The client presses the button
Circles the problem, writes a sentence, hits “Send”. No account required.
The report is in the panel
With the whole context, a status and an assignee. Sync it to ClickUp or push it to a webhook if you need to.
Related features
What this pairs with
Each of these adds a layer to the same record, so the panel keeps one report per bug, not one per feature.
Session replay
A DOM recording, screen video with voice and a step timeline — exactly what happened before the bug.
AI triage
Turns the captured evidence into a title, reproduction steps, a priority and a category.
Monitoring
14 services that check a site’s uptime, speed, security and compliance on their own.
Stop collecting screenshots by email
Install the widget on one site and see what a first report with the full context looks like.
No payment card · Unlimited reporters · Interface in 6 languages