E-commerce
July 1, 2026
"Which slot did I choose exactly?" "Can I switch from Thursday to Friday?" "The delivery person did not show up in my 2pm-6pm window." Three messages where a customer without a lookup slot self-service opens a ticket even though SLOT-MAP and order metafield already contain the answer.
An e-commerce delivery slot AI chatbot does not replace SLOT-FLOW agents (#427). It reads SLOT-MAP, quotes the confirmed window, guides portal modification before the deadline, explains the missed policy, and routes slot_missed P1 to pre-filled agents.
This guide #428 covers intents bot_slot_*, flow SLOT-BOT, and KPI slot_bot. Distinct from slot customer service (#427) and the express bot (#339): here, delivery scheduling AI use case: zip code availability, slot modification, and D-1 reminder.
Summary
Why does a slot bot reduce delivery slot tickets?
An avoidable delivery slot ticket is created when the customer cannot find their confirmed window, does not know until when they can modify it, or is unaware of the missed slot procedure before writing to support.
Five botifiable slot ticket triggers
Confirm lookup: what day/time did I choose
Modify request: change date or window post-purchase
Availability CP: possible slots for my postal code
Fee explain: misunderstood premium surcharge
Missed policy: what to do if courier is outside the window
Shopify allows delivery dates and slot apps via checkout extensions (Shopify, delivery dates 2026). Metapack estimates that 40-55% of pre-delivery scheduled inquiries concern slot confirmation or modification resolvable by grounded FAQ without an agent (Metapack, scheduled delivery 2026).
Angle #428 vs related content
CS slot #427: SLOT-FLOW refund execute carrier claim. #428 = bot tier 1 lookup modify explain D-1 reminder.
Express #338: cut-off speed tomorrow. #428 = chosen time window Thursday 2pm-6pm.
Bot express #339: pre-purchase eligibility go/no-go. #428 = post-purchase slot confirm modify.
Bot shipping #203: general shipping FAQ. #428 = dedicated intents bot_slot_* scheduling.
Perishables #313: slot_fresh mandatory CS. #428 = bot cites slot_fresh windows, handoff fresh P1 #427.
DTC Example
Gourmet grocery + furniture, 280 slot orders/month, 38 tickets baseline #427. After SLOT-BOT: slot_bot_resolution 83%, slot_ticket_delta -46%, slot_j1_reminder_open_rate 41%.
D-1 reminder bot vs email only
Email D-1 slot only: 22% open rate. Bot link D-1 in SMS + order status widget: slot_confirm_missing tickets -38% vs email-only cohort.
Tidio deflection slot tier 1
Tidio estimates that a tier 1 scheduled delivery bot reduces slot_confirm_missing and slot_modify_request by 42-55% vs static FAQ alone (Tidio, chat stats 2026).
How does SLOT-BOT differ from SLOT-FLOW #427?
Self-service slot bot and agent playbook slot: two layers on SLOT-MAP #427.
Bot slot → role matrix
#428 SLOT-BOT: lookup confirm, modify link, availability CP, fee explain, D-1 reminder, missed policy cite
#427 SLOT-FLOW: modify WMS execute, refund fee, carrier claim, fresh P1 refund full
#339 EXPRESS-BOT: pre-purchase cut-off tomorrow
#183 address: address change reset slot zone
Router upstream
"Which slot", "modify Friday", "available slots 75011", "premium fees", "reminder tomorrow" → SLOT-BOT. "Missed slot refund", "damaged fresh", "slot chargeback", "modify after WMS dispatch" → handoff #427 SL-6 execute. "Express tomorrow?" → #339.
SLOT-BOT Data
SLOT-MAP JSON #427, order slot_id metafield, slot_datetime, slot_type, modify_deadline, fulfillment status, carrier_confirm, slot_fee line item.
Promise #428
SLOT-BOT Policy, 12 intents bot_slot_*, flow SB-1 to SB-8, guardrails no refund execute, KPI slot_bot_*.
Pre-purchase vs post-purchase bot scope
bot_slot_availability CP: visitor or cart without order. bot_slot_confirm_lookup: auth order required. Do not mix the two SB-2 flows.
Oversize RDV bot boundary
slot_oversize carrier phone D-2: bot cites RDV policy SLOT-MAP. Phone rescheduling → handoff #427 slot_oversize_rdv, not bot API call.
Which bot_slot_* intents should be configured?
Twelve delivery slot bot intents cover tier 1 pre-delivery and post-missed policy.
Twelve bot_slot intents
bot_slot_confirm_lookup: confirmed window order lookup
bot_slot_modify_request: change slot, self-service portal link
bot_slot_modify_deadline: until when to modify
bot_slot_availability: checkout preview area zip-code slots
bot_slot_not_available: zip-code out of area, standard ETA
bot_slot_fee_explain: premium weekend fee SLOT-MAP
bot_slot_reminder_j1: proactive day-before delivery reminder
bot_slot_tracking_window: courier in window today
bot_slot_missed_policy: explain missed_policy, do not execute refund
bot_slot_fresh_requirement: slot_fresh mandatory windows
bot_slot_handoff_427: missed P1, modify denied shipped, chargeback
bot_slot_route_express: express #338 vs slot choice redirect
Session tags
slot_bot, slot_bot_confirm, slot_bot_modify, slot_bot_resolved, slot_bot_handoff_427, slot_bot_j1. Distinct express_bot, wismo_bot, tick_bot.
Triggers T1-T5
T1: proactive confirmation page slot order SLOT-CONFIRM cite. T2: keyword slot/window/delivery Thursday/modify. T3: order status widget slot_display. T4: /pages/delivery-slots FAQ. T5: slot_date=tomorrow proactive J-1 reminder.
How to apply the SLOT-BOT flow in eight steps?
The SLOT-BOT flow guides grounded slots SLOT-MAP #427 and order slot metafield.
Eight steps SB-1 to SB-8
SB-1 Welcome: "I am checking your slot: date, window, possible modification."
SB-2 Auth context: order_id + email post-purchase | zip code only pre-purchase availability
SB-3 Classifier intent: bot_slot_* section 3
SB-4 Match SLOT-MAP: zone, slot_type, modify_deadline, missed_policy, slot_fee
SB-5 Read order slot: slot_datetime, fulfillment, carrier_confirm
SB-6 Respond: SLOT-CONFIRM style | modify link | SLOT-UNAVAIL | missed policy explain
SB-7 CTA: modify portal | /pages/delivery-slots | tracking link
SB-8 Close/handoff: refund execute | fresh P1 | chargeback → #427 SL-6
SB-5 confirm_lookup
If slot_datetime metafield present → bot_slot_confirm_lookup cite day window address deadline modify. If absent but slot_type standard → explain ETA without window SLOT-UNAVAIL variant.
SB-6 modify_request
If unfulfilled + before modify_deadline → deep link order status modify button + bot_slot_modify_deadline cite. If shipped or past deadline → bot_slot_handoff_427 SLOT-MODIFY-DENY explain + carrier phone oversize.
SB-6 missed_policy
bot_slot_missed_policy cite missed_policy refund fee timeline. Keyword "rembourser maintenant" → handoff #427 slot_missed SL-6 execute.
SB-5 tracking_window today
If slot_date=today + tracking in_transit → cite window + carrier ETA live link. If window passed + no delivery → bot_slot_handoff_427 P1 slot_carrier_no_show.
Split shipment multi-slot
Multi-package: SB-5 list each line slot. Link split (#356) explain policy upfront.
Which SLOT-BOT policy should be documented?
The SLOT-BOT slot bot policy governs lookup, modify link, and handoffs.
Eight SLOT-BOT rules
SLOT-MAP only: windows, fees, deadlines from JSON #427
Auth before confirm: order_id + email before slot_datetime quoted
Modify link not execute: self-service portal if eligible, not WMS bot API
Missed explain only: quote missed_policy, handoff #427 refund execute
No slot invent: bot_slot_not_available if postal code excluded, no fictitious slot
Fresh handoff P1: slot_fresh_violation keyword → #427 SL-6 full refund path
Address change reset: #183 change invalidates slot → re-offer availability or handoff
Max 6 turns slot admin: then portal CTA or handoff #427
RAG corpus sources
/pages/delivery-slots, SLOT-MAP #427, SLOT-SUP #427, macros SLOT-CONFIRM SLOT-UNAVAIL from #427 section 7.
Sync ops
SLOT-MAP zone postal code update → bot glossary same hour. Carrier partner suspend slot zone → bot_slot_not_available auto boost.
Monthly review
Audit: wrong window quoted, refund promise bot, missed handoff skipped, availability hallucination postal code.
Premium fee transparency
bot_slot_fee_explain always quote checkout line item amount. Reduce slot_fee_dispute handoffs.
Holiday slot capacity bot
Peak holidays: bot_slot_availability may show limited windows. Proactive SLOT-UNAVAIL + standard ETA better than checkout surprise empty calendar.
What guardrails protect modify and refunds?
The authorized vs. forbidden bot slot matrix protects WMS ops and finance.
Authorized bot actions
Lookup slot_datetime confirm cite SLOT-CONFIRM format
Cite SLOT-MAP windows fees modify_deadline missed_policy
Deep link order status modify portal if eligible
bot_slot_availability CP preview from SLOT-MAP zones
Send D-1 reminder bot_slot_reminder_j1 proactive T5
Explain missed policy timeline refund fee process
Handoff #427 P1 missed fresh chargeback modify denied
Forbidden bot actions
Execute WMS reslot API direct bot
Process Shopify partial refund slot fee
Promise slot CP if SLOT-MAP excludes zone
Override modify_deadline without agent
Fresh full refund execute bot
Open carrier claim bot API
Modify portal vs bot execute
Self-service modify through checkout app Zapiet/Delivery Scheduler : bot links only. Bot never calls carrier reslot if policy requires agent WMS validation oversize.
Chargeback slot keyword
Litigation threat + slot_missed → immediate handoff #427 slot_chargeback fields pre-filled. Bot zero refund promise.
Address stale slot
If #183 address changed after slot booked : bot explain slot reset, offer bot_slot_availability new CP or handoff modify.
How to integrate SLOT-MAP #427 and Shopify slot apps?
The Shopify slot bot integration combines SLOT-MAP, order metafields, and app scheduler.
SLOT-BOT read fields
order metafield slot_id: app scheduler reference
slot_datetime: ISO start end window display
slot_type: standard, premium, fresh, oversize
modify_deadline: computed D-N before slot
fulfillment_status: unfulfilled gate modify link
slot_fee line: premium amount checkout
Shopify checkout extensions + Zapiet apps, Delivery Scheduler (Shopify, delivery dates 2026).
SLOT-MAP bot layer
Import #427 JSON: slot_zone CP ranges, window_options, modify_deadline rules, missed_policy, carrier. SB-4 per order shipping CP or visitor CP input.
Modify portal deep link
TB-7 equivalent: order status URL with modify=true param if app supports. Reduces slot_modify_request tickets by 35-50% per #427 self-service KPI.
Carrier confirm webhook
carrier_confirm true → bot_slot_confirm_lookup adds “confirmed carrier” badge. False pending → explain 24h confirmation delay.
Multi-address orders
Each fulfillment address separate slot lookup SB-2 disambiguate line. Prevent wrong window cite multi-ship orders.
Shopify Qstomy Integration
See Shopify integration for order metafield read + RAG /pages/delivery-slots sync.
What are the D-1 reminder and UX triggers for SLOT-BOT?
The UX SLOT-BOT deployment maximizes delivery week deflection.
Five widget placements
Slot order confirmation: T1 proactive SLOT-CONFIRM mentions
/pages/delivery-slots: T4 FAQ availability PC
Order status page: T3 modify button + bot widget
SMS D-1 slot reminder: T5 bot link confirm modify
Checkout slot step: bot_slot_availability PC preview pre-pay
D-1 SMS bot link
Klaviyo D-1: bot_slot_reminder_j1 + modify deadline CTA if still eligible. Reduce slot_confirm_missing and slot_modify_request day-of historical 32%.
D-0 tracking window path
slot_date=today sessions auto-priority bot_slot_tracking_window. Window passed no delivery → bot_slot_handoff_427 P1 pre-fill SL-4 fields #427.
Fresh slot_fresh proactive
slot_type fresh: T5 morning D-0 "fresh delivery today [window]" reduce anxiety cold chain.
A/B test
T5 D-1 SMS bot link vs email only: slot_bot_resolution + slot_confirm_missing delta 4 weeks.
Pre-purchase availability widget
PDP "slots available my PC?" bot_slot_availability before add cart. Complement #339 express eligibility not replace slot choice.
Order status embed bot chip
Chip "My slot" on tracking page routes bot_slot_confirm_lookup T3. Highest intent match rate placement post-purchase.
Which slot bot KPIs should be measured?
The delivery slot bot KPIs link deflection and self-service modification.
Eight key metrics
slot_bot_resolution_rate: resolved without handoff / slot_bot sessions
slot_ticket_delta: decrease in #427 tickets vs baseline
slot_confirm_self_service_rate: confirm lookup bot / confirm questions
slot_modify_link_convert: modification portal clicks / modification intents
slot_j1_reminder_open_rate: bot opens Day-1 / SMS sent
slot_handoff_427_rate: missed modification denied routed agents
slot_availability_bot_rate: postal code availability resolved pre-purchase
slot_bot_csat: satisfaction tag slot_bot resolved
DTC Benchmark
slot_bot_resolution 78-88%, slot_ticket_delta -40-50%, slot_modify_link_convert > 45%, slot_bot_csat > 4.2/5.
Weekly dashboard
Intent breakdown, postal code zone top availability, handoff reasons missed vs modification denied, Day-1 funnel.
Transcript audit
20 sessions/month: window always grounded metafield, no refund bot promise, handoff #427 triggered correctly.
Correlation missed rate
Track slot_missed_rate ops vs slot_bot_missed_policy sessions. Bot explains quality before handoff.
Modify self-service funnel KPI
Track bot modify intent → portal click → modify success WMS. Full funnel identifies broken deep link vs policy deny confusion.
Which anti-patterns should be avoided on slot bots?
Ten delivery slot bot anti-patterns to ban.
1. Refund fee promise bot missed
Rule 4 explain only. Execute #427 SL-7 partial refund agents.
2. WMS reslot execute bot
Rule 3 modify portal link only. Agent WMS oversize #427.
3. Inventer créneau CP excluded
Rule 5 SLOT-UNAVAIL grounded. No Saturday slot hallucination if SLOT-MAP excludes.
4. Confirm sans auth order
Rule 2 order_id + email before slot_datetime cite privacy.
5. Fresh violation bot refund full
Rule 6 handoff #427 SLOT-FRESH-P1 agents only.
6. Confondre express #339
bot_slot_route_express redirect tomorrow cut-off ≠ Thursday 2pm-6pm window.
7. Skip SLOT-SUP #427 prérequis
/pages/delivery-slots SLOT-MAP before bot launch. Empty RAG = wrong answers.
8. Modify promise after ship
SB-6 check fulfillment. Shipped → SLOT-MODIFY-DENY handoff not false hope.
9. Stale SLOT-MAP zone
Sync CP ranges same hour ops. Wrong availability = checkout frustration.
10. Conversation 12 tours
Max 6 turns rule 8. Portal modify CTA SB-7.
11. Split shipment single slot cite
Multi parcels: list each line slot. Wrong package window cite = trust loss.
12. Address change ignore slot reset
#183 change must trigger slot zone re-check bot or handoff.
13. Carrier API latency bot
If carrier_confirm pending > 24 h : bot explain delay, no false confirm badge. Stale carrier_confirm worse than honest pending state.
How does Qstomy manage availability, modifications, and slot reminders?
Qstomy on Shopify: SLOT-BOT order lookup, SLOT-MAP zone availability, modify portal deep link, D-1 proactive reminder, missed policy explain, handoff #427 pre-filled fields slot_missed modify denied.
Qstomy slot bot capabilities
slot_order_lookup: SB-2 slot_datetime type deadline
slot_map_availability: PC preview windows fees
slot_modify_link: portal if eligible unfulfilled
slot_j1_reminder: T5 proactive SMS widget
slot_missed_explain: policy cite handoff trigger
slot_handoff_427: P1 fields SL-4 pre-fill
Pipeline #428 → #427
Bot tier 1 confirm modify availability reminder. Agents refund WMS carrier claim fresh P1. Shared SLOT-MAP.
Encrypted DTC Scenario
Grocery + furniture 280 slot orders/month, 38 baseline tickets.
After Qstomy SLOT-BOT: slot_bot_resolution 85%, slot_ticket_delta -48%, slot_modify_link_convert 52%, slot_bot_csat 4.4/5.
Explore customer support and request a demo.
Training corpus sync
See train Shopify chatbot for SLOT-MAP RAG sync on zone PC update webhook.
What is the checklist for deploying SLOT-BOT?
SLOT-BOT Checklist (12 steps)
Validate SLOT-SUP #427 + SLOT-MAP /pages/delivery-slots
Export SLOT-MAP JSON → bot glossary per slot_zone
Configure 12 intents bot_slot_* section 3
Implement flow SB-1 to SB-8 + order metafield read
Activate guardrails no refund/modify execute + fresh P1 handoff
Route slot vs #427 #339 #203 express
Placements confirmation + order status T3 + /pages/delivery-slots T4
Triggers T5 D-1 SMS bot link + checkout availability pre-purchase
Staging tests 8 scenarios: confirm, modify link, deadline deny, availability CP, fee explain, D-1 reminder, missed policy, handoff missed
Modify portal deep link + fulfillment gate
Dashboard KPI slot_bot weekly + handoff audit
A/B T5 D-1 SMS bot vs email 4 weeks
At a glance
#428 = bot slots tier 1, #427 agents execute refund WMS
SLOT-MAP grounded: windows, fees, deadlines, missed policy
SLOT-BOT: lookup → modify link → D-1 reminder → handoff
No refund bot: explain missed, handoff #427 execute
KPI slot_bot_resolution: target > 80 %
FAQ
Difference with #427?
#427 CS modify execute refund carrier claim. #428 bot confirm modify link availability D-1 reminder.
Does the bot modify the slot directly?
No. Portal deep link self-service if eligible. WMS reslot agents #427.
Missed slot refunded by bot?
No. bot_slot_missed_policy explain timeline. Refund fee execute #427 SL-7.
Express vs slot?
bot_slot_route_express → #339 cut-off. #428 selected time window post slot checkout.
Fresh product mandatory slot?
bot_slot_fresh_requirement quote slot_fresh windows. P1 violation → handoff #427.
Go further
This week: sync SLOT-MAP bot per CP zone, configure SB-5 order metafield staging, test modify portal link path, activate widget D-1 SMS T5.
Share this guide #428 with ops and support: a bot that quotes Thursday 2pm-6pm at 10pm is worth ten avoided slot_confirm_missing tickets the next morning.
Multi-parcel different slots?
SB-5 list each package slot. Split policy #356 explain upfront checkout.
Enzo
July 1, 2026
