Qaid
ARTICLE

Dashboard Quick Start: Managing Your Feedback

Learn how to create projects, install the embed, and manage incoming feedback with filters, archiving, and admin notes.

Qaid Team

You have signed up for Qaid and are ready to start collecting feedback from your users. This guide walks you through the complete workflow from creating your first project to managing incoming feedback like a pro.

Creating Your First Project

After signing in, you land on the Projects page. This is your command center for all feedback collection across your sites and applications.

Step 1: Click “New Project”

In the top right corner of the Projects page, click the New Project button. A modal appears asking for basic information.

Step 2: Fill in Project Details

Enter your project details:

  • Name: A descriptive name like “Marketing Site” or “Customer Portal”
  • Domain: The domain where you will install the embed (e.g., example.com)

The domain helps you identify where feedback originates, especially when managing multiple projects.

Step 3: Get Your API Key

After creating the project, you are taken to the project dashboard. Here you will find your API Key in the Settings tab. This key authenticates feedback submissions from your site.

You can create multiple API keys per project if you need to track different environments (staging vs. production) or revoke access without affecting other integrations.

Installing the Embed

With your API key in hand, installation takes just a few minutes.

Option 1: Script Tag (Simplest)

Add this script tag before your closing </body> tag:

<script
  src="https://unpkg.com/@qaiddev/thumbs-embed"
  data-endpoint="https://qaid.dev/api/feedback"
  data-api-key="your-api-key-here"
></script>

Replace your-api-key-here with the API key from your project settings.

Option 2: NPM Package

For JavaScript frameworks and build systems:

npm install @qaiddev/thumbs-embed

Then initialize in your code:

import { QaidFeedback } from '@qaiddev/thumbs-embed';

new QaidFeedback({
  endpoint: 'https://qaid.dev/api/feedback',
  apiKey: 'your-api-key-here'
});

Verify Installation

Once installed, you should see the feedback buttons appear on your site:

client:load id=“install-demo” title=“Default Feedback Buttons” description=“What you’ll see after installation” height=“120px” background=“linear-gradient(135deg, #1a1a2e 0%, #16213e 100%)” config=[object Object] />

Click either button to test the feedback flow. Submitted feedback appears in your dashboard within seconds.

Viewing Incoming Feedback

Navigate to your project and click the Feedback tab. This is your inbox for all user submissions.

The Feedback List

Each feedback entry shows:

  • Sentiment: Thumbs up (positive) or thumbs down (negative)
  • Page URL: Where the feedback was submitted
  • Message: Optional text the user provided
  • Timestamp: When it was submitted
  • Attachments: Screenshots or video recordings if captured

Feedback Details

Click any feedback item to expand its details. The detail view includes:

  • Full message text from the user
  • Element selector if the user targeted a specific element
  • Screenshot of the targeted area
  • Video recording if the user recorded their session
  • Console errors captured during the session
  • Browser and device information

This context helps you understand exactly what the user experienced and where.

Filtering Your Feedback

As feedback volume grows, filters become essential for staying organized.

Sentiment Filters

At the top of the feedback list, you will find sentiment filters:

  • All: Shows all feedback regardless of sentiment
  • Positive: Only thumbs up feedback
  • Negative: Only thumbs down feedback

Negative feedback often contains the most actionable insights. Start there when triaging issues.

Special Filters

Beyond sentiment, you can filter by:

  • Has Video: Feedback entries that include screen recordings
  • Escalated: Feedback you have marked as high priority

The video filter is particularly useful when debugging complex issues. Seeing exactly what the user did often reveals problems that text descriptions miss.

Combining Filters

Filters work together. For example, selecting “Negative” and “Has Video” shows only negative feedback with attached recordings. This combination is perfect for your weekly bug triage meetings.

Working with Escalated Feedback

Some feedback requires immediate attention. The escalation feature helps you track these items.

Escalating Feedback

When viewing a feedback item, click the Escalate button (flag icon) to mark it as high priority. Escalated items:

  • Appear with a visual indicator in the list
  • Can be filtered to show only escalated items
  • Stay escalated until you manually de-escalate them

Use escalation for:

  • Critical bugs affecting user experience
  • Security-related reports
  • Issues reported by VIP customers
  • Problems you need to discuss with your team

De-escalating

Once an issue is resolved, click the Escalate button again to remove the flag. This keeps your escalated list focused on active issues.

Archiving Feedback

Not all feedback requires action. The archive system keeps your inbox clean while preserving history.

When to Archive

Archive feedback when:

  • You have addressed the reported issue
  • The feedback is spam or irrelevant
  • The feedback duplicates an existing item
  • No action is needed (e.g., simple positive feedback)

How to Archive

Click the Archive button (box icon) on any feedback item. The item moves out of your main inbox view.

Viewing Archived Items

To see archived feedback, toggle the Show Archived switch at the top of the feedback list. This reveals all archived items alongside active ones.

Archived feedback is never deleted. You can always unarchive items if needed.

Adding Admin Notes

Admin notes let you and your team add context to feedback items that only dashboard users can see.

Use Cases for Admin Notes

  • Investigation notes: Document what you discovered about an issue
  • Handoff context: Explain the situation when assigning to a teammate
  • Resolution summary: Record how you fixed the problem
  • Related links: Add Jira tickets, GitHub issues, or Slack threads

Adding a Note

In the feedback detail view, find the Admin Notes section. Type your note and click Add Note. Notes are timestamped and attributed to your user account.

Note Visibility

Admin notes are private to your team. Users who submitted feedback never see these notes. This makes notes safe for candid internal discussion.

Here is a proven workflow for managing feedback effectively:

Daily Review (5 minutes)

  1. Open your project feedback inbox
  2. Filter to Negative feedback
  3. Scan for critical issues and escalate any that need immediate attention
  4. Archive obvious spam or duplicates

Weekly Triage (30 minutes)

  1. Filter to Escalated feedback
  2. Review each item and update admin notes with investigation findings
  3. Create tickets in your issue tracker for confirmed bugs
  4. De-escalate and archive resolved items

Monthly Analysis

  1. Review feedback trends over the past month
  2. Look for patterns in negative feedback
  3. Share positive feedback highlights with your team
  4. Adjust your product roadmap based on user sentiment

Team Collaboration

Qaid supports team access to projects. Invite team members from the project Settings tab.

Roles

  • Owner: Full access including billing and member management
  • Member: Can view and manage feedback but cannot modify project settings

Inviting Members

  1. Go to your project Settings
  2. Click Invite Member
  3. Enter their email address
  4. They receive an invitation to join your project

Team members see the same feedback inbox and can add admin notes, archive items, and manage escalations.

Next Steps

Now that you know how to manage feedback, explore these related guides:

Your feedback inbox is now ready to capture valuable user insights. The most successful teams check their inbox daily and act on negative feedback within 48 hours. Start collecting feedback today and watch your product improve with every submission.

Back to all articles