Six Ways to Ask
Pick the input that fits the page: faces, stars, thumbs, NPS, a 1 to 5 scale, or comment only.
New accounts get 30 days of Pro free. No credit card. Start Free
Every report carries console, network, and click context so you can reproduce what broke on the live site. Then customize the widget, triage, and send reports where your team works.
Start with 30 days of Pro free, no credit card. Then Free forever: 3 sites, 150 reports/month.
This is the part that turns a complaint into a fix, and it is not an upgrade. Free, Pro, and Max all collect it on every report so you can reproduce production bugs from the report itself.
The launcher is yours to shape. Every setting below lives in the Widget page of the dashboard, with a live preview beside the form.
Pick the input that fits the page: faces, stars, thumbs, NPS, a 1 to 5 scale, or comment only.
Rewrite the header, panel title, comment label, send and cancel buttons, the thank you message, and the validation text. Add an extra prompt and placeholder when you need one more answer.
Set the accent, panel, header, border, and text colors, plus the font family, so the launcher matches your site instead of announcing a third party tool.
Keep the launcher floating in a corner with your own side and bottom offsets, or render the panel inline in a container you name. Auto tuck keeps a floating launcher out of the way.
Turn on the JavaScript error prompt and the panel offers itself the moment a visitor hits an uncaught error, while the details are still fresh.
Start collecting console and network context from page load instead of from the moment the panel opens, so the report includes what happened before the visitor gave up.
Ask for an email address when you want to reply, or leave it off and keep submissions anonymous.
The free plan shows a small FeedBlox badge on the widget. Pro and Max can turn it off.
Pro and Max let visitors attach up to 5 files to a report.
Visitors capture the page and mark the part that is wrong, so you are not guessing which button they meant.
Up to 30 seconds on Pro and 60 seconds on Max, for the bugs that only make sense in motion.
Pro accepts images up to 8 MB and video up to 32 MB. Max raises that to 25 MB and 200 MB.
Every submission lands in one list with the comment, sentiment, page, browser, and timestamp already attached.
Narrow to praise, neutral, complaints, or bugs when you want one kind of signal instead of the whole stream.
Combine triage status and any tags your rules applied, so a filtered view matches how your team actually works.
Search across comments and metadata to find the report someone mentioned in standup.
Open a row to read the comment beside the page URL, the site, the user agent, and the full client debug payload.
New reports raise an in app notification, and the API can send email alerts when your deployment enables them.
Move a report through Open, In Review, and Done. The triage board shows how many of your reports are cleared.
Tag reports so related feedback groups together, then filter the inbox by those tags later.
Write rules that tag a report on arrival when the sentiment matches, when the comment contains a phrase, or both. Rules can be reordered, turned off, and deleted.
Add HTTPS endpoints per site and receive JSON on every new report, signed with your secret so you can verify it came from FeedBlox.
Filter a webhook by tags so Slack, Linear, or your own service only hears about the reports that matter to it.
Fire a test delivery from the dashboard and confirm your endpoint accepts the payload before real reports depend on it.
Create an API key and connect Cursor or another MCP client. The agent can call list_sites, list_inbox, get_feedback, get_analytics, and update_triage. Pro and Max.
A 30 day bar chart shows praise, neutral, and complaints stacked per day, so a bad release is visible rather than anecdotal.
One donut gives you the current split at a glance, per site and per range.
Deepsite chat: ask what the main themes are, how sentiment is trending, or what to triage first. Answers come from that site's reports - not an automatic summary on every submission. Pro and Max.
Add a site, prove you own the domain with a meta tag, then install. Nobody can point your widget at a site they do not control.
Invite teammates to a site as admin, member, or viewer. Only the owner manages members, and viewers cannot change your widget.
Issue and revoke keys for MCP access without handing anyone your password.
Subscriptions run through Polar. Cancel whenever you want and the account drops back to Free instead of locking you out.
The widget does not set tracking cookies on your visitors to capture feedback.
The element trail records the structure of what was clicked, not the text on the page, so private content does not travel with the report.
The widget data page lists exactly what a report can contain, so you can answer a privacy question without reading our source.
The difference is volume, media, and team size. The debug context that makes a report useful is on every plan.
| Feature | Free | Pro | Max |
|---|---|---|---|
| Price | $0 | $9/mo launch pricing | $49/mo |
| Free trial | Not needed | First 30 days for every new account, no card | Not included |
| Sites | 3 | Up to 10 | Up to 20 |
| Reports | 150 per month | Unlimited | Unlimited |
| Client debug on every report | Yes | Yes | Yes |
| Screenshots and recordings | No | Up to 30s, 8 MB images, 32 MB video | Up to 60s, 25 MB images, 200 MB video |
| Attachments per report | None | 5 | 5 |
| Collaborators | Single user | Yes | Yes |
| Webhooks and automations | No | Yes | Yes |
| MCP for Cursor | No | Yes | Yes |
| FeedBlox badge on the widget | Shown | Optional | Optional |
Verify your site, paste one script tag, and watch the first report arrive with its debug attached.