How to Respond to a Google Review About a Loyalty Program

A customer earned points on every visit for two years, opened the app on their birthday expecting the free reward the program had promised them, and discovered that the points had quietly expired three weeks earlier. They walk into the store anyway, the cashier confirms the points are gone, and by the evening they have written a one-star review titled "fake points program." Every future searcher reading the listing for the next twelve months is going to see that review before they ever click on a single positive one.

Loyalty program complaints land differently from most negative reviews. They are not about a single transaction that went wrong. They are about earned currency, accumulated over many visits, that the customer thought they had and the business no longer recognizes. The reply has to do two things at once, acknowledge that loyalty points are the business's promise from the moment the customer started earning them, and signal to every future reader that the team will not weaponize an expiration policy or a terms-and-conditions section to protect a balance the customer worked for.

Quick Answer: Acknowledge the customer by name, name the specific points balance or reward they tried to use, and take ownership of the gap between what the program promised and what happened at the counter. Avoid blaming the app, blaming the customer for missing the expiration email, or hiding behind the program rules. Offer a real make-good such as crediting the missing points, honoring the reward this visit, or upgrading the tier back to where it was, and resolve it through a named contact. For the broader framework, see our complete guide to responding to Google reviews.

In this guide, you will learn:

• Why loyalty program reviews behave differently from coupon, gift card, or pricing complaints on your listing
• The first move before drafting the reply, including the account reconciliation step that changes everything
• A four-part formula that works for any loyalty program complaint
• Templates for eight common loyalty scenarios across retail, restaurants, hotels, salons, and gyms
• What never to say when a customer feels their earned points have vanished
• How to fix the expiration, app, and migration gaps that quietly generate these reviews

Why Loyalty Reviews Behave Differently From Coupon or Gift Card Complaints

Most negative reviews about money describe a price the customer thinks was too high, a discount that did not apply, or a prepaid balance that did not honor. A loyalty program complaint is a different category. The customer is not arguing about the price, the discount, or a prepaid balance. They are arguing that the points they earned, often slowly, over many visits, are not what the program promised. That distinction shapes how the reply should land.

Three things shift in particular.

The first shift is in what the customer is actually upset about. The frustration is rarely about the dollar value of the reward in isolation. The frustration is about feeling that the time and visits they put in, the receipts they scanned, the app they downloaded, the email signup they completed, did not add up to what they were told they would get. A reply that focuses on the dollars, "we apologize for the inconvenience with the missing reward," misses the relational layer of the complaint. The cleaner reply addresses the earning gap first, the specific reward second, and the long-term loyalty third when the review names it.

The second shift is in what future readers are evaluating. A future shopper reading a loyalty review is not deciding whether your prices are reasonable. They are deciding whether joining your loyalty program is worth their time, their email address, their phone number, and their attention. They want to know whether the points they will earn in the next twelve months will actually convert to the rewards the marketing promised, or whether they will end up in the same spot as the reviewer. Loyalty enrollment is a leading indicator of repeat-visit revenue, and a string of unanswered "the points disappeared" reviews quietly suppresses every future signup.

The third shift is in pattern recognition. A single loyalty review reads as one customer who missed an expiration email or hit an edge case. Three or four loyalty reviews across different customers over a quarter reads as a program whose mechanics are not aligned with how customers actually use it. Future readers scan for repeated complaints, and an unanswered string of "the app says zero points," "the reward was not available," or "my tier dropped" reviews signals that the program has structural problems the business has not addressed.

The job of the reply is not to defend the expiration policy or the points-to-reward conversion. It is to land as a business that understands the loyalty program was a two-way promise, takes the gap seriously, and is doing something concrete so the next member is not stranded at the counter.

The First Move: Reconcile the Account Before Drafting a Word

Before writing the reply, pull up the customer's actual loyalty account, look at the earn history, redemption history, expiration events, tier changes, and any system events on their record. The default reflex is to write a quick general apology because the complaint feels small. The better reply is the one that names the specific account state, references the specific gap, and shows the future reader that the team actually traced the loyalty record.

A few things to check before you start typing.

The customer's actual points balance, earn history, and expiration events. Pull the loyalty platform record, the earn pipeline log, the redemption pipeline log, and any expiration events the program ran. Match the reply to the actual account state, since a customer who genuinely earned and lost points reads differently than a customer whose points never properly synced from the point-of-sale. A specific complaint, "I had five hundred points last month and now I have zero," gets a reply that names what happened to the points and when.

