bugpot

Website feedback

Feedback from the people who use the site

The classic case. Anyone who visits the site — a client mid-review, a colleague testing a fix, a tester running through a checklist — can hit the widget and send you an annotated screenshot with context. No account, no meeting, no “can you send that in a Google Doc”.

The scenario

Someone finds something wrong at 4pm

The classic afternoon email would take twenty minutes to write, another twenty to interpret. With Bugpot it takes twenty seconds and lands as a real issue.

  1. 1

    A reviewer spots the pay button clipped on their phone.

  2. 2

    They tap the feedback launcher, draw a box around it and type “broken on mobile”.

  3. 3

    Bugpot captures the screenshot with browser, OS, viewport and console log attached.

  4. 4

    The report lands in the inbox with status “open”, priority “medium”, ready to triage.

  5. 5

    The engineer opens the ticket and has everything needed to reproduce, before they’ve refilled the kettle.

How Bugpot fits

The parts that carry this scenario

One script tag

The widget installs in one line before your closing body tag. No SDK, no build step, no account required for reporters.

Anyone can report

Show a guest form or a member form depending on who’s browsing. Ask for a name and email from strangers, ask for nothing from your team.

Every report a real issue

Reports arrive as full issues in the triage inbox — status, priority, assignee, comments, filters, keyboard shortcuts.

Never breaks the host page

Shadow-DOM isolation stops the widget colliding with your site’s CSS or JS. Safe to leave on production.

Put a feedback button on your site today

Free for five websites. Install in two minutes, no card required.