For dev & QA teamsAll use cases

    Bug reports your team can reproduce.

    Reports arrive with the page URL, browser, OS, viewport, and clicked element attached, plus a screenshot when the page supports capture. Triage them on one board with status, priority, and assignee.

    • Browser, OS, viewport, URL, and clicked element attached automatically
    • Page targeting and allowed origins decide where the widget runs
    • Status tracking from open to resolved on one board
    Every reportcarries URL, browser, OS, viewport
    Per projectwidget toggle and path rules
    When supportedreports can include screenshot capture
    The ClickCues comment composer open next to a pinned element on a live page, showing the captured screenshot thumbnail attached to the comment before it is sent.
    The comment composer opens beside the pin with the captured screenshot already attached. No reviewer account is required.
    Workflow

    Reproduce, triage, close

    Every bug becomes a reproducible report. Every report becomes a task on the board. Every task closes with its history attached.

    STEP 01

    Decide where the widget runs

    Enable the widget per project, restrict it to specific paths with targeting rules, and limit submissions to allowed origins.

    STEP 02

    Someone reports a bug

    The report attaches URL, viewport, browser, OS, and the clicked element, plus a screenshot when the page supports capture. Reporters can add steps to reproduce.

    STEP 03

    Triage on the board

    Assign an owner, set priority, and move the report through your columns as work progresses. AI-assisted summaries clean up long or messy reports.

    STEP 04

    Resolve and close the loop

    Mark the report resolved and keep the full comment history on the item, with a shareable link for anyone outside the workspace.

    Old way vs. ClickCues

    Bug-report problems, solved

    "Can't reproduce, works on my machine."
    Every report includes browser, OS, viewport, and page details your team can use to reproduce the issue faster.
    Steps-to-reproduce buried in a chat thread.
    Steps, screenshot, and comments stay attached to the report itself, so the whole thread lives on the item.
    You don't want the widget loading on every page of the app.
    Targeting rules limit the widget to the paths you choose, and the project toggle turns it off entirely when you're done.
    Two systems, two backlogs, drift.
    One board holds the report, its status, and its history, so there is a single place to check what is still open.
    Built for the job

    Built for engineering rigor

    Browser + page context

    URL, viewport, browser, OS, and the clicked element stay attached to the report so QA and engineering can reproduce issues faster.

    Scoped widget delivery

    Per-project on/off toggle, path targeting rules, and allowed origins keep the widget where you want it.

    Shareable report links

    Send a single report to someone outside the workspace with the screenshot and context intact.

    Screenshot capture

    When the page supports capture, the report arrives with a screenshot of exactly what the reporter saw.

    The ClickCues feedback board showing demo feedback items grouped into New, To Do, In Progress and Done columns, each card showing page path, priority and a screenshot indicator.
    Submitted feedback lands on the project board as tasks with page path, priority and status you can move as work progresses.
    Suggested plan

    Most dev & qa teams start on Studio.

    Studio plan

    Why it fits

    50 team members, 200 GB storage, browser and viewport context, and email support.

    $79/mo
    billed annually

    Stop decoding vague feedback. Start shipping.

    Drop one script tag. Invite your team. Get your first pinned comment in under five minutes.

    7-day free trial Card only at checkout Set up in 2 minutes