Whether the program ran an expiration sweep the customer never received notice of. Loyalty programs typically expire points after a set inactivity window, and the program is supposed to notify the customer at least thirty days before any expiration occurs. Check whether the warning email actually sent, whether it landed in spam, whether the customer had opted out of marketing emails which the program defaulted into the same channel, and whether the in-app notification fired. A customer who lost points without warning has a stronger claim than the expiration policy alone would suggest, and the reply has to reflect that.

Whether the loyalty app, integration, or sync had a known outage. Check the loyalty platform status page, the point-of-sale integration logs, the mobile app crash reports, and the third-party CRM logs if your program runs through one. Customers whose points never properly recorded from receipts during a known outage are showing up to the counter with a real gap, and a reply that blames the customer for not scanning the receipt correctly reads as the business pointing at the wrong layer. The reconciliation step has to surface the outage before the reply goes out.

Whether the customer's tier changed because of a program rule change. Loyalty tiers are often time-sensitive. A customer who hit gold tier last year and dropped to silver this year may have lost the tier because the qualifying spend reset or because the program changed the tier thresholds. A tier change driven by a quiet program update reads very differently from a tier change driven by the customer's own spending. The reply has to know which one applies before it goes out.

Whether the program migrated to a new system, and what got lost. Migrations are the single largest source of loyalty complaints. Customers lose points history, lose tier status, lose enrollment records, and lose the rewards they had been working toward. Check whether the customer's account predates the migration, what the legacy export shows, and whether the migration imported their record correctly. If the migration is the actual root cause, the reply has to own the migration, not the customer.

The owner reflex of "the expiration policy is in the loyalty terms" is true and irrelevant in the public reply. Every future reader knows loyalty programs have terms. What they want to see is the team registering this specific gap and doing something concrete to keep the next member from arriving at the counter and finding that the points they earned do not exist anymore.

The Four-Part Formula for a Loyalty Program Review Response

Every reply to a loyalty review should hit the same four beats. The whole response fits in three to four sentences.

Step 1: Acknowledge the customer by name and the earning gap

Open with the first name from the review and a direct acknowledgment that the gap between what the program promised them and what happened at the counter is on the business, not on them. The complaint is not really about the dollar value of the missing reward, it is about feeling that the loyalty they invested did not add up, and the reply has to register that first.

Say this: "Hi Priya, you came in on your birthday expecting the free entree the program promises gold members, and the team told you the points had expired three weeks earlier, and the gap between what you earned across two years of visits and what showed up on the screen is on us."

Not this: "Dear Valued Customer, we apologize for any confusion regarding our loyalty rewards program."

Step 2: Name the specific account state and what went wrong

Be precise about the loyalty account without ever publishing a member number, a phone number, or any other identifier. A reply that stays vague reads as a business that did not look at the actual situation, and future readers cannot tell whether the issue was an expiration without notice, a sync failure, a tier downgrade, or a migration loss. One short line that names the program area and the gap gives every future reader the actual context.

Say this: "The points should have come with at least one expiration warning, and the warning email never sent because of a known issue with our notification pipeline that week."

Not this: "We apologize that the rewards were not available at the time of your visit."

Step 3: Take honest ownership without weaponizing the program rules

Once the gap is named, address why the points or reward did not honor, in one short, candid line. The customer does not need a paragraph about the points-to-reward ratio, the expiration policy, the tier thresholds, or the loyalty terms, and future readers do not want one. They want a signal that the team is not going to defend the failure by pointing at section three of the loyalty terms. Avoid framing the gap as the customer's fault for missing an email, not opening the app, or not reading the rules.

Say this: "Birthday rewards are the whole point of the program for many members, and arriving on the day expecting a reward that quietly expired three weeks earlier is the wrong answer to a customer who scanned the receipt every visit for two years."

Not this: "Per our loyalty program terms, points expire after twelve months of inactivity and members are responsible for tracking their balance in the app."

Step 4: Offer a concrete make-good and a named contact

A reply that ends with "we hope you will give us another chance" is a soft close that future readers correctly read as not really addressing the earning gap. The reply has to give the customer, and every future reader, a real recovery for this account and a real signal about what changes for the next member. The recovery can be reinstating the expired points, honoring the reward this visit anyway, restoring the prior tier, or sending the equivalent reward by email today. Hand off through a named person or inbox, not a generic "contact our team" line.

