E-commerce
July 1, 2026
"The bot does not explain to me how to unlock the followers offer." "The AI says I am not subscribed without checking." "Chatbot invents a compensatory code." Three failures where a poorly calibrated subscriber offer bot creates an ad hoc gesture or denies without verify_steps.
An e-commerce social media subscriber offer AI chatbot does not replace FOLLEX agents (#951). It reads FOLLEX-MAP, cites verify_steps follower_code discount_value platform, and hands off mismatch ops to humans.
This guide #952 covers intents bot_follex_*, flow FOLLEXBOT and KPI follex_bot. Pair bot from the FOLLEX playbook (#951). Use case: verify eligibility conditions without manual follow checks.
Summary
Why botify follower offers?
"Subscriber code not working", "how to unlock the Instagram offer?" and "TikTok or Instagram offer?" arrive before agent ticket. A calibrated bot looks up FOLLEX-MAP, cites verify_steps account_handle follower_code without manually verifying the follow or issuing a compensatory code.
What the bot Tier 1 resolves
Unlock steps: verify_steps map order follow story code
Code status: follower_code valid expired exclusions Shopify API
Eligible platform: platform account_handle unlock_url map
Conditions cited: discount_value stack_rules exclusions
Current offer: alternative if followers offer expired
The bot intercepts bot_follex_unlock_guide before agent ad hoc gesture or negation without verify_steps.
FOLLEXBOT #952 vs FOLLEX #951, AMBbot #576, AFFOFFbot #938, PUSHbot #928 and POFF #573
Seven social bot promo contents, seven distinct roles.
Quick matrix
#952 FOLLEXBOT: tier 1 bot eligibility verify_steps code followers brand account
FOLLEX #951: agents unlock ops platform mismatch execute
AMBbot #576: creator code influencer named distinct brand followers
AFFOFFbot #938: affiliate offer third-party comparator blog
PUSHbot #928: push flash promo app distinct social followers
POFF #573: segmented CRM email offer reroute
INFLMISbot #950: creator promise ≠ distinct sheet follower offer
Pipeline: bot unlock code platform cite → #951 ops mismatch handoff execute.
Which bot_follex_* intents should be configured?
Eight bot intents offer mapped followers typologies #951.
Eight intents bot_follex
bot_follex_unlock_guide: verify_steps account_handle unlocking order
bot_follex_code_status: follower_code status Shopify API map
bot_follex_platform_check: eligible platform unlock_url mention
bot_follex_eligibility_info: no manual verification follow self-service
bot_follex_stack_info: stack_rules accumulation mention
bot_follex_expiry_info: expiry followers offer TTL
bot_follex_discount_info: discount_value conditions map mention
bot_follex_handoff: mismatch ops gesture → #951
Tier 1 auto: unlock_guide, code_status, platform_check, stack_info, expiry_info, discount_info if platform or code + FOLLEX-MAP + guardrails.
bot_follex_handoff, discount_mismatch ops, ad hoc gesture → agents #951 payload follex_offer_id.
How should FOLLEX-MAP #951 be consumed?
The bot reads FOLLEX-MAP #951: follex_offer_id, platform, account_handle, follower_code, discount_value, verify_steps, unlock_url, stack_rules, min_spend, exclusions, expiry, current_offer, agent_handoff_url.
Lookup grounded
Platform lookup: instagram tiktok → active FOLLEX-MAP row
Code lookup: follower_code → verify offer row
Shopify Discount API: usage status live exclusions
VERIFY-STEPS-GATE: verify_steps map only exact order
NO-MANUAL-FOLLOW-BOT: never ask for follow screenshot
Social referral checkout widget: bot_follex_unlock_guide badge if bio story traffic.
FOLLEXBOT-SUP policy in six rules
Six bot rules offer safe followers.
FOLLOWER-REGISTRY-GATE: discount conditions from FOLLEX-MAP only
VERIFY-STEPS-GATE: cites verify_steps map before code_status
PLATFORM-GROUNDED-BOT: offer valid on platform map only
NO-MANUAL-FOLLOW-BOT: no screenshot verification for follow
NO-CODE-ISSUE-BOT: bot does not issue or replace follower_code
AMB-AFF-REROUTE-BOT: named creator → #576, blog affiliate → #938
Flow FOLLEXBOT FLXB-1 to FLXB-8
Eight-step flow: ingest detect lookup classify answer reroute handoff log.
FLXB-1 Ingest: message code followers platform story highlight
FLXB-2 Intent detect: bot_follex_* via keywords platform code
FLXB-3 Registry lookup: FOLLOWER-REGISTRY-GATE platform or code
FLXB-4 Shopify verify: follower_code status exclusions live
FLXB-5 Tier 1 answer: unlock code platform stack expiry discount
FLXB-6 Reroute: AMBbot #576 AFFOFFbot #938 INFLMISbot #950
FLXB-7 Handoff: mismatch ops gesture → agent #951
FLXB-8 Log: deflect unlock_complete handoff KPI
Example TPL-FOLLEX-UNLOCK
“Follower offer {{platform}}: 1) Follow {{account_handle}} 2) {{verify_steps map}} 3) Code: {{follower_code}}.”
TPL-FOLLEX templates and touchpoints
Four short templates for the followers embed checkout widget.
TPL-FOLLEX-UNLOCK
[account_handle map.] [verify_steps map.] [follower_code map.] VERIFY-STEPS-GATE.
TPL-FOLLEX-CODE
[follower_code status map.] [discount_value map.] [exclusions expiry.]
TPL-FOLLEX-PLATFORM
[platform map.] [unlock_url map.] Offer valid on {{platform}} only. PLATFORM-GROUNDED.
TPL-FOLLEX-HANDOFF
[agent_handoff_url.] Request [mismatch / ops] forwarded. Offer [follex_offer_id]. Delay [handoff_sla].
Touchpoints
Checkout error chip: bot_follex_code_status entry
"How to unlock?": unlock_guide verify_steps
"TikTok or IG offer?": platform_check grounded
"Combine with site promo?": stack_info grounded
Edge cases: private account, expired story, ambassador, gifted
Five cases outside tier 1 standard bot followers.
Private account: self-service eligibility_info, no follow screenshot
Expired story highlight: expiry_info + current_offer + handoff ops
Named creator code: reroute AMBbot #576
Comparison blog deal: reroute AFFOFFbot #938
Collab promise ≠ sheet: reroute INFLMISbot #950
Bot does not correct story highlight: handoff #951 follex_ops_flag social marketing.
Essential follex_bot KPIs
Five FOLLEXBOT steering metrics and correlation #951.
follex_bot_deflect: follower offers clarified without follex_ ticket
follex_bot_unlock_complete_rate: % verify_steps sessions provided
follex_bot_code_status_rate: % tier 1 diagnosed code sessions
follex_bot_platform_mismatch_rate: % wrong platform detected sessions
follex_bot_code_issue_violation: compensatory codes issued target 0
Target: code_issue_violation at zero and unlock_complete above 78% post FOLLEX-MAP D-1 sync.
FOLLEXBOT anti-patterns
Five common mistakes with follower bot offers.
Asking for follow screenshot: NO-MANUAL-FOLLOW-BOT mandatory
Compensatory code: NO-CODE-ISSUE-BOT map only
Ignoring verify_steps: VERIFY-STEPS-GATE before code
Off-platform offer: PLATFORM-GROUNDED cite unlock_url
Duplicating AMBbot #576: #952 followers brand account only
FOLLEXBOT with Qstomy
Qstomy on Shopify: detect bot_follex intent, FOLLEX-MAP RAG grounded, Shopify discount verify, templates UNLOCK CODE PLATFORM, handoff #951 ops payload follex_offer_id.
Pipeline: #952 bot unlock code platform → #951 ops mismatch execute.
Scenario: DTC accessories, 13 tickets/month. Registry D-1 go-live. follex_bot_deflect +49%, ad hoc gestures -52%.
Explore AI support and request a demo.
Checklist, FAQ and going further
FOLLEXBOT Checklist (8 steps)
Sync FOLLEX-MAP #951: RAG bot + Shopify discount API
Policy FOLLEXBOT-SUP: 6 rules VERIFY-STEPS-GATE NO-MANUAL-FOLLOW
8 intents bot_follex_*: flow FLXB-1 to FLXB-8
4 templates TPL-FOLLEX-*: UNLOCK CODE PLATFORM HANDOFF
Checkout social referral chip: unlock_guide entry
verify_steps tested: mobile desktop before go-live
Red team 10 prompts: compensatory code screenshot follow
Dashboard KPI: follex_bot_* section 9
FAQ
Difference with #951?
#951 = agents unlock ops platform execute. #952 = bot tier 1 verify_steps widget.
Does the bot verify the follow?
No. NO-MANUAL-FOLLOW-BOT. verify_steps self-service only.
Difference with AMBbot #576?
#576 = creator code. #952 = brand account subscriber offer.
Difference with AFFOFFbot #938?
#938 = affiliate blog. #952 = brand social followers.
Go further
This week: sync FOLLEX-MAP #951, checkout social chip, UNLOCK CODE templates, measure follex_bot_deflect.
Enzo
July 1, 2026
