E-commerce
July 30, 2026
"My package is broken, does insurance cover it?" "How do I file a Route claim?" "I paid for protection, why am I being redirected to the warranty?" Three messages where a generic bot confuses transit incidents, product warranties, and express delays.
Route indicates that its protection covers lost, stolen, or damaged packages in transit, with claims submitted via the Resolve Center within 30 days (Route, policies 2026). Onward estimates that self-serve claims automation can reduce delivery incident tickets by 30 to 40% (Onward, Shopify protection 2026).
This guide #362 formalizes the AI delivery insurance chatbot: explaining coverage, exclusions, and the claim process. It complements insurance support (#361) (SHIP-INS policy ops) with an AI use case perspective: protection lookup, coverage FAQ, claim redirection, and warranty triage.
Summary
Why automate delivery insurance with a bot?
A shipping insurance bot Carlton answers on coverage, exclusions, and claim link. It does not issue refunds on its own: it routes to the Resolve Center or handoff agent according to policy SHIP-INS (#361).
Three generic bot failures
Refund promise: bot guarantees refund without checking protection status
Warranty confusion: intact package, bot opens insurance claim
Delay = damage/loss: express late treated as covered claim
Route specifies that non-damaged express delays are not covered (Route, 2026 exclusions).
Angle #362
The #361 documents SHIP-INS macros and human INS-CLAIM flow. The #362 implements the bot intents ins_bot_* layer: coverage FAQ, claim redirect, warranty triage, photo collect.
ROI ins bot
On Route brand 42% adoption, 67 insurance tickets/month: targeted bot 70 to 80% self-resolved vs 20% generic WISMO bot.
DTC Example
Decor brand, 71 ins tickets/month. After INS-BOT bot: ins_bot_resolution 79%, ins_wrong_routing_warranty 4%, response time 35 s, bot claim CSAT 4.6/5.
Journey touchpoint
Post-delivery: broken package, stolen package, stuck tracking. Pre-purchase: "what is checkout protection?" Trigger: insurance, Route, package protection, claim.
Ops prerequisites
SHIP-INS policy (#361) published. route_protected metafield on order. Bot cites RAG policy, does not invent coverage.
Why a dedicated insurance bot
Coupling with WISMO bot dilutes accuracy: "broken package" customer receives a tracking update. Routing ins_bot_* avoids mismatch and applies specific claim safeguards.
Volume and seasonality
Insurance tickets peak November-January (stolen package) and June-August (delivery absences). Pre-purchase ins_bot_coverage bot smooths checkout questions during conversion peaks.
Cost of bot refund promise
A bot promising a refund before Route approval creates double payment or chargeback. INS-BOT-GUARD prohibits any financial promise: claim link or handoff only.
Protection adoption and bot
Route targets 40 to 50% opt-in depending on vertical. The pre-purchase ins_bot_coverage bot answers hesitations without weighing down the cart: the customer understands the value before checking the protection.
How does it differ from support #361 and warranty #349?
Seven claim delivery contents, seven distinct bot roles.
Insurance support (#361)
Guide #361: policy SHIP-INS, macros SHIP-INS-*. #362 = automation bot lookup + redirect claim.
Damaged parcel (#363)
The future damaged parcel support (#363): photos, human ops replacement. #362 covers insurance eligibility and claim link before workflow #363.
Bot warranty (#349)
Bot warranty (#349): product defect. #362 handoff if parcel is intact via ins_bot_warranty_triage.
Express (#338)
Express (#338): cut-off delays. #362: ins_bot_express_delay, insurance exclusion.
Bot WISMO (#184)
Bot WISMO (#184): tracking. #362 = post-delivery claim sub-intent, not transit status alone.
Split (#357)
Bot split (#357): multi-parcel. #362 handles claim on specific parcel N.
Post-claim returns
Returns bot intervenes after claim resolution. #362 does not create RMA: it qualifies claim and sends to claim or warranty first.
Promise #362
Intents ins_bot_*, flow INS-BOT-GATE, safeguards INS-BOT-GUARD, handoff #361/#363, KPI ins_bot.
Which ins_bot intents should the bot classify?
Map ins_bot intents before flows. Scope: explain and route, do not approve claim.
Ten insurance bot intents
ins_bot_coverage: what is covered?
ins_bot_exclusion: delay, wrong item, quality
ins_bot_claim_link: file a claim Route
ins_bot_not_protected: not purchased at checkout
ins_bot_lost: lost package tracking
ins_bot_stolen: stolen after delivery
ins_bot_damaged: broken package upon receipt
ins_bot_warranty_triage: warranty redirect if intact
ins_bot_express_delay: delay not covered
ins_bot_denied_handoff: claim denied, escalation
Mandatory session fields
order_id, route_protected, carrier, tracking_status, delivery_date, loss_type, photos_uploaded (bool). See taxonomy (#135).
Parent router
"insurance", "Route", "protection", "claim", "broken package covered" → ins_bot_* (#362). "Where is my package" without loss → WISMO (#184).
90-day ticket mining
Export insurance tags #361. Prioritize top verbatim flows before Route API integration.
MVP Prioritization
Week 1: ins_bot_coverage + ins_bot_claim_link. Week 2: ins_bot_damaged + ins_bot_warranty_triage. Week 3: ins_bot_not_protected + handoff.
How to build the INS-BOT-GATE flow?
The INS-BOT-GATE flow routes each message via lookup protection before high-level claim response.
Six sequential gates
Auth Gate: email + order_id
Protection Gate: route_protected yes/no
Intent Gate: coverage vs claim vs exclusion
Claim Type Gate: lost / stolen / damaged / delay
Delay Gate: 30 days OK or handoff denied
Output Gate: FAQ, claim link, photo collect, handoff
Branch ins_bot_claim_link
If route_protected=true: Resolve Center link + 30-day delay reminder + photo proof. If false: ins_bot_not_protected + carrier options (#361 SHIP-INS-NOPROTECT).
Branch ins_bot_damaged
Collect packaging photos before claim redirect. If product intact as mentioned → ins_bot_warranty_triage.
Branch ins_bot_express_delay
Quote Route delay exclusion intact. Express link (#338) if shipping refund is requested.
Max turns
3 clarifications max. Then handoff to agent with claim payload.
Bot photo checklist
Before ins_bot_claim_link on damaged: bot asks for confirmation of 3 photos (outer packaging, inner packaging, product + carrier label). Session flag photos_acknowledged=true before sending Resolve link.
Which data sources does the insurance bot read?
The insurance bot reads Shopify order + Route protection flag + policy SHIP-INS RAG.
Five Shopify sources
Order API: payment, fulfillment, gift tags
Metafield route_protected: active protection
Tracking carrier: delivered_at, status
Premium amount: line item protection
Resolve Center URL: per Route order
Route documents the merchant portal claims process (Route, claims 2026).
Policy RAG #361
SHIP-INS chunks coverage, exclusions, deadlines, proofs. Bot cites policy, no overpromising.
Alternative apps
Onward, ShipProtect: adapt claim URL according to protection_provider metafield.
Cache protection status
Refresh at each ins_bot session. Route does not allow post-purchase addition (Route, FAQ 2026).
Sync checkout opt-in
Webhook order/create tag route_protected if line item protection is present. Bot reads flag in session without delay to avoid false ins_bot_not_protected on recent orders.
What safeguards should be imposed on the insurance bot?
The INS-BOT-GUARD guardrails prevent promised refunds and incorrect routing.
Five strict rules
No bot refund: redirect claim or agent handoff
Auth before claim: order_id + email mandatory
Warranty triage: undamaged → #349, not a claim
Delay ≠ covered: express delay explicit exclusion
Photos damage: checklist before claim link
Ins bot system prompt
"You explain parcel insurance coverage according to the SHIP-INS policy. You never promise a refund. If route_protected, you send the Resolve Center link. If the parcel is undamaged and the product is defective, you redirect to warranty." See anti-hallucination.
Standard response ins_bot_coverage
"Your order #7842 includes delivery protection. Covered: loss in transit, reported theft, damage upon receipt. Not covered: delay only, wrong item, product defect outside of transport. Claim: [link] within 30 days."
Regression tests
25 scenarios: protected claim, not protected, damaged photos, warranty redirect, express delay, stolen, lost, denied handoff, gift, split parcel 2. target ins_bot_hallucination is 0%.
Audit logging
Log order_id, route_protected, intent, claim_link_sent. Monthly audit of 10 sessions: verify no bot refund promises.
High value threshold
Orders > €500: bot stops auto claim link, handoff to agent supervisor even if protected. Avoids complex billing disputes on bot alone.
Which bot flows for claims and insurance FAQ?
The insurance bot operates on claim and pre-purchase FAQ touchpoints.
Broken package chat flow
Auth → ins_bot_damaged → photo checklist → ins_bot_claim_link if protected.
Checkout widget FAQ flow
Pre-purchase "Package Protection": ins_bot_coverage + ins_bot_exclusion without order lookup.
Tracking page flow
"Delivery issue?" button → route to ins_bot if delivered, WISMO if in_transit.
Claim email flow
Pre-filled order_id chat link. Bot retrieves protection status without asking again.
Claim denied flow
Customer disputes Route rejection → ins_bot_denied_handoff supervisor payload claim_id.
ins_bot_not_protected flow
Bot explains options: carrier claim (15-30 days delay), commercial gesture according to grid #361, no Resolve link. Collects photos if damaged. Agent handoff if customer insists on immediate refund.
Ins bot handoff payload
order_id, route_protected, sinistre_type, photos_collected, claim_link_sent, session_log, handoff_reason.
Proactive post-delivery
If delivered + protected: 24h message "Package issue? File a claim here". Reduces ins_bot_claim_howto tickets.
How do I connect the insurance bot to Shopify?
The Shopify insurance bot setup connects Route, router intents, and RAG SHIP-INS.
Technical Checklist
Install Route or app protection (Shopify App Store)
Sync metafield route_protected webhook order
Index policy SHIP-INS #361 RAG
Configure router ins_bot_* keywords
Write prompt INS-BOT-GUARD section 6
Connect Resolve Center URL API or template
Test 25 regression scenarios
Weekly ins_bot_resolution dashboard
Helpdesk integration
Handoff payload visible sidebar: protection yes/no, claim type, photos OK.
Gradual launch
Phase 1: coverage + claim link. Phase 2: damaged + warranty triage. Phase 3: not protected + denied handoff.
Fallback without Route
Bot ins_bot_coverage from merchant self-insured policy. ins_bot_claim_link → customer service form #361, not Resolve.
Which KPIs should be measured on the insurance bot?
Without ins_bot KPIs, it is impossible to prove ROI vs macros #361 alone.
Seven Key Metrics
ins_bot_resolution: resolved without an agent / ins bot sessions
ins_bot_deflection: insurance tickets avoided / sessions
ins_claim_link_sent_rate: protected + link / ins_bot_claim
ins_warranty_redirect_rate: triage OK / damaged intents
ins_bot_handoff_rate: escalations / sessions
ins_bot_hallucination_rate: refund promises bot
CSAT intent ins_bot: claim satisfaction bot
DTC Benchmark
Target ins_bot_resolution > 75%, ins_warranty_redirect_rate > 90% on intact mentions, CSAT > 4.5/5.
#361 Correlation
human insurance_support_volume must drop 40%+ post-bot on coverage and claim howto intents.
Monthly Review
Top handoff reasons, top claim type, adjust RAG exclusions.
Segmented Dashboard
Separate ins_bot_coverage CSAT vs ins_bot_damaged: a weak intent guides photo checklist enrichment or RAG exclusion.
A/B Test Checkout Widget
Measure ins_bot_deflection with online chat protection FAQ vs without widget. Brands with Route adoption < 35% often gain 0.3 conversion points when the bot answers coverage questions before opt-in hesitation.
What edge cases and escalations should be anticipated?
Seven ins bot edge cases training handoff or special procedure.
Split parcel 2 damaged
Loss on parcel 2 tracking. Check if protection covers the order. Link bot split (#357).
Recipient gift loss
Recipient initiates contact: verify buyer is protected. Gift claim policy according to #361, do not send link without buyer auth if required.
Claim beyond 30 days
Bot cites time limit exclusion. Supervisor handoff if amount > threshold and mitigating circumstances.
Customer threatens chargeback
P1 priority, claim link if protected, supervisor if not protected.
International customs damage
Check Route international policy exclusions. Handoff to ops if coverage is doubtful.
Multi-loss repeat customer
3+ claims within 90 days: handoff to fraud review, no auto claim link.
High-value product > threshold
Order amount > €500: agent handoff even if protected, do not use bot alone.
Wrong item received
Parcel intact but SKU incorrect: ins_bot_exclusion, no insurance claim. Route to exchange return or product customer service, not Resolve Center. Frequent post-loss confusion where customer mixes up transport damage and warehouse picking error.
Customer insists on immediate refund
Bot never promises instant refund. Message: insurer processing delay of 5 to 10 business days after complete file submission. Handoff if there is a threat of chargeback or public negative review.
How does Qstomy handle delivery insurance?
Qstomy routes the ins_bot_* intents from order API, route_protected and policy SHIP-INS RAG.
Capabilities
ins_protection_lookup: Yes/no route + premium
ins_coverage_faq: covered vs policy exclusions
ins_claim_redirect: Resolution Center URL
ins_damage_photo_checklist: collection before claim
ins_warranty_triage: handoff #349 if intact
Encrypted DTC Scenario
Furniture brand, 64 ins/month tickets, generic WISMO bot confused claims with tracking.
After Qstomy ins bot: 77% self-resolved, ins_bot_resolution 81%, ins_bot_handoff_rate 14%, CSAT 4.7/5.
Explore AI support, Shopify, request a demo.
What is the checklist for launching the insurance bot?
Insurance Bot Checklist (10 steps)
Validate policy SHIP-INS #361
Audit insurance tickets 90 d
Connect route_protected metafield
Index RAG exclusions coverage
Document flow INS-BOT-GATE section 4
Configure router ins_bot_* intents
Draft prompt INS-BOT-GUARD section 6
Test 25 regression scenarios
Integrate handoff #361 and #363
Weekly ins_bot_resolution dashboard
At a glance
#362 = shipping insurance bot, not ops support alone (#361)
INS-BOT-GATE: auth → protection → damage → claim link
10 ins_bot_* intents: coverage, claim, damaged, warranty
No bot refund: redirect Resolve or handoff
KPI ins_bot_resolution: target > 75%
FAQ
Difference with #361?
#361 = SHIP-INS agent macros. #362 = bot automation for coverage and claims.
Does the bot approve claims?
No. Route or agent approves. Bot sends link and proof checklist.
Intact package but broken product?
ins_bot_warranty_triage → warranty #349, not insurance.
Express delay covered?
No if package is intact. ins_bot_express_delay + link #338.
Without Route installed?
Bot FAQ policy merchant + customer service handoff form #361.
Going further
Test staging: Route protected order, message "broken package covered?", check coverage FAQ + claim link without refund promise.
Share this guide #362 with ops and CRM: a well-calibrated insurance bot turns the claim process into a 30-second step, not a warranty dispute.
Enzo
July 30, 2026
