live demo · Chainlinks Reviews + Referrals OS
Turn every finished job into reviews + referrals.
Most local businesses leave reviews and referrals to chance. The Reviews + Referrals OS asks every customer the right way, routes unhappy ones to private service recovery BEFORE they post a public review, issues tracked referral codes to the happy ones, and drafts owner-approved replies to every public review. Compliant, operator-approved, attributable.
public vertical demo
The page is review-and-referral-flavored, but the backend pattern generalizes to any post-purchase moment: capture the trigger, route happy vs unhappy separately, attribute every recovered relationship.
try the real token flow
Issue a REAL referral code with QR. Reward issues ONLY after the referred customer is redeemed at the staff portal — not on share, not on signup. Fraud-guard built in. Try it: issue → claim → redeem (PIN 5150) and watch the audit log.
Staff redeem PIN for the demo: 5150. Production wires per-staff PINs from your CRM or POS.
source moments · what the agent catches
Four moments. Four routings. One ledger.
completed jobs and visits
Trigger: Job marked complete in the CRM, dispatcher, or POS.
Action: Operator-approved review request goes to the customer with one CTA. No incentive attached. Single channel by their preference.
proof: 312 post-job review requests this month
service recovery before public review
Trigger: Pre-send check detects dissatisfaction (low NPS, complaint keyword, hold-time abandon, escalated ticket).
Action: Customer routed to a private make-it-right offer first. Owner approves. Public review request paused until recovery resolves.
proof: 47 cases intercepted, 31 relationships saved before posting
honest reviewer → referral ask
Trigger: Customer leaves a verified 4-5 star review.
Action: Owner-approved referral code or share link sent to the reviewer. Code attributes any future booking back to the referrer.
proof: 36 referral shares · 14 booked jobs · $42,800 attributed
existing Google / Yelp / Facebook reviews
Trigger: New public review posted, positive or negative.
Action: Agent drafts a 2-3 sentence owner-tone reply. Never defensive, never argumentative. Owner approves before publish.
proof: Average reply within 48h · 92% reply rate
work queues · what the operator sees
Drafted, owner-approved, never autonomous.
| queue | audience | approved action | expected impact |
|---|---|---|---|
| Post-job review request Every customer whose job closed in the last 72h | Job status → complete | Single-CTA SMS or email asking for an honest Google or Yelp review. No raffle tied to rating. | 188 honest reviews / month at 4.7 avg |
| Service-recovery intercept Customers flagged dissatisfied before any review is asked | Negative-signal detection in survey, complaint, or ticket history | Private apology + make-it-right offer drafted; owner approves; public review request held pending resolution. | 31 saved relationships, ~$0 public negative review damage |
| Referral loop Customers who left a verified 4-5 star review | Verified review posted | Branded referral code + share copy sent. Reward issued ONLY after the referred customer books a real job (fraud guard). | 36 shares → 14 bookings → $42,800 tracked |
| Bad-review reply Existing 1-3 star public reviews | New low-star review detected on Google / Yelp / Facebook | Owner-tone 2-3 sentence reply drafted. Never defensive. Always offers a private path. Owner approves before publishing. | Faster reply window changes Google ranking + future-buyer perception |
workflow · capture → recover → reward → reply → prove
01 · capture the moment
Catch every post-purchase signal
Job complete, ticket closed, meal delivered, install signed off — each becomes a tracked moment the agent can act on. Demo uses safe mock events; production wires into your CRM, dispatcher, or POS.
02 · route happy vs unhappy
Dissatisfaction goes private first
If the pre-send check finds dissatisfaction signals, the customer gets a private service-recovery path instead of a public review ask. No review gating — recovery offer goes to ALL detected complaints, public review request goes to ALL customers.
03 · owner approves every send
Operator in the loop
Drafted SMS, email, public review replies, and referral copy land in an approval queue. Owner clicks send. Nothing autonomous touches customers without sign-off.
04 · referral loop with fraud guard
Reward only on verified booking
Happy reviewer gets a tracked share link or referral code. Referred customer redeems on booking. Reward issues only after the booking confirms — not on share, not on signup. Prevents farming.
05 · proof in the ledger
Every recovered relationship attributable
Weekly ROI report rolls up review requests sent, reviews captured, service recoveries, referral shares, referral-attributed bookings, attributed revenue, and reply turnaround time.
talk to the agent
Ask the Reviews + Referrals OS
Try a tricky review reply, a recovery scenario, or a referral question. The agent answers with what the production system would actually do — not generic AI fluff.
Reviews + Referrals OS · live
post-job · service recovery · tracked referrals
I'm the Reviews + Referrals OS agent. Ask me about: post-job review requests, intercepting unhappy customers before they post, drafting replies to existing reviews, referral codes with fraud-guard attribution, or this week's ROI ledger. (Tap a chip below or type freely.)