The team conversation, right on the post.

Public comment threads are for users. Internal notes are for everyone else. The product manager scoping the request, the engineer flagging a hidden complication, the support lead noting that this same customer reported it last quarter under a different account, the designer linking the Figma file. All of that is critical context, all of it needs to live somewhere, and none of it belongs in the user-facing thread. Without internal notes, that conversation ends up scattered across Slack, Linear, Notion, and someone's brain, and the next person who picks up the post has to reassemble it from nothing.

Internal notes in Upvoty fix that. They live on the post, are visible only to your team, and stay attached forever, even after the post is merged, moved, archived, or shipped. The discussion you have today is exactly the context the next teammate needs in six months when a similar request comes in, and they can find it instantly via search instead of asking the original participants to remember.

@mentions that respect everyone's attention

Every internal note supports @mentions. Mentioned teammates get an in-app notification, an email, and an optional Slack ping via the Slack integration. Notification preferences are per user, so the people who live in Slack get pinged in Slack, the people who live in email get pinged in email, and the people who live in Upvoty just see the badge. Nobody is forced into a channel they ignore.

Mentions also create a paper trail, which matters more than it sounds. When a decision is made on a post, the @mention that triggered the discussion is the first thing the audit log shows. You always know who escalated, who was looped in, who approved, and when.

How internal notes change your operations

Internal notes pair naturally with team roles: you can restrict who can read or post internal notes, so contractors or external moderators only see public comments while full-time staff see the entire conversation. They also pair with assignees and priorities, since most assignment discussions ("can you take this?", "do we ship it this sprint?") are inherently private and belong on an internal note rather than a public reply.

Combined with moderation, internal notes give your moderators a quiet place to discuss edge cases ("is this spam or a legitimate complaint from a frustrated user?") without exposing that deliberation to the submitter. The result is calmer moderation, better decisions, and fewer escalations that started as misreadings.

Search, audit, and forever-attached context

Internal notes are indexed in workspace search, so you can find them by content, author, or post. They survive merges, moves, board changes, and exports. They are excluded from any export that goes to a user (changelog emails, public roadmaps, public boards) and included in admin exports. The result is a complete, durable, private team narrative attached to every public post, which is exactly what serious feedback operations require.