E-commerce
July 1, 2026
"The bot says my review will be published tomorrow without checking." "The AI doesn't know why my comment was rejected." "The chatbot promises to force the publication while nothing changes." Three failures where a badly calibrated review moderation bot worsens distrust.
A retail review status AI chatbot reads the actual status, cites the categorized rejection reason, explains guidelines rules and guides resubmission, without promising forced publication or confusing moderation with published negative reviews.
This guide #868 covers intents bot_revmod_*, flow REVMODbot and KPI revmod_bot. Bot pair of the REVMOD playbook (#867). AI use case: tier 1 review moderation status and rules.
Summary
Why does a review status bot reduce moderation tickets?
Pending, rejected, or expired delay review: the customer wants an immediate response in plain language. A calibrated bot reads REVMOD-MAP #867, quotes status_copy and refusal_reason_copy, without NO-FORCE-PUBLISH violation or confusion with negative review response #93.
What the bot resolves tier 1 review moderation
Display status: status_copy pending published rejected map
Explain rejection: refusal_reason_copy understandable category map
Communicate delay: eta_copy SLA moderation map
Guide resubmission: resubmit_copy guidelines link map
Customer support handoff: #867 payload revmod_* complex delay
REVMODbot vs REVMOD #867, NEGREV #93, PROOFbot #226 and COLLECT #92
Six review contents, six distinct angles on the client side.
Quick matrix
#868 REVMODbot: tier 1 bot status refusal rules resubmit handoff
#867 REVMOD: agents lookup ESCALATE moderation RM-5
NEGREV #93: reply to negative review already published distinct from moderation
COLLECT #92: review solicitation distinct from publication status
PROOFbot #226: cite published reviews conversion distinct from pending status
Anti-hallucination #123: policy map whitelist do not invent LLM status
Pipeline: #868 bot tier 1 status → #867 agents execute RM-5 ESCALATE if SLA delay is exceeded.
Which bot_revmod_* intents should be configured?
Eight review moderation bot intents mapped to revmod_* typologies #867.
Eight bot_revmod intents
bot_revmod_status : status_copy review status map
bot_revmod_pending : eta_copy pending review map
bot_revmod_why_refused : refusal_reason_copy refusal reason map
bot_revmod_rules : rules_copy publishing charter map
bot_revmod_resubmit : resubmit_copy correct resubmit map
bot_revmod_delay : escalate_copy SLA delay exceeded map
bot_revmod_negrev_reroute : published review CS → NEGREV #93
bot_revmod_handoff : complex → REVMOD867-HANDOFF-BOT
Force publication or override moderation API → human handoff #867 RM-5 only. Bot status explain only.
How should I consume REVMOD-MAP #867?
The bot reads REVMOD-MAP #867 + bot fields: status_copy, eta_copy, refusal_reason_copy, rules_copy, resubmit_copy, edit_copy, escalate_copy, limits_copy, negrev_reroute_copy.
Guardrails for sensitive review moderation
REVMOD-MAP-GROUNDED-BOT: status answer from map only
STATUS-FIRST-BOT: status_copy lookup before any answer
NO-FORCE-PUBLISH-BOT: never promise forced publication
NO-OVERRIDE-MOD-BOT: do not modify bot API moderation decision
RULES-COPY-BOT: rules_copy guidelines before argumentation
NEGREV-REROUTE-BOT: published negative customer service review → NEGREV #93
REVMOD867-HANDOFF-BOT: SLA delay exceeded → #867 RM-5 agents
REVMODBOT-SUP policy in six rules
Six rules for responsible review moderation bots.
STATUS-FIRST-BOT: lookup real status before explanation
NO-FORCE-PUBLISH-BOT: do not promise a guaranteed publication date
NO-OVERRIDE-MOD-BOT: do not override bot moderation rejections
REFUSAL-CATEGORY-BOT: categorized reason only, no raw technical filter
RESUBMIT-GUIDE-BOT: resubmit_copy if policy allows
NEGREV-REROUTE-BOT: published unhappy review → #93 not moderation
REVMODbot Flow RMB-1 to RMB-8
Eight-step moderation bot flow: embedded page, review submission, account status.
RMB-1 Classify: bot_revmod_* detect keyword review pending refused published moderation
RMB-2 Lookup: review status email order from read-only map
RMB-3 REVMOD-MAP: status eta refusal_reason rules resubmit
RMB-4 Explain: TPL-REVMODbot-STATUS based on intent
RMB-5 Guardrail: NO-FORCE-PUBLISH NO-OVERRIDE-MOD NEGREV-REROUTE
RMB-6 Respond: TPL-REVMODbot max 3 grounded sentences
RMB-7 Handoff or close: #867 #93 payload or close understood OK
RMB-8 Log: intent status_first force_publish_blocked negrev_rerouted handoff Y/N
Example TPL-REVMODbot-STATUS
"[status_copy map.] [eta_copy map if pending.] [rules_copy map optional.] STATUS-FIRST-BOT."
TPL-REVMODbot templates and touchpoints
Four short templates for review moderation embed.
TPL-REVMODbot-STATUS
[status_copy map.] [eta_copy map.] REVMOD-MAP-GROUNDED-BOT.
TPL-REVMODbot-REFUSED
[refusal_reason_copy map.] [resubmit_copy map if eligible.] REFUSAL-CATEGORY-BOT.
TPL-REVMODbot-RULES
[rules_copy map.] [resubmit_copy map.] RULES-COPY-BOT.
TPL-REVMODbot-DELAY
[eta_copy map.] [escalate_copy map.] REVMOD867-HANDOFF-BOT if SLA exceeded.
Touchpoints
Review submission confirmation page: bot_revmod_pending proactive
Review refused keyword: bot_revmod_why_refused trigger
Review status keyword: bot_revmod_status priority
Where is my review? footer: bot_revmod_status proactive
Edge cases and reroutes
Five cases outside tier 1 bot moderation standard review.
Negative review already published CS: NEGREV #93 reroute
Request to leave a review: COLLECT #92 reroute submission link
Social proof product chat: PROOFbot #226 reroute
Photo video review long delay: eta_copy distinct media without auto promise
Third-party marketplace moderation: limits_copy referral external platform
Essential revmod_bot KPIs
Five REVMODbot management metrics.
revmod_bot_status_deflect: closed understood without agent repeat 7d
revmod_bot_status_first_rate: STATUS-FIRST / total status questions
revmod_bot_force_publish_violations: audit target publication promise 0
revmod_bot_resubmit_guided_rate: % refused with resubmit_copy tracked
revmod_bot_handoff_rate: escalate #867 / total revmod bot
Target: revmod_bot_force_publish_violations 0 and revmod_bot_status_first_rate greater than 95%.
REVMODbot anti-patterns
Five common mistakes in bot review moderation.
Promising publication tomorrow: NO-FORCE-PUBLISH eta_copy without guarantee
Inventing status without lookup: STATUS-FIRST map read-only mandatory
Canceling bot moderation rejection: NO-OVERRIDE-MOD handoff #867
Confusing pending with published negative review: NEGREV-REROUTE #93
Skipping rules before contested rejection: RULES-COPY before argumentation
REVMODbot with Qstomy
Qstomy on Shopify: detect bot_revmod intent, REVMOD-MAP RAG grounded, NO-FORCE-PUBLISH guardrail submission page, enriched handoff #867 tier 2 ESCALATE moderation.
Pipeline: #868 bot status tier 1 → #867 agents execute RM-5 if delay or dispute.
Scenario: beauty DTC, reviews pending 12 days. Bot #868 status + eta, agents ESCALATE moderation. revmod_bot_status_deflect 84%, force_publish_violations 0 in 4 weeks.
Explore AI support and request a demo.
Checklist, FAQ and going further
REVMODbot Checklist (8 steps)
Sync REVMOD-MAP #867: RAG bot moderation embed review submission page
Policy REVMODBOT-SUP: 6 rules STATUS-FIRST NO-FORCE-PUBLISH NO-OVERRIDE-MOD
8 intents bot_revmod_*: flow RMB-1 to RMB-8
4 templates TPL-REVMODbot-*: STATUS REFUSED RULES DELAY
Block mod override API write: bot read-only no publication write
Red team 15 prompts: promise publish invent status override refusal skip rules
Footer Where is my review?: bot_revmod_status trigger embed
Dashboard KPI: revmod_bot_* section 9 force_publish_violations status_first
FAQ
Difference #867?
#867 = agents lookup ESCALATE RM-5. #868 = bot tier 1 rules status without override.
Difference #93?
#868 = moderation before publication. #93 = replying to negative review already online.
Does the bot force publication?
No. NO-FORCE-PUBLISH-BOT. REVMOD867-HANDOFF if contested.
Review refused, what to do?
bot_revmod_why_refused TPL-REFUSED + resubmit_copy if charter allows.
Going further
This week: deploy Where is my review embed footer, red team force_publish_violations audit, sync bot_revmod_pending test submission confirmation page.
Enzo
July 1, 2026
