Training Your Team to Ask for Reviews

Jacob Mishalanie

Oct 7

11 min read

A cup of coffee sitting on top of a wooden table

Right now, whether a customer gets asked for a review at your counter depends on which barista is working and whether they happen to remember. Short answer: fix that with a short training session and a script that sounds like your shop, not with a quota or a reward tied to review counts, because Google's own policies do not allow incentivized or gated reviews, and a target puts your staff in an uncomfortable spot for no good reason.

I have watched this go wrong in both directions. A shop with no plan at all gets reviews only when a customer happens to think of it themselves, which is rare. A shop that leans too hard the other way, pushing every customer for a review, starts to feel transactional, and staff hate doing it. The fix sits in the middle: make the ask a normal, comfortable part of service that any staff member can do the same honest way, remove the awkwardness for them, and measure what is safe to measure without turning anyone into a review machine.

A Fifteen Minute Training Session

You do not need a half day workshop for this. A fifteen minute session, run once with the whole team and repeated for new hires, is enough if it is structured well. Split it into four parts: two minutes on why this matters, three minutes on the policy dos and don'ts, six minutes of script practice in pairs, and four minutes for questions.

The why comes first because staff need a reason that is not just a company mandate on them. Reviews genuinely help other customers find a shop worth trying, and a specific, recent review often means more to someone deciding where to go than a star count alone. That is a real reason, not a sales pitch, and it is worth saying plainly instead of skipping straight to the ask.

The policy segment matters more than it might seem. Google's Business Profile guidance on getting reviews from customers, and its policy on user contributed content, both draw a clear line: businesses cannot offer incentives for reviews, cannot ask only customers likely to leave positive reviews while skipping others, and cannot have staff or their families post reviews of the business they work for. Walking through this with the team up front means nobody accidentally crosses a line they did not know existed, and it protects both your shop's listing and your staff from an awkward gray area.

The practice segment is where the training actually sticks. Pair staff up and have them say a script out loud to each other, not silently read it. A line that looks natural on paper can sound stiff coming out of someone's mouth, and the only way to catch that is to hear it said. Close with open questions, because staff will have real scenarios come up that a script cannot fully cover, and it is better to talk through those in the room than to leave people guessing on the floor.

Run this session once with the full team together, so everyone hears the same policy explanation and practices in front of each other, and then repeat a shorter version for every new hire during their first week. New staff have not built up the same comfort with regulars yet, so their version of the training should spend a little more time on the quick order script, since that is the moment they will hit most often before they know customers by name.

A dry run before the real session is worth doing too. Time each segment with a stopwatch once, see where it runs long, usually the practice segment if pairs get talking, and adjust the minutes until the whole thing genuinely fits inside fifteen. A training session that keeps sliding to twenty five minutes stops feeling like a quick, respectful use of everyone's time, and that defeats part of the point.

Scripts That Sound Like Your Shop

A script only works if the person saying it would say those words. Draft three versions for three different moments, then have two staff members read each one aloud and rewrite anything that feels off to them before it goes anywhere near a customer.

For a warm regular, someone your barista already knows by name and drink order, the ask can be direct and personal. Something like, if you have a minute sometime and you like what we're doing here, a Google review really helps people find us, fits naturally into a conversation you are already having. It does not need to be delivered as a formal request, because the relationship already exists.

For a quick order, someone moving through the line with little time to talk, keep it to one short sentence, offered once and dropped if there is no response. A line like, thanks for coming in, if you get a chance a review helps us out a lot, said while handing over a cup, respects that this customer may be in a hurry and does not need a follow up push.

For a complaint that got resolved, this one takes more care. Never ask for a review in the same breath as apologizing for a mistake, and never suggest what the review should say. If a customer's issue was fixed and they seem satisfied, a review ask can come later, separately, framed around the shop generally rather than around the specific problem that was resolved. Staff should feel free to skip the ask entirely here if it feels wrong in the moment, and that instinct should be respected, not overridden.

