live demo · Chainlinks Reactivation OS
Restaurant winback growth, operated by agents.
Start with the customer list restaurants already have: lapsed buyers, loyalty members, VIP regulars, birthday guests, bad reviews, and catering leads. Chainlinks turns that database into manager-approved campaigns, tracked claim links, staff redemptions, and a recovered-revenue report the operator can trust.
public vertical demo
The page is restaurant-flavored, but the backend pattern generalizes to any customer database: segment stale records, propose a recovery action, track the claim link, prove ROI.
try the real token flow
Click to issue a REAL working claim code with QR. Open the customer claim link, claim it, then open the staff redeem portal (PIN 5150) and mark it redeemed. Same token + claim + redeem code path that ships into your restaurant.
Staff redeem PIN for the demo: 5150. Production wires per-staff PINs from your CRM or POS.
source database
Past orders, loyalty members, POS exports, reviews, catering/private-event leads, or a CSV.
segments
30/60/90-day inactive guests, VIP regulars, birthdays, bad-review recovery, catering leads.
approval queue
The agent drafts offers and copy; operators approve the exact campaign before anything sends.
claim page
SMS, email, receipt, and table-tent links all resolve to the Chainlinks-controlled mobile page.
segment console
Five approval-ready campaigns from one restaurant database.
60-day pizza winback
1,842 lapsed ordering customers
triggerNo order in 60+ days, opted into SMS/email
offer$8 off a $35 Friday night order
channelSMS first, email backup
VIP regular rescue
312 guests who used to order weekly
triggerSpend dropped 40% vs. personal baseline
offerChef note + free dessert with next table
channelEmail + manager call list
Birthday / anniversary
428 loyalty profiles with dates this month
triggerBirthday or anniversary window opens
offerCelebration entree upgrade for two
channelEmail, QR claim page
Bad-review recovery
47 recent 1-3 star reviewers
triggerReview mentions wait, cold food, or rude service
offerOwner-approved apology + make-it-right credit
channelReview reply + private claim link
Catering / private event leads
96 past banquet and large-party inquiries
triggerNo catering order in 90 days
offerFree tray upgrade on next event order
channelEmail sequence + staff follow-up queue
Reactivation OS · restaurant demo
linked crew · restaurant winback
I’m the Chainlinks Reactivation OS demo. Give me a restaurant segment, offer idea, or review-recovery scenario and I’ll draft the manager-approved campaign plan. For the first public build, chat uses a safe shared-service backend stand-in while the restaurant-specific persona is being separated.
backend note
This first public build proves the restaurant workflow with a safe shared-service chat backend. A dedicated restaurant persona can replace that backend without changing this page, the claim-flow model, or the ROI ledger.
campaign builder to ROI proof
01 · source database
Pull the list you already own
Chainlinks starts from past orders, loyalty profiles, POS exports, review feeds, catering inquiries, or a plain CSV. The public demo uses safe mock rows; the deployed system reads your real customer database.
02 · segment builder
Find the guests most likely to come back
30/60/90-day inactive guests, VIP drop-offs, birthday/anniversary windows, bad-review recovery, and catering leads become approval-ready work queues instead of forgotten spreadsheets.
03 · campaign approval
Offer + channel + manager review
The agent drafts the offer, message, channel mix, suppression rules, and staff notes. Nothing sends until an operator approves the campaign and the exact guest-facing copy.
04 · QR/link claim flow
Chainlinks owns the source-of-truth page
Every SMS, email, receipt insert, or table tent points to a Chainlinks-controlled mobile claim page. That page records scans, claims, opt-outs, referral shares, and expiry rules.
05 · redemption tracking
Staff can redeem manually today
A server enters the code or scans the QR. POS integration can come later; the demo proves the redemption ledger and recovered-revenue math without pretending every POS is already wired.
06 · ROI proof
Show scans, claims, redemptions, referrals, revenue
The weekly report ties activity back to recovered revenue estimates, staff follow-ups, and segments that paid off. Restaurants are the public demo; the backend pattern works for any customer database.
Scan + claim
Each QR or link scan opens a tracked mobile claim. The claim page is the source of truth for eligibility, expiry, referrals, and opt-outs.
Manual redemption
Staff can scan the code or type it into the operator view. POS integration is optional later; the ledger works today.
ROI report
Weekly proof rolls up scans, claims, redemptions, referrals, and estimated recovered revenue by segment and offer.
sample claim page
Friday Pizza Comeback
mobile claim preview
$8 off tonight
Valid for guests who have not ordered in 60+ days. Expires Sunday 10 PM.
One claim per guest
Referral share tracked
Manager can comp recovery cases
roi ledger
6,284
source records
orders, loyalty profiles, reviews, catering inquiries
2,913
inactive guests
30/60/90-day segments ready for approval
1,184
QR/link scans
mobile claim page events, not vanity clicks
326
claimed offers
unique guests who accepted the winback
118
redemptions
manual staff redemptions in the demo ledger
42
referrals
shared claim links attributed to the original guest
$9,740
recovered revenue
estimated checks from redemptions + referrals
5
approval queue
campaigns drafted and waiting for operator review
Demo data — your real ROI is measured weekly post-deploy from your actual POS, loyalty, and review data. Numbers above are safe mock rows for the public demo.
ships in your business
Pilot $500–$1,500 setup + $1,500–$2,500/mo retainer after pilot proof. Multi-location and strong-niche packages scale higher. The founder approves any final scope with you directly.