The loads arrive as email. So start there.
For a carrier subcontracting to forwarders, the working day arrives as forty emails in six languages with a PDF attached to a third of them. Someone opens each one, decides whether it is a load, and retypes it. That is a job, and it is not a job anybody should have.
What happens to an email.
It arrives
Your company mailboxes sync into one shared pool, so the load that landed in a colleague's inbox is not invisible to the rest of the office.
It is classified
Each email is read and sorted: an order request, or noise. Rules and spam rules handle the senders you already know about, so the pool stays a working list rather than a second inbox.
It is read
The order details are extracted from the body or the attached PDF, including scans and photographs of paper orders with no text layer. Brokers write in Polish, Romanian, French, German, Italian and English, and the extraction reads all of them.
A dispatcher takes it
One click turns the request into a prefilled new order on the board: customer, reference, stops, addresses, dates and price. The dispatcher corrects what is wrong instead of typing what is right.
Forty emails in, three orders out.
Most of what arrives is not a load. The value is not in reading the three that are, it is in never having to open the thirty-seven that are not.
A shared pool, not four private inboxes.
Order email is a team problem disguised as a personal one. When each dispatcher works their own inbox, the same load gets quoted twice, or missed, and there is no record of which of the two happened. The pool is shared, an email is taken by one person, and the rest of the office can see that it was.
- Several company mailboxes syncing into one pool
- Taken emails visibly claimed, so two dispatchers do not work the same load
- Replies sent from the thread, without leaving the board
- Rules and spam rules per sender, so the pool gets quieter over time
Nothing is created behind your back. Extraction produces a draft that a dispatcher reviews and confirms. A model reading a scanned Polish order at 06:40 is a very good typist and a bad person to give commit rights to.
Questions people actually ask.
- Which mailboxes can we connect?
- Google mailboxes, through Google's own OAuth consent. You grant access, you can revoke it from your Google account at any time, and we never see a password.
- Does it read PDFs, or only the email body?
- Both, including scanned or photographed orders with no text layer, which are read the way you would read a photo of a document.
- What languages do the order requests have to be in?
- Polish, Romanian, French, German, Italian and English are all handled, including mixed-language documents, which is what most forwarder templates actually are.
- Does it create orders automatically?
- No. It prepares the order and a dispatcher confirms it. The extraction returns nothing rather than guessing when a field is missing.
- What happens to email that is not a load?
- It stays classified as noise and out of the working list. Spam rules per sender make that permanent.
Read next
Stop retyping your own inbox.
Bring a real forwarder order to the call, PDF and all, and we will run it through in front of you.