Pillar · Reputation
The average is what gets reported. The spread is what gets experienced.
Mapboard collects what people say about each Location, groups the themes that repeat, and shows the Location next to competitors in its radius.
“Got there at 9 and it was closed, even though Maps says it opens at 8. Second time this has happened to me at this Location.”
Orbit suggests a reply
We're sorry this happened. The published hours have been corrected and we're reviewing the opening routine at that Location. Thank you for flagging it both times.
01 · The problem
A network averaging 4.0 has Locations sitting at 2.5
The average is the number that goes into the report. The customer walks into one Location, and that Location is the brand to them.
Reading the network only in aggregate hides the Location that is pulling away from the rest. Mapboard keeps reviews on the Location they belong to.
02 · How it works
From what they say to what you do
Five steps. The last one leaves the recurring theme with the Location's owner.
- 01
It gets collected
Google Business Profile reviews stay on the Location they belong to.
Rating, text, and history live with that Location's listing. The inbox shows the network and can be filtered by group.
- 02
It gets understood
Semantic analysis groups themes and surfaces what repeats across the network.
That is where a theme shows up again: the checkout, at one Location, on Saturdays. Orbit summarizes the pattern. The team reads it before treating it as fact.
- 03
It gets answered
Orbit drafts a reply and your team reviews it before it publishes. The text that goes out is the text a person approved.
The suggestion uses the review and the Location. Publishing stays a decision for the team.
- 04
It gets compared
Each Location is compared with nearby competitors, by radius, using Google data.
The comparison uses ratings and review signals. The source is Google.
- 05
It gets handled
When a theme repeats, Orbit surfaces it and the owner of that Location is already identified.
Orbit recommends. The team decides what to do with the Location. The review stays on the Location, with its history.
Reputation is read Location by Location.
Mapboard shows reviews, recurring themes, and the radius comparison, so the team can see each Location.
- Incorrect hours62
- Checkout wait time48
- Out of stock31
- Staff attitude19
Orbit surfaces the themes that repeat in reviews across the network.
03 · The difference
What the average leaves out.
The unit is the Location
Reviews are read on the Location and across the network. A theme that repeats shows up where it happens, and the average stops being the only reading.
Competitors in the radius, on Google data
The Location is compared with nearby businesses: ratings and review signals. The source is Google.
A person reviews the suggestion
Orbit drafts, summarizes, and surfaces recurring complaints. The team approves the reply before it is published.
Downtown Brooklyn
- This Location3.2
- Another Location in the group4.3
- Competitors within 1 mile4.1
Google ratings, on the Location and by radius.
04 · Made to fit
It adapts to how your customers talk
A pharmacy's vocabulary is not a fuel station's. The analysis runs on your network's reviews.
Recurring themes
Semantic analysis groups what repeats in reviews across the network.
Reply suggestion
Orbit drafts a reply and a person on the team reviews it before publishing.
Summary per Location
Orbit summarizes a Location's reviews and the complaints that return.
Radius competitors
Nearby competitors, ratings, and review signals, using Google data.
Location owner
When a theme repeats, the owner assigned to that Location is identified.
QR per Location
One QR per Location. The destination can change after printing, and scans are counted.
Google Business Profile. Each review stays on its Location, with its rating and history. The team replies from there, after reviewing the suggestion.
Orbit drafts a suggestion. Your team edits and approves it. The text that publishes is the one a person approved.
Mapboard reads reviews by Location and across the network, with the themes that repeat. The Location stays visible next to the aggregate.
Nearby competitors, by radius. The comparison uses ratings and review signals. The source is Google.
Orbit summarizes what that Location has. With few reviews, the summary is short, and the team reads it at that scale.
Orbit flags the recurring theme, and that Location's owner is assigned. The team reviews the summary and decides what to do. The review stays on the Location.
Let's see where your network pulls apart.
You tell us how you read reviews today and we show you, on a demonstration network, the themes that repeat and the radius comparison.
