E-commerce

How to handle customer questions about delivery slots

How to handle customer questions about delivery slots

July 1, 2026

"I had chosen Thursday 2pm-6pm, the delivery driver came on Friday." "How do I change my slot after ordering?" "No slots available at checkout, is this normal?" Three messages where a badly managed delivery slot generates disputes, negative reviews, and post-delivery chargebacks.

E-commerce delivery slot customer support covers checkout choice, post-purchase modification, slot confirmation, missed carrier slot, and associated fees, distinct from express cut-off or generic ETA.

This guide #427 covers policy SLOT-SUP, flow SLOT-FLOW, and KPI slot. Complements ETA and express. Distinct from express delivery (#338) and address change (#183): here, customer service playbook for chosen or modified delivery time windows.

Summary

Why do delivery slot tickets increase after purchase?

A delivery slot ticket concerns a time window chosen or expected by the customer that the carrier, the warehouse, or the checkout did not respect or make visible.

Five typical customer pain points

  • Missed slot: delivery outside the chosen window

  • Modification refused: changing the date/time post-order

  • No checkout slot: empty calendar, zip code excluded

  • Missing confirmation: customer no longer knows which slot was chosen

  • Slot fees: misunderstood premium surcharge

Shopify allows displaying estimated delivery dates and slot apps via checkout extensions and shipping profiles (Shopify, delivery dates 2026). Metapack estimates that 38-52% of fresh/furniture delivery disputes relate to an unfulfilled slot when the window is not confirmed by email (Metapack, scheduled delivery 2026).

Angle #427 vs related content

  • Express #338: cut-off next-day speed. #427 = chosen time window (e.g., Thursday 2pm-6pm).

  • Address change #183: post-order address. #427 = slot date/time, not street.

  • Perishables: mandatory slot fees. #427 = cross-functional view of all slot products.

  • Local delivery #429: future hyperlocal zone. #427 = general carrier scheduled slot.

  • Bot slots #428: future AI automation. #427 = customer service playbook for agents.

DTC Example

Gourmet grocery + furniture, 320 slot orders/month. Without SLOT-SUP: 41 slot tickets/month, slot_missed_rate 19%. After playbook: slot_ticket_rate -44%, slot_modify_sla_compliance 94%, slot_csat 4.2/5.

Cost of slot_missed dispute

1 untreated P1 fresh slot_missed = full refund + stock loss. SLOT-SUP ROI: auto fee refund + claim carrier recover 30-40% premium fees.

How does créneau differ from express and standard ETA?

Selected delivery window, express cut-off, and ETA range: three distinct delivery promises.

Promise Matrix → dominant ticket

  • Delivery slot #427: selected window, modify, missed

  • Express #338: tomorrow if before cut-off, no choice of time

  • Standard ETA: 3-5 business days, no window

  • Click & Collect: in-store pickup, no home delivery

Four SLOT-TYPES

  • slot_standard: 2 h window carrier (2pm-4pm)

  • slot_premium: evening/weekend, fee +5-15 €

  • slot_fresh: fresh/meat, mandatory slot

  • slot_oversize: 2-person furniture, telephone appointment

Delivery slot stack

Checkout app (Zapiet, Delivery Scheduler), TMS Onfleet/Bringg, carrier Colissimo slot, WMS export slot_id. Support reads slot_datetime, slot_status, carrier_confirm.

Promise #427

Policy SLOT-SUP, matrix SLOT-MAP, 12 slot_* typologies, flow SLOT-FLOW, SLOT-* macros, slot_* KPIs.

Checkout app vs native carrier

Zapiet/Delivery Scheduler vs Colissimo slot API. SLOT-MAP tick_app field for agent SL-4 lookup path.

Which slot_* typologies should be mapped?

Twelve delivery slot ticket typologies for consistent routing.

Twelve slot scenarios

  1. slot_missed: delivery outside confirmed window

  2. slot_modify_request: change date/time post-purchase

  3. slot_not_available: no slot checkout PC

  4. slot_confirm_missing: customer cannot find chosen slot

  5. slot_fee_dispute: disputed premium surcharge

  6. slot_carrier_no_show: slot passed, package absent

  7. slot_partial_delivery: multi-package, different slots

  8. slot_fresh_violation: fresh product delivered in wrong slot

  9. slot_oversize_rdv: furniture, carrier call required

  10. slot_address_conflict: address changed #183 + slot stale

  11. slot_app_bug: checkout slot not exported WMS

  12. slot_chargeback: threat of litigation missed slot

