E-commerce
July 1, 2026
"The bot says my package has been picked up even though I'm standing in front of the locker." "The AI promises a free redelivery tomorrow without checking the expiration date." "The chatbot confuses an InPost locker with a post office pickup." Three failures where a poorly calibrated locker bot over-promises redelivery or invents a tracking status.
An AI locker pickup chatbot does not replace LOCKER agents (#631). It reads LOCKER-MAP, lookups the carrier tracking API, cites code_type retention_days, and hands off breakdown redelivery disputes to humans.
This guide #632 covers intents bot_locker_*, flow LOCKERbot, and KPI locker_bot. Pairs with the bot from the LOCKER playbook (#631). New AI delivery use case: guiding code and expiration without confirming pickup or redelivery.
Summary
Why automate pickup lockers with a bot?
"My PIN code doesn't work", "how long to withdraw?" and "the door won't open what should I do?" come up as soon as SMS notifications are received and on-site at the terminal. A calibrated bot references LOCKER-MAP retention_days code_type without promising redelivery or picked status bot.
What the bot resolves tier 1
Explain model: customer_copy code SMS retention map
Code support: code_type correct terminal locator reference
Parcel status: tracking available expired picked API reference
Location: locker_locator_url address GPS map
Breakdown guide: malfunction_escalate hotline without ticket promised bot
Locker networks reduce tickets when retention and code procedures are explained in the shipped SMS (InPost France, lockers 2026). The bot intercepts bot_locker_code_help before NO-PICKED-CONFIRM violation.
LOCKERbot vs LOCKER #631, POD bot #316, local delivery #291, and consignment shop #624
Five contents, five distinct delivery and pickup methods.
Quick matrix
#632 LOCKERbot: bot tier 1 code expiration locator handoff
#631 LOCKER: agents malfunction redelivery escalate carrier
POD bot #316: proof delivery signature distinct pickup locker
Local delivery #291: bike shop distinct slot auto locker
Consignment bot #624: CONSIGN distinct product package locker
Pipeline: bot explain code retention tier 1 → #631 malfunction redelivery lost escalate ops.
Which bot_locker_* intents should be configured?
Eight locker bot intents mapped to locker_* typologies #631.
Eight bot_locker intents
bot_locker_explain : customer_copy how works code retention map
bot_locker_code_help : code_type PIN QR terminal guide
bot_locker_status : tracking available expired picked API cite
bot_locker_retention : retention_days pickup_deadline cite
bot_locker_locator : locker_locator_url address GPS map
bot_locker_malfunction_guide : malfunction_escalate hotline guide
bot_locker_expired_info : expired_parcel_rule redelivery_policy info
bot_locker_handoff : breakdown redelivery dispute → #631
Tier 1 auto: explain, code_help, status, retention, locator, malfunction_guide if LOCKER-MAP + carrier API.
bot_locker_handoff redelivery execute wrong parcel dispute → agents #631 payload order_ref locker_id photos.
How to consume LOCKER-MAP #631?
The bot reads LOCKER-MAP #631: locker_carrier_id, code_type, retention_days, expired_parcel_rule, malfunction_escalate, tracking_status_map, redelivery_policy, locker_locator_url, customer_copy, sms_notification_template.
Lookup grounded
Order locker detect: shipping method locker → LOCKER-MAP row
CARRIER-STATUS-VERIFY-BOT: tracking API before available picked cite
NO-PICKED-CONFIRM-BOT: bot does not confirm pickup without picked API
NO-REDELIVERY-PROMISE-BOT: redelivery execute handoff #631 only
NO-CODE-REGEN-BOT: bot does not regenerate PIN carrier execute ops
CONSIGN624-REROUTE-BOT: consignment → #624 CONSIGNbot distinct logistics
Alignment anti-hallucination (#123): retention status code = LOCKER-MAP + carrier API whitelist only.
LOCKERBOT-SUP six-rule policy
Six bot rules for secure pickup lockers.
LOCKER-MAP-GROUNDED: retention code malfunction from map only
CARRIER-STATUS-VERIFY-BOT: tracking API status before citing
NO-PICKED-CONFIRM-BOT: bot does not confirm package picked up without API
NO-REDELIVERY-PROMISE-BOT: bot does not promise redelivery execute ops
NO-CODE-REGEN-BOT: code regeneration carrier handoff #631 only
MALFUNCTION-HANDOFF-BOT: door malfunction empty compartment dispute → #631
Flow LOCKERbot LKB-1 to LKB-8
Flow eight steps locker collection bot.
LKB-1 Classify: bot_locker_* intent detect
LKB-2 Collect: order_ref locker_id code terminal question photos
LKB-3 LOCKER-MAP: retention code malfunction locator rules
LKB-4 Carrier API: tracking status available expired picked locker_address
LKB-5 Guardrail: NO-PICKED NO-REDELIVERY NO-CODE-REGEN
LKB-6 Respond: TPL-LOCKERbot grounded map API
LKB-7 Handoff: malfunction redelivery dispute → #631
LKB-8 Log: intent locker_carrier_id tag locker_bot
Example TPL-LOCKERbot-CODE
"Order [order_ref] locker [locker_id]: status [tracking_status API map]. [If available: code [code_type map] valid until [pickup_deadline map]. Terminal: [locker_address map]. Map: [locker_locator_url map].] Bot does not confirm collection. Breakdown: [malfunction_escalate map]."
TPL-LOCKERbot templates and touchpoints
Four essential templates.
TPL-LOCKERbot-EXPLAIN
Locker delivery [locker_carrier_id map]: [customer_copy map]. Code [code_type map] by SMS upon deposit. Pickup within [retention_days map] days. Locate: [locker_locator_url map].
TPL-LOCKERbot-CODE
Status [tracking_status API]. [If available: enter [code_type map] on terminal [locker_address]. Deadline [pickup_deadline].] [If expired: [expired_parcel_rule map info]. Redelivery: agent #631.] Verify correct locker on [locker_locator_url].
TPL-LOCKERbot-MALFUNCTION
Locker incident [locker_id]: call [malfunction_escalate hotline map]. Do not force door. Order reference [order_ref]. Store team is following up within [handoff_sla map] via agent #631.
TPL-LOCKERbot-HANDOFF
Request [redelivery / empty compartment / code regen] transmitted to locker team. Order [order_ref] locker [locker_id]. Delay [handoff_sla map].
Touchpoints
SMS shipped deep link: bot_locker_code_help entry
Tracking page widget: bot_locker_status embed
Checkout locker picker: bot_locker_explain FAQ
Email J-1 expiration: bot_locker_retention reminder
Edge cases and reroutes
Five cases outside tier 1 standard locker bot.
Redelivery execute: NO-REDELIVERY-PROMISE-BOT handoff #631 LK-7
Empty compartment dispute: MALFUNCTION-HANDOFF-BOT POD #315 escalate
Code regen carrier: NO-CODE-REGEN-BOT agents #631 ops
Delay before locker deposit: bot delay shipping distinct incident locker
Human relay point confused: explain locker auto vs merchant counter
Bot never executes redelivery reship nor regenerates code: agents #631 workflow LK-7.
Essential locker_bot KPIs
Five LOCKERbot steering metrics.
locker_bot_code_deflect: help code resolved without agent
locker_bot_retention_deflect: info expiration resolved TPL-CODE
locker_bot_locator_deflect: localization resolved locator_url
locker_bot_handoff_rate: malfunction redelivery dispute / total locker bot
locker_bot_picked_promise_violations: confirmed pickup bot audit target 0
Target: locker_bot_picked_promise_violations 0 and locker_bot_code_deflect greater than 70% with LOCKER-MAP sync.
LOCKERbot anti-patterns
Five common pickup locker bot errors.
Picked up package confirmed bot: NO-PICKED-CONFIRM-BOT API only
Free redelivery promised bot: NO-REDELIVERY-PROMISE-BOT handoff #631
Regenerated code bot: NO-CODE-REGEN-BOT carrier ops only
Invented status: CARRIER-STATUS-VERIFY-BOT tracking API
Confusing consignment store: CONSIGN624-REROUTE-BOT #624 distinct
LOCKERbot with Qstomy
Qstomy on Shopify: detect bot_locker intent, LOCKER-MAP RAG grounded, carrier tracking lookup, retention cite, handoff #631 malfunction redelivery payload.
Pipeline: #632 bot explain code retention tier 1 → #631 malfunction redelivery lost escalate carrier.
Explore AI support and request a demo.
Checklist, FAQ and going further
LOCKERbot Checklist (8 steps)
Sync LOCKER-MAP #631: RAG bot checkout SMS shipped
Policy LOCKERBOT-SUP: 6 NO-PICKED NO-REDELIVERY rules
8 bot_locker_* intents: flow LKB-1 to LKB-8
4 TPL-LOCKERbot-* templates: EXPLAIN CODE MALFUNCTION HANDOFF
Carrier tracking API: connect LKB-4 available expired picked
SMS shipped embed: bot_locker_code_help deep link
Red team 10 prompts: promised pickup redelivery bot code regen
Dashboard KPI: locker_bot_* section 9
FAQ
Difference #631?
#631 = agents malfunction redelivery escalate carrier execute. #632 = bot tier 1 code expiration locator handoff.
Does the bot confirm the package has been picked up?
No. NO-PICKED-CONFIRM-BOT status picked API only handoff if there is a dispute.
Does the bot resend an expired code?
TPL-LOCKERbot-CODE expired_parcel_rule info. Redelivery execute agents #631.
Difference with local pick-up point?
Locker = 24h automated terminal PIN QR. Local shop pick-up = shopkeeper hours counter.
Go further
This week: index LOCKER-MAP RAG, connect carrier API bot, red team promised pickup bot.
Enzo
July 1, 2026
