E-commerce
July 1, 2026
"The bot says my customization is approved while it is still pending." "The AI accepts my JPG file when the map requires vector." "Chatbot promises modification after ops approval." Three failures where a miscalibrated personal bot review short-circuits human validation.
An AI chatbot human validation customization does not replace MANPERS agents (#597). It reads MANPERS-MAP, verifies queue ops status, cites file_requirements rejection_rules, and hands off change approve reject to design humans.
This guide #598 covers intents bot_manpers_*, flow MANPERSbot, and KPI manpers_bot. Pair bot of the MANPERS playbook (#597). New AI workflow use case: explain review status and file requirements without approving or rejecting customization.
Summary
Why automate the personal review status with a bot?
"What is the status of my validation?", "what file format?", and "why was it rejected?" come up every day regarding custom logo orders. A bot calibrated to lookup MANPERS-MAP, verify the actual queue status, and cite requirements without improvising ops approval.
What the tier 1 bot resolves
Review status: pending approved rejected production queue API
File requirements: file_requirements format DPI upload_url
Rejection explanation: rejection_rules map correctable cause
Modification window: change_window_policy cite handoff
Review SLA: review_sla_hours map business hours turnaround
Gorgias notes that pre-production customization tickets convert poorly if a status is made up or if the promised turnaround time is outside the ops workflow (Gorgias, support stats 2026). The bot intercepts bot_manpers_review_status before any fictional approval.
MANPERSbot vs MANPERS #597, validation #418, ENGRVAL #490 and failed personal #417
Five contents, five distinct customization moments.
Quick Matrix
#598 MANPERSbot: bot tier 1 status review file requirements handoff
#597 MANPERS: agents change approve reject escalate ops design
Bot validation #418: auto pre-purchase validation no human review
ENGRVAL #490: engraving text char limit pre-prod distinct logo
Failed perso #417: post-delivery remake dispute
Pipeline: bot status file rejection explain → #597 change approve reject cancel ops. Auto checkout → #418 reroute.
Which bot_manpers_* intents should be configured?
Eight personal review bot intents mapped to manpers_* typologies #597.
Eight bot_manpers intents
bot_manpers_review_status : review_sla status queue quote
bot_manpers_file_requirements : DPI format upload file_requirements
bot_manpers_rejection_info : rejection_rules correctable cause
bot_manpers_change_info : change_window_policy handoff explanation
bot_manpers_submit_guide : incomplete submission checklist map
bot_manpers_approved_delay : approved production delay info
bot_manpers_upload_collect : file metadata handoff ops not approve
bot_manpers_handoff : change approve reject cancel → #597
Tier 1 auto : review_status, file_requirements, rejection_info, change_info, submit_guide if order_ref + MANPERS-MAP + guardrails.
bot_manpers_handoff, approve reject execute, post-approved change → agents #597 payload order_ref perso_type_id.
How should MANPERS-MAP #597 be consumed?
The bot reads MANPERS-MAP #597: perso_type_id, review_sla_hours, file_requirements, rejection_rules, change_window_policy, approval_notification, escalation_ops, production_hold_tag.
Lookup grounded
Order SKU detect: properties tags → MANPERS-MAP row
Review queue API: Notion ops queue status REVIEW-STATUS-VERIFY-BOT
Shopify hold tag: production_hold_tag pending approved
FILE-REQUIREMENTS-GROUNDED-BOT: format DPI map only
NO-APPROVE-BOT: bot never approves perso
NO-REJECT-EXECUTE-BOT: final rejection → handoff #597 ops
Alignment anti-hallucination (#123): review status = queue API or Shopify tag only.
MANPERSBOT-SUP policy in six rules
Six custom bot review rules apply.
MANPERS-MAP-GROUNDED: SLA file rejection change from map only
REVIEW-STATUS-VERIFY-BOT: queue API before status cite
NO-APPROVE-BOT: bot neither approves nor launches production
NO-REJECT-EXECUTE-BOT: final rejection → handoff #597 ops
CHANGE-WINDOW-CITE-BOT: modification according to change_window_policy map
VALID418-PERSO417-REROUTE-BOT: auto #418, post-delivery #417
Flow MANPERSbot MPB-1 to MPB-8
Eight-step human validation bot customization flow.
MPB-1 Classify: bot_manpers_* intent detect
MPB-2 Collect: order_ref perso_type file question
MPB-3 MANPERS-MAP: sla file rejection change hold
MPB-4 Queue verify: ops queue Shopify tag REVIEW-STATUS
MPB-5 Guardrail: NO-APPROVE NO-REJECT-EXECUTE CHANGE-WINDOW
MPB-6 Respond: TPL-MANPERSbot grounded map
MPB-7 Handoff: change approve reject cancel → #597
MPB-8 Log: intent perso_type_id tag manpers_bot
TPL-MANPERSbot-STATUS Example
"Order [order_ref] [perso_type_id]: status [queue API: pending / approved / rejected / production]. [If pending: delay [review_sla_hours map] business hours.] [If rejected: TPL-MANPERSbot-REJECT.] [If change requested: handoff #597.]"
Templates TPL-MANPERSbot and touchpoints
Four essential templates.
TPL-MANPERSbot-STATUS
Order [order_ref] custom [perso_type_id] : [statut queue]. SLA review [review_sla_hours]. [If delayed: handoff [escalation_ops].]
TPL-MANPERSbot-FILE
Requirements [perso_type_id] : [file_requirements map format DPI size]. Upload : [upload_url]. [If incomplete: checklist submit_guide map.]
TPL-MANPERSbot-REJECT
Refusal [order_ref] : [rejection_rules map cause]. [If correctable: resubmit compliant [file_requirements].] [If dispute: handoff #597 ops.]
TPL-MANPERSbot-HANDOFF
Request [change / approve / reject / cancel] forwarded to design team. Order [order_ref]. Custom [perso_type_id]. Delay [handoff_sla].
Touchpoints
Custom email confirmation : bot_manpers_review_status embed
Upload portal page : bot_manpers_file_requirements widget
Order status page : bot_manpers_review_status entry
Rejection email footer : bot_manpers_rejection_info chip
Edge cases and reroutes
Five cases outside tier 1 bot review standard personalization.
Ops approval requested: NO-APPROVE-BOT handoff #597 ops design
Definitive rejection dispute: NO-REJECT-EXECUTE handoff #597 MANPERS-REJECT-01
Auto checkout validation: VALID418-REROUTE #418 distinct
Text engraving char limit: ENGRVAL #490 reroute
Failed personalization received: PERSO417-REROUTE #417 post-delivery
Bot never executes approve reject: design ops decision → agents #597 workflow queue.
Essential man-hours/bot KPIs
Five MANPERSbot steering metrics.
manpers_bot_status_deflect: review_status resolved without agent
manpers_bot_file_deflect: file_requirements resolved without handoff
manpers_bot_handoff_rate: change approve reject / total manpers bot
manpers_bot_hallucination_rate: approve status outside audit queue
manpers_bot_reroute_accuracy: VALID418 PERSO417 correct reroute
Target: manpers_bot_status_deflect greater than 70% with API sync queue MANPERS-MAP review_sla.
MANPERSbot anti-patterns
Five common mistakes in personal bot reviews.
Invented approval status: REVIEW-STATUS-VERIFY-BOT queue first
Bot approval: NO-APPROVE-BOT handoff #597 ops
Accepted file format outside map: FILE-REQUIREMENTS-GROUNDED map only
Post-approved promised modification: CHANGE-WINDOW-CITE handoff
Failed personal confusion: PERSO417-REROUTE #417 post-delivery
MANPERSbot with Qstomy
Qstomy on Shopify: detect bot_manpers intent, MANPERS-MAP RAG grounded, review queue lookup, Shopify hold tag verify, handoff #597 change approve payload order_ref.
Pipeline: #598 bot status file rejection → #597 approve reject change escalate design ops.
Explore AI support and request a demo.
Checklist, FAQ and going further
MANPERSbot Checklist (8 steps)
Sync MANPERS-MAP #597: RAG bot + API queue
Policy MANPERSBOT-SUP: 6 NO-APPROVE-BOT rules
8 intents bot_manpers_*: flow MPB-1 dummy to MPB-8
4 templates TPL-MANPERSbot-*: STATUS FILE REJECT HANDOFF
Order status embed: bot_manpers_review_status entry
Upload portal widget: bot_manpers_file_requirements
Red team 10 prompts: approve promise format JPG accepted post-approved change
Dashboard KPI: manpers_bot_* section 9
FAQ
Difference #597?
#597 = agents change approve reject escalate ops. #598 = bot tier 1 status file requirements handoff.
Bot approves my customization?
No. NO-APPROVE-BOT. Handoff #597 ops design.
File rejected?
TPL-MANPERSbot-REJECT rejection_rules file_requirements map.
Difference bot #418?
#418 = auto checkout validation. #598 = human review ops post-order.
Going further
This week: index MANPERS-MAP RAG, embed bot order status page, red team approve promise bot.
Enzo
July 1, 2026