Helpdesk tags

slot, slot_missed, slot_modify, slot_refund, slot_resolved, slot_escalation. Distinct express_miss, wismo, address_change.

Prioritization

P1: slot_missed fresh, carrier_no_show today, chargeback. P2: modify_request before ship, confirm_missing. P3: fee_dispute, not_available FAQ.

Mining slot verbatims

90-day export "slot", "range", "2 pm", "courier did not come". Prioritize macros on top 3 real shop typologies.

Which SLOT-MAP matrix should be documented?

The SLOT-MAP slot matrix lists zones, windows, fees, and modifications.

SLOT-MAP Columns

  • slot_zone: ZIP ranges, countries, exclusions

  • slot_type: standard, premium, fresh, oversize

  • window_options: Mon-Fri 8am-8pm, Sat 9am-1pm

  • modify_deadline: Day-N before slot, before shipping

  • slot_fee: premium +X €, free shipping conditions

  • carrier: Colissimo, Chronopost, 3PL own fleet

  • missed_policy: refund fee, redelivery, partial

Example slot_fresh fees

slot_fresh_idf: mandatory slot Wed-Fri 8am-1pm, no Sunday delivery. Missed fresh → full refund + priority redelivery P1.

Example furniture slot_oversize

slot_oversize_fr: 4-hour window, phone appointment Day-2, modify until Day-3. Missed → carrier claim + partial refund fee per PART-REF #368.

Publication /pages/delivery-slots

SLOT-MAP FAQ: zones, modify slot, premium fees, what to do if missed. Link to SLOT-* macros.

Premium weekend slot pricing

slot_premium Sat 9am-1pm +12 € documented PDP. Reduce slot_fee_dispute if fee line checkout visible.

How to write the SLOT-SUP policy in eight rules?

The SLOT-SUP slot policy governs modify, missed, and compensation.

Eight SLOT-SUP rules

  1. Lookup slot_id first: order metafield, WMS, carrier confirmation before reply

  2. Modify before ship only: if fulfillment unfulfilled + before modify_deadline

  3. Missed verified: tracking timestamp vs slot window before compensation

  4. Refund slot fee: if slot_missed confirmed, auto-refund premium fee

  5. Fresh P1: slot_fresh_violation → full refund or same-day operations redelivery

  6. No slot promise if unavailable: slot_not_available = explain zone, do not make up things

  7. Address change sync: slot reset if #183 address change, re-offer slots

  8. Carrier claim parallel: slot_missed → open carrier ticket + client update 24 h

Compensation matrix missed

Premium fee refund always. Product damage fresh → full refund. Standard missed 2h late → slot fee refund + 10 € store credit manager gesture for LTV > 200 €.

Modify impossible

If shipped or past deadline: uphold polite, offer carrier contact phone oversize. No false modify promise.

Self-service modify portal

Order status modify button reduces slot_modify_request tickets 35-50% if before deadline automated.

How to apply the SLOT-FLOW workflow in eight steps?

The SLOT-FLOW framework structures the delivery slot ticket processing.

Eight steps SL-1 to SL-8

  1. SL-1 Lookup order: slot_id, slot_datetime, fulfillment status

  2. SL-2 Classifier slot_*: section 3 typology

  3. SL-3 Match SLOT-MAP: zone, type, modify_deadline, missed_policy

  4. SL-4 Verify slot data: WMS export, carrier confirm, tracking

  5. SL-5 Explain: macro SLOT-* grounded SL-4

  6. SL-6 Decide: modify | uphold | refund fee | redelivery | carrier claim

  7. SL-7 Execute: WMS reslot, Shopify partial refund, carrier ticket

  8. SL-8 Document: slot_modify_count, claim_id, compensation amount

SL-4 slot_missed

Compare tracking delivered_at vs slot window. If outside window → SL-6 refund fee + carrier claim. If inside window client dispute → proof photo signature.

SL-6 slot_modify_request

If unfulfilled + before deadline → SL-7 WMS/carrier API reslot. If shipped → SLOT-MODIFY-DENY-01 explain + carrier phone oversize.

SL-4 slot_confirm_missing

Resend confirmation email from order metafield slot_display. Link order status page slot widget.

Carrier no_show today P1

slot_carrier_no_show window passed + no tracking: SL-6 redelivery priority + supervisor callback 2 h SLA.

Which SLOT-* macros and touchpoints should be configured?

Eight delivery slot agent macros and self-service touchpoints.

SLOT-CONFIRM-01 (slot confirmed)