Say this: "Please reach me at [phone] or [email] and we will reinstate the points, honor the birthday reward this week, and fix the notification pipeline so the next member does not lose a balance without a warning."

Not this: "Please contact our customer service team for assistance."

Response Templates for Common Loyalty Program Scenarios

These templates follow the formula. Fill in the name, the relevant context, the contact details, and the make-good that fits your business. Avoid copy-pasting the same wording across multiple loyalty reviews. Future readers and the AI-generated business summary both scan for repetition, and a row of identical "we apologize for the rewards issue" replies reads worse than a row of slightly different honest ones.

Template 1: Retail or restaurant - points did not apply at checkout

"Hi [Name], you came in on [day] and the points from your last three visits never showed up in the app, and the gap between the receipts you scanned and the balance on your screen is on us. Our scan-to-points pipeline had a sync delay across the affected dates and your earns landed in the queue instead of on your account. Please reach me at [phone] or [email] and we will credit the missing points and add a small token reward for the trouble, and the pipeline backlog has been cleared for the affected window."

Template 2: Any program - points expired without an expiration warning

"Hi [Name], you arrived on [occasion] expecting the reward your balance had been building toward, and the team told you the points expired before you had a chance to use them, which is on us. Our program is supposed to send a warning email at least thirty days before any expiration, and our notification pipeline misfired for the cohort you were in. Please reach me at [phone] or [email] and we will reinstate the points, honor the original reward this week, and our notification cadence has been audited and re-tested."

Template 3: Mobile app - loyalty app showed wrong balance or crashed

"Hi [Name], you tried to use your reward on [day] and the loyalty app showed a different balance than the team saw at the counter, which is on us. Our most recent app release introduced a sync bug between the in-app balance display and the back-end of record, and you ended up in the gap between the two. Please reach me at [phone] or [email] and we will reconcile the account to the higher of the two balances and honor the intended reward today, and the affected app release has been patched."

Template 4: Tier-based program - customer dropped a tier unexpectedly

"Hi [Name], you came in expecting the gold-tier benefit on [day] and our system had moved you to silver because your annual qualifying spend reset at the start of the program year, and the program change was not communicated to existing gold-tier members clearly enough. Please reach me at [phone] or [email] and we will restore your gold tier for the remainder of this program year and honor the gold-tier benefits today, and we are revisiting how we communicate annual tier resets to members."

Template 5: Birthday or anniversary reward - reward never arrived

"Hi [Name], you came in for your [birthday or anniversary] expecting the loyalty perk the program promises, and the team did not see the reward attached to your account, which is on us. Birthday and anniversary rewards are supposed to load on the first of the month and the load did not run on time for the affected cohort. Please reach me at [phone] or [email] and we will honor the perk today, send a digital version of the reward by email, and the monthly load has been re-run for all affected members."

Template 6: Salon, spa, or studio - reward could not be redeemed for the service

"Hi [Name], you came in for [service] on [day] expecting to redeem the reward your balance had been building toward, and the front desk told you the reward was not valid for that service, which is on us. The reward should have applied to any service we offer, and the limit our front desk applied was a stale rule from a prior promotion that was never retired. Please reach me at [phone] or [email] and we will refund the service to the original card or credit a free upgrade on your next visit, and the front-desk runbook has been updated this week."

Template 7: Hotel - elite-status benefit not honored at check-in

"Hi [Name], you checked in on [day] expecting the elite-status benefits you have earned across the year, and the front desk could not get the system to recognize the status against your booking, which is on us. The booking flow on our end has a gap between the central loyalty record and the property-level rate engine, and your reservation fell into the seam. Please reach me at [phone] or [email] and we will refund the equivalent of the missed benefits, credit additional points for the night, and we are working with our central system to flag the rate-engine gap so the next guest is not in the same spot."

Template 8: Program migration - history or tier lost in a system change

"Hi [Name], you opened the app on [day] expecting the points and gold tier you had built across the last few years, and the migration to our new program imported your record at zero points and base tier, which is on us. The legacy export did not map the historical earns to the new system on the schedule we communicated, and your account was caught in the affected batch. Please reach me at [phone] or [email] and we will rebuild your prior balance from the legacy export, reinstate the gold tier for the remainder of the program year, and we are reaching out to the rest of the affected members proactively."

