Demonstrated operation
AutonomeX · InboxOS · Logistics
AutonomeX is the company. InboxOS is the platform. Logistics and freight forwarding is the operation InboxOS is demonstrated on today.
Bookings and amendments, quote chases, status questions, documents, schedule changes, holds, invoice disputes and claims arrive as mail. InboxOS reconstructs what each message is about, checks it against the fields the request actually needs, and raises it as owned work with priority and risk attached. You choose which low-risk workflows auto-queue; uncertain and high-impact work stays with people.
Bookings. Documents. Holds. Exceptions. Claims. InboxOS turns fragmented freight communication into owned, prioritised work.
What changes
Want the platform view first? Read how InboxOS works.
Fast enough for an operations desk. Clear enough for review.
The governed execution environment · logistics
A customs hold rarely arrives as one message. Watch the rejected entry, the missing commercial invoice and the chase cross the boundary as one shipment situation, move through the stages InboxOS records, and stop where your team decides.
Drag to explore
What the animation shows: unresolved shipment signals, such as a customs hold, a rejected entry, a missing commercial invoice and an urgent chase, sit outside a governed boundary. They converge on a single entry point and cross it as one shipment situation, blocked on the missing entry detail and waiting on the sender. That situation moves through the decision stages InboxOS records and stops at human review required. InboxOS has no shipped connector into a TMS, ERP, WMS or CRM, and the scene says so.
The forwarding desk
A forwarding or logistics operations desk works through requests that arrive as mail: shipment commitments, pricing, tracking questions, documents, exceptions, money and claims. The mix differs by operation, lane and customer base. What repeats is the shape of the problem.
A customs or carrier hold, a last free day approaching, a draft bill of lading waiting for approval: each arrives beside promotions, duplicates and routine status questions. The inbox gives them all the same visual weight, and cost is invisible until someone opens the message.
Booking reference in one thread, the revised sailing in another, the document in an attachment nobody filed.
Judgment that belongs on cargo, carriers and customers goes into triage and re-keying instead.
What actually arrives
The InboxOS logistics pack in our repository carries seven request families across seventeen request types. They are example categories of forwarding mail, drawn from how this work is usually organised. No operation is assumed to run all seven: your pack is reviewed with you, and families you do not handle stay out of it.
These seven are what the logistics pack covers today, not a description of your desk. If a family above is not your work, it stays out of your pack. If your operation carries a family that is not listed, say so in a conversation and we will tell you honestly whether it is configurable now or later.
Where the judgment lives
InboxOS is one shared core. The industry pack holds how the work is judged, and for logistics that judgment is written down per request type rather than improvised per message. That is the difference between a tool that drafts and a tool that can be reviewed.
Priority and risk are separate values on purpose. An invoice dispute is configured as medium priority and high risk; a carrier arrival notice is high priority and low risk. Collapsing the two is how automation starts sending things it should not.
The product
This is the current offline demo, running on fictional logistics records. The operator decision shown is a draft bill of lading approval: the evidence, the next action, and send held because this demo does not deliver mail. Human review still gates what would leave. There is no customer deployment behind this screen and no named customer anywhere on this page.
The current offline demo, on fictional logistics records: an operator decision for a draft bill of lading approval, with send held. No customer deployment behind this screen.
Want to click it rather than read about it? Request demo access. It runs on the same fictional records, so nothing about it is a customer reference.
Fit with your stack
Your TMS, ERP, WMS and CRM are where the shipment, the money and the customer record live. InboxOS is not a replacement for any of them. It sits between the conversation and those systems, and it is designed to complement them: the mail becomes structured, prioritised work that your people and your systems of record can act on.
The AutonomeX execution model · six governed stages
Mail comes in from customers, carriers, agents, brokers and truckers; prepared, reviewable work goes out, and your TMS, ERP, WMS and CRM stay the system of record. Between the two sits one execution model.
No rip and replace, and no connector claim on this page. Today InboxOS reads the operational mail, reconstructs the request and prepares reviewed work; committing that work into your systems of record stays with your team. Writing directly into those systems is product direction, not something we present as shipped. The honest boundary is set out in the security overview.
Built now. Built next.
Logistics is the operation InboxOS is demonstrated on today. That is a real, checkable status and it is not the same thing as a live customer deployment. We keep the difference on the page.
Human control
Those two sentences only hold together if the boundary is yours to set. You determine which logistics workflows are eligible for automation at all. Autonomy is bounded by workflow, by request risk and by your policy, and sensitive actions can remain subject to human approval however confident the system is.
Who decides what
Configurable autonomy
The Autonomous Queue is optional and can be switched off where regional policy or your own preference requires every item to stay in human review. Classification, extraction, drafting and human approval before send remain available either way.
Need something to share with security or leadership? Open the public security overview Request the detailed pack
Built for freight
Container yards, uplift windows and the long haul on asphalt. InboxOS is built for the inbound mail that moves work across these modes.
Scroll · the lanes open
Start a conversation
A thirty minute conversation. No cutover, and no mailbox access to arrange first. Bring one request family your desk still handles by hand, from bookings to holds to claims, and we will walk through how InboxOS would treat it, where the fields would come from, what would stay in human review and what we cannot do yet.
Prefer to read first? The platform view is on the InboxOS page, and the control detail is in the security overview.
