Respond to every review in your own voice, within the hour

Who you are actually writing for

The person you answer is rarely the person you are writing for. A review response is read by the reviewer once and by prospective customers for years - it is the most public writing your business does, and the only part of your review pages you control. Handled well, even a bad review becomes an asset: the response underneath it shows every future reader how you behave when something goes wrong, which is the exact question they came to the reviews to answer.

The system you are building: your AskEleven Employee watches every platform where you are reviewed, responds to the straightforward reviews promptly in a voice tuned to yours, and routes anything delicate to you as a drafted suggestion rather than a decision already made. The sorting is the design's core. Speed on the easy ones, judgment on the hard ones, and a bright line between the two that you draw once and it never crosses.

Before you start: gather three things

Access to your platforms. Google Business Profile first - it is where most reading happens - then whichever others matter for your business: Yelp, TripAdvisor, OpenTable. Connect them through your AskEleven dashboard, or grant manager access where a platform requires it.
Ten responses you would stand behind. Your own best past responses if they exist, or responses you have admired from businesses you respect. For each, one line on what makes it good. These teach voice faster than any description of voice.
Your lines in the sand, written down. The house rules a response may never break. Typical set: never argue with a guest's account of their own experience, never offer compensation publicly, never confirm someone was a customer if the platform fight gets legal, never name a staff member in a negative context, never use the phrase "we apologize for any inconvenience." Add your own. This document does more work than any other part of the setup.

Step 1: The voice-tuning prompt

One session, and the voice is set:

Prompt - tune the voice

I have shared ten review responses I consider excellent, with notes, and our house rules. Study them, then write responses to the last fifteen reviews we received across our platforms - including the ones already answered, so I can compare yours against what we actually said. Rules: every response mentions something specific from the review itself, so no two responses could be swapped; thank without groveling; vary the openings - never start three responses the same way; two to four sentences for praise, four to six for criticism; sign them [how you sign - a first name, initials, "The house"]. Where a review criticizes us fairly, the response owns it plainly and says what changed. Where a review is unfair, the response stays gracious and correct without being defensive - the reader we care about is the future guest, not the argument.

What to expect: fifteen test responses to mark up. Be picky about the near-misses - "too formal," "we would never say delighted," "this one argues" - because every correction becomes a permanent rule. Two rounds of this and the voice is usually indistinguishable, which you will verify in the quality tests below before anything posts.

Step 2: The standing rules

Now the routing - what posts on its own, and what waits for you:

Prompt - standing rules

From now on, check all our review platforms at least hourly and handle every new review as follows. Four and five stars with no complaint buried inside: respond within the hour, in our voice, specific to what they wrote. Three stars, or any review mixing praise with a genuine complaint: draft a response and hold it for my approval - do not post. One and two stars, anything mentioning illness, refunds, discrimination, legal action, or a named staff member: never respond without me. Send me the review and a suggested draft immediately, flagged urgent, and if I have not acted within 24 hours, remind me - an unanswered bad review ages badly. Never offer compensation in a public reply; where warranted, the draft should invite the conversation offline to [MANAGER EMAIL]. Weekly, send me a digest: every review, every response, our rating trend on each platform, and any theme showing up more than twice.

What to expect: the easy majority handled within the hour, and the delicate ones arriving in your inbox with a considered draft attached - which changes the job from composition under emotion to editing with judgment. The 24-hour reminder exists because the angry review you are avoiding is the one doing compound damage. The weekly digest earns its keep within a month: reviews are the cheapest operational intelligence you have, and a theme that appears three times is not a review problem, it is an operations problem wearing a review costume.

A worked example: the Tuesday three-star

A neighborhood restaurant with a strong 4.7 on Google. Tuesday morning, a three-star lands: "Food was genuinely great - the short rib might be the best in the city. But we sat for 25 minutes before anyone took a drink order, and we had mentioned it was my mother's 70th when we booked. Nobody acknowledged it. Expected more at these prices."

Mixed review, so it routes to the owner with a draft: "Thank you for this - and I am glad the short rib landed, because the kitchen works hard on it. The rest of your evening was not up to our standard. Twenty-five minutes before a drink order is a service failure, plain and simple, and missing your mother's 70th after you had told us about it makes it worse; occasions like that are exactly what we are supposed to be good at. I have gone over the night with our floor team and changed how we flag occasions from OpenTable bookings so a note like yours cannot get lost again. I hope you will give us the chance to show your mother a proper evening. - Marco"

The owner changes one word and approves from his phone; it posts 90 minutes after the review appeared. The reviewer never replies - but that response is read by hundreds of people deciding where to book a birthday dinner, and it answers their real question perfectly: this is what happens here when something goes wrong. The weekly digest, meanwhile, has flagged "slow first service on Tuesdays" as a repeating theme, which turns out to be a real staffing gap on the floor manager's night off.

Quality tests before it posts unsupervised

The two-week approval run. Start with every response held for approval, including the five-stars. When a full week of drafts goes out unedited, release the easy tier to post directly. The delicate tier stays held forever - that is not a training phase, it is the design.
The shuffle test. Take five responses to five different reviews and strip the review text. If you cannot tell which response answers which review, they are template-grade - send them back with "each response must be impossible to reuse."
The voice test. Mix three of its responses with three of your own and show someone who knows how you write. Reliable sorting means another tuning round.
The escalation drill. Have a friend post a review mentioning a refund, or simulate one in chat. Confirm it arrives flagged urgent with a draft and that nothing posts. This rule protects you most on the day you least expect to need it.

The first month, and the long game

Within the first month the visible record changes: every review answered, quickly, specifically, in one voice. Prospective customers notice without knowing they noticed - a page where the owner clearly reads and answers everything simply feels like a better-run business, because it is one.

Two habits keep the system honest long-term. First, keep reading the weekly digest even when the responses no longer need you; the themes are the point, and the digest is where "three mentions of slow Tuesdays" becomes a staffing fix rather than a slow slide to 4.4. Second, when something real goes wrong in the business - a bad night, a departed chef, a renovation - tell your Employee before the reviews arrive, so the responses can be honest instead of blindsided. The voice only stays yours if it knows what you know.