The Coverage Gap Quietly Killing Your Review Numbers

The morning number that shouldn't be a problem

Owen sells a packable camp chair, and his review count grows at a slow, steady trickle — enough that he's never flagged it as broken, never quite enough to feel like it's working either. One post-purchase email goes out, some customers leave a review, most don't, and he's assumed for over a year that this is just what review rates look like for a category like his. Nobody complained, so nobody looked closer.

That's the trap with a metric that's merely mediocre instead of obviously broken. A 2% review rate doesn't set off alarms the way a 0.3% CTR does. It just sits there, quietly underperforming, while the founder's attention goes to the numbers that actually look wrong.

Why "we have a review email" keeps failing

Having a review-request touchpoint and having the right review-request touchpoint aren't the same claim, and the gap between them is easy to miss because a checkbox — "do we ask for reviews, yes or no" — gets satisfied either way. Owen's single generic email fires after delivery and asks for a review. It exists. It's just aimed at the wrong moment for this specific product.

A camp chair's real proof-of-value moment isn't delivery — it's the first actual trip. A customer who bought a packable chair for camping doesn't have anything meaningful to say about it until they've used it outdoors, packed it back down, and found out whether it holds up the way the listing promised. Asking once, right after delivery, catches almost nobody at that moment. It's not that the email is worded badly. It's that "generic email after delivery" is one touchpoint doing the job of what should probably be two.

The diagnosis lens: coverage, not just performance

This is a funnel-coverage problem before it's a copy problem, which is why get_funnel_coverage matters here more than tweaking the existing email would. It doesn't just score how well the current touchpoint performs — it maps the entire Advocacy stage and shows where a meaningful moment in the customer journey has no touchpoint covering it at all. A single email can look "fine" in isolation while the coverage map shows it's the only thing standing where two or three moments actually need attention.

Once a gap is identified, run_funnel_audit puts a number on what that gap is actually costing — whether the missing touchpoint would be pulling more weight than the one that already exists, or whether it's a lower-priority fix than it feels like.

The working session

Owen came to the coach assuming his review numbers were "probably fine for the category" and wanted help writing better follow-up copy. The coach started with get_funnel_coverage across the Advocacy stage instead of touching the email.

The map showed exactly one touchpoint live in the entire stage: the generic post-purchase email, fired on a fixed delivery-based schedule. Nothing exists that's triggered by actual product use — no second touchpoint tied to a repeat-trip pattern, no signal-based ask timed to when a customer's chair has clearly been out and used more than once.

What the coach said: "You've got one touchpoint covering a stage that needs at least two different moments addressed. The email you have isn't wrong, it's just alone. The best moment for this specific product — right after someone's actually taken it on a trip and packed it back down — has zero coverage. You're not underperforming at asking for reviews. You're just not asking at the moment that would actually work."

run_funnel_audit confirmed the gap was worth closing before anything else in Advocacy: the missing usage-triggered ask scored as a higher-impact fix than optimizing the wording of the existing delivery-triggered email, because the existing email was never going to catch the right moment no matter how it was worded.

The fix was adding a second touchpoint — a usage-signaled ask sent later, framed around the first-trip experience specifically, rather than rewriting or replacing the delivery-day email. Both touchpoints now exist, each covering a different real moment instead of one email trying to cover both.

What to measure after

Give the new second touchpoint a full sales cycle before judging it, since it depends on customers actually completing a trip before it fires — for a seasonal outdoor product, that could be weeks depending on when someone bought. Watch total review rate first, then check whether the new reviews specifically reference actual outdoor use rather than just delivery experience. If the rate climbs but the content still skips real usage, the trigger timing for the second email may need adjusting, not the existence of the touchpoint itself.

If you're not sure whether your own Advocacy stage has real coverage or just one email standing in for several missing moments, the free Trust Gap diagnostic is a fast starting read on where your listing's proof is thin.

Coverage gaps rarely show up alone. A referral program that's underperforming on redemption is often the same kind of timing miss one stage further down. Permissioned UGC sitting unused and a loyalty-community blind spot are two more places the Advocacy stage tends to have gaps nobody's mapped yet. And if you're wondering whether your About page is quietly carrying work other touchpoints should be doing, your About page trying to do the whole funnel's job covers that same "one thing standing in for several" pattern on a different stage.

The one next action

Map every touchpoint currently live in your Advocacy stage and ask, for each one, what specific moment in the customer's real experience it's triggered by. If you find a stage with only one touchpoint covering what should be two or three distinct moments, that's the gap to close before you touch a single word of existing copy.