Google Review Card Staff Prompt Playbook

Why the prompt matters more than the script

Everyone has been on the receiving end of a review ask that went wrong: the server who recites a memorised paragraph at the exact moment your payment card is in the terminal, or the cheerful 'don't forget to rate us!' delivered to the back of your head as you are already halfway to the door. The request was probably worded fine. The moment was a disaster. Operators tend to obsess about the wording of the ask. The wording matters, but the timing and motion of the prompt matter more. A clumsy script at the right moment outperforms a perfect script at the wrong moment, and the teams that get this programme right usually spend 80% of their effort on timing and handoff motion and only 20% on copy.

• Customers decide whether to engage with a review prompt in the first two seconds. That window is controlled by when staff asks, not by the specific words used. The exact same sentence can feel warm at the right moment and intrusive at the wrong one, and the customer judgement is pre-verbal. A well-timed ask rides the natural goodwill of the end of service; a mistimed ask runs against it.
• A natural prompt at the right moment produces 5–15% conversion (some luxury hospitality teams see 20–25% on exceptional service days). An awkward prompt at the wrong moment produces under 1%, regardless of how polished the script reads, and worse. It trains the team to believe the programme does not work and to quietly stop asking. The timing decision determines the entire programme's upside.
• The prompt has to fit the service rhythm. If asking for a review interrupts the handoff flow, staff drops the script within days; if it completes the handoff flow, staff sustains it for months. The best review prompts are indistinguishable from the rest of the service choreography. The 'thank you for visiting' line that was already there, now with a card in hand.
• Staff discomfort is a leading indicator of script failure. If the pilot team looks embarrassed delivering the prompt, or visibly rushes it, or skips steps to get through it faster, the script is wrong for this team. Rewrite before you train harder. A script that staff cannot say authentically never scales.
• The ask-versus-gift framing matters: customers respond better to 'a quick review helps us a lot' than to 'please rate us' because the first frames it as a generous act and the second frames it as an evaluation assignment. Gift framing feels reciprocal; evaluation framing feels hierarchical and less motivating.

Finding the right service moment

Every hospitality and service workflow has a natural pause point. The prompt belongs inside that pause. Not before it, not after it. Identifying the pause is usually a five-minute conversation with a seasoned floor manager; the harder work is protecting that pause from the operations habits that tend to erode it. The manager who works the floor can usually point to that moment without thinking; the planning deck almost never finds it.

