E-commerce
July 1, 2026
" help " " ??? " A photo without a caption. The bot responds with a generic block of text or " I did not understand ".
An e-commerce clarification AI chatbot detects the incomplete message, asks one targeted question per turn, fills the slots progressively, and hands off before it becomes an interrogation.
This guide #894 covers intents bot_clarify_*, flow CLARIFYbot CQB-1 to CQB-8, and KPI clarify_bot. Bot pair of the MESSYMSG ($893) playbook. Use case: progressive clarification on the widget side.
Summary
Why clarify progressively?
Asking ten questions at once scares away the mobile customer. ONE-QUESTION-PER-TURN-BOT and PROGRESSIVE-SLOTS reduce messymsg_ tickets #893 and complete triage #879 without confusing them with attachments #895.
What the clarification bot solves
Vague message: help ??? detected
Missing slot: email-order intent
Visual without text: visual_ack then a question
Short loop: max N turns then handoff
Fewer tickets: decrease in messymsg_incomplete
DTC Retail Example
DTC mode, ONE-QUESTION + slots. clarify_bot_messymsg_deflect +29%, clarify_bot_slot_fill_rate 74% in 5 weeks.
CLARIFYbot #894 vs MESSYMSG #893, TRIAGE, CHATMIS #879 and PJ #895
Five fuzzy input contents, five distinct roles.
Quick Matrix
#894 CLARIFYbot: bot to detect and ask progressive questions for widget slots
MESSYMSG #893: agents to manage emojis and screenshots MM-5
CHATMIS #879: clear but misrouted, distinct, incomplete text
MISUND #880: confirm distinct intent, slots clarification
#895 PJ: support for attachments, security, distinct clarification
Pipeline: fuzzy message → #894 clarify → resolution or handoff to #893 if failed.
Which bot_clarify_* intents should be configured?
Eight clarification intents mapped MESSYMSG-MAP #893.
Eight bot_clarify intents
bot_clarify_detect_incomplete: vague message fragment emoji map
bot_clarify_ask_one: one targeted question per turn map
bot_clarify_slot_intent: return delivery order status map
bot_clarify_slot_order: order number email map
bot_clarify_progressive: sequential slot filling map
bot_clarify_visual_ack: acknowledge capture map
bot_clarify_max_handoff: handoff after N turns map
bot_clarify_messymsg_feed: consume LOG #893 map
Each turn logs slots_filled questions_asked clarify_turn_count.
How to consume MESSYMSG-MAP #893?
The bot reads MESSYMSG-MAP #893 + clarify fields: max_clarify_turns, slot_priority, question_templates, messymsg_feed_priority, visual_ack_enabled.
Guardrails clarification
ONE-QUESTION-PER-TURN-BOT: only one question per bot message
PROGRESSIVE-SLOTS-BOT: intent then order then detail
NO-INTERROGATION-BOT: no list of 5+ fields in the same turn
VISUAL-ACK-BOT: visual_ack before question if screenshot
MAX-CLARIFY-TURNS-BOT: handoff after max_clarify_turns
MESSYMSG-FEED-LOOP-BOT: messymsg_feed enriches question_templates
HANDOFF-CONTEXT-BOT: filled slots attached to handoff #155
CLARIFYBOT-SUP Policy in six rules
Six rules for responsible clarification.
ONE-QUESTION-PER-TURN-BOT: one targeted question per bot response
PROGRESSIVE-SLOTS-BOT: order intent → identifier → detail
VISUAL-ACK-BOT: acknowledge capture before clarifying
MAX-CLARIFY-TURNS-BOT: human handoff after N turns
NO-INTERROGATION-BOT: never a long form in chat
MESSYMSG-FEED-LOOP-BOT: LOG #893 review questions within 48 hours
Flow CLARIFYbot CQB-1 to CQB-8
Eight-step flow: incoming message, slot detection, question, resolution, handoff.
CQB-1 Ingest: text emojis attachments
CQB-2 Incomplete detect: bot_clarify_detect_incomplete
CQB-3 Visual ack: visual_ack if screenshot
CQB-4 Slot gap: missing slot priority map
CQB-5 Ask one: ask_one question template
CQB-6 Fill progressive: update slots client reply
CQB-7 Resolve or handoff: CS if complete or max_handoff
CQB-8 Log: slot_fill_rate messymsg_deflect messymsg_feed
Example TPL-CLARIFYbot-ASK
“[optional visual_ack.] [ask_one_copy: Is this a return or a order follow-up?]”
TPL-CLARIFYbot templates and touchpoints
Four short templates clarification embed.
TPL-CLARIFYbot-ASK-INTENT
[ask_intent_copy map.] ONE-QUESTION-PER-TURN. Order delivery return.
TPL-CLARIFYbot-ASK-ORDER
[ask_order_copy map.] Order number or email. PROGRESSIVE-SLOTS.
TPL-CLARIFYbot-VISUAL-ACK
[visual_ack_copy map.] Then ask_one. VISUAL-ACK-BOT.
TPL-CLARIFYbot-HANDOFF
[handoff_copy map.] Partial slots attached. MAX-CLARIFY-TURNS reached.
Touchpoints
help ???: detect + ask_intent
Capture only: visual_ack + ask_one
return without number: ask_order turn 2
LOG MESSYMSG #893: messymsg_feed templates
Edge cases and reroutes
Five cases out of the standard flow.
Plain text poorly routed: #879 CHATMIS not clarify
Heavy PDF file: #895 PJ security
Customer refuses to reply: handoff #12 partial slots #155
Emoji alone 3 rounds: max_handoff not infinite loop
Ticket #893 despite clarify: messymsg_feed review templates
Essential clarify_bot KPIs
Five CLARIFYbot steering metrics and correlation #893.
clarify_bot_messymsg_deflect: resolved without messymsg_ ticket
clarify_bot_one_question_rate: % of single-question turns
clarify_bot_slot_fill_rate: complete slots before resolution
clarify_bot_handoff_after_max_rate: handoffs after N turns / incomplete
clarify_bot_avg_turns_to_resolve: average turns before CS resolution
Target: one_question_rate close to 100% and rising messymsg_deflect.
CLARIFYbot anti-patterns
Five common clarification errors.
Five questions same message: ONE-QUESTION-PER-TURN strict
Ignore capture: VISUAL-ACK before ask
Infinite loop: MAX-CLARIFY-TURNS handoff
Clarify clear text: handoff CHATMIS #879
Ignore feed #893: MESSYMSG-FEED-LOOP templates
CLARIFYbot with Qstomy
Qstomy on Shopify: slot engine, MESSYMSG-MAP feed #893, ONE-QUESTION templates, visual_ack attachments, KPI clarify_bot dashboard.
Scenario: retail DTC, 35% incomplete turns. Progressive slots + max 3 turns. clarify_bot_messymsg_deflect +29%, slot_fill_rate 74% in 5 weeks.
Explore AI support and request a demo.
Checklist, FAQ and going further
CLARIFYbot Checklist (8 steps)
Sync MESSYMSG-MAP #893: feed incomplete fragment screenshot
Policy CLARIFYBOT-SUP: 6 rules ONE-QUESTION PROGRESSIVE MAX-TURNS
8 intents bot_clarify_*: flow CQB-1 to CQB-8
4 templates TPL-CLARIFYbot-*: ASK-INTENT ASK-ORDER VISUAL-ACK HANDOFF
slot_priority: configurable intent order detail
max_clarify_turns 3: handoff #12 #155
Red team help: ??? alone → ask_intent not test block
Dashboard KPI: clarify_bot_* section 9 + delta messymsg_
FAQ
Difference #893?
#893 = agents messy messages. #894 = bot gradually clarify.
How many max turns?
Default 3. max_handoff then agent partial slots.
Difference #880 confirm?
#880 = confirm ambiguous text intent. #894 = fill empty message slots.
Difference #895?
#894 = clarify content. #895 = security management of attachments.
Going further
This week: activate detect_incomplete, templates ask_intent ask_order, max_turns 3, measure clarify_bot_messymsg_deflect.
Enzo
July 1, 2026
