Your portal lives at chattering.ai/portal/s/<your-slug> once you claim a Public roadmap address in your agent's Deploy tab, and inside the widget's Roadmap tab.
Visitors can submit a request, vote on existing ones, and comment — without an account. Every request has its own indexable page, so it can be linked and found in search.
You manage the board from Feedback in the dashboard: set status, add tags and an ETA, and merge duplicates. Merging moves the votes, comments, subscribers and evidence across, and old links still resolve.
What the portal is for
Most product teams collect feedback in email threads, Slack DMs, and support tickets — scattered places where the same request shows up five times from five different people and nobody can tell how much actual demand sits behind it. The public feedback portal brings all of that into one place.
Customers see what others have already asked for, which means common requests gather votes rather than duplicating. Your team sees exactly how many real people want each thing, sorted by demand. The portal does not replace your planning process — it feeds it with accurate signal.
Submitting a new request
Anyone can post a request on your portal page. There's no account needed. The form asks for a short title that will appear on the board, plus an optional description where the submitter can explain their use case and an optional email address.
After submitting, the request appears on the portal right away, marked for review — unless it duplicates a request already on the board, in which case it counts as a vote on that request and its description is added to that request's thread. The person who submitted it is automatically subscribed, so if they left an email address they'll get an email when it ships.
Upvoting
Each request on the portal has an upvote button. One click registers a vote; to hear when it ships, use Email me when it ships and leave your address. Click again to remove your vote. Each browser gets one vote per request.
Vote counts are visible to everyone who visits the portal. There's no fixed number that automatically moves a request forward — that decision stays with your team — but high vote counts push items toward the top of the board and give your team a clear picture of what matters most to the people actually using the product.
How the team triages requests
Open Feedback in the Chattering dashboard to see every incoming request. From there you can:
- Set a status to show where each request sits:
- Under review — you've seen it and are thinking about it
- Planned — it's on the roadmap
- In progress — being built now
- Shipped — done; everyone waiting on it is told, in their chat or by email
- Declined — won't be built; it is hidden from the public board
- Add tags to group related items
- Set a target (for example, Q4 2026) if you have a target date
- Merge duplicates with Merge as duplicate… — all votes, comments, and subscribers move to the surviving request, and the old link now opens that request, so shared links keep working
Visibility and privacy
Requests on your board and their vote counts are public, except requests the AI suggested that you haven't accepted and requests you declined. Anyone visiting your portal page can read them, and search engines can index the individual request pages.
What's not shown: who voted, and the identity of the person who submitted the request. Submitters are not named on the portal by default. The portal doesn't ask commenters for a name, so visitor comments show as "A customer".
Your team sees full details in the dashboard — including conversation context when a request came in through chat.
Writing a good request
Specific titles get more votes. "Export contacts as CSV" is easier for other users to recognise as their own need than "Better data export". Clear titles also help your team act without having to ask follow-up questions.
Use the description to explain what you're trying to accomplish, not just the feature you're picturing. "I reconcile payments every week and currently copy rows by hand" gives your team enough context to solve the real problem — which might be a different solution than the one you described.
Keep each post to one request. Bundling two ideas together makes it harder to vote accurately and harder to track each item separately.
Tracking your requests
After you submit a request, you're subscribed to it. When it ships, you'll get an email if you left your address; if you asked for it in a chat instead, you'll get a message in that conversation.
You can also check the portal page directly to see the current status of any request on the board.