Review Reporting
Review analytics and tribe performance
Comparing locations on rating, volume and response rate, and what to do with the answer.
Last updated September 2, 2026
The dashboard covers the whole network: totals, averages, response rates, the mix of positive and negative, and how each tribe compares.
The comparisons that matter
| Ranking | Tells you |
|---|---|
| Most reviews | Who is actually asking. |
| Least reviews | Where the opportunity is. Almost always the more useful list. |
| Highest rated | Who is doing the work well. |
| Lowest rated | Where to look, gently, before it becomes a pattern. |
| Response rate | Who is engaging with what customers say. |
Periods
Analytics run over 2, 3, 12 or 24 months. Use a long window for rating — it moves slowly — and a short one for volume and response rate, which respond to effort within weeks.
Using it with the network
- Share the volume table, not the rating table. Volume is within a tribe's control this month; rating is not.
- Ask the tribes with the most reviews what they actually do — it is usually one habit, and it transfers.
- Treat a low response rate as a training issue, not a performance one. Most people simply have not been told it is their job.
A TRIBE WITH NO REVIEWS MAY NOT BE CONNECTED
Before concluding a location is not asking, check their Google, Facebook and Yelp connections. A lapsed connection looks exactly like a tribe that has stopped collecting reviews.