Drafting careful loyalty replies adds up across a busy month. Try our free AI response generator for a clean, on-brand starting draft in seconds, no signup needed.

What Never to Say in a Loyalty Program Review Response

Each line below shows up in tone-deaf loyalty replies. Each one reads worse to future readers than no reply at all, and several follow the listing for months because they get pulled into the AI-generated business summary or the snippet shown on Google search.

Do not quote the program terms in the reply

"Per our loyalty terms, points expire after twelve months of inactivity and members are responsible for monitoring their balance" is a sentence that reads as the business defending its own rules instead of the customer experience. Future readers correctly read it as the team prioritizing fine print over the relationship. The cleaner version skips the terms entirely and addresses the earning gap directly. The terms can live in the private follow-up if they are even relevant.

Do not blame the loyalty app or platform by name

"Our loyalty platform experienced a sync issue at the time of your visit" is a sentence that reads as the business pointing fingers at a vendor the customer never directly interacted with. Future customers do not care which platform sits between them and a balance. They care that the points they earned across many visits did not honor when they tried to use them. The cleaner version owns the gap, fixes the account, and files the platform ticket offline.

Do not say "you should have read the expiration email"

"You should have received an email thirty days before the points expired" is a sentence that puts the burden on the customer for an email the business cannot prove they actually opened, that may have landed in spam, that may have been buried in marketing emails, or that may not have sent at all because of a pipeline issue. Future readers correctly read it as the business shifting responsibility for a notification system the customer does not control. The cleaner version assumes the notification did not actually land and treats the expiration as a system check that needs to happen before the team takes a position.

Do not promise to reinstate every expired balance going forward

"We will reinstate any expired loyalty balance for any member on request" is a sentence that ages badly the moment the program runs an expected expiration sweep, because expirations are a planned program mechanic and a public promise to reverse them on request trains members to ignore the warnings entirely. Future readers reading the over-promise alongside the next firm expiration will read the over-promise as the more damaging part. The cleaner version is a specific, narrower commitment, such as "we are reinstating the points for the cohort affected by the missed warning," which is honest, narrow, and durable.

Do not respond with "you should have used the app to track your points"

A reply that explains that the customer should have monitored their balance more actively is a public lecture. Future readers correctly read the lecture as the business prioritizing being right over being usable. The cleaner version acknowledges the gap as a signal that the balance visibility was not clear enough, not as a sign that the member was careless. The app's job is to surface the balance to the customer, not to be a defense the business hides behind.

Do not push a future-purchase credit as the only make-good

A reply that is just "please come back and we will apply a credit on your next visit" reads as the business pushing the cost of the original gap back onto the customer in the form of a return visit. Future readers see the make-good as conditional on more spending, which both trains future reviewers to expect a credit-only recovery and signals that the business does not actually have a fix for the underlying loyalty problem. A direct reinstatement of the points, honoring the original reward, or sending a digital version of the reward today lands as honest recovery without requiring anyone to come back.

Do not use generic apology language

"We apologize for any inconvenience caused by the loyalty program issue" is the sentence that defines a business that responds to every negative review with the same script. Loyalty reviews specifically deserve specific language because the complaint is specific, the member arrived with earned currency that did not honor. The apology has to name what points and what gap, not gesture at "any inconvenience."

For the broader pattern on what to avoid, see our guide on what not to say in review responses.

Fixing the Expiration, App, and Migration Gaps Quietly Generating These Reviews

The most reliable way to cut loyalty reviews is not better replies, it is fewer surprises at the counter. A significant share of "the points disappeared" reviews trace back to four operational gaps that the business can close without a platform change. The job is not to eliminate every edge case, it is to remove the most common ones.

Expiration warnings that actually land. A loyalty program should never run an expiration sweep without firing a warning email at least thirty days out, a second warning at seven days out, and an in-app notification in the same window. Verify that the warning emails are sending from the correct sender, are not getting flagged by major email providers, and are being delivered to members who opted out of marketing because the loyalty channel should not share an opt-out with promotional email. A single missed warning generates more reviews than a year of well-communicated expirations.

