E-commerce
July 1, 2026
"The bot offers a module incompatible with my base revision." "The AI invents benefits out of map to push the extension." "Chatbot confuses shell accessory #350 and extension sensor module." Three failures where a poorly calibrated additional module bot over-sells, invents compatibility, or mixes up generic cross-sell #152.
An e-commerce additional modules AI chatbot does not replace ADDON agents (#669). It reads ADDON-MAP, references the base product order API, explains benefit_copy compat_rules, and hands off wrong_compat stack install complex to humans.
This guide #670 covers intents bot_addon_*, flow ADDONbot, and KPI addon_bot. Bot pair of the playbook ADDON (#669). AI use case: explaining compatibility and benefits in assisted sales without pressure.
Summary
Why automate add-on modules with bots?
"Is this module compatible with my database?", "what does the extension bring me?" and "can I add it after my purchase?" are frequent pre and post-purchase database questions. A calibrated bot cites ADDON-MAP addon_module_skus benefit_copy compat_rules without invented promises or forced checkouts.
What the tier 1 extension bot resolves
Compat check: compat_rules database API map
Benefit explain: benefit_copy customer_communication map
Which module: addon_module_skus for database map
Post-purchase: post_purchase_addon_allowed policy map
Purchase guide: addon_purchase_url link map
Gorgias estimates that 20 to 30% of pre-purchase extension tickets concern compatibility and benefits that can be resolved by a grounded bot without an agent (Gorgias, CS 2026).
ADDONbot vs ADDON #669, accessory bot #351, cross-sell #152 and UPGRBND #664
Five pieces of content, five distinct extension and upsell models.
Quick matrix
#670 ADDONbot: bot tier 1 compat benefit purchase handoff
#669 ADDON: agents wrong_compat stack install escalate AO-7
Accessory bot #351: accessory bot shell filter distinct module capacity
Cross-sell #152: generic recommendation timing distinct addon compat map
UPGRBND #664: progressive pack tier distinct extension module
Pipeline: #670 bot compat benefit tier 1 → #669 agents wrong compat stack install escalate.
Which bot_addon_* intents should be configured?
Eight additional module bot intents mapped to addon_* typologies #669.
Eight bot_addon intents
bot_addon_compat: compat_rules base API cite map
bot_addon_benefit: benefit_copy added capabilities map
bot_addon_which_module: addon_module_skus for base map
bot_addon_post_purchase: post_purchase_addon_allowed policy map
bot_addon_stack: stack_rules combinable modules map
bot_addon_purchase: addon_purchase_url buying guide map
bot_addon_install: install_guide_url simple tier 1 map
bot_addon_handoff: wrong_compat stack install complex → #669
Tier 1 auto: compat, benefit, which_module, post_purchase, purchase if ADDON-MAP + base lookup.
bot_addon_handoff addon_wrong_compat stack max install complex → agents #669 payload order_ref addon_sku.
How to consume ADDON-MAP #669?
The bot reads ADDON-MAP #669: addon_program_id, base_product_skus, addon_module_skus, module_type, benefit_copy, compat_rules, stack_rules, post_purchase_addon_allowed, addon_purchase_url, install_guide_url, customer_communication_copy, forbidden_addon_phrases.
Lookup grounded
BASE-API-CITE-BOT: base product order API before compat respond
BENEFIT-CITE-BOT: benefit_copy map only, no invented promise
COMPAT-CITE-BOT: compat_rules stack_rules cite map only
ADDON-SKU-CITE-BOT: addon_module_skus cite map only
NO-PRESSURE-ADDON-BOT: forbidden_addon_phrases blacklist map
ACC351-REROUTE-BOT: simple accessory → #351 accessory bot distinct extension
INCOMPAT483-REROUTE-BOT: configurator block → #484 incompat bot combo excludes
ADDON669-HANDOFF-BOT: wrong_compat stack install → #669 agents AO-7
Anti-hallucination alignment (#123): compat benefit SKU = ADDON-MAP whitelist only.
ADDONBOT-SUP policy in six rules
Six bot rules for safe assisted sales add-on module.
ADDON-MAP-GROUNDED-BOT: SKU compat benefit from map only
BASE-API-CITE-BOT: base product order API before compat module
BENEFIT-CITE-BOT: benefit_copy cite map not invented capacity
COMPAT-CITE-BOT: compat_rules stack_rules cite map only
PURCHASE-GUIDE-BOT: addon_purchase_url link not forced checkout bot
EXCEPTION-HANDOFF-BOT: wrong_compat stack install complex → #669 AO-7
Flow ADDONbot AOB-1 to AOB-8
Flow eight steps bot additional module.
AOB-1 Classify: bot_addon_* intent detect PDP post-base email
AOB-2 Collect: order_ref base model addon question
AOB-3 ADDON-MAP: modules compat benefit stack purchase install
AOB-4 Base lookup: base product order API line SKUs map
AOB-5 Guardrail: BASE-CITE BENEFIT COMPAT NO-PRESSURE PURCHASE-GUIDE
AOB-6 Respond: TPL-ADDONbot grounded map API
AOB-7 Handoff: wrong_compat stack install complex → #669
AOB-8 Log: intent addon_program_id tag addon_bot purchase_click Y/N
Example TPL-ADDONbot-BENEFIT
"Base [base_product_skus map API]: module [addon_module_skus map] compatible [Y/N compat_rules map]. Benefits: [benefit_copy map]. Purchase: [addon_purchase_url map]. NO-PRESSURE-ADDON-BOT: information only."
TPL-ADDONbot templates and touchpoints
Four essential templates.
TPL-ADDONbot-COMPAT
Program [addon_program_id]: base [base API order lookup]. Module [addon_module_skus map]: compatible [compat_rules map]. Stack modules owned: [stack_rules map]. COMPAT-CITE-BOT.
TPL-ADDONbot-BENEFIT
Module [addon_module_skus map] type [module_type map]: [benefit_copy map]. [customer_communication_copy map]. BENEFIT-CITE-BOT map only. Link: [addon_purchase_url map].
TPL-ADDONbot-POSTPURCHASE
Base order [order_ref API]: compatible modules [addon_module_skus map]. Post-purchase: [post_purchase_addon_allowed Y/N map]. PURCHASE-GUIDE-BOT addon_purchase_url.
TPL-ADDONbot-HANDOFF
Request [poor compatibility / max stack / complex install] escalated to team. Summary [order_ref base addon_sku question]. Agent response time [handoff_sla map].
Touchpoints
PDP base widget extension: bot_addon_benefit proactive
Email post-base addon CTA: bot_addon_post_purchase entry
Chat keyword module compatible: bot_addon_compat trigger
addon_purchase_url landing: bot_addon_which_module assist
Edge cases and reroutes
Five cases outside tier 1 bot standard additional module.
Optional accessory: ACC351-REROUTE-BOT #351 distinct capacity extension
Block configurator: INCOMPAT483-REROUTE-BOT combo excludes map
Scalable tier pack: #664 UPGRBNDbot sequence tier distinct addon
Max stack reached: bot_addon_handoff #669 stack exception policy
Complex install: partner installation handoff map
Bot never creates module order: addon_purchase_url checkout or agents #669 if exception.
Essential bot addon KPIs
Five ADDONbot management metrics.
addon_bot_compat_deflect: compat benefit resolved without agent
addon_bot_base_cite_rate: % BASE-API-CITE map responses
addon_bot_benefit_cite_rate: % BENEFIT-CITE map responses
addon_bot_purchase_click_rate: addon_purchase_url clicks / bot sessions
addon_bot_benefit_invent_violations: promise out of map target audit 0
Target: addon_bot_benefit_invent_violations 0 and addon_bot_compat_deflect greater than 45%.
ADDONbot anti-patterns
Five common add-on module bot errors.
Invented benefit: BENEFIT-CITE-BOT benefit_copy map only
Compat without base lookup: BASE-API-CITE-BOT order base API
Immediate purchase pressure: NO-PRESSURE-ADDON-BOT forbidden_addon_phrases
Confusing accessory #351: ACC351-REROUTE distinct shell filter module
Forced bot checkout: PURCHASE-GUIDE-BOT addon_purchase_url not bot order
ADDONbot with Qstomy
Qstomy on Shopify: detect bot_addon intent, ADDON-MAP RAG grounded, base product order lookup, BENEFIT COMPAT cite, handoff #669 wrong_compat stack payload.
Pipeline: #670 bot compat benefit tier 1 → #669 agents wrong compat stack install escalate.
Explore AI support and request a demo.
Checklist, FAQ and going further
ADDONbot Checklist (8 steps)
Sync ADDON-MAP #669: RAG bot PDP base post-base widget
Policy ADDONBOT-SUP: 6 rules BENEFIT-CITE COMPAT PURCHASE-GUIDE
8 intents bot_addon_*: flow AOB-1 to AOB-8
4 templates TPL-ADDONbot-*: COMPAT BENEFIT POSTPURCHASE HANDOFF
Base product API sync: order metafield Shopify bot agents
forbidden_addon_phrases: blacklist red team pressure audit
Red team 10 prompts: invented benefit compat without base accessory confused
KPI Dashboard: addon_bot_* section 9
FAQ
Difference #669?
#669 = wrong_compat agents stack install escalate AO-7. #670 = bot tier 1 compat benefit purchase handoff without pressure.
Does the bot take a module order?
No. PURCHASE-GUIDE-BOT addon_purchase_url purchase link. Exception → #669 agents.
Difference cross-sell #152?
#152 = generic recommendation timing. #670 = addon compat benefit map linked to base product.
Difference accessory bot #351?
#351 = optional accessory compat. #670 = capacity extension module stack rules map.
Going further
This week: index ADDON-MAP RAG, embed PDP base extension widget, red team invented benefit compat bot.
Enzo
July 1, 2026
