Frequently asked questions

Start by documenting your current claims SOP: which carriers you file with, what documentation you collect, and when you escalate. CorePiper's agents encode that SOP, monitor your orders for exceptions, gather documentation automatically, and file claims with each carrier's API. Most teams automate 80%+ of claims within the first month. See claims automation.

A delivery exception is any event that prevents a package from being delivered on its scheduled date — lost, damaged, stolen, delayed, returned to sender, or undeliverable. Each carrier uses its own exception codes (e.g., FedEx "DEX 07", UPS "Delivery Attempted"). Exceptions are the trigger point for most carrier claims. Glossary of shipping terms.

FedEx claims typically resolve in 5–7 business days for straightforward cases and up to 30–60 days for disputed or high-value claims. Claims must be filed within 9 months for domestic shipments (60 days for international). Automating documentation collection is the biggest lever for faster resolution. Automate FedEx claims.

UPS claims usually resolve in 8–15 business days for approved claims, with payment issued within 30 days of approval. Damage claims must be filed within 60 days of delivery; lost package claims within 9 months. Missing or incomplete documentation is the single biggest cause of delay. Automate UPS claims.

USPS claims generally resolve in 5–10 business days once all documentation is submitted, though contested claims can take 30–60 days. Domestic claims must be filed within 60 days of mailing for most services. USPS requires the original mailing receipt and evidence of value. Automate USPS claims.

DHL claims typically resolve in 10–30 business days, with international shipments often taking longer due to cross-border investigation. Claims must be filed within 30 days of delivery for damage and within 120 days for loss. DHL requires commercial invoices and proof of value for all claims. Automate DHL claims.

Standard documentation includes the tracking number, proof of value (invoice or purchase receipt), photos of damage (for damage claims), packaging evidence, and the original shipping label. Some carriers also require a signed statement from the recipient. CorePiper collects all of these automatically from your OMS, helpdesk, and carrier APIs. See the full claims workflow.

Manually filed claims recover 40–60% on average, largely because teams miss deadlines or submit incomplete documentation. Automated claims routinely recover 80–90% because every claim is filed on time with complete evidence. The difference is tens of thousands of dollars per month for mid-volume shippers. See results for e-commerce teams.

CorePiper supports FedEx, UPS, USPS, DHL, and major regional carriers out of the box, with direct API integration for claim filing. We also support freight carriers and 3PL-specific claim flows. If your carrier has an API, we can connect to it. See all supported carriers.

A carrier claim is a reimbursement request filed with the carrier (FedEx, UPS, etc.) for lost or damaged shipments under their default liability (typically $100). Shipping insurance is a separate policy — from the carrier or a third party — that covers declared value above that baseline. Most merchants end up doing both. See glossary definitions.

Gorgias is a helpdesk with AI assistance focused on conversation handling inside its own UI. CorePiper is an agent layer that runs your SOPs across Gorgias and the rest of your stack — carrier APIs, OMS, ERP — resolving tickets end-to-end rather than just drafting replies. Teams often run CorePiper on top of Gorgias. Compare in detail.

Zendesk AI (including Advanced AI and Zendesk Copilot) is optimized for reply generation and routing inside Zendesk. CorePiper's agents act across platforms — they can pull from Shopify, file a carrier claim, update Salesforce, and close the Zendesk ticket in one workflow. The difference is conversation assistance vs. end-to-end resolution. Compare in detail.

Salesforce Agentforce is tightly coupled to Salesforce Data Cloud and works best when Salesforce is your system of record. CorePiper is platform-agnostic and especially strong for teams running Zendesk, Gorgias, or Shopify-first stacks. We're SOP-driven from day one, while Agentforce relies heavily on prompt engineering. Compare in detail.

FreightClaims and similar claim-filing services are narrow point solutions — they file the claim, but leave exception detection, documentation gathering, and customer communication to you. CorePiper treats the claim as one step in a larger workflow that starts at exception detection and ends at customer resolution. You also don't share recovered dollars with a claim agency. See the full claims flow.

Building in-house agents looks cheap until you account for LLM infrastructure, integration maintenance, audit logging, human-in-the-loop tooling, and the ongoing cost of keeping agents aligned to changing SOPs. CorePiper ships all of that as a product, so your team focuses on writing SOPs, not maintaining ML infrastructure. Most teams ship in weeks instead of quarters. Explore the platform.