Why Your Review Request Gets Opened But Never Clicked Through

You send the review request. The customer opens it — you can see that in your SMS or email dashboard. And then nothing. No review shows up on Google or Facebook.

It's tempting to read that as "they changed their mind." Sometimes that's true. But if it's happening at scale — a healthy open rate with a consistently low completion rate — the more common explanation is duller and more fixable: something between the click and the platform is losing people who were already willing to leave a review.

Open rate tells you the ask worked. It doesn't tell you what happened next

Your email or SMS provider will happily report that 68% of customers opened your review request. What it can't tell you is:

• Did the link actually load, or did it hang on a slow connection?
• Did the customer land on your page and immediately bounce, or did they read it and hesitate?
• Did they get redirected to Google, hit a login wall, and give up?
• Did they start typing a review and abandon it halfway through?

All of that happens after the metric you're looking at stops being useful. Click-through tells you they clicked. It doesn't tell you why the review never landed.

The three places requests usually die

After digging through customer setups that had good open rates and bad completion rates, the drop-off almost always sits in one of three places:

1. The redirect itself. Some review platforms require the customer to be logged into a Google or Facebook account on that device. If they aren't, they're bounced into a login flow mid-request — exactly the moment you don't want to add friction.

2. Page load time on mobile. Most review requests get opened on a phone, often on a spotty connection right after finishing a job or leaving a location. A landing page that takes three seconds to render loses people who were already moving on to the next thing.

3. An unclear "what do I actually do here" moment. If the page doesn't make it obvious in one glance — "tap here to leave your review on Google" — some customers just close the tab, not because they don't want to help, but because it wasn't obvious what to do next.

How to actually find out which one it is

You can guess, or you can watch it happen. When we've wanted to see exactly where our own review-request flow lost people, rather than inferring it from drop-off numbers, we've used UserTapes to pull up the actual session — the real page load, the real hesitation, the real point someone closed the tab. It's a small thing, but watching two or three real sessions usually tells you more in five minutes than a week of A/B testing metrics without context.

You don't need a dedicated analytics stack to do this. Any session replay tool that shows you real visits to your landing page will do — the point is watching actual behavior instead of guessing from a percentage.

What to check once you can see the sessions

• Time to first interaction. If most sessions show a 3–5 second gap before anything happens, that's your load time or a confusing layout, not disinterest.
• Whether people scroll before acting. If customers are scrolling to look for something before clicking through, your call-to-action isn't visible enough.
• Where the session actually ends. A session that ends on your landing page (not on Google or Facebook) means the redirect or the instructions failed, not the customer.

The fix is usually small

Most of the time, this doesn't require rebuilding your review request flow. It's a bigger button, a page that loads faster, or removing a step you didn't realize was there. The hard part isn't fixing it — it's knowing it's broken in the first place, since a good open rate quietly hides a bad landing page.

If you're already running review requests through Plaudit and your open rates look healthy but completions don't match, this is the first place to look before you touch your messaging or your timing.