Pillar · Operations
The network is large. The work happens at the Location.
Mapboard organizes the network into groups, assigns an owner to each Location, and uses Orbit to surface complaints that repeat, so the team can decide what to do.
Published hours do not match opening time
On the Location
- 09:04Google review on the LocationOrbit
- 09:06Recurring theme: opening hoursOrbit
- 09:41Owner assigned to the LocationTeam
- 11:20Hours ready for Google Business ProfileTeam
01 · The problem
The signal lands far from the person who runs the Location
In a large network, what happens at a Location arrives in pieces: a review, hours that no longer match, a detail nobody updated. The person who notices is rarely the person who runs that Location.
Without an assigned owner, every signal gets handled a different way. Mapboard puts the Location, its owner, and what customers say in one place, so the team works on the same Location.
02 · How it works
The chain, link by link
Five links. Each one lives on the Location.
- 01
It arrives
Google Business Profile reviews and listing details land on the same Location.
Hours, reviews, and the owner stay together. A signal stops living apart from the Location it belongs to.
- 02
It gets understood
Orbit summarizes what customers say and surfaces complaints that repeat across the network.
The analysis runs across the network. Orbit recommends. The team reviews before acting.
- 03
It gets assigned
Every group and every Location has a responsible user.
Access is role-based. The owner is in charge of the Locations assigned to them.
- 04
It gets done in bulk
Filters and bulk workflows prepare the same change for a group of Locations.
Hours, listing details, and posts are prepared on the group and published to Google Business Profile.
- 05
It gets reviewed
The team comes back to the Location: what was published to Google Business Profile, and which themes are still in the reviews.
Orbit can search the history and summarize a Location. A person decides what happens next.
The owner is assigned to the Location.
Running a network means someone is in charge of each Location. The corporate team sees the same network, on the same record.
Recurring theme · opening hours
Orbit summarizes this Location's reviews: published hours do not match opening time. The team reviews the summary before publishing the change to Google Business Profile.
Team note
“Hours for this Location are corrected on the record. We are publishing them to Google Business Profile.”
Orbit summarizes. A person decides.
03 · The difference
What a spreadsheet cannot hold.
An owner per Location
You assign responsible users to groups and to Locations. The work sits with a person.
A repeated complaint shows up across the network
Orbit detects themes that return in reviews and summarizes them. The team reviews the finding before treating it as fact.
The same change, on the group
Filters and bulk workflows apply hours, a detail, or a post across many Locations. Publishing goes to Google Business Profile.
On this Location
- Reviews
Themes that repeat on Google
- Owner
User assigned to the Location
- Listing
Published to Google Business Profile
Orbit surfaces the theme. The team reviews it before publishing.
04 · Made to fit
It adapts to how your network is organized
What changes between a pharmacy chain and a fuel network is the organization.
Groups and hierarchy
You organize the network into nested groups and filter to the group you are operating.
Assigned owners
A responsible user per group and per Location.
Role-based access
Each person signs in with the role that fits them.
Bulk workflows
The same hours, detail, or post, prepared for a group.
Google Business Profile
Business info, hours, special hours, posts, reviews, and performance, from the Location.
Orbit in operations
Summaries, recurring complaints, and search across what the network has already said. The team reviews.
Operating the network of Locations: group organization, assigned owners, role-based access, bulk workflows on Google Business Profile, and Orbit to summarize and detect complaints that repeat. The team reviews before acting.
You assign a responsible user to a group or to a Location. That person is in charge of those Locations. Access stays role-based.
Access is role-based, and owners are assigned to groups and Locations. The person who runs an area is the owner assigned to those Locations.
Orbit summarizes, detects recurring complaints, searches history, and recommends. A person on the team reviews before acting.
On Google Business Profile: business info, hours, special hours, posts, reviews, and performance.
Yes. Filters and bulk workflows prepare the same change for a group of Locations, and publishing goes to Google Business Profile.
On the Location: its Google Business Profile listing, its reviews, and the summary Orbit builds. The team consults that record when they come back to the same Location.
Let's see how you operate your network.
You tell us how it is organized today and, on a demonstration network, we look at owners per Location, a bulk change on Google Business Profile, and what Orbit summarizes from the reviews.
