Feedback & Insights

Collecting Feedback

Three ways to collect feedback from your users — the embedded widget, the REST API, or manual submission in the dashboard.

You can collect feedback in three ways: the feedback widget embedded on your site, the REST API for programmatic submission, or manual entry from the dashboard.

Option 1: Feedback widget

The feedback widget is a small button that floats on your site. When clicked, it opens a form where users can submit feedback without leaving the page.

Getting the embed code

Go to Feedback → Board in your dashboard.

Copy the embed snippet from the Widget tab.

Paste it into your site's HTML before the closing </body> tag.

<!-- Paste before </body> -->
<script
  src="https://cdn.futurebase.ai/feedback.js"
  data-project-id="YOUR_PROJECT_ID"
  async
></script>

The actual embed snippet in your dashboard contains your real agent ID. Use the snippet from the dashboard, not this placeholder.

Framework-specific setup

Use Next.js's Script component to load the widget after the page is interactive:

import Script from "next/script";

export default function Layout({ children }) {
  return (
    <html>
      <body>
        {children}
        <Script
          src="https://cdn.futurebase.ai/feedback.js"
          data-project-id="YOUR_PROJECT_ID"
          strategy="lazyOnload"
        />
      </body>
    </html>
  );
}

Widget configuration

You can configure the widget appearance and behavior from Feedback → Board:

OptionDescription
Button labelText shown on the floating button (default: "Feedback")
Button positionBottom-left or bottom-right
Accent colorMatches your brand color
Prompt textPlaceholder inside the feedback textarea
CategoriesOptional dropdown to let users tag their feedback (Bug, Feature, Other)

Option 2: REST API

Use the REST API to submit feedback programmatically — for example, from an in-app NPS survey, a post-interaction prompt, or a backend system.

Authentication

All API requests require an API key. Get yours from Settings → API Keys.

Authorization: Bearer YOUR_API_KEY

Submit feedback

POST https://api.futurebase.ai/v1/feedback
Content-Type: application/json
Authorization: Bearer YOUR_API_KEY

{
  "content": "It would be great if I could export conversations to CSV.",
  "category": "feature",
  "userEmail": "[email protected]",
  "userName": "Jane Smith",
  "metadata": {
    "plan": "pro",
    "source": "in-app-survey"
  }
}

Request fields:

FieldTypeRequiredDescription
contentstringYesThe feedback text (max 5,000 chars)
categorystringNo"bug", "feature", "other"
userEmailstringNoEmail of the user submitting feedback
userNamestringNoDisplay name of the user
metadataobjectNoArbitrary key/value pairs (plan, version, page, etc.)

Response:

{
  "id": "fb_01J9XXXXXX",
  "status": "received",
  "clustered": false
}

Newly submitted feedback is queued for AI clustering. The clustered field will be true once the AI has processed it and added it to a theme (usually within a few minutes).


Option 3: Manual submission

You can add feedback directly from the dashboard — useful for logging feedback received via email, sales calls, or support conversations.

Go to Feedback → Inbox.
Click Add feedback.

Enter the feedback text, optionally a title and the customer's name and email, then click Add feedback.

It shows up in the Inbox as Added by team and is grouped into a theme like any other feedback.


Working through the Inbox

Feedback → Inbox lists everything, newest first. Filter by status, source or a search term; the filters stay in the URL, so you can share a view. Click an item to read it in full and see its theme, or select several and click Archive. Archived items are hidden unless you pick the Archived status.


Best practices

  • Capture context — pass metadata like the current page, plan tier, or app version. This helps with filtering and clustering.
  • Don't require a login — anonymous feedback is better than no feedback. Collect email optionally.
  • Prompt at the right moment — post-interaction (after a support chat resolves) or post-onboarding are high-signal moments.
  • Keep the form short — a single textarea converts better than a multi-field form.

On this page