E-commerce
July 1, 2026
"The bot says Standard while my store card shows Gold." "The AI promises a tier upgrade without checking POS." "Chatbot does not state my member benefits nor the online store sync delay." Three failures where a miscalibrated membership card bot amplifies omnichannel disputes.
An omnichannel e-commerce loyalty card AI chatbot does not replace MEMCARD agents (#971). It reads MEMCARD-MAP, looks up POS status online, cites benefits_by_tier sync_rules map, and hands off renewal and lost operations to humans.
This guide #972 covers intents bot_memcard_*, flow MEMCARDBOT MCB-1 to MCB-8, and KPI memcard_bot. Bot pair of the MEMCARD playbook (#971). Use case: tier status benefits sync store web tier 1.
Summary
Why botify omnichannel membership cards?
"What is my member status?", "the store does not recognize me" and "what Gold benefits?" come up every week. A calibrated bot looks up MEMCARD-MAP, verifies the POS Shopify tier, and cites benefits_by_tier without improvising upgrades or benefits outside the map.
What the bot resolves tier 1
Tier status lookup: member_tier POS online cite map
Tier benefits: benefits_by_tier grounded map
Sync delay: sync_rules hours batch explain
Store recognition: store_recognition_method cite
Digital card: member_portal_url app wallet explain
The bot intercepts bot_memcard_status_verify before any invented tier or refusal, without guiding store online.
Omnichannel retail example
Retail fashion 42 stores 3-tier program, 14 memcard_ tickets/month. Bot syncs MEMCARD-MAP Day-0. memcard_bot_deflect +42%, memcard_bot_tier_invent_violation 0 over 8 weeks.
MEMCARDBOT #972 vs MEMCARD #971, LCARDbot #588, MEMSALEbot #584, LOYALTY #375 and PTS #374
Seven membership card bot contents, seven distinct roles.
Quick Matrix
#972 MEMCARDBOT: bot tier 1 status tier benefits sync online store widget
MEMCARD #971: agents verify sync staff cc renewal lost execute
LCARDbot #588: loyalty card points balance wallet distinct member status tier
MEMSALEbot #584: sales members access sale distinct identity card ongoing
LOYALTY #375: current program rules redemption
OMNIbot #272: stock general pickup distinct member card tier
Pipeline: bot status tier benefits cite → #971 renewal lost ops handoff execute.
Which bot_memcard_* intents should be configured?
Eight member card intents mapped to memcard_* typologies #971.
Eight bot_memcard intents
bot_memcard_status_lookup : tier active expired pending lapsed map
bot_memcard_benefits_explain : benefits_by_tier cite grounded
bot_memcard_store_guide : store_recognition_method staff brief
bot_memcard_sync_delay : sync_rules delay POS online cite
bot_memcard_renewal_info : renewal_policy member_portal_url
bot_memcard_digital_card : digital card app wallet portal
bot_memcard_lost_info : replacement_policy explain handoff
bot_memcard_handoff : mismatch ops renewal lost → #971
Tier 1 auto : status_lookup, benefits_explain, sync_delay, store_guide if email auth + MEMCARD-MAP + guardrails.
bot_memcard_handoff, renewal execute, lost replace, tier dispute → agents #971 payload memcard_id email.
How to consume/use MEMCARD-MAP #971?
The bot reads MEMCARD-MAP #971: memcard_id, membership_program, member_tier, benefits_by_tier, card_types, store_recognition_method, sync_rules, renewal_policy, replacement_policy, member_portal_url, staff_brief_url, expiry_date, agent_handoff_url.
Lookup grounded member
Member lookup API: email card_number barcode map
Status POS online: tier expiry STATUS-VERIFY-BOT both
TIER-GROUNDED-BOT: member_tier benefits_by_tier map only
SYNC-RULES-CITE-BOT: sync_rules before blame client
NO-TIER-INVENT-BOT: never upgrade tier off-register
LCARD-REROUTE-BOT: points balance → LCARDbot #588
Customer account widget: entry "My membership card" + lookup email card_number.
MEMCARDBOT-SUP policy in six rules
Six rules bot omnichannel membership card secure.
MEMBER-REGISTRY-GATE: lookup MEMCARD-MAP before status response
TIER-GROUNDED-BOT: member_tier benefits from map only
NO-TIER-INVENT-BOT: bot neither upgrades nor promises tier off-registry
STATUS-VERIFY-BOT: POS online API before citing tier
SYNC-RULES-CITE-BOT: cite sync_rules map before dispute
MEMSALE-REROUTE-BOT: member sales access → MEMSALEbot #584, points → LCARDbot #588
MEMCARDBOT MCB-1 to MCB-8 Flow
Eight-step flow: ingest detect lookup verify answer reroute handoff log.
MCB-1 Ingest: message status member tier store benefits
MCB-2 Intent detect: bot_memcard_* via keywords tier Gold
MCB-3 Registry lookup: MEMBER-REGISTRY-GATE MEMCARD-MAP
MCB-4 Status verify: POS online tier expiry live
MCB-5 Tier 1 answer: status benefits sync store_guide
MCB-6 Reroute: LCARDbot #588 MEMSALEbot #584 PTS #374
MCB-7 Handoff: renewal lost mismatch ops → agent #971
MCB-8 Log: deflect status benefits sync KPI
TPL-MEMCARD-STATUS Example
“Member card {{memcard_id}}: tier {{member_tier map}}. Status {{status}}. Validity {{expiry_date}}. Benefits: {{benefits_by_tier map}}.”
TPL-MEMCARD templates and touchpoints
Four short member card embed widget templates account mobile first.
TPL-MEMCARD-STATUS
[member_tier map.] [status.] [expiry_date.] TIER-GROUNDED.
TPL-MEMCARD-BENEFITS
[benefits_by_tier map.] [member_tier.] [member_portal_url.] BENEFITS-GROUNDED.
TPL-MEMCARD-SYNC
[sync_rules map.] Tier visible online within [sync_hours] h. [store_recognition_method map.] SYNC-RULES-CITE.
TPL-MEMCARD-HANDOFF
[agent_handoff_url.] Request [renewal / lost / mismatch / ops] transmitted. Member [memcard_id]. Delay [handoff_sla].
Touchpoints
"My member status": status_lookup + benefits_explain
Account membership widget: tier chip sync_delay entry
"Store does not recognize me": store_guide + SYNC template
Expired renewal: renewal_info + handoff if execute
Edge cases: loyalty points, member sales, paid club, duplicates
Five cases outside tier 1 bot standard member card.
Loyalty card points balance: reroute LCARDbot #588
D-day member sale access: reroute MEMSALEbot #584
Confirmed missing points: reroute PTS #374
Paid club renewal execute: handoff #971 renewal_policy ops billing
Unknown member outside map: handoff #971 UNKNOWN no guess tier
Bot never executes renewal replace tier adjust: post-verify status dispute → agents #971 ops retail.
Essential memcard_bot KPIs
Five MEMCARDBOT driving metrics and correlation #971.
memcard_bot_deflect: clarified statuses without memcard_ ticket
memcard_bot_benefits_cite_rate: % benefits_by_tier sessions provided tier 1
memcard_bot_sync_deflect: sync_delay explained without handoff
memcard_bot_handoff_rate: % renewal lost mismatch routed #971
memcard_bot_tier_invent_violation: invented tiers outside target map 0
Target: tier_invent_violation at zero and benefits_cite_rate above 85% post MEMCARD-MAP sync D-0.
MEMCARDBOT anti-patterns
Five common mistakes with the member card bot.
Inventing tiers off-map: NO-TIER-INVENT-BOT registry only
Promising non-map benefits: TIER-GROUNDED benefits_by_tier only
Forgetting sync delay: SYNC-RULES-CITE always cited
Confusing loyalty card points: #972 member status not LCARDbot #588
Duplicating MEMSALEbot #584: #972 access identity card distinct from member sales
MEMCARDBOT with Qstomy
Qstomy on Shopify: detect bot_memcard intent, MEMCARD-MAP RAG tier index, POS status verify API, templates STATUS BENEFITS SYNC, handoff #971 ops payload memcard_id.
Pipeline: #972 bot status tier benefits → #971 renewal lost ops execute.
Scenario: retail mode 42 shops 3 tiers program. Registry D-0. memcard_bot_deflect +42 %, tier_invent_violation 0.
Explore AI support and request a demo.
Checklist, FAQ and going further
MEMCARDBOT Checklist (8 steps)
Sync MEMCARD-MAP #971: RAG bot tier benefits index
Policy MEMCARDBOT-SUP: 6 REGISTRY-GATE TIER-GROUNDED NO-TIER-INVENT rules
8 intents bot_memcard_*: flow MCB-1 to MCB-8
4 templates TPL-MEMCARD-*: STATUS BENEFITS SYNC HANDOFF
Account membership chip: status_lookup entry widget
POS status API sync: verify tier online test store
Red team 10 prompts: invented tier benefit out of map test
Dashboard KPI: memcard_bot_* section 9 + delta memcard_
FAQ
Difference #971?
#971 = agents verify sync staff cc renewal execute. #972 = bot tier 1 status widget.
Bot upgrade the tier?
No, except MEMCARD-MAP. NO-TIER-INVENT-BOT. Handoff if dispute.
Difference LCARDbot #588?
#588 = loyalty card points balance. #972 = member tier status benefits.
Difference MEMSALEbot #584?
#584 = member sale access. #972 = ongoing member card identity.
Points balance or status?
Tier status benefits here. Points → LCARDbot #588 reroute.
Go further
This week: sync MEMCARD-MAP #971, member status widget, templates STATUS BENEFITS, measure memcard_bot_deflect.
Enzo
July 1, 2026
