E-commerce
July 1, 2026
"The bot says my box contains 4 products whereas the map lists 3." "The AI promises a return router without checking the split shipment kit." "Chatbot routes to missing accessory #680 whereas it is a bundle pack." Three failures where a poorly calibrated incomplete pack bot invents components, reships without verification, or confuses MISSACC #679.
An e-commerce incomplete pack AI chatbot does not replace MISSBND agents (#681). It reads MISSBND-MAP, cites component_skus_manifest verify_steps_copy, guides split shipment kit and handoff reship refund warehouse to humans.
This guide #682 covers intents bot_miss_bnd_*, flow MISSBNDbot and KPI miss_bnd_bot. Bot pair of the playbook MISSBND (#681). AI use case: verify pack components and escalate without executing reship refund.
Summary
Why automate incomplete packs with a bot?
"Product 2 of the box is missing", "my kit is incomplete" and "where is the grinder of the coffee set?" come up as soon as the pack is unboxed. A calibrated bot cites MISSBND-MAP component_skus_manifest kit_packaging_type multiparcel_reroute_policy without invented components or promised entire pack return.
What the tier 1 bot resolves for incomplete packs
Component Manifest: component_labels_copy map
Verify guide: verify_steps_copy sub-packaging map
Split shipment kit: multiparcel fulfillments API map
Photo collect: photo_requirements_copy structured
Reship Escalation: handoff #681 payload verify outcome
Nventory estimates that a bundle manifest triage before reship reduces useless entire pack returns on targeted picking errors (Nventory, RMA 2026).
MISSBNDbot vs MISSBND #681, MISSACC #680, wrong item #186 and UPGRBND #663
Five contents, five distinct package and bundle models.
Quick matrix
#682 MISSBNDbot: bot tier 1 manifest verify split photo handoff
#681 MISSBND: agents reship refund warehouse MB-7
MISSACCbot #680: bot accessory distinct box multi-SKU pack
Wrong item #186: wrong SKU missing line distinct pack component
UPGRBND #663: modular upgrade pack distinct incomplete fulfillment
Pipeline: #682 bot manifest verify tier 1 → #681 agents reship partial refund WRONG186 MISSACC679.
Which bot_miss_bnd_* intents should be configured?
Eight incomplete bot pack intents mapped to typologies miss_bnd_* #681.
Eight bot_miss_bnd intents
bot_miss_bnd_manifest : component_skus_manifest map explain
bot_miss_bnd_verify : verify_steps_copy map guide
bot_miss_bnd_component : missing component confirm map
bot_miss_bnd_split_ship : kit_packaging_type split_ship API
bot_miss_bnd_wrong_comp : wrong component vs manifest map
bot_miss_bnd_photo : photo_requirements_copy collect
bot_miss_bnd_refund_info : partial_refund_policy explain map
bot_miss_bnd_handoff : missing confirmed reship → #681
Tier 1 auto : manifest, verify, split_ship, photo if MISSBND-MAP + bundle fulfillments lookup.
bot_miss_bnd_handoff component confirmed post-verify → agents #681 payload order_ref component photos.
How do I consume MISSBND-MAP #681?
The bot reads MISSBND-MAP #681: missbnd_program_id, bundle_parent_sku, component_skus_manifest, component_labels_copy, kit_packaging_type, verify_steps_copy, photo_requirements_copy, component_reship_skus, reship_sla_days, multiparcel_reroute_policy, partial_refund_policy, missacc679_reroute_policy, customer_communication_copy.
Lookup grounded
BUNDLE-FULFILL-CITE-BOT: bundle_parent_sku fulfillments API before respond
COMPONENT-MANIFEST-CITE-BOT: component_skus_manifest cite map only
VERIFY-CITE-BOT: verify_steps_copy before missing confirm
NO-COMPONENT-INVENT-BOT: no components outside map whitelist
NO-FULL-RETURN-PROMISE-BOT: no whole pack RMA before verify map
NO-RESHIP-EXECUTE-BOT: bot never launches reship alone handoff #681
NO-REFUND-EXECUTE-BOT: bot never executes refund partial_refund_policy explain only
MISSACC679-REROUTE-BOT: device box accessory u2192 #680 MISSACCbot distinct pack
WRONG186-REROUTE-BOT: wrong SKU u2192 #186 wrong item workflow
MISSBND681-HANDOFF-BOT: reship refund u2192 #681 agents MB-7
Alignment anti-hallucination (#123): manifest components = MISSBND-MAP whitelist only.
MISSBNDBOT-SUP policy in six rules
Six rules bot pack incomplete sure.
MISSBND-MAP-GROUNDED-BOT: manifest components from map only
BUNDLE-FULFILL-CITE-BOT: fulfillments API before split_ship respond
VERIFY-CITE-BOT: verify_steps_copy before missing confirm
NO-FULL-RETURN-PROMISE-BOT: no whole pack return promised before verify map
NO-RESHIP-EXECUTE-BOT: handoff #681 reship agents never bot alone
EXCEPTION-HANDOFF-BOT: reship refund WRONG186 MISSACC679 → #681 #186 #680
Flow MISSBNDbot MBB-1 to MBB-8
Eight-step flow incomplete bot pack.
MBB-1 Classify: bot_miss_bnd_* intent detect pack component missing
MBB-2 Collect: order_ref component name pack received items list
MBB-3 MISSBND-MAP: manifest verify reship multiparcel refund
MBB-4 Order lookup: email order API bundle_parent_sku fulfillments
MBB-5 Guardrail: COMPONENT VERIFY NO-COMPONENT-INVENT NO-RESHIP NO-REFUND-EXECUTE
MBB-6 Respond: TPL-MISSBNDbot grounded map manifest or split_ship
MBB-7 Handoff: missing confirmed photos → #681 reship refund payload
MBB-8 Log: intent missbnd_program_id tag miss_bnd_bot verify_complete handoff Y/N
Example TPL-MISSBNDbot-MANIFEST
“Pack [bundle_parent_sku map]: components [component_labels_copy map]. SKU [component_skus_manifest map]. [customer_communication_copy map]. Packaging [kit_packaging_type map]. COMPONENT-MANIFEST-CITE-BOT map only. Verification [verify_steps_copy map]. Confirm or photos [photo_requirements_copy map].”
TPL-MISSBNDbot and touchpoints templates
Four essential templates.
TPL-MISSBNDbot-MANIFEST
Program [missbnd_program_id] bundle [bundle_parent_sku API]: components [component_labels_copy map]. [component_skus_manifest map]. COMPONENT-MANIFEST-CITE-BOT.
TPL-MISSBNDbot-VERIFY
Before confirmation missing: [verify_steps_copy map]. Photos [photo_requirements_copy map]. VERIFY-CITE-BOT. NO-FULL-RETURN-PROMISE-BOT.
TPL-MISSBNDbot-SPLIT
Bundle [bundle_parent_sku] split_ship kit: [multiparcel_reroute_policy map fulfillments tracking]. Component may arrive in package 2. BUNDLE-FULFILL-CITE-BOT.
TPL-MISSBNDbot-HANDOFF
Component [component_labels map] confirmed missing post-verify. Recap [order_ref bundle SKU photos]. Team initiates reship [reship_sla_days map] days or refund [partial_refund_policy summary]. NO-RESHIP-EXECUTE-BOT MISSBND681-HANDOFF-BOT.
Touchpoints
PDP bundle content widget: bot_miss_bnd_manifest proactive
Box packaging QR insert: bot_miss_bnd_verify entry
Chat keyword incomplete box: bot_miss_bnd_component trigger
Post-delivery bundle email: bot_miss_bnd_manifest component list
Edge cases and reroutes
Five cases outside tier 1 bot pack incomplete standard.
Accessory box device only: MISSACC679-REROUTE-BOT #680 distinct component pack
Wrong component received: WRONG186-REROUTE-BOT #186 wrong SKU distinct missing
Modular upgrade pack: #664 UPGRBNDbot tier distinct fulfillment
Damaged package lost component: #182 carrier claim distinct picking
Customer insists on immediate reship: NO-RESHIP-EXECUTE-BOT verify photo handoff #681
Bot never triggers reship, refund, or pack return: MISSBND681-HANDOFF-BOT agents MB-7.
Essential bottom bound miss KPIs
Five MISSBNDbot monitoring metrics.
miss_bnd_bot_manifest_deflect: resolved split_ship verify without agent
miss_bnd_bot_manifest_cite_rate: COMPONENT-MANIFEST-CITE-BOT / bot_miss_bnd_manifest
miss_bnd_bot_verify_before_handoff_rate: VERIFY-CITE before handoff / total
miss_bnd_bot_reship_execute_violations: reship bot alone target audit 0
miss_bnd_bot_missacc_misroute_rate: routed #680 on pack / total low target
Target: miss_bnd_bot_reship_execute_violations 0 and miss_bnd_bot_manifest_deflect greater than 45%.
MISSBNDbot Anti-patterns
Five common incomplete bot pack errors.
Invented components: COMPONENT-MANIFEST-CITE-BOT component_skus_manifest map
Reship executed bot: NO-RESHIP-EXECUTE-BOT handoff #681 MB-7 only
Entire pack return promised: NO-FULL-RETURN-PROMISE-BOT reship component map
Confusing MISSACC #680: MISSACC679-REROUTE accessory box distinct pack
Ignoring split shipment kit: BUNDLE-FULFILL-CITE-BOT multiparcel before missing confirm
MISSBNDbot with Qstomy
Qstomy on Shopify: detect bot_miss_bnd intent, MISSBND-MAP RAG grounded, bundle fulfillments lookup, COMPONENT VERIFY cite, handoff #681 reship refund payload.
Pipeline: #682 bot manifest verify tier 1 → #681 agents reship partial refund WRONG186 MISSACC679 escalate.
Explore AI support and request a demo.
Checklist, FAQ and going further
MISSBNDbot Checklist (8 steps)
Sync MISSBND-MAP #681: RAG bot PDP pack widget QR insert
Policy MISSBNDBOT-SUP: 6 rules VERIFY NO-RESHIP NO-FULL-RETURN
8 intents bot_miss_bnd_*: flow MBB-1 to MBB-8
4 templates TPL-MISSBNDbot-*: MANIFEST VERIFY SPLIT HANDOFF
Bundle fulfillments API sync: split_ship kit_packaging_type bot agents
component_skus_manifest index: RAG components grounded audit
Red team 10 prompts: invented components reship bot return pack MISSACC confused
Dashboard KPI: miss_bnd_bot_* section 9
FAQ
Difference #681?
#681 = agents reship refund warehouse MB-7 escalate. #682 = bot tier 1 manifest verify split photo handoff.
Difference MISSACCbot #680?
#680 = accessory included box single product. #682 = SKU component pack multi-product bundle sold together.
Does the bot initiate the reshipment?
No. NO-RESHIP-EXECUTE-BOT TPL-MISSBNDbot-HANDOFF #681 component_reship_skus.
Kit split shipment bot?
TPL-MISSBNDbot-SPLIT multiparcel_reroute_policy fulfillments API. Component parcel 2 in transit possible.
Going further
This week: index MISSBND-MAP RAG components, embed PDP pack widget, red team reship bot standalone violations.
Enzo
July 1, 2026
