E-commerce
July 1, 2026
"The bot told me I would receive it on Saturday even though the date was grayed out at checkout." "The AI promises birthday delivery without checking the D-3 cut-off." "Chatbot confuses a fixed calendar date and a Thursday 2pm-6pm slot." Three failures where a badly calibrated delivery date bot over-promises an impossible date or invents feasibility without FIXDATE-MAP.
A fixed-date delivery AI chatbot does not replace FIXDATE agents (#641). It reads FIXDATE-MAP, calculates pre-purchase feasibility, cites lead_time cutoff blocked_dates, and handoff miss change compensate to humans.
This guide #642 covers intents bot_fixdate_*, flow FIXDATEbot, and KPI fixdate_bot. Companion bot of the FIXDATE playbook (#641). AI use case: verify feasibility of a gift event date before purchase without making impossible promises.
Summary
Why automate fixed-date feasibility with a bot?
"Can I receive it before June 15?", "why is this date greyed out?" and "ordering today for a birthday on Saturday?" come back before the fixed checkout date. A calibrated bot quotes FIXDATE-MAP lead_time_days_min cutoff without promising an unverifiable date.
What the bot resolves tier 1 pre-purchase
Date feasibility: desired date feasible or not map
Lead time explain: min delay days map customer_copy
Cut-off today: order deadline for date X map
Greyed out date: blocked_dates_calendar explain map
Eligible SKU: fixed date program products map
Gorgias estimates that 14 to 22% of gift delivery tickets concern date feasibility resolvable by lookup map without an agent (Gorgias, CS 2026).
FIXDATEbot vs FIXDATE #641, SLOT-BOT #428, express #339, and gift #205
Five contents, five distinct planned delivery layers.
Quick matrix
#642 FIXDATEbot: bot tier 1 pre-purchase feasibility handoff
#641 FIXDATE: agents miss change compensate escalate
SLOT-BOT #428: time slot 2pm-6pm distinct calendar date
Express bot #339: cut-off tomorrow speed not event date
Gift #205: wrapping message distinct date mechanics
Pipeline: #642 bot pre-purchase feasibility tier 1 → checkout date picker → #641 agents miss change compensate post-order.
Which bot_fixdate_* intents should be configured?
Eight fixed-date delivery bot intents mapped to fixdate_* typologies #641.
Eight bot_fixdate intents
bot_fixdate_feasibility: desired date feasible pre-purchase map
bot_fixdate_explain: how fixed-date checkout works
bot_fixdate_lead_time: lead_time_days_min rule map
bot_fixdate_cutoff: cutoff_time_rule order today date X
bot_fixdate_not_available: greyed-out date blocked_dates explain
bot_fixdate_eligibility: eligible SKU categories program map
bot_fixdate_commit_lookup: post-purchase committed date order API quote
bot_fixdate_handoff: miss change compensate → #641 agents
Tier 1 auto: feasibility, explain, lead_time, cutoff, not_available, eligibility if FIXDATE-MAP + date engine.
bot_fixdate_handoff miss change compensate modify execute → agents #641 payload order_ref target_date.
How should FIXDATE-MAP #641 be consumed?
The bot reads FIXDATE-MAP #641: fixdate_program_id, eligible_skus_categories, lead_time_days_min, cutoff_time_rule, blocked_dates_calendar, carrier_fixed_date_map, modify_date_policy, miss_date_compensation_rule, customer_copy, gift_sync_note.
Lookup grounded
Date engine: target_date + today → feasibility Y/N map calc
FEASIBILITY-CITE-BOT: feasibility from map only
NO-DATE-PROMISE-BOT: bot does not promise date without lead_time verify
NO-MODIFY-EXECUTE-BOT: bot does not change order ops date
NO-COMPENSATE-EXECUTE-BOT: bot does not issue refund compensate
SLOT428-REROUTE-BOT: time slot → #428 bot_slot distinct calendar date
FIXDATE641-HANDOFF-BOT: miss change compensate → #641 FD-7 agents
Alignment anti-hallucination (#123): lead_time cutoff feasibility = FIXDATE-MAP whitelist only.
FIXDATEBOT-SUP policy in six rules
Six rules bot fixed delivery date sure.
FIXDATE-MAP-GROUNDED-BOT: cutoff lead_time blocked from map only
FEASIBILITY-CITE-BOT: feasibility cite map calc, do not invent
NO-DATE-PROMISE-BOT: bot does not guarantee date without verify engine
NO-MODIFY-COMPENSATE-EXECUTE-BOT: bot does not modify or compensate
SLOT428-REROUTE-BOT: time slot → #428 distinct calendar day
MISS-HANDOFF-BOT: missed date dispute → #641 agents
Flow FIXDATEbot FDB-1 to FDB-8
Eight-step flow for fixed-date bot feasibility.
FDB-1 Classify: bot_fixdate_* intent detect pre or post purchase
FDB-2 Collect: target_date sku CP event_type order_ref if post
FDB-3 FIXDATE-MAP: program lead_time cutoff blocked modify compensate
FDB-4 Date engine: feasible Y/N cutoff_date calc today target
FDB-5 Guardrail: FEASIBILITY-CITE NO-DATE-PROMISE SLOT428-REROUTE
FDB-6 Respond: TPL-FIXDATEbot grounded map engine
FDB-7 Handoff: miss change compensate → #641
FDB-8 Log: intent fixdate_program_id tag fixdate_bot feasible Y/N
TPL-FIXDATEbot-FEASIBILITY Example
“Requested date [target_date]: [feasible / not feasible map engine]. Min delay [lead_time_days_min map] days. Order before [cutoff_date time map]. [If not feasible: next available date [next_available map].] Bot does not guarantee delivery without order placed checkout date picker.”
TPL-FIXDATEbot and touchpoints templates
Four essential templates.
TPL-FIXDATEbot-FEASIBILITY
Date [target_date] for [event_type]: [faisable/non map]. Lead time [lead_time_days_min map] days. Cut-off [cutoff_time_rule map]. Order before [cutoff_datetime calc]. Checkout: choose calendar date [customer_copy map].
TPL-FIXDATEbot-EXPLAIN
Fixed date delivery [fixdate_program_id]: [customer_copy map]. Choose calendar day at checkout. Distinct time slot #428. Eligible products: [eligible_skus_categories map]. Gift: see #205 packaging.
TPL-FIXDATEbot-CUTOFF
For delivery [target_date]: order before [cutoff_datetime calc map]. It is [now]. [If too late: not feasible, next [next_available map].] Blocked dates: [blocked_dates_calendar cite map].
TPL-FIXDATEbot-HANDOFF
Request [miss / change / compensate] forwarded to delivery team. Order [order_ref] promised date [committed_date]. Agent response time [handoff_sla map].
Touchpoints
Pre-purchase PDP widget: bot_fixdate_feasibility embed date picker preview
Checkout date greyed: bot_fixdate_not_available explain tooltip
Birthday gift basket: bot_fixdate_feasibility proactive event_type
Post-purchase order status: bot_fixdate_commit_lookup committed_date API
Edge cases and reroutes
Five cases out of tier 1 bot fixed date standard.
Time slot question: SLOT428-REROUTE-BOT #428 bot_slot
Express tomorrow: #339 express eligibility distinct event date
Missed date dispute: MISS-HANDOFF-BOT #641 FIXDATE-MISS
Address change #183: reconsider feasibility handoff agents
After-sales slot #427: slot_missed agents distinct calendar date
Bot never executes modify date or compensation: agents #641 workflow FD-7.
Essential fixdate_bot KPIs
Five FIXDATEbot management metrics.
fixdate_bot_feasibility_deflect: pre-purchase feasibility resolved without an agent
fixdate_bot_explain_deflect: explain fixed date resolved map
fixdate_bot_handoff_rate: miss change compensate / total fixdate bot
fixdate_bot_no_promise_violations: promised date bot without verify target audit 0
fixdate_bot_pre_purchase_rate: pre-purchase sessions / total fixdate bot
Target: fixdate_bot_no_promise_violations 0 and fixdate_bot_feasibility_deflect greater than 75% with FIXDATE-MAP sync.
Anti-patterns FIXDATEbot
Five common errors in fixed date delivery bots.
Date promised without verification: NO-DATE-PROMISE-BOT date engine map
Invented feasibility: FEASIBILITY-CITE-BOT FIXDATE-MAP calc only
Confusing slot #428: SLOT428-REROUTE distinct hour day
Compensating for bot miss: NO-COMPENSATE-EXECUTE FIXDATE641-HANDOFF
Ignoring blocked_dates: bot_fixdate_not_available map cite
FIXDATEbot with Qstomy
Qstomy on Shopify: detect bot_fixdate intent, FIXDATE-MAP RAG grounded, date engine feasibility calc, FEASIBILITY-CITE, handoff #641 miss change compensate payload.
Pipeline: #642 bot pre-purchase feasibility tier 1 → checkout → #641 agents miss change compensate escalate.
Explore AI support and request a demo.
Checklist, FAQ and going further
FIXDATEbot Checklist (8 steps)
Sync FIXDATE-MAP #641: RAG bot PDP checkout widget
Policy FIXDATEBOT-SUP: 6 NO-DATE-PROMISE rules
8 intents bot_fixdate_*: flow FDB-1 to FDB-8
4 templates TPL-FIXDATEbot-*: FEASIBILITY EXPLAIN CUTOFF HANDOFF
Date engine connect: FDB-4 calc feasible cutoff next_available
PDP embed widget: bot_fixdate_feasibility pre-purchase entry
Red team 10 prompts: promised date without map, confused slot, compensate bot
KPI Dashboard: fixdate_bot_* section 9
FAQ
Difference #641?
#641 = agents miss change compensate escalate carrier. #642 = bot tier 1 feasibility pre-purchase handoff.
Does the Bot guarantee delivery date?
No. NO-DATE-PROMISE-BOT. Bot quotes map feasibility. Commitment = checkout date picker post-order.
Difference SLOT-BOT #428?
#428 = time slot Thursday 2pm-6pm. #642 = calendar date Thursday for gift event.
Missed date post-delivery?
bot_fixdate_handoff MISS-HANDOFF-BOT #641 FIXDATE-MISS macro compensate.
Going further
This week: index FIXDATE-MAP RAG, connect date engine bot, red team promised date without map verify.
Enzo
July 1, 2026
