Chirio
Get Started
Introduction
Quickstart
How Chirio works
Authentication
MCP server
Platforms
Overview
Instagram
Threads
X
LinkedIn
Supa Hub
Guides
Connect accounts
Publish a post
Media requirements
Carousels
First comments
Idempotency and retries
Account lifecycle
Revocation and deletion
The dashboard
Products
Screenshots
Feedback boards
What's new
Inbox
Messages
Site analytics
Page comments
Billing
Plans
Metering
Quotas
Api Reference
Overview
Accounts
Posts
Errors
Changelog
Roadmap
TrademarkTrademark
Ctrl k
Search…
Sign up
Chirio
Get Started
Introduction
Quickstart
How Chirio works
Authentication
MCP server
Platforms
Overview
Instagram
Threads
X
LinkedIn
Supa Hub
Guides
Connect accounts
Publish a post
Media requirements
Carousels
First comments
Idempotency and retries
Account lifecycle
Revocation and deletion
The dashboard
Products
Screenshots
Feedback boards
What's new
Inbox
Messages
Site analytics
Page comments
Billing
Plans
Metering
Quotas
Api Reference
Overview
Accounts
Posts
Errors
Changelog
Roadmap
TrademarkTrademark© Dopler. All rights reserved.
Built with Aveiro

Feedback boards

Public feedback boards with votes, comments, a roadmap and a changelog, plus the widget, pin feedback and API that put them inside your product.
Updated 4 days ago
Screenshots
What's new
A board is a public place for your users to report bugs, request features, give feedback and ask questions, at chirio.dev/b/your-board. People upvote and comment, your team answers and moves posts along, and an agent can work the queue through the API or the MCP server. Every board post is also an item in your inbox, so the same queue serves your team, your agent and your users.

What a board has

  • Roadmap. Posts sit in kanban columns, Under review, Planned, In progress and Done, taken from each item's status. The team drags cards between them. A list view groups the same posts by progress.
  • Roadmap projects. The team can group posts into projects with a start and target date. A project's progress is how many of its posts are done, so moving a card moves the project too. Projects are made in the dashboard, and public ones show above the board's columns.
  • Votes and comments. Signed-in people upvote and comment, and comments take replies. Answers from your agent show as the board's assistant.
  • What's new. A changelog your users read on the board and in the widget. See What's new.
  • Follows. Anyone with a Chirio account can follow a board and switch between the boards they follow.
People sign in on the board with an email link. A board can instead accept posts only from your product's own signed-in users (below).

Create one

In the dashboard, Boards creates and edits boards and shows each one's setup steps. With an API key:
curl https://chirio.dev/api/v1/boards \
  -H "Authorization: Bearer chirio_sk_..." \
  -H "Content-Type: application/json" \
  -d '{ "slug": "acme", "name": "Acme feedback", "destination": "acme", "locale": "en" }'
POST /api/v1/boards creates a board, or changes yours if you already own that slug. Slugs are global across Chirio. destination is the its posts go to; is or . lists your boards.
inbox destination
locale
en
hu
GET /api/v1/boards

Put it in your product

One script tag adds a feedback button, and a What's new button once the changelog has an entry:
Opening New post takes a screenshot of what is on screen, without the widget itself, and attaches it to the form, where people can drop numbered comments on it. The buttons notice what else floats in their corner, such as a chat launcher, and sit above it. Options:
Attribute
Effect
data-position="left"the left corner
data-offsetdistance from the corner
data-labela text button instead of an icon
data-launcher="false"no buttons; open it from your UI
data-capture="false"no screenshot of the page
data-changelog="false"no What's new
data-feedback="false"What's new only
data-changelog-triggeryour element opens What's new
data-langthe widget's language
data-hotkeythe pin mode key, or off
data-preload="false"load only when asked
data-lang defaults to the page's own <html lang>, then the board's. data-preload="false" suits a public landing page: the widget fetches its token and scripts only when someone asks for it. From your code: window.Chirio.open("new"), .close(), .identify(token), .openChangelog() and .closeChangelog().

