Google Review Cards For Restaurant Franchises

Why restaurant franchises are a specific review-programme case

Restaurant franchises look like standard multi-location service businesses, but the service-flow diversity within one brand, the franchisor-franchisee split, the peak-hour operating pressures, and the delivery-channel fragmentation create constraints that do not apply to retail or healthcare. A franchise programme designed on a single-format template or on a pure corporate governance assumption fails on all four structural fronts.

• Format diversity within one brand: QSR, fast-casual and full-service sub-brands each have different service flows. A single placement plan across all three almost always fits the largest format and fails the others. Parent groups like Yum! and Inspire operate brands across all three formats and need format-specific sub-playbooks rather than one global template.
• Franchisor-franchisee governance: corporate can mandate programme compliance at company-operated stores; franchisees have to want to participate. The programme has to be voluntarily attractive to franchisees, not just brand-mandated, because a mandate produces malicious compliance and a voluntary incentive produces enthusiastic adoption.
• Peak-hour operating pressure: at lunch rush and dinner rush, staff cannot add a verbal review ask to the service flow without damaging throughput. Programmes designed for off-peak conversion fail at peak, and restaurants living on thin margins cannot afford throughput damage from a prompting motion that earns them twelve reviews per shift.
• High customer turnover: restaurants see more transactions per day than most service businesses. A busy QSR can see 800–1,500 transactions per day, a fast-casual 300–600, a full-service 150–400. Small conversion improvements compound fast, but so do small handoff failures.
• Tabletop vs counter vs pickup vs drive-through: the placement format drives the prompt. Tabletop prompts reach customers during the meal; counter prompts reach them at checkout; pickup prompts reach takeout customers; drive-through requires bag-insert or receipt-printed handling because the customer is in a car.
• Delivery and third-party orders: customers ordering through DoorDash, Uber Eats, Grubhub or the brand's own app do not see the physical card. The programme has to account for the channel mix, which increasingly means virtual-brand and ghost-kitchen operations where there is no storefront card placement at all.
• App and loyalty integrations: many restaurant brands run loyalty apps with push-notification capabilities. The digital review prompt in the app, timed to fire 2–4 hours after a visit, complements the in-store card and reaches customers who left without tapping.
• Reservation-platform integration: for full-service, reservations often flow through OpenTable or Resy. These platforms have their own review systems that overlap with Google; the programme has to decide whether to direct post-reservation reviews to Google (for local-pack ranking) or OpenTable (for platform visibility). Or both, in sequence.

Per-store URL routing and owner-vs-franchisee governance

Restaurant franchises almost always need per-store URL routing. Customers are reviewing a specific restaurant, not the brand, and routing a review to the wrong Place ID damages the local map-pack ranking that drives the location's foot traffic. The admin layer has to accommodate mixed ownership. Corporate stores, franchisee stores, and multi-brand franchisees who operate several locations under the same entity.

• Subdomain pattern: review.brandname.com/store-1234, review.brandname.com/store-5678, and so on. Each 301-redirects to the store's specific Google Business Profile review URL. The brand-owned subdomain survives closures, remodellings and Google profile URL changes.
• Central admin: one admin panel mapping store number to Place ID to redirect URL, with a column for ownership model (corporate, franchisee, master franchisee). New openings, closures, rebrandings and ownership transfers all flow through this admin.
• Profile ownership: corporate brand usually owns Google Business Profiles for company-operated stores; franchisees often own their own. The programme has to accommodate both without ambiguity about who responds to reviews. Most successful programmes set response-authority policy: franchisees respond to their own stores unless escalated to corporate, corporate reserves the right to respond to legally sensitive reviews across the network.
• Franchisee onboarding: when a new franchisee joins the system, the Place ID capture and redirect mapping is part of the onboarding checklist. Leaving it to the franchisee to set up themselves produces inconsistent coverage and routing errors that show up six months later when the franchisee's marketing team tries to debug local-pack ranking.
• Closures and transfers: when a store closes or changes hands, the redirect updates within the admin and the next print-run corrects. Printed cards at a closed store become someone else's redirect traffic if the admin lags; this silently routes reviews away from living stores for months.
• Measurement tagging: appending ?src=counter, ?src=table, ?src=pickup, ?src=drive-thru, ?src=bag-insert to the redirect URL lets the brand measure which placement earns each review without changing the card print. The tag is logged in the redirect, stripped before the Google handoff, and does not appear in the review itself.
• Multi-brand franchisees: a franchisee may operate multiple brands under the same parent (Taco Bell + Pizza Hut at a highway stop, Chick-fil-A + drive-through-only KFC in the same plaza). Keep the admin mapped by store-level Place ID, not by franchisee entity; each brand has its own Business Profile even if the operator is the same.
• Corporate-store vs franchisee routing consistency: both use the same subdomain wrapper (review.brandname.com) even if the underlying Place IDs are owned differently. Customers should never see evidence that one store is franchised and another is corporate. The review flow feels identical.

