Send feedback

{status === 'done' ? (

Thanks, feedback received.

) : ( <>

setMessage(e.target.value)}
                placeholder="Tell us what you think..."
                style={{ width: '100%', boxSizing: 'border-box', minHeight: 80, padding: 10, fontSize: 13, borderRadius: 6, border: '1px solid #e5e7eb', resize: 'vertical' }}
              />
              <button
                onClick={submit}
                disabled={status === 'loading'}
                style={{ marginTop: 10, width: '100%', padding: 9, background: '#F59E0B', color: '#000', border: 'none', borderRadius: 6, fontWeight: 600, cursor: 'pointer' }}
              >
                {status === 'loading' ? 'Sending...' : 'Send'}
              </button>
              {status === 'error' && <p style={{ color: '#ef4444', fontSize: 12, marginTop: 8 }}>Failed. Please try again.</p>}
            </>
          )}
        </div>
      )}
    </>
  );
}
```

Use it in your layout:

```tsx
// app/layout.tsx

return (
    <html>
      <body>
        {children}
        <FeedbackButton
          publishableKey={process.env.NEXT_PUBLIC_NORDVA_KEY!}
          userId="user_abc123"
        />
      </body>
    </html>
  );
}
```

## Option C: A hosted form (a link)

No code on your site: a page of its own at `https://widget.nordva.dev/feedback/<your-slug>`, for an email footer, a support page or a QR code. It is off until you switch it on, in the dashboard under **Feedback Routing** → **Hosted form**, or with `PATCH /v1/project` and `{ "hosted_feedback": true }` (an AI agent uses `update_project`). Off again, the link shows "not switched on".

The page has type buttons (Bug, Idea, Praise, Question) and carries the browser and device labels, like the widget. Options in the link:

| Option | Example | |
|---|---|---|
| `types` | `?types=bug,idea,billing` | Which type buttons, in order. `?types=false` for none |
| `rating` | `?rating=stars` or `?rating=emoji` | A 1 to 5 rating |
| `email` | `?email=1` | An email field for a reply |
| theme | `?accent=%23e11d48&mode=dark` | Same as the other hosted widgets |

A Cloudflare Turnstile check and a limit of 10 messages per visitor per hour guard it, and messages count toward the monthly feedback limit. They are stored and sent as the `feedback.created` webhook; to also send them to your routing destinations, tick **Send to the destinations below** (`"route_hosted_feedback": true`).

## View and triage feedback

In the [Nordva Launch dashboard](https://app.nordva.dev) → **Feedback**, or via the API:

```bash
curl "https://api.nordva.dev/v1/feedback?classification=bug&status=open" \
  -H "Authorization: Bearer nv_live_YOUR_SECRET_KEY"
```

## Reply from the inbox

Open the item in the dashboard and write under **Reply**, or send `POST /v1/feedback/<id>/reply` with `{ "body": "…", "channel": "…" }` (an AI agent uses `reply_to_feedback`). Pick how it reaches them:

| `channel` | Reaches | Needs |
|---|---|---|
| `email` (default) | One plain-text email with your words and theirs quoted under them, from your project's name. Their answer goes to your project's reply-to address (Settings), or to `reply_to` if you send one. With neither, nothing is sent (`REPLY_TO_REQUIRED`): your sign-in address is never used. | The email they left. |
| `notification` | A notification in that person's bell, titled with `subject` (default "Reply to your feedback"), at most 2,000 characters, category `feedback`. Counts against the month's notifications. | The `user_id` the feedback was sent with (`data-user-id` on the widget). Otherwise `FEEDBACK_NO_USER_ID`. |
| `none` | Nobody: the reply is kept on the item, for when you answered somewhere else. | Nothing. |

The item becomes reviewed, and the reply stays listed on it with its `channel`.

At most 20 replies a day per project. Past that, or when the day's email allowance is used up, nothing is sent (`REPLY_LIMIT_REACHED`) and the address is right there to answer from your own email.

## Many at once, and CSV

Tick items in the inbox to mark them reviewed or resolved, or set their category, together; the API takes up to 100 ids in `PATCH /v1/feedback/bulk` (`bulk_update_feedback` over MCP). **Export CSV** (Indie and up) downloads the inbox as it is filtered: id, date, category, status, rating, the text, summary, email, user id, page, browser, device, the entry it shipped in and the number of replies. `GET /v1/feedback/export` gives the same file as a link that works for 15 minutes.

## Tell people when it ships

When feedback turns into a changelog entry, link the two: in the dashboard, pick the entry under **Shipped in** on the feedback item, or send `{ "linked_entry_id": "ce_…" }` to `PATCH /v1/feedback/<id>`. An AI agent can do it with `update_feedback`.

When that entry is published, the item is marked resolved and, if the person left an email with their feedback, they get one message: what they asked, the entry's title and its link. It is sent within a few minutes of publishing, once, and never for an entry that is still scheduled. Nothing is sent to people who left no email.

## Route feedback to Slack or Linear

In the dashboard → **Feedback Routing**, connect a destination and tick the categories it should get: for example bugs to Linear, and ideas and praise to Slack. With every category ticked (the default) it gets everything. Over the API, send `categories` beside the destination's fields, such as `{ "destination": "linear", …, "categories": ["bug"] }`; left out, every category is sent. Feedback from the [hosted form](#option-c-a-hosted-form-a-link) is forwarded only when you switched that on.

Source: https://docs.nordva.dev/guides/feedback-react/