Your own drawer

An app with its own design system can keep its own buttons and drawer. Set data-launcher="false", then let the widget fill your drawer's body:

Pin feedback

Early access
Pin feedback and the options below are switched on per workspace while they roll out. Without them, the widget opens its panel as described above.
With pin feedback, the feedback button points at the page instead of opening a panel. People hover to outline an element, click it, write a note and send it: the post reaches the board with a screenshot of that spot, the pin drawn in. A toolbar at the bottom holds the other kinds as icon buttons: an idea or a question, the whole screen, What's new and the board.
A person's earlier pins on the page come back as numbered markers with their threads, so they read your answers and reply where they asked. Pins wear their author's avatar, and a thread shows names, times and a via Claude mark on your agent's answers, the same look as page comments.
  • The C key toggles pin mode, outside text fields, for people your token URL vouches for. Everyone else gets nothing, so the tag can sit on a public landing page.
  • From your own button, call if (window.Chirio?.pin?.()) return; before opening your drawer. pin() returns false when the board takes no pins, so your drawer opens as before.
  • Events. The window gets chirio:pins once it is known whether the board takes pins, and chirio:pinning with { detail: { on } } as the mode starts and stops.
Two more options ride on the same rollout:
  • Screenshot-first form. The page's screenshot opens large: click to pin comments on it and post, with no type or title to fill in. A post without a title takes its first pinned comment.
  • Only the team. A toggle in the widget keeps a post off the public board. It lands in your inbox with public: false, and the team and the person who sent it still see it and talk on it.

Know who is posting

From Indie up, people can post as themselves without a second sign-in. Your server asks Chirio for a token:
Pass data-token-url="/api/chirio-token" on the widget, or call window.Chirio.identify(token). A token lasts 12 hours and works on that board only. It can also carry avatar and mrr (in cents). Without a token, the panel links to the board's email sign-in.
The plan rides along for your team only: the board never shows it. Paying reporters are listed first in the inbox and in the agent's queue, and GET /api/v1/inbox?paid=true keeps only them. A board set to customers-only posting accepts posts only from people your product vouched for this way.

Act for your users from your server

If your users stay inside your app, your server can act for them by your own user id: list and create posts with GET|POST /api/v1/boards/:slug/posts, read one with GET /api/v1/boards/:slug/posts/:id, vote with POST .../:id/vote (a toggle) and comment with POST .../:id/comments. Each call names the user as { id, name }. Keep the key on your server.

Answering

GET /api/v1/inbox?needsReply=true is the support queue: posts whose last word is a user's. POST /api/v1/inbox/:id/comments with { body } answers publicly and takes the post out of the queue. POST /api/v1/inbox/:id changes its status (which moves its card), hides it with public: false, or edits the title. See Inbox.

Your look and your domain

From Indie up, a board can carry your product's logo and wordmark, a link back to your product, its own colours and theme, and its own domain, such as feedback.example.com, connected from the board's settings.
Boards on Free and Indie show a small Built with Chirio badge. From Studio up there is no badge, unless you switch it on to keep it.

Limits by plan

Plan
Boards
Your users and branding
Free1no
Indie3yes
Studio10yes
Scaleunlimitedyes
Boards, posts, votes, comments, pins, the roadmap and the changelog cost no units. Creating a board past the cap is a 403 board_limit; changing an existing one never is. See Plans.
<script src="https://chirio.dev/board-widget.js" data-board="acme" async></script>
const stop = window.Chirio.embed(element, "new"); // or "changelog"
// Your route, e.g. GET /api/chirio-token, behind your own session
const res = await fetch("https://chirio.dev/api/v1/boards/acme/identify", {
  method: "POST",
  headers: { authorization: `Bearer ${process.env.CHIRIO_API_KEY}`, "content-type": "application/json" },
  body: JSON.stringify({ user: { id: user.id, name: user.name, email: user.email, plan: "pro", paid: true } }),
});
return Response.json(await res.json()); // { token, expiresAt }