Asking for a review without sounding needy

Reviews are the single most under-prioritized thing a service business owns. Owners spend hours editing their website copy and hundreds on ads, while letting a steady stream of happy customers pass through without ever asking for a review.

The reason isn't laziness. It's that asking for a review feels needy. So most owners ask once, awkwardly, and then drop it.

This is the playbook. Four steps, the legal rule almost no one knows, and the scripts.

The legal rule first, because it matters

The FTC explicitly prohibits review gating, the practice of filtering customers based on how satisfied they are before deciding who to ask for a public review. If you send a satisfaction survey and only ask the happy customers for a Google review, that's a violation. If your software does this automatically, you're still on the hook.

This rule trips up a lot of service businesses because review-request tools have historically built this exact funnel and called it "smart." It's not smart. It's a violation that can carry FTC enforcement, and on a more practical level, it skews your public reviews to a degree that customers and platforms increasingly notice.

The clean way: ask every customer. Let them rate where they actually want to rate. If they're unhappy, they'll tell you in private. If they're happy, they'll post publicly. You don't need to engineer the filter.

This is also why Yesoma's review request templates don't do gating. Same script goes to every customer who passes the eligibility check; no satisfaction screen in between. It's the only ethical and the only legal way to do this.

Step 1: Get the timing right

The two-week window after a great experience is the conversion zone for reviews. After two weeks, response rate drops by half.

The best moment to ask is right after the customer expressed satisfaction. They just told you "thank you, this was perfect." That is the moment. Not next week, not next month. Inside an hour if you can.

Specific timing recommendations:

• For event-based services (weddings, parties, photography sessions): send the review request 24 to 72 hours after the event, when the high is still warm.
• For appointment-based services (beauty, fitness, coaching): send within 24 hours of the appointment, ideally when they're checking their phone post-session.
• For project-based services (consulting, contractor work, design): send within a week of project sign-off, after the deliverable has had time to feel real but before they've moved on mentally.
• For ongoing relationships (subscriptions, retainers): pick a milestone (3-month mark, anniversary, a recent win) and tie the request to it. Don't ask randomly.

The customer needs the moment of the request to have a clear "why now" attached, or it reads as transactional.

Step 2: Ask the right way

Three principles.

Make it about them, not you. "Would you mind leaving a review?" is about your need. "I'd love to know what worked for you, and a quick review helps other people decide" reframes the ask around them helping the next customer.

Make it as low-friction as possible. A direct link to your Google review page, opened with one tap, beats "you can find us on Google" by an order of magnitude. If the customer has to search for you, you've lost most of them.

Make it personal. A templated review request that doesn't mention the customer by name or the specific service they got reads as a campaign. A request that says "Sarah, thanks for trusting me with the bridal shoot, here's the link to leave a quick review" reads as a personal favor.

Step 3: The scripts

Three scripts that work, each for a slightly different context.

Script A: The post-event request

Hey [name], thank you for letting me be part of [the event]. It was such a joy. If you have a minute in the next few days, a quick Google review would mean a lot, both for me and for other [type of customer] trying to figure out who to trust. Here's the direct link: [URL]. No pressure if you're slammed.

Why it works: the gratitude is specific, the favor is small ("a minute"), and the framing ("for other customers trying to figure out who to trust") puts the request in service of someone else, not the business.

Script B: The appointment follow-up

Hi [name], hope you're loving [the result] from yesterday. If you're up for it, would you leave a quick review? It really does help my business. [URL]

Why it works: short, casual, low-ask. Suits a customer relationship where you already have rapport. Don't use this for a first-time customer; it reads as too familiar.

Script C: The "you said something nice" request

Hey [name], you mentioned [the specific thing they said in the conversation] and it absolutely made my week. If you ever felt like sharing that on Google, here's the link: [URL]. No worries if not, either way thank you for being a great client.

Why it works: this is the highest-converting version. You're essentially handing the customer the words they already used. They feel like the review is half-written for them, because their own praise is the prompt.

Step 4: The follow-up rule (do it once, never twice)

If a customer doesn't respond to the first request inside two weeks, you have one more shot, then you let it go.

Hey [name], realized I sent the review link a couple weeks back and didn't want to chase you on it. If you ever feel like leaving one, the link is still here: [URL]. If not, no worries, just appreciated working with you.

That's the entire follow-up cycle. Two messages, two weeks apart, then stop. If you ask a third time, you cross from request to harassment, and customers remember it.

What never to do

• Don't offer discounts or freebies in exchange for reviews. This is also against most review platforms' terms (and arguably an FTC issue if not disclosed). It corrupts the review signal and customers can smell it.
• Don't draft the review for them. "Could you say something about [these three things]?" reads as coaching, and reviews that look coached get filtered by platforms.
• Don't ask unhappy customers to leave a review by accident. This is where it gets nuanced: you can't filter, but if a customer just complained, sending an automated review request inside 24 hours is bad timing. Resolve the complaint first, then they're eligible for the next cycle.
• Don't ask the same customer twice in a year. Repeat customers can leave one good review; you don't need three from the same person, and platforms detect the pattern.

How to think about volume

A useful target for service businesses: aim for a review-request response rate of 15 to 25 percent. So if you send 100 requests in a quarter, you should see 15 to 25 new reviews land. If your number is lower, the most common reasons are:

• Timing is too late (send sooner).
• Link is hard to use (test it on your own phone).
• Script is too formal (rewrite in your own voice).
• You're asking customers who weren't actually delighted (be selective without filtering: only ask customers who completed without a complaint).

A service business with 50 Google reviews ranking on the first page beats a competitor with 8 reviews almost every time. The compounding effect of reviews on local search visibility is large enough that the time spent on the request workflow returns more than almost any other marketing investment.

The mindset shift

The owners who ask for reviews well don't feel they're asking for a favor. They feel they're inviting customers to participate in something the customer also gets value from (helping the next person decide).

If you can hold that frame in your head, the request stops feeling needy. You are not asking a customer to do you a favor. You are giving them a 30-second way to help someone they'll never meet pick a service they'll be happy with.

That reframe is the whole game.