None of these three scripts are meant to be memorized word for word and recited exactly. They are starting points, meant to be said aloud, rewritten by the staff who will use them, and adjusted until each one sounds like something that specific person would naturally say. A script that gets handed down without that rewriting step tends to sound scripted, which customers notice immediately, even if they could not say exactly why a moment felt off.

Recognition Without Turning It Into a Contest

Do not rank staff by review count, and do not tie pay, tips, or perks to how many reviews come in while someone is on shift. Beyond running against Google's own rules on incentivized reviews, a per person leaderboard creates pressure that shows up in how customers are treated, and it can tempt a well meaning employee to nudge in ways that cross the line you just spent fifteen minutes explaining.

Recognition works better aimed at service stories than at numbers. If a specific, well written review mentions a staff member by name or describes a moment that went well, that is worth reading out loud in a team meeting and thanking the person for, not because it produced a review, but because it describes good service that deserves recognition on its own terms. The review is evidence of the good moment, not the goal itself.

This distinction is subtle but it changes behavior. A shop that celebrates good service, and treats a resulting review as a nice side effect, keeps the ask honest and evenly given. A shop that celebrates review counts by name, even informally, quietly teaches staff to chase the metric instead of the moment, and that shift is hard to undo once it starts.

It helps to say this out loud to the team directly, not just build it into how you run recognition quietly in the background. Tell staff plainly that you will never rank them by review count, and that the goal is good service, full stop, with reviews as a natural, occasional result rather than a target anyone is expected to hit. Staff who hear that clearly tend to relax into the ask instead of dreading it, because the pressure of a hidden scoreboard has been removed before it could ever form.

What You Can Safely Track

You do not need outside software to know whether this is working. Your Google Business Profile itself shows total review count and recent reviews, and that is enough to build a simple weekly log: date, total review count, number of new reviews since the last check, and whether any needed a reply.

Replying matters as much as counting. A weekly rhythm of checking for new reviews and responding, especially to anything critical, tells you more about how your shop is doing than the raw count ever will. A count alone can rise or stall for reasons that have nothing to do with service quality, seasonal traffic, a slow week, a competitor closing nearby, so treat it as one number among several, not a verdict.

One thing worth naming honestly: any metric here that gets tied to an individual person's performance can be gamed, even unintentionally. If you ever find yourself wanting to measure how many reviews mention a specific staff member by name, ask why you want that number before you start tracking it. A safer version of the same curiosity is simply reading new reviews together as a team and noting what customers said they liked, without turning it into a scoreboard.

The weekly log itself does not need to be complicated. A simple notebook or spreadsheet with four columns, date checked, total review count, new reviews since last check, and whether each was replied to, is enough to see direction over time without requiring any tool beyond what your Business Profile already gives you for free. Keep the log itself out of the break room where it could turn into an informal leaderboard by accident; it is an owner's tool for tracking the shop's overall standing, not a staff performance sheet.

Handling the Edge Cases

A customer with an unresolved complaint should never be asked for a review in that moment, full stop. Fix the problem first, follow up separately if you follow up at all, and let enough time pass that the ask does not read as an attempt to paper over what went wrong.

A customer who asks what to write should get an honest, simple answer: whatever was true for them. Staff should never suggest specific wording, star ratings, or phrases, both because it edges toward the kind of review manipulation Google's policies prohibit and because a review written in someone else's words rarely sounds genuine anyway.

A tourist in a hurry, someone clearly passing through with a flight or a checkout time to make, is a case where the quick order script applies, offered once, not repeated, and dropped entirely if the person seems stressed. There is no version of chasing a stranger out the door for a review that reflects well on your shop.

Across all of these edge cases, the same underlying rule holds: the ask should never make a customer's day worse, even slightly, in exchange for the chance of a review. If a moment does not feel right for it, skip it. There will be another moment.

It is worth building a short, informal debrief into your regular team meetings for edge cases that came up during the week. A barista who was unsure whether to ask a particular customer, or who handled a tricky complaint moment well, should be able to bring that up and talk it through with the rest of the team. That kind of ongoing conversation does more to keep the whole approach honest and consistent over months than a single fifteen minute session ever could on its own, since real situations rarely match a script exactly.

