E-commerce
July 1, 2026
"The bot says immediate refund even though I just dropped it off at the locker." "The AI regenerates a label without checking my RMA." "Chatbot confuses parcel shop return and outgoing locker delivery." Three failures where a badly calibrated parcel shop return bot over-promises refunds or mixes up inbound and outbound flows.
An AI locker and parcel shop returns chatbot does not replace RETLOCK agents (#633). It reads RETLOCK-MAP, performs a lookup on the rma_status return tracking API, cites label_format deposit_proof, and hands off not_scanned refund disputes to humans.
This guide #634 covers intents bot_retlock_*, flow RETLOCKbot, and KPI retlock_bot. Pair bot of the RETLOCK playbook (#633). New AI returns use case: guide label deposit tracking without refunding or regenerating labels.
Summary
Why automate parcel pickup point returns using a bot?
"Where is my QR label?", "how do I drop off at the locker?" and "when is the refund?" come up as soon as a relay return RMA is created. A calibrated bot cites RETLOCK-MAP label_format refund_trigger_rule without promising refund or bot label regeneration.
What the tier 1 bot resolves
Explain model: customer_copy locker drop-off counter map
Label guide: label_format portal link cite
Drop-off procedure: deposit_steps compartment_size_rules map
Return tracking: return tracking status API cite
Refund timing info: refund_trigger_rule NO-REFUND-BEFORE-SCAN explain
Relay returns reduce tickets when scan_sla and proof of deposit are explained in the RMA email (Mondial Relay, 2026 Return FAQ). The bot intercepts bot_retlock_refund_timing before NO-REFUND violation.
RETLOCKbot vs RETLOCK #633, LOCKERbot #632, RETSHIPbot #510 and returns #10
Five contents, five distinct return and delivery flows.
Quick Matrix
#634 RETLOCKbot: tier 1 bot deposit label tracked handoff
#633 RETLOCK: agents proof not_scanned refund escalate carrier
LOCKERbot #632: outbound delivery distinct pickup code inbound return
RETSHIPbot #510: return fees who pays distinct deposit procedure
Returns bot #10: full RMA flow exchange refund
Pipeline: #10 eligible RMA → #510 fees if needed → #634 tier 1 deposit label → #633 proof refund execute.
Which bot_retlock_* intents should be configured?
Eight bot relay return intents mapped to locker_ret_* typologies #633.
Eight bot_retlock intents
bot_retlock_explain: customer_copy how works return_method map
bot_retlock_label: label_format portal link guide
bot_retlock_deposit_guide: deposit_steps compartment_size_rules map
bot_retlock_tracking: return tracking status transit API cite
bot_retlock_refund_timing: refund_trigger_rule scan_sla info
bot_retlock_proof_info: deposit_proof_type explain without validating ops
bot_retlock_compartment_help: fallback_if_full other point map
bot_retlock_handoff: not_scanned refund dispute → #633
Tier 1 auto: explain, label, deposit_guide, tracking, refund_timing if RETLOCK-MAP + rma API.
bot_retlock_handoff not_scanned lost claim refund execute → agents #633 payload rma_id proof photos.
How should RETLOCK-MAP #633 be consumed?
The bot reads RETLOCK-MAP #633: retlock_program_id, return_carrier_id, return_method_type, label_format, deposit_proof_type, scan_sla_hours, refund_trigger_rule, compartment_size_rules, fallback_if_full, customer_copy.
Lookup grounded
RMA retlock detect: return_method locker relay → RETLOCK-MAP row
CARRIER-DEPOSIT-VERIFY-BOT: return tracking API before deposit confirm cite
NO-REFUND-BOT: bot neither refunds nor confirms refund execute
NO-LABEL-REGEN-BOT: label regeneration handoff #633 only
NO-REFUND-BEFORE-SCAN-BOT: refund_timing info refund_trigger map only
LOCKER632-REROUTE-BOT: outbound delivery → #632 LOCKERbot distinct return
Alignment anti-hallucination (#123): label refund scan = RETLOCK-MAP + rma return API whitelist only.
RETLOCKBOT-SUP policy in six rules
Six bot rules for secure relay locker returns.
RETLOCK-MAP-GROUNDED: label deposit refund from map only
CARRIER-DEPOSIT-VERIFY-BOT: return tracking API before cite status
NO-REFUND-BOT: bot does not refund or confirm refund execute
NO-LABEL-REGEN-BOT: bot does not regenerate label execute ops
NO-REFUND-BEFORE-SCAN-BOT: refund_timing explain refund_trigger map only
NOT-SCANNED-HANDOFF-BOT: deposit dispute lost → #633 agents
RETLOCKbot RLB-1 to RLB-8 flow
Eight-step drop-off point bot flow.
RLB-1 Classify: bot_retlock_* intent detect
RLB-2 Collect: rma_id order_ref deposit question photos
RLB-3 RETLOCK-MAP: label deposit refund scan rules
RLB-4 RMA API: rma_status label_generated return tracking scan
RLB-5 Guardrail: NO-REFUND NO-LABEL-REGEN NO-REFUND-BEFORE-SCAN
RLB-6 Respond: TPL-RETLOCKbot grounded map API
RLB-7 Handoff: not_scanned refund dispute → #633
RLB-8 Log: intent retlock_program_id tag retlock_bot
Example TPL-RETLOCKbot-DEPOSIT
"Return [rma_id]: deposit [return_method_type map] [return_carrier_id map]. Label [label_format map] on parcel. [Locker: compartment [compartment_size_rules map], keep [deposit_proof_type map].] Scan within [scan_sla_hours map] hours. Refund: [refund_trigger_rule map info without executing]."
TPL-RETLOCKbot and touchpoints templates
Four essential templates.
TPL-RETLOCKbot-EXPLAIN
Return [rma_id] via [return_method_type map] : [customer_copy map]. Label [label_format map] return portal. Drop-off within [return_window_days map] d. Refund after [refund_trigger_rule map].
TPL-RETLOCKbot-LABEL
RMA [rma_id] : [label_format map] [lien portail map]. Print or mobile QR. Closed package labeled. Label regeneration: agent #633 if expired.
TPL-RETLOCKbot-DEPOSIT
Drop-off [return_method_type map] : [deposit_steps map]. Compartment [compartment_size_rules map]. Proof: [deposit_proof_type map]. If full: [fallback_if_full map]. Tracking: bot_retlock_tracking.
TPL-RETLOCKbot-HANDOFF
Request [not_scanned / refund execute / label regen / colis perdu] transmitted to return team. RMA [rma_id] order [order_ref]. Delay [handoff_sla map].
Touchpoints
Embedded return portal : bot_retlock_label entry
Email RMA label : bot_retlock_deposit_guide deep link
Return tracking widget : bot_retlock_tracking embed
Post-drop-off D+1 : bot_retlock_refund_timing proactive if no scan
Edge cases and reroutes
Five cases out of tier 1 bot return relay standard.
Refund execute requested: NO-REFUND-BOT handoff #633 RL-7
Label regen: NO-LABEL-REGEN-BOT agents #633 regenerate
Not scanned dispute: NOT-SCANNED-HANDOFF-BOT proof #633
Return fees question: bot_retship #510 reroute who pays
Locker delivery confused: LOCKER632-REROUTE-BOT outbound distinct
Bot never executes refund nor regenerates label: agents #633 workflow RL-7.
Essential retlock_bot KPIs
Five RETLOCKbot management metrics.
retlock_bot_label_deflect: label guide resolved without agent
retlock_bot_deposit_deflect: deposit guide resolved TPL-DEPOSIT
retlock_bot_refund_timing_deflect: refund_timing info resolved map
retlock_bot_handoff_rate: not_scanned refund dispute / total retlock bot
retlock_bot_refund_promise_violations: refund promised bot audit target 0
Target: retlock_bot_refund_promise_violations 0 and retlock_bot_label_deflect greater than 65% with RETLOCK-MAP sync.
RETLOCKbot anti-patterns
Five common errors bot return drop-off point.
Refund promised bot: NO-REFUND-BOT handoff #633
Label regenerated bot: NO-LABEL-REGEN-BOT agents only
Scan confirmed without API: CARRIER-DEPOSIT-VERIFY-BOT tracking lookup
Confusing outbound #632: LOCKER632-REROUTE-BOT distinct delivery
Refund before scan poorly explained: NO-REFUND-BEFORE-SCAN-BOT refund_trigger map
RETLOCKbot with Qstomy
Qstomy on Shopify: detect bot_retlock intent, RETLOCK-MAP RAG grounded, rma return tracking lookup, refund_trigger cite, handoff #633 not_scanned refund payload.
Pipeline: #634 bot explain label deposit tier 1 → #633 proof not_scanned refund escalate carrier.
Explore AI support and request a demo.
Checklist, FAQ and going further
RETLOCKbot Checklist (8 steps)
Sync RETLOCK-MAP #633: RAG bot parcel shop return portal
Policy RETLOCKBOT-SUP: 6 NO-REFUND NO-LABEL-REGEN rules
8 intents bot_retlock_*: flow RLB-1 to RLB-8
4 templates TPL-RETLOCKbot-*: EXPLAIN LABEL DEPOSIT HANDOFF
RMA return API: connect RLB-4 tracking scan status
Email RMA embed: bot_retlock_deposit_guide widget
Red team 10 prompts: refund promise label regen bot outbound confused
Dashboard KPI: retlock_bot_* section 9
FAQ
Difference #633?
#633 = agents proof not_scanned refund escalate carrier execute. #634 = bot tier 1 label deposit tracking handoff.
Bot confirms refund?
No. NO-REFUND-BOT refund_trigger_rule info only handoff #633.
Difference LOCKERbot #632?
#632 = outbound delivery collection code. #634 = inbound return parcel shop deposit RMA.
Deposited yesterday no scan?
TPL-RETLOCKbot-DEPOSIT scan_sla_hours map. If exceeded: bot_retlock_handoff #633.
Going further
This week: index RETLOCK-MAP RAG, connect rma return API bot, red team refund promise bot.
Enzo
July 1, 2026
