--- title: "Freight Damage Claims Management | Kylon" description: "How a claims team disposes carrier damage claims against the tariff, reviews the filing manifest and applies carrier answers in one Kylon room, with people approving." url: "https://kylon.io/use-cases/carrier-damage-claims" language: "en" --- [HOME](https://kylon.io/)\>[Use Cases](https://kylon.io/use-cases)\>Carrier Damage Claims: Filings That Match the Tariff and the Paperwork Use Case7 min read # Carrier Damage Claims: Filings That Match the Tariff and the Paperwork Thirty freight damage claims, the filing manifest, carrier acceptances, a disputed delivery receipt and a tariff revision run through one Kylon room. Agents read ClickUp and the Dropbox claim packets, and the claims manager approves every change. [Get started](https://app.kylon.io/sign-up) Kylon TeamProduct November 6, 2026 ## Thirty claims, three carriers and a tariff that caps what can be recovered When freight arrives damaged, the claims team has a filing window and a list of documents to assemble: the bill of lading, the delivery receipt with any exception noted, photos from the dock, the commercial invoice and a repair or salvage estimate. Each carrier's tariff caps its liability, often by weight or freight class, so the amount filed is not always the invoice value. Claims are tracked in ClickUp, the packets sit in Dropbox, and the policy, tariff tables and filing manifest are in Google Drive. Carriers write to the claims mailbox in Outlook, customers and account managers use Gmail, and the receiving dock posts damage exceptions in Slack. Most carrier mail is notices that need no answer, mixed in with the few threads that do. ## Who works in the room People - Claims manager Owns the claims policy, approves each disposition and amount, and decides on settlements - Claims specialists Build the filing manifest, file with carriers and send the replies - Account manager Handles the customer side of an escalated claim Agents - AdaClaims adjudicator Disposes each claim under the policy and the carrier tariff from its document packet, and re-checks claims when a carrier answers ClickUpDropboxGoogle Drive - RyanCarrier and customer mail Reads carrier and customer threads, sorts notices from questions, and drafts a reply only where one is needed Outlook[Gmail](https://kylon.io/integrations/gmail)ClickUp - NovaManifest and follow-ups Checks the filing manifest against approved dispositions and sets up a follow-up for every open claim Google DriveClickUp[Slack](https://kylon.io/integrations/slack) Ryan holds the Outlook and Gmail connections in this room, so it reads every incoming thread first and sorts notices from questions. Ada is the default agent and owns each claim's disposition, so a dock photo posted without a name goes to Ada. When a carrier's reply changes a claim, Ryan mentions Ada with the claim id and the message, and Ada leads from there. Nova picks up from the approved dispositions to check the manifest. ## From packet to settlement The claims policy and the carrier tariffs apply to every claim in the cycle. For the first pass, Ada can split the thirty packets across parallel helpers and get one result back. Every step stops at a person before ClickUp changes. ```mermaid flowchart TD dock([The dock posts a damage
exception in Slack]) disp["Ada disposes each claim from its
packet, capped by the tariff"] ok1["Claims manager approves
before ClickUp is updated"] manifest["Nova checks the filing manifest
against the approved dispositions"] answers([Carriers answer in
the claims mailbox]) update["Ada updates only the claims
whose disposition changes"] reply["Ryan drafts one reply per thread
that needs one, none for notices"] send["Claims manager approves,
claims specialist sends it"] tariff["Ada re-checks only claims still
in the carrier's queue"] tok["Claims manager approves
changed amounts"] esc["Ryan drafts a reply to the
customer escalation"] am["Account manager sends the reply"] follow["Nova proposes a ClickUp follow-up
for every open claim"] confirm["Claims manager confirms the list"] dock --> disp --> ok1 --> manifest --> update answers -.- update update --> reply --> send send -->|new tariff| tariff --> tok send -->|escalation| esc --> am tok & am --> follow --> confirm class disp,manifest,update,reply,tariff,esc,follow agent class ok1,send,tok,am,confirm person class dock,answers event classDef agent fill:#FFFFFF,stroke:#DCD3C8,color:#1B1712 classDef person fill:#EEF0E3,stroke:#6E7447,color:#1B1712 classDef event fill:#F4ECDD,stroke:#F4ECDD,color:#564C42 ``` | Stage | What happens | Who acts | Who decides | | --- | --- | --- | --- | | Claim disposition | Each claim is filed, held for documents, denied or referred to insurance, with the amount capped by the tariff | Ada, from ClickUp and the Dropbox packets | The claims manager approves before ClickUp is updated | | Manifest review | The specialist's filing manifest is checked against the approved dispositions | Nova | The specialist corrects the manifest | | Carrier responses | Acceptances and a disputed delivery receipt update only the claims they name | Ada, and Ryan for any reply | The claims manager approves and a specialist sends the reply | | Tariff revision | Claims still in the carrier's queue are re-checked against the new limits | Ada | The claims manager approves changed amounts | | Escalation | A customer escalation moves one claim up the queue and gets a reply | Ryan | The account manager sends the reply | | Follow-ups | Each open claim gets a ClickUp follow-up named with its claim id | Nova | The claims manager confirms the list | One month of claims work. Claim numbers, carriers and amounts are illustrative. ## Carrier answers, a disputed receipt and a new tariff Carriers answer at their own pace. One accepts two claims in full, another accepts one at a reduced amount, and a third disputes a claim because the delivery receipt was signed clean. Ada updates only the claims whose disposition actually changes, and a claim that is still waiting keeps its status even if the carrier wrote about it. For the disputed receipt, Ada pulls the dock photos and the driver's exception note from Dropbox and lays them out in the thread for the claims manager. A tariff revision has a boundary. It applies to claims still in the carrier's queue, and claims already paid, declined or withdrawn stay where they are. Many messages need no answer at all: a carrier's acknowledgment that a claim was received, or a notice that its tariff changed, is information, and Ryan drafts nothing for it. The threads that do need a reply get exactly one draft each. ## What the checks catch - Carrier notices kept free of replies, and exactly one draft on each thread that needs an answer - A tariff revision applied only to claims still in the carrier's queue - A status change on a claim whose disposition did not change - A claim filed above the carrier's liability limit for its weight or freight class - A follow-up for every open claim, named with the exact claim id ## What stays with people - Approving each disposition and filing amount before ClickUp changes - Sending every reply to a carrier or customer, which Ryan prepares as a draft - Deciding whether to accept a reduced settlement or refer a claim to insurance - Confirming recovered amounts with finance ## Integrations in this workflow Kylon is not a freight claims or transportation management system, and it does not replace one. It works across the claims team's existing tools and keeps each claim's coordination in one thread. Ada reads the Dropbox claim folders through a lasting grant the claims manager approved for this room, and Ryan drafts mail as the specialist it is working for, checked on every call. - ClickUp - Dropbox - [Gmail](https://kylon.io/integrations/gmail) - Google Drive - Outlook - [Slack](https://kylon.io/integrations/slack) - **ClickUp** holds each claim with its disposition, amount and follow-ups - **Dropbox** holds the claim packets: photos, bills of lading, delivery receipts and invoices - **Outlook** is the claims mailbox where carriers write, and replies there are drafts a specialist sends - **Gmail** carries customer and account manager threads, including escalations - **Google Drive** keeps the claims policy, the carrier tariff tables and the filing manifest - **Slack** is where the receiving dock posts damage exceptions as freight comes in ## Where to start Choose one carrier and one month of claims. Connect the ClickUp list and the Dropbox claims folder, and write one rule into the room guidelines: a claim's status changes only when its disposition changes, and the claims manager approves that change first. > “Notices get read, replies go only where they are needed, and claims that did not change keep their status.” ## Set it up with your agent Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it. Set-up prompt Set up our carrier damage claims desk in this Room. Take it one step at a time and wait for my OK before you move on. 1. Connect ClickUp, Dropbox, Gmail, Google Drive, Outlook and Slack. Tell me which ones still need connecting. 2. Ask me who works this desk: the claims manager, the claims specialists who build filing manifests and send replies, and the account manager who handles customer escalations. Help me invite them to this Room. 3. Build a Freight Claims App with columns Documenting, Filed, Carrier review and Settled, one record per claim. Pull open claims from ClickUp and match each to its Dropbox packet. 4. Check each claim packet against the carrier tariff tables in Google Drive. Flag any claim filed above the carrier's liability limit for its weight or freight class. Propose a disposition and amount for each, and show me the ones that fail our checks. 5. Draft carrier replies in Outlook and customer replies in Gmail only where a thread needs an answer. Hold every draft until the claims manager approves the disposition and amount, and until a specialist sends each reply. Flag each escalation for the account manager to send. 6. Write into this Room's guideline that a claim's status changes only when its disposition changes, that the claims manager approves every disposition and amount before ClickUp changes, and that the account manager sends escalation replies. 7. After one clean cycle, offer to turn open-claim follow-ups into an Automation. Before you start, ask me for our rules one at a time. [Get started](https://app.kylon.io/sign-up) Your first company harness. Where humans and agents run your business together. [Get started](https://app.kylon.io/sign-up) ## More Use Cases [View all](https://kylon.io/use-cases) [ ### Backorder Communications: Customers Hear the Latest Date, Not Last Week's Customers hear the latest supplier date, an approved substitute or a cancellation offer, line by line. Agents work Pipedrive lines against Outlook notices and the Notion substitution table in one Kylon room, and every notice is a draft a rep sends. Logistics & supply chainEmail operationsSupport & customer success ](https://kylon.io/use-cases/backorder-communications)[ ### Constrained Order Allocation: Short Stock Shared by Priority, Walk After Walk Short stock is shared by priority tier and walked again after every receipt, tier change and cancellation. Agents work the Salesforce orders in one Kylon room, report every order after each walk, and the planner approves the full result. Logistics & supply chainSupport & customer success ](https://kylon.io/use-cases/constrained-order-allocation)