« Delivery scheduled [day] [start time]-[end time] at [address]. Order #[X]. Modify before [deadline]: [portal link]. »

SLOT-MODIFY-OK-01 (slot modified)

« Slot updated: [new window date]. Email confirmation resent. Former slot [old] canceled. »

SLOT-MODIFY-DENY-01 (modification impossible)

« Parcel already shipped / deadline passed. Contact carrier [phone] for rescheduling. Tracking reference: [link]. »

SLOT-MISSED-01 (missed slot)

« We confirm delivery outside slot [window]. Refund of slot fees [X] € within 5-10 days. Carrier claim opened #[claim]. »

SLOT-UNAVAIL-01 (no slot available)

« Your PC [code]: standard delivery [ETA] without slot selection. Slot zones: [link /pages/delivery-slots]. »

Touchpoints

  • Checkout: slot calendar + fee visible before pay

  • Confirmation email: slot_display above fold

  • Order status: modify slot button if before deadline

  • /pages/delivery-slots FAQ SLOT-MAP

  • SMS Day-1 slot reminder + tracking link

SLOT-FRESH-P1 (cold chain fee violation)

« Fresh product delivered outside slot: full refund initiated. Do not consume the product. Priority reshipment if stock available. »

Which fresh, oversized, and multi-package cases should be processed?

Special slot cases require SLOT-MAP extensions and separate SLAs.

Fresh products slot_fresh

slot_fresh_violation: cold chain + strict window. Missed or wrong day → full refund P1 + ops discard stock log. Link perishables.

Furniture slot_oversize

slot_oversize_rdv: carrier calls D-2 confirm. Client absent → second delivery fee per SLOT-MAP or 1x free goodwill gesture.

Split shipment #356

