The freight agent that answers on your tracking page
Where is my load, can I move my slot, what does this lane cost, what does this accessorial mean: they are lookups against the systems your track-and-trace and quote pages already call, and Algomo answers them there, in the shipper's own portal session, at 23:00 as at 09:00. What needs a person goes to your team with the whole thread.
Answer the quote request, and never let a load go dark
The load you lose is the one nobody got to: the quote request that sat in an inbox until somebody else answered it, the shipper who gave up on the tracking page at 23:00 and went elsewhere in the morning. Algomo sits on your quote page and your track-and-trace page. A shipper types a lane and it prices it off your own contract rates, through the lookup your quoting screen uses; a lane with no contract rate becomes a quote request, assembled and handed to your team with the whole thread. It reads status and ETA from the endpoints your tracking page already calls, so what it tells a shipper at 23:00 is what your TMS shows at 09:00.
- Lanes quoted on your quote page, off your contract rates
- Where-is-my-load answered off the lookup your tracking page uses
- Live ETA off the tracking record, not off a guess
- Off-contract lanes handed to your team as a quote request, with the thread
Every party's record in one thread, while the queue is still moving
A dock supervisor with a truck and no paperwork has three systems to check and no hands free. Algomo, on the portal she is already signed into, reads the load record, the appointment book and the tracking position together and tells her what each one shows. If the portal lets her move a bay, it moves the bay, in the appointment book her own screen reads. The parts that need a person, the carrier's office, the shipper's account manager, go to your team as one case with the whole thread attached, not as three messages to catch up on.
- Load record, appointment book and tracking read together
- Bays moved where the portal lets the dock move them
- One thread, picked up where it left off after the shift change
- Handed to your team the moment it needs a judgement call
Every document on the record, read back the moment somebody asks
Freight runs on documents somebody says they sent: the rate confirmation that is on the portal somewhere, the claim whose photographs went in three weeks ago, the offer nobody can find in the thread. Algomo reads the load record and the claim record a carrier or shipper is already signed into and says what is there, when it went in and what is still missing, then puts the document in the chat. A returning visitor picks up the same thread rather than starting cold, and a handover carries the thread itself rather than a note about it.
- Rate confirmations found on the load record and put in the chat
- Claim documents the shipper uploaded, read back with their dates
- The offer on file and the figure claimed, side by side
- Handover carries the whole thread, not a summary
The load record that answers the chargeback, laid out in the chat
Detention, OTIF penalties and freight claims are all arguments about what happened and when. The answer is usually already on the load record: gate times, wait time, the POD and the photograph the driver took. Algomo reads that record in the shipper's session and lays it out in the chat, minute by minute, then starts the claim from the documents the shipper uploaded on the portal, reads them back, and hands the assembled case to your team. When the decision belongs to a person, because a bill is disputed or a shipper is worth more than the invoice, they get the case, not a ticket number.
- Gate times and wait times read off the load record
- POD and photographs put in the chat, with their timestamps
- Claims started in the chat from the documents already uploaded
- Handover to a person with the case, not a ticket
What it closes, and what it hands to a person
Freight is not a regulated conversation, so the line here is not a legal one. It is commercial. The agent answers what the portal can show and moves what the portal lets the customer move, and the moment a decision costs money or costs a relationship it stops and hands over the whole thread.
Where is my load
The question that fills a dispatch desk, answered off the same tracking lookup your own portal reads, at three in the morning if that is when it gets asked.
What does this lane cost
Contract lanes priced off your own rate table, through the lookup your quoting screen uses. A lane with no contract rate becomes a quote request for your team, with the thread, rather than a number somebody half remembered.
Move my appointment
Dock slots checked and moved against the live appointment book, where your portal already lets the customer move them. Where it does not, the request goes to your team assembled, not left sitting in somebody's inbox.
Where is my paperwork
Rate confirmations, PODs and claim documents found on the load record and put in the chat, with the date each one went in and what is still missing.
Take the lower offer
It does not decide that. An out-of-policy settlement, a disputed bill or a lane below your floor goes to whoever owns the account, with the thread.
What does this accessorial mean
Detention, redelivery, liftgate, the line on the invoice nobody can decode: explained from your own published tariff and the load it was charged against, not from a general definition.
What brokers and 3PLs get out of it
The same agent takes the quote requests that decide whether you book the load and the exceptions that decide whether you keep the customer.
More loads quoted
A lane priced while the shipper is still on your quote page is a load still open to you. Answering first is most of winning it.
Fewer OTIF penalties
A shipper who can see the exception and move the slot at 23:00, on your portal, is the difference between a rebooked slot and a retailer chargeback.
Claims that start complete
A claim started in the chat carries the POD, the photographs and the dock log the shipper already uploaded, so your team opens a file rather than a question.
Dispatchers on the loads that need one
Where-is-my-load, slot moves and paperwork questions stop reaching a person at all, so the ones that do are the ones worth a person.
Three differences, one loop
It connects itself
Algomo discovers the endpoints your own tracking and quote pages call. That is why an ETA it quotes is the ETA your TMS shows, rather than a line somebody typed into a note.
So its actions are real
Because it holds those endpoints, moving a dock slot means the slot moves, in your appointment book, on the screen the dock supervisor is looking at, in the customer's own session.
And you run it by talking to it
New lane, new accessorial, a customer who must never be quoted spot: say it in plain language and the next conversation follows it.
Never settle a claim under 90% without asking us.
Done. Anything below 90% now goes to the account manager with the thread.
Discovery gives it live data. Live data makes real actions safe. Plain-language control keeps the commercial decisions yours.
Questions, answered
What it is
**What is a logistics AI agent?**
Web chat on your track-and-trace and quote pages that runs the question half of freight: where is my load, what does this lane cost, can I move my slot, what does this accessorial mean, where is my POD. Algomo answers off your live systems, in the shipper's own signed-in session, rather than describing what they contain, and hands what needs a person to your team with the thread.
**How is this different from a visibility platform?**
A visibility platform tells you a load is late. It is a very good alarm and it does nothing about the alarm. Algomo is what the shipper meets when they come to your tracking page about it: it says what the record shows, moves the slot if the portal lets them, and hands the rest to your team with the case assembled. One shows you the problem, the other answers for it.
**Does it replace our dispatchers?**
No. It takes the repetition off them: where-is-my-load, slot moves, rate lookups, paperwork questions. What reaches a dispatcher after that is load coverage and customer relationships, which is the part the job was supposed to be.
Working a case
**Does it contact the carrier or the dock for us?**
No. It does not message anyone off your site. What it does is read what each system already shows, the tracking position, the appointment book, the load record, and tell the person in front of it in one thread, so a three-system exception is one answer rather than three waits. The parts that need a human, the carrier's office, a shipper's account manager, go to your team as one case with the whole thread.
**How long does it hold a case open?**
The thread is kept. A shipper who comes back to the portal a week later picks up where they left off rather than starting cold, and the handover to your team carries the whole conversation in order. It does not chase anyone off the site: when a party goes quiet, that is your team's move, made with the thread in front of them.
**When does a person get involved?**
When judgement or money is at stake: a disputed freight bill, a settlement below your policy, a lane rate under your floor, or a shipper relationship worth more than the invoice. The handover carries the whole thread, in order, so nobody re-reads a month of it to catch up.
**What record is there of a conversation?**
The whole conversation is kept and goes with the handover: what the agent read off the load record, what the shipper uploaded, what was moved and when. Your team receives it by email and Slack with the thread attached, whether the case is a detention dispute, a chargeback or a shift handover.
The work itself
**Can it book and move dock appointments?**
It can move them where your portal already lets a signed-in customer move them, against your real appointment book, and each of those is a separate permission. A site that wants the agent to show slots but never move them can have exactly that. Where the portal does not allow the move, the request goes to your team assembled.
**How does it price a lane?**
Off your own rate tables and contract lanes, through the same lookup your quoting screen uses. Where a lane has no contract rate, it can offer a bracket you have set and hand anything outside it to your team as a quote request rather than inventing a number.
Your systems and setup
**Does it work with our TMS?**
It works against whatever your website and customer portal already talk to. If a page a shipper can open shows a load status, the agent can read it in their session. It does not write into the TMS. Systems reachable only from inside your network we connect with you.
**What languages does it work in?**
Whatever language the driver, dock or shipper types in, and it stays in it for the whole thread. On a cross-border lane that is often three languages against one load, which is exactly where a shared inbox falls over.
**How long does setup take?**
Minutes for the public side, because Algomo finds the endpoints your own pages call and builds its own tools to use them. You can try it against your live tracking before a shipper ever does. Anything a signed-in customer can already see on your site, the agent reads in their own session. Anything only your staff can reach, we connect with you. You build and change it from Claude Code, Codex or any other tool that speaks MCP, the open protocol AI tools use to talk to each other, or from the dashboard.
**What does it cost?**
You pick a monthly amount and it buys credits: a conversation that actually helped someone costs five, one that went nowhere costs nothing, and the amount is the most any one charge can be, so a peak week or a bad weather event never raises the bill on its own. There is no overage: run out early and you renew early, or wait for the month to turn. Every number is on [this site's pricing page](/pricing).
Explore more from Algomo
Why Algomo
Why we built an agent that does its own integration work.
[Why Algomo](/resources/why-algomo)
Comparisons
See how Algomo compares to Sierra, Intercom Fin, Decagon and Gorgias.
[Comparisons](/resources/comparisons)
Product
How it connects itself, works your pages with the visitor, and takes instructions in plain language.
[Product overview](/product)