Do we really need a second tool for feedback?
Answer
If you are buying this portal for support questions, probably not. A category, votes and an accepted reply cover what most feedback boards do.
Use case
Feature requests with votes,
and a reply from your team
A question with votes and a reply your team stands behind is already a feedback board. Same portal, same price, one more category. Live in about five minutes.
This is a public board for requests and the replies to them. There is no roadmap view and no changelog.
Free for 7 days. No credit card. Live in about five minutes.
1portal for support questions and requests
5 minfrom sign-up to a live portal
$9one time for a working portal
7 days freeto try it, no card needed
One portal, two jobs
You may not need a second tool.
A support forum and a feedback board hold the same thing: a post, some votes, and a reply. Most teams pay for both.
Say you were pricing a feedback tool like Canny, Upvoty or Featurebase. The question worth asking first is whether the portal you are already buying does the job.
Make a category called Feature requests. Sort the list by votes. Answer the top one in public. That is the board.
Capability
What a feedback board needs, and how the portal does it.
Every row below is on both plans. The plan changes the address and the caps, never the features.
| What a feedback board needs | How the portal does it |
|---|---|
| Upvotes, so the loudest voice is not the winner | One vote per person on a question, and votes on replies too. The list sorts by votes. |
| A status customers can see | Open, then solved when a reply is accepted, then closed by staff when it is done. |
| Pinned announcements | Staff can pin a question so it sits at the top of the list for everyone. |
| A way to group requests | One category per request, plus up to 3 tags from a list your team keeps. |
| An official reply | Staff replies show the person and their role, so nobody mistakes a comment for an answer. |
| Somewhere for the sensitive ones | Any question can be private, and a whole category can be too. Only the asker and your team see it. |
| A public page for each request | Every request is a real page with its own address and a preview card in your brand. Answered ones carry QAPage structured data too. |
| A way to pull the list into your own tools | REST API and MCP server on every plan. A script or your own agent can read the requests and the votes. |
Basic is $9 one time on yourcompany.myforumcat.com. Pro is $99 a month and adds your own domain. Neither one charges per seat, per request or per vote.
Setup
One category, and you have a board.
Categories and tags live on one dashboard page. Add a category called Feature requests, give it a slug, and it has its own address straight away.
Tags cut across it: billing, mobile, integrations, whatever your product is made of. Your team keeps the tag list, so customers pick from it instead of inventing new ones.
If some requests should not be public, make the category private. Everything posted there is visible only to the person who asked and your team.
Housekeeping
Pin the important one. Close the ones that are done.
The staff toolbar sits on the thread itself, so moderation is where the request is. Pin, close, make private, accept a solution, or delete.
The dashboard Questions page does the same work in bulk when the board gets busy.
The reply
A reply people can trust.
The reply is what customers actually want from a feedback board. A staff answer carries the name and the role, so it reads as official without anyone claiming it is.
Accept it as the solution and the request turns solved, with the answer pinned under the question. That is your "shipped" or "not now", right where people look for it.
Five roles share the work: owner, admin, agent, finance and member. Product can answer requests without touching billing.
What this is not.
There is no roadmap view. No board with columns for planned, in progress and shipped.
There is no changelog. If you announce releases, pin a question or keep posting them where you do today.
The statuses are open, solved and closed. There is nothing else to configure, and nothing else for your team to learn.
And there is no importer. Requests on another board stay there. Most teams start the new board fresh, and link the old one until it goes quiet.
Pricing
One flat price. No surprises.
Not per user. Not per question. Grow all you want, your bill stays the same. More traffic is good news, not a bigger bill.
Basic
$9 one-time
Create your portal- Portal on yourcompany.myforumcat.com
- 2 team seats
- 1,000 registered members
- 10,000 questions
- 1 GB (≈2,000 images) of media
- Full SEO and GEO: structured data + sitemap
- Analytics built in
most popular
Pro
$99 per month
Start with ProEverything in Basic, plus
- Your own custom domain
- Unlimited team seats
- 10,000 registered members
- Unlimited questions
- 50 GB (≈100,000 images) of media
- 1,000,000 page views / month
FAQ
Fair questions.
Can customers vote without an account?
Answer
No. Reading is open to everyone, and voting needs a sign-in. That is what keeps it to one vote per person, and the sign-in is passwordless.
Can we pull the request list into our own tools?
Answer
Yes, on every plan. Requests, votes and replies are readable through the REST API and the MCP server. A script or an agent can put them in your roadmap doc.
Who can see a private question?
Answer
Only the person who asked it and your team. Whole categories can be private too, so every question posted there starts private.
Can our whole support team answer?
Answer
Yes. Invite teammates as owner, admin, agent, or finance. Basic includes 2 seats and Pro is unlimited (fair use). Staff replies show the person's role.
What does it cost in month twelve?
Answer
The same as month one. $9 one time for a portal on a Forumcat subdomain, or $99 a month for your own domain. The bill never grows with traffic or questions.
Can we import our old forum or help docs?
Answer
Not today. There is no importer. Most teams start fresh and let the new questions build the archive, which is live in minutes.
Where next
Support forumThe same portal, for the team that wants a forum without servers.Q&A softwareVotes, accepted solutions, categories, search and the API behind them.Customer communityWhen the requests and the questions become one place customers visit.Ticket deflectionThe other half of the same portal: answers that stop repeat questions.
Put the requests where customers can vote on them.
One category, one afternoon, and the board is public on your own address.
Create your portalFree for 7 days. No credit card. Live in about five minutes.
