Your client never installs anything. They click the widget on the page, describe what looks wrong, and the report lands in your project with the screenshot attached.
It is rarely about the bug β it is about friction.
Without the page, the browser and the exact element, every report starts with three questions back.
Asking a client to install an extension, create an account and learn a tool is where feedback goes to die.
When a sign-off is disputed, chat history is not evidence. A dated table of items is.
Nothing for the client to learn.
Add the SDK to the staging or delivered site, whitelisting only the domains you control.
The widget appears on the page; they annotate the screenshot and submit.
Reports arrive with the screenshot, the page URL and diagnostics attached β no clarifying round, so the developer reproduces and fixes right away.
Evidence you can hand over.
They never install, register or learn a second system.
Page URL, browser, screenshot and Console/network errors all attached β complete information, nothing left to chase.
Reports land in one shared table instead of scrolling away in a chat thread β and stay searchable later.
Captured on the exact page and path where it went wrong, not retold from memory afterwards.
One script tag lets any site visitor report without installing anything.
Send reports into Feishu Bitable or any webhook you own.
Pixel-perfect screenshots, recording, annotation and auto context for your testers.
One person configures, the whole team shares.