Post insights

Every feedback post has an Insights tab that answers the questions a vote count cannot: is demand growing or fading, who is actually asking, how much revenue is behind them, and how do those people feel about it. It reads the post against your own workspace, so “a lot of votes” means a lot for your board, not for someone else’s. Use it in the moment you are deciding what to build next, or just before you tell a customer “not yet”.

​

Open the Insights tab

​

Start with the summary

The first line is a plain-language verdict, written from fixed thresholds and your workspace’s own baselines. It states at most three things: how much demand there is, what the request is worth, and the single loudest risk or signal attached to it (rising or falling votes, urgency, tone, or a status that has not moved). If a post has fewer than five votes, the summary refuses to draw a conclusion and says so. That is deliberate: a verdict built on four votes is worse than no verdict. Underneath it sits a band of headline numbers. Read the shares, not just the totals. “620 voters” means little on its own; “25% of your customers” settles an argument.

​

Votes per week

The chart covers the last 52 weeks, one point per week, so you can see whether a request is building, steady, or long dead. When downvotes are enabled and the post has any, they are drawn as a second, dashed line. Vertical guides mark the moments that explain a sudden jump or drop: a status change, and any post merged into this one. A merge hands over the other post’s votes at once, so a spike with a merge marker on it is not a wave of new interest. Hover any week to see the exact counts and what happened that week. Below the chart, a short line compares the last 30 days with the 30 before whenever the change is meaningful.

​

Who is asking

​

Groups

Groups counts the accounts behind the request rather than the individual voters, so five people from one customer count as one customer. It covers every group type in your workspace, not only companies. The header shows how many groups are involved, what share of voters belong to a group at all, and the combined revenue of those groups. Underneath, the five highest-paying groups are listed with their voter count and MRR, and a “+N more” line if there are others. Click any row to open that group’s profile. If nobody’s voters belong to a group, the block says so. Groups are created from the data you send about your users, so this block fills up once your customer identity setup includes a company or account.

​

Top customers

The ten highest-paying voters, with their group, the urgency they picked, and their MRR. Only voters with revenue recorded appear here, sorted by MRR, so this is the list to skim before a renewal conversation. A customer’s MRR comes from their record in Customers, where you can edit it by hand, or from the mrr value your single sign-on token carries. See Revenue behind a request for where to record revenue and how the combined figure is built.

​

Voter segments

How this post’s voters split across your user segments, showing the voters in each segment against the post’s total. It answers “is this only our enterprise tier asking, or everyone”. Up to ten segments are checked, and a segment with no voters on this post is left out.

​

How much it matters

​

Urgency

The full spread of urgency levels people chose when they voted, highest first, with the number of voters at each level. When a clear majority sit in the top levels, a line underneath says so in words. This block needs priority voting turned on. Until it is, voters have no way to say how badly they want something, and the block stays empty.

​

Voter happiness

How the people asking for this feel about you overall, averaged across the voters who have answered a survey:

• Satisfaction: their average CSAT answer, out of 5.
• Promoter: their average NPS answer, out of 10.
• Happiness score: both combined onto a single 0 to 10 scale, using whichever of the two a customer has answered.

Scores come from NPS and CSAT questions in surveys and popups. Customers who never answered are left out rather than counted as zero, so a low number means unhappy voters, not quiet ones.

​

What they are saying

Comment sentiment splits the post’s comments into positive, neutral, and negative, and shows how many of them have been scored. The most recent negative comment is quoted underneath with a View comment link that jumps straight to it in the discussion, so a bad signal is one click from its context. Sentiment is scored by Sleek Intelligence as comments come in. If the block tells you sentiment is off, turn on Sentiment analysis for comments in Settings → Sleek Intelligence → Feedback Processing. Comments are scored as they arrive, so the block fills up from the moment you switch it on rather than scoring everything already on the board.

​

Voter system information

The last section is collapsed by default. Expand it for the top platforms, browsers, cities, and countries among the people who voted. It is mostly useful on bug reports and platform-specific requests, where “90% of the voters are on iOS” changes what you build first.

​

The numbers in the sidebar

Insights is the deep read. A few of the same figures live permanently in the post’s sidebar under Engagement, so you can see them without leaving the discussion:

• Views: how many times the post has been opened on your board or widget.
• Emails: how many emails Sleekplan has sent about this post.
• MRR and Groups: the same combined revenue and account count as the Insights tab.
• In status since and Changelog: how long the post has sat in its current status, and a link to the changelog entry that shipped it, if there is one.

​

Good to know

​

Related