See review performance in Reports

Last updated: Oct 4, 2026

Review performance lives in Reports → Reviews Management. The tab has two views — Responses (every star rating that came back, public Google redirects and private feedback alike) and Requests (the send log of your review-request automation) — plus a Per-source summary table on top showing requests sent, opens, responses, response rate, and average stars for each job source. It defaults to all time, with a date filter to narrow the window.

Before you start

The per-source summary

The top table has one row per source plus an All sources row, with columns Requests sent, Opened, Responded, Response rate, Avg ★, Sent to Google, Said posted (self-reported), "Google count", Verified and Private. Verified counts the public Google reviews you confirmed as that source's customers (see the Responses view below) — the one number in this table that is checked against Google itself. "Google count" is how far Google's public review count moved on the listings that source sends customers to, between the first and last reading in the period — Google's number, anyone's reviews, so a floor on what got posted rather than a tally of your customers. It reads "—" until the listing ids are saved by Check review links in Automations ▸ Sender Numbers. Click any row to filter the lists below to that source — All sources is the only view that can never hide a review. The Hide inactive sources checkbox trims sources with no activity in the period.

The Responses view

Each row is one customer response, with columns Customer, Rating, GBP, Outcome, Job ID, Phone, and Date:

  • Outcome — what the customer's visit told us, at its proof level: a blue Sent to Google chip means they were taken to your public listing and nothing more is known; a green Says posted chip means they came back and tapped "Yes, I posted it" (their word — not verified with Google); a grey Not yet chip means they came back and said why (sign-in, couldn't find where, later, changed mind); a red Private chip means they submitted the private form. A small "back after 52s" line under a chip is the measured return — a hint, never a proof. A filled green "Verified on Google" chip replaces the outcome once a public Google review matched this customer by name, stars and timing and you confirmed it; before you decide, the row shows a small "Possible Google match" line under its chip.
  • GBP — the Google Business Profile link tied to this review. For a redirected review it is the exact URL the customer was sent to at the time (not today's setting); hover the chip and the tooltip tells you which it is.
  • Job ID — click to open the job in a new tab.

Selecting a row opens the detail panel: private feedback shows the customer's message, email, and service address with a "needs follow-up" flag; Google-bound responses show their outcome with the star count, and — when the listing id is known — a line with Google's public review count for that listing at the redirect and after it (0 min, 15 min, 2 h, 24 h, 72 h), read as a floor, never as that customer's review. When a public Google review on the listing looks like this customer (the listing id must be saved for the match to run), the panel shows it — reviewer name, stars, date and the first line — with why it matched and the question "Yes, it's them" / "No". A match on the first name alone says so and asks you to check the stars and the date. Yes makes the row "Verified on Google" and counts it in the summary's Verified column; No remembers that this customer is not that reviewer, on every one of their redirects. A warning with an Open Sender Numbers button appears in two cases: the link that customer was sent to opens a Maps profile page instead of the review box, or the customer came back saying they couldn't find where to post. If the customer left a phone number, the Call / Text button opens the source-aware chooser so your follow-up call or text comes from the right line. Use the search box ("Search name, phone, job #…") to find a specific customer.

The Requests view

The Requests view is the review-request send log. Status chips filter it: All, Delivered, Failed, Skipped, Pending, and Cancelled — the Requests toggle shows a red badge counting failed plus skipped runs that deserve a look. Each row shows the customer, phone, job, source, when it ran, its status, and the Reason for any skip or failure, plus a Call / Text action to reach the customer manually.

If the automation itself is turned off, a banner warns you: "Review request automation is off." — new completed jobs won't get a request automatically until you "turn it on in Automations ▸ Workflows ▸ Review Request."

Troubleshooting

  • "Unable to load review analytics." — the tab couldn't fetch data. Reload the page; if it persists, check your connection.
  • A review you were notified about isn't on screen — you're filtered to a single source or a narrow date range. Click the All sources row and widen the date filter; all-sources with all time can never hide a review.
  • The GBP column is empty for a row — no Google review link is tied to that review's job or source. Set one per source or per number.
  • Lots of Skipped runs — read the Reason column: common causes are customers who opted out of texts or jobs without a phone number.
  • "No requests match this filter." — the status chip you selected has no rows in this period; click All.

FAQ

What counts as Sent to Google vs Private in the report?

Sent to Google means the customer rated high and was taken to your Google review page (since October 2026 after a short hold-on screen; before that, instantly at the star tap). Private means they rated low and submitted the private feedback form — only your team sees those.

Does the report show whether a review actually got posted on Google?

Three levels, each labelled. A green Says posted chip is the customer's own word. The Google count column is how far the public review count on your listings moved — a floor. A filled green Verified on Google chip means a public Google review matched this customer by name, stars and timing and you confirmed it was them — the only state checked against Google itself.

How does a review become Verified on Google?

After each redirect, Dispatch Bros reads the listing's newest public Google reviews — once the listing id is saved by Check review links in Automations ▸ Sender Numbers. When one looks like the customer by name, stars and timing, the row shows Possible Google match and the detail panel asks you — Yes, it's them or No. Only your Yes makes it Verified on Google. Google returns at most the 5 newest reviews per read, so a very busy listing can miss some, and a review whose author has no public Google profile cannot be matched. When two of your customers look equally like one reviewer — or two reviews look equally like one customer — nothing is proposed.

What is the Google count column and why is it a dash?

It is the change in Google's public review count on the listings that source sends customers to, between the first and last reading in the period. It counts anyone's reviews, so it is a floor, not a tally of your customers. A dash means no listing id is saved yet — run Check review links in Automations ▸ Sender Numbers.

Why is a review request marked Skipped or Failed?

The Requests view logs every review-request automation run with a status and reason — for example an opted-out customer, a missing phone number, or a delivery failure. Open the Requests view and read the Reason column.

Can I contact a customer straight from the report?

Yes — every response and request row with a phone number has a Call / Text button that opens the source-aware dialer or the Messages thread.

Related articles