Review and Referral Requests at the Moment of Proven Success
The short answer
Review requests work when tied to proven success and sent over iMessage. Blue Reacher fires the ask within an hour into a thread where 90% of messages are read in three minutes. Ask every customer the same link.
4 use cases in this category
Trigger
Event in your CRM
Under 60s
Send iMessage
Result
Reply in the thread
Key takeaways
- Email: 27.7% open, 85% spam folder, 0.45% reply (Belkins, 2025, 7.5M sends).
- Gating asks how someone feels, then sends happy ones only to public sites.
- A success moment is a CRM event, not a calendar date.
- Timing is the only variable that changes across industries.
- The ask should read like a text from the person who did the work.
- Track ask-to-review conversion per trigger, not campaign, because rates differ by event.
Where iMessage runs in the funnel
Why the ask dies in email and lands in threads
Email: 27.7% open, 85% spam folder, 0.45% reply (Belkins, 2025, 7.5M sends). Your ask lands with promos the customer archives instantly. The channel is broken.
- iMessage: 98% open, 90% read in three minutes, same app as their texts. Delivery states show what happened. Timing beats copy: the customer who just won reads it; the one in trouble ignores it.
- The table below runs one quarter through both channels. Multiplying your opened-to-posted rate against 392 reads instead of 111 moves posted-review count by 3.5x. The copy didn't get better. The ask just got read.
Customers hitting a success milestone per quarter
- Number
- 400
- Result
- 400 asks sent
Email review request opened
- Number
- 27.7%
- Result
- 111 asks seen
iMessage ask opened
- Number
- 98%
- Result
- 392 asks seen
Extra asks seen per quarter
- Number
- same list, same copy
- Result
- 281
Extra asks seen per year
- Number
- four cycles
- Result
- roughly 1,124
Reviews posted
- Number
- your own opened-to-posted rate
- Result
- 3.5x whatever email produced
Ask everyone, same link
Gating asks how someone feels, then sends happy ones only to public sites. Google, Trustpilot, G2 prohibit it. The FTC Rule on Consumer Reviews (Oct 21, 2024) bans misrepresenting shown reviews as representative.
- Send the same message to everyone who hit the success event. Reply publicly to bad ratings and name the fix. A thread gives early warning: unhappy customers text before review sites, giving your rep time to call.
How the success-moment play works
A success moment is a CRM event, not a calendar date. Examples: placement past week one, claim paid, delivery, usage threshold, renewal, escalation closed. Write it as a field or tag your stack sets.
- Fire on the event itself. The webhook fires when the pipeline stage changes and the contact drops into a short sequence. Scheduled sends hold the message until it's inside the recipient's local window, so a win logged at 11pm goes out at the start of their next business morning.
- Lead with the specific result. Name the number, the placement, the delivery date. A generic "how did we do" reads like it came from software. Naming the win proves a person is on the other end.
- One link, one tap. Send the direct review URL for one platform, chosen per segment. Two links make the reader choose before they act, and split your volume across two pages that both end up looking thin.
- The account owner answers, not a shared inbox. Replies to a review ask are half thank-yous and half problems, and both need the person who owns the relationship.
- Follow up once, three days later, then stop. Two asks is the ceiling. A third turns a customer into someone who mutes the thread.
- Split the referral ask out by 10 to 14 days. Bundling review and referral into one message makes the reader decide twice before replying once, and the usual result is neither. Ask for one named introduction rather than "know anyone who'd benefit," and offer to write the two lines they forward.
Reading how it works is not the same as watching it answer one of your own leads. The Blue Funnel Map does the second one.
See it on your own listWhen to send
Timing is the only variable that changes across industries. Sequences run 1-12 steps with delays from 15 minutes to 90 days, fitting inside one workflow.
Success event detected
- Timing
- T+0
- What it does
- Webhook fires from the CRM, contact enters the sequence
Ask 1
- Timing
- Within 1 hour, held to your sending window, 9am to 6pm local
- What it does
- Names the specific win, one link, one tap
Reply handling
- Timing
- Within 1 hour, business hours
- What it does
- Account owner answers personally, good or bad
Ask 2
- Timing
- 3 days after ask 1, only if no reply
- What it does
- One line, same link, no new pitch
Hard stop
- Timing
- After ask 2
- What it does
- No third ask on this event
Referral ask
- Timing
- 10 to 14 days after the review moment
- What it does
- One named introduction, offer to draft the forward
Public reply to a negative review
- Timing
- Within 48 hours of it posting
- What it does
- Own it, state the fix, leave the review up
Next cycle
- Timing
- Next success event, minimum 90 days apart
- What it does
- Same play, new proof point
What to say
What to say
The ask should read like a text from the person who did the work. Keep it to a couple of lines, name the specific win. Lowercase is fine. STOP handling runs account-wide.
- First ask (within 1 hour): "hey [name], just saw [win]. [platform] link. say it honestly, good or bad."
- Three-day nudge: "no pressure, just bumping in case it got buried: [link]"
- Referral ask (12 days): "worth an intro with [person]? happy to draft it."
- Complaint reply: "that's on us and i'd rather hear it now. calling you in ten."
How to set this up in a CRM
How to set this up in a CRM
Make the success event machine-readable. In GoHighLevel, trigger on pipeline stage, tag, or custom field. Branch on a custom field set when a review lands so people who already reviewed never see ask 2.
- Other CRMs connect via REST API and webhooks. iMessage checks before send; RCS then SMS fallback covers non-Apple. Consent and opt-out handling run account-wide. FCC rules require honoring STOP within 10 business days.
How to measure what worked
How to measure what worked
Track ask-to-review conversion per trigger, not campaign, because rates differ by event. Track median hours from event to posted review: shrinking gap means your trigger fires closer to the win.
- Watch rating distribution, not average. Count negative thread replies as support saves. On referrals: count named introductions per 100 asks, intro-to-closed rate, and revenue back to referring customers.
Frequently asked questions
Can I ask customers who might leave a bad review?
Yes, and you're required to. Google prohibits selectively soliciting positive reviews, Trustpilot requires inviting everyone the same way, and G2 flags sellers who solicit only positive ones. Send the same message and the same link to everyone who cleared the success event, then fix what the unhappy ones tell you.
Is review gating illegal, or just against platform rules?
Both. Gating on solicitation breaks platform policy at Google, Trustpilot, G2, and Capterra. Suppressing reviews you display breaks the FTC's Rule on Consumer Reviews, effective October 21, 2024. Fashion Nova paid $4.2M (January 2022) for holding back four-star reviews.
How soon after the success moment should the ask go out?
The ask goes out within the hour, held to recipient's local business window. When a customer feels the win, they'll spend 90 seconds on you; that feeling fades fast. Scheduled sends handle timing, so a Friday 11pm trigger goes out Monday morning their time.
Should the review ask and the referral ask go in the same message?
No. Two asks in one message cuts response on both, because the reader has to decide twice before replying once. Send the review ask at the success moment and the referral ask 10 to 14 days later, phrased as one named introduction rather than an open call for anyone.
What should I do about a one-star review?
Reply in public within 48 hours, name what went wrong, say what changed, and leave the review up. Pulling it or pressuring the customer to pull it is exactly what the FTC's suppression provisions cover. A well-handled negative review does more for a skeptical buyer than five more five-star one-liners.
Can I offer a gift card or discount for a review?
No. Google bars offering payment, discounts, or goods for posting or removing reviews. G2 allows incentives only through its own program, never conditioned on the review content. Ask well and incentivize nothing.
Does sending review requests over iMessage need A2P 10DLC registration?
No A2P registration is required. A2P 10DLC governs US carrier SMS routes, and iMessage isn't carrier SMS. That's a registration distinction rather than a consent exemption, so TCPA and your existing suppression rules still apply exactly as they do on email and SMS.
What happens if the customer isn't on an iPhone?
The message still reaches them. Availability checking runs before the send, and RCS then SMS fallback covers non-Apple devices, so a mixed customer list runs through one sequence instead of two. Delivery states report back per message either way, so your reporting stays intact across device types.
Put the ask where they already reply
A dedicated iMessage line runs $249 a month with unlimited iMessages (unlimited covers the conversations you're in; new outreach is paced at the safe-send rate of up to 50 opted-in / 30 cold new conversations per line per day, because this is a conversation channel, not a blast tool) and no A2P registration required, wired to your CRM so every success event triggers the ask within the hour. White-glove activation is waived on annual billing. Book a walkthrough and we'll map your success events to a live sequence on the call.