Dashboard Quick Start: Managing Your Feedback
Learn how to create projects, install the embed, and manage incoming feedback with filters, archiving, and admin notes.
From a fresh account to feedback arriving in your inbox is about ten minutes. Most of it is deciding what to call the project.
The command center
Signing in lands you on a grid of panels you choose. Your projects, unread and escalated counts, thirty days of volume, a sentiment dial, live quest completion, your plan and seats. The layout saves to your account, so the board you build is the board you get back on any machine.
Adding a Panel
The Panel Array strip above the grid controls the board. + Panel lists what you can add, each with a line saying what it shows, and the one you pick drops into the first free space. Panels can repeat, which is the point: two Inbox panels aimed at two projects is a good dashboard.
Arranging the Grid
Press Arrange and every panel grows a grip in its header and a pull-tab at the bottom right. Drag the grip to move, drag the corner to resize, and everything underneath repacks around it. The keyboard uses the same two handles: arrows move, shift and arrows resize. Done returns the board to read-only. Reset layout, which only shows while arranging, puts back the shipped arrangement.
On a narrow screen the panels stack into one column and arranging switches off, since a single column has no arrangement to make.
Pointing a Panel at One Project
Every panel that reads project data has a selector in its header. All projects totals everything you can see; pick one and the panel narrows. Account-level panels like Subscription and the Projects roster have no selector, because there is nothing to narrow.
Keeping It Current
Panels load with the page and then stay put; nothing polls. Refresh pulls them all again when you need to trust the numbers. Layout changes save a moment after you stop moving things, and a Layout saved chip appears by the controls to say so.
Your first project
The Projects page in the left navigation, and the Projects panel on your board, list everything you collect feedback for.
Create it
New Project, top right. The modal wants two things:
A name you will recognise in a list of six, like "Marketing Site" or "Customer Portal". And the domain you will install on, example.com. The domain both labels where feedback came from and, once set, restricts which pages may submit to this project.
Take the API key
The project's Settings tab holds its API key. That key is what ties a submission to this project.
Make more than one if you want to tell staging from production, or to revoke one integration without breaking the rest.
Installing the embed
A script tag
Before the closing </body>:
<script
src="https://unpkg.com/@qaiddev/thumbs-embed/dist/embed.js"
data-endpoint="https://qaid.dev/api/feedback"
data-api-key="your-api-key-here"
></script>Swap in the key from Settings.
Or npm
For anything with a build step:
npm install @qaiddev/thumbs-embedThen construct it:
import { QaidFeedback } from '@qaiddev/thumbs-embed';
new QaidFeedback({
endpoint: 'https://qaid.dev/api/feedback',
apiKey: 'your-api-key-here'
});Check it worked
The buttons should appear bottom-right:
Default Feedback Buttons
What you'll see after installation
Click one and walk the flow through. It lands in your dashboard within seconds.
Reading what arrives
The Feedback tab on your project is the inbox.
The list
Each row carries its sentiment, the page URL it came from, whatever message was typed, a timestamp, and markers for any screenshot or recording attached.
One item
Click a row and you get the full message, the CSS selector if they targeted an element, the screenshot, the recording, the console errors from that session, and their browser and device.
That is usually enough to skip the reproduction step entirely.
Filters
By sentiment
All, Positive and Negative sit at the top of the list.
Start on Negative. That is where the work is.
By attachment and escalation
Has Video narrows to items with a recording. Escalated narrows to items your escalation rules flagged.
The video filter earns its place on hard bugs. Watching what somebody actually did tends to answer questions their description never raised.
Together
Filters combine. Negative plus Has Video is the queue for a weekly triage meeting.
Escalated items
Escalation is not something you do by hand. An item is escalated when it matches one of your project's escalation rules, which match on keywords, the page URL, sentiment, whether console errors were captured, and whether a screenshot came with it.
A matched item gets a red Escalated badge and shows up under the Escalated filter. To change what gets flagged, change the rules. Escalation rules need a Pro plan.
Archiving
Archive anything you have dealt with, anything that duplicates something else, spam, and the thumbs-up with no message. Those last ones are most of your inbox and none of your work.
The Archive button on any item moves it out of the inbox. Show Archived at the top of the list brings them back into view. Nothing is deleted and everything unarchives.
Admin notes
Notes attach to a feedback item and only your team can read them. Use them for what you found while investigating, for the context somebody needs when you hand an item over, for how it was fixed, and for links out to the Jira ticket or GitHub issue.
The Admin Notes section of the detail view takes them. Each one is stamped with the time and your name. The person who sent the feedback never sees any of it, so write what you actually think.
A rhythm that works
Five minutes a day: open the inbox on Negative, read what is new, archive the spam and the duplicates.
Half an hour a week: filter to Escalated, write up what you find in admin notes, open tickets for the confirmed bugs, archive what is done.
Once a month, look at Insights instead of the inbox. A month of individual items tells you nothing; a month of themes tells you what to build.
Adding people
Invite from the project's Settings tab. Owners get everything including billing and member management; members work the feedback but cannot change project settings. Team collaboration covers assignment and notifications properly.
Next
Themes match the buttons to your brand, custom CSS goes further than the presets, and brand color matching covers the three colour settings.