E-commerce
July 1, 2026
"The bot suggests a pickup point that does not exist on Rue de la Paix." "The AI says a change is possible even though the parcel is already at the locker." "Invented a 14-day storage limit, it is actually 7." Three failures where an ungrounded pickup point bot invents a pickup address or promises a post-label modification.
An e-commerce pickup point AI chatbot does not replace PICKPT agents (#515). It reads PICKPT-MAP, cites the official relay_lookup_url, explains pickup codes and storage_days, and refuses changes if the fulfillment stage is off-map.
This guide #516 covers intents bot_pick_pt_*, flow PICKPTbot, and KPI pickpt_bot. Pair bot of the PICKPT playbook (#515). New AI use case: relais carrier modify explain track without invented addresses.
Summary
Why automate parcel pickup points with a bot?
Relay questions arrive before and after pickup point delivery. A calibrated bot reads carrier relay status and PICKPT-MAP in seconds, without inventing a relay address or promising post-label changes.
What the bot resolves at tier 1
Change feasibility: change_allowed Y/N from map
Relay map link: official carrier relay_lookup_url
Storage countdown: storage_days exact collection deadline
Retrieval code: carrier PIN QR SMS explain FR
Saturated closed: saturated_action closed_action cited
Mondial Relay documents holding times and returns if not collected (Mondial Relay, FAQ 2026). The bot intercepts bot_pick_pt_change_request before the agent ticket.
PICKPTbot vs PICKPT #515, C&C #177 and WISMO
Four contents, four delivery collection layers.
Quick matrix
#516 PICKPTbot: bot relay change storage code tier 1
#515 PICKPT: agents reroute carrier ticket exception
#177 C&C: in-store pickup BOPIS
WISMO tracking: normal transit parcel status
Pipeline: bot_pick_pt feasibility quote → #515 carrier reroute if change confirmed or saturated exception.
Which bot_pick_pt_* intents should be configured?
Eight pick-up point bot intents.
Eight bot_pick_pt intents
bot_pick_pt_change_request: modify pick-up point after order
bot_pick_pt_relay_map: pick-up point map choose new point
bot_pick_pt_storage_deadline: how many days to collect parcel
bot_pick_pt_retrieval_code: explain PIN QR collection code
bot_pick_pt_saturated: full pick-up point what to do
bot_pick_pt_closed: closed pick-up point reroute explain
bot_pick_pt_not_arrived: parcel not yet at the pick-up point
bot_pick_pt_confirm_change: customer confirms → handoff #515
Tier 1 auto: change_request, relay_map, storage_deadline, retrieval_code, saturated, closed, not_arrived if carrier status API.
Intent bot_pick_pt_confirm_change, locker_size and storage_expired → agents #515 with payload order_id, relay_id, fulfillment_stage.
How do I consume PICKPT-MAP #515?
The bot reads PICKPT-MAP #515: carrier, fulfillment_stage, change_allowed, change_method, storage_days, saturated_action, closed_action, fees_paid_by, relay_lookup_url.
Lookup grounded
Order context: shipping line relay_id address CP
Carrier relay API: status at_relay closed saturated
PICKPT-MAP row: carrier + fulfillment_stage branch
Storage calc: at_relay_date + storage_days deadline
Map URL only: relay_lookup_url whitelist NO-RELAY-INVENT
Alignment anti-hallucination (#123): relay address = relay_lookup_url only.
PICKPTBOT-SUP policy in six rules
Six rules for a reliable relay point bot.
NO-RELAY-INVENT: never relay address outside of relay_lookup_url
PICKPT-MAP-GROUNDED: storage change fees from map only
VERIFY-RELAY-STATUS: carrier API before feasibility change
NO-CHANGE-PROMISE: change only if change_allowed Y map
STORAGE-CITE: storage_days exact countdown mandatory
REROUTE-HANDOFF: bot does not reroute, handoff #515 post-confirm
Flow PICKPTbot PPTB-1 to PPTB-8
Eight-step pick-up point bot flow.
PPTB-1 Classify: bot_pick_pt_* intent
PPTB-2 Context: order lookup relay_id carrier
PPTB-3 Relay status: carrier API at_relay closed saturated
PPTB-4 PICKPT-MAP: change_allowed storage_days actions
PPTB-5 Guardrail: NO-RELAY-INVENT NO-CHANGE-PROMISE
PPTB-6 Respond: TPL-PICKPTbot grounded
PPTB-7 Confirm handoff: client OK → #515 carrier ticket
PPTB-8 Log: storage_cited relay_url tag pickpt_bot
Example TPL-PICKPTbot-STORAGE
“Parcel at the relay [relay_name] since [date]. Collection before [deadline] ([storage_days] days). Code: SMS carrier. Map: [relay_lookup_url].”
Templates TPL-PICKPTbot and touchpoints
Four essential templates.
TPL-PICKPTbot-CHANGE
Relay change [change_allowed map]. Choose new point: [relay_lookup_url]. Fees: [fees_paid_by]. Confirm change?
TPL-PICKPTbot-SATURATED
Saturated relay. Action: [saturated_action]. New relay proposed by carrier within 24 hours. Tracking: [tracking_url].
TPL-PICKPTbot-CODE
Pickup code: Mondial Relay SMS or carrier app. 6-digit PIN + recipient name at the counter. No code? Check order number.
TPL-PICKPTbot-NOT-ARRIVED
Parcel in transit to relay [relay_name]. Status: [carrier_status]. ETA: [eta]. SMS notification upon arrival at the point.
Touchpoints
Checkout relay widget: bot_pick_pt_relay_map helps with choice
SMS at_relay webhook: auto bot_pick_pt_retrieval_code
Order status page: chip "Modify my relay"
Help center relay FAQ: bot embed storage countdown
Edge cases and reroutes
Five cases outside tier 1 bot.
Click & Collect #177: store pickup reroute distinct BOPIS
Address change #183: distinct home delivery relay
Parcel refused at relay: #511 REFDEL
Storage expired return: handoff #515 ops reship refund exception
Locker too small: handoff #515 home delivery fallback fee map
Bot does not modify Shopify relay_id directly: handoff #515 carrier API or ops ticket post-customer confirmation.
Essential pickpt_bot KPIs
Five PICKPTbot steering metrics.
pickpt_bot_auto_resolve: % tier 1 without agent
pickpt_bot_map_grounded_rate: answers compliant with PICKPT-MAP
pickpt_bot_relay_invent_violation: NO-RELAY-INVENT, target 0
pickpt_bot_storage_cited: % with storage_days deadline
pickpt_bot_handoff_change: sessions confirm → #515 reroute
Monthly red team: 10 prompts "relay street X invented", "guaranteed change shipped parcel", "30 days storage promised". Address out of map = NO-RELAY-INVENT violation.
PICKPTbot anti-patterns
Six common mistakes.
Invented relay: NO-RELAY-INVENT violation
Promised change post-label: NO-CHANGE-PROMISE
Invented storage days: PICKPT-MAP-GROUNDED
Confusing C&C #177: distinct carrier relay
Duplicating entire WISMO: relay focus only
Direct bot reroute: REROUTE-HANDOFF #515
PICKPTbot with Qstomy
Qstomy on Shopify + carrier relay API: detect pick_pt intent, PICKPT-MAP RAG, relay status lookup, storage countdown widget, relay_lookup_url embed, handoff #515 reroute.
Pipeline: bot relay explain → #515 carrier ticket → AI governance #142 audit relay claims.
Explore AI support and request a demo.
Checklist, FAQ and going further
PICKPTbot Checklist (8 steps)
Sync PICKPT-MAP #515: RAG bot whitelist only
Policy PICKPTBOT-SUP: 6 NO-RELAY-INVENT rules
8 intents bot_pick_pt_*: flow PPTB-1 to PPTB-8
4 templates TPL-PICKPTbot-*: CHANGE SATURATED CODE NOT-ARRIVED
Carrier relay API sync: closed saturated at_relay gate
Order status chip modify relay: bot_pick_pt entry
Red team 10 prompts: invented relay change shipped
Dashboard KPI: pickpt_bot_* section 9
FAQ
Difference #515?
#515 = agents reroute carrier ticket exception. #516 = bot tier 1 map storage code explain.
Difference #177 C&C?
#177 = brand store. #516 = third-party carrier relay network.
Bot direct relay change?
No. Confirm handoff #515 carrier API ops.
Lost pickup code?
TPL-PICKPTbot-CODE then carrier handoff if blocked.
Going further
This week: index PICKPT-MAP into bot corpus, test red team "invented relay", measure pickpt_bot_storage_cited. Activate chip modify relay order status page.
Enzo
July 1, 2026
