Site Feedback Widget
Point at the problem on the page, and the ticket writes itself.
The Site Feedback Widget lets reviewers capture what they see on a website we're building and turns each note into a tagged ticket in our project tracker. You can follow every fix in TIF OS instead of chasing it by email.
What it does
Website reviews usually arrive as an email with six screenshots, a sentence that says the thing on the right looks off, and no clue which browser the reviewer was using. Someone then turns each comment into a ticket, guesses the page, asks follow-up questions, and waits for the answers. By launch week, feedback is spread across email, chat, and a spreadsheet, and nobody is sure what's been fixed.
On every website project with Think It First, we add the widget to the site under review and link it to that project in our tracker. A reviewer clicks the widget wherever something needs attention, captures exactly what they see, tags it, and adds a note. The ticket lands in our tracker with the capture, the page, the browser, and the reviewer attached, and it appears in your Web Feedback view in TIF OS, so you can watch our team work through it.
The widget captures and files feedback, and people decide what it means. Our project manager sets priorities with you, merges duplicates, and confirms what's in scope. Our designers and developers decide how to fix each item, and the reviewer confirms the fix before the ticket closes.
What it handles
Four ways to capture
Reviewers choose a screenshot, a scrolling capture of a long page, a short video, or a text-only note. They pick whichever explains the issue best and can mark the exact element they mean. A video of the steps that led to a bug saves a developer an hour of guessing.
Tagged at the source
Each piece of feedback is marked as a Bug, Suggestion, Question, or Design note when the reviewer sends it. The team can sort a whole review before anyone reads it in full. Bugs go to developers, design notes go to designers, and questions go to whoever can answer them.
Browser and reporter details
Every ticket carries the page URL, the browser, the screen size, and the name of the person who reported it. Nobody has to write back to ask which browser the reviewer was on. Developers can reproduce the issue in the same setup the reviewer saw.
Filed in our project tracker
Tickets file straight into our tracker under your project, grouped in a QA epic created for the review. Nobody types up tickets from an email thread. Each ticket includes the capture, so the developer fixing it sees exactly what the reviewer saw.
Reviewers see their own notes
Each reviewer keeps a list of the feedback they've already sent. They can check what they flagged last week before adding something new, which cuts down on duplicates. It also gives them one place to look back over their part of the review.
Only where you want it
The widget appears only on the sites and environments we agree on with you, such as a staging or review site. It never shows up for your customers unless you decide it should. We set the site list with you before reviewers start.
Who it's for
FAQ
Site Feedback Widget questions
What can reviewers capture?
A screenshot, a scroll capture of a long page, a short video, or a text-only note. Reviewers tag and annotate each one right on the page they're reviewing, so the ticket shows exactly what they mean. The page, browser, and screen size are attached to every ticket automatically.
Where do the tickets go?
Into our own project tracker (today that's Jira), under your project and grouped in a QA epic created for the review. Each ticket carries the page, browser, screen size, and reviewer details. It's where our team does the work, and you can follow each item in the Web Feedback view in TIF OS, next to the rest of your project.
Who decides what gets fixed?
Our project manager sets priorities with you, merges duplicates, and confirms what's in scope. Our designers and developers decide how to fix each item. The reviewer confirms the fix before the ticket closes, so nothing is marked done until the person who raised it agrees.
Will customers see the feedback widget on our live site?
No, unless you want them to. The widget appears only on the sites and environments we agree on, such as a review environment, so it never shows up for your customers. We add it to the site under review and link it to your project in our tracker before reviewers start.
How does the widget help with pre-launch QA?
Every piece of feedback becomes a ticket in one QA epic created for the review, so nothing lives in email, chat, or a spreadsheet. Each item is tagged Bug, Suggestion, Question, or Design, so the team can sort a review before reading it in full. Everyone can see which items are fixed and which are still open.
How do reviewers avoid sending the same feedback twice?
Each reviewer keeps a list of the feedback they've already sent, so they can check what they flagged before adding something new. When several reviewers do report the same issue, our project manager merges the duplicates, sets the priority, and assigns one ticket, so developers fix it once.
What is a website feedback widget?
A website feedback widget is a small tool that sits in the corner of a site under review and lets reviewers report issues on the page itself. Instead of emailing screenshots, a reviewer clicks the widget, captures what they see, and adds a note. The widget files that note as a ticket with the page and browser details attached.
Is the Site Feedback Widget included with a website project?
Yes. The widget is included with every website project we take on, so reviewers can use it from the first review round. If your team would like its own version for its own sites, connected to your own tracker, we can build one for you. Tell us how your reviews run today, and we'll scope it from there.
You know AI could help. Let’s build it.
Bring us a task you have in mind, or just a hunch. We’ll help you find the right place to start and build it around the way your business works.