{
  "url": "https://proudtek.com/guides/google-review-card-staff-prompt-playbook/",
  "sourceUrl": "https://proudtek.com/guides/google-review-card-staff-prompt-playbook/",
  "title": "Google Review Card Staff Prompt Playbook",
  "description": "A staff-prompt playbook for Google review cards that makes the ask feel like part of service. Covering timing, wording, handoff motion, training...",
  "kind": "article",
  "imageUrl": "https://proudtek.com/landing-images/google-review-card-staff-prompt-playbook-hero.jpg",
  "imageAlt": "Five stars and a trophy representing five-star Google reviews — staff-prompt playbook for review cards",
  "imageGallery": [
    {
      "url": "https://proudtek.com/landing-images/google-review-card-staff-prompt-playbook-hero.jpg",
      "alt": "Five stars and a trophy representing five-star Google reviews — staff-prompt playbook for review cards"
    }
  ],
  "breadcrumbs": [
    {
      "name": "Home",
      "url": "https://proudtek.com/"
    },
    {
      "name": "Guides",
      "url": "https://proudtek.com/guides/"
    },
    {
      "name": "Google Review Card Staff Prompt Playbook",
      "url": "https://proudtek.com/guides/google-review-card-staff-prompt-playbook/"
    }
  ],
  "summary": [
    "A staff-prompt playbook for Google review cards that makes the ask feel like part of service."
  ],
  "faq": [
    {
      "question": "Should every review-card rollout rely on a staff prompt?",
      "answer": "No. Some environments benefit from a light self-serve prompt (pickup counters, unattended in-room surfaces, delivery inserts, kiosk-order formats, drive-through windows) while others convert far better when staff introduces the card during an existing service handoff. The right answer depends on the team's capacity to sustain a prompt for months, not weeks, and on the transaction window (if service completes in under 90 seconds, hand-delivery usually fails). Match the prompt style to the team reality rather than forcing a universal standard across different formats."
    },
    {
      "question": "What should a staff-prompt pilot measure first?",
      "answer": "Whether staff actually uses the prompt at all. Measure prompts-per-100-transactions before measuring review velocity, because review velocity is meaningless if the prompt does not happen. A programme showing zero lift might be failing at the customer end or failing at the staff end, and those need completely different fixes. If staff is prompting at least 50% of eligible transactions, then review velocity becomes the signal; below 50%, the diagnosis is a staff-adoption issue that script polish will not fix."
    },
    {
      "question": "What is the right moment to deliver the prompt?",
      "answer": "Inside the natural pause at the end of service. After the bill is settled, after the payment terminal confirms, after the room folio is closed, after the prescription is handed across. Never during payment (the customer is distracted and the ask feels like upsell), never before service completes (the review has not been earned and the ask is premature), and never when a queue is visibly waiting (staff feels rushed and delivers a poor prompt). The moment is usually obvious to a seasoned floor manager. Trust that local knowledge in the pilot design."
    },
    {
      "question": "How long should a script be?",
      "answer": "One sentence, ideally under 15 words. 'If you had a good time, a quick Google review helps us a lot.' Longer scripts get shortened by staff under service pressure, so the operator loses control of what is actually said. The posted script might be 32 words but the actual said script drifts to 11 within two weeks. A short script that everyone delivers consistently beats a polished script that drifts, and the operator at least knows what customers are hearing."
    },
    {
      "question": "How do you prevent prompt decay?",
      "answer": "Light training rhythm. Month 1 training, month 2 refresh, monthly review velocity check from month 3 onward. Share the numbers with the team. A visible lift keeps motivation up and converts the programme from 'corporate initiative we tolerate' into 'thing we are good at'. If managers stop prompting themselves on the floor, staff correctly reads the signal ('the boss doesn't think this matters') and the programme dies within weeks. Managerial participation is the single biggest predictor of sustained adoption across pilots."
    },
    {
      "question": "Can a high-turnover team sustain a staff prompt?",
      "answer": "Yes, with adaptations. Shorter script, more reliance on physical placement, monthly training refresh built into shift schedules, peer-to-peer onboarding (new hires learn the prompt from tenured staff rather than from a manual), and written prompt guidance in the new-hire onboarding packet from day one. The programme will run lower per-interaction conversion than a low-turnover team (5-8% instead of 10-15%), but absolute review volume can still be strong because the transaction count per location tends to be higher in high-turnover formats."
    },
    {
      "question": "What is the single biggest avoidable mistake in staff prompting?",
      "answer": "Writing a long corporate script that no one can realistically use during service. Scripts drift or disappear within weeks; the prompt decays; the programme fails and the team blames the cards, the customers or Google. Start with a short, conversational one-line ask that a stressed staff member can deliver authentically at 9:45 pm on a Friday double shift, and iterate from there based on what the team actually says in real handoffs. Not on what the marketing memo thought they would say."
    },
    {
      "question": "Should staff incentives be tied to Google review counts?",
      "answer": "No. Tying staff bonuses or recognition to Google review counts creates two problems. First, it incentivises gating ('only ask if the customer seems happy'), which violates Google's Prohibited Content policy and has triggered Business Profile de-indexing across dealer groups and dental practices. Second, FTC 16 CFR 465 (effective October 2024) treats financial incentives for review collection as a material connection that requires disclosure, with civil penalties up to USD 51,744 per violation. Recognise prompt-delivery counts (prompts-per-100-transactions) instead, which incentivises consistent asking without crossing the gating or incentive lines."
    },
    {
      "question": "How do I handle staff who are uncomfortable asking?",
      "answer": "First, identify why. Most discomfort is one of three things: the script is too long or too corporate-sounding (rewrite it), the timing is wrong (move the ask to the natural pause), or the staff member has a personal accommodation need (anxiety, speech-related disability, ESL discomfort with the script wording). For accommodation cases, offer a written-only variant where the staff member places the card with a small smile but does not deliver the verbal script; for script-fit cases, let the staff member adapt the wording inside the locked structure. Forcing one identical script on every team member produces inauthentic delivery that converts poorly and turns the ask into a job stressor."
    }
  ],
  "procurementFields": [],
  "collectionGuidanceFields": [],
  "coreGuidanceFields": [],
  "articleGuidanceFields": [
    {
      "label": "Best for",
      "value": "Google Review Card Staff Prompt Playbook supports RFID and NFC evaluation, comparison, and sourcing decisions."
    },
    {
      "label": "Compare first",
      "value": "Compare Google Review Card Staff Prompt Playbook against reader compatibility, chip family, material, and deployment environment."
    },
    {
      "label": "What to confirm",
      "value": "Confirm target application, compatibility requirements, customization needs, quantity, and sample expectations before quoting Google Review Card Staff Prompt Playbook."
    }
  ],
  "sourceLinks": [],
  "related": [],
  "productSpecs": [],
  "machineJsonUrl": "https://proudtek.com/machine/guides/google-review-card-staff-prompt-playbook.json",
  "machineTextUrl": "https://proudtek.com/machine/guides/google-review-card-staff-prompt-playbook.txt",
  "author": {
    "name": "Nancy Wu",
    "title": "NFC Product Specialist",
    "expertise": [
      "NFC business cards",
      "Google Review NFC cards",
      "NFC tag programming",
      "Digital product authentication"
    ]
  },
  "publisher": "Proud Tek Co., Limited",
  "datePublished": "2026-04-19",
  "dateModified": "2026-06-06T14:11:38Z",
  "reviewedBy": "Proud Tek Editorial Team",
  "lastReviewedDate": "2026-06-06T14:11:38Z",
  "credentials": [
    "ISO 9001:2015",
    "ISO 14001:2015",
    "RoHS Compliant",
    "CE Marking",
    "REACH Compliant"
  ],
  "generatedAt": "2026-03-16T01:42:30.697Z"
}