Feedback from the right screen
Add “Suggest a feature” to your app's menu, and the request arrives from the screen it's about, with the customer's account attached.
Private previewWorkspaces are by invitation
Skip to content01Collect
Feedback boardsBoards that ask for exactly what your team needs to act.Votes, comments & mentionsOne vote per person, threads with mentions, and notes only your team sees.In-app widgetFeedback from inside your product, from customers who are already signed in.02Understand
Merge & duplicatesTen posts asking for the same thing become one, with every vote kept.User segments & revenueProSee which requests your biggest customers want, in dollars.InsightsWho reads, what's rising, and whether you answered.HeedPost AIPlus and ProTags, duplicate judging, drafts, summaries, themes and Ask, each with its own switch.03Ship and tell
Roadmap & statusesMove a post and everyone who asked hears, in your own status words.ChangelogRelease notes linked to the requests behind them, mailed to everyone who asked.Notifications & digestThe right email to the right person, and a switch for every one.04Run it
Activity logEvery change, who made it and when, a day at a time.Team, roles & sign-inUnlimited teammates, clear roles, and sign-in your way.Branding, domain & languagesYour logo and colour, your own domain, and 21 languages.ImportMove in from Canny, Featurebase or UserJot, with nobody emailed.05Connect
Slack & issue trackersPlus and ProSlack threads, and issues in Linear, Jira, GitHub or ClickUp that move posts back.MCP serverPlus and ProYour AI agent can read, file, vote and ship, as you.REST APIPlus and Pro27 operations and one key: build anything on top of your feedback.WebhooksPlus and Pro110 events, signed and retried, the moment they happen.Chapter 1 · Collect · In-app widget
Add a launcher to your product. It opens your board, the post form, the roadmap or the changelog in a panel over your page, in the customer's language, already knowing who they are.
Try it
Press the launcher. Switch between a signed-in customer and a visitor, and try another language.
Step by step
Copy one script tag from your workspace and paste it before the closing body tag.
Choose the board the panel opens on. The roadmap and changelog sit beside it as tabs.
If you like, your server signs a short token for whoever is logged in, and the tag passes it on.
Use the launcher, or open the panel from your own menu item with Heedpost.open().
Post a private test, check that the keyboard and the close button work, and try it on a phone.
Who it's for
Add “Suggest a feature” to your app's menu, and the request arrives from the screen it's about, with the customer's account attached.
Not only the vocal few who find your board. Put their company in the sign-in token, and on Pro every post and vote counts toward that company's revenue.
The widget is walled off from your page's styles and scripts, and your server says who the customer is. Call Heedpost.locale("ar") and it switches language, right to left.
The details
Paste one script tag into your app. It's served from your own workspace's address and already carries your name and colour. Point it at a board.
The panel opens on the board you name, with your roadmap and changelog as tabs beside it. A dot on the launcher shows when a release is new to the reader. Start with one clear job, like "Suggest a feature" in your app's menu.
If your server signs a short token for the customer who's logged in, they're signed in to the widget before it appears. Their posts and votes arrive with their name, and on Pro with the segment they belong to. Without a token the widget still works, and people sign in inside it.
The widget speaks the reader's browser language, then your workspace's default. If your app is in one language, pin it.
The API, the events, and what you can rely on when you build on it.
Add data-badge="label" to show a small pill beside the launcher with the number of releases the reader hasn't seen yet.
<script src="https://acme.heedpost.com/widget.js" data-board="feedback" data-identity="<token your server signed>" data-locale="de" async></script>
window.Heedpost.identify(token) // sign a customer in, or out with null window.Heedpost.open() window.Heedpost.close() window.Heedpost.locale("ar") // a page that changes language without a reload
The token is a JWT signed with HS256, using your workspace's single sign-on secret. It needs sub, email, iat and exp. You can add name, which we use the first time we see someone, and user_segment, which we read again at every sign-in. A token can be up to two minutes old, and can't be dated in the future.
Sign tokens on your server, never in the browser. When you rotate the secret, every token signed with the old one stops working.
Your page's styles can't reach the launcher, and the panel can't reach your page. A widget session never sees who voted or what a customer segment is worth, even when the token belongs to an admin.
The widget is set up with its tag and driven by its JavaScript API, above, not by the REST API.
3 event types from this feature reach your webhooks. Each line shows what its data carries.
post.createdtitle, board_id, is_privatevote.addedcountcomment.createdpost_id, is_internalPlans
Free is $0, Plus $29 and Pro $59 a month, per workspace. Never per seat. Every plan, line by line
| Feature | Free | Plus | Pro |
|---|---|---|---|
| The widget | Included | Included | Included |
| Customers signed in by your token | Not included | Included | Included |
| Segment in the token, counted as revenue | Not included | Not included | Included |
Something else? Write to us, and a person answers.
No. Without a token the widget still works, and customers sign in inside it. A token saves them that step, and it needs Plus or Pro.
Yes. Call window.Heedpost.open() from any button or menu item.
No. The launcher is sealed off from your page's styles, and the panel runs in its own frame.
Yes. The panel has its own small-screen layout. Try it on a phone before you publish.
Ask your server for a fresh one and pass it to Heedpost.identify(). Don't fall back to an older token, or to someone else's.
Yes. They can read everything public, and sign in inside the widget to post or vote.