Review source freshness check
Distinguish a quiet month from a disconnected review source. Use a freshness check before relying on review summaries or historical comparisons.
No signup. Enter reference codes, add records and download a CSV. Entries stay in the browser tab. Filled fields do not establish completion, approval or compliance.
| Location reference | Source platform | Last successful observation | Observed coverage | Connection owner | Next verification |
|---|---|---|---|---|---|
| Location-A | Unknown | Summary unavailable | Account manager | Check source profile |
- Starting values are fictional examples, not customer records.
- Keep confidential evidence in your approved business systems. Record only a reference here.
- Complete each row from observed evidence. A completed worksheet does not certify legal compliance or provider compatibility.
- Export your CSV to approved storage before leaving this page.
An empty review chart doesn’t prove nobody reviewed your business. The source could be disconnected, delayed, or unavailable for that location. So before you change your review process, check what the chart actually shows. First, find out when the system last saw the source. That’s not the same as asking whether your front desk needs to send more requests.
Use with this guide
review management workspace
Continue with review management workspace.
Blù business advisor
Continue with Blù business advisor.
Review local body-shop search visibility without calling rankings sales
A map point is an observation, not a customer. Keep neighborhood search coverage separate from recorded inquiries and accepted repair orders.
Identify the missing piece
These are three different problems: no new reviews during a verified period, an update that failed, or no source connection. Each calls for a different next step. For a verified quiet period, review your service and request process. If an update failed, troubleshoot the connection. With no account connection, you can’t tell whether reviews are coming in.
Use the review management workspace to check the location, source, and evidence you can actually see. BlueFinch's product description limits summaries to available source data. It also separates Google reply management from Yelp analysis. Seeing a Yelp summary on a screen doesn’t mean you can publish a Yelp reply there. Treat each source and action separately.
Sources for this section: Google: review requests and public replies · BlueFinch: review management
Compare the source with the dashboard
Check the correct public business profile and note its displayed review count and rating. Then compare them with the dashboard’s timestamp, not just today’s date. If it last updated on Monday and you check on Friday, a review posted Wednesday doesn’t automatically mean the software is broken. First, record the timing difference.
In a fictional machine-shop example, the theme summary is blank while the public profile shows recent reviews and the competitor watchlist works normally. The working watchlist does not prove the review source is healthy. These tools use different data and update paths. Ask the account owner to verify the specific review connection and selected business identity.
Keep missing values visible
Don’t put zero in a spreadsheet when ratings, counts, or dates are unavailable. Zero new reviews means you measured none. Unknown activity is a data-quality condition. Treating both as zero will make your chart invent a sudden collapse whenever a connection breaks. That’s why the worksheet tracks observed coverage and the next verification in separate columns.
When the connection comes back, check whether it filled the historical gaps or just resumed collecting from today. Don’t assume a complete-looking line has real observations for every missing day. Before claiming your reputation improved, ask where the comparison data came from and how it was measured.
Resume decisions only when evidence is usable
As an owner using the Blù business advisor, first check which review sources are available before asking why sentiment changed. A confident answer won't fix missing data. Stick to the evidence you have: What concerns show up in available reviews? Which dates or locations are still unavailable?
Pick a connection owner and set a real follow-up date. They don’t have to be a developer. They do need access to the authorized business account and a clear record of what failed. Keep login details and customer records out of the worksheet. Just record the connection status and internal support reference.
Add the connection check to your regular opening or weekly office review, based on how often the source updates. Match the schedule to the service, not some assumed real-time feed. When support fixes a problem, record the first successful check and confirm coverage before removing the issue from the team’s queue.
After the repair, check one current review against its original source. Confirm the location, then inspect any new reply draft before publishing it. Now get back to the real question. If the shop actually received little recent feedback, look at service timing and optional review access. If the feed was stale, fix the reporting. Don’t push customers for reviews to solve a problem that wasn’t there.
Primary sources
BlueFinch last reviewed these sources on October 23, 2026. Check the linked sources for current requirements and product details.
Use this page for general business information. It is not legal, tax, or accounting advice.