E-commerce
July 1, 2026
"???" "😡📦" A screenshot with no text. Three messages where the customer does not send a structured question and the bot or agent gets stuck.
The unstrictered e-commerce message support covers emojis alone, screenshots, fragments, visual proof and vague requests. Distinct from bot misunderstanding (#879): here the message is incomplete or visual, not poorly interpreted based on clear text.
This guide #893 deploys policy MESSYMSG-SUP, flow MM-1 to MM-8 and matrix MESSYMSG-MAP. Customer service pair of the future clarification bot (#894).
Summary
Why do disorganized messages generate tickets?
Mobile, urgency, anger: the customer sends a photo, three emojis, or "it doesn't work". The bot demands structured text. The agent asks to rephrase without looking at the screenshot.
Five typical messy message frictions
Emoji only: no explicit text
Screenshot: visual proof without context
Fragmented message: "order", "return ???"
Failed attachment: image not received
Vague intent: impossible to sort without clarification
DTC Retail Example
DTC Fashion, 9 messymsg_ tickets/month. After MESSYMSG-MAP: messymsg_clarify_resolution_rate 81%, empty clarification loops -37%.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
MESSYMSG #893 vs CHATMIS #879, CHATTYP #889, TRIAGE and bot #894
Five customer input contents, five distinct angles.
Quick Matrix
#893 MESSYMSG: handle emojis captures fragments incomplete messages
CHATMIS #879: clear text poorly routed distinct blurry input
CHATTYP #889: spelling mistakes distinct empty message
TRIAGE: general support intents triage
PHOTO #871: image rights distinct general after-sales service proof
#893 = incomplete or visual message. #879 = clear text wrongly understood.
Promise #893
Policy MESSYMSG-SUP, tree MESSYMSG-GATE, 8 macros, clarify minimum and resolve if possible, KPI messymsg_clarify_resolution_rate.
Which messymsg_* typologies should be classified?
Action-oriented classifier: emoji_only ≠ screenshot ≠ incomplete ≠ attachment_fail.
Eight MESSYMSG-MAP typologies
messymsg_emoji_only: emojis without explicit text
messymsg_screenshot: screenshot attached or described
messymsg_incomplete: message too vague, help???
messymsg_fragment: single word, return order
messymsg_visual_proof: photo of product, package, damage
messymsg_unclear_intent: indeterminable intent
messymsg_attachment_fail: image file not received
messymsg_frustration: anger, bot did not understand short message
MESSYMSG-SUP Policy: agent and escalation rules
The MESSYMSG-SUP policy sets a minimum clarification without blaming the customer for their format.
Six MESSYMSG-SUP rules
ACKNOWLEDGE-FIRST: MESSYMSG-ACKNOWLEDGE macro to validate receipt
Read visual: MESSYMSG-READ-SCREENSHOT if screenshot is available
Clarify minimum: MESSYMSG-CLARIFY-MIN one targeted question
Resolve if clear: MESSYMSG-RESOLVE-IF-CLEAR obvious intent
Log triage: MESSYMSG-LOG-TRIAGE feeds #894
Do not demand a novel: forbidden to ask a list of 10 questions at once
Situation matrix (agent)
Visible order screenshot: READ-SCREENSHOT + RESOLVE or CLARIFY no.
Angry emoji: ACKNOWLEDGE + CLARIFY-MIN subject
Feedback fragment: CLARIFY order or RESOLVE if customer is known
Clear text wrongly routed: handoff CHATMIS #879
Flow MM-1 to MM-8: standard resolution
Eight sequential steps, SLA P3 messymsg < 24 h, escalate if attachment_fail is recurrent.
Flow MM-1 to MM-8
MM-1 Triage: read message attachments, tag messymsg_*
MM-2 Inspect: screenshot emoji fragment attachment status
MM-3 Infer: probable intent command return visual dispute
MM-4 Classify: messymsg_* via MESSYMSG-MAP
MM-5 Execute: READ-SCREENSHOT, CLARIFY-MIN, RESOLVE, REQUEST-DETAIL
MM-6 Confirm: macro MESSYMSG-DONE clarification resolution
MM-7 Test: customer has provided minimum detail or CS resolved
MM-8 Close: KPI messymsg_clarify_resolution_rate + export #894
Eight ready-to-paste MESSYMSG-* macros
Aligned macros, minimal clarification, and visual reading.
MESSYMSG-* Library
MESSYMSG-ACKNOWLEDGE: "We have received your message. We are helping you move forward."
MESSYMSG-READ-SCREENSHOT: "We have viewed your screenshot. We see {{élément_visible}}."
MESSYMSG-CLARIFY-MIN: "To help you: is this about {{question_unique}}? (order, return, delivery)"
MESSYMSG-REQUEST-DETAIL: "Could you specify {{un_détail}}? Order number or email is enough."
MESSYMSG-RESOLVE-IF-CLEAR: "According to your message: {{solution_SAV}}."
MESSYMSG-HANDOFF: "An agent is taking over with your attachments. Reference: {{id}}."
MESSYMSG-LOG-TRIAGE: "Format reported to improve the chatbot: {{typologie}}."
MESSYMSG-DONE: "Recap: {{besoin}}. Action: {{résolution}}. Detail requested: {{oui_non}}."
MESSYMSG-GATE tree and agent-ready clarification registry
Decision tree before ignoring capture or bombarding with questions.
MESSYMSG-GATE
Readable screenshot + clear intent? → READ-SCREENSHOT + RESOLVE
Emoji or single fragment? → CLARIFY-MIN one question
Missing attachment? → REQUEST-DETAIL or alternative email channel
Proof of product damage? → HANDOFF CS + keep visual
Structured text misunderstood? → handoff CHATMIS #879
Minimum internal registry
Document helpdesk: attachment access, CLARIFY macros by typology, limit of one question per turn, procedure LOG #894. Train agents: messy ≠ typo #889 ≠ misunderstanding #879.
KPIs, QA, and handoff to bot #894
Measuring MESSYMSG detects excessive clarifications or ignored captures.
Four MESSYMSG KPIs
messymsg_clarify_resolution_rate: resolved or usefully clarified / total
messymsg_one_question_rate: % CLARIFY-MIN a single question
messymsg_screenshot_read_rate: % screenshot with READ-SCREENSHOT
messymsg_repeat_7d: same blurry message within 7 days
Handoff #894
Export weekly MESSYMSG-MAP: messymsg_incomplete messymsg_fragment priority. Guardrail MESSYMSG-CLARIFY-LOOP: each LOG-TRIAGE feeds bot questions #894.
Edge cases: expired ad capture, sensitive photo, emoji spam
Three cases outside the standard flow.
Capture of old promotional ad
READ-SCREENSHOT + verify active offer. Promo handoff if expired. No MESSYMSG alone if promo subject is clear.
Sensitive photo or minor
HANDOFF + moderation procedure. No automatic RESOLVE on visuals.
Emoji sequence without CLARIFY response
ACKNOWLEDGE + human HANDOFF if there is frustration. LOG-TRIAGE emoji_only.
Agent training: 20 minutes MESSYMSG
Module: read screenshots, CLARIFY-MIN one question, RESOLVE if clear, LOG-TRIAGE, distinguish #879 #894.
Exercises
Ticket A: cart error screenshot → READ-SCREENSHOT + RESOLVE or CLARIFY no.
Ticket B: "???" alone → CLARIFY-MIN subject one question
Ticket C: clear sentence poorly routed by bot → handoff CHATMIS #879
How Qstomy structures MESSYMSG in your stack
Qstomy route messymsg_*, displays agent attachments, CLARIFY-MIN macros, and LOG export to #894.
Three bricks
Routing: intent messy_message vs typo vs misunderstanding
Attachment panel: sync macros MESSYMSG-* screenshot status
Clarify loop #894: weekly messymsg_incomplete aggregation
Scenario: retail DTC, 8 tickets/month captures without text. READ-SCREENSHOT agents, progressive CLARIFY bot #894. messymsg_clarify_resolution_rate increases from 64% to 83% in 4 weeks.
FAQ and MESSYMSG deployment checklist
FAQ
How many questions to ask?
One per CLARIFY-MIN turn. Not a list of ten fields.
Difference #879?
#893 = fuzzy or visual input. #879 = clear text poorly routed.
Difference #894?
#893 = agents. #894 = bot asking right clarification questions.
7-day Checklist
D1: MESSYMSG-SUP + MESSYMSG-MAP + attachment access
D2: 8 helpdesk macros
D3: routing matrix #879 #889 TRIAGE
D4: 20-min agent training
D5: messymsg_* tags + KPIs
D6: test READ vs CLARIFY vs CHATMIS
D7: bot brief #894 CLARIFY-GATE
Interlinking
Enzo
July 1, 2026
