Rating drop alerts for a business with many locations
Rating drop alerts for multi location business owners: look up every branch each morning, compare with yesterday, and tell the right manager when one falls.
Part of the guide Location intelligence automation
Rating drop alerts for multi location business owners work by looking up each of your own branches on online maps on a timetable, comparing each branch's rating with the one seen last time, and telling the branch's manager only when it fell by more than a set amount. Nobody has to open forty listings a week; the branch that slipped from 4.6 to 4.3 overnight is in someone's inbox by 9:00.
This article is for operations, regional and customer experience managers at chains, franchises, clinic groups, dealer networks and hotel groups. It explains how to decide what counts as a drop, the two ways to watch ratings in xMap Flows and when each fits, a made-up example of a network of 38 branches, and how to keep the alerts from turning into noise.
Decide what a drop is before you watch for one
A rating is an average, and an average moves a little every time someone posts. The question is how far it must move before a person should act. Three things decide it:
- How many reviews the branch has. A branch with 3,000 reviews barely moves on one bad week; when it falls by 0.2, something real happened. A branch with 40 reviews can fall 0.2 on two angry customers.
- How often you look. Looked at daily, small moves are common. Monthly, a move of the same size means more.
- What the manager can do about it. If the answer to any drop is the same call to the same person, set the line where that call is worth making.
Two ways to watch in xMap Flows
| What changed, after a lookup | When something changes | |
|---|---|---|
| Best for | Your own branches, many of them | A few places, or the rivals near them |
| How it watches | Each branch looked up by name near its address, then compared with last time | xMap checks places of a kind around up to 5 points on a timetable |
| What triggers it | A rating that moved by the amount you set, up or down | A rating going from a line or above to under it |
| How it starts | A Schedule (every morning, every Monday) | The check itself; the flow runs only when it finds a change |
Both read ratings; they differ in how many places they suit and what starts them.
For a network of your own branches, the first is the usual choice. My data holds your branch list; Map business scan with Look for: Each place itself finds each branch's live listing (up to 100 a run); What changed set to Rating lets through only the branches whose rating moved by at least the amount you choose, each with the rating it had before and a line such as "Rating dropped from 4.6 to 4.3".
The second, When something changes, suits a handful of flagship sites, or watching the competitors around them fall below 4. Its first check only looks; changes show from the next one.
A network of 38 branches (made up)
This example is made up. A bakery-cafe group runs 38 branches across Paris, Lyon and Lille. Its operations director wants each area manager told when one of their branches falls, with enough context to know whether to call the branch or wait.
- The branch list in My data has the name as it appears on the shopfront, the address and a column for the area manager's email.
- Every morning at 07:30 the flow looks each branch up and passes them to What changed, rating, by 0.1.
- On a typical morning nothing reaches the end. On the morning that matters, two branches do: one in Lille from 4.5 to 4.4 (a branch with about 900 reviews) and one in Lyon from 4.3 to 4.0 (about 120 reviews).
- An xMap LLM block writes one line for each from the fields it has: where it now stands among the 38, and whether the move is large for its number of reviews.
- A Branch block sends falls of 0.3 or more to the area manager that morning; smaller ones wait for the Monday digest.
The Lyon manager gets one email, about one branch, with the before and after, and a note that the branch is now in the bottom five of the network. The Lille fall waits until Monday.
Keeping the alerts useful
- The first run sets the baseline. What changed compares with what the flow remembers, so the first real run only remembers. Alerts start from the second.
- Send each alert to one person. An email to the whole region about one branch teaches everyone to ignore it. Route by the manager column.
- Say rises too. A branch climbing from 4.1 to 4.4 after a new manager started is worth a word of thanks; the same block reports moves up when you leave it on both.
- Watch for branches that vanish. A branch the lookup cannot find comes back as Not found on online maps. Treat that as an alert of its own: a listing merged, moved or was taken down.
- Do not chase one review. Ratings from online maps are averages of public reviews. Use the alert to look, then read what people wrote before acting.
Setting it up as an AI employee
Built as a flow, it runs on its own every morning and fits the operations jobs in the field operations guide.
- Schedule: every day at 07:30, in the network's time zone.
- My data: your branches, one row each.
- Map business scan: Each place itself.
- What changed: Rating, by the amount you chose.
- xMap LLM: a line of context for each branch that moved.
- Email: one email per item, to the address in the manager column.
In the inbox: on most days, nothing at all. On the day a branch slips, its manager gets its name, the rating before and after, and one line on where it now stands. The template alert when a branch's rating drops is this flow for restaurants and cafes; my dealerships whose rating moved runs it monthly for a dealer network, and rating scorecard for my clinics turns the same lookup into a regular scorecard. To watch your rivals' ratings rather than your own, see competitor ratings and reviews tracking.
Questions
How small a drop can I be told about?
As small as 0.1. Whether you should be depends on how many reviews a branch has: for a branch with few reviews, 0.1 is often noise, so many teams use 0.2 or 0.3 for those.
How many branches can one flow watch?
Map business scan looks up to 100 places a run with Each place itself, so one flow covers a network of up to 100 branches each run. A bigger network is split by region into flows, or linked copies of one flow.
Does it tell me why the rating fell?
It tells you that it fell, from what to what, and the branch's other details. The reviews themselves are best read on the listing before you act.
Can it watch my competitors' ratings as well?
Yes. Put your competitors in a table, or use When something changes around your flagship sites to hear when a rival nearby falls below a line you set.
Templates that do this
Read next
More on business and places data · Every article · Templates