> ## Documentation Index
> Fetch the complete documentation index at: https://sleekplan.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Post insights
> Open the Insights tab on any feedback post to see how demand is trending, which companies and revenue sit behind the request, how urgent voters think it is, and what the comments sound like.
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".
The Insights tab is available on the **Business** plan and above. On lower plans the tab still appears, and opening it offers an upgrade. See [Plans and billing](/help/account-security/billing). Everyone on your team can read it, including **Members**, because it counts as analytics. See [Roles and permissions](/help/account-security/roles-permissions).
## Open the Insights tab
Go to [**Feedback**](https://app.sleekplan.com/feedback) and click the post you want to understand.
In the post header, click **Insights** next to **Discussion**.
## 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.
| Tile | What it tells you |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Revenue at stake** | The combined monthly recurring revenue behind everyone who upvoted, and what share that is of your whole board's revenue. |
| **Urgency** | The share of urgency votes that fall in your two most urgent levels, with the counts. This tile appears when [priority voting](/help/portal-widget/feedback-submission-voting#priority) is turned on. |
| **Momentum** | Upvotes in the last 30 days, and how that compares with the 30 days before. |
| **Reach** | How many customers voted, and what share of all your end users that is. |
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](/help/portal-widget/feedback-submission-voting) 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](/help/feedback/statuses), and any post [merged into](/help/feedback/merge-feedback) 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](/help/account-security/groups) 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](/help/portal-widget/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**](https://app.sleekplan.com/customers), where you can edit it by hand, or from the `mrr` value your [single sign-on token](https://sleekplan.com/docs/authentication/single-sign-on) carries. See [Revenue behind a request](/help/feedback/revenue-mrr) for where to record revenue and how the combined figure is built.
### Voter segments
How this post's voters split across your [user segments](/help/account-security/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](/help/portal-widget/feedback-submission-voting#priority) 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](/help/surveys/question-types#nps) 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](/help/feedback/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](/help/sleek-intelligence/processing) as comments come in. If the block tells you sentiment is off, turn on **Sentiment analysis** for comments in [**Settings → Sleek Intelligence → Feedback Processing**](https://app.sleekplan.com/settings/intelligence/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](/help/feedback/statuses), and a link to the [changelog entry](/help/changelog/create-entries) that shipped it, if there is one.
## Good to know
Each voter is counted once. If a voter belongs to a group that has MRR recorded, that group's MRR is counted a single time no matter how many of its members voted. If a voter's groups have no MRR, that voter's own MRR is used instead. So a company and its staff can never be added together twice, and it does not matter whether you track revenue on customers, on groups, or on a mix of both.
The board figure it is compared against is built the same way across your whole workspace.
Sleekplan compares this post's upvotes against the spread of upvotes across every live post in your workspace, and reports which band it falls into: the top 10%, the top 25%, the top half, or below average. It is a position on your own board, so it stays meaningful whether you have 40 posts or 4,000.
The workspace-wide figures (total revenue, total customers, and the vote bands) are recalculated at most once every six hours. They move slowly, and reading them on every post open would be expensive on a large workspace. The post's own numbers are always live.
No voter on this post has MRR recorded, on their own record or through a group. Add it on a customer in [**Customers**](https://app.sleekplan.com/customers), on a group in [**Groups**](https://app.sleekplan.com/groups), or send it with your user data. Until then the summary falls back to reach, and tells you what share of your customers voted instead.
No. Insights is admin-only. Nothing in it is returned to the widget or the public portal, so you can record revenue and weight your biggest accounts without anyone on your board noticing.
The [Impact Score](/help/feedback/impact-score) is one number you can sort the whole board by, so it answers "which post first". Insights explains a single post in detail, so it answers "why, and who is behind it". Most teams sort by impact to shortlist, then open Insights on the shortlist.
## Related
Rank your whole board by real impact, and tune the weights behind the score.
Group your end users into companies and accounts, and give them revenue.
Build the segments the voter breakdown is measured against.
Turn on comment sentiment and the rest of the AI triage.