E-commerce
July 1, 2026
"The bot is suggesting a belt that is incompatible with my revision." "The AI is opening a warranty claim when the brush is simply worn out." "The chatbot is ignoring my intensive usage for the replacement frequency." Three failures where a poorly calibrated wear part bot invents references, confuses spare #343, and mixes up normal wear maps.
An e-commerce wear parts AI chatbot does not replace WEARPART agents (#667). It reads WEARPART-MAP, cites the parent product order API, collects usage intensity, and hands off warranty_dispute, oos, and complex install issues to humans.
This guide #668 covers intents bot_wear_part_*, flow WEARPARTbot, and KPI wear_part_bot. Companion bot to the WEARPART playbook (#667). AI use case: identify usage patterns and the correct product maintenance reference.
Summary
Why automate wear parts with a bot?
"My brush is worn out, is this normal?", "which reference for heavy-duty use?" and "how to replace the pad?" are common post-device purchase and maintenance manual questions. A calibrated bot cites WEARPART-MAP wear_part_skus usage_intensity_map normal_wear_copy without opening a warranty claim or inventing reference numbers.
What the tier 1 maintenance bot resolves
Model identify: parent_product_skus order API map
Usage collect: light normal heavy usage_intensity map
Which ref: wear_part_skus compat_rules cite map
Normal wear: normal_wear_copy warranty_excluded_wear map
Install guide: install_guide_url reorder_url map
Gorgias estimates that 18% to 28% of wear part maintenance tickets concern model reference and normal wear listable and resolvable by a grounded bot without an agent (Gorgias, CS 2026).
WEARPARTbot vs WEARPART #667, spare bot #344, consum #666 and diagnostic #342
Five contents, five distinct part maintenance types.
Quick matrix
#668 WEARPARTbot: bot tier 1 model usage ref normal wear install handoff
#667 WEARPART: agents warranty_dispute oos install escalate WP-7
Spare bot #344: spare parts bot breakdown distinct wear cycle
Consum bot #666: consumable bot filter cartridge distinct pad brush
Diagnostic #342: fail_* breakdown qualification before wear vs repair
Pipeline: #668 bot model usage ref tier 1 → #667 agents warranty dispute oos escalate.
Which bot_wear_part_* intents should be configured?
Eight wear part bot intents mapped to wear_part_* typologies #667.
Eight bot_wear_part intents
bot_wear_part_model : parent product order API identify map
bot_wear_part_usage : usage_intensity light normal heavy collect
bot_wear_part_which_ref : wear_part_skus compat_rules cite map
bot_wear_part_normal_wear : normal_wear_copy warranty_excluded_wear map
bot_wear_part_frequency : replacement_interval_usage usage_intensity map
bot_wear_part_install : install_guide_url guide replacement map
bot_wear_part_reorder : reorder_url guide repurchase map
bot_wear_part_handoff : warranty_dispute oos complex → #667
Tier 1 auto: model, usage, which_ref, normal_wear, frequency if WEARPART-MAP + parent lookup.
bot_wear_part_handoff wear_part_warranty_dispute wear_part_oos → agents #667 payload order_ref wear_sku.
How to consume WEARPART-MAP #667?
The bot reads WEARPART-MAP #667: wearpart_program_id, parent_product_skus, wear_part_skus, wear_part_type, replacement_interval_usage, usage_intensity_map, normal_wear_copy, warranty_excluded_wear, install_guide_url, compat_rules, reorder_url, customer_communication_copy.
Lookup grounded
MODEL-API-CITE-BOT: parent product order API before wear ref
USAGE-INTENSITY-ASK-BOT: collect light normal heavy before FREQ respond
WEAR-SKU-CITE-BOT: wear_part_skus cite map only
NORMAL-WEAR-CITE-BOT: normal_wear_copy before warranty route
FREQ-CITE-BOT: replacement_interval_usage usage_intensity map only
SPARE343-REROUTE-BOT: broken part breakdown → #343 spare distinct wear
CONSUM665-REROUTE-BOT: consumable → #665 CONSUM filters distinct pad
WEARPART667-HANDOFF-BOT: warranty oos exception → #667 agents WP-7
Alignment counter-hallucination (#123): SKU freq wear = WEARPART-MAP whitelist only.
WEARPARTBOT-SUP Policy in six rules
Six rules bot wear part maintenance sure.
WEARPART-MAP-GROUNDED-BOT: SKU freq wear from map only
MODEL-API-CITE-BOT: parent product order API before ref respond
USAGE-INTENSITY-ASK-BOT: collect usage before frequency cite
NORMAL-WEAR-CITE-BOT: normal_wear_copy warranty_excluded_wear before warranty
WEAR-SKU-CITE-BOT: wear_part_skus cite map only reorder
EXCEPTION-HANDOFF-BOT: warranty_dispute oos complex → #667 WP-7
Flow WEARPARTbot WPB-1 to WPB-8
Eight-step wearing part maintenance bot flow.
WPB-1 Classify : bot_wear_part_* intent detect post-purchase maintenance
WPB-2 Collect : order_ref model usage_intensity wear question
WPB-3 WEARPART-MAP : wear_part_skus freq normal_wear install reorder
WPB-4 Model lookup : parent product order API line SKUs map
WPB-5 Guardrail : MODEL-CITE USAGE-ASK NORMAL-WEAR WEAR-SKU FREQ
WPB-6 Respond : TPL-WEARPARTbot grounded map API
WPB-7 Handoff : warranty_dispute oos complex → #667
WPB-8 Log : intent wearpart_program_id tag wear_part_bot reorder_click Y/N
Example TPL-WEARPARTbot-REF
“Device [parent_product_skus map API] usage [usage_intensity map]: wearing part [wear_part_type map] reference [wear_part_skus map]. [normal_wear_copy map.] Frequency: [replacement_interval_usage map usage_intensity]. Guide: [install_guide_url map]. Reorder: [reorder_url map].”
TPL-WEARPARTbot and touchpoints templates
Four essential templates.
TPL-WEARPARTbot-MODEL
Program [wearpart_program_id]: device identified [parent API order lookup]. [customer_communication_copy map.] Daily usage: light, normal or heavy? USAGE-INTENSITY-ASK-BOT.
TPL-WEARPARTbot-REF
Model [parent API] usage [intensity]: [wear_part_skus map]. Compatibility: [compat_rules map]. WEAR-SKU-CITE-BOT map only. Reorder: [reorder_url map].
TPL-WEARPARTbot-NORMAL
[normal_wear_copy map]. Normal wear [wear_part_type map]. Wear warranty: [warranty_excluded_wear Y/N map]. NORMAL-WEAR-CITE-BOT. [If suspected breakdown: diagnostics #342 handoff map.]
TPL-WEARPARTbot-HANDOFF
Request [warranty dispute / stockout / complex install] forwarded to team. Summary [order_ref model usage wear_sku question]. Agent delay [handoff_sla map].
Touchpoints
PDF maintenance guide widget: bot_wear_part_which_ref proactive
Email maintenance reminder: bot_wear_part_frequency entry
Chat keyword worn brush: bot_wear_part_normal_wear trigger
reorder_url landing: bot_wear_part_model assist
Edge cases and reroutes
Five cases outside tier 1 bot standard wear part.
Broken part breakdown: SPARE343-REROUTE-BOT #344 spare bot distinct wear cycle
Consumable consumed: CONSUM665-REROUTE-BOT #666 distinct wear brush pad
Uncertain breakdown: #342 fail_* before wear vs repair route
Wear warranty dispute: bot_wear_part_handoff #667 warranty_dispute escalate
Complex install: partner installation handoff map
Bot never creates warranty file: NORMAL-WEAR-CITE-BOT then handoff #667 if dispute.
Essential wear_part_bot KPIs
Five WEARPARTbot management metrics.
wear_part_bot_ref_deflect: which_ref resolved without agent
wear_part_bot_model_cite_rate: % responses MODEL-API-CITE map
wear_part_bot_usage_collect_rate: usage intensity collected / sessions freq
wear_part_bot_reorder_click_rate: clicks reorder_url / bot sessions
wear_part_bot_warranty_misroute_rate: bot warranty on normal wear target 0
Target: wear_part_bot_warranty_misroute_rate 0 and wear_part_bot_ref_deflect greater than 48%.
WEARPARTbot anti-patterns
Five common wear part bot errors.
Invented reference: WEAR-SKU-CITE-BOT wear_part_skus map
Warranty on normal wear: NORMAL-WEAR-CITE-BOT warranty_excluded_wear first
Ref without model lookup: MODEL-API-CITE-BOT parent product API
Frequency without usage: USAGE-INTENSITY-ASK-BOT before FREQ-CITE
Confusing spare #343: SPARE343-REROUTE breakdown distinct from wear cycle
WEARPARTbot with Qstomy
Qstomy on Shopify: detect bot_wear_part intent, WEARPART-MAP RAG grounded, parent product order lookup, usage intensity collect, handoff #667 warranty oos payload.
Pipeline: #668 bot model usage ref tier 1 → #667 agents warranty dispute oos escalate.
Explore AI support and request a demo.
Checklist, FAQ and going further
Checklist WEARPARTbot (8 steps)
Sync WEARPART-MAP #667: RAG bot user manual widget
Policy WEARPARTBOT-SUP: 6 rules MODEL-CITE USAGE-ASK NORMAL-WEAR
8 intents bot_wear_part_*: flow WPB-1 to WPB-8
4 templates TPL-WEARPARTbot-*: MODEL REF NORMAL HANDOFF
Parent device API sync: order metafield Shopify bot agents
Usage intensity flow: WPB-2 collect before FREQ respond
Red team 10 prompts: invented ref warranty wear spare confused
Dashboard KPI: wear_part_bot_* section 9
FAQ
Difference #667?
#667 = agents warranty_dispute oos install escalate WP-7. #668 = bot tier 1 model usage ref normal wear handoff.
Bot opens warranty?
No. NORMAL-WEAR-CITE-BOT warranty_excluded_wear map. Dispute → #667 agents.
Why collect usage?
USAGE-INTENSITY-ASK-BOT: replacement_interval_usage varies light normal heavy map.
Difference spare bot #344?
#344 = spare parts breakdown repair. #668 = normal wear maintenance cycle.
Going further
This week: index WEARPART-MAP RAG, embed user manual widget, red team normal wear warranty bot.
Enzo
July 1, 2026
