Monitoring is the quiet half of review management. Nobody notices a business that monitors well, but everyone notices the one that does not: the one-star review that sat unanswered for two weeks, the complaint that repeated until a customer wrote "same problem as the others." This guide covers how monitoring works, how to set it up with free tools, and which parts need dedicated software. It is the "notice" half of the process in how to manage Google reviews.
What is the difference between monitoring and replying?
They are separate jobs with different failure modes.
| Monitoring | Replying | |
|---|---|---|
| Question it answers | "What happened, and what needs attention first?" | "What do we say publicly?" |
| Output | A sorted list, alerts, patterns | A published reply |
| Failure mode | Reviews are missed or noticed late | Replies are generic, wrong or risky |
| Who does it | Process owner, system or software | Writer, approver, sometimes AI |
| Typical tools | Notifications, inbox, dashboards | Google's reply box, drafting tools |
If you only improve one, improve monitoring. A late, thoughtful reply is better than no reply, but you cannot reply to what you never saw. Wording is covered in how to respond to Google reviews and our 30 reply examples.
How do you set up basic monitoring with free tools?
1. Confirm access
The person who monitors must have owner or manager access to the profile. Google describes how to see and respond to reviews on its help page about managing reviews.
2. Turn on notifications
Check the notification settings available for your Business Profile and enable review notifications for the owner and a backup. Notification features can change, so test: ask a friendly customer to leave a review and confirm that the alert arrives, and how fast.
3. Add a calendar check
Notifications can be delayed, filtered into spam or missed. A ten-minute daily check is the safety net.
4. Keep one log
A shared spreadsheet or task list with columns for date, location, rating, theme, status and owner is enough for a single location.
5. Assign a backup
Name who covers vacations and sick days.
6. Check the public view
Once a week, open your profile as a customer would. Confirm replies are visible and the latest reviews match your log. If a reply is missing, see why a reply might not show. If a review you expected is missing, see Google's page on missing reviews.
How should you prioritize what you find?
Triage turns a pile into an order of work. Use risk first, then rating, then age.
- Safety, legal, discrimination or serious allegation: escalate immediately and hold the public reply until a senior person approves.
- 1 and 2-star complaints: reply within about one business day, after reading carefully.
- 3-star and mixed reviews: reply within about two days. These often contain the most useful detail.
- Reviews naming an employee: tell the employee's manager, and consider praise or coaching depending on the content.
- 4 and 5-star reviews: reply within a few days, shortly and specifically.
- Ratings without text: a brief thank-you, or an invitation to share more for low ratings.
The time targets are suggestions, not Google rules.
How do you spot recurring complaints?
The biggest payoff from monitoring is not the individual reply but the pattern. The method is simple.
- Choose a period, usually thirty days.
- List every review under four stars.
- Tag each with one main theme: wait time, staff attitude, price, quality, cleanliness, billing, communication, availability, or another category that fits your business.
- Count tags by location if you have more than one.
- Rank themes and choose one to fix.
- Record the fix, owner and date, then recheck next month.
A theme that appears three times in a month is a pattern worth acting on. One angry review may be an outlier. The same complaint from four unrelated customers is information.
Software can reduce this work. Replora AI records low-star Google reviews as complaints with an issue type and severity, and AI Insights turns open complaints into three to five suggested actions. It reads review and private-feedback data only and does not forecast rating changes. Use it as a starting point for judgment, and verify the suggestions against the actual reviews.
Which monitoring features need third-party software?
Google's own tools handle the basics. The gap appears with volume and multiple locations. The comparison below is general, because features differ by product and Google changes its own tools.
| Feature | Google's free tools | Third-party software |
|---|---|---|
| See and reply to reviews | Yes | Yes, often in a combined inbox |
| Email notifications for new reviews | Available through notification settings; confirm in your account | Typically yes, with more routing options |
| Combined view across many locations | Limited; varies by account | Common |
| Rules (by rating, location, keyword) | No | Common in review tools |
| Unanswered-review queue | Manual | Common |
| Complaint tagging and trends | No | Offered by some |
| Response-time reporting | No | Offered by some |
| AI drafts of replies | Not a standard feature we can confirm | Common |
| Monitoring other review sites | Not applicable | Multi-site tools only; Replora AI is Google only |
Software features come from each vendor and may require specific plans. Check the vendor's own documentation, as we describe in our tools comparison.
What can Replora AI monitor, and what can it not?
- It can continuously detect new Google reviews through Google's Business Profile API across your connected locations, route them by star rating, and show a reply queue for those awaiting approval.
- It can record low-star reviews as complaints, group them by issue type and severity and show trends.
- It can email alerts, based on the product's transactional email setup.
- It cannot monitor reviews on Facebook, Yelp or any non-Google site.
- It cannot provide role-based team access, since accounts are single-owner.
- It cannot guarantee that Google will display every review or reply. Google controls what is shown. Review Booster, for example, reports how many customers opened the Google review page and never reports those as reviews received.
Details are on the Review Auto-Reply product page and in the documentation.
A worked triage example
The reviews below are invented to show how the order of work plays out. Imagine five reviews arrive overnight for a single-location restaurant.
| Review | Priority | Action |
|---|---|---|
| 1 star: "My daughter had an allergic reaction after eating here." | Urgent | Alert the owner immediately. No public reply until the owner has spoken to staff and, ideally, the customer. |
| 2 stars: "Waited 45 minutes for cold pasta." | High | Manager replies today: apology, no excuses, invitation to contact the restaurant. |
| 3 stars: "Food fine, service slow, parking nightmare." | Medium | Reply tomorrow. Tag themes: service speed, parking. |
| 5 stars: "Best tiramisu in town, thank you Luca!" | Routine | Short specific thank-you; pass the praise to Luca. |
| 5 stars, no text | Routine | A brief thank-you, or leave to an approved automated reply. |
Done in this order, the urgent review gets human attention first, the complaint is answered within a day, and the pattern fields (service speed, parking) feed the monthly count. Notice that the order has nothing to do with arrival time or star rating alone. The allergy claim is the first priority because of the risk, not because of the rating.
How does monitoring change as you grow?
One location, low volume
Notifications, a daily check and a spreadsheet are enough. Focus on habit.
A few locations
The pain point is switching between profiles and knowing who owns what. A single inbox, per-location owners and a shared log help. This is the point at which many businesses first consider software.
Many locations
You need rules, dashboards, response-time reporting and clear escalation. Local managers should handle routine replies, while a central owner reviews patterns across locations. Our guide to multi-location review management covers permissions, reporting and consistency in detail.
Agencies
You monitor for clients, so you need access that is separate per client and a documented escalation path to each client. Confirm whether your tool supports separate client accounts before you rely on it.
What notification practices work best?
- Alert people, not inboxes. A shared mailbox that nobody owns is where alerts go to die. Send alerts to named individuals.
- Use two channels for urgent reviews. For example, an email plus a message in your team chat, if your tools allow it.
- Avoid alert fatigue. If you receive dozens of reviews a day, alert on low ratings only and review the rest in batches.
- Test your alerts. Once a quarter, confirm that they still arrive.
- Document the response chain. Who is alerted, who replies, who approves, who escalates.
- Record who acted. A simple "handled by" note prevents double replies.
A weekly monitoring routine
Daily (5 to 10 minutes)
- Check new reviews on every location.
- Triage using the order above.
- Reply or approve drafts.
Weekly (15 minutes)
- Check the public profile for replies that did not appear.
- Check for reviews that went unanswered.
- Update the complaint log.
Monthly (30 minutes)
- Count themes, pick one fix, assign it.
- Check that alerts still reach the right people.
How do you measure whether monitoring is working?
You do not need a dashboard to judge it. Ask four plain questions each month:
- How many reviews arrived, and how many have a reply?
- What was the longest a review waited for a reply?
- Did any alert fail to arrive?
- Which complaint theme appeared most often, and who owns the fix?
If the longest wait is measured in weeks, monitoring is not working. If an alert failed, repair it before anything else. These checks are also a good test of whether software would help, since they show how much time the process takes today.
Common monitoring mistakes
- Relying on one person. Without a backup, a holiday becomes a gap.
- Trusting alerts without testing them.
- Only tracking rating. A 4.6 average can hide an unanswered complaint that affects an important customer.
- Ignoring reviews without text. A low rating with no comment is still a signal.
- Ignoring patterns. Repeating the same apology without fixing the cause makes replies feel hollow.
- Reporting reviews as a reflex. Report only reviews that appear to break Google's policy, as explained in Google's guidance. Reporting does not guarantee removal.
Next steps
Set up notifications, name a backup, and start the daily check today. Count themes at the end of the month. When volume or locations make it unmanageable, consider a tool that detects reviews, queues replies and tracks complaints. If you manage a profile more broadly, our Google Business Profile management guide shows how monitoring fits with the rest of the profile, and for multiple locations, read about the multi-location operating model.