Skip to main content
The Portal is BuildBetter’s customer-facing surface. It gives the people who use your product one public place to ask for something, watch it get built, and read about it when it ships. Unlike a standalone feedback tool, Portal posts connect back to the requests BuildBetter already extracts from your calls, tickets, and conversations — so a public board reflects everything you know, not only what customers thought to post themselves.

​
Boards

Everything in the Portal is a board. Each board has a kind, a name, a URL slug, and a visibility setting. You can run several boards at once. A typical setup keeps one feedback board for ideas and a separate changelog board per product line, so a mobile release doesn’t clutter the main feed.
Boards are managed through the MCP tools or the Portal settings in the app. Creating, updating, and deleting boards, posts, and voters are all available programmatically.

​
The Two Board Kinds

Feedback boards

Customers post ideas and vote. You see who asked, how many wait, and which accounts are behind each request.

Changelog boards

Publish what shipped, with labels, and embed the feed in your own product.
A feedback board can also carry status columns — the public roadmap. See Roadmap.

​
How It Connects

The Portal is not a silo. Three connections matter:
  • Post matching — portal posts are matched against feature requests already extracted from your other sources, so duplicates collapse into one item with all its evidence.
  • Voters — every vote records the person and company behind it, which feeds the demand picture you use to prioritize.
  • Releases / Close the Loop — when something ships, BuildBetter matches it back to everyone who asked and drafts the message telling them. Publishing a changelog entry and telling the individual customer are separate jobs; the Portal does the first, Close the Loop does the second.

​
Next

Boards & Voting

Running feedback boards, posts, statuses, and voters.

Roadmap

Planned, In Progress, and Shipped columns.

Changelog

Publishing entries and embedding the feed.

Close the Loop

Telling the customers who asked.