E-commerce
July 1, 2026
"The bot confirms Gold access without verifying my Smile status." "The AI promises -30% while the tier_benefits map says -20%." "The chatbot upgrades my tier to access the sale." Three failures where a miscalibrated member sales bot invents advantages or fraudulent tier upgrades.
An AI member sales chatbot does not replace MEMSALE agents (#583). It reads MEMSALE-MAP, verifies loyalty API tier status, cites tier_benefits early_access stack_rules, and uses handoff tag fix escalate to transfer to humans.
This guide #584 covers intents bot_mem_*, flow MEMSALEbot, and KPI mem_bot. Companion bot of the playbook MEMSALE (#583). New loyalty AI use case: verify access and explain benefits without upgrading tiers or issuing codes.
Summary
Why automate member sales with a bot?
"Why access denied?", "what are the Gold benefits?" and "can I join today?" skyrocket from D-1 to D+3 of the member sale. A calibrated bot looks up MEMSALE-MAP, verifies the Smile Yotpo tier, and quotes the early access discount without improvising upgrades.
What the tier 1 bot resolves
Access check: member status tier active pending expired
Tier benefits: tier_benefits discount early_access map
Status code: member_discount_code Shopify conditions
Join info: join_window_policy map quote
Stack policy: stack_rules stacking quote
Smile.io notes that 40% of loyalty tickets concern misunderstood benefit eligibility at the time of promotion (Smile, loyalty support 2026). The bot intercepts bot_mem_access_check before an agent invents a tier.
MEMSALEbot vs MEMSALE #583, PRIVATE #250, POFFbot #574 and loyalty bot
Five pieces of content, five distinct loyalty access models.
Quick matrix
#584 MEMSALEbot: tier 1 bot tier access code advantages
#583 MEMSALE: agents tag fix escalate ops marketing
Private sale #250: password gated distinct members
POFFbot #574: CRM offer distinct email segment
Loyalty bot: loyalty program current rules
Pipeline: bot access tier code → #583 tag fix escalate ops. Password gated → #250 reroute.
Which bot_mem_* intents should be configured?
Eight sales bot intents mapped member typologies #583.
Eight intents bot_mem
bot_mem_access_check: tier status access collection map
bot_mem_tier_benefits: tier_benefits discount early_access cite
bot_mem_code_status: member_discount_code status conditions
bot_mem_join_info: join_window_policy late membership
bot_mem_early_access: early_access_schedule hours tier
bot_mem_stack_info: stack_rules stacking cite
bot_mem_status_info: pending expired non-member explain
bot_mem_handoff: tag fix tier dispute escalate → #583
Tier 1 auto: access_check, tier_benefits, code_status, join_info, early_access, stack_info if email auth + MEMSALE-MAP + guardrails.
bot_mem_handoff, tag fix, tier dispute, upgrade demand → agents #583 payload sale_id email tier intent.
How to consume MEMSALE-MAP #583?
The bot reads MEMSALE-MAP #583: sale_id, membership_program, eligible_tiers, tier_benefits, member_discount_code, join_window_policy, early_access_schedule, stack_rules.
Lookup grounded
Sale lookup: sale_id → MEMSALE-MAP row
Loyalty API: Smile Yotpo tier status active pending
Shopify tag verify: customer tag tier collection gate
Discount API: member_discount_code status conditions
MEMBER-VERIFY-BOT: loyalty API before access yes
TIER-PRIVACY-BOT: tier criteria client tiers never disclosed
Alignment anti-hallucination (#123): access benefits = MEMSALE-MAP or loyalty API only.
MEMSALEBOT-SUP policy in six rules
Six rules bot member sales safe.
MEMSALE-MAP-GROUNDED : tier benefits access from map only
MEMBER-VERIFY-BOT : confirm loyalty status API before access yes
NO-TIER-UPGRADE-BOT : bot does not upgrade or create member tier
NO-CODE-ISSUE-BOT : bot does not issue or replace member sale code
TIER-PRIVACY-BOT : tier criteria of other clients never mentioned
PRIVATE-POFF-REROUTE-BOT : private sale → #250, CRM offer → #574
Flow MEMSALEbot MSB-1 to MSB-8
Eight-step flow for the member sales bot.
MSB-1 Classify: bot_mem_* intent detect
MSB-2 Collect: email sale_id tier claim
MSB-3 MEMSALE-MAP: tiers benefits schedule stack code
MSB-4 Member verify: loyalty API Shopify tag MEMBER-VERIFY
MSB-5 Guardrail: NO-TIER-UPGRADE NO-CODE TIER-PRIVACY
MSB-6 Respond: TPL-MEMSALEbot grounded map
MSB-7 Handoff: tag fix tier dispute → #583
MSB-8 Log: intent sale_id tier tag mem_bot
Example TPL-MEMSALEbot-ACCESS
"Member sale [sale_id] [email]: status [active / pending / expired / non-member]. Tier [tier map]. [If active: access [collection_url], discount [tier_benefits].] [If denied: reason [tag missing / ineligible / join_window]. Handoff if tag dispute.]"
TPL-MEMSALEbot templates and touchpoints
Four essential templates.
TPL-MEMSALEbot-ACCESS
Sale [sale_id]: status [tier status map]. [If active: collection [url], discount [tier_benefits].] [If not: join [join_url] or handoff #583.]
TPL-MEMSALEbot-TIER
Tier [tier]: discount [discount map], early access [early_access_schedule]. Conditions [min_spend exclusions]. Stacking [stack_rules map].
TPL-MEMSALEbot-CODE
Code [member_discount_code] tier [tier]: [Shopify status: valid / expired / tier mismatch]. Discount [discount_value map]. Valid [sale_dates].
TPL-MEMSALEbot-HANDOFF
Request [tag fix / tier dispute / upgrade] forwarded to agent. Sale [sale_id]. Email [email]. Tier claim [tier]. Delay [handoff_sla].
Touchpoints
Member sale landing: bot_mem_access_check embed auth
Checkout code error: bot_mem_code_status chip
Early access email: bot_mem_early_access entry tier
Loyalty program FAQ: bot_mem_join_info widget sale
Edge cases and reroutes
Five cases outside tier 1 bot sale standard members.
Tier upgrade requested: NO-TIER-UPGRADE-BOT handoff #583 ops marketing
Tag fix bug access: handoff #583 MEMSALE-ACCESS-01 escalate ops
Private sale password: PRIVATE #250 reroute
Missing points: PTS-REC #374 investigation
CRM email offer: POFFbot #574 reroute
Bot never upgrades tier: tag fix tier dispute → agents #583 ops loyalty marketing.
Essential mem_bot KPIs
Five MEMSALEbot management metrics.
mem_bot_access_deflect: access_check resolved without agent
mem_bot_code_deflect: code_status explained without handoff
mem_bot_tier_deflect: tier_benefits cited without dispute
mem_bot_handoff_rate: tag fix tier dispute / total mem bot
mem_bot_hallucination_rate: tier benefits outside audit map
Target: mem_bot_access_deflect greater than 65% during member sales window with MEMSALE-MAP sync loyalty API.
MEMSALEbot anti-patterns
Five common member sales bot mistakes.
Access without API verify: MEMBER-VERIFY-BOT loyalty first
Promised tier upgrade: NO-TIER-UPGRADE-BOT handoff #583
Verbal marketing benefits: tier_benefits map only
Bot-issued code: NO-CODE-ISSUE-BOT handoff marketing
Private sale confusion: PRIVATE-POFF-REROUTE #250 #574
MEMSALEbot with Qstomy
Qstomy on Shopify: detect bot_mem intent, MEMSALE-MAP RAG grounded, loyalty API tier lookup, Shopify discount verify, handoff #583 tag fix payload sale_id tier.
Pipeline: #584 bot access tier code → #583 execute escalate ops marketing.
Explore AI support and request a demo.
Checklist, FAQ and going further
MEMSALEbot Checklist (8 steps)
Sync MEMSALE-MAP #583: RAG bot + loyalty API
Policy MEMSALEBOT-SUP: 6 NO-TIER-UPGRADE-BOT rules
8 intents bot_mem_*: flow MSB-1 to MSB-8
4 templates TPL-MEMSALEbot-*: ACCESS TIER CODE HANDOFF
Landing embed auth: bot_mem_access_check entry
Checkout error chip: bot_mem_code_status trigger
Red team 10 prompts: upgrade tier code issued invented benefits
KPI Dashboard: mem_bot_* section 9
FAQ
Difference #583?
#583 = agents tag fix escalate ops marketing. #584 = bot tier 1 access tier code handoff.
Bot upgrade my tier?
No. NO-TIER-UPGRADE-BOT. Handoff #583 ops loyalty.
Member access denied?
TPL-MEMSALEbot-ACCESS MEMBER-VERIFY-BOT loyalty API tag.
Difference loyalty bot?
Loyalty bot = current program rules. #584 = members sale MEMSALE-MAP sale window.
Going further
This week: index MEMSALE-MAP active sale RAG, embed bot members landing, red team upgrade tier promised.
Enzo
July 1, 2026
