Let clients point at the problem

Stop translating "the thing on the page is wrong" from email threads. Put a feedback tab on the client site and get structured reports in your tracker instead.

Agency review cycles run on ambiguity. A client emails "the header looks off on mobile", nobody knows which page or which device, and two replies are spent establishing what everyone is looking at.

A widget on the site removes the ambiguity at the source. The report carries the URL, the viewport, and the browser, because it was written from the page in question.

One project per client site

Each client gets their own project, their own allowed origins, and their own destination. Nothing crosses over, and a client can never see another client's reports.

Match the client's brand

Set the accent colour and the launcher label per project. The widget renders in a Shadow DOM, so it looks identical regardless of what the client's theme does to buttons and inputs.

Route to where your team works

Send one client's feedback into a GitHub repository and another's into a Jira project. Labels and assignees are set per integration, so client work lands pre-sorted.

Frequently asked

Can we white-label the widget?
You control the colour, the label, the headline, and the confirmation message. The widget carries no visible BugLoop branding on your client's page.
What if a client site has a strict Content Security Policy?
You need two entries: the widget origin in script-src and the API origin in connect-src. The widget injects no inline script and requires no unsafe-inline or unsafe-eval.
Does it work on WordPress and Shopify sites?
Yes — it is a single script tag with no dependencies. The installation guide covers the exact place to paste it in both.