Earn-to-account sync that runs in real time. A customer who scans a receipt and watches the points land in the app immediately experiences the program as working. A customer who scans a receipt, sees no points, scans again, and walks out frustrated has the seed of a one-star review. Verify that the earn pipeline runs synchronously with the transaction, that the back-end of record updates within seconds, and that the app display reflects the back-end of record without a separate cache. Most "the points did not show up" reviews are sync-latency reviews.

Tier change communication. Tier downgrades are particularly volatile because they feel like a punishment for a year the customer thought they had earned. When the program year resets, when the qualifying spend thresholds change, or when the tier benefits change, the business has to communicate the change explicitly, in writing, to the affected members, with enough lead time that they can act on it. A tier change that arrives at the counter as a surprise generates reviews. A tier change that arrives as a clear email two months ahead generates resignation, not anger.

Migration playbooks that protect history and tier. A loyalty program migration is the highest-risk event in the program lifecycle. Verify that the legacy export captures every earn, every redemption, every tier change, and every expiration event. Verify that the import to the new platform maps every field correctly. Run a sample reconciliation across a hundred randomly selected accounts before the migration goes live, and a second reconciliation after. Reach out proactively to any member whose record does not reconcile, before the member finds the gap themselves.

When the Loyalty Complaint Becomes a Pattern Worth Naming

A single loyalty review reads as one edge case. Three or four loyalty reviews on different accounts over a quarter reads as a pattern the business has not addressed. At a certain point, the right move is to address the pattern in the listing itself, not just in individual replies.

A few signals that the pattern is worth naming.

The same expiration window shows up in multiple reviews. Two or more complaints involving balances that expired in the same month is a clear sign that the expiration sweep ran without the warning emails firing. The cleaner move is to identify every member in the affected cohort, reach out proactively to reinstate the balances, and post an acknowledgment on the Google Business Profile that the warning system has been audited and fixed. A small public note pre-empts the next reviewer.

App-related complaints are a recurring theme. When reviews repeatedly mention the app showing the wrong balance, the app crashing on the rewards screen, or the app not recognizing the member at the counter, the program is operating without real-time visibility for the customer. The fix is a coordinated audit of the app release pipeline, the back-end sync, and the in-store integration, plus a counter-team workaround that does not depend on the app at all. Most app-related loyalty reviews would never have been written if the team could pull up the balance on a back-of-house terminal in front of the customer.

Migration-related complaints are clustering. When the reviews repeatedly mention a system change, a new app, a balance reset, or a tier change tied to a program update, the migration is generating the reviews. The fix is to publish a clear migration FAQ, reach out to every affected member by email, and post a Google Business Profile update acknowledging the migration and pointing to the recovery process. A migration that generates reviews quietly generates many more enrollment cancellations that never show up in the listing at all.

For the broader framework on review patterns and what they signal, see our guide on Google review analytics and our walkthrough on why respond to Google reviews. For the closely related case of a paid membership that did not honor as promised, see our guide on responding to a review about a membership.

Protecting the Team Through the Process

A loyalty review can land hard on the counter team, especially when the decline at the counter was made in good faith based on what the app or the back-end showed. The cashier who told the customer the points had expired, the host who said the reward was not valid for the service, the front-desk staffer who could not get the tier to recognize against the booking, often reads the review on a personal phone before the owner has even seen it. The reflex of "who declined the reward" lands as a blame message faster than the team has time to talk through what they actually saw on the screen.

A few small habits make the conversation healthier.

Tell the team about the review yourself, before they see it. Walking into a shift knowing a loyalty review is on the listing is far better than discovering it through a customer screenshot at the counter or a tagged post in the team chat.

Frame the conversation as a system review, not a personal one. "Let me walk through what the app showed when the customer opened it at the counter" lands very differently from "who told the customer the points expired?" The former invites the team to surface the actual sync, expiration, or migration gap. The latter shuts down the conversation and trains the team to hide the next gap.

Give the counter a small honoring threshold for balance discrepancies. A team that can honor a borderline balance on the spot up to a small dollar amount, without a manager call, will generate dramatically fewer loyalty reviews than a team that has to escalate every edge case. A free coffee on a customer who is one short on points is cheaper than a year of a one-star review on the listing.

Track the system adjustments that came out of the review. A simple log of "review on [date] led to expiration warning fix on [date]" gives the team visible feedback that the review pattern is shaping the operational decisions. Reviews that change nothing land as noise. Reviews that change the next expiration sweep land as evidence.

