Orders arrive in Outlook with a PDF, from the Trans.eu exchange and from Transporeon, and the dispatcher retypes them into CargoWise by hand. The agent extracts the route, cargo, windows and price, creates a draft order in CargoWise or FireTMS, and the dispatcher approves with one click.
Built for ISO 27001NIS2 DORA
A carrier's or forwarder's order rarely gets into the system by itself. A customer sends an email to Outlook with a PDF order, a forwarder sends a notification in Trans.eu, a large shipper posts a task on the Transporeon platform: loading and unloading addresses, time windows, pallets and weight, the agreed price. The dispatcher opens each source, retypes the data into CargoWise or FireTMS, checks whether the customer is already in the partner list, and only then looks for a free lorry. When there are dozens of such orders a day, some wait until evening, and rushing produces errors in addresses and dates that both the driver and accounting fix later.
The agent connects to the shared orders mailbox in Outlook and to agreed channels, Trans.eu notifications and Transporeon tasks that arrive by email or export, and reads each one: it extracts the route, windows, cargo parameters, price, payment terms and company details, matches the customer against the CargoWise partner list by company registration number, and creates an order card in CargoWise with the status "awaiting approval". In the CargoWise window the dispatcher sees the prepared card with the original email next to it and approves with one click or corrects a field. If a date is missing or an address is ambiguous, the agent does not create a card but hands the email to the dispatcher with specific questions for the customer. We deploy the Claude agent through the Anthropic API or Amazon Bedrock in an EU region; we integrate with CargoWise or FireTMS through an API, a file import or an email flow, depending on your version, and we get mailbox access through your Microsoft 365 tenant. Your emails are not used for model training, and every agent action is written to a log.
Four steps from input to a record in your system, with human approval wherever there is risk.
The agent monitors the shared orders mailbox in Outlook and the agreed channels: Trans.eu notifications about accepted offers and Transporeon tasks. It reads every email, PDF or Excel attachment and separates orders from questions, confirmations and advertising.
From the text and attachments the agent extracts loading and unloading locations, time windows, cargo type, weight and pallets, price and payment terms. It matches the customer against the CargoWise or FireTMS partner list by name and company registration number so that it does not create duplicates.
The agent creates an order card in CargoWise or FireTMS with the status "awaiting approval" and a link to the original email. The dispatcher reviews the fields, corrects them if needed and approves. Only then does the order become active and can it be assigned to a lorry.
If a date is missing, an address is ambiguous or the price is not stated, the agent does not create a card in CargoWise but hands the email to the dispatcher with specific questions for the customer. We monitor the agent log and the correction rate in CargoWise, and review the rules with you every month.
The agent is connected to CargoWise or FireTMS through an API, a file import or an email flow, depending on the version, and to the orders mailbox in Outlook in your Microsoft 365 tenant.
The prepared order card in CargoWise is shown with the status "awaiting approval" and the original email next to it, and the fields the agent is unsure about are marked separately.
Every email read from Outlook or Trans.eu, every card created in CargoWise and every correction is recorded with the time and user, so you see what the agent did and what a person changed.
Training dispatchers to work with the agent's cards in CargoWise, monitoring during the first month and adjusting the rules to real emails and Trans.eu orders are included in the implementation.
Claude agent via API + CargoWise or FireTMS integration + Outlook and Trans.eu flows. We choose the integration method after checking your version. Read more about this service and its limits on the service page.
No. The agent creates only a card with the status "awaiting approval", which the dispatcher approves or corrects in the CargoWise window. An active order appears only after approval, so a misread email cannot become a trip without human eyes on it.
Yes. We connect to FireTMS through its API and to CargoWise through an API, a file import or an email flow, depending on the version and the modules you have. We choose the integration method after a check at the start of the implementation, and the agent receives Trans.eu and Transporeon orders from email notifications or an export.
The model runs through the Anthropic API or Amazon Bedrock in an EU region, and your emails are not used for model training. We limit access to Outlook and CargoWise to the permissions that are needed, and you keep the action log yourself.
Drivers send photos of CMR and declarations through Viber or Teams, and logistics checks them by eye and attaches them to the trip in CargoWise by…
Drivers call the dispatcher with the same questions: how to fill in a CMR, what to do after an accident, when loading is.
A request from Outlook, Trans.eu or TimoCom waits while the sales rep calculates the distance, finds a similar trip in CargoWise and writes up the…
DKV and Eurowag statements and toll, ferry and subcontractor invoices arrive from Outlook and portals, and an accountant keys them into SAP…
This service is delivered by specialists with valid international certifications. Their expertise is confirmed by independent organisations, not by us.
AI systems are deployed with protection against data leakage and model abuse.
The AI security programme and its controls are managed following the ISACA methodology.
AI risks are identified and managed like any other IT risk.
We reply within 1 business day
