E-commerce
July 1, 2026
“The bot says refund within 24 hours even though the package hasn't been returned.” “The AI promises immediate reshipment after an accidental refusal.” “Tracking refused, the chatbot doesn't understand return to sender.” Three failures where a non-grounded package refused bot invents refund timelines or confuses voluntary RMA returns.
An e-commerce package refused AI chatbot does not replace REFDEL agents (#511). It reads REFDEL-MAP, explains carrier refused status, warehouse return timeline, carrier return fees, and grounded reship options.
This guide #512 covers intents bot_ref_del_*, flow REFDELbot, and KPI refdel_bot. Bot pair of the REFDEL playbook (#511). New AI use case: consequences of delivery refusal without premature refund promises.
Summary
Why automate "parcel refused by bot"?
After delivery refusal, the customer looks for the refund timeframe and the meaning of the refused tracking status. A calibrated bot cites REFDEL-MAP and carrier status in seconds, without promising a refund before the warehouse scan.
What the tier 1 bot resolves
Refund when: return_transit_days + refund_sla_days map
Tracking explain: refused return_to_sender status FR
Fees who pays: return_fee_paid_by merchant customer
Accidental reship: reship_allowed fee grounded
Gift recipient: buyer timeline post-return
Colissimo documents automatic return to sender upon refusal (Colissimo, parcel refusal 2026). The bot intercepts bot_ref_del_refund_when before the anxious agent ticket.
REFDELbot vs REFDEL #511, WISMO and RETSHIP #509
Four contents, four delivery incident layers.
Quick matrix
#512 REFDELbot: bot refused timeline fees reship tier 1
#511 REFDEL: agents refund exception COD reship ops
WISMO tracking: normal parcel transit status
#509 RETSHIP: voluntary return RMA fees
Pipeline: carrier webhook refused → #512 timeline explain → #511 if refund exception reship COD or lost return.
Which bot_ref_del_* intents should be configured?
Eight parcel refused bot intents.
Eight bot_ref_del intents
bot_ref_del_refund_when : when refund after refusal
bot_ref_del_tracking_explain : refused return sender explain FR
bot_ref_del_accidental_reship : accidental refusal reship possible
bot_ref_del_fees_who : return carrier fees who pays
bot_ref_del_gift_recipient : gift recipient refused
bot_ref_del_cod : parcel refusal cash on delivery handoff
bot_ref_del_partial_multi : multi-parcel one refused explain
bot_ref_del_status_check : parcel returned to warehouse scan refund
Tier 1 auto : refund_when, tracking_explain, fees_who, status_check, accidental_reship if reship_allowed map Y.
Intent bot_ref_del_cod, gift dispute and lost return → agents #511 with payload order_id, carrier_status, refund_trigger map.
How do I consume REFDEL-MAP #511?
The bot reads REFDEL-MAP #511: refusal_reason, carrier, return_transit_days, refund_trigger, return_fee_paid_by, reship_allowed, refund_sla_days, customer_comms_template.
Lookup grounded
Order + tracking: carrier API refused return_to_sender scan
REFDEL-MAP row: carrier + refusal_reason branch
Timeline calc: refused_date + return_transit_days + refund_sla
Fees cite: return_fee_paid_by exact map value
Reship gate: reship_allowed Y/N fee EUR only
Alignment anti-hallucination (#123): refund delays = REFDEL-MAP whitelist only.
REFDELBOT-SUP policy in six rules
Six rules bot parcel refused safe.
NO-REFUND-BEFORE-SCAN: refund timeline from refund_trigger map only
REFDEL-MAP-GROUNDED: never delay or fee outside of map
TRACKING-CITE: exact carrier status refused return sender
NO-RESHIP-BEFORE-RETURN: reship after return scan or map exception
GIFT-BUYER-ONLY: gift recipient → buyer timeline
COD-HANDOFF: COD refusal → #511 finance carrier claim
Flow REFDELbot RDB-1 to RDB-8
Eight-step flow for refused package bot.
RDB-1 Classify: bot_ref_del_* intent
RDB-2 Context: order lookup + carrier tracking API
RDB-3 Detect refused: status refused return_to_sender confirm
RDB-4 REFDEL-MAP: lookup timeline fees reship rules
RDB-5 Guardrail: NO-REFUND-BEFORE-SCAN NO-RESHIP-BEFORE-RETURN
RDB-6 Respond: TPL-REFDELbot grounded timeline
RDB-7 Proactive: webhook refused auto e-mail template map
RDB-8 Log: refund_sla_cited tag refdel_bot handoff if needed
Example TPL-REFDELbot-REFUND
“Package refused on [refused_date]. Carrier return ~[return_transit_days] days. Refund within [refund_sla_days] business days after warehouse receipt. Tracking: [url] status [carrier_status]. Return fee: [return_fee_paid_by].”
TPL-REFDELbot templates and touchpoints
Four essential templates.
TPL-REFDELbot-REFUND
Parcel refused on [date]. Return ~[return_transit_days] days. Refund within [refund_sla_days] days post-warehouse-scan. Tracking: [url].
TPL-REFDELbot-ACCIDENTAL
Refusal recorded. Reshipment: [reship_allowed fee]. Possible after warehouse return or new order. Contact us upon return scan.
TPL-REFDELbot-TRACKING
Current status: [carrier_status FR]. "Refused by recipient" = automatic return to sender. Next step: warehouse return scan.
TPL-REFDELbot-GIFT
Recipient refused. Return in progress. Buyer refund within [refund_sla_days] days post-scan. See #205 gift.
Touchpoints
Carrier refused webhook: auto TPL-REFDELbot-REFUND email
Tracking widget page: "I refused the parcel" tag
Post-delivery SMS: link bot_ref_del_refund_when
Help center FAQ refused: embedded grounded timeline bot
Edge cases and reroutes
Five cases outside tier 1 bot.
Voluntary return RMA: #510 RETSHIP distinct from delivery refusal
Parcel damaged in transit: #363 claim priority
Change address intercept: #183 too late explain
Refund status follow-up: refund status bot post-scan
Lost warehouse return: handoff #511 ops carrier claim exception
Bot does not trigger Shopify refund: handoff #511 if refund_trigger exception or customer disputes timeline.
Essential refdel_bot KPIs
Five steering metrics for REFDELbot.
refdel_bot_auto_resolve: % tier 1 without agent
refdel_bot_timeline_grounded_rate: compliant answers REFDEL-MAP
refdel_bot_refund_promise_violation: NO-REFUND-BEFORE-SCAN, target 0
refdel_bot_tracking_cited: % with exact carrier status
refdel_bot_handoff_rate: sessions → #511 COD exception reship
Monthly red team: 10 prompts "guaranteed immediate refund", "reship now without return", "24-hour refund promised". Delay outside map = REFDEL-MAP-GROUNDED violation.
REFDELbot anti-patterns
Six frequent mistakes.
Immediate refund promised: NO-REFUND-BEFORE-SCAN
Reship before warehouse return: NO-RESHIP-BEFORE-RETURN
Confusing RMA return #509: distinct delivery refusal
Invented delay: REFDEL-MAP-GROUNDED violation
Ignoring carrier status: TRACKING-CITE mandatory
Duplicating entire WISMO: refused focus only
REFDELbot with Qstomy
Qstomy on Shopify + carrier API: detect refused webhook, REFDEL-MAP RAG, TPL-REFDELbot timeline, proactive e-mail refused, handoff #511 COD reship exception payload.
Pipeline: webhook refused → #512 timeline → #511 refund reship exception → AI governance #142 audit refund claims.
Explore AI support and request a demo.
Checklist, FAQ and going further
REFDELbot Checklist (8 steps)
Sync REFDEL-MAP #511: RAG bot whitelist only
Policy REFDELBOT-SUP: 6 NO-REFUND-BEFORE-SCAN rules
8 intents bot_ref_del_*: flows RDB-1 to RDB-8
4 templates TPL-REFDELbot-*: REFUND ACCIDENTAL TRACKING GIFT
Webhook carrier refused: proactive auto-email
Tracking widget chip refused: bot_ref_del_refund_when entry
Red team 10 prompts: immediate refund, made-up reship
Dashboard KPI: refdel_bot_* section 9
FAQ
Difference #511?
#511 = exception refund agents COD reship ops. #512 = bot tier 1 timeline fees explain.
Difference #509 RETSHIP?
#509 = voluntary return RMA. #512 = carrier return refusal at delivery.
Bot triggers refund?
No. Timeline grounded. Refund action → #511 post-scan.
Accidental refusal reship?
TPL-REFDELbot-ACCIDENTAL if reship_allowed map Y.
Going further
This week: index REFDEL-MAP in bot corpus, test red team "promised 24h refund", measure refdel_bot_timeline_grounded_rate. Activate proactive email refused webhook.
Enzo
July 1, 2026
