Forty emails a day and one quote that arrived late.

What we see in forwarding

An enquiry arrives by email, written in plain language, often incomplete, sometimes in German. The forwarder reads it, retypes the data into a system, looks up a rate, asks about the missing date, writes a reply. By then the customer has an offer from somebody else.

Beside that sits a second, less visible loss: knowledge about procedures, exceptions and agreements lives in a few people's heads. When they are away, everyone else guesses or waits.

What we do about it

Classification and extraction

The system tells a quote request apart from rate correspondence and from noise. From a request it pulls route, cargo, ADR class, dates and sender - and flags immediately what is missing before a price can be quoted.

A draft reply in the sender's language

The reply is prepared, not sent. The forwarder reads it, edits, approves. That distinction is the entire architecture of these systems, not a configuration option.

A knowledge base that cites its source

"Which documents for ADR class 8?" - the answer points at the procedure and the page. With no cover in your documents the system says it does not know, rather than guessing at transport paperwork.

Why this is not another TMS

We do not replace the transport management system and do not want to. We work on the layer that in most forwarders is not software at all - the mailbox, and the knowledge sitting in files.