The assistant you already use a connector into Claude, ChatGPT and the rest
Your team asks about shipments in the same window where they do the rest of their work. Nobody learns a new tool, and nobody leaves the thread they are in.
What is going on with this shipment?
It is 14 hours behind the plan. Held at the Columbus hub since 02:10. The other shipments that left with it are two scans ahead.
Any weather events that will disrupt my shipments enroute?
Two, with 46 shipments in the path. A winter storm on the I-80 corridor and a heat advisory over Phoenix.
How much revenue is enroute right now?
$4.1M, and $210K of it is at risk. The risk sits in 38 shipments that are behind the plan or in a weather path.
Ask a question in plain language and get the answer, with the shipments, the numbers and the map behind it. Analyst works inside the assistant your team already uses, and inside Shipping Hub.
Today an answer costs somebody an afternoon. A person opens the carrier portal, then the TMS, then a spreadsheet, and assembles the answer by hand. The question was simple. The work was not.
With Analyst the same person types the question and reads the answer. Customer service answers the call while the customer is still on it. Operations sees the pattern across a carrier instead of one shipment at a time.
This is not a report that you request and wait for. It is a person on your team who has read every shipment, every scan and every delivery photograph. It is available the moment you need it.
These are real questions, in the words that people typed. One shipment or the whole network, the answer comes back the same way.
What is going on with this shipment?
The history in plain language, the exception named, and the plan that the shipment missed.
A customer says the shipment arrived damaged. How many shipments to them showed damage?
Every shipment to that account with damage on the delivery photograph, and the date of each one.
How many shipments had exceptions on this carrier in the last three months?
The count, the exception types, and how that carrier performs against the others on the same lanes.
Are there major weather events that will disrupt my shipments enroute?
The events, the number of shipments in the path of each one, and the map that shows which lanes cross them.
Are there any major weather events that will disrupt my shipments enroute?
Your TMS knows where the shipments are. It does not know what the weather will do to them. Analyst holds both.
The model gets whatever your systems hold, in the words that each carrier chose. It can count the rows. It cannot tell you that a shipment is behind, because nothing in that data says what the plan was.
Each tool is ours, and each one runs on data that we normalize first. Guardrails keep the answers inside what your account is allowed to see. That is the difference between a model that queries and one that answers.
Your team asks about shipments in the same window where they do the rest of their work. Nobody learns a new tool, and nobody leaves the thread they are in.
For the people who live in Shipping Hub all day, the same analyst sits beside the shipment list. Ask about what is on the screen and act on the answer without moving.
Ask your TMS and it knows where every shipment is, but not what any of it is worth. Ask your ERP and it knows the value, but not where the goods are. The carrier knows neither. So the money in motion, which is often the largest number in the business, is the one number that nobody reports.
Analyst joins the two. It holds the value on the shipment, and it knows that the shipment is three scans behind the plan. So it can tell you what is enroute, what is late, and what the lateness is worth today.
Ask that question in your next operations meeting. Watch the room.
The one your team asks every week and nobody can settle without an afternoon of work. We will connect Analyst to your own shipments and you can put the question to it yourself.
You ask the questions. We do not script the demo.