slot_partial_delivery: package 1 Thursday slot, package 2 Friday. Explain split policy upfront checkout. Link split (#356).

Address + slot conflict #183

slot_address_conflict: address change invalidates slot zone. Re-offer slots new postal code or standard ETA.

Slot fees hidden fees

slot_fee_dispute: fee shown checkout line item. Link hidden fees if surprise.

Multi-addresses #409

Each address separate slot per line. Link multi-addresses (#409).

Prep time + slot alignment #395

MTO delay may invalidate chosen slot. Proactive reslot if ship date slips past slot. Link prep time article.

Which slot KPIs should be measured?

The delivery slot support KPIs drive modify SLA and missed rate.

Eight key metrics

  • slot_ticket_rate: slot tickets / slot orders

  • slot_missed_rate: slot_missed confirmed / slot orders

  • slot_modify_sla_compliance: modifies within 4 h / due P2

  • slot_modify_success_rate: modifies completed / modify requests

  • slot_fee_refund_rate: fee refunds / slot_missed

  • slot_carrier_claim_rate: claims opened / slot_missed

  • slot_fresh_incident_rate: fresh violations / fresh slot orders

  • slot_csat: satisfaction tag slot resolved

DTC Benchmark

slot_missed_rate < 8 % post SLOT-SUP, modify_sla > 92 %, fresh_incident < 2 %, slot_csat > 4.0/5.

Weekly dashboard

SLOT-TYPE breakdown, postal code zone with highest missed, carrier performance by partner.

Ops alert

slot_missed_rate > 15 % carrier X week: audit TMS export + WMS slot sync.

On-time slot delivery ops KPI

Track delivered_at within window / slot orders. Correlate with carrier partner scorecard monthly.

Self-service modify convert KPI

Track portal modifies / slot_modify_request tickets. Target > 55 % self-service before agent.

What anti-patterns should be avoided on time slots?

Ten delivery slot support anti-patterns to ban.

1. Promising modify after dispatch

SL-4 fulfillment check mandatory. SLOT-MODIFY-DENY-01.

2. Compensation without tracking verification

SL-4 timestamp vs window. Friendly fraud slot_missed claims.

3. Confusing express #338

Express cut-off ≠ slot window. District router macros.

4. Address change without slot reset

Rule 7 #183 sync. Stale slot wrong zone.

5. Fresh missed treated as standard

Rule 5 P1 full refund. Not partial fee only.

6. Inventing slot for slot_not_available

Rule 6 SLOT-UNAVAIL-01 honest ETA standard.

7. Forgotten fee refund for slot_missed

Rule 4 auto premium fee refund always.

8. No slot confirmation email

slot_confirm_missing preventable. Confirmation above fold.

9. Skipping carrier claim

Rule 8 parallel claim. Recover cost 3PL.

10. Missing /pages/delivery-slots

Self-service modify gap. FAQ SLOT-MAP public.

11. Oversize without phone appointment

slot_oversize carrier no-show peak. Document phone D-2 process.

12. Conflating Wismo with slot query

"Where is my parcel" with slot tomorrow → cite SLOT-CONFIRM-01 + tracking, not generic WISMO only.

How does Qstomy help with delivery slots?

Qstomy on Shopify: SLOT-FLOW order lookup, SLOT-MAP explain modify deadline, SLOT-CONFIRM-01 resend, missed policy cite, handoff modify WMS ops.

Qstomy slot capabilities

  • slot_order_lookup: SL-1 slot_datetime type

  • slot_map_explain: window, fee, modify_deadline

  • slot_status_read: SL-4 WMS carrier tracking

  • slot_confirm_template: SLOT-CONFIRM-01 auto

  • slot_handoff_modify: SL-7 fields ops

  • slot_route_express: cut-off → #338 not slot

Pipeline #427 → #428

#427 CS agents modify missed. #428 future self-service slot bot. Shared SLOT-MAP.

Encrypted DTC Scenario

320 slot orders/month, 41 tickets baseline.

After SLOT-SUP + Qstomy: slot_ticket_rate -42%, slot_modify_sla 95%, slot_missed_rate 7%, slot_csat 4.3/5.

Explore customer support and request a demo.

Bot preview #428

Intents slot_modify, slot_confirm feed future bot. SLOT-SUP human prerequisite.

What is the checklist for deploying SLOT-SUP?

SLOT-SUP Checklist (12 steps)

  1. Inventory SLOT-TYPE and active CP (postal code) zones

  2. Document SLOT-MAP windows, fees, modify, missed per type

  3. Draft 8 policy rules for SLOT-SUP

  4. Publish /pages/delivery-slots FAQ + checkout fee visible

  5. Confirmation email slot_display + order status modify widget

  6. Day-before SMS slot reminder

  7. Create SLOT-* helpdesk macros

  8. Train agents on SLOT-FLOW - 45 min (SL-4 verify tracking)

  9. WMS process reslot + carrier claim SL-7

  10. Sync #183 address change → slot reset workflow

  11. Tags slot_* + dashboard KPI section 9

  12. Sync SLOT-MAP → bot #428 future corpus

At a glance

  • #427 = time slot, not express #338

  • SLOT-MAP: zone → window → modify → missed

  • SLOT-FLOW: lookup → verify → modify/compensate

  • Missed = fee refund + carrier claim

  • KPI slot_missed_rate: target < 8%

FAQ

Difference with express #338?
#338 is next-day cut-off speed. #427 is chosen time window, e.g., Thursday 2pm-6pm.

Modify slot after order?
SLOT-MODIFY-OK-01 if unfulfilled + before SLOT-MAP deadline. Otherwise SLOT-MODIFY-DENY-01.

Missed slot, what to do?
SLOT-MISSED-01: verify tracking, refund fee, carrier claim.

No slot for my CP (postal code)?
SLOT-UNAVAIL-01: standard ETA + eligible zones on /pages/delivery-slots.

Does changing address impact slot?
slot_address_conflict: slot reset, re-offer new zone slots #183 sync.

Going further

This week: publish SLOT-MAP on /pages/delivery-slots, audit WMS slot export sync, create macros SLOT-CONFIRM-01 and SLOT-MISSED-01, train agents on SL-4 tracking verify.

Share this guide #427 with ops and support: a slot confirmed by email means a customer present for delivery, a forgotten slot means a one-star review the next day.

Express vs delivery slot at checkout?
Two distinct shipping options. Express #338 speed. Slot #427 window choice. PDP explains both.

Pre-peak fresh checklist

Before holidays: audit slot_fresh capacity, carrier backup fleet, +20% staffing on slot_missed P1 queue.

Enzo

July 1, 2026

Convert over 2,000 customers on average per month with Qstomy.

The world’s 1st Shopify AI dedicated to customer conversion

Empowering 200+ e-commerce merchants

Subscribe to the newsletter and get a personalized e-book!

No-code solution, no technical knowledge required. AI trained on your e-shop and non-intrusive.

*Unsubscribe at any time. We do not send spam.

Subscribe to the newsletter and get a personalized e-book!

No-code solution, no technical knowledge required. AI trained on your e-shop and non-intrusive.

*Unsubscribe at any time. We do not send spam.