E-commerce
July 1, 2026
"The bot sends a tracking screenshot, not a signature." "The AI invents a Colissimo signatory name." "Parcel delivered but the chatbot loops without a drop-off photo." Three failures where a WISMO bot poorly calibrated on POD generates false proof or ignores a DNR dispute.
An AI delivery proof chatbot does not replace POD agents (#527). It reads POD-MAP, retrieves AfterShip cache, redacts PII, and reroutes #529 DNR if there is a dispute.
This guide #528 covers bot_pod_* intents, the PODbot flow, and pod_bot KPIs. Pair bot of the POD playbook (#527). New AI use case: finding a photo signature or pickup point scan without an invented POD.
Summary
Why automate proof of delivery with a bot?
"Send proof of delivery" often comes after a delivered WISMO status. A calibrated bot reads POD-MAP, fetches carrier cache, and shares the redacted document without inventing a signature.
What the bot solves in tier 1
POD admin: signature photo for customer file
POD cache hit: AfterShip API delivered event attachment
POD delay: retrieval_sla_hours quoted if not yet available
Relay scan: drop-off point Mondial Relay locker info
Dispute routing: pod_request_dispute → #529 DNR handoff
AfterShip and 17track expose POD depending on the carrier (AfterShip, Tracking API 2026). The bot intercepts bot_pod_request before generic tracking capture.
PODbot vs POD #527, DNR #529, WISMO #184 and lost parcel
Five types of content, five layers of delivery disputes.
Quick Matrix
#528 PODbot: bot retrieve redact POD tier 1
#527 POD: agents portal pro carrier claim
#529 DNR: delivered not received replace refund
WISMO #184: tracking status before delivered
Lost parcel: carrier claim thresholds
Router: delivered + proof request → #528. Customer denies receipt after POD → #529 DNR. Not yet delivered → #184 WISMO.
Which bot_pod_* intents should be configured?
Eight proof of delivery bot intents.
Eight bot_pod intents
bot_pod_request: send proof of delivery signature
bot_pod_signature: who signed for my package
bot_pod_photo: photo of delivered package drop-off
bot_pod_pickup_point: scan pickup point locker
bot_pod_not_received: delivered but not received, proof first
bot_pod_delay: proof not yet available SLA
bot_pod_untracked: without tracking manifest WMS
bot_pod_escalate: complex dispute handoff #527 or #529
Tier 1 auto: request, signature, photo, pickup_point, delay if POD cache hit and POD-MAP lookup.
Intent bot_pod_not_received and bot_pod_escalate → handoff #529 DNR with payload pod_attachment dispute_flag.
How should POD-MAP #527 be consumed?
The bot reads POD-MAP #527: carrier_code, pod_type, retrieval_method, retrieval_sla_hours, customer_shareable, redact_fields, dispute_routing, claim_parallel, fallback_proof.
Lookup grounded
Order lookup: fulfillment delivered_at tracking carrier
POD-MAP row: carrier_code + service level
Delivered gate: if not delivered → reroute #184
Cache fetch: AfterShip pod_url attachment API
Redact pipeline: redact_fields before chat delivery
Alignment anti-hallucination (#123): never POD outside carrier API or cache.
PODBOT-SUP policy in six rules
Six rules for secure proof of delivery.
NO-FAKE-POD: never use an invented signature photo
POD-MAP-GROUNDED: retrieve via map retrieval_method
REDACT-PII: auto-mask neighbor name and third-party address
DNR-REROUTE: bot_pod_not_received → #529 after POD share
DELIVERED-GATE: POD only if fulfillment delivered
SLA-CITE: retrieval_sla_hours on cache miss
Flow PODbot PODB-1 to PODB-8
Flow eight steps bot proof of delivery.
PODB-1 Classify : bot_pod_* intent
PODB-2 Order lookup : fulfillment delivered_at carrier
PODB-3 Delivered gate : not delivered → #184 reroute
PODB-4 POD-MAP : pod_type retrieval sla shareable
PODB-5 Fetch : cache AfterShip or async carrier ticket
PODB-6 Redact : REDACT-PII pipeline
PODB-7 Respond : TPL-PODbot attachment or SLA delay
PODB-8 Log : pod_type tag dispute routing escalate
Example TPL-PODbot-SIGNATURE
“Colissimo proof: delivered on [delivered_at], signed by [signatory_redacted]. Attachment below. Package missing? Check with neighbors in the next 24 hours or say NOT RECEIVED to launch an investigation.”
TPL-PODbot templates and touchpoints
Four essential templates.
TPL-PODbot-SIGNATURE
Delivered [delivered_at]. Signed [signatory_redacted]. [pod_attachment_redacted].
TPL-PODbot-PHOTO
Drop-off photo [delivered_at]. Location [location_redacted]. [pod_attachment_redacted].
TPL-PODbot-DELAY
Delivery confirmed [delivered_at]. Proof available in [retrieval_sla_hours] h. Auto email upon carrier receipt.
TPL-PODbot-DISPUTE
Proof attached. Delivered-not-received inquiry launched. Check neighboring lockers. Return delay [dnr_sla].
Touchpoints
WISMO delivered branch: "View proof of delivery" chip
Chargeback warning: bot_pod_request priority queue
Proactive POD cache: webhook delivered → pre-fetch
Email follow-up: bot_pod_delay notify when ready
Edge cases and reroutes
Five cases outside tier 1 bot.
Not yet delivered: DELIVERED-GATE reroute #184 WISMO
Dispute confirmed: DNR-REROUTE #529 replace refund flow
Split shipment: POD by fulfillment, handoff #527
No tracking: #525 NOTRACK fallback_proof manifest WMS
Delivery refused: POD return to sender #511
Bot does not create carrier claim: handoff #527 if claim_parallel required and dispute not resolved tier 1.
Essential pod_bot KPIs
Five PODbot management metrics.
pod_bot_auto_resolve: % tier 1 cache hit without agent
pod_bot_retrieve_rate: POD obtained compliant with POD-MAP
pod_bot_fake_pod_violation: NO-FAKE-POD, target 0
pod_bot_dnr_reroute: sessions → #529 dispute
pod_bot_redact_compliance: PII masked before sending, 100% target
Monthly red team: 10 prompts "invent Dupont signature", "photo of package at my home without API". POD outside carrier cache = NO-FAKE-POD violation.
PODbot anti-patterns
Six common mistakes.
Generic tracking capture: not a POD
Invented signature: NO-FAKE-POD violation
Unredacted PII: neighbor's name, third-party address
Ignoring dispute intent: DNR-REROUTE #529
POD before delivered: DELIVERED-GATE
Confusing lost package: POD first, lost second
PODbot with Qstomy
Qstomy on Shopify: WISMO delivered POD branch, POD-MAP RAG, AfterShip cache webhook, redact PII auto, handoff #529 DNR payload, escalate #527 carrier claim.
Pipeline: bot retrieve POD → #529 DNR if dispute → #527 carrier claim → AI governance #142 audit POD claims.
Explore AI support and request a demo.
Checklist, FAQ and going further
PODbot Checklist (8 steps)
Sync POD-MAP #527: RAG bot whitelist only
Policy PODBOT-SUP: 6 NO-FAKE-POD REDACT-PII rules
8 intents bot_pod_*: flow PODB-1 to PODB-8
4 templates TPL-PODbot-*: SIGNATURE PHOTO DELAY DISPUTE
AfterShip cache webhook: pre-fetch delivered POD
Redact pipeline: redact_fields auto
Red team 10 prompts: invented signature forbidden
KPI Dashboard: pod_bot_* section 9
FAQ
Difference #527?
#527 = agents portal pro carrier claim. #528 = bot tier 1 cache retrieve.
Difference DNR #529?
#528 shares POD. #529 resolves delivered not received dispute.
Does bot send raw POD?
No. REDACT-PII mandatory before chat or email.
POD not in cache?
TPL-PODbot-DELAY mentions retrieval_sla_hours, notify async.
Going further
This week: index POD-MAP in bot corpus, configure AfterShip delivered webhook pre-fetch, test redact PII pipeline, measure pod_bot_retrieve_rate.
Enzo
July 1, 2026
