E-commerce
July 1, 2026
"The bot says compatible when my OS is too old." "The AI invents 8 GB RAM minimum missing from the map." "Chatbot confuses accessory fitment and product WiFi specs." Three failures where a badly calibrated technical prerequisites bot promises compatibility, invents specs, or routes to MULTIMDL instead of techreq.
An e-commerce technical prerequisites AI chatbot does not replace TECHREQ agents (#727). It reads TECHREQ-MAP, guides compat_wizard_steps, cites minimum_requirements, and hands off incompatible postbuy to humans.
This guide #728 covers intents bot_techreq_*, flow TECHREQbot, and KPI techreq_bot. Pair bot of the TECHREQ playbook (#727). AI use case: validate customer setup before ordering without invented compat or off-map specs.
Summary
Why automate technical prerequisites with a bot?
"Is my PC OK?", "which power outlet?" and "does it work without fiber?" arrive on the PDP specs tab and widget compat wizard. A calibrated bot cites TECHREQ-MAP hardware_requirements network_requirements without OK compat without wizard complete or invented specs.
What the bot resolves tier 1 technical prerequisites
Specs explain: minimum_requirements_summary SPEC-CITE map
Compat wizard: compat_wizard_steps collect structured
Hardware software: hardware_requirements software_requirements cite map
Network power space: network_requirements power_electrical_specs map
Alternative SKU: alternative_sku_ids recommend if not compatible map
Baymard observes that clarifying product constraints on the PDP reduces technical shopping cart abandonment (Baymard, product page 2026). Without a grounded bot, AI amplifies false compat or invented specs.
TECHREQbot vs TECHREQ #727, MULTIMDLbot #686, MANDINSTbot #726 and COMPAPP #674
Six contents, six distinct compatibility moments.
Quick Matrix
#728 TECHREQbot: bot tier 1 specs wizard compat alt handoff
#727 TECHREQ: agents postbuy incompatible alternative return escalate
MULTIMDLbot #686: fitment distinct parent model specs customer environment
MANDINSTbot #726: mandatory install post-purchase distinct pre-buy prerequisite
COMPAPPbot #674: app setup post-purchase distinct minimum OS pre-buy
CHRGCBLbot #616: wattage port cable distinct global product specs
Pipeline: #728 bot compat check tier 1 → #727 agents postbuy return alternative escalate.
Which bot_techreq_* intents should be configured?
Eight bot technical prerequisite intents mapped to techreq_* typologies #727.
Eight bot_techreq intents
bot_techreq_specs : minimum_requirements_summary SPEC-CITE map
bot_techreq_hardware : hardware_requirements cite map
bot_techreq_software : software_requirements cite map
bot_techreq_network_power : network power space specs map
bot_techreq_compat_wizard : compat_wizard_steps collect verdict
bot_techreq_alternative : alternative_sku_ids recommend map
bot_techreq_prebuy_gate : block checkout hint if not compatible map
bot_techreq_handoff : postbuy incompatible return → #727
Tier 1 auto: specs, hardware, software, network, compat_wizard if TECHREQ-MAP active + guardrails.
bot_techreq_handoff postbuy incompatible return → agents #727 payload sku wizard verdict.
How to consume TECHREQ-MAP #727?
The bot reads TECHREQ-MAP #727 : techreq_program_id, eligible_skus, hardware_requirements, software_requirements, network_requirements, power_electrical_specs, space_environment_specs, minimum_requirements_summary, compat_wizard_steps, alternative_sku_ids, customer_communication_copy.
Lookup grounded
SPEC-CITE-BOT : minimum_requirements cite map verbatim
WIZARD-GATE-BOT : compat_wizard_steps complete before compat OK
NO-COMPAT-PROMISE-BOT : not compatible confirmed without wizard map
NO-SPEC-INVENT-BOT : specs whitelist TECHREQ-MAP only
MULTIMDL686-REROUTE-BOT : model fitment → #686 MULTIMDLbot distinct environment specs
MANDINST726-REROUTE-BOT : post-purchase install → #726 distinct pre-buy prerequisites
ALT-SKU-CITE-BOT : alternative_sku_ids cite if not compatible map
TECHREQ727-HANDOFF-BOT : postbuy return → #727 TR-7 agents
Alignment anti-hallucination (#123) : compat specs = TECHREQ-MAP whitelist only.
TECHREQBOT-SUP policy in six rules
Six bot rules technical prerequisites responsible.
TECHREQ-MAP-GROUNDED-BOT: minimum specs from map only
SPEC-CITE-BOT: minimum_requirements cite confirmed SKU
WIZARD-GATE-BOT: compat_wizard_steps before OK map verdict
NO-COMPAT-PROMISE-BOT: no compatible bot without complete wizard
NO-SPEC-INVENT-BOT: no RAM OS WiFi invented outside map
PREBUY-CONTEXT-ONLY-BOT: tier 1 pre-purchase handoff postbuy #727
Flow TECHREQbot TRB-1 to TRB-8
Eight-step flow technical prerequisites bot.
TRB-1 Classify: bot_techreq_* intent detect PDP wizard widget chat
TRB-2 Collect: sku setup client wizard inputs
TRB-3 TECHREQ-MAP: hardware software network power space alt
TRB-4 Wizard run: compat_wizard_steps structured compare specs
TRB-5 Guardrail: SPEC WIZARD NO-COMPAT NO-SPEC-INVENT MULTIMDL HANDOFF
TRB-6 Respond: TPL-TECHREQbot grounded customer_communication_copy
TRB-7 Handoff or close: postbuy incompatible alt recommend close
TRB-8 Log: intent techreq_program_id tag techreq_bot spec_cited wizard_complete Y/N
Example TPL-TECHREQbot-COMPAT
“ [sku map] specs [minimum_requirements_summary map.] Your setup [wizard inputs]: [compatible / not compatible / missing data map.] WIZARD-GATE-BOT SPEC-CITE-BOT. [If no: alternative [alternative_sku_ids map.] ALT-SKU-CITE-BOT.] ”
TPL-TECHREQbot and touchpoints templates
Four essential templates.
TPL-TECHREQbot-SPECS
Program [techreq_program_id] [sku map] : [minimum_requirements_summary map.] Hardware [hardware_requirements map.] Software [software_requirements map.] SPEC-CITE-BOT.
TPL-TECHREQbot-COMPAT
Setup [wizard inputs map] vs specs [minimum_requirements_summary map] : [verdict map.] WIZARD-GATE-BOT NO-COMPAT-PROMISE-BOT if incomplete.
TPL-TECHREQbot-ALT
Insufficient specs: alternative [alternative_sku_ids map PDP link.] [minimum_requirements_summary alt map.] ALT-SKU-CITE-BOT.
TPL-TECHREQbot-HANDOFF
Request [incompatible postbuy return / specs dispute] transmitted to team. Recap [order_ref sku wizard verdict]. TECHREQ727-HANDOFF-BOT.
Touchpoints
PDP specs tab widget: proactive bot_techreq_specs
Compat wizard embed: bot_techreq_compat_wizard entry
Checkout pre-buy chip: bot_techreq_prebuy_gate hint
Purchased incompatible keyword: bot_techreq_handoff trigger
Edge cases and reroutes
Five cases outside tier 1 bot standard technical prerequisites.
Parent model fitment: MULTIMDL686-REROUTE-BOT #686 wizard model distinct specs client
Mandatory post-purchase installation: MANDINST726-REROUTE-BOT #726 prereq installation distinct pre-buy
Companion app setup: #674 COMPAPPbot post-purchase distinct minimum OS
Cable-only charger: #616 CHRGCBLbot wattage distinct port
Return execute bot: TECHREQ727-HANDOFF-BOT #727 agents only
Bot validate compat tier 1 pre-purchase. Post-buy return dispute → #727 agents.
Essential techreq_bot KPIs
Five TECHREQbot steering metrics.
techreq_bot_compat_deflect: resolved compat wizard without agent
techreq_bot_spec_cite_rate: SPEC-CITE-BOT / bot_techreq_specs hardware software
techreq_bot_wizard_complete_rate: wizard completed before verdict / total compat
techreq_bot_false_compat_violations: promised compat incompatible target audit 0
techreq_bot_alt_recommend_rate: ALT-SKU recommend non-compatible / total
Target: techreq_bot_false_compat_violations 0 and techreq_bot_compat_deflect greater than 55%.
TECHREQbot Anti-patterns
Five common errors in bot technical prerequisites.
Compat OK without wizard bot: WIZARD-GATE-BOT compat_wizard_steps map
Invented specs bot: NO-SPEC-INVENT SPEC-CITE-BOT map only
Confusing MULTIMDL #686 bot: fitment distinct model specs environment
Confusing MANDINST #726 bot: post-purchase install distinct from pre-buy
Return execute bot: TECHREQ727-HANDOFF postbuy only
TECHREQbot with Qstomy
Qstomy on Shopify: detect bot_techreq intent, TECHREQ-MAP RAG grounded, compat wizard, spec cite, alt recommend, handoff #727 tier 2.
Pipeline: #728 bot compat check tier 1 → #727 agents postbuy return alternative escalate.
Explore AI support and request a demo.
Checklist, FAQ and going further
TECHREQbot Checklist (8 steps)
Sync TECHREQ-MAP #727: RAG bot PDP specs wizard widget
Policy TECHREQBOT-SUP: 6 rules SPEC WIZARD NO-COMPAT NO-SPEC-INVENT
8 intents bot_techreq_*: flow TRB-1 to TRB-8
4 templates TPL-TECHREQbot-*: SPECS COMPAT ALT HANDOFF
Compat wizard sync: compat_wizard_steps bot agents test
PDP specs tab embed: bot_techreq_specs proactive chat
Red team 10 prompts: compat without wizard invented specs MULTIMDL confused return bot
Dashboard KPI: techreq_bot_* section 9 compat_deflect false_compat
FAQ
Difference #727?
#727 = agents postbuy return alternative escalate. #728 = bot tier 1 specs wizard compat alt handoff.
Difference MULTIMDLbot #686?
#686 = fitment parent model accessory. #728 = specs client environment hardware software network.
How does the bot confirm compatibility?
TPL-TECHREQbot-COMPAT WIZARD-GATE-BOT compat_wizard_steps complete map.
Does the bot handle post-purchase returns?
No. TPL-TECHREQbot-HANDOFF TECHREQ727-HANDOFF-BOT #727.
Going further
This week: index TECHREQ-MAP RAG PDP wizard, sync compat_wizard_steps bot, red team false compat violations audit.
Enzo
July 1, 2026
