Private previewWorkspaces are by invitation

HeedPost

01Collect

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.
AIDocsHelpPricingBlog

Collect

Understand

Ship and tell

Run it

Connect

Request an inviteSign in

DocsGuides

Add HeedPost to your product.

Let customers share feedback, follow the roadmap and read updates without leaving the page they were on.

Plan Every planSigned-in customers Plus and Pro

Portal or widget?

The public boarda full destination

A shareable board with its own address, navigation and search. Customers can bookmark it and you can link to it from anywhere.

The widgetinside your product

A focused panel opened from your app. Customers stay on the page they were on, and if they're signed in, they don't have to say who they are.

Most teams use both: the board for the world, the widget for the people already in the product.

Install the script

Copy the snippet from Settings › Widget and place it once, before the closing body tag, on the pages where HeedPost can open.

HTML
<script src="https://acme.heedpost.com/widget.js"
        data-board="feedback"
        async></script>

The address is your own workspace's. The script is served by your workspace and carries its name and colour, so there's no shared script host to load it from. Copy it from your settings instead of typing it.

The launcher lives in a Shadow DOM, so your page's CSS cannot reach it, and the panel is an iframe, so ours cannot reach your page.

Attributes

data-boardthe board

The address of the board the panel opens on, like feedback.

data-identityoptional

A token your server signed for the customer who is logged in. See identifying customers.

data-localeoptional

The language your page is written in, like de. Without it the widget follows the reader. The tags.

data-badgeoptional

label adds a pill beside the launcher saying how many releases are new to the reader, like “2 new releases”. Without it, a dot on the launcher says the same.

HTML
<script src="https://acme.heedpost.com/widget.js"
        data-board="feedback"
        data-identity="<token your server signed>"
        data-locale="de"
        data-badge="label"
        async></script>

What is in the panel

The panel opens on the board named by data-board, with Roadmap and Changelog as tabs beside it. A dot on the launcher marks a release the reader has not seen, and opening the Changelog tab clears it.

The launcher is always shown, and no attribute hides it. Opening the panel from your own button adds a second way in. It doesn't replace the launcher.

The JavaScript API

Four functions on window.Heedpost.

JavaScript
window.Heedpost.open();                // open the panel
window.Heedpost.close();               // close it; focus returns to the launcher
window.Heedpost.identify(token);       // sign a customer in, or out with null
window.Heedpost.identify(() => fetchToken());  // or hand it a function
window.Heedpost.locale("ar");          // a page that changes language without a reload

A Give feedback item in your own menu can open the panel without anybody hunting for the launcher:

JavaScript
document.querySelector("#feedback").addEventListener("click", () => {
  window.Heedpost?.open();
});

The script is async, so window.Heedpost is not there on the first paint. Guard the call the way the snippet does. Nothing queues a call made too early, and a handler wired at the top of your own bundle will run before ours has.

Identify signed-in customers

Pass a verified identity from your server, so posts and comments arrive with the customer's name. It's the same token single sign-on uses, signed the same way, and its claims are here. It needs Plus or Pro. Never sign it in the browser.

In the attribute

The two minutes start when you render the page, and the widget uses the token when someone first presses the launcher. A reader who opens it later, or a page cached for ten minutes, gets the public board, and your console notes that the token was too old. So the attribute suits a page someone acts on straight away.

As a function

Otherwise, give window.Heedpost.identify a function that fetches a fresh token from your own server, or returns null for nobody. The widget calls it only when it needs a token: on the first press, after locale(), and before its own session ends. The reader stays signed in however long the page is open.

HTML
<script src="https://acme.heedpost.com/widget.js"
        data-board="feedback"
        onload="Heedpost.identify(() =>
          fetch('/heedpost-token').then((answer) => answer.text()))"
        async></script>

After your app signs somebody in

A single-page app that signs someone in without reloading calls window.Heedpost.identify(token) with a fresh token, and identify(null) signs them out of the panel. The panel's own session lasts twelve hours.

A token we will not accept is not an error your users see. The panel opens as the public board and one line in the browser console says why, which is where the developer who wrote the tag is looking.

Languages

The widget follows the reader's browser, then your workspace's default language. Name your page's language with data-locale, or call window.Heedpost.locale(tag) when your page changes language without a navigation. Changing it while the panel is open draws the panel again in the new language, from its first page.

en ar bn de es fr he hi it ja ko ms nl pt-BR ru sw ta tr ur zh-CN zh-Latn-pinyin

zh-Latn-pinyin is Chinese in Hanyu Pinyin. A regional tag such as de-AT is read as the nearest of these, one we do not speak is ignored, and locale(null) hands the choice back to the browser. Arabic, Hebrew and Urdu draw right to left.

Test it

  1. Load a page with the script installed.
  2. Open the widget from the launcher, and from your own button if you added one.
  3. Submit a private test post and check it landed on the right board.
  4. Check keyboard focus, closing with Escape, and the layout on a phone.

Troubleshooting

Nothing opens

Check the tag loads from your workspace's own address and appears once. A call to open() before the script has loaded does nothing: guard it with window.Heedpost?.open().

The wrong board

data-board takes the board's address, not its name. Check the board is one the reader may see.

Signed out

A token in the attribute has to be used within two minutes of the page loading, and the console says when one was too old. Give identify() a function instead.

Styles clash

They cannot: the launcher is in a Shadow DOM and the panel is an iframe. If something looks wrong, it is worth a message to us.