Every post has a page for your team, with everything about it in one place. Open it from Feedback: click a post's title, then Open full page in the pane. Anyone on your team can do everything on it.
Find your way around the page
The line under the title shows the post's number, author, age, votes and, if you use Who's asking, its total (see Triage your feedback).
At the top of the page:
The up and down arrows go to the Newer post and the Older post, by number, skipping merged posts. K and J do the same.
View on portal opens the post on your portal, as your users see it.
More actions (•••) has Merge into…. See Merge duplicate posts.
On a phone, these actions are in the menu at the top of the screen, and the sidebar comes after the description and comments.
Reply as the team
Write in Reply as the team… under the comments and choose Comment. Your reply appears on the portal with a Team badge.
Two switches under the box change what the reply does. Both turn off again after each comment.
Email your reply to the voters
Turn on Email voters to send the reply to the people who voted for the post, for example to tell them it's planned. The count beside it, such as (8 people), is how many it emails. The button becomes Comment and email.
The count includes only people the email can reach:
voters whose email address is confirmed, or comes from your single sign-on;
not your team;
not people who unsubscribed from your project's emails or turned these emails off in their Account;
on a private portal, only people who can still read it.
The post's author voted for it when they posted it, so they're included. (nobody to email) means nobody can be reached, and the switch is off. Posts from sample content email nobody.
Each person gets one email, with the subject Re: and the post's title. It says who replied, quotes the reply (up to 1,000 characters) and has a See the post button and a link to unsubscribe. If you merge the post before the emails go, they aren't sent.
Over the API, set emailVoters to true when you create the comment. See API and MCP.
Leave an internal note
Turn on Internal note (only your team sees it) for context your users shouldn't see, such as what a customer said on a call. The button becomes Add note.
Notes show among the comments with an Internal note badge and a tinted background. They never appear on the portal, in emails or in webhooks, and they aren't counted as comments: the heading says, for example, 2 comments · 1 internal note. When you merge the post, its notes move with it. A note can't be emailed, so Email voters is hidden while the switch is on.
Follow what happened
The comments also list each status change, in order: what it was, what it became, who changed it and when, such as Open → Planned, by Maya Chen · 2 days ago. A change to Completed adds how many people were emailed. Changes made by Tuti itself, or by someone whose account was deleted, have no name.
Your portal shows the same status changes, without who made them or how many were emailed.
Plan the post
The sidebar holds the post's properties. Each one saves as soon as you pick it.
Status: see Statuses and your roadmap.
Board: moves the post to another board. Its votes, comments and number stay the same.
Owner: the team member who looks after it, or Nobody. Only your team sees it, here and on roadmap cards. When someone leaves the team, posts they owned go back to Nobody.
ETA: the month you expect it, this month or one of the next 23, or No ETA.
ETAs are public. While the month is still to come, your portal shows it on the post, such as expected December 2026, and the message after you pick it says shown on the portal. Once the month has passed, or the post is Completed or Closed, the portal stops showing it, so a missed date doesn't read as a promise. Your team roadmap shows it on the card, such as ETA Dec 2026.
The Feedback pane has the same four properties.
See who's behind it and what's linked
Further down the sidebar:
Votes and Voters: up to 10 voters with their company and Who's asking value, then and N more.
Conversations: up to 10 support conversations linked to the post, the latest first, with who they're with and their status. Closed ones older than your plan's history aren't listed. See Link conversations to posts.
Merged into it: posts merged into this one.
Shipped by: the pull request that completed it, when Autopilot marked it done. See Review Autopilot's updates.
Changelog: changelog entries that ship it, each marked Published or Draft. See Write and publish changelog entries.
Similar: up to five posts like this one, with their status and votes. If one is the same idea, merge them.
Under the description:
GitHub pull requests, issues and releases linked to the post, each opening on GitHub. From Autopilot marks one Autopilot added; × removes a link. See Connect GitHub.
A Possible duplicates card, with posts Tuti thinks repeat this one. See Merge duplicate posts.