Plain-English definitions of feedback management, product roadmap, and changelog terms — written by people who have shipped them, not a marketing dictionary.
A public or semi-public surface where customers can post requests, complaints, and ideas, and where other customers can vote and comment.
In Hollahoop the board is per-project. You can keep it fully open, ask for an account before posting, or run it private with magic-link access.
A way for customers to signal demand by upvoting an existing feedback post instead of duplicating it.
Hollahoop catches near-duplicates as users type and nudges them to vote on the existing post — so a feature with 200 votes is genuinely 200 customers, not 30 customers and 170 duplicate threads.
A public or internal view of what your team is going to build, ordered by intent and not by exact dates.
Roadmaps in Hollahoop have seven default stages: Backlog → Triage → Planned → In progress → DevOps → Shipped → Won’t do. Every card is a feedback post being moved by someone, so customers see their request progressing.
A reverse-chronological feed of what shipped. Lives at a public URL and ideally has its own RSS feed.
Hollahoop turns completed feedback posts into changelog drafts automatically so the loop closes itself: you announce something to the same audience that asked for it.
A roadmap your customers can read. Builds trust because people stop wondering "is anyone going to fix this?".
Public roadmaps work best when they’re honest about uncertainty. We default to stage labels, not dates.
A protocol that lets AI agents call tools on a remote server. Think of it as "REST for chatbots", but typed and discoverable.
Hollahoop ships an MCP server out of the box. Claude, Cursor, ChatGPT and any other MCP client can list posts, draft changelog entries, and update statuses without learning a new API surface.
The umbrella term for organising what customers tell you — feedback, support tickets, NPS, sales calls — into a usable signal.
Hollahoop covers the public-facing slice of VoC: posts, votes, comments. Pairs well with whatever you use for support tickets and call notes.
The cycle of receiving customer input, deciding what to do, building it, and reporting back.
A loop only works if all four steps are visible to the same people. That’s why feedback / roadmap / changelog living together matters.
A single-question survey: "How likely are you to recommend us?". Useful as a trend, dangerous as a target.
A customer who opted in to receive an email when a new update ships.
Hollahoop keeps subscribers per-project with a one-click unsubscribe token. No external email list service required.
A specific suggestion for something you should build. Different from a bug report or a complaint.
In Hollahoop, the post type is the same — what differs is what customers vote on and what your team prioritises.
The first decision after a post arrives: is this a duplicate, is it scoped, does it belong on the roadmap?
There’s a dedicated Triage view in Hollahoop with a single feedback post in focus, so you can move through inbox-style without losing context.
A board with columns where work moves left to right as it progresses.
The Hollahoop roadmap is Kanban by default; cards are draggable and dropping a card on a new column changes its status.
A pricing tier that stays free indefinitely — no trial countdown, no usage cliff that flips it into a paywall.
Hollahoop’s Free plan is permanent. Paid plans exist for teams that want a custom domain, SSO, or higher API rate limits, but the public board, roadmap, changelog, and MCP server work the same on every tier.
An ancient-but-effective format for publishing a feed that anyone can subscribe to without giving you their email.
Every Hollahoop changelog has an RSS feed at `/<project>/changelog/rss.xml`.
