E-commerce
July 29, 2026
"I paid for shipping insurance, how do I get a refund?" "My package arrived broken, is it covered?" "I didn't check the protection box, what should I do?" Three questions on the same poorly-documented subject: post-purchase package insurance.
Route states that its protection covers lost, stolen, or damaged packages in transit, with claims filed via the Resolve Center within 30 days (Route, policies 2026). Onward estimates that a well-explained checkout protection can reduce shipping-related support tickets by 30% to 40% (Onward, protection Shopify 2026).
This guide #361 addresses e-commerce shipping insurance customer support: answering questions about coverage, exclusions, and the claim process. No existing content covered this topic from a customer support perspective. It prepares the future insurance bot (#362) with a focus on policy ops, agent macros, and claim routing vs. product warranty.
Summary
Why does shipping insurance generate support tickets?
Delivery support insurance comes into play when the customer experiences a transport loss or anticipates a risk. Without a clear policy, the agent confuses package insurance, product warranty, and carrier liability.
Five customer frustrations
Vague coverage: "insurance" at checkout without detail of exclusions
Who to contact: store vs Route vs carrier
Not purchased: customer discovers the option after the incident
Claim deadline: 30 days max, late customer
Delay ≠ loss: delayed express delivery not covered by Route
Route specifies that carrier delays on express delivery are not covered if the package arrives intact (Route, exclusions 2026).
Angle #361
Delivery guides (#338 express, #340 help page) cover deadlines and costs. The warranty (#62, #349) covers product defects. #361 isolates in-transit package insurance: customer questions, claim process, support macros.
DTC Example
Decor brand, Route opt-in 42% adoption, 67 insurance tickets/month. After SHIP-INS policy + 8 macros: insurance_support_resolution 82%, wrong warranty routing -55%, CSAT claim 4.4/5.
Claim SLA
P1 priority if package is declared stolen or broken upon receipt. Response < 4 hours with process link or claims handoff.
Typical volume
On a store with checkout protection, expect 1 to 3% of post-shipment tickets to be related to insurance or package damage. Peak during package theft periods (holidays, summer).
Cost of bad routing
Agent opens a warranty file for a crushed package: 5 to 10 days lost, customer follows up 3 times. Insurance vs warranty triage in the first response avoids this cycle and preserves post-claim trust.
Carrier vs Insurance Difference
The carrier sometimes compensates based on limited contract liability (deductible, 21-day delay). Opt-in Route insurance covers according to marine cargo policy with accelerated resolution. The agent must understand both frameworks without mixing them up in the same promise.
How does it differ from the guarantee and the express?
Six neighboring contents, six distinct support roles.
Insurance bot (#362)
The future insurance bot (#362) will automate coverage and exclusions. #361 sets up the human policy and macro bot base.
Express delivery (#338)
Express (#338): cut-offs, delays. #361: express delay not covered by insurance, claim covered.
Product warranty (#62, #349)
Warranty (#62) and bot warranty (#349): manufacturing defect. #361: transit damage, not product failure.
Split shipment (#356)
Split (#356): multi-package WISMO. #361: claim on package N, claim by tracking.
Delivery help page (#340)
Help page (#340): pre-purchase conversion. #361: post-purchase claim and insurance FAQ.
Damaged package returns
Returns bot: RMA after claim resolution. #361 intervenes before return: insurance eligibility.
Promise #361
SHIP-INS policy, INS-CLAIM tree, 8 SHIP-INS-* macros, Route vs merchant routing, insurance_support KPI.
Which customer questions should be categorized before answering?
Map the delivery insurance questions before macros and bot #362.
Ten scenarios to tag
ins_coverage_question: what is covered?ins_exclusion_question: delay, wrong item, qualityins_claim_howto: how to file a claimins_not_purchased: not purchased at checkoutins_lost_transit: lost package, tracking blockedins_stolen_porch: theft after deliveryins_damaged_delivery: damaged package upon receiptins_claim_denied: claim denied, disputeins_vs_warranty: confusion between insurance / warrantyins_premium_refund: refund protection fees
Required ticket fields
order_id, route_protected (bool), carrier, tracking_status, delivery_date, claim_filed (bool), photos_damage (bool). See taxonomy (#135).
Distinction between insurance vs carrier
Carrier liability (Colissimo, DHL) ≠ opt-in Route insurance. POLICY SHIP-INS documents who to process according to order metafield protection.
Ticket mining 90 days
Export "insurance", "Route", "damaged package", "stolen", "protection". Prioritize macros for top 5 verbatims.
How to structure the SHIP-INS policy?
The SHIP-INS policy aligns agents, FAQs, and future bot #362.
Ten policy blocks
Verify protection: Route order or merchant self-insured
Covered: lost, stolen, damaged in transit
Not covered: delay only, wrong SKU, product quality, damage post 30 days
Claim window: 30 days from tracking or delivery depending on the incident
Proof: packaging photos + damaged product photos are mandatory
Route orders: redirect to Resolve Center, no direct agent refund
Unprotected: goodwill policy or carrier claim
No warranty: route to warranty if defect is non-transit related
Premium refund: cancellation before shipping only
Escalation: claim denied + amount > threshold → supervisor
INS-CLAIM Flow
Five branches: lookup protection → incident type (lost/stolen/damaged) → timeframe OK → evidence collected → redirect to Route or merchant claim form.
ins_not_purchased branch
Route cannot add post-purchase protection (Route, FAQ merchant 2026). Options: carrier liability, goodwill policy, polite documented refusal.
ins_vs_warranty branch
Package intact, product defective → warranty (#62). Package damaged upon receipt → ins_damaged_delivery.
Unprotected goodwill grid
Document ops thresholds: replacement if clear photos + client's first incident; refusal if customer has a history of abuse claims. Prevents each agent from improvising a different response on ins_not_purchased.
Which SHIP-INS macros for agents?
Eight SHIP-INS macros cover 90% of delivery insurance tickets.
SHIP-INS-COVER-01 (coverage)
"Your order #[X] includes delivery protection. Covered: package lost in transit, reported stolen after delivery, damaged upon receipt. Not covered: delay only, wrong item, product defect unrelated to transport damage. File a claim: [Resolve Center link]. Deadline: 30 days."
SHIP-INS-CLAIM-02 (Route process)
"File your claim here: [Route Resolve link]. Prepare photos of the outer packaging + inner packaging + product, and order number #[X]. Route typically processes claims within 24 to 48 hours. We are kept updated on the status."
SHIP-INS-NOPROTECT-03 (not purchased)
"Order #[X] without checkout protection. We are contacting the carrier [carrier] regarding potential liability. Carrier processing time: 15 to 30 days. We will get back to you within 5 business days with options."
SHIP-INS-DAMAGE-04 (damaged package)
"Sorry for this damage. Before opening the product: take photos of the packaging and the carrier label. If protection is active: claim [link]. If not: reply with 3 photos for the carrier file."
SHIP-INS-STOLEN-05 (theft)
"If tracking indicates delivered but the package is missing: file a theft claim within 30 days with carrier proof of delivery. If Route protection: [link]. File a police report for proven theft if applicable to your home insurance."
SHIP-INS-EXPRESS-06 (delay not covered)
"The protection does not cover express delays if the package is delivered intact. Please contact us in case of damage or confirmed loss. For express shipping fee refunds: see express policy (#338)."
SHIP-INS-WARRANTY-07 (warranty redirect)
"Package received intact, product defective: this is not a transport issue. Your request falls under the product warranty: [warranty customer service link]."
SHIP-INS-DENIED-08 (claim denied)
"Claim denied for reason [X]. To appeal: reply with additional details within 7 days. Escalate to supervisor if amount > [threshold] €."
How to route Route vs. merchant claims?
The insurance claim workflow differs depending on Route, third-party app, or merchant self-insurance.
Route Flow (majority of DTC Shopify)
Customer files a claim in the Resolve Center
Route evaluates policy eligibility
If approved: merchant refunds/reships, Route reimburses the merchant
Store support informs the customer, does not duplicate refund
Route documents: merchant issues refund or reorder then requests reimbursement via portal (Route, claims process 2026).
Self-insured merchant Flow
CS Form + photos → ops review within 48 hours → reship or refund → carrier claim if recourse is available.
Unprotected Flow
Colissimo/DHL carrier file opened → 15-30 days delay → commercial gesture if carrier refuses, according to the SHIP-INS grid.
Standard Evidence
Route requires damage photos/videos in the claim process. Agent collects them before redirecting if the customer contacts the store first.
Communication SLA
Claim acknowledgment within 4 hours. Customer update every 48 hours as long as the claim is open. No promise of refund before Route or ops approval.
How to communicate reassurance before and after purchase?
Checkout insurance communication reduces post-purchase tickets if clear pre-purchase.
Opt-in vs opt-out
Route offers opt-in and opt-out depending on the merchant config. Checkout wording must list coverage and exclusions in one sentence.
Pre-purchase FAQ
/shipping page or PDP: "Package protection: covers loss, theft, damage in transit. Does not cover delays. Claim within 30 days." Link to Route policy.
Confirmation email
If protection purchased: reminder of Resolve Center link + order number. Reduces ins_claim_howto D+1 tickets.
Tracking page
"Delivery issue?" button → redirect to Route if protected, support form otherwise.
Agent training
Never promise coverage outside of policy. Always State order protected yes/no from Shopify metafield or Route portal.
Premium transparency
Customer asks why €2.50 protection: explain transit incident, not product warranty extension. Premium refund if cancelled before fulfillment only.
How to set up Shopify and protection apps?
The Shopify delivery insurance setup connects the protection app, helpdesk, and SHIP-INS policy.
Common Apps
Route: licensed protection, Resolve Center (Shopify App Store)
Onward, ShipProtect, Protectify: self-serve claims alternatives
Merchant self-insured: no app, courtesy policy + carrier
Order Metafields
Tag route_protected, insurance_premium_amount, protection_provider. Helpdesk sidebar displays status before agent response.
Helpdesk Integration
Macro auto-inserts Resolve link if route_protected=true. Otherwise SHIP-INS-NOPROTECT-03.
Checkout UX
Clear label "Parcel Protection" not just "Insurance". "Learn more" link to FAQ #361 coverage section.
Route Merchant Reporting
Route Portal: claims tab, reimbursement requests. Ops weekly review of denied claims to adjust FAQ.
Which KPIs should be measured for insurance support?
Without the insurance_support KPI, it is impossible to steer SHIP-INS and protection adoption.
Seven Key Metrics
insurance_support_volume: tickets / protected orders of the month
insurance_support_resolution: first-contact resolution / total
ins_wrong_routing_rate: sent to warranty by mistake
ins_claim_redirect_rate: redirect Route OK / protected
ins_denied_contest_rate: denied claim disputes
ins_nop protect_gesture_rate: commercial gestures on non-protected orders
CSAT intent insurance: claim satisfaction
DTC Benchmark
Target insurance_support_resolution > 80%, ins_wrong_routing_rate < 5%, claim CSAT > 4.2/5.
Adoption Correlation
If ins_not_purchased tickets dominate: review checkout opt-in wording. Target adoption is 40% to 50% with standard opt-in.
Monthly Review
Top claim types (damage vs. stolen vs. lost), top carriers, adjust macros and FAQ.
Claim Dashboard
Cross-reference insurance_support_volume with Route approved claim rates. A spike in ins_damaged_delivery tickets without an increase in approved claims signals agents redirecting incorrectly or customers without sufficient photos: enrich macro SHIP-INS-DAMAGE-04.
What edge cases and escalations should be anticipated?
Six shipping insurance edge cases require a special procedure.
Split shipment damaged parcel 2
Claim by tracking for a damaged parcel. Verify that protection covers the entire order. Link split (#356).
International customs
Parcel held by customs then damaged: check Route international policy exclusion. Handoff to ops if in doubt.
Required signature refused
Returned to carrier warehouse: lost in return transit vs ins_not_purchased depending on tracking status.
Partially damaged kit product
Photos of each SKU. Claim for partial amount or reship parts according to merchant policy post-Route approval.
Customer threatens claims-related chargeback
P1 priority, redirect claim if protected, supervisor if unprotected amount > €150.
Claim outside 30-day window
Route may refuse. Agent empathy + documented policy refusal, no exception without ops director approval.
Recipient gift claim
Recipient contacts customer support: check if buyer has protection. Redirect buyer for claim if Route policy requires it, or collect recipient proof depending on merchant config.
How does Qstomy handle delivery insurance?
Qstomy routes ins_* intents with lookup protection order, SHIP-INS RAG policy, and Resolve Center redirect.
Capabilities
ins_protection_lookup: Route yes/no + premium
ins_coverage_faq: covered vs exclusions
ins_claim_link: Resolve Center URL
ins_warranty_triage: warranty redirect if intact
ins_photo_collect: damage handoff with proof
Encrypted DTC Scenario
Fashion brand, 58 insurance tickets/month, agents used to confuse warranty and insurance.
After Qstomy + SHIP-INS: 74% auto-resolved, insurance_support_resolution 84%, ins_wrong_routing_rate 3%, CSAT 4.5/5.
Explore AI support, Shopify, request a demo.
What checklist is needed to launch SHIP-INS?
SHIP-INS Checklist (10 steps)
Audit insurance tickets 90 days
Identify provider (Route, other, self)
Write SHIP-INS policy section 4
Import 8 SHIP-INS-* helpdesk macros
Configure route_protected sidebar metafield
Publish checkout + /delivery coverage FAQ
Train agents on the INS-CLAIM flow
Document standard photo evidence
Weekly insurance_support_resolution dashboard
Monthly review of denied claims + FAQ
In brief
#361 = after-sales shipping insurance, not product warranty (#62)
Covered: lost, stolen, damaged in transit
Not covered: delay only, wrong SKU, quality
Route protected: redirect to Resolve Center
KPI insurance_support_resolution: target > 80%
FAQ
Is shipping insurance the same as warranty?
No. Insurance = shipping incident. Warranty = product defect.
Is express delay covered?
No if the package is intact (Route). See express (#338) for shipping cost gestures.
Can protection be added after purchase?
Route: no. Cancel/reorder if unfulfilled, otherwise carrier or merchant gesture.
Who refunds if the claim is approved?
The merchant refunds the customer, Route reimburses the merchant if Route protection is active.
What is the difference with bot #362?
#361 = human policy ops. #362 = coverage and claim automation bot.
Going further
Perform a mystery shop test: protected order, simulated damaged package, check macro SHIP-INS-CLAIM-02 and Resolve redirect without double agent refund.
Share this guide #361 with support and ops: well-explained shipping insurance turns an incident into a clear process, not a warranty dispute.
Enzo
July 29, 2026
