E-commerce
July 1, 2026
“The bot says to reset the device when it's a Bluetooth issue.” “The AI invents pairing steps that are missing from the guide map.” “Chatbot confuses proactive onboarding #179 with reactive sync ticket.” Three failures where a poorly calibrated companion app bot over-diagnoses hardware, invents steps, or mixes up troubleshoot #229.
An e-commerce companion app AI chatbot does not replace COMPAPP agents (#673). It reads COMPAPP-MAP, cites order email API, guides pairing_guide_url sync_troubleshoot_steps, and handoffs transfer account reset hardware to humans.
This guide #674 covers intents bot_comp_app_*, flow COMPAPPbot, and KPI comp_app_bot. Pairs bot with COMPAPP playbook (#673). AI use case: assist connection, synchronization, and connected product usage.
Summary
Why automate the companion app with a bot?
"How do I install the app?", "my device is not showing up" and "my data is no longer syncing" are frequent queries right after a connected product is delivered. A calibrated bot quotes COMPAPP-MAP app_store_urls pairing_guide_url sync_troubleshoot_steps permissions_required_copy without inventing steps or suggesting premature hardware resets.
What the tier 1 connected app bot resolves
Install guide: app_store_urls min_os_versions map
Account link: account_link_policy order email API
Pairing assist: pairing_guide_url pairing_method map
Sync restore: sync_troubleshoot_steps cite map
Usage basics: offline_mode_copy customer_communication map
Gorgias estimates that 25 to 35% of post-delivery IoT tickets concern install pairing sync issues that can be resolved by a grounded bot without an agent (Gorgias, CS 2026).
COMPAPPbot vs COMPAPP #673, onboarding #179, troubleshoot #229 and PRODUPD #672
Five contents, five distinct connected product layers.
Quick Matrix
#674 COMPAPPbot: bot tier 1 install pair sync usage handoff
#673 COMPAPP: agents transfer account reset hardware CA-7
Onboarding #179: proactive bot setup D+0 distinct reactive app tickets
Troubleshoot #229: hardware breakdown diagnostic distinct app ecosystem
PRODUPD #672: bot firmware version distinct account pairing
Pipeline: #674 bot install pair sync tier 1 → #673 agents transfer reset hardware escalate.
Which bot_comp_app_* intents should be configured?
Eight companion app bot intents mapped to comp_app_* typologies #673.
Eight bot_comp_app intents
bot_comp_app_install: app_store_urls min_os_versions map
bot_comp_app_account: account_link_policy order email API
bot_comp_app_pairing: pairing_guide_url pairing_method map
bot_comp_app_sync: sync_troubleshoot_steps cite map
bot_comp_app_permissions: permissions_required_copy map
bot_comp_app_usage: offline_mode_copy usage basics map
bot_comp_app_login: reset tier 1 access or handoff map
bot_comp_app_handoff: transfer hardware account → #673
Tier 1 auto: install, account, pairing, sync, permissions if COMPAPP-MAP + order lookup.
bot_comp_app_handoff comp_app_transfer sync persist hardware → agents #673 payload order_ref device.
How do I consume COMPAPP-MAP #673?
The bot reads COMPAPP-MAP #673: compapp_program_id, parent_product_skus, app_name, app_store_urls, min_os_versions, account_required, account_link_policy, pairing_method, pairing_guide_url, sync_troubleshoot_steps, permissions_required_copy, offline_mode_copy, customer_communication_copy.
Lookup grounded
ORDER-API-CITE-BOT : API order email before account respond
PAIRING-GUIDE-CITE-BOT : pairing_guide_url steps cite map only
SYNC-STEPS-CITE-BOT : sync_troubleshoot_steps cite map only
PERMISSIONS-CITE-BOT : permissions_required_copy cite map
NO-PAIRING-INVENT-BOT : no pairing steps outside map whitelist
ONBOARD179-REROUTE-BOT : proactive setup Day+0 → #179 separate reactive onboarding
TRB229-REROUTE-BOT : hardware breakdown post-sync fail → #229 troubleshoot diagnostic
COMPAPP673-HANDOFF-BOT : hardware reset transfer → #673 CA-7 agents
Alignment anti-hallucination (#123): pairing sync permissions = COMPAPP-MAP whitelist only.
COMPAPPBOT-SUP six-rule policy
Six safe companion app bot rules.
COMPAPP-MAP-GROUNDED-BOT: pairing sync permissions from map only
ORDER-API-CITE-BOT: order API email before account_link respond
PAIRING-GUIDE-CITE-BOT: pairing_guide_url steps cite map only
SYNC-STEPS-CITE-BOT: sync_troubleshoot_steps cite map only
NO-HARDWARE-RESET-BOT: do not reset device before sync steps exhausted map
EXCEPTION-HANDOFF-BOT: account hardware transfer → #673 CA-7
Flow COMPAPPbot CAB-1 to CAB-8
Eight-step companion app bot flow.
CAB-1 Classify: bot_comp_app_* intent detect post-delivery email app
CAB-2 Collect: order_ref device OS app version question
CAB-3 COMPAPP-MAP: app stores pairing sync permissions account
CAB-4 Order lookup: email order API device SKU map
CAB-5 Guardrail: ORDER-CITE PAIRING SYNC PERMISSIONS NO-HARDWARE-RESET
CAB-6 Respond: TPL-COMPAPPbot grounded map API
CAB-7 Handoff: transfer reset hardware → #673
CAB-8 Log: intent compapp_program_id tag comp_app_bot paired Y/N
Example TPL-COMPAPPbot-PAIRING
“App [app_name map] device [parent_product_skus map]: pairing [pairing_method map]. Guide: [pairing_guide_url map]. Permissions: [permissions_required_copy map]. PAIRING-GUIDE-CITE-BOT map only. NO-PAIRING-INVENT-BOT.”
TPL-COMPAPPbot templates and touchpoints
Four essential templates.
TPL-COMPAPPbot-INSTALL
Program [compapp_program_id]: app [app_name map] [app_store_urls map]. Min OS [min_os_versions map]. Account: [account_required Y/N map]. [customer_communication_copy map.]
TPL-COMPAPPbot-PAIRING
Device [parent API SKU]: [pairing_method map]. Steps: [pairing_guide_url map]. PERMISSIONS-CITE-BOT: [permissions_required_copy map]. PAIRING-GUIDE-CITE-BOT.
TPL-COMPAPPbot-SYNC
Sync [app_name map]: [sync_troubleshoot_steps map]. SYNC-STEPS-CITE-BOT. [If failure after steps: TRB229-REROUTE-BOT hardware check.]
TPL-COMPAPPbot-HANDOFF
Request [phone transfer / account reset / hardware failure] forwarded to team. Summary [order_ref device OS question]. Agent SLA [handoff_sla map].
Touchpoints
Post-delivery email app CTA: bot_comp_app_install widget proactive
QR onboarding packaging: bot_comp_app_pairing entry
Chat keyword app not syncing: bot_comp_app_sync trigger
pairing_guide_url landing: bot_comp_app_permissions assist
Edge cases and reroutes
Five cases outside tier 1 companion app bot standard.
Proactive setup Day 0: ONBOARD179-REROUTE-BOT distinct reactive ticket
Confirmed hardware failure: TRB229-REROUTE-BOT after sync steps exhausted
Firmware app update: #672 PRODUPDbot firmware distinct pairing
QR scan pairing fail: #590 QRSCANbot if QR onboarding map
New phone transfer: bot_comp_app_handoff #673 comp_app_transfer policy
Bot never resets device without sync_troubleshoot_steps map exhausted: NO-HARDWARE-RESET-BOT.
Essential comp_app_bot KPIs
Five COMPAPPbot management metrics.
comp_app_bot_pair_deflect: pairing resolved without agent
comp_app_bot_sync_restore_deflect: sync OK without agent
comp_app_bot_order_cite_rate: % ORDER-API-CITE map responses
comp_app_bot_pairing_cite_rate: PAIRING-GUIDE-CITE / bot_comp_app_pairing
comp_app_bot_pairing_invent_violations: steps outside map target audit 0
Target: comp_app_bot_pairing_invent_violations 0 and comp_app_bot_pair_deflect greater than 55%.
COMPAPPbot anti-patterns
Five common companion app bot mistakes.
Invented pairing steps: PAIRING-GUIDE-CITE-BOT pairing_guide_url map
Premature hardware reset: NO-HARDWARE-RESET-BOT sync steps first
Account without order lookup: ORDER-API-CITE-BOT email order API
Confusing troubleshoot #229: TRB229-REROUTE after sync steps exhausted only
Improvised sync steps: SYNC-STEPS-CITE-BOT sync_troubleshoot_steps map
COMPAPPbot with Qstomy
Qstomy on Shopify: detect bot_comp_app intent, COMPAPP-MAP RAG grounded, order email lookup, PAIRING SYNC cite, handoff #673 transfer hardware payload.
Pipeline: #674 bot install pair sync tier 1 → #673 agents transfer reset hardware escalate.
Explore AI support and request a demo.
Checklist, FAQ and going further
COMPAPPbot Checklist (8 steps)
Sync COMPAPP-MAP #673: RAG bot email post-delivery widget
Policy COMPAPPBOT-SUP: 6 rules PAIRING SYNC NO-HARDWARE-RESET
8 intents bot_comp_app_*: flow CAB-1 to CAB-8
4 templates TPL-COMPAPPbot-*: INSTALL PAIRING SYNC HANDOFF
Order email API sync: Shopify metafield bot agents
pairing_guide_url index: RAG steps grounded audit
Red team 10 prompts: invented steps hardware reset onboarding confused
Dashboard KPI: comp_app_bot_* section 9
FAQ
Difference #673?
#673 = agents transfer account reset hardware escalate CA-7. #674 = bot tier 1 install pair sync usage handoff.
Difference onboarding #179?
#179 = proactive setup D+0 email sequence. #674 = reactive tickets app pairing sync.
Bot sync fails?
TPL-COMPAPPbot-SYNC steps map. Persistent → TRB229-REROUTE or #673 handoff.
Bot reset device?
No. NO-HARDWARE-RESET-BOT sync_troubleshoot_steps exhausted then handoff if needed.
Going further
This week: index COMPAPP-MAP RAG, embed email post-delivery app widget, red team pairing invented steps bot.
Enzo
July 1, 2026
