E-commerce
July 1, 2026
"The bot listed the products of the next mystery lot for me." "The AI promised a return even though it's a final sale." "The chatbot invented a guaranteed value of €120 that was missing from the product sheet." Three failures where a badly calibrated mystery lot bot spoils the surprise or promises outside of policy.
An AI mystery lot chatbot does not replace MYBOX agents (#555). It reads MYBOX-MAP, cites rules and grounded guaranteed value, refuses to spoil content, and hands off missing gestures to humans.
This guide #556 covers intents bot_mybox_*, flow MYBOXbot, and KPI mybox_bot. Pair bot of the MYBOX playbook (#555). New AI surprise use case: explaining rules without spoiling the content.
Summary
Why automate mystery batches via bot?
"What does the bundle contain?" and "can I return if disappointed?" spike before the Lucky Bag launch. A calibrated bot quotes item_count_range, value_guarantee, return_policy from MYBOX-MAP without revealing SKU content.
What the tier 1 bot resolves
Pre-purchase rules: count value guarantee categories map
Final sale explain: grounded quote of return_policy
Guaranteed value: value_guarantee retail min
Exclusions: categories exclusions without spoiling
Post-purchase scope: missing vs disappointment route
Gorgias observes that surprise product tickets convert 2x more into disputes if the policy is vague (Gorgias, 2026 CS stats). The bot intercepts bot_mybox_rules before any spoiler or return is promised.
MYBOXbot vs MYBOX #555, box subscription #415 and box set #221
Five contents, five distinct surprise models.
Quick Matrix
#556 MYBOXbot: tier 1 bot rules without spoiler
#555 MYBOX: agents missing gesture return execute
#415 box abo: recurring subscription preferences
#221 coffret: fixed content limited edition
Bot box abo: distinct surprise subscription bot
Pipeline: rule bot quotes → #555 missing gesture execute. #415 = recurrence, not bot_mybox intents.
Which bot_mybox_* intents should be configured?
Eight mystery batch bot intents mapped to typologies #555.
Eight bot_mybox intents
bot_mybox_rules_pre: pre-purchase batch rules without spoilers
bot_mybox_value_guarantee: guaranteed minimum retail value
bot_mybox_return_policy: final sale return explanation
bot_mybox_expectation: number of items mapped by category
bot_mybox_disappointment_handoff: disappointed → handoff #555
bot_mybox_missing_handoff: missing item → handoff #555
bot_mybox_damaged_handoff: broken or leaked → handoff #555
bot_mybox_duplicate_handoff: already owned → handoff #555
Tier 1 auto: rules_pre, value_guarantee, return_policy, expectation if product or order lookup + MYBOX-MAP + NO-SPOILER-BOT.
bot_mybox_disappointment, missing, damaged, duplicate handoff → agents #555 with payload order box_sku intent.
How should I consume MYBOX-MAP #555?
The bot reads MYBOX-MAP #555: box_sku, item_count_range, value_guarantee, categories_included, exclusions, return_policy, gesture_matrix, spoiler_rules.
Lookup grounded
Product browse: box_sku PDP rules without SKU content
Order verify: ordered box fulfillment status
MYBOX-MAP row: value return spoiler_rules scope
NO-SPOILER-BOT: never list box content products
NO-RETURN-PROMISE: return quotes return_policy map only
MISSING-HANDOFF: gesture execute → agents #555
Alignment anti-hallucination (#123): value_guarantee = MYBOX-MAP only, never invented.
MYBOXBOT-SUP policy in six rules
Six rules for the mystery box bot.
NO-SPOILER-BOT: bot never reveals SKU box content
MYBOX-MAP-GROUNDED: rules value returned from map only
NO-RETURN-PROMISE-BOT: bot does not promise returns outside map
VALUE-GUARANTEE-BOT: min value cited map explicit
NO-GESTURE-BOT: goodwill gesture → handoff #555
SCOPE-SPOILER-RULES: spoiler_rules map limits responses
Flow MYBOXbot MBB-1 to MBB-8
Eight-step mystery lot bot flow.
MBB-1 Classify: bot_mybox_* intent detect
MBB-2 Context: product browse or order verify
MBB-3 MYBOX-MAP: rules value return spoiler scope
MBB-4 Guardrail: NO-SPOILER NO-RETURN NO-GESTURE
MBB-5 Respond: TPL-MYBOXbot grounded
MBB-6 Spoiler check: SCOPE-SPOILER-RULES filter
MBB-7 Handoff: missing disappointment u2192 #555
MBB-8 Log: intent box_sku tag mybox_bot
Example TPL-MYBOXbot-RULES
u201cLot [box_name]: [item_count_range] surprise items. Minimum guaranteed retail value [value_guarantee] u20ac. Categories: [categories_included]. Policy: [return_policy summary]. Exact content not disclosed before opening.u201d
TPL-MYBOXbot templates and touchpoints
Four essential templates.
TPL-MYBOXbot-RULES
Lot [box_name]. [item_count_range] items. Min value [value_guarantee] €. Exclusions: [exclusions]. Final sale: [return_policy]. Surprise preserved.
TPL-MYBOXbot-VALUE
Guaranteed retail value [value_guarantee] € minimum. Retail price indicated on each item packaging. Value disputes: describe the item, an agent will verify.
TPL-MYBOXbot-RETURN
Mystery lot policy: [return_policy map]. [Final sale: return not accepted except for proven missing or damaged item.] Questions after receipt: contact us with order number.
TPL-MYBOXbot-HANDOFF
Request [missing / disappointment / duplicate] forwarded to an agent. Order #[order_num], lot [box_name]. Delay [handoff_sla].
Touchpoints
Mystery lot PDP: bot_mybox_rules_pre chip
Surprise FAQ: bot_mybox_return_policy embed
Post-purchase tracking page: bot_mybox_missing_handoff trigger
Help center: bot embed MYBOX-MAP RAG spoiler filter
Edge cases and reroutes
Five cases outside tier 1 standard bot rules.
Client insists on content: NO-SPOILER-BOT redirect rules_pre
Return promised threat: NO-RETURN-PROMISE handoff #555 RETURN-01
Box subscription confusion: reroute bot box subscription #416
Box fixed content: #221 bundle not mystery
Imminent chargeback: handoff #555 FINAL-SALE-CLEAR
Bot does not refund or re-issue batch: gesture missing reship → agents #555 ops.
Essential mybox_bot KPIs
Five MYBOXbot steering metrics.
mybox_bot_spoiler_violation: bot revealed content, target 0
mybox_bot_rules_deflect: rules sessions without human ticket
mybox_bot_return_promise_violation: promised return off map, target 0
mybox_bot_value_accuracy: % value_guarantee correct audit
mybox_bot_handoff_rate: sessions → #555 agents
Monthly red team: 10 prompts "batch product list", "I will return if disappointed promise", "guaranteed value €150". Spoiler or promised return = guardrail violation.
MYBOXbot anti-patterns
Six common mistakes.
Spoiler content box: NO-SPOILER-BOT
Return promise final sale: NO-RETURN-PROMISE-BOT
Invented value: VALUE-GUARANTEE-BOT map
Direct bot gesture: NO-GESTURE-BOT handoff #555
Rules off map: MYBOX-MAP-GROUNDED
Bypassing spoiler_rules: SCOPE-SPOILER-RULES
MYBOXbot with Qstomy
Qstomy on Shopify: detect bot_mybox intent, MYBOX-MAP RAG, NO-SPOILER guardrail, value return cite, spoiler_rules filter, handoff #555 payload.
Pipeline: bot tier 1 rules → #555 missing gesture execute → AI governance #142 audit spoiler bot.
Explore AI support and request a demo.
Checklist, FAQ and going further
Checklist MYBOXbot (8 steps)
Sync MYBOX-MAP #555: RAG bot + spoiler_rules filter
Policy MYBOXBOT-SUP: 6 NO-SPOILER-BOT rules
8 intents bot_mybox_*: flow MBB-1 to MBB-8
4 templates TPL-MYBOXbot-*: RULES VALUE RETURN HANDOFF
PDP mystery lot chip: bot_mybox_rules_pre entry
Red team 10 prompts: spoiler return promised value
Handoff workflow #555: missing disappointment payload
Dashboard KPI: mybox_bot_* section 9
FAQ
Difference #555?
#555 = agents missing gesture return execute. #556 = bot tier 1 rules without spoiler.
Bot reveals content?
No. NO-SPOILER-BOT. SCOPE-SPOILER-RULES.
Return if disappointed?
TPL-MYBOXbot-RETURN return_policy map. Handoff if dispute.
Value guaranteed?
TPL-MYBOXbot-VALUE value_guarantee map only.
Going further
This week: sync MYBOX-MAP RAG bot, red team "lot product list", measure mybox_bot_spoiler_violation. Activate PDP mystery lot chip.
Enzo
July 1, 2026
