I’m testing a 90-second opt-in follow-up that starts with a quick satisfaction check, then offers a simple loyalty perk (10% birthday credit). Over 30 days it lifted repeat orders about 15% on our warm list — happy to share the script and compliant consent language if you’ll share what CRM tags you use to track outcomes.
Ran a similar 90-sec check-in and got a 12% repeat lift once we tagged in HubSpot like ‘checkin_90s’, ‘perk_bday10’, ‘nps_passive|detractor’, ‘warm_list’, plus an outcome ‘repeat_30d’ and a channel flag ‘sms’ vs ‘voice’. Caveat: birthday credits drew coupon-chasers, so we added DOB validation and a $20 minimum, and end consent with ‘Reply STOP to opt out’ to keep TCPA clean — shorter than a microwave popcorn cycle. If you’ll share your script, I can swap our workflow that auto-pings reps on ‘detractor’ within 24h so follow-ups don’t slip.
One tweak that helped us: ask for “birthday month” instead of the exact date and tag birthday_month + consent_source in SFDC — cut the call to about 55s and lifted opt-ins about 9%; tiny caveat, if they’re a detractor we park the perk for the follow-up so it doesn’t feel transactional. @lindsey_t89 if you share your detractor auto-ping, I’ll swap you our script and consent blurb.
We got a solid bump by asking a quick “about when should I remind you — 7, 14, or 30 days?” right after the satisfaction check, then tagging next_need_bucket and reminder_optin so the CRM schedules the nudge automatically… Small caveat: if they sound unsure, we switch to email-only reminder to keep opt-outs down and still saw about 10–12% more repeats.
Tried your “90-second” flow but let reps offer a quick choice — “10% credit” or “free shipping” — and warm-list repeats beat baseline by about 18% over 28 days; we tracked perk_choice, consent_ts, and reorder_window in Pipedrive to make attribution painless. Small caveat: shipping can eat margin, so add a max-cost rule; this breakdown helped me pick the perk: https://www.shopify.com/blog/free-shipping-vs-discounts.
We now ask “text or email?” right after the satisfaction check and tag channel_pref plus last_issue_code in HubSpot; it nudged repeat orders and cut opt-outs, but keep it to that one extra question to stay under 90 seconds. > eat margin, so add a max-cost rule; this breakdown helped me pick the perk: https://www.shopify.com/blog/free-shipping-vs-discounts. Same here — I cap perks at $3 COGS via a perk_cap_cents field so reps don’t over-offer.
I’ve had good results adding a one-line “morning, afternoon, or evening?” right after the satisfaction check in your “90-second” flow, then tagging daypart_pref and perk_accept in Salesforce; it bumped answer rates and made the 10% birthday credit feel more relevant on the next touch. Small caveat: keep it to that single extra choice or you’ll blow past the 90 seconds.
@OP We swapped to “anniversary month” perk; tag consent_ts+nps_bucket in Salesforce; 12% over 30 days, but expiry wording mattered.
I add a quick “reorder window — 2, 4, or 8 weeks?” right after the satisfaction check; we tag reorder_window and perk_variant in Pipedrive and trigger a 4‑week follow-up — kept it under “90 seconds” and repeat orders rose about 14%. @lauren_m89’s daypart idea is solid, but it adds about 20s for us, so we only ask it if they accept the 10% credit.
We saw about 12% by adding a soft “mind if I text the perk link?” micro‑ask and tagging consent_strength (soft|recorded), channel_pref (sms|email), perk_deferral (now|later), and objection_reason (price|timing|irrelevant) to auto‑route the next touch. Caveat: the birthday credit worked best with a 45‑day expiry and small minimum basket — otherwise it ate margin; happy to swap for your script/consent language — like a turn signal before a lane change.
Quick example: we bumped repeat orders about 11% over 30 days by stating the 10% birthday credit as a dollar figure — “for most orders that’s about $7 off.” In HubSpot we tracked value_frame and avg_cart_band and stamped perk_shown_ts for clean holdout math; @OP if you test it, try a small holdout. Caveat: if your AOV is under $25, percent phrasing edged out dollars.
I’ve had better stickiness by offering a “share it with a friend?” option right after the perk, which turns it into a mini-referral without feeling salesy. We track referral_optin (yes|no) and ref_channel (sms|email) in Salesforce and auto‑send a single‑use link; tiny caveat: it only works if you state the guardrails up front (“one per household”) so it doesn’t get gamed.
In my last test, keeping it pit‑stop quick worked when I opened with a one‑line pulse and closed with “mind if I tag this as ‘perk used’ or ‘saving for later’ so I don’t bug you?”, @OP. I track sat_snap (1–5), perk_stage (accepted|parked), and reason_decline (code); if they start venting I use “I’ve got 60 seconds — what’s the one thing to fix?” as a cap, and I’m happy to swap those tags for your consent language.