E-commerce
July 1, 2026
"My package is broken, what photo should I send?" The bot replies with a generic block of text. The customer attaches a blurry image. Three follow-ups later, ticket photoproof_ is opened.
An e-commerce photo proof AI chatbot guides the framing angle by angle, collects the 4 mandatory photos, validates basic readability, and escalates to customer service or dispute #363 with full context.
This guide #898 covers intents bot_photoproof_*, flow PHOTOPROOFbot PPB-1 to PPB-8, and guardrails PHOTOPROOF-GUIDE-GATE. Bot companion to PHOTOPROOF playbook (#897). Usecase: collecting actionable proof on the widget side.
Summary
Why guide the scoping on the bot side?
Without step-by-step guidance, the client sends 3 blurry close-ups and no box. PHOTOPROOF-GUIDE-GATE and ONE-ANGLE-PER-TURN-BOT reduce photoproof_angle_missing #897 and complete attachment upload #896 without confusing it with clarification #894.
What the photoproof bot solves
Opaque checklist: client does not know which angles
Blurry photo: no framing light guide
Missing angle: damage is OK, no label
Agent follow-ups: photoproof_resend_guided tickets
Resolution delay: handoff #363 without a complete set
DTC retail example
DTC home decor, 4-angle widget guidance. photoproof_bot_first_round_accept_rate 76%, photoproof_bot_deflect +41% in 5 weeks.
PHOTOPROOFbot #898 vs PHOTOPROOF #897, CUSTATTbot #896, DMG #363 and CLARIFY #894
Six damage proof contents, six distinct roles.
Quick matrix
#898 PHOTOPROOFbot: bot guide framing collect 4 angles climb
PHOTOPROOF #897: agents validate acceptance criteria PP-5
CUSTATTbot #896: upload gate format size general attachment
CUSTATT #895: CS reception attachment distinct from photo criteria
DMG-PKG #363: dispute resolution after photos OK
CLARIFY #894: clarification blurry message distinct from damage
Pipeline: damage reported → #898 guidance 4 angles → validation #897 or handoff #363.
Which bot_photoproof_* intents should be configured?
Eight photo proof intents mapped PHOTOPROOF-MAP #897.
Eight bot_photoproof intents
bot_photoproof_detect_damage: intent package product damage map
bot_photoproof_guide_angle: one framing instruction per turn map
bot_photoproof_collect_damage_close: slot close-up damage map
bot_photoproof_collect_product_full: slot entire product map
bot_photoproof_collect_packaging: slot outer box map
bot_photoproof_collect_label: slot shipping label map
bot_photoproof_blurry_retry: guide blurry retry framing map
bot_photoproof_feed_loop: consume LOG #897 refusal reasons map
Each upload logs angle_collected blur_score checklist_complete proof_status.
How do I consume PHOTOPROOF-MAP #897?
The bot reads PHOTOPROOF-MAP #897 + guide fields: required_angles, angle_order, guide_copy_per_angle, blur_threshold, photoproof_feed_priority, escalate_sla.
Photoproof Guardrails
PHOTOPROOF-GUIDE-GATE: guide before accepting incomplete set
ONE-ANGLE-PER-TURN-BOT: one framing instruction per message
PROGRESSIVE-CHECKLIST-BOT: order damage → product → box → label
BLURRY-RETRY-BOT: blurry_retry before agent handoff
NO-CLAIM-WITHOUT-SET-BOT: do not promise refund without 4 angles
UPLOAD-VIA-CUSTATT-BOT: size format via gate #896
PHOTOPROOF-FEED-LOOP-BOT: LOG #897 enriches guide_copy
HANDOFF-CONTEXT-BOT: 4 photos + attached slots handoff #155
PHOTOPROOFBOT-SUP Policy in Six Rules
Six rules for responsible evidence collection.
PHOTOPROOF-GUIDE-GATE: guided checklist before final validation
ONE-ANGLE-PER-TURN-BOT: one framing instruction per bot response
PROGRESSIVE-CHECKLIST-BOT: fixed order of angles register #897
BLURRY-RETRY-BOT: max 2 blur retries then human handoff
NO-CLAIM-WITHOUT-SET-BOT: no reship refund decision on the bot side
PHOTOPROOF-FEED-LOOP-BOT: each LOG #897 review guide within 48 hours
Flow PHOTOPROOFbot PPB-1 to PPB-8
Eight-step flow: damage detection guidance collection validation escalation log.
PPB-1 Ingest: damage message or existing photo upload
PPB-2 Detect: bot_photoproof_detect_damage vs clarify #894
PPB-3 Upload gate: CUSTATT gate #896 size format
PPB-4 Guide angle: guide_angle slot according to checklist
PPB-5 Blur check: blurry_retry if threshold exceeded
PPB-6 Set complete: 4 angles → handoff #897 or #363
PPB-7 Feed loop: LOG #897 adjusts guide_copy angles
PPB-8 Log: first_round_accept deflect checklist_complete
Example TPL-PHOTOPROOFbot-GUIDE-PACKAGING
« Thank you for the photos of the damage and the product. Now, please take a photo of the entire outer cardboard box (visible crushing or tearing). »
TPL-PHOTOPROOFbot templates and touchpoints
Four short templates for framing guidance embed.
TPL-PHOTOPROOFbot-GUIDE-DAMAGE
[damage_close_copy map.] Close-up crack chip. ONE-ANGLE-PER-TURN.
TPL-PHOTOPROOFbot-GUIDE-PACKAGING
[packaging_copy map.] Whole outer box. PROGRESSIVE-CHECKLIST.
TPL-PHOTOPROOFbot-BLURRY-RETRY
[blurry_copy map.] Natural light, clear damage. BLURRY-RETRY-BOT.
TPL-PHOTOPROOFbot-SET-COMPLETE
[complete_copy map.] 4 photos received. Handoff to team under {{SLA}}. NO-CLAIM-WITHOUT-SET.
Touchpoints
"broken parcel": detect + guide damage_close
Blurry photo uploaded: blurry_retry before next angle
4 angles OK: set_complete handoff #897 #363
LOG PHOTOPROOF #897: feed_loop guide_copy packaging
Edge cases and reroutes
Five cases out of the standard flow.
Vague message without damage: #894 CLARIFY
Invoice PDF only: #896 not photoproof
Customer refuses 4th angle: handoff #12 partial slots #155
Immediate refund request: NO-CLAIM-WITHOUT-SET + guidance
Photoproof ticket despite bot: feed_loop review angle_order
Essential photoproof_bot KPIs
Five PHOTOPROOFbot steering metrics and correlation #897.
photoproof_bot_first_round_accept_rate: complete sets without agent follow-up
photoproof_bot_deflect: collection OK without photoproof_ ticket
photoproof_bot_checklist_complete_rate: % of conversations with 4 angles collected
photoproof_bot_blurry_retry_rate: blurry follow-ups before handoff
photoproof_bot_to_dmg_handoff_hours: delay set complete → resolution #363
Target: checklist_complete increasing and first_round_accept correlated with decrease in vague_resend #897.
PHOTOPROOFbot anti-patterns
Five common errors in proof guidance.
Checklist 4 angles same message: strict ONE-ANGLE-PER-TURN
Promising refund before set: NO-CLAIM-WITHOUT-SET
Ignoring blurry photo: BLURRY-RETRY before next slot
Validating without box: PROGRESSIVE-CHECKLIST packaging mandatory
Ignoring feed #897: PHOTOPROOF-FEED-LOOP guide_copy refused angles
PHOTOPROOFbot with Qstomy
Qstomy on Shopify: 4-angle slot engine, PHOTOPROOF-MAP sync #897, progressive widget guidance, blur check upload, context handoff #155, KPI photoproof_bot dashboard.
Scenario: DTC home decor, 22% dmg tickets with incomplete photos. Widget guidance + feed #897. photoproof_bot_first_round_accept_rate 76%, photoproof_ tickets -36% in 5 weeks.
Explore AI support and request a demo.
Checklist, FAQ and going further
PHOTOPROOFbot Checklist (8 steps)
Sync PHOTOPROOF-MAP #897: angles guide_copy blur rejection reasons
Policy PHOTOPROOFBOT-SUP: 6 rules GUIDE-GATE ONE-ANGLE PROGRESSIVE
8 intents bot_photoproof_*: flow PPB-1 to PPB-8
4 templates TPL-PHOTOPROOFbot-*: GUIDE-DAMAGE PACKAGING BLURRY SET-COMPLETE
angle_order: damage product box label configurable
Upload gate #896: format size before blur check
Red team broken parcel: detect → 4 guides not paved test
KPI Dashboard: photoproof_bot_* section 9 + delta photoproof_
FAQ
Difference #897?
#897 = agents validating criteria. #898 = bot guiding collection before validation.
Does the bot decide refunds?
No. NO-CLAIM-WITHOUT-SET. Handoff #363 after complete set.
Difference #896?
#896 = general attachment upload. #898 = 4-angle damage protocol.
How many blur retries?
Default 2. Then human handoff for partial slots.
Going further
This week: enable detect_damage, guide templates by angle, blur retry 2 max, measure photoproof_bot_first_round_accept_rate.
Enzo
July 1, 2026