Frequently Asked Questions

Should every staff member ask every customer for a review?

No. The ask stays optional in every moment and gets dropped for customers who are rushed, upset, or plainly uninterested. Training gives staff comfortable, honest language for the moments where it fits: a direct, personal line for a warm regular, one short sentence for a quick order, and a later, separate ask, or none, after a resolved complaint. The goal is a consistent, natural habit across shifts, not turning every transaction into a request.

Can we offer a discount or free item for leaving a review?

No. Google's Business Profile guidance on getting reviews from customers and its policy on user contributed content both prohibit incentivized reviews, so nothing can be offered in exchange for one, positive or otherwise. That rules out discounts, free drinks, and perks or pay tied to review counts. Cover this in the three minute policy segment of your fifteen minute training session, so every staff member knows the line before they ever make an ask.

Can staff or their family members leave reviews of the shop?

No. Google's policy treats reviews from employees or their families as a conflict of interest, since they undermine what a review is for. Cover it plainly in the three minute policy segment of the fifteen minute training, alongside the bans on incentives and on asking only customers likely to be positive. Repeat the same explanation for every new hire during their first week, so nobody breaks the rule without realizing it.

How long should a review training session take?

Fifteen minutes works well as a structure: two minutes on why reviews matter, three minutes on policy dos and don'ts, six minutes of script practice in pairs said out loud, and four minutes for open questions. Timing it with a dry run and adjusting the segments to fit keeps the session tight and repeatable for new hires.

What should we do if a customer had a complaint that got resolved?

Never ask for a review in the same conversation as an apology or a fix. If the issue was resolved and the customer seems satisfied, an ask can come later and separately, framed around the shop generally rather than the specific problem, and staff should feel free to skip it entirely if the moment does not feel right.

Should we rank staff by how many reviews they generate?

No. A leaderboard tied to review counts puts pressure on how customers are treated, and it can tempt a well meaning barista toward the incentivized or gated asks Google's policies prohibit. Never tie pay, tips, or perks to reviews. Instead, read a specific, well written review aloud at a team meeting and thank the person it describes, treating the review as evidence of good service rather than the target. Tell staff directly that no ranking exists.

What can we safely track without outside software?

Your Google Business Profile already shows total review count and recent reviews, which is enough for a weekly log with four columns: date checked, total count, new reviews since the last check, and whether each got a reply. Replying, especially to critical reviews, tells you more than the count, which can stall for reasons like seasonal traffic or a slow week. Keep the log out of the break room so it never becomes a leaderboard.

Is it okay to tell a customer what to write in their review?

No. Suggesting wording, phrases, or star ratings edges toward the review manipulation Google's policies prohibit, and a review written in someone else's words rarely sounds genuine to the next reader. If a customer asks what to write, staff should answer simply: whatever was true for you. Cover this during the six minute script practice in your fifteen minute training, so staff have the honest answer ready before the question comes up at the counter.

How do we handle a tourist or someone in a hurry?

Use the quick order script: one short line such as thanks for coming in, if you get a chance a review helps us out a lot, said once while handing over the cup. Never repeat it or follow someone toward the door, and skip it entirely if the person seems stressed about a flight or a checkout time. There is always another moment, and the ask should never make a customer's day worse.

What is the single biggest mistake shops make with review training?

Treating it as a quota instead of a habit. A target, even an informal one, tends to make staff either avoid the ask out of discomfort or push it in ways that feel transactional to customers. A short, honest script practiced out loud, paired with recognition that celebrates service rather than counts, tends to hold up better over time.

Work with Hillcane

Reviews should not depend on which barista happens to remember to ask. A fifteen minute training session and a script your staff would actually say fixes that without a quota in sight.

If you want help building a review routine that fits your shop's own voice, reach Hillcane at hillcane.co/contact or call (256) 384-2449.