E-commerce
July 1, 2026
"I followed your Instagram account, the followers code isn't working." "The followers offer was on TikTok, I'm on Instagram." "How do I prove I'm subscribed to get -15%?" Three tickets where an offer reserved for followers creates friction with eligibility and cart abandonment.
The social media e-commerce subscriber offer support covers unlock steps, follower code validity, eligible platform, promo stacking, and expired offers still visible in stories. Distinct from ambassador codes (#575), affiliate offers (#937), and CRM offers (#573).
This guide #951 deploys the FOLLEX-SUP policy, flows FLX-1 to FLX-8, and the FOLLEX-MAP matrix. Future customer service pair: subscriber offers bot (#952).
Summary
Why do follower offers generate tickets?
DTC brands use "followers only" codes to convert organic audience. The customer must follow the account, sometimes activate notifications, or retrieve the code in a close friends story. When the steps are not clear or the code fails at checkout, the ticket arrives at customer service without verifiable proof of following on the agent's side. Without FOLLEX-MAP, the agent grants an ad-hoc gesture or denies it without referencing verify_steps map.
Five typical frictions for follower offers
Invalid follower code: coupon rejected at Shopify checkout
Vague eligibility: customer does not know how to unlock the offer
Wrong platform: IG offer, customer comes from TikTok
Stacking refused: follower code + site promo impossible
Expired story: ended offer still visible in highlights
DTC fashion example
DTC accessories, -15% Instagram followers offer, 13 follex_/month tickets. After FOLLEX-MAP: follex_resolution_rate 86%, ad-hoc gestures -52% in 5 weeks.
FOLLEX #951 vs AMB #575, AFFOFF #937, POFF #573, PUSH #927 and bot #952
Seven social promo contents, seven distinct angles.
Quick Matrix
#951 FOLLEX: offer reserved for brand account subscribers step verification
AFFOFF #937: third-party comparison blog affiliate offer
POFF #573: segmented profile email CRM offer
PUSH #927: app flash promo push distinct from social followers
INFLMIS #949: creator promise ≠ distinct sheet brand followers offer
Bot #952: bot verify eligibility tier 1 conditions
#575 = visible creator code. #951 = brand account subscribers offer with follow steps.
Promise #951
FOLLEX-SUP policy, FOLLEX-GATE tree, 8 macros, followers offer registry, KPI follex_resolution_rate.
Which follex_* typologies to classify?
Action-oriented classifier: eligibility ≠ code ≠ platform ≠ stacking ≠ expiration.
Eight FOLLEX-MAP typologies
follex_unlock_steps: customer does not know how to unlock the followers offer
follex_code_invalid: subscriber code rejected at checkout
follex_eligibility_ask: how to prove subscriber status
follex_platform_mismatch: platform A offer, customer on platform B
follex_stack_denied: stacking followers code with site promo rejected
follex_expired_offer: offer ended but still in story highlight
follex_discount_mismatch: story discount different from checkout
follex_ops_flag: marketing signal to align followers messaging
Tags: follex, followers_offer, social_exclusive, platform_gate. FOLLEX-MAP-GROUNDED: verify_steps discount from registry only.
FOLLEX-SUP Policy: agent rules and followers offers registry
The FOLLEX-SUP policy sets explanation steps without manually verifying the follow or honoring off-registry.
Six FOLLEX-SUP rules
FOLLOWER-REGISTRY-FIRST : check followers offer registry before agreeing
VERIFY-STEPS-CITE : cite verify_steps map step-by-step
PLATFORM-GROUNDED : valid offer platform map only
NO-MANUAL-FOLLOW-CHECK : agents do not verify follow manually
STACK-RULES-CITE : stacking according to stack_rules map only
Handoff #952 : bot brief eligibility conditions widget
Minimum followers offer registry
follex_offer_id : followers offer identifier
platform : instagram tiktok facebook etc.
account_handle : @ brand account to follow
follower_code : active Shopify code
discount_value : official discount map
verify_steps : follow notification story bio link order
unlock_url : code unlocking landing page if applicable
stack_rules expiry exclusions : stacking validity excluded SKUs
Flow FLX-1 to FLX-8: subscriber offer ticket processing
Eight steps: intake lookup verify classify resolve ops log closure.
Flow FLX-1 to FLX-8
FLX-1 Intake: source code platform story highlight order_ref
FLX-2 Classify: follex_* via FOLLEX-MAP
FLX-3 Registry lookup: FOLLOWER-REGISTRY matching offer
FLX-4 Shopify verify: follower_code status usage exclusions live
FLX-5 Resolve: macro FOLLEX grounded map verify_steps
FLX-6 Platform check: PLATFORM-GROUNDED if platform mismatch
FLX-7 Ops flag: expired story active → social marketing ops
FLX-8 Log: KPI follex + registry correction brief
SLA: follex_unlock_steps verify_steps quoted in one interaction if map exists.
Eight ready-to-paste FOLLEX-* macros
Factual macros without ad hoc gesture out of followers register.
FOLLEX-* Library
FOLLEX-UNLOCK-01: "Follower offer {{platform}}: 1) Follow {{account_handle}} 2) {{verify_steps map}} 3) Code: {{follower_code}}."
FOLLEX-CODE-01: "Follower code {{follower_code}}: {{statut}}. Discount {{discount_value}}. Terms: {{exclusions}}."
FOLLEX-PLATFORM-01: "Offer valid {{platform}} only. Account: {{account_handle}}. Link: {{unlock_url}}."
FOLLEX-STACK-01: "Follower code stacking: {{stack_rules}}. Site offer: {{lien_promo}}."
FOLLEX-EXPIRED-01: "Follower offer ended {{expiry_date}}. Current offer: {{offre_actuelle}}."
FOLLEX-MISMATCH-01: "Official discount {{discount_value}}. Story reported to alignment team."
FOLLEX-ELIG-01: "We do not manually verify subscriptions. Please follow the steps: {{verify_steps}}."
FOLLEX-DONE: "Ticket summary {{id}}. Resolution: {{résolution}}."
FOLLEX-GATE tree and social marketing coordination
Decision tree before ad hoc action or negation without verify_steps.
FOLLEX-GATE
Platform or code provided? u2192 registry lookup FLX-3
Customer does not know how to unlock? u2192 UNLOCK-01 verify_steps
Valid Shopify code? u2192 CODE-01 + conditions map
Wrong platform? u2192 PLATFORM-01 unlock_url
Stack requested? u2192 STACK-01 stack_rules map
Expired story highlight? u2192 EXPIRED-01 + ops flag social
Discount u2260 story? u2192 MISMATCH-01 ops flag
Named creator code? u2192 reroute AMB #575
Followers offer launch ritual
Social marketing publishes FOLLEX-MAP D-1: verify_steps tested on mobile, follower_code active on Shopify, expiry_date. Bot #952 sync go-live.
KPI, QA and handoff to bot #952
Measuring FOLLEX detects obsolete offers and incomplete unlock_steps.
Five FOLLEX KPIs
follex_resolution_rate: tickets resolved without ad hoc action
follex_unlock_success_rate: customers guided through verify_steps without escalation
follex_code_success_rate: codes diagnosed without ad hoc reissue
follex_platform_mismatch_rate: wrong platform / active offers tickets
follex_ops_flag_rate: reports of active expired story highlight
Handoff #952
Export FOLLEX-MAP to bot: priority follex_unlock_steps, follex_code_invalid, and follex_platform_mismatch. Guardrail VERIFY-STEPS-GATE brief #952 verify_steps widget checkout.
Edge cases: private account, unfollow, multi-platform offer
Four cases outside the standard flow.
Private Instagram client account
ELIG-01: no manual follow verification. verify_steps self-service only.
Client unfollows then re-follows
UNLOCK-01 complete order verify_steps. No exception without documented marketing policy.
Followers offer + ambassador code
Two distinct codes: STACK-01 + reroute AMB #575 if creator code is mentioned.
Story promise ≠ product sheet
No follex alone: reroute INFLMIS #949 if creator collab promises something different.
Agent training: 20 minutes FOLLEX
Module: FOLLOWER-REGISTRY, distinguish AMB #575 AFFOFF #937 POFF #573 bot #952.
Exercises
Ticket A: how to unblock → UNLOCK-01 verify_steps
Ticket B: invalid followers code → CODE-01 Shopify reason
Ticket C: IG client TikTok offer → PLATFORM-01
Ticket D: scale followers + promo → STACK-01
How Qstomy structures FOLLEX in your stack
Qstomy on Shopify: follex_* route, followers offer registry sync, UNLOCK CODE PLATFORM and handoff macros, bot #952 eligibility gate.
Three building blocks
Routing: followers_offer vs ambassador vs active promo intent
Follower offer registry: platform verify_steps code stack_rules expiry
Bot #952: tier 1 eligibility conditions unlock widget
Scenario: DTC accessories, 13 tickets/month. Registry D-1 go-live. follex_resolution_rate 86%, ad hoc gestures -52%.
Explore AI support and request a demo.
FOLLEX deployment FAQ and checklist
FAQ
Manually check the follow?
No. NO-MANUAL-FOLLOW-CHECK. ELIG-01 verify_steps self-service.
Difference AMB #575?
#575 = named influencer creator code. #951 = brand account subscribers offer.
Difference AFFOFF #937?
#937 = affiliate blog comparison site offer. #951 = brand social account followers.
Difference #952?
#951 = agents verify ops unlock. #952 = bot tier 1 eligibility widget.
Honor expired story offer?
No without marketing bridge. EXPIRED-01 + current offer.
FOLLEX deployment checklist (8 steps)
FOLLEX-SUP + FOLLEX-MAP: followers offer registry template
verify_steps tested: desktop mobile journey before go-live
Shopify follower_code: active stack_rules exclusions documented
follex_* Tags: follex_offer_id platform correlation
Ops flag channel: marketing social story highlight expiry
Reroute AMB #575 INFLMIS #949: documented FOLLEX-GATE tree
Sync bot #952: VERIFY-STEPS-GATE
20 min training: section 10 exercises
Linking
Enzo
July 1, 2026
