E-commerce
July 1, 2026
"The bot says Saturday delivery to the office is possible, even though the reception desk is closed." "The AI forgets to ask for the mandatory company name." "The chatbot treats reception desk packages as home DNR and promises a refund." Three failures where a poorly calibrated business delivery bot invents schedules or confuses the mailroom with a home dispute.
An AI office delivery chatbot does not replace BIZDEL agents (#645). It reads BIZDEL-MAP, guides checkout instruction fields, quotes reception_hours company_name_required, and hands off mailroom not_received to humans.
This guide #646 covers intents bot_bizdel_*, flow BIZDELbot, and KPI bizdel_bot. Bot pair to the BIZDEL playbook (#645). AI use case: verifying reception constraints and instructions before office purchase.
Summary
Why automate office delivery instructions with a bot?
"Which fields for office delivery?", "reception open when?" and "company name mandatory?" recur at the pro address checkout. A calibrated bot quotes BIZDEL-MAP delivery_instructions_fields reception_hours_default without inventing reception hours.
What the bot resolves tier 1 pre-purchase
Required fields: company floor building map
Reception hours: reception_hours_default quotes map
Office weekend: weekend_office_closed explain map
Company name: company_name_required Y/N map
Post-purchase lookup notes: delivery_notes metafield quotes
Gorgias estimates that 16% to 24% of pro address tickets concern instructions resolvable by grounded checkout FAQ without an agent (Gorgias, CS 2026).
BIZDELbot vs BIZDEL #645, address #183, DNR #509 and Saturday #644
Five contents, five distinct office delivery layers.
Quick matrix
#646 BIZDELbot: tier 1 bot pre-purchase schedule instructions handoff
#645 BIZDEL: mailroom agents not_received POD escalate
Address change #183: modify distinct address reception constraints
DNR #509: home dispute distinct from mail office
SATDEL bot #644: Saturday premium distinct from weekend closed office
Pipeline: #646 bot schedule instructions tier 1 → checkout pro fields → #645 mailroom agents not_received escalate.
Which bot_bizdel_* intents should be configured?
Eight corporate delivery bot intents mapped to biz_del_* typologies #645.
Eight bot_bizdel intents
bot_bizdel_explain : how office delivery checkout map
bot_bizdel_hours : reception_hours_default desk hours map
bot_bizdel_instructions : delivery_instructions_fields required fields map
bot_bizdel_company_name : company_name_required mandatory map
bot_bizdel_weekend : weekend_office_closed Saturday Sunday map
bot_bizdel_mailroom : mailroom_routing_days mail delay map
bot_bizdel_notes_lookup : post-purchase delivery_notes metafield quote
bot_bizdel_handoff : not_received mailroom dispute → #645 agents
Tier 1 auto : explain, hours, instructions, company_name, weekend, mailroom, notes_lookup if BIZDEL-MAP.
bot_bizdel_handoff biz_del_not_received_office POD dispute → agents #645 payload order_ref POD status.
How should BIZDEL-MAP #645 be consumed?
The bot reads BIZDEL-MAP #645: bizdel_program_id, carrier_business_map, reception_hours_default, weekend_office_closed, company_name_required, delivery_instructions_fields, security_desk_policy, mailroom_routing_days, not_received_office_sla, customer_copy_checkout.
Lookup grounded
Checkout field guide: required fields from map only
INSTRUCTIONS-CITE-BOT: delivery_notes metafield cite verbatim
NO-MODIFY-EXECUTE-BOT: bot does not modify address ops notes
NO-POD-INVENT-BOT: bot does not cite POD without carrier API
ADDRESS183-REROUTE-BOT: change address → #183 distinct office instructions
DNR509-REROUTE-BOT: home dispute → #509 distinct mailroom
BIZDEL645-HANDOFF-BOT: not_received escalate → #645 BD-7 agents
Alignment anti-hallucination (#123): hours instructions = BIZDEL-MAP whitelist only.
BIZDELBOT-SUP Policy in six rules
Six rules for a safe company delivery bot.
BIZDEL-MAP-GROUNDED-BOT: schedule instructions company from map only
INSTRUCTIONS-CITE-BOT: driver notes metafield cite verbatim
NO-MODIFY-EXECUTE-BOT: bot does not change address or ops notes
NO-POD-INVENT-BOT: POD reception carrier API only
WEEKEND-CLOSED-BOT: weekend_office_closed cite, do not promise Saturday office
MAILROOM-HANDOFF-BOT: not_received beyond sla → #645 agents
Flow BIZDELbot BDB-1 to BDB-8
Flow eight-step bot office delivery instructions.
BDB-1 Classify : bot_bizdel_* intent detection pre or post purchase
BDB-2 Collect : company_name building floor order_ref if post
BDB-3 BIZDEL-MAP : hours weekend company instructions mailroom sla
BDB-4 Order lookup : delivery_notes metafield shipping_address if post
BDB-5 Guardrail : INSTRUCTIONS-CITE WEEKEND-CLOSED NO-POD-INVENT
BDB-6 Respond : TPL-BIZDELbot grounded map metafield
BDB-7 Handoff : not_received mailroom dispute → #645
BDB-8 Log : intent bizdel_program_id tag bizdel_bot pre_post
Example TPL-BIZDELbot-INSTRUCTIONS
“Office delivery [bizdel_program_id]: [customer_copy_checkout map]. Required fields: [delivery_instructions_fields map]. Company name [company_name_required map]. Reception hours [reception_hours_default map]. Weekend: [weekend_office_closed map]. Bot does not modify notes after shipping, contact agents if urgent.”
TPL-BIZDELbot and touchpoints templates
Four essential templates.
TPL-BIZDELbot-EXPLAIN
Business delivery [bizdel_program_id]: [customer_copy_checkout map]. Carrier [carrier_business_map map]. Reception desk: [security_desk_policy map]. Internal mail delay [mailroom_routing_days map] business days post-reception delivery.
TPL-BIZDELbot-INSTRUCTIONS
Professional address checkout: [delivery_instructions_fields map]. Company name [company_name_required map]. Example notes: floor building reception contact. [If order [order_ref]: current notes [delivery_notes metafield cite].]
TPL-BIZDELbot-HOURS
Reception open [reception_hours_default map] Mon-Fri. Weekend office [weekend_office_closed map]. [If weekend Y closed: Saturday Sunday delivery not guaranteed office, home alternative #183 or pickup point.]
TPL-BIZDELbot-HANDOFF
Request [not_received_office / POD dispute] forwarded to delivery team. Order [order_ref] company [company_name]. Agent response time [handoff_sla map]. Wait [not_received_office_sla map] hours for internal mail before escalation.
Touchpoints
Professional address checkout toggle: bot_bizdel_instructions proactive fields
Cart shipping step: bot_bizdel_hours bot_bizdel_company_name embed
Order confirmation email: bot_bizdel_notes_lookup deep link
Tracking delivered reception: bot_bizdel_mailroom proactive wait sla
Edge cases and reroutes
Five cases outside tier 1 bot standard office.
Change office address : ADDRESS183-REROUTE-BOT #183 cutoff sync
DNR confused home : DNR509-REROUTE-BOT #509 distinct mailroom
Recipient name only : #541 WRONGNAME distinct company
Premium Saturday office closed : #644 SATDELbot weekend_office_closed reroute
B2B wholesale account : B2B delivery contract handoff guide
Bot never executes modify address notes nor refund DNR : agents #645 workflow BD-7.
Essential bizdel_bot KPIs
Five BIZDELbot management metrics.
bizdel_bot_instructions_deflect: required fields resolved without agent
bizdel_bot_hours_deflect: business hours resolved map
bizdel_bot_handoff_rate: not_received mailroom / total bizdel bot
bizdel_bot_pod_invent_violations: invented POD bot audit target 0
bizdel_bot_pre_checkout_rate: pre-purchase sessions / total bizdel bot
Target: bizdel_bot_pod_invent_violations 0 and bizdel_bot_instructions_deflect higher than 72% with BIZDEL-MAP sync.
BIZDELbot anti-patterns
Five common business delivery bot errors.
Invented schedules: BIZDEL-MAP-GROUNDED-BOT reception_hours only
Promising Saturday office: WEEKEND-CLOSED-BOT weekend_office_closed map
Treating as residential DNR: DNR509-REROUTE mailroom sla first
Invented POD: NO-POD-INVENT-BOT carrier API only
Modifying bot notes: NO-MODIFY-EXECUTE handoff #645 ops
BIZDELbot with Qstomy
Qstomy on Shopify: detect bot_bizdel intent, BIZDEL-MAP RAG grounded, checkout field guide, delivery_notes lookup, handoff #645 not_received mailroom payload.
Pipeline: #646 bot instructions hours tier 1 → checkout → #645 agents mailroom POD escalate.
Explore AI support and request a demo.
Checklist, FAQ and going further
BIZDELbot Checklist (8 steps)
Sync BIZDEL-MAP #645: RAG bot checkout shipping step
Policy BIZDELBOT-SUP: 6 rules INSTRUCTIONS-CITE NO-POD-INVENT
8 bot_bizdel_* intents: flow BDB-1 to BDB-8
4 templates TPL-BIZDELbot-*: EXPLAIN INSTRUCTIONS HOURS HANDOFF
Checkout embed widget: bot_bizdel_instructions pre-purchase entry
Order metafield connect: BDB-4 delivery_notes lookup
Red team 10 prompts: Saturday office invented POD DNR confused modify notes
Dashboard KPI: bizdel_bot_* section 9
FAQ
Difference #645?
#645 = mailroom agents not_received POD escalate carrier. #646 = tier 1 bot instructions hours handoff.
Does the bot modify delivery notes?
No. NO-MODIFY-EXECUTE-BOT. Handoff #645 or #183 if unfulfilled.
Parcel delivered to reception but not received?
bot_bizdel_mailroom mailroom_routing_days then bot_bizdel_handoff if SLA is exceeded.
Difference with DNR #509?
#509 = home dispute neighborhood POD. #646/#645 = reception desk internal mail.
Going further
This week: index BIZDEL-MAP RAG, embed checkout business address widget, red team invented POD bot.
Enzo
July 1, 2026
