Progress without writing emails
Customers hear about their requests as they move, without anyone writing a word. Each teammate picks what they hear about, so engineers can follow only the Bugs board.
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 3 · Ship and tell · Notifications & digest
HeedPost sends email because someone asked to know: their request moved, someone replied, they were mentioned, something they asked for shipped. Everyone controls their own, every email has a way out, and each arrives in the reader's language.
Try it
Flip the switches and see which of this week's emails Dana would get.
Step by step
A post moves, someone replies, someone is mentioned, or a release ships.
Followers, the person named, the people who asked, or subscribers.
Everyone's own choices for that workspace decide what they get.
The language is chosen when the email is sent, so it's always the reader's current one.
Every email can turn off email from that workspace in one click.
Who it's for
Customers hear about their requests as they move, without anyone writing a word. Each teammate picks what they hear about, so engineers can follow only the Bugs board.
Email comes from “Acme via HeedPost”, and replies go to your own address. Pause email while you import and tidy. Sign-in links and invitations still arrive.
Every email arrives, and arrives once, even when something retries. An address that hard-bounces isn't tried again, so one bad list doesn't hurt everyone's sending.
The details
Each person sets what they get in their own settings, per workspace. A link in every email turns off everything from that workspace in one click.
Pick the digest's day, or don't send one. You can pause all email from the workspace while you move in or tidy up. Sign-in links and invitations still go out, so nobody is locked out.
The API, the events, and what you can rely on when you build on it.
Each customer has seven switches per workspace: status changes, comments, replies only, mentions, releases they asked for, every release and the digest. A teammate has three more: new posts, posts they own, and posts held for review. A new switch starts the way HeedPost already behaved, so nobody is surprised. Imported people start with their own requests switched on and broadcasts off.
Each email is sent at least once, with retries, and a retry never sends it twice. An address that bounces hard is kept off every future send. Every email has a plain-text version and a reply-to address.
Each email is written in the recipient's language when it's sent: their own choice first, then the language they last signed in with, then the workspace default. The sender is "your workspace via HeedPost", so no workspace can pose as somebody else.
A bulk status change holds its emails for the eight-second undo, then sends them together.
Email settings belong to each person and aren't in the public REST API.
1 event type from this feature reaches your webhooks. Each line shows what its data carries.
digest.sentposts, shippedPlans
Free is $0, Plus $29 and Pro $59 a month, per workspace. Never per seat. Every plan, line by line
| Feature | Free | Plus | Pro |
|---|---|---|---|
| Every email type and switch | Included | Included | Included |
| Weekly digest | Included | Included | Included |
| Pause workspace email | Included | Included | Included |
| Emails a month | 1,000 | 10,000 | 25,000 |
| Email packs and your own SMTP | Not included | Packs | Both |
Something else? Write to us, and a person answers.
Not by the import. Afterwards, they hear about their own requests.
Yes. Each person chooses the boards they hear about.
Yes. Pause the workspace's email. Sign-in links and invitations still go out, so nobody is locked out.
Yes. Every kind of email has its own switch.
Your team, and people who posted, voted or commented recently, once you choose a day.
"Your workspace via HeedPost", with your reply-to address.