The tracking inbox that answers itself.
An AI agent monitors your shared Gmail inbox, reads every broker and customer status request, and replies in minutes with the live answer out of Amous — pickup in and out times, current ETA, delivery appointment. Anything it can't verify goes to your Track & Trace team, not to the customer.
Your Track & Trace team spends the day answering the same email.
Brokers and customers, all day long — did it pick up, where is it now, what's the ETA, is the delivery appointment holding. Different senders, same four questions.
Every reply is the same loop: open the email, find the load in Amous, check the driver, check the position, type it up. Two windows, five minutes, hundreds of times a week.
The answers live in your TMS the whole time — the bottleneck is a person retyping them. And the emails keep landing after the team goes home.
Three emails. Three right answers.
The same agent on three real situations: an on-time load it answers by itself, a late load it clears with your dispatcher before replying, and an uncovered load it hands straight to your team. The card on the right fills in as the agent works — the same fields the pilot pulls off the load in Amous.
Shared Track & Trace inbox · loads and times illustrative
Morning — need a status on 45912, picked up Elk Grove yesterday, delivering Dallas tomorrow.
Can you confirm it loaded and give me a current ETA?
Hi Dana — 45912 picked up in Elk Grove Village yesterday: arrived 14:05, loaded and out at 15:12.
The truck is currently on I-44 near Lebanon, MO, running on schedule. Current ETA into Dallas is 08:10 tomorrow, ahead of the 09:00 delivery appointment.
We'll flag it to you right away if anything changes.
One decision tree. Your rules at every branch.
This is the entire scope — one shared inbox, one workflow. The branches your team decides today stay with your team; the retyping in the middle goes away.
The agent reads the shared inbox the moment mail arrives. Only shipment-status requests get picked up — everything else sits untouched for your team.
Is it a tracking request? The thread is tagged “track” so your team can see at a glance which emails the agent owns.
Matched by load number, PO, or reference — pulling status, pickup arrival and departure, live ETA, and the delivery appointment straight off the load.
Checks the driver and unit on the load before it says anything.
Live position against the appointment.
Every classification, lookup, reply, and escalation is on the record — you can audit any answer it ever gave.
Built to your scope. Not an inch past it.
You told us exactly where the line is — documents stay with people, and this is one workflow, not a platform takeover. That's how it's built.
PODs and BOLs are never auto-attached. A document request routes to your ops team for review — the agent answers status questions; people send paperwork.
This is not an enterprise AI rollout. It reads one shared inbox and answers one kind of email. It doesn't touch dispatch, billing, or anything else in your TMS.
If the load, the driver, or the ETA can't be verified in Amous, no reply goes out — your Track & Trace team gets the request with the lookup already done.
Every email it reads, every reply it sends, every alert it raises — logged and auditable, so you can see exactly what it said and why, on every load.
Free pilot, on your real inbox, live this week.
No integration project and nothing for your team to learn. We connect the shared inbox and Amous, the agent starts answering a slice of real traffic, and your team watches every reply until you're comfortable letting go. If it isn't saving hours by week two, unplug it.
One call to answer three setup questions · pilot can be answering by Friday
Or just reply to Shafay's email — setup starts with a single inbox connection.