QSR, fast-casual and full-service format differences

A franchise brand that uses one placement plan across all its formats will always be wrong about at least one. Format-specific placement is worth designing deliberately rather than letting each store improvise. The cost of running three format-specific playbooks at group level is trivial compared with the review volume that format-matched placement unlocks.

• QSR (quick-service): counter placement dominates. Drive-through customers rarely review from the car, so the counter-facing card is the main channel for dine-in, while bag inserts and receipt-printed URLs cover drive-through. Short, unmissable copy wins. QSR tabletop cards fail because customers eat quickly and leave without settling into the table.
• Fast-casual: mixed counter and tabletop opportunity. Customers order at the counter, sit down to eat, and the tabletop card catches them mid-meal or at the walk-out moment. Two placements, one design. The tabletop card in fast-casual formats (Chipotle, Panera, Shake Shack) converts noticeably better than the counter card because customers pause mid-meal and the table has dwell time.
• Full-service: tabletop and bill-presenter placement. The review ask fits naturally inside the bill folio at the end of the meal, and the tabletop card pairs with it during the meal itself. Full-service servers can deliver a verbal prompt with the bill that lifts conversion substantially; QSR counter staff usually cannot because the interaction is too short.
• Pickup and takeaway: a separate card or sticker at the pickup counter, routed with ?src=pickup tagging. Takeout customers review less readily than dine-in customers (they did not experience the full restaurant) but respond well to a well-placed prompt and a printed short-URL on the bag or receipt.
• Drive-through: the hardest format. Printed card or sticker attached to the bag, or printed URL on the receipt, is the only viable channel. Conversion per transaction is lower but the volume is high enough at busy drive-through stores (500–1,000+ transactions per day) that the programme still pays.
• Delivery-first brands: virtual brands operating through DoorDash and Uber Eats need a digital review prompt in the packaging insert, not a physical card at a storefront. Some brands also include a QR code on the packaging that drives to the brand's own survey first, then to Google. A two-step that lets the brand capture structured feedback alongside public reviews.
• Kiosk-order formats: increasing adoption of self-order kiosks (McDonald's kiosks, airport quick-serve kiosks) creates a new touchpoint. A small sticker or card near the kiosk's payment confirmation screen catches customers in the brief pause after ordering before they move to pickup.
• Bar and lounge separate from dining room: some full-service brands (Applebee's, Outback Steakhouse) operate bars with separate customer flow. The bar conversion is different from dining-room conversion and should be measured separately with its own placement.

Counter, tabletop and pickup placement mechanics

Most restaurant franchise review programmes succeed or fail on whether the placement is visible during the customer's actual attention window, not whether the card is present somewhere in the store. Visibility plus timing is what converts; a beautifully designed card in the wrong place produces fewer reviews than a plain card in the right place.

• Counter: card in a stand at register, face visible to the customer while paying. A card flat on the counter under receipts is invisible and produces almost no conversion. The stand should be 10–15 cm tall. Below 10 cm the card disappears into the counter clutter, above 15 cm it blocks the server's sight line.
• Tabletop: small stand on every table, clear of menus and condiments. Replace it with the table setting after every clean; if it becomes a clutter item, it disappears. Tabletop stands should be minimal. Acrylic holder, branded insert, NFC tag. Complex multi-surface stands distract during the meal and reduce conversion.
• Pickup counter: dedicated placement, not shared with the dine-in counter. Takeout customers have a different rhythm and a different conversion window; they are in pickup-and-go mode and will not navigate around a dine-in counter to review.
• Bill presenter (full-service): printed insert inside the bill folio, branded consistently with the card artwork. The moment the bill is handed over is the strongest tabletop conversion window because the customer is focused on the folio and has just articulated satisfaction by paying.
• Bag insert (drive-through and takeaway): a small card dropped into the bag with the receipt. Short copy, clear Google branding, QR visible for customers who scan later at home. Many drive-through reviews are written 30–90 minutes post-visit, often during or after the meal at home, so the insert has to survive being carried in a bag with hot food.
• Kiosk adjacency: a small stand or sticker near the kiosk payment confirmation screen catches self-order customers. Self-order customers skew younger and tap NFC readily; the kiosk-adjacent placement is one of the fastest-growing successful placements in QSR.
• Avoid: wall-mounted cards that require the customer to walk over (nobody does), menu-board inserts that compete with food ordering attention, bathroom placement (off-brand and reads desperate), inside-the-bag-at-the-bottom placement where the customer pulls out food and discards the card without seeing it.
• Seasonal menu promotion adjacency: avoid placing review cards next to limited-time-offer menu inserts because the promotion steals attention. Keep the review prompt on its own surface, visually separate from the seasonal menu campaign.

Staff prompts, peak-hour discipline and service flow

A verbal prompt lifts scan rate by roughly 30% over placement alone, but only if it fits into the existing service flow. At peak hours, a verbal prompt that slows throughput damages more than it helps. The programme needs daypart-aware rules that let staff know when to prompt and when to skip, not a single script delivered regardless of conditions.

• Script: 'If you enjoyed it, a quick Google review means a lot to us.' One sentence, delivered when the bill or receipt is handed over. Longer scripts do not survive three weeks of service pressure; staff cut back to one sentence within the first month regardless of the official script length.
• Who delivers: counter staff at QSR and fast-casual (at cash-out); server at full-service (with the bill). Host staff do not deliver the prompt because they interact with customers at arrival, not departure, and the arrival moment is too early for a review ask.
• Peak-hour discipline: skip the verbal ask at peak (11:30am–1:30pm for lunch brands, 6:00pm–8:00pm for dinner brands). The card still does 70% of the work, and protecting throughput matters more than a 30% conversion lift on a smaller number of transactions. Most franchise operators agree to this discipline once they see the per-hour conversion data.
• Off-peak conversion: that is where the verbal ask earns its lift. Train staff to default to verbal prompts during slower periods and to fall back to card-only during peak. Weekday mid-afternoon and late evening are the strongest off-peak conversion windows.
• New-customer vs regular: a verbal prompt works better on new customers; regulars feel over-prompted. Flag regulars quietly (loyalty app check-in, POS customer-note, server recognition) and skip the verbal ask with them unless there is a specific milestone like a birthday or 100th visit.
• Server-level attribution for full-service: with staff-parameter routing (?server=jm), full-service brands can run server leaderboards. Published monthly, paired with non-cash recognition. Leaderboards sustain the programme through server turnover, which averages 75% annually in the industry.
• Training rhythm: five-minute pre-shift huddle once a week covering the script, the peak-hour rule, and the leaderboard. Staff who hear the prompt repeated weekly maintain adoption; staff trained once at launch drift within a month.
• Avoid: scripted-sounding delivery, 'please' over-apology, asking for five-star specifically (review gating is against Google's terms and can de-index the profile if caught), prompting a customer who just complained about food quality or wait time.

Franchisor-franchisee governance and incentive design

In franchise networks, governance is harder than in pure corporate operations. The review programme has to reward franchisees for participating, not just brand-mandate their compliance. Mandate-driven programmes in franchise networks tend to achieve 60–70% compliance with reluctance; incentive-driven programmes reach 85–95% with enthusiasm, and the enthusiasm shows up in how staff deliver the verbal prompt.

• Corporate stores: mandate participation, measure in the standard operations dashboard, audit quarterly. Compliance should reach 95%+ within a quarter. Corporate stores also serve as the baseline against which franchisee performance is benchmarked.
• Franchisee stores: show the local map-pack impact with real data from pilot stores, subsidise the first order of cards (a meaningful gesture that removes the financial objection), let performance data drive adoption at franchisee meetings. Franchisees who see a neighbour store's map-pack move after six weeks adopt more readily than franchisees who see a deck.
• Opt-out handling: allow franchisees to opt out politely. Measure network-wide velocity, surface the gap at quarterly reviews, let the best-performing franchisees become peer advocates for the programme at franchisee conferences. Peer-driven adoption almost always outperforms corporate-driven adoption in franchise networks.
• Franchisee-specific incentives: tie review velocity to store-level marketing co-op funding, or surface review velocity in the franchisee performance dashboard. Performance-linked incentives outperform mandates, and co-op-funding ties make the programme visible at the franchisee's own P&L level.
• Brand-standard enforcement: the franchisee agreement usually already covers signage. Review cards fit inside the existing brand-standard clause rather than requiring a new contract addendum, which avoids a legal renegotiation for an operational programme.
• Multi-brand franchisees: a franchisee may operate multiple brands or multiple stores. Keep the admin mapped by store-level Place ID, not by franchisee entity; the admin audit trail then separates per-brand performance within the franchisee's portfolio.
• Master franchisee handling: in international markets, a master franchisee holds rights to a whole region and sublicenses to local franchisees. The admin layer has to accommodate this three-tier structure (brand → master franchisee → local franchisee), with clear response-authority rules at each tier.
• Franchise renewal and transfer: review velocity becomes part of the franchise-renewal scorecard over time. Franchisees whose stores underperform on review velocity across multiple consecutive quarters face renewal friction; surfacing this at the franchisee-meeting level aligns incentives early.

POS, loyalty and ordering-platform integration — routing the prompt through systems franchises already run

Restaurant franchises already run a stack (POS, loyalty, online-ordering, delivery middleware) that touches the customer at multiple points. A review programme that lives only on the physical card misses the digital touchpoints where the same customer is most reachable. Integration with the existing stack is where the second 30–40% of incremental review volume comes from, and it is almost always cheaper than additional card printing.

• Toast POS integration: Toast's Marketing add-on and the open POS API (docs.toasttab.com) allow a post-transaction SMS or email prompt to fire at a chosen delay (typical 2 hours for dinner, 3 hours for lunch). The prompt links to the per-store review.brandname.com/store-1234 redirect. Toast-powered chains like Jersey Mike's franchisees can enable this at the store-level without head-office deployment work.
• Square for Restaurants: the Customer Directory plus Square Marketing can send an automated email or SMS 2–4 hours after the customer's card is on file. The Square webhook fires on payment.created; a Cloudflare Worker or AWS Lambda receiver inspects the payload's location_id, resolves the corresponding Place ID redirect, and queues the message through the brand's messaging provider (Postmark, Twilio, Attentive).
• Oracle Micros/Simphony and NCR Aloha: older full-service POS systems do not have native post-transaction messaging, but middleware like Olo Dispatch, Paytronix and Punchh bridges the gap. Export transaction events nightly (or in near-real-time via the POS's CLI batch export) and feed them to the loyalty platform, which owns the prompt message.
• Loyalty-app prompts: Punchh, Paytronix, Thanx and Sparkfly all support post-visit push notifications with deep links. The push fires 2–4 hours after a visit detected via receipt-scan or geofence-exit. The deep link opens the review redirect in the device's default browser, which is routed to the Google app if installed and the Google review sheet if not.
• DoorDash and Uber Eats: the delivery platforms own the customer relationship for delivery orders and do not allow branded review prompts inside the platform's chat or review system. The brand's leverage is the packaging insert (a printed card dropped into the bag at the store level) and the brand's own order-confirmation email if the customer opted into marketing communications.
• Olo and online-ordering: Olo's Expo, Rails and Dispatch APIs allow post-order webhooks with order_completed and order_delivered events. Use the order_delivered event (fires when the delivery driver marks delivered) as the trigger for a follow-up review prompt email, because order_completed fires when the store prepares the order. Too early to prompt.
• Reservation platforms: OpenTable and Resy fire post-reservation confirmation and post-visit thank-you emails. For full-service brands, a custom thank-you template with the Google review link embedded (alongside or instead of the platform's own review prompt) captures Google velocity for local-pack ranking. The legal team should confirm this does not breach the platform's terms. OpenTable explicitly allows Google review links in the restaurant-branded thank-you, Resy is case-by-case.
• Store-locator and brand-site integration: the brand's store-locator page (restaurant.brandname.com/locations/store-1234) should embed the per-store Google review widget alongside the hours, menu and phone number. Customers researching the store before visiting see the live review feed; customers looking up the store after visiting find the review link at the same URL they already visited.

Crisis handling, negative-review triage and response governance at scale

A restaurant franchise running a review programme at any serious scale will receive negative reviews continuously. Some are routine (wait time, cold fries, mis-ordered drink), some are material (food safety, allergen reaction, service conflict). The programme has to define who responds, at what SLA, with what template, and when corporate escalates. Networks without clear response governance either over-respond (corporate chasing every two-star review) or under-respond (legally sensitive complaints ignored for weeks).

• Response SLA by tier: franchisee owner or GM responds to routine 1–3-star reviews within 24 hours on weekdays, 48 hours on weekends. Corporate escalation-team responds within 4 business hours to food-safety, allergen, injury or legal threats. Best-in-class franchise networks (Chick-fil-A, In-N-Out operationally though not franchised, Panera franchisees) hold to the 24-hour SLA across 95%+ of reviews.
• Food-safety triage: a review mentioning illness, food-borne pathogen symptoms (nausea, vomiting, diarrhoea within 24 hours of eating), or foreign object (glass, metal, hair) triggers corporate-tier response. Do NOT offer refunds or comps in the public response. That establishes a pattern that incentivises false claims. The public response acknowledges the concern and directs the customer to a private channel (corporate customer-care phone or email); the substantive resolution happens privately.
• Allergen reactions: anaphylaxis, hospitalisation, or severe allergic reaction mentioned in a review is a legal matter. The public response is a short acknowledgement and an explicit ask for the customer to contact the corporate risk team; no substantive admission, no offer, no defence of the store. The legal team takes over private correspondence. Insurance carriers (Lloyd's, Starr, Liberty Mutual) often have specific response-language requirements.
• Wait-time complaints: the most common 1–3-star theme at QSR. A short acknowledgement (sub-50-word template) paired with an invitation to come back during the quieter daypart is adequate. Avoid defending the wait. Customers who experienced a long wait do not want the store to justify it.
• Staff-conflict complaints: a review naming a specific employee by name triggers an HR review at the store level. The public response does not address the employee specifically; the private follow-up (store GM to customer) handles the specifics. Best practice is to remove employee-naming specifics from the public response template. Even a positive mention of an employee can create internal pay-compression issues.
• Review gating and filtering are against Google's terms: the programme must NOT instruct staff to hand the card only to customers who expressed satisfaction, must NOT gate reviews through a satisfaction-filter landing page, and must NOT offer discounts or comps in exchange for reviews. Google has de-indexed Business Profiles for review gating (Xlear vs Google precedent, various 2023–2025 de-indexing actions). Train franchisees on this because they often hear 'gate the five-stars' advice from consultants.
• Fake-review takedown: when a review is clearly fake (spam, competitor, no actual visit evidence, profanity), flag via Google Business Profile's report-review flow. Response rate from Google is 48–72 hours on obvious cases, 1–2 weeks on contested ones. The brand legal team can escalate through Google's Trust & Safety contact if the volume of fake reviews crosses a threshold (typically 10+ clearly fake reviews per location in a month).
• Crisis-spike handling: a viral complaint on Reddit or TikTok can spike a single store's 1-star count by 50–200 in 48 hours. The playbook: pause review solicitation at the affected store for 72 hours (do not add new reviews into the spike), let corporate PR respond to the underlying issue, resume solicitation once the spike cools. Continuing to solicit during a 1-star spike makes the average look worse and signals indifference.

Per-store launch checklist — 12 items before the cards arrive at the counter

The checklist below is the structured version of what experienced franchise operations leads run through before the review-card programme goes live at a new store. Each item maps to a typical failure mode at multi-store franchises; running through the list at a 30-minute pre-launch huddle catches most issues that would otherwise surface in the first month and force a stock reorder during a peak service window.

• Per-store Google Business Profile claimed and verified, with admin access mapped to the store GM plus a backup at franchisee or franchisor level. Place ID captured in the central admin alongside store number, ownership model (corporate vs franchisee), and brand sub-format (QSR, fast-casual, full-service).
• Brand-owned redirect configured (review.brandname.com/store-1234) with 301 to the store's specific Google review URL. ?src= tagging supported for counter, table, pickup, drive-thru and bag-insert attribution without changing the printed URL.
• POS integration tested: Toast, Square, Lightspeed, Clover, NCR Aloha or Oracle Micros webhook fires on order-close events; transaction-count denominator available for prompts-per-100-transactions calculation.
• Loyalty platform integration tested: brand-app push-notification fires 2-4 hours post-visit with the per-store review URL, segmented by visit type (dine-in, takeaway, drive-through, delivery).
• Format-matched stock prepared: counter stand for QSR, tabletop card for fast-casual and full-service, pickup-counter sticker for to-go, bag-insert printed with QR-first design for delivery and drive-thru.
• Bag-insert and receipt-printed URL configured for drive-through and delivery channels where physical card placement is impossible.
• Third-party delivery (DoorDash, Uber Eats, Grubhub) packaging insert designed: physical card or printed insert in the bag with QR-first design for the at-home unpacking moment.
• Peak-shift fallback specified: 'point at the stand' mode for Saturday lunch and Friday dinner when the full handoff motion is impossible; documented in the staff training so the prompt does not collapse during peak.
• Server-tip-pooling and FLSA compliance for prompt time confirmed: the 5-minute training huddle is on the clock; the in-service prompt sits inside the natural service flow (tip-producing under 80/20/30 rule).
• Franchisee subsidy commitment documented (if applicable): 50-100% of first batch, tapering on refresh; opt-out path defined for franchisees who decline.
• Response capacity sized: someone responds within 24 hours to every review including negative ones; response template approved for negative-review acknowledgement without escalation.
• Pilot exit criteria written before launch: 2-3x review velocity baseline, 50%+ staff prompt rate at peak, 70%+ at off-peak, no franchisee complaints about pace, no compliance issues. Two-store pilot (one corporate, one franchisee) for four to six weeks.

Common restaurant franchise programme mistakes — eight failure patterns and their fixes

The patterns below are the ones that surface across multi-store rollouts that under-perform. Each is invisible at the franchise-marketing-deck level and obvious only after the first month of live operation. Memorising them shortens the rollout review meeting because most diagnoses end up pointing at one of the eight.

• One placement plan across QSR, fast-casual and full-service: the most common franchise mistake at multi-format brand groups. Fix: format-specific sub-playbooks that adapt placement (counter for QSR, tabletop for fast-casual, bill-folio for full-service) within the same group template.
• Peak-shift staff prompting as the assumption: lunch rush and dinner rush staff cannot add a verbal handoff without damaging throughput. Programmes designed around peak-hour prompts collapse in the first week. Fix: peak-shift fallback to self-serve 'point at the stand', accept lower per-tap conversion in exchange for sustained prompting at off-peak.
• Drive-through omitted from programme design: drive-through customers cannot tap a counter card. Fix: bag-insert with QR-first design, receipt-printed short URL, brand-app push-notification 2-4 hours post-visit.
• Delivery-channel customers ignored: DoorDash, Uber Eats and Grubhub customers never see a storefront card and represent 20-40% of total transaction volume in many brands. Fix: packaging insert with QR-first design, brand-controlled redirect URL routing per-store.
• Franchisee mandate without subsidy: franchisees deliver malicious compliance, the data underperforms opt-out franchisees. Fix: voluntary participation with first-batch subsidy, peer-data persuasion, opt-in ramp over 6-12 months at the franchisee advisory council.
• Profile ownership ambiguity: corporate and franchisee both claim response authority, contradictory responses appear publicly, brand voice fragments. Fix: explicit response-authority policy at programme launch, documented per-store, with escalation path for legally sensitive reviews.
• Tabletop card competing with menu, condiments and tip jar: customers register the table as visually busy and skip the prompt entirely. Fix: minimal acrylic stand on a clean surface, replaced after every clean-down, never accumulating with promotional inserts.
• Worn cards left in place beyond 60 days: grease, drink spills and constant handling degrade card surface; conversion drops 30-50% as the card looks neglected. Fix: 60-day reception/counter cadence, 90-day tabletop cadence, central quarterly replenishment.

Pilot, measurement and refresh rhythm

A two-store pilot spanning owned and franchise governance is the right shape. Network-wide rollouts without a governance-spanning pilot always produce the wrong adoption curve in the franchise segment, because the two operating models respond to different levers. Four weeks of measurement is enough for a restaurant pilot because transaction volume is high; longer pilots risk franchisee patience running out before the rollout decision is made.

• Pilot selection: one corporate store and one franchisee store, in different markets and at different formats if the brand spans formats. Measure separately. Run for four weeks. Choose stores with average (not flagship) traffic so the pilot data scales to the network, not just to the best stores.
• Metrics: reviews per 100 transactions, by placement (counter / tabletop / pickup / drive-thru / bag-insert) via URL source tagging, by daypart (peak vs off-peak), by ownership (corporate vs franchisee), by service model (dine-in, takeout, delivery, drive-through).
• Exit criteria: review velocity at least 2.5× baseline in both pilot stores, staff adoption above 70% of off-peak eligible moments, franchisee willingness to participate evidenced by positive pilot feedback, no damage to service throughput metrics during peak.
• Replacement cadence: counter cards wear in 45–60 days at a busy QSR; tabletop cards last 60–90 days at fast-casual and full-service; pickup-counter cards wear in 60 days because of heavy bag-handling traffic; drive-through bag inserts are single-use and consumed in real time. Plan quarterly replenishment centrally.
• Seasonal variation: back-to-school (August), summer peak (June–August), Thanksgiving and Christmas (November–December), and Super Bowl weekend all shift volume materially. Plan the replenishment calendar to cover peak periods with fresh stock, and pre-print the promotional-menu-adjacent cards ahead of LTO launches.
• Franchisee pilot report: at week three of the pilot, prepare a one-page report for franchisee-facing presentation. Include local-map-pack movement, review velocity lift, and staff feedback. The one-page report is what sells the programme to the broader franchisee base more than the operations team's internal memo.
• Audit: quarterly store-level audit of review velocity, card wear, script adherence and response quality. Laggard stores get coaching and training before replacement print. A store whose velocity lags by more than 30% has a handoff-mechanics problem (or a franchisee-buy-in problem) rather than a card problem.
• Delivery-channel measurement: separately track reviews generated via packaging-insert prompts for delivery orders. These convert at lower rates than in-store prompts but add 10–20% incremental volume at brands with heavy delivery mix, which is material over a quarter.

FAQ