--- title: "Cold Chain Excursion Review With AI Agents | Kylon" description: "How a QA team totals excursion minutes, dispositions shipments against stability budgets and closes the week in one Kylon room, with every release approved by a person." url: "https://kylon.io/use-cases/cold-chain-excursions" language: "en" --- [HOME](https://kylon.io/)\>[Use Cases](https://kylon.io/use-cases)\>Cold Chain Excursion Review: Every Shipment Dispositioned Against Its Stability Budget Use Case9 min read # Cold Chain Excursion Review: Every Shipment Dispositioned Against Its Stability Budget Logger files, stability budgets, QA reviewer assignments and carrier claims run through one Kylon room. Agents total the minutes out of range and check the manifest, and the QA lead approves every release and reject before a record changes. [Get started](https://app.kylon.io/sign-up) Kylon TeamProduct November 6, 2026 ## Minutes out of range, a budget per product and a manifest that has to agree An excursion review looks simple on paper. Each shipment's data logger shows how long the product sat outside its labeled range, each product carries a stability budget of allowed minutes, and minutes spent earlier in the lot's journey count against that budget. A shipment within budget is released, one close to the limit goes to a QA reviewer, and one over budget is rejected. In practice the logger files land in Box, the shipment and product records live in Airtable, carrier reports arrive in the logistics team's Outlook mailbox, and receiving staff post in Slack when a logger is missing. The manifest the warehouse works from is assembled from all of it in a spreadsheet. A budget revision or a late logger download means someone recomputes minutes by hand and hopes every dependent field moved with them. ## Who works in the room People - QA excursion lead Approves every disposition and reviewer assignment, decides borderline cases and signs the weekly close-out - QA reviewers Take quarantined shipments, examine the logger data and record a conclusion - Distribution coordinator Owns the manifest and carrier claims, and sends notices to carriers and consignees - Stability scientist Issues budget revisions when new stability data changes the allowed time out of range Agents - MycoExcursion analyst Reads each logger file, totals the minutes out of range, compares them with the product's remaining budget and proposes a disposition and a reviewer BoxAirtableGoogle Drive - RyanManifest checker Checks the manifest and every changed record against the approved dispositions, including the fields that have to move alongside them AirtableGoogle Drive - FinCarrier and consignee notices Drafts claim notices and disposition notices for a person to send, and brings receiving updates in from Slack Outlook[Gmail](https://kylon.io/integrations/gmail) [Slack](https://kylon.io/integrations/slack) The QA team keeps one Kylon room for excursions with Myco as its default agent, so a question about a shipment's minutes or disposition reaches Myco without a mention. The room guidelines send manifest questions to Ryan and anything addressed to a carrier or consignee to Fin. Myco reads Box and writes Airtable through a lasting grant the QA lead approved for this room. Fin drafts into the logistics mailbox through a grant the distribution coordinator approved, and each draft waits there for a person to send it. ## A week of excursions, from logger file to close-out The excursion procedure and the current budgets sit in a Drive folder the room guidelines point to, so every agent works from the same version. Each step ends with a person. ```mermaid flowchart TD logger([Logger files land in Box]) total["Myco totals minutes out of range
against the remaining budget"] ok1["QA excursion lead approves
each disposition"] assign["Myco proposes a QA reviewer
within each reviewer's load"] manifest["Ryan compares the draft manifest
with the approved dispositions"] fix["Coordinator corrects it,
QA excursion lead signs off"] late["Fin brings in a receiving
update from Slack"] rerun["Myco re-runs only the shipments
a late report names"] lateok["QA excursion lead approves
the changed records"] budget([The stability memo revises
a budget in hours]) convert["Myco applies it in whole minutes
to the product and open shipments"] side["Ryan checks the side effects,
such as a reviewer to give back"] sci["Stability scientist confirms,
QA excursion lead approves"] close["Myco counts by product and
disposition from current records"] sign["QA excursion lead signs the week"] logger --> total --> ok1 ok1 -->|quarantine| assign ok1 -->|release, reject| manifest assign --> manifest --> fix fix --> late & convert budget -.- convert late --> rerun --> lateok convert --> side --> sci lateok & sci --> close --> sign class total,assign,manifest,late,rerun,convert,side,close agent class ok1,fix,lateok,sci,sign person class logger,budget 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 | | --- | --- | --- | --- | | Logger review | Every shipment's minutes out of range are totaled from its logger file and compared with the product's remaining budget | Myco, from Box logger files and Airtable product rows | The QA lead approves each disposition before Airtable changes | | Reviewer assignment | Quarantined shipments get a QA reviewer within each reviewer's open load | Myco | The QA lead confirms the assignments | | Manifest check | The coordinator's draft manifest is compared line by line with the approved dispositions | Ryan | The coordinator corrects it and the QA lead signs off before it goes out as one complete file | | Late reports | A late logger download or a carrier temperature trace re-runs only the shipments it names | Myco, then Ryan | The QA lead approves the changed records | | Budget revision | A revised budget is converted to whole minutes and applied to the product row and every open shipment of that product | Myco | The stability scientist confirms the figure, then the QA lead approves | | Close-out | Counts by product and disposition are taken from the current Airtable records | Myco, checked by Ryan | The QA lead signs the week | Stages of a weekly excursion review. Shipment numbers, products and minutes in this example are illustrative. ## When a report or a budget changes mid-week Most changes arrive as messages. A receiving clerk posts in Slack that a missing logger turned up at the bottom of a tote. A carrier emails a temperature trace for a leg the shipment logger did not cover. A QA reviewer is out for the rest of the week, so her open shipments are proposed to the others within their load. Myco treats each message as the source for that change, re-runs only the shipments it touches and leaves a note on every changed record saying why it moved. A budget revision is the change most likely to leave something behind. The stability memo states the new budget in hours, so the figure is converted to minutes and rounded down as the procedure says, and it has to land on the product row as well as on every open shipment of that product. A shipment that moves from quarantine to release also has to give its reviewer back. Ryan checks those side effects before the QA lead approves, and every agent turn that uses a tool keeps a step-by-step run history, so an auditor can see which logger file and which budget figure produced each disposition. ## What the checks catch - Minutes carried with a fraction after a budget revision, when the procedure rounds down to whole minutes - A released shipment that still names a QA reviewer, which leaves work open on someone's list - A revised budget applied to the shipments but not to the product's own row in Airtable - A carrier email accepting liability for an excursion, which settles the claim but does not make the product releasable - A manifest line whose disposition disagrees with the approved record, or a shipment missing from the manifest altogether ## What stays with people - Approving every disposition and reviewer assignment before Airtable is updated - Deciding borderline cases where the logger data is incomplete or the trace is ambiguous - Sending every carrier and consignee notice, which Fin prepares as a draft in Outlook or Gmail - Signing the weekly close-out ## Integrations in this workflow Kylon is not a quality management system or a temperature monitoring service, and it replaces neither. It sits across the tools the QA team already uses and keeps the coordination between them in one place. - Airtable - Box - [Gmail](https://kylon.io/integrations/gmail) - Google Drive - Outlook - [Slack](https://kylon.io/integrations/slack) - **Airtable** holds the shipment and product tables, with dispositions, reviewers and stability budgets - **Box** stores the logger downloads and temperature reports for each shipment - **Outlook** is the logistics mailbox where carrier reports arrive and claim notices go out as drafts a person sends - **Gmail** carries disposition notices to consignee sites, each one a draft the coordinator sends - **Google Drive** keeps the excursion procedure, the budget memos and the draft manifest - **Slack** is where receiving staff outside the room report missing loggers and damaged packaging ## Where to start Start with one product family and one week of shipments. Connect the Airtable base that holds your shipments and products, point the room at the Box folder where logger files land, and put the one rule that matters in the room guidelines: an agent may total minutes and propose dispositions, and the QA lead approves every release and reject before a record changes. > “The arithmetic was never the hard part. Keeping every field that depends on it in step was.” ## 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 cold chain excursion review desk in this Room. Take it one step at a time and wait for my OK before you move on. 1. Connect Airtable, Box, Gmail, Google Drive, Outlook and Slack. Tell me which ones still need connecting. 2. Ask me who works this desk: the QA excursion lead, the QA reviewers, the distribution coordinator and the stability scientist. Help me invite them to this Room. 3. Build an Excursion Review App with Shipment, Minutes out, Disposition and Status, one record per shipment. Pull open shipments from Airtable and match each to its logger file in Box. 4. Read each logger file, total the minutes out of range and compare them with the product's remaining stability budget. Propose a disposition and a reviewer for each shipment and show me the ones that are over the threshold we set or close to it. 5. Check the draft manifest line by line against the approved dispositions, including reviewer fields and every shipment missing from the manifest. Flag every disagreement for the coordinator to correct before the QA lead signs off. 6. Draft carrier claim notices and consignee disposition notices into Outlook and Gmail. Hold every draft until the distribution coordinator sends it. The QA lead approves every disposition before Airtable is updated. 7. Write the approval order and who approves what into this Room's guideline so every excursion follows the same steps. 8. After one clean week, offer to turn the weekly close-out 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) [ ### Clinical Site Monitoring: A Monthly Visit Plan That Holds Up When Things Change Site dispositions, monitor assignments, schedule reviews and mid-cycle changes run through one Kylon room. Agents work the Salesforce and Box records, and the desk lead approves every assignment before a visit is booked. Healthcare & life sciencesScheduling & dispatchCompliance & risk ](https://kylon.io/use-cases/clinical-site-monitoring)[ ### Interpreter Scheduling: A Week of Assignments That Holds Through Sick Calls and Time Moves A week of interpreter requests is matched in policy order, checked against every calendar and kept right through sick calls, time moves and language fixes. The coordinator approves each assignment in the Kylon room before anything is booked. Healthcare & life sciencesScheduling & dispatch ](https://kylon.io/use-cases/interpreter-scheduling)