Teams that have been walked through a loyalty review and felt heard, instead of blamed for a decline they made in good faith, are the ones who quietly look up a balance in front of the customer the next time, rather than turning the reward away and pointing at the program rules.

Frequently Asked Questions

How do you respond to a Google review about a loyalty program?

Acknowledge the customer by name, name the specific points balance, reward, or tier they tried to use, and take ownership of the gap between what the program promised and what happened at the counter. Offer a real make-good such as crediting the missing points, honoring the reward this visit, or upgrading the tier back to where it was, and resolve it through a named contact. Avoid blaming the app, blaming the customer for misreading the terms, or hiding behind the program rules.

What if the customer's points expired or the program rules genuinely don't allow the reward they wanted?

Honor it anyway when the gap is small, and explain the limit calmly in the reply when it is not. Loyalty points feel different from a coupon because the customer earned them across many visits, and a public refusal reads as the business treating points as fake money it controls. When the rules genuinely prevent the redemption, acknowledge the confusion, name what is possible instead, and offer something equivalent in private. Avoid quoting the terms in the public reply.

Should you name the specific points balance or reward value in the public reply?

Name the points only enough to confirm you read the situation, not the dollar value of what you are giving back. Saying "we credited the missing five hundred points to your account" is different from "we credited fifty dollars in store credit." The first reads as honoring earned currency, the second trains every future reader that a one-star review converts to cash. Take ownership of the gap publicly, name a specific contact, and handle dollar-value make-goods privately.

What if the loyalty program migrated to a new system and the customer lost their history?

Take ownership of the migration in public and rebuild the history in private. A program migration is the single most preventable source of loyalty complaints, and a reply that blames "the system update" reads as the business pushing its technical decision onto the customer. Acknowledge that the migration was on you, name what you can do to restore the prior balance or tier, and invite the customer to a private channel where you can pull the legacy export.

How do you prevent loyalty program complaints from showing up in your Google reviews?

Send an expiration warning email or push notification at least thirty days before any points or reward expires, and again at seven days, so customers never discover an expired balance at the counter. Train the counter team to look up a loyalty balance in front of the customer rather than telling them to check the app later, and to honor a small balance discrepancy on the spot. Audit the loyalty app and sync pipeline monthly, especially after any new software release.

What if the customer's loyalty complaint is really about a wider unhappiness with the program changes?

Address the specific complaint in the reply, and address the program change in a separate, public-facing communication. When a business raises the points required for rewards, ends a popular tier, or migrates to a new program, the loyalty reviews become a referendum on the change, not just on the specific transaction. The reply has to be honest about the change and point to a clear written explanation outside the review, such as a Google Business Profile post or an email to the program list.

The Bottom Line

A loyalty program review is not a complaint about pricing, it is a complaint about earned currency, accumulated across many visits, that the business no longer recognizes. The customer is not really upset about the dollar value in isolation, they are upset that the loyalty they invested did not add up to what the program promised them. The reply has to register the earning gap first, name the specific account state and what went wrong second, take honest ownership without weaponizing the program rules third, and offer a real make-good through a named contact fourth.

Key Takeaways:

• Open with the customer's name and a direct acknowledgment that the gap between what the program promised and what happened at the counter is on the business.
• Name the specific points balance, reward, or tier, and what went wrong. Vague apologies read as scripts.
• Take ownership without quoting the program terms in the reply. Future readers correctly read terms-citing as defending policy over experience.
• Offer a real make-good, such as reinstating expired points, honoring the reward this visit, restoring the prior tier, or sending the equivalent reward today. Avoid future-credit-only recoveries.
• Do not blame the loyalty app or platform vendor in public. Take ownership first and file the vendor ticket privately.
• Send expiration warnings at thirty days and seven days, audit the earn-to-account sync, and reconcile every migration before the member discovers a gap.
• Give the counter team real-time balance lookups and a small honoring threshold so borderline balances never become reviews in the first place.
• A pattern of loyalty reviews is an expiration, sync, or migration problem, not just a reply problem. Address the cohort proactively, not one review at a time.
• Walk the team through the reply before it goes live and frame the internal conversation as a system review, not a personal one.

For the broader framework, see our complete guide to responding to Google reviews. For related cluster guides, see responding to a review about a coupon or promo code, responding to a review about a gift card, and responding to a review about a membership.

---