E-commerce
July 1, 2026
"The bot shows 200 points while my store card shows 80." "The AI promises to block my lost card without agent escalation." "Chatbot merges two accounts without POS verification." Three failures where a poorly calibrated loyalty card bot amplifies omnichannel disputes.
An AI loyalty card chatbot does not replace LCARD agents (#587). It reads LCARD-MAP, looks up online POS balance, cites sync_rules replacement_policy wallet_url, and hands off merge block replace disputes to humans.
This guide #588 covers intents bot_lcard_*, LCARDbot flow, and lcard_bot KPIs. Bot companion of the LCARD playbook (#587). New AI loyalty use case: explain balance number sync delay without merging accounts or blocking card.
Summary
Why automate the loyalty card with a bot?
"What is my balance?", "my card number is not working" and "my store points are not showing up online" come up every week. A calibrated bot maps LCARD-MAP lookup, verify balance API POS Smile Yotpo, and cites sync_rules without improvising merging or blocking.
What the tier 1 bot solves
Balance lookup: online POS cite map sync_rules
Card number: validation lookup_methods map
Sync delay: sync_rules hours batch explain
Info linking: merge_account_policy procedure cite
Wallet pass: wallet_url regen explain map
Antavo notes that 38% of tier 1 loyalty card requests are balance or sync delay, resolvable without an agent if map grounded (Antavo, 2026 Loyalty Report). The bot intercepts bot_lcard_balance before an invented balance is returned.
LCARDbot vs LCARD #587, loyalty bot #375, PTS #374 and MEMSALEbot #584
Five contents, five distinct loyalty layers.
Quick matrix
#588 LCARDbot: tier 1 bot balance number sync wallet handoff
#587 LCARD: agents merge block replace escalate ops
Loyalty bot #375: common redemption program rules
Points #374: PTS-REC incident missing points adjust
#584 MEMSALEbot: member sale distinct tier card
Pipeline: balance bot sync number quotes → #587 merge block replace dispute ops. Confirmed missing points → #374 PTS-REC.
Which bot_lcard_* intents should be configured?
Eight loyalty card bot intents mapped to lcard_* typologies #587.
Eight bot_lcard intents
bot_lcard_balance: online balance POS cite sync_rules
bot_lcard_card_number: lookup number valid invalid map
bot_lcard_link_info: card linked unlinked merge procedure
bot_lcard_sync_delay: store purchase delay sync_rules cite
bot_lcard_wallet: Apple Google pass status wallet_url
bot_lcard_lost_info: replacement_policy explain handoff block
bot_lcard_lookup_fail: number not found invalid escalate
bot_lcard_handoff: merge block replace dispute → #587
Tier 1 auto: balance, card_number, sync_delay, link_info, wallet if email auth + LCARD-MAP + guardrails.
bot_lcard_handoff, merge execute, block lost, replace issue, balance dispute → agents #587 payload email card_number intent.
How do I consume LCARD-MAP #587?
The bot reads LCARD-MAP #587: program_id, card_types, lookup_methods, sync_rules, merge_account_policy, replacement_policy, wallet_pass_provider, escalation_ops.
Lookup grounded
Card lookup API: email card_number phone barcode map
Balance POS online: Smile Yotpo POS API BALANCE-VERIFY-BOT
Sync status check: batch pending transaction sync_rules
Link status: Shopify metafield card_number linked
SYNC-DELAY-CITE-BOT: sync_rules before blame client
GIFT-REROUTE-BOT: gift card balance euros distinct points
Alignment anti-hallucination (#123): balance sync replacement = LCARD-MAP or API only.
LCARDBOT-SUP Policy in six rules
Six safe loyalty card bot rules.
LCARD-MAP-GROUNDED: balance sync replacement from map only
BALANCE-VERIFY-BOT: POS online API before quoting balance
NO-MERGE-BOT: bot never merges duplicate accounts
NO-BLOCK-BOT: bot neither blocks nor replaces lost card
SYNC-DELAY-CITE-BOT: cite sync_rules map before dispute
PTS-GIFT-REROUTE-BOT: incident points → #374, gift card → gift card customer service
LCARDbot flow LCB-1 to LCB-8
Eight-step loyalty card bot flow.
LCB-1 Classify : bot_lcard_* intent detect
LCB-2 Collect : email card_number order_ref magasin
LCB-3 LCARD-MAP : program sync merge replacement wallet
LCB-4 Balance verify : POS online API BALANCE-VERIFY-BOT
LCB-5 Guardrail : NO-MERGE NO-BLOCK SYNC-DELAY-CITE
LCB-6 Respond : TPL-LCARDbot grounded map
LCB-7 Handoff : merge block replace dispute → #587
LCB-8 Log : intent program_id tag lcard_bot
Example TPL-LCARDbot-BAL
« Card [card_number] [email]: online balance [points_online] / POS [points_pos API]. [If gap in sync_rules delay: visible within [sync_hours] h.] [If dispute confirmed: agent handoff #587 escalation_ops map.] »
TPL-LCARDbot and touchpoints templates
Four essential templates.
TPL-LCARDbot-BAL
Card [card_number] [email]: online [points_online] / store [points_pos]. [If sync pending: delay [sync_rules map].] [If dispute: handoff #587.]
TPL-LCARDbot-LINK
Card linking [card_number] account [email]: [linked / not linked]. [If not: procedure [merge_account_policy map] link [account_url].] Account merger: agent handoff #587.
TPL-LCARDbot-SYNC
Store purchase [date]: sync [sync_rules map batch hours]. Points visible online within [sync_hours] h if POS transaction validated. [If delay exceeded: ops handoff #587.]
TPL-LCARDbot-HANDOFF
Request [merge / block / replace / balance dispute] forwarded to agent. Email [email]. Card [card_number]. Program [program_id]. SLA [handoff_sla].
Touchpoints
Account loyalty widget: bot_lcard_balance embed
Checkout card field error: bot_lcard_card_number chip
Wallet pass fail: bot_lcard_wallet entry
Loyalty FAQ: bot embed LCARD-MAP RAG
Edge cases and reroutes
Five cases outside tier 1 bot standard card.
Duplicate account merge: NO-MERGE-BOT handoff #587 LCARD-LINK-01
Lost card blocking: NO-BLOCK-BOT handoff #587 LCARD-LOST-01
Confirmed missing points: PTS-REC #374 reroute
Gift card balance euros: gift card distinct programme points
Program redemption rules: loyalty bot #375 reroute
Bot never executes merge block replace: balance dispute post-verify → agents #587 ops POS.
Essential lcard_bot KPIs
Five LCARDbot steering metrics.
lcard_bot_balance_deflect: balance resolved without agent
lcard_bot_sync_deflect: sync_delay explained without handoff
lcard_bot_handoff_rate: merge block replace dispute / total lcard bot
lcard_bot_hallucination_rate: sync balance outside audit map
lcard_bot_reroute_accuracy: PTS gift loyalty reroute correct
Target: lcard_bot_balance_deflect greater than 65% with LCARD-MAP sync POS API and sync_rules FAQ.
LCARDbot anti-patterns
Five common loyalty card bot errors.
Balance without verify API: BALANCE-VERIFY-BOT POS online first
Bot account merging: NO-MERGE-BOT handoff #587
Bot lost card blocking: NO-BLOCK-BOT handoff LOST-BLOCK-FIRST
Blaming customer for sync issues: SYNC-DELAY-CITE-BOT sync_rules first
Gift card points confusion: GIFT-REROUTE-BOT distinct euros points
LCARDbot with Qstomy
Qstomy on Shopify: detect bot_lcard intent, LCARD-MAP RAG grounded, Smile Yotpo POS balance lookup, handoff #587 merge block replace payload card_number program_id.
Pipeline: #588 bot balance sync wallet number → #587 merge block replace escalate ops.
Explore AI support and request a demo.
Checklist, FAQ and going further
LCARDbot Checklist (8 steps)
Sync LCARD-MAP #587: RAG bot + POS Smile Yotpo API
Policy LCARDBOT-SUP: 6 NO-MERGE-BOT NO-BLOCK-BOT rules
8 bot_lcard_* intents: LCB-1 to LCB-8 flow
4 TPL-LCARDbot-* templates: BAL LINK SYNC HANDOFF
Account widget embed: bot_lcard_balance entry
Checkout card chip: bot_lcard_card_number error
Red team 10 prompts: merge promised balance invented block card
Dashboard KPI: lcard_bot_* section 9
FAQ
Difference #587?
#587 = agents merge block replace escalate ops. #588 = bot tier 1 balance sync number handoff.
Bot merges accounts?
No. NO-MERGE-BOT. Handoff #587 merge_account_policy.
Lost card bot blocks?
No. NO-BLOCK-BOT. Handoff #587 LOST-BLOCK-FIRST.
Difference loyalty bot #375?
#375 = redemption program rules. #588 = omnichannel sync card ID.
Going further
This week: index LCARD-MAP RAG, embed bot account loyalty widget, red team merge bot promised accounts.
Enzo
July 1, 2026
