E-commerce
July 1, 2026
Simple question, 12-line response, customer closes the widget. On mobile, every extra word costs a conversion.
An e-commerce short-answer AI chatbot places the direct answer in the first line, limits bullet points, offers a single CTA, and links the details to a page, not a wall of text in the chat.
This guide #888 covers bot_brief_* intents, SHORTANSWERbot SAB-1 to SAB-8 flows, and brief_bot KPIs. Bot pair from the CHATLONG playbook (#887). Use case: conversational conciseness oriented towards conversion.
Summary
Why keeping it short converts better?
The widget customer wants a quick decision: yes I can return, here is the cart link, here is the deadline. ANSWER-FIRST-BOT and MAX-LINES-BOT reduce chatlong_ #887 tickets and mobile abandonment.
What brevity solves
Immediate reading: direct line 1 answer map
Mobile friendly: max 3 short bullet points map
Clear CTA: one action link map
Detail on demand: hub link, not a block of text map
Fewer tickets: decrease in chatlong_too_verbose
DTC Retail Example
DTC Fashion, ANSWER-FIRST + max 4 lines. brief_bot_chatlong_deflect +32%, brief_bot_cta_click_rate +18% in 5 weeks.
SHORTANSWERbot #888 vs CHATLONG #887, CHATMIS #879, TRIAGE and PDP conversion
Five UX writing bot contents, five distinct roles.
Quick Matrix
#888 SHORTANSWERbot: prompt templates short response limits CTA conversion
CHATLONG #887: agents manage tickets block CL-5
CHATMIS #879: misunderstanding distinct length
TRIAGE: intent triage general support
RESUME #882: session resume distinct conciseness
MISUND #880: synonyms distinct verbosity
Pipeline: #887 LOG verbosity → #888 adjusts prompts → decrease in chatlong_.
Which bot_brief_* intents should be configured?
Eight conciseness intents mapped CHATLONG-MAP #887.
Eight bot_brief intents
bot_brief_answer_first: direct answer line 1 map
bot_brief_bullet_max3: optional bullets max 3 map
bot_brief_cta_single: one CTA link cart PDP map
bot_brief_mobile_format: short line breaks mobile map
bot_brief_detail_link: details to help hub map
bot_brief_max_tokens: response tokens cap map
bot_brief_progressive: expand only if customer asks for more map
bot_brief_chatlong_feed: consume LOG #887 verbose intents map
Each response logs line_count cta_shown for brief_bot KPI.
How should CHATLONG-MAP #887 be consumed?
The bot reads CHATLONG-MAP #887 + brevity fields: max_lines, max_bullets, max_tokens_reply, cta_templates, detail_link_base, chatlong_feed_priority.
Short answer guardrails
ANSWER-FIRST-BOT: yes/no decision in the first sentence
MAX-LINES-BOT: line limit unless progressive is requested
NO-WALL-OF-TEXT-BOT: no 200+ word paragraph in the widget
CTA-SINGLE-BOT: only one link button per turn
MOBILE-BREAK-BOT: short lines with frequent breaks
DETAIL-ON-DEMAND-BOT: link hub do not paste everything
CHATLONG-FEED-LOOP-BOT: chatlong_feed reduces max_tokens for verbose intent
SHORTBOT-SUP policy in six rules
Six rules for conversion-oriented conciseness.
ANSWER-FIRST-BOT: decision or key figure at the top
MAX-LINES-BOT: default 4 lines for mobile widget
CTA-SINGLE-BOT: one CTA for purchase / return to cart per response
DETAIL-ON-DEMAND-BOT: hub link for the rest
CHATLONG-FEED-LOOP-BOT: each LOG #887 review prompt within 48 hours
NO-FILLER-BOT: no long, repeated polite formulas
Flow SHORTANSWERbot SAB-1 to SAB-8
Eight-step flow: short response query CTA log feed #887.
SAB-1 Intent detect: purchase topic AFTER-SALES simple info
SAB-2 Brevity profile: max_lines tokens according to intent map
SAB-3 Answer first: generate direct ANSWER-FIRST sentence
SAB-4 Bullets optional: bullet_max3 only if necessary
SAB-5 CTA attach: cta_single PDP cart return map
SAB-6 Detail link: detail_link if complex policy
SAB-7 Progressive gate: expand if customer "more details"
SAB-8 Log: line_count cta_click chatlong_deflect chatlong_feed
Example TPL-SHORTbot-CORE
“[answer_first map.] [bullet_max3 optional.] [cta_single map.]”
Templates TPL-SHORTbot and touchpoints
Four short conversion embed templates.
TPL-SHORTbot-CORE
[answer_first_copy map.] ANSWER-FIRST-BOT. MAX-LINES respected.
TPL-SHORTbot-CTA
[core_copy map.] [cta_copy map: View product / Return / Cart.] CTA-SINGLE-BOT.
TPL-SHORTbot-DETAIL-LINK
[core_copy map.] Details: [detail_link map.] DETAIL-ON-DEMAND-BOT.
TPL-SHORTbot-PROGRESSIVE
[extended_copy map.] Only if customer asks for more. progressive gate.
Touchpoints
Yes/No question: answer_first one sentence
Purchase intent: core + cta_single PDP
Policy 3+ rules: core + detail_link not a block of text
LOG CHATLONG #887: chatlong_feed reduced max_tokens
Edge cases and reroutes
Five cases outside the standard flow.
Long legal obligation: detail_link + progressive, do not shorten at risk
Client requests all details: progressive TPL-SHORTbot-PROGRESSIVE
Topic poorly understood: #879 CHATMIS do not shorten alone
Short but incorrect answer: #123 HALLU accuracy priority
Ticket #887 despite brief: chatlong_feed intent review prompt
Essential brief_bot KPIs
Five SHORTANSWERbot steering metrics and correlation #887.
brief_bot_chatlong_deflect: resolved without a chatlong_ ticket
brief_bot_answer_first_rate: % first-line decision responses
brief_bot_avg_line_count: average lines per widget response
brief_bot_cta_click_rate: unique CTA clicks / responses with CTA
brief_bot_mobile_abandon_delta: mobile abandon evolution post-brief
Target: avg_line_count under max_lines and chatlong_deflect on the rise.
Anti-patterns SHORTANSWERbot
Five common conciseness mistakes.
Shortening without answering: ANSWER-FIRST mandatory before cutting
Three CTAs per message: CTA-SINGLE one single link
Pasting entire help hub: DETAIL-ON-DEMAND link, do not dump RAG
Ignoring feed #887: CHATLONG-FEED-LOOP on verbose intents
Repetitive politeness: NO-FILLER no thank you have a good day every turn
SHORTANSWERbot with Qstomy
Qstomy on Shopify: max_lines per intent, CHATLONG-MAP feed #887, cart PDP CTA templates, KPI brief_bot dashboard, progressive expand.
Scenario: retail DTC, verbose return intent. ANSWER-FIRST + detail_link. brief_bot_chatlong_deflect +32%, brief_bot_cta_click_rate +18% in 5 weeks.
Explore AI support and request a demo.
Checklist, FAQ and going further
Checklist SHORTANSWERbot (8 steps)
Sync CHATLONG-MAP #887: feed chatlong_too_verbose lost_key_info
Policy SHORTBOT-SUP: 6 rules ANSWER-FIRST MAX-LINES CTA-SINGLE
8 intents bot_brief_*: flow SAB-1 to SAB-8
4 templates TPL-SHORTbot-*: CORE CTA DETAIL-LINK PROGRESSIVE
max_lines 4 mobile: configurable max_tokens_reply
CTA templates: cart PDP return one link
Red team block: simple question response > 6 lines test
Dashboard KPI: brief_bot_* section 9 + delta chatlong_
FAQ
Difference #887?
#887 = agents summarizing block tickets. #888 = bot writing short directly in the widget.
Short response = less precise?
No if ANSWER-FIRST + detail_link. Accuracy #123 takes precedence over trimming.
How many lines max?
Default 4 mobile. progressive if customer asks for more.
CTA on every CS message?
CTA-SINGLE on purchase return intents. No CTA on sensitive disputes.
Go further
This week: activate ANSWER-FIRST delivery return intents, max_lines 4, a test cart CTA, measure brief_bot_chatlong_deflect.
Enzo
July 1, 2026
