Logistics

Email, documents, bids, and shipment status in one operations layer

Dispatch lived in the inbox. Quote requests, carrier replies, rate confirmations, and “where is this load?” emails arrived all day. Status lived in the TMS if someone had updated it, and in a spreadsheet if they had not. Asking “what needs action before noon?” meant searching threads, not opening a board.

Discuss a similar workflow

What was breaking

The same shipment existed as an email, a spreadsheet row, and a TMS record — often out of sync.
BOLs and rate cons were attachments, not fields anyone could ask about.
Automation that sent quotes without review was a non-starter for the operators.
Handoffs stalled whenever the person who “knew the thread” was out.

What changed

The desk has one answer to “what is waiting on us?” instead of three tools and a search.
Documents and email are context for the shipment, not a parallel pile.
Automation is allowed to draft. It is not allowed to send.

AI workflow + inbox consolidation

What we built

Inbox intake that becomes a shipment

Connected mailboxes surface quote and status threads. AI extracts lane, equipment, dates, and missing fields onto a shipment record the whole desk can see.

An agent that explains the workspace

Operators can ask what arrived, which shipment it belongs to, what a document says, and what the next step is — from the dashboard, not by hopping tabs.

Human-in-the-loop before anything customer-facing

Outreach, quotes, and bookings are proposed, then approved. Suspicious senders hit a review queue instead of entering the live board. Booked loads hand off to the TMS when the team is ready.

Questions about this build

Can AI handle freight quote requests and status emails automatically?

It reads them and drafts the next step. Connected mailboxes surface quote and status threads, and the model extracts lane, equipment, dates, and missing fields onto a shipment record. Automation is allowed to draft; it is not allowed to send.

How do you stop an AI agent from sending a customer something wrong?

By never giving it the send button. Outreach, quotes, and bookings are proposed and then approved by an operator, and suspicious senders go to a review queue instead of onto the live board. Operators told us automated sending was a non-starter, so it was designed out rather than bolted down.

Do we have to replace our TMS?

No. The TMS stays where it is. This is an operations layer over email, documents, and the TMS, and booked loads hand off to it when the team is ready. Replacing a working system of record is rarely the cheapest way to fix an inbox problem.

Can it read BOLs and rate confirmations?

Yes. Documents become context attached to the shipment rather than a parallel pile of attachments, so operators can ask what a document says and which load it belongs to from the dashboard instead of searching threads.

More case studies

Construction

From blueprint PDFs to a tracked purchase order

Estimators were reading plans into spreadsheets, then emailing suppliers one by one. We built a desk where uploaded drawings become a reviewable material list, a quote, and a side-by-side RFQ — without another SaaS seat for each step.

Read the case study

Field service

Truck stock and warehouse as one inventory pool

Crews were requesting material by text. Warehouse counts were a week old. We built a requisition workflow across trucks, the warehouse, and contract budgets, and left the ERP in place as the system of record.

Read the case study

Have a workflow that looks like this?

Tell us the tools, spreadsheets, or legacy systems in the way. We will say whether it should become one custom app.

Start a conversation