Plain-language definitions for the terms that come up across logistics claims, helpdesk operations, and AI agent deployments.
A 3PL is an external logistics provider that handles warehousing, fulfillment, and shipping on behalf of a merchant. 3PLs operate distribution centers, pick and pack orders, and hand off packages to carriers. Merchants use 3PLs to scale fulfillment without owning their own warehouses.
CorePiper's agents interact with 3PL systems through integrations to reconcile inventory, track shipments, and resolve fulfillment exceptions. See how e-commerce teams use CorePiper.
Back-office operations are the internal workflows that keep a business running but don't directly touch customers — reconciliation, data entry, claims, refunds, approvals, and cross-system updates. These are typically high-volume, rules-based tasks. They're the single biggest opportunity for AI automation.
CorePiper is built to automate back-office operations across platforms, not just customer-facing chat. See the platform.
A Bill of Lading is a legal document between a shipper and a carrier detailing the type, quantity, and destination of goods. It serves as a receipt of shipment, a contract of carriage, and a document of title. BOLs are required for freight claims and customs clearance.
Agents extract BOL data automatically when filing freight claims. Automate freight claims.
A carrier claim is a reimbursement request filed with a shipping carrier (FedEx, UPS, USPS, DHL) for packages that were lost, damaged, or delayed. Claims must be filed within carrier-specific deadlines with required documentation. Default carrier liability is usually capped at $100 per package.
CorePiper files carrier claims automatically with complete documentation to maximize recovery. See claims automation.
A carrier dispute is a formal challenge to a carrier decision — a denied claim, an incorrect surcharge, or a misrated shipment. Disputes require additional evidence and often involve escalation through the carrier's appeals process. Winning disputes consistently requires disciplined documentation.
Automated evidence collection increases dispute win rates substantially. Automate carrier disputes.
Case operations is the practice of managing customer and internal cases across their full lifecycle — intake, triage, investigation, action, escalation, and closure. Cases often span multiple systems (helpdesk, CRM, issue tracker). Effective case operations require consistent SOPs and cross-platform visibility.
CorePiper unifies case operations across Salesforce, Jira, and Zendesk. See case management.
A chargeback is a forced reversal of a payment initiated by the customer's bank, often due to disputed charges, fraud, or "item not received" claims. Merchants have a limited window to respond with evidence. Unresolved chargebacks result in lost revenue and higher processing fees.
Agents collect and submit chargeback evidence automatically so your team never misses a response window. See e-commerce use cases.
Claims automation is the practice of using software to detect claimable events, gather required documentation, file claims with carriers, and track resolution — without manual work. Automation typically raises recovery rates from 40–60% (manual) to 80–90%. It's one of the highest-ROI applications of AI agents.
CorePiper automates claims end-to-end across FedEx, UPS, USPS, and DHL. See claims automation.
Cross-platform automation means executing a single workflow across multiple systems — for example, reading from Shopify, updating Zendesk, and filing with FedEx, all in one agent run. Most real business workflows span 3+ systems, which makes cross-platform capability a requirement, not a nice-to-have. This is the core design of CorePiper.
CorePiper agents run cross-platform workflows natively. See unified automation.
Declared value is the merchant-stated value of a package used to determine carrier liability and insurance premiums. Without a declared value, liability defaults to a minimum (often $100 for FedEx/UPS). Accurately declaring value is critical for high-ticket shipments to ensure full recovery on claims.
Agents ensure declared value is captured for every eligible shipment. Learn more about claims.
A delivery exception is any event that prevents a package from being delivered as scheduled — lost, damaged, stolen, delayed, returned, or undeliverable. Exceptions are the trigger for most customer WISMO tickets and carrier claims. Detecting them early dramatically improves recovery and CX.
CorePiper monitors shipments in real time and acts on exceptions automatically. See exception handling.
A delivery exception code is a carrier-specific identifier for a delivery problem — e.g., FedEx "DEX 07" (delivery attempted), UPS "Address Correction Required", or USPS "Undeliverable as Addressed". Each code maps to a specific remediation path. Automation depends on mapping codes to the correct SOP.
CorePiper's carrier integrations parse exception codes and route them to the right SOP automatically. Browse integrations.
A freight claim is a reimbursement request filed against a freight carrier (LTL or FTL) for damaged, lost, or short-shipped cargo. Freight claims require BOLs, proof of damage, and commercial invoices, with deadlines typically ranging from 9 months to 2 years. Recovery rates without automation are notoriously low.
Agents file freight claims with complete documentation and track them to resolution. Automate freight claims.
Human-in-the-loop (HITL) is a workflow pattern where AI agents handle most steps autonomously but escalate specific decisions to a human for approval. HITL balances automation speed with human judgment on edge cases. It's essential for any workflow involving money movement or customer-facing actions.
CorePiper's agents escalate to humans on configurable triggers, with full context attached. See the platform.
Last-mile delivery is the final leg of a shipment, from the local distribution hub to the customer's door. It's the most expensive and most failure-prone stage of shipping, accounting for the majority of delivery exceptions. Solving last-mile issues is a primary driver of claims and WISMO volume.
CorePiper automates the customer-facing and carrier-facing work triggered by last-mile failures. See e-commerce workflows.
Package protection is a checkout-level add-on (from providers like Route, Seel, or native shipping insurance) that covers lost, damaged, or stolen packages. Merchants pass the cost to the customer, then rely on the provider to cover claims. Some teams build their own package protection using a mix of carrier claims and self-insurance.
CorePiper can operate inside either a third-party protection flow or a self-insured model. See claims workflows.
Proof of Delivery (POD) is documentation — signature, photo, or geolocation — confirming a package was delivered. Carriers use POD to defend against "item not received" claims. POD is a critical artifact for chargeback disputes and lost-package investigations.
Agents pull POD automatically to contest chargebacks and resolve WISMO cases. See claims automation.
Queue management is the practice of routing, prioritizing, and clearing work items in a helpdesk or operations queue. Traditional queue management relies on rigid rules; AI-driven queue management uses context, SLA proximity, and customer impact to prioritize dynamically. Good queue management is the difference between hitting SLAs and missing them.
CorePiper's agents handle queue items end-to-end, not just routing. See case management.
A shipping exception is a broader term for any deviation from the expected shipment path — including origin scan failures, transit delays, customs holds, and delivery exceptions. Exceptions surface early warning signs before a package is officially late. Acting on them proactively reduces both claims and customer complaints.
CorePiper acts on shipping exceptions the moment they appear in carrier data. See exception handling.
Shipping insurance is a policy (from the carrier or a third-party underwriter) that reimburses declared value beyond default carrier liability. It's distinct from a carrier claim: insurance pays out per the policy terms, while a claim recovers against carrier liability. Most shippers use a combination of both.
Agents handle both carrier claims and insurance claim flows. Learn more.
A Standard Operating Procedure is a documented, repeatable process that describes how a team handles a specific task — e.g., "how to file a FedEx damage claim". SOPs are the operational knowledge base of any team. They're also the ideal input for AI agents because they're already structured, reviewed, and owned.
CorePiper turns your existing SOPs into executable AI workflows. See SOP-driven agents.
SOP-driven AI is a design pattern where AI agents execute documented standard operating procedures step-by-step rather than free-forming responses from prompts. Every action is traceable to a specific SOP step, which makes agents predictable, auditable, and easy to update. This contrasts with prompt-first or chat-first AI products.
This is the core architecture of CorePiper. Read the deep dive.
Ticket automation is the use of software to resolve helpdesk tickets end-to-end — not just route or draft replies. True ticket automation reads the ticket, takes action across systems, updates the record, and closes the loop with the customer. It's distinct from ticket deflection (avoiding tickets) and ticket assistance (helping agents reply faster).
CorePiper's agents handle ticket automation across your full stack. See the platform.
WISMO stands for "Where Is My Order" — the single highest-volume support ticket type for e-commerce teams. WISMO tickets spike on delivery exceptions, shipping delays, and promotional pushes. Automating WISMO responses with live tracking data is one of the fastest automation wins for any CX team.
Agents answer WISMO tickets with real-time carrier data and proactive notifications. See WISMO automation.
Workflow automation is the broader category of software that executes multi-step business processes across systems. Traditional workflow tools (Zapier, Workato, n8n) require explicit rules; agent-based workflow automation uses AI to handle decisions, exceptions, and variations. Both approaches coexist — agents are best for knowledge-heavy, variable workflows.
CorePiper is an agent-based workflow automation platform purpose-built for operations. See the platform.
Dig deeper into how CorePiper applies these concepts across real operations workflows.