• Restaurants: after settling the bill, before the card machine leaves the table. The customer is about to leave anyway; the prompt adds seconds, not friction. Fast-casual and QSR have a shorter window. At the counter after the order is handed off, or in the drive-through after the bag is passed. Each format has a distinct pause point and the prompt adapts.
• Retail: after the payment terminal confirms and the receipt prints. The customer is waiting for the card to return, the bag to be handed over, or the change to be counted; the prompt fills that wait naturally. In premium retail, the post-sale 'anything else for you today?' line is the natural home; in pharmacy, the prescription handoff is the moment.
• Hotels: at checkout, after the folio is settled and the key card is collected. The customer is about to depart; a short card handoff slots neatly in. For extended-stay properties and loyalty-elite guests, the prompt can alternatively come earlier. During the 'how was your stay?' conversation mid-visit when the guest is still engaged and has concrete impressions to share.
• Salons and spas: at the front desk after the service is complete and payment is done. The customer is in a post-service glow (hair styled, nails finished, massage afterglow) and the prompt captures that mood. The stylist or therapist can also hand a personalised card at the chair, which typically converts 2-3× the front-desk version because the emotional bond is freshest.
• Pickup counters: while the order is being bagged or at the moment of handoff. Twenty seconds of attention the customer is already giving the counter, often with their phone already in hand because they scanned a QR code to confirm the order. This is the only customer-facing moment in a pickup flow and the card has to use it.
• Healthcare and dental: at the reception desk at discharge, after any paperwork is complete. Senior patients respond well to a warm hand-delivery; younger patients often prefer a card placed face-up on the counter with a verbal cue. The prompt must never feel like it is asking the patient to review during vulnerability. Always after service completion, never during a clinical interaction.
• Wrong moment indicators: before service is complete (the review isn't earned), during payment (the customer is distracted and the ask feels like upsell), when a queue is visibly waiting (staff feels rushed and delivers a poor prompt), when there is any sign of dissatisfaction (the prompt feels tone-deaf and the review will likely be negative), when the customer is on a phone call (the moment is already taken), when a child is having a meltdown (the parent has no bandwidth).

Scripts that survive three weeks of service pressure

A script has to be short enough to use under pressure and flexible enough to sound different coming from different staff members. Corporate-tone scripts fail; conversational scripts survive. The test of a good script is not how it reads on paper. It is how it sounds when a tired server says it at 9:45 pm on a Friday after a double shift.

• Base ask: 'If you had a good time with us, a quick Google review helps us a lot.' Handed card. That's the entire prompt. Short, warm, platform-named, action-implied. This single line converts across verticals and team types with only minor localisation.
• Add warmth: 'Hope you enjoyed dinner. A Google review would mean the world to our chef.' The emotional hook belongs in the second sentence, not the first, because the first sentence's job is to set the action. Leading with emotion before the ask buries the request and confuses the customer about what is actually being asked.
• Hotel variant: 'Thanks for staying with us. If your visit was good, a quick Google review helps the next guest find us.' The 'helps the next guest' framing is particularly effective in hospitality because guests understand travel research and recognise that other travellers will benefit. It converts the ask from 'help us' to 'help your community', which feels more generous.
• Retail variant: 'Glad we could help find what you were looking for. If you have 30 seconds for a Google review, it really helps the shop.' The 30-second time cue is effective because it quantifies the ask. Customers who hear 'quick review' imagine different timeframes, and some imagine 5 minutes and decline. 30 seconds removes that objection.
• Healthcare variant (dental, clinic): 'Thanks for coming in today. If you have a moment, a quick Google review helps other patients find us. Takes about 30 seconds.' The healthcare variant is more reserved and explicitly time-bounded because patients in healthcare contexts are more cautious about promotional requests during medical interactions.
• Avoid corporate phrasing: 'We would appreciate your feedback on our Google Business Profile' sounds like a survey, not a chat. Customers disengage. 'Please consider leaving a review at your convenience' sounds like an HR memo. The script has to sound like a human being talking to another human being. That is the only register that survives service pressure.
• Never sound conditional: 'If you wouldn't mind...' and 'only if you have time...' signal that the ask is unimportant, and also that the asker is uncomfortable with their own request. The ask has to feel confident to convert. Confidence does not mean pushy. It means the staff member believes the ask is reasonable and the customer is likely to agree.
• Pair the script with a staff-chosen variant: let individual team members adapt the wording within a locked structure. One server might prefer 'appreciate it if you could'; another might prefer 'help us out a lot'. Flexibility within structure produces more authentic delivery than a locked script, and authenticity is what converts.

The handoff motion

The physical motion of handing over the card is as important as the script. Practised well, the motion takes three seconds and feels like service; practised badly, it feels like upselling. The gap between gracious and pushy is a narrow one, which is why the motion is drilled and not merely described. The motion is teachable in five minutes and worth re-teaching every quarter, because it is the first thing staff stop doing as service pressure rises.

• Card is already in the staff's hand before the prompt starts. Reaching for a card while saying the script halves the conversion because the customer sees the staff member fumble for something and mentally categorises the moment as 'they're trying to sell me something'. Staff should pre-position cards at the start of each shift. In a front-pocket stack, in a server-book insert, or beside the register.
• Card is placed on the counter face up or handed over with a specific gesture (a small two-finger offer from waist height, not a thrust from above). The card should feel offered, not imposed. Placement face-up means the action line is immediately visible; face-down requires the customer to flip the card, which adds friction.
• Eye contact at the moment of handover. A card handed over while looking at the till, the receipt printer, or the next guest reads as afterthought. A half-second of eye contact with a small smile converts the gesture from 'transaction completion' to 'personal ask', and the conversion difference is substantial.
• Slight smile on delivery. The prompt should feel like warmth, not a sales request. A smile also signals to the customer that the ask is normal and expected rather than awkward or exceptional. If the staff member looks uncomfortable, the customer reads discomfort and backs away.
• Walk-away: staff immediately returns to service or moves on. Hovering for the customer to tap creates pressure and reduces conversion. Customers who feel watched will pocket the card and never use it. The pattern is ask, place, walk; the customer's decision happens without an audience.
• For stand-based placements, the motion is a point and a sentence: 'there's a quick Google review card here if you have 30 seconds'. The customer decides the pace. Stand-based prompts convert at 3-8% versus 10-15% for hand-delivered, but they require no staff effort and they work in high-volume or unattended moments where hand-delivery is impossible.
• Card orientation on handoff: the QR code and action line should face the customer, not the staff member. This sounds obvious but it is one of the most common mystery-shop findings. Staff hand the card with the QR facing themselves, which forces the customer to rotate the card before they can read it.
• Under-pressure fallback: on peak shifts when the full handoff motion is impossible, staff can skip to 'point-at-the-stand' mode for one shift without abandoning the programme. Trading conversion rate for sustained coverage is a better outcome than dropping the prompt entirely during peak.

Training rhythm and decay prevention

Staff prompts decay within four to six weeks unless actively maintained. Managers who expect the script to self-sustain are disappointed; managers who build a light training rhythm see sustained results. The rhythm does not have to be heavy (five minutes per huddle, one conversion check per month) but it has to be consistent, because consistency is what the team reads as leadership priority.

• Week 1: training. Five-minute team huddle covering the prompt, the timing, the handoff motion. One role-play per staff member, practised with the manager playing the customer. Include both the 'customer says yes' and 'customer says no thanks' branches so staff knows what to do in both paths and neither response catches them off-guard.
• Week 2: observation. Manager watches two to three real handoffs per staff member and coaches quietly. No public corrections: feedback happens privately at shift end, because public correction in front of customers erodes team confidence and staff starts avoiding the prompt to avoid being observed.
• Week 4: first conversion check. Pull Google review velocity and share the number with the team. 'we went from 5 reviews last month to 18 this month, nice work'. Concrete numbers are the single most motivating training tool available; vague praise ('you've been doing great with the reviews') has a fraction of the impact of specific numbers.
• Week 8: refresh. One team huddle revisiting the prompt. Address any drift, celebrate high performers, surface any script friction the team has discovered. The refresh huddle is also the moment to introduce any script iteration based on pilot data. Letting the team see their input shaped the final script builds buy-in.
• Month 3+: monthly review velocity check. If conversion drops 20%+, diagnose whether it's prompt decay (team stopped asking), staff churn (new hires not trained), card wear (placements getting tired), or a placement issue (counter layout changed). Each diagnosis points to a specific intervention, not a general 'try harder' message.
• New-hire onboarding: the prompt is part of the service training from day one, not an optional add-on or an after-thought added in week three. Every new hire gets the prompt demoed by a peer on shadow shifts, practised in role-play, observed on their first live shift. Programmes that depend on new-hire memos without practice do not survive the first staff turnover cycle.
• Managerial signal: if managers do not prompt themselves on the floor, staff correctly reads it as low priority and the programme dies. Floor-working managers who still prompt when they are on the line anchor the programme's legitimacy; manager-from-the-office programmes degrade within 60 days. This is the single most diagnostic variable for programme sustainability.
• Celebration cadence: month-one spike, month-three plateau, month-six re-energise. Each of these is a natural moment for a team-level acknowledgement. A lunch, a small bonus tied to programme metrics, or just public recognition at the all-hands. Programmes without celebration moments become rote; programmes with them stay visible.

Matching prompt style to team reality

Not every team can sustain a hand-delivered prompt. Forcing one on a team that cannot support it produces worse results than designing around the team's real capacity, because an unsustainable programme quietly dies and also erodes trust in future operator-led programmes. Design for the team you have, not the team you wish you had.

• High-touch teams (fine dining, luxury hotels, premium salons, concierge healthcare): hand-delivered card with a personalised ask. Conversion is high (10-20%) and feels on-brand. These teams are usually smaller, more tenured, and comfortable with relationship-led service; the hand-delivered motion is already part of their rhythm. Invest here in personalisation. Server name on the card, a sentence about the specific service received.
• Mid-touch teams (casual restaurants, hotel front desks at scale, mid-tier retail, dental practices): card handoff with a short general script. Conversion is solid (5-10%) with moderate training investment. These teams need more training structure than high-touch teams and benefit from role-play in onboarding, but they can sustain hand-delivery with quarterly refreshers.
• High-volume teams (fast casual, QSR, convenience retail, pickup counters, drive-throughs): gesture to a stand or sticker, short verbal cue ('quick Google review over there?'). Lower conversion per interaction (2-5%) but high absolute volume because transaction count is so much higher. Do not force these teams into hand-delivery; the transaction window is too short and the prompt collapses under time pressure.
• Low-staff moments (self-service, unattended pickup, delivery drops, kiosk ordering, vending): no prompt; rely on fixed placement with strong copy and a prominent card or sticker. Conversion is lower still (1-3%) but the alternative is no programme at all in these contexts. Strong placement design compensates for the missing verbal cue.
• Franchise teams with high turnover (QSR franchisees, convenience retail, some hotel-brand franchise teams): simpler script, more reliance on physical placement, monthly training refresh built into the shift schedule rather than depending on individual manager initiative. The programme design assumes that 30-50% of the team six months from now will be different from today's team.
• Mixed-shift teams (hospitality operating 16+ hours daily, hotels with 24-hour front desks): each shift needs its own training and its own champion, because the dynamics of a 7am breakfast service and a 10pm late check-in are genuinely different. Cross-shift consistency requires intentional design, not just a single training event.
• Seasonal teams (resort, tourism, holiday retail): the programme needs a season-opening training ramp and a season-closing debrief, with written playbooks that survive the off-season gap. Seasonal teams do not remember programmes between seasons; the playbook has to carry the memory.

LMS, training-tech and operational-system integration for sustained prompts

Sustained staff-prompt programmes across more than three or four locations quickly outgrow the capacity of a single manager's memory and a paper role-play sheet. They need to live inside the learning and operations systems the team already uses. The LMS that tracks onboarding, the POS that reports transaction counts, the shift-communication app the front-line actually reads, the mystery-shop vendor that already audits service standards. Integrating the review-prompt programme into those rails turns it from a separate initiative that competes for attention into a thin additional layer on top of the ones that already work.

• Learning-management systems (LMS) for formal training: Cornerstone Learning, Docebo, 360Learning, WorkRamp, TalentLMS, SAP Litmos, Absorb LMS, and Seismic Learning (formerly Lessonly) all support SCORM 1.2 / 2004 / xAPI (Tin Can) content packages and most enterprise-deployed hospitality and retail groups already have one of these in place. A review-prompt module typically runs 8-12 minutes of microlearning (scenario video, script walk-through, role-play quiz, handoff-motion checklist) and is assigned automatically via the LMS's new-hire curriculum trigger. Completion data feeds back to the HR system of record (Workday, UKG Pro, BambooHR, ADP Workforce Now) for compliance reporting.
• POS and transaction-count integration for denominator data: Toast POS, Square for Restaurants, Lightspeed Retail, Clover, NCR Aloha, Oracle Micros Simphony, and the retail equivalents (Shopify POS, Square Retail, Vend/Lightspeed X-Series) all expose transaction-count APIs that let the programme owner calculate prompts-per-100-transactions without manual tallying. Toast's Orders API (api.toasttab.com) exposes order-count at location-hour granularity; Square's Orders API (connect.squareup.com/v2/orders) does the same. Pairing the POS denominator with the Google review velocity numerator produces the conversion curve that drives all coaching conversations.
• Shift-scheduling and time-and-attendance integration: HotSchedules (now Fourth Engage), 7shifts, Deputy, When I Work, Homebase, Sling and Jolt let the programme owner schedule the 5-minute huddle training as a paid shift slot (avoiding FLSA 29 CFR 785.27 off-the-clock training problems under the Portal-to-Portal Act) and track completion per staff member. The huddle shows up as a shift task with a mandatory check-in, which makes training participation auditable and protects the employer in any downstream wage-hour claim.
• Front-line communication apps (huddle channel): Beekeeper (acquired by ECI 2024), Crew by Square, WorkJam, theEMPLOYEEapp, SnapComms, Axonify Communicate and Microsoft Teams for Frontline Workers carry the week-by-week programme cadence. The script card, the 'this week's coaching focus' note, the leaderboard update. Unlike email (which front-line teams rarely check), these apps have 70-90% daily open rates and support acknowledgement receipts, making coaching notes auditable. Beekeeper's open API (developer.beekeeper.io) and WorkJam's REST API both support posting programmed messages on a defined cadence.
• Microlearning and reinforcement: Axonify, EduMe, Seismic Learning, Arist (SMS-based), Spekit, Tovuti LMS and Rallyware deliver 90-second refresh bursts that counter the four-to-six-week prompt-decay curve documented in hospitality field research. Spaced-repetition scheduling (7-day, 21-day, 60-day re-exposure) has been shown in Axonify's own effectiveness studies to lift retention versus single-session training by 30-50%, and the same curve applies to review-prompt scripts.
• AI role-play and speech-coaching platforms: Second Nature (secondnature.ai), Balto (balto.ai, voice-agent coaching at the headset level), Gong.io (call-recording analytics, relevant for phone-based review-ask channels), CallMiner, Observe.AI and Yoodli all let a programme owner put a scripted role-play through an AI-graded simulation before staff delivers it to a real customer. Adoption is highest in call-centre review-follow-up programmes, where voice-agent coaching is already part of the QA stack; in-person hospitality adoption is earlier but growing.
• Mystery-shop integration for audit signal: Intouch Insight, Ipsos MSX, Maritz CX (now Merkle), HS Brands Global, Market Force Information, Reality Based Group and Coyle Hospitality already run mystery-shop audits for most multi-unit hospitality and retail groups. Adding a 'review-prompt delivered' question to the existing audit questionnaire costs effectively zero and produces a per-location adoption score over the quarterly audit cycle, which is a cheaper and more reliable signal than counting prompts-per-100-transactions manually.
• Field observation and checklist digitisation: Jolt, Opture, GoAudits, SafetyCulture (iAuditor), MeazureUp and Yoobic let district managers log observed handoffs directly on a tablet during a store visit, replacing the paper observation sheet. The data rolls up per location, per shift and per staff member, and the programme owner sees drift within a week rather than after a quarterly review.
• CRM and review-platform feedback loops: Google Business Profile API (businessprofileperformance.googleapis.com) provides first-party review count and average-rating data at per-location granularity with a 24-48 hour lag; pairing that with HubSpot, Salesforce, Zoho CRM, Birdeye, Podium or ReviewTrackers lets the programme attribute review volume back to individual locations and shifts. The attribution story matters when the franchise-operations conversation shifts from 'does this programme work?' to 'which locations are not running it?'
• Privacy, TCPA and wage-hour considerations in integration design: in-person card handoffs do not trigger TCPA (47 USC 227) because they are not automated telephone communication, but any SMS follow-up funded by the programme (review-reminder texts via Podium, Birdeye, Whistle, Kenect, Thryv or Weave) does trigger TCPA and FTSA (Florida §501.059) prior-express-written-consent requirements. Training time scheduled through the LMS and shift app must be paid under FLSA 29 CFR 785.27-785.32 if it is mandatory or if non-attendance has any employment consequence. An important detail that often surfaces only during a DOL audit.

Script governance, wage-hour compliance and enforcement precedent

Staff-prompt programmes sit at the intersection of several regulatory regimes most operators do not think about until an enforcement letter arrives. The FTC 2024 Rule on Consumer Reviews and Testimonials (16 CFR Part 465), the 2024 FTC refresh of the Endorsement Guides (16 CFR 255), FLSA training-time rules, state consumer-protection statutes, EU/UK fake-review regimes and union script-bargaining obligations all shape what a legitimate staff prompt can say and how it can be enforced. A governed programme documents those constraints up front; an ungoverned one discovers them the hard way.

• FTC 16 CFR Part 465 (Rule on the Use of Consumer Reviews and Testimonials, effective October 21, 2024): prohibits fake reviews, review suppression, buying positive or negative reviews, undisclosed insider reviews, and review hijacking. Civil penalties up to $51,744 per violation (2024 adjusted amount, 16 CFR 1.98). Staff-prompt programmes remain clearly legal because they are solicitations of honest first-person reviews from real customers; the line is crossed only when the prompt is conditional on a positive review ('only ask if you had a 5-star experience') or when an incentive is paid in exchange for a specific rating.
• FTC 16 CFR Part 255 (Guides Concerning the Use of Endorsements and Testimonials, 2023 refresh): requires clear and conspicuous disclosure of any material connection between the review writer and the business. A plain unconditional staff ask ('a quick Google review helps us a lot') does not create a material connection. An incentive-tied ask ('leave a review and get 10% off your next visit') does create one, and would require disclosure under §255.5 and would also likely violate Google's own Prohibited & Restricted Content policy on review gating and incentives (support.google.com/contributionpolicy/answer/7400114).
• Google Business Profile review policy enforcement precedent: Google removes reviews and (in repeated cases) suspends the Business Profile when incentives, gating, or staff-manipulation are detected. High-profile enforcement examples include widespread takedowns across dealer groups in 2022-2023 after the Attorney General of New York Lifestyle Lift 2009 precedent pattern reappeared, and the Xlear v. Google litigation (D. Utah 2023-2025) that has been debated as a First Amendment case but has not changed the underlying Google policy that gated review workflows are prohibited. A staff prompt that says 'only ask if the customer seems happy' is de facto gating and creates suspension risk.
• State consumer-protection enforcement: California Business & Professions Code §17200 (Unfair Competition Law), §17500 (False Advertising), and the CLRA (§1750) all apply to deceptive review practices. New York Executive Law §63(12) and GBL §349/350 cover the same ground. Texas DTPA, Florida Deceptive and Unfair Trade Practices Act, and the Massachusetts Chapter 93A statutes similarly apply. FTC Fashion Nova settlement 2022 ($4.2M for review suppression), Sunday Riley 2019 FTC consent order (for staff-written fake reviews), and the 2020 Sunday Riley follow-up civil penalty all create a precedent pattern operators should know before designing the script governance.
• FLSA training-time compensability (29 CFR 785.27-785.32): training is non-compensable only if all four Portal-to-Portal Act tests are met (outside normal hours, truly voluntary, not job-related, no productive work). Review-prompt training almost always fails the 'not job-related' test, so the 5-minute team huddle has to be on the clock. DOL Wage and Hour Division regional audits routinely flag unpaid training time in hospitality and retail, and the exposure is three years of back pay plus liquidated damages plus §216(b) attorney fees in class actions. Scheduling huddles through the shift app (7shifts, HotSchedules, Deputy) as paid shift tasks is the cleanest audit defence.
• Tip-credit and gratuity interaction (29 CFR 531.52-531.56 and the 2021 tip-rule final rule at 29 CFR Part 10): in tipped-worker contexts, the 80/20/30 rule (as of December 2021 and further clarified in the 2024 Fifth Circuit Restaurant Law Center v. DOL decision) constrains how much time a tipped employee can spend on non-tip-producing work while still being paid the tipped minimum wage. A prompt delivered inside the natural service flow is part of tip-producing work; a separate standing session soliciting reviews off the floor is not. Programme design needs to keep the prompt inside the service flow to stay on the right side of this distinction.
• NLRA concerted-activity protection (29 USC §§157-158, NLRB 2023 Cemex decision): if staff collectively raise concerns about the prompt (pace, discomfort, perceived pressure on customers), those conversations are protected concerted activity. Disciplining a staff member for publicly pushing back on the script is an unfair labour practice and carries reinstatement-plus-backpay risk. Good programmes treat pushback as script-improvement signal, which also aligns with NLRA compliance. The legal rail and the operational rail point the same direction.
• ADA reasonable accommodation (42 USC §12112, 29 CFR 1630.2(o)): staff with speech-related disabilities (stuttering, aphasia, certain anxiety disorders) may need a written card handoff without the verbal script, or a signed-language alternative in ASL-speaking teams. Accommodation requests have to be handled through the employer's standard interactive process, and 'everyone has to say the script exactly' is not a defensible posture if an accommodation request arrives. Building a pre-approved written-only variant into the playbook closes this exposure in advance.
• Union script-bargaining: UNITE HERE, SEIU, Teamsters and Workers United contracts in hospitality (major properties under Marriott, Hilton, Hyatt, Accor; major retail under Kroger, Albertsons, Macy's; major food service under Sodexo, Aramark, Compass) may require bargaining before adding new scripted duties under the 'scope of work' and 'new job classification' clauses. NLRA §8(a)(5) duty-to-bargain applies; the remedy is typically a bargaining order plus any lost-opportunity backpay. Programme rollouts in unionised properties need labour-relations sign-off alongside operations sign-off.
• International rules for multinational rollouts: EU Digital Services Act (Regulation 2022/2065, Articles 30-31 on trader traceability and review authenticity, fully applicable since February 2024), Omnibus Directive (2019/2161 amending UCPD Article 7(6), in force May 28, 2022) banning fake reviews and undisclosed paid endorsements across EU27. UK Digital Markets, Competition and Consumers Act 2024 (Royal Assent May 24, 2024, most provisions commenced April 2025) criminalises commissioned fake reviews with fines up to £300,000 or 10% of global turnover per CMA determination. Australia ACL §§18, 29, 33 (Australian Consumer Law); Canada Competition Act §52; Singapore CPFTA; Japan Act Against Unjustifiable Premiums and Misleading Representations. All prohibit the same patterns. A global staff-prompt programme needs one legal baseline that is tight enough for the strictest regime (UK CMA 2024) and adapts locally from there.
• Documentation as defence: a programme that keeps the script, the training record (LMS completion), the mystery-shop adoption score, the shift-app huddle log, and the Google review velocity numbers together in one governance file is in a strong position against any regulatory inquiry, whether FTC, DOL, state AG, or EU/UK equivalent. The documentation also serves as the franchise-manual exhibit when a franchisee wants to contest a programme mandate. Which, in many multi-unit organisations, is the more common adversarial scenario than a regulator.

Ready-to-use script library — copy-paste prompts by vertical

The script library below is intended to be copy-pasted into a shift-app huddle, a laminated desk card or a new-hire onboarding deck. Each script is one sentence, under 15 words, and has been used in operator deployments where it converted in the 5-15% range when delivered consistently. Pick the variant that fits the venue voice and let the local staff adapt the wording inside the locked structure.

• Restaurant (full-service): 'If dinner was a good one, a quick Google review helps the chef out. Takes 30 seconds.' Delivered with the bill folio at table, before the customer signs the slip. The 30-second time cue removes the silent objection 'how long will this take?'
• QSR / counter-service: 'Quick Google review on the way out? There's a card right here.' Pointed at, not handed. Customer at the pickup counter has 20-30 seconds while waiting for the order to be called.
• Coffee shop: 'Loved your latte? A Google review keeps the lights on for a small shop.' Handed at register handoff. The 'small shop' framing converts particularly well at independent and neighbourhood cafes.
• Hotel front desk (checkout): 'Thanks for staying with us. If your visit went well, a Google review helps the next traveller find us.' Delivered with the folio at checkout, in the 30-second window before the bellhop motion.
• Hotel concierge: 'It was a pleasure helping you with [restaurant/excursion/booking]. If you found the recommendations useful, a Google review is the best thank-you we can ask for.' Personalised to the specific concierge interaction, which converts 2-3x the generic ask.
• Dental practice (reception checkout): 'If today went well with the team, a quick Google review helps other patients find us. Takes 30 seconds.' Generic deliberately, no clinical reference, no specific dentist named, complies with HIPAA marketing rules.
• Salon (mirror reveal by stylist): 'If you love how it turned out, a Google review for the salon would mean a lot.' Stylist-delivered at reveal; converts 2-3x the front-desk version because the relationship is direct.
• Spa treatment-room exit: 'I hope you feel relaxed. If today was good, a quick Google review helps us. The card's right here when you're ready.' Soft, no pressure, leaves the card on the side table.
• Fitness PT milestone: 'You crushed that PR today. If you're up for it, a quick Google review for the studio helps me out a lot.' PT-delivered after a personal record or block-completion; converts at 15-25%.
• Auto sales delivery (F&I / salesperson): 'If your buying experience went well, a Google review helps the next customer find us.' Delivered at key handoff in the delivery bay; substantive sales reviews are the most influential for new-car shoppers comparing dealers.
• Auto service pickup (advisor): 'If service went well today, a Google review helps us out.' Shorter than the sales script because the interaction is shorter; delivered at key return.
• Retail boutique: 'Glad we could help find what you were looking for. If you have 30 seconds for a Google review, it really helps the shop.' At register handoff with the bag.
• Healthcare (urgent care, walk-in clinic discharge): 'Thanks for coming in today. If you have a moment, a quick Google review helps other patients find us.' Generic, no clinical reference, delivered with discharge paperwork at checkout.
• What every script avoids: conditional phrasing ('if you wouldn't mind', 'only if you have time'), emotional escalation ('would mean the world', 'we'd be so grateful'), corporate speak ('we appreciate your feedback'), gating language ('if you had a 5-star experience'), incentive trade ('leave a review and get 10% off').

Pre-launch staff-training checklist — 10 items before the first live shift

The checklist below is the structured version of what experienced operations leads run through before the staff prompt programme goes live on the floor. Run through it as a yes/no list with the manager and the pilot team in a 30-minute pre-shift meeting. Each missed item is a typical failure mode that the pilot will then have to surface the hard way.

• Script chosen, written down, and laminated at the staff station: one sentence, under 15 words, names Google explicitly, uses an imperative verb, no conditional or gating language. Posted where reception can glance at it without breaking eye contact with the customer.
• Staff role-play completed: every team member who will deliver the prompt has rehearsed it three times, with the manager playing the customer including both the 'yes' and 'no thanks' branches.
• Manager commits to delivering the prompt themselves on the floor: at least 3-4 prompts per shift, visible to staff, modelling the behaviour. Manager-from-the-office programmes degrade within 60 days.
• Card location specified: the physical card is within arm's reach of the seated/standing staff member, in the line of motion of the handoff. Not in a drawer, not in a rack behind the monitor, not at the far end of the counter.
• FLSA-compliant huddle scheduled: the 5-minute training huddle is on the clock, posted in the shift app (HotSchedules, 7shifts, Deputy, When I Work) as a paid task. Training on personal time is non-compliant under 29 CFR 785.27 if it is mandatory or job-related.
• Mystery-shop or peer-observation cadence agreed: the manager observes 2-3 real handoffs per staff member per week for the first month, with private (not public) feedback at shift end. Public corrections in front of customers erode team confidence.
• Compliance script-check completed: no incentive language ('review for a discount'), no gating language ('only ask if customer seems happy'), no clinical reference (in healthcare contexts), no quid-pro-quo phrasing of any kind. Brief team explicitly that gating violates Google policy and FTC 16 CFR 465.
• Measurement baseline captured: the location's Google review velocity (reviews per month, average rating) for the 4 weeks before launch, recorded in writing. Without the baseline, the post-launch lift is anecdote, not evidence.
• Accommodation paths defined: written-only variant (no verbal script) ready for staff with speech-related disabilities or anxiety; Spanish or other-language script variant ready for non-native-English speakers on the team.
• Pilot exit criteria written before launch: 'at least 50% of prompt-eligible transactions see the prompt' and 'review velocity lifts to at least 2x baseline over 4 weeks'. Writing the criteria before the data arrives prevents motivated-reasoning interpretation at the pilot review.

Common staff-prompt mistakes — eight patterns that consistently kill adoption

The patterns below are the ones we see across operator pilots that under-perform. Each one is invisible in the design slide and obvious only after week three of live service. Memorising them shortens the pilot review meeting because most diagnoses end up pointing at one of the eight.

• Long corporate script that no one can use under pressure: 'We would appreciate your feedback on our Google Business Profile' becomes 'thanks' within two weeks because nobody can deliver the long version on a busy Friday. Fix: one sentence, under 15 words, conversational verb.
• Manager does not prompt themselves: staff correctly reads it as low priority and the programme dies within 60 days. Fix: manager delivers 3-4 asks per shift visibly on the floor; documented in the manager job description.
• Reception fumbles for the card while delivering the script: customer registers 'they're trying to sell me something' and disengages. Fix: card pre-positioned in hand or arm's reach before the handoff begins; pre-positioned at shift start.
• Conditional phrasing creeps in: 'if you wouldn't mind' and 'only if you have time' signal that the ask is unimportant. Conversion drops 30-50%. Fix: imperative verb, no conditional. Confidence does not mean pushy; it means the staff member believes the ask is reasonable.
• Public correction of a hesitant staff member in front of a customer: humiliated staff stops prompting to avoid being observed. Fix: feedback at shift end, privately; coaching in 1:1 setting, never in front of customers.
• Gating language ('only ask if the customer seems happy'): de facto review gating, violates Google's Prohibited Content policy, has triggered Business Profile suspension across dealer groups and dental practices. Fix: universal prompt for every prompt-eligible transaction.
• Incentive trade ('review and get 10% off'): violates both Google's policy and FTC 16 CFR 255 endorsement guides. Civil penalties up to USD 51,744 per violation as of 2026. Fix: no material benefit linked to a review, ever, documented or undocumented.
• No new-hire training: existing staff trained at launch, new hires onboarded without the prompt. Six months later, the team is half new hires and the programme runs at 30% of launch capacity. Fix: prompt is part of the standard new-hire onboarding from day one.

A four-week staff-prompt pilot

Before committing to a full print run and a company-wide script, run a structured pilot. Four weeks is the minimum length to see past weekly noise (weather, local events, staff rotation, random coincidence), and the pilot is where nine out of ten script, timing and motion issues surface before they become network-wide problems. A pilot costs one location and a month of attention; skipping it costs a warehouse of beautifully printed cards for a script the team quietly abandoned after the first busy Friday. Run the pilot.

• Week 0 — preparation: select one location, pick two to three staff champions (tenured staff members who are respected by peers, not necessarily the managers), brief them on script and motion, role-play the handoff twice, print 200 pilot cards with a per-location URL already in place. The champions will anchor the programme's credibility with the rest of the team.
• Week 1: observe. Track how often the prompt actually happens. Manager shadows two shifts and counts prompts per 100 transactions. The first-week number is almost always below expectations. Staff need the first five to seven days to build muscle memory. Do not panic and do not coach yet; just observe and record.
• Week 2: measure. Track Google review velocity against the prior four weeks, along with prompts-per-100-transactions from week 1. Note which staff members prompt most often and which hesitate. The variance across staff members is almost always larger than expected, and understanding the variance is the foundation of the coaching plan.
• Week 3: coach. Address hesitation individually: what specifically is hard about the handoff for this staff member? Is it the phrasing, the moment, the walk-away? Share early wins publicly ('we're up from 6 reviews last month to 15 this month'). Adjust the script wording if a specific phrase is consistently hard to deliver; the script should serve the team, not the other way around.
• Week 4: decide. Review velocity lift, staff adoption, customer reaction (complaints, body language during the ask, re-ask rates). Decide whether to scale (all three exit criteria pass), iterate (one criterion misses and has a clear fix), or shift to a self-serve placement (two criteria fail and the team cannot sustain hand-delivery).
• Pilot exit criteria written before week 0: at least 50% of prompt-eligible transactions see the prompt (ideally 70%); review velocity lifts at least 2× over baseline; no staff member actively resists the programme; customer reaction is neutral-positive (no complaints, no defensive body language). Writing criteria before the data arrives prevents motivated-reasoning interpretation at the week-4 review.
• Failure modes and their fixes: if staff will not prompt, redesign as self-serve with strong placement; if staff prompt but customers do not engage, the moment or the card is wrong; if staff and customers both engage but reviews do not appear, the redirect routing is broken and the Place ID mapping needs verification. Each failure points to a specific fix rather than 'try harder'.
• Post-pilot documentation: the programme owner writes a 2-page memo covering the pilot numbers, the staff feedback, the script iterations, and the go/iterate/stop decision with rationale. The memo becomes the training asset for the rollout, the evidence in the franchisee conversation, and the audit trail when the programme is reviewed a year later.

FAQ