Your users report it. Your AI agent ships it.
One script tag on your site. Your own coding agent opens the pull request. The person who reported it hears the day you merge.
The whole loop runs on Free · No credit card
An animated walkthrough of the full Reqio loop. On your site, a visitor picks Make a request, types Slack integration please above a small board of existing requests, and sends it. In your Reqio inbox, the message becomes a managed request card above the rest of the pipeline: category Request, status Needs action, a context note reading Trying to pipe alerts into our team channel, an upvote count that climbs from one to four, and a cumulative MRR figure that climbs from eight hundred forty dollars to three thousand two hundred dollars. The team replies On it, shipping. Status moves to In progress, then to Completed. What your user sees: an in-product notification titled Shipped: Slack integration, saying the thing you asked for is now live, and an email from Reqio arrives beside it, subject Slack integration is live, headlined It's live, marked Completed, Shipped, with a button to see what shipped.
Five ways in, pre-sorted: ideas to a public board, everything else to a private thread.
Before Reqio
Feedback has a habit of dying quietly.
#feedback
Last seen: never
Spreadsheet, row 4,072
Rest in peace, unsorted
That one Slack thread
Scrolled into the void
“We'll circle back”
They did not circle back
Reqio gives it somewhere to land. And somewhere to come back from.
Built-in MCP server
Your AI agent can run this whole thing.
42 tools over OAuth 2.1, no local process. Connect Claude, Cursor, or any MCP client once.
- Role-gated, live, every call. A developer agent gets developer powers. An owner agent gets owner powers. Same permission matrix as the dashboard.
- Structurally excluded: billing, project deletion, token issuance. No tool exists, so no prompt injection can reach them.
- Destructive tools ask twice. Deletes, member removal and announcements need an explicit confirm. One misread prompt can't blast your users.
$ mcp connect https://reqio.app/p/my-project/mcp Connected. 42 tools available. $ call list_features --status needs_action --sort mrr 1. SSO login 4 votes $3,200 MRR 2. Webhook retries 2 votes $1,100 MRR $ call get_conversation conv_7r9 [bug] "[user-submitted] toolbar icons overlap on Safari" reported by jamie@acme.co, unread $ call reply_conversation conv_7r9 “Fixed in v2.4, deploying today. Thanks for the console dump, it helped.” Reply sent. User notified in-widget and by email.
The whole loop
The bug came back as a pull request.
An open-source Action, running in your CI on your model key. Reqio never holds your repo credentials and never sees your code.
Someone hits a bug and reports it in the widget. Page URL, context and a screenshot come with it.
Move it to In progress and the next run picks it up. That's the whole approval. Turn on auto mode and it skips even that.
Your agent opens a pull request carrying the report and a link back to the thread. It can run your tests first.
Review and merge like any other pull request. The request closes itself and the reporter hears. Not shipping yet? Queue it; subscribers hear the day it ships.
Two-way threads
You reply. They actually hear it.
One inbox, one thread. They get your reply in the widget and by email, and hitting reply drops them back into the same thread.
Your Reqio inbox
What the user gets
Prioritize by revenue
The loudest voice isn't the biggest account.
Pass a signed token from your own auth, and every vote carries that account's plan and MRR.
- No SDK to install. A short-lived HS256 JWT, minted with your language's standard library: jose, PyJWT, php-jwt, ruby-jwt, golang-jwt. The dashboard generates the exact snippet for your stack.
- Anonymous by default. Identity is opt-in, and you choose exactly what to attach.
- Signed, verified server-side. Nobody self-reports their own MRR.
Users who feel heard don't churn.
Plain answer
What is Reqio?
Reqio is a two-way, AI-native customer feedback platform. It has three surfaces: an embeddable widget (one script tag, five routed flows), a dashboard with a revenue-weighted backlog and a chat inbox, and a remote MCP server with 42 role-gated tools your coding agent can work over OAuth 2.1.
Two-way, not a board.
Boards collect and go quiet. Reqio answers back: every private submission is a conversation the user can keep, even from their inbox.
Revenue-weighted, not vote-counted.
A signed identity token ties each request to a real account and its MRR. The backlog sorts by who is asking, not how many.
Ships, not just collects.
Your own coding agent opens the pull request in your own repo, overnight if you let it. Boards stop at collecting. This ends in a merge.
Setup
From zero to hearing things in under five minutes.
Paste the script tag
One line, before </body>. Async, Shadow DOM isolated, never touches your styles or your render path.
Make it yours
Color, logo, and position live in the dashboard. Change them any time, no redeploy.
Optional: level up
Add the signed identity token for revenue weighting. Point your AI agent at the MCP server. Both opt-in, both take minutes.
Also in the box
Pricing
No per-user tax, ever.
Unlimited end-users on every plan, including Free. You pay for teammates and usage, never for who shows up.
Questions
The things you'd ask anyway
What is the Reqio MCP server?
Every Reqio project includes a built-in remote MCP (Model Context Protocol) server with 42 tools, secured with OAuth 2.1. AI agents like Claude or Cursor connect once and can triage requests, change statuses, reply to conversations, send announcements, configure the widget, and manage the team. Every call is gated by the connecting user's real role. Billing, project deletion, and token issuance have no tools at all.
Is Reqio just a feature request board?
No. Public feature requests with voting are one of five flows. The other four (bugs, unexpected behavior, feedback, questions) open private two-way threads between the user and your team. A board collects; Reqio also answers back.
How does reply-by-email work?
When Reqio notifies a user by email, the message carries a unique per-conversation reply address. If the user hits reply in their inbox, that reply is verified and lands back in the same thread in your dashboard. No forwarding, no support inbox in the middle.
How is this different from Canny?
Canny is a public voting board. Reqio is a two-way feedback loop: private threads, email replies, revenue-weighted priority, and an MCP server so your AI agent can triage and close requests directly from the backlog.
How much does it cost?
Free runs the entire loop on one project: the widget, two-way threads, MCP write access at 25 calls a day, and 100 REST API calls a day, enough for the GitHub agent loop at its default cadence. No credit card. Paid plans add projects, teammates, revenue weighting, integrations, and higher quotas.
Can Reqio open pull requests in my repository?
Yes. The loop runs as an open-source GitHub Action in your own repository, driving your own coding agent on your own model key. Reqio never holds your repo credentials and never sees your code. Nothing merges without a human, and the whole loop runs on Free.
Does a human stay in the loop?
Always, at the merge, and by default earlier too: the agent only picks up bugs you have moved to In progress, and it can only ever open a pull request, never merge one. Nothing reaches your default branch without your review. Want the fix waiting when you wake up? Turn on auto mode and it claims new bug reports on its own; the pull request stays your gate.