For supply chain, logistics and fleet leaders
Fix freight exceptions before customers feel them
Ask out loud about a late container, a SKU about to stock out, the open loads on the board or a supplier that keeps missing dates. Tiersel reads your TMS, WMS, ERP and carrier data, shows every step it took, and waits for your approval before anything is booked, moved or sent.
Live demo on synthetic data · Built on Jev by TypeSafe AI
An animated example types requests as if they were spoken and shows the card Tiersel builds for each one.
For the VP Supply Chain, Director of Logistics or COO at a shipper, distributor, 3PL or carrier
Your planners spend the day stitching screens together.
A container slips at the port and someone has to find out which POs are on it, which stores and customers are short, and what an expedite would cost. A SKU runs low at one DC while another DC has plenty. Dispatchers juggle hours of service, equipment and empty miles by hand. Supplier problems show up in receiving before anyone looks at the scorecard. The data for every one of these decisions exists. It sits in five systems, and pulling it together takes longer than making the call.
4 agent workflows
Built for the work your team already does.
Each workflow starts from a sentence. The agent calls your systems, shows its evidence, and waits for a person before anything consequential happens. Every card below is the real, working interface.
Workflow 01 · Logistics manager or supply planner
Shipment exception recovery
01 · Trigger
A shipment slips
A carrier event, a customs hold or a revised ETA flags a container or truckload as late, or a planner asks about it.
02 · Tool call
Track and price
Reads the latest carrier and terminal events, then the POs, SKUs and customer orders tied to the shipment in the ERP and OMS.
03 · Tool call
Quote the options
Prices recovery options such as air freight for the fast movers, a reroute through another port, or a split shipment.
04 · Reasoning
Compare cost and days saved
Ranks each option by days recovered, cost and the share of units it covers, and checks it against the expedite policy.
05 · Human approval
Planner approves
The planner picks an option and decides whether affected customers get the revised date. Nothing is booked or sent before that.
Nothing happens until a person approves06 · Outcome
Customers hear first
The booking is made, affected customers get a new date, and the decision is logged against the shipment.
What changes
A late shipment goes from an alert to a priced, approved recovery plan with customers told, in one conversation.
Workflow 02 · Inventory planner or DC operations lead
Stockout risk and rebalancing
01 · Trigger
Morning risk check
A planner asks which SKUs are at risk, across the network or at one distribution center.
02 · Tool call
Read stock and inbound
Pulls on-hand from the WMS, open POs and ASN dates from the ERP, and the demand forecast for the next 14 days.
03 · Reasoning
Find the gaps
Compares days of cover with when inbound lands and with supplier lead time, and sizes the lost sales for each SKU.
04 · Tool call
Find the fix
Looks for DCs with stock above safety stock and the transit time between them, or an expedited PO when no DC can spare units.
05 · Human approval
Planner picks the fixes
The planner ticks the transfers and POs to create. Donor DCs stay above safety stock.
Nothing happens until a person approves06 · Outcome
Shelves stay full
Transfers go to the WMS and POs to purchasing as drafts, each tied to the forecast that justified it.
What changes
At-risk SKUs are caught while there is still time to move stock, with the fix and its sales impact on one screen.
Workflow 03 · Dispatcher or fleet manager
Load dispatch
01 · Trigger
Loads on the board
A dispatcher asks to cover the open loads in a region for the next day.
02 · Tool call
Read loads and drivers
Pulls open loads from the TMS, hours of service from the ELD, live truck positions and trailer types.
03 · Reasoning
Build the pairs
Matches equipment, checks each driver has hours for the trip plus deadhead, and minimizes empty miles across the plan.
04 · Human approval
Dispatcher approves
The dispatcher reviews each pair, drops any they disagree with, and approves the rest.
Nothing happens until a person approves05 · Outcome
Tenders go out
Drivers get the loads in their ELD app, and uncovered loads stay on the board for a broker carrier.
What changes
The board is covered with fewer empty miles, and the dispatcher reviews a plan instead of building it pair by pair.
Workflow 04 · Procurement or supplier quality manager
Supplier scorecard and corrective action
01 · Trigger
A supplier question
A buyer asks how a supplier is performing, often after a late receipt or a quality reject.
02 · Tool call
Score the history
Reads 12 months of receipts for OTIF and lead time, and nonconformance reports for defect rate in PPM.
03 · Tool call
Check risk and alternates
Pulls open POs, financial and site risk signals, and qualified alternates from the approved vendor list.
04 · Reasoning
Grade and compare
Grades the supplier against OTIF and quality targets and compares it with the alternates on OTIF, lead time, defects and price.
05 · Human approval
Buyer approves the request
A corrective action request, and an optional RFQ to an alternate, wait for the buyer to approve.
Nothing happens until a person approves06 · Outcome
Problems get a paper trail
The supplier receives the request with a response date, and the scorecard and decision are logged to the supplier record.
What changes
Supplier reviews start from a scorecard with evidence, and corrective actions go out while there is still time to protect open POs.
How it plugs in
An agent on your systems, one component per workflow.
Requests come in by voice, text or system event. The router picks the workflow, the agent calls your systems, and the answer lands as a live card where your team works. Nothing is written back until a person approves it.
In
Tiersel
Your systems
Out
Workflow blueprint · Logistics manager or supply planner
Shipment exception recovery
- Starts when
- A shipment slips. A carrier event, a customs hold or a revised ETA flags a container or truckload as late, or a planner asks about it.
- Reads
- Track and price. Reads the latest carrier and terminal events, then the POs, SKUs and customer orders tied to the shipment in the ERP and OMS.
- Quote the options. Prices recovery options such as air freight for the fast movers, a reroute through another port, or a split shipment.
- Decides
- Compare cost and days saved. Ranks each option by days recovered, cost and the share of units it covers, and checks it against the expedite policy.
- Waits for
- Planner approves. The planner picks an option and decides whether affected customers get the revised date. Nothing is booked or sent before that.
- Writes back
- Customers hear first. The booking is made, affected customers get a new date, and the decision is logged against the shipment.
This workflow is one component
export const shipment = defineSkill({id: "shipment", category: "supply",// when this workflow, and not a neighbour, is meantcriterion: "A business asks about a delayed or held freight shipment, container, vessel or inbound purchase order: where it is, why it is late, what it affects and how to recover. Not a personal package or parcel, and not assigning truck drivers to loads.",examples: ["what's happening with the delayed container from shenzhen", "show me the shipment exception on po 4471"],match: (text) => score, // intent score, runs on every wordparse: (text, ctx) => record, // entities + tool calls into your systemsreply: (record) => "…",Card: ShipmentExceptionCard, // the live UI, with its approval step});
The id, criterion, examples and reply are read live from the skill that renders the card above. Adding a workflow for your team means adding one of these: its intent, the calls it makes, what it says, and the interface your people approve in.
Fits your stack, answers to your people
Reads your systems. Acts only with approval.
What the agent connects to
Transportation management
Warehouse management
ERP and purchasing
Shipment visibility
ELD and telematics
Procurement and supplier quality
Product names are examples of systems in this category. Each deployment is connected to your systems through their APIs as part of the build.
Approval before anything moves
Booking freight, creating a transfer or PO, dispatching a load and sending a supplier request all wait for a person to approve. The agent prepares the action and stops.
Every step is logged
Each card shows the systems the agent read, what it found and how long it took. Approvals and rejections record who decided and when.
Least-privilege access in your environment
When deployed, the agent runs in your environment with scoped service accounts. It reads what each workflow needs and writes only the actions a person approves.
Synthetic data in this demo
Every company, driver, supplier, shipment and number on this page is invented.
The cost of doing it by hand
Put your own numbers in.
Move the sliders to match your operation. Nothing is sent anywhere unless you choose to email it.
Each year
960
staff hours back, about 0.5 full-time people
$50,880
of staff time, at your hourly cost
Email me a pilot plan for these numbersAssumes the agent takes over the data gathering and the first draft of the decision, not the decision itself. The $53 default starts from the BLS May 2025 median wage for logisticians ($39.58 an hour) and adds roughly a third for benefits and overhead. Change any number to match your team.
Hours = exceptions and planning decisions a month × 12 × minutes each × share, ÷ 60. A full-time person is 2,080 hours a year. Default hourly cost from U.S. Bureau of Labor Statistics, Occupational Outlook Handbook: Logisticians, 2025.
Questions buyers ask
Straight answers.
When deployed, the agent runs in your environment and reads your TMS, WMS and ERP through scoped service accounts. Your data stays there. This demo uses only synthetic data.
No. Bookings, transfers, purchase orders, load tenders and supplier requests all wait for a person to approve. Every approval and rejection is logged.
They are only as good as the carrier events, inventory records and forecast behind them. Each card shows its sources and a confidence read so a planner can check before acting. A pilot compares the agent's calls with what actually happened over past weeks.
No. It reads from and writes to the systems you already run. It removes the work of pulling data from several of them before each decision.
Pick one workflow, usually shipment exceptions or stockout risk, connect read-only access to the systems it needs, and run it next to your current process for a few weeks before turning on any write actions.
The demo on this page is free and needs no signup. For a pilot on your own data, book a call and we will scope it with you.
See it on your own workflow.
Watch the supply chain workflows run end to end, or speak to the agent yourself. Then tell us which one to build on your data.
Scope a pilot with hello@sasid.ai- 01
Pick one workflow
A short call to choose the workflow that costs you the most time, and who approves its actions.
- 02
See it on your data
We build that workflow against your sample or de-identified data so your team judges the real thing.
- 03
Run it with people in charge
Your staff use it on live work. The agent drafts and prepares; a person approves every consequential step.
- 04
Decide from results
You keep what measurably saves time and drop what does not.
Other operations
