Quote requests
A constant stream of requests by email and web form, each priced by hand against rate tables and a carrier network while the client waits.
AI for freight forwarders: quotes, documents and customs
AI for a freight forwarder is not a chatbot on the inbox. It is the quote request priced against your contracted rates, the freight documents read once and written into your TMS, the customs data checked against the invoice and packing list before filing, and the carrier invoice checked against the agreed rate before payment. Anything outside the standard pattern goes to an operator before it goes out. In production at OFRET Groupe, where more than 90% of standard quote requests are answered automatically.
Where a forwarding desk loses its day
None of it is hard. It is the volume, the formats, and the fact that every request and every document is read and keyed by hand.
Freight documents
Bills of lading, CMRs, airway bills and packing lists from every carrier, in every format, re-keyed into the TMS for each shipment.
Customs files
Commercial invoices, packing lists and certificates of origin that have to agree with each other before a declaration is filed, not after a hold.
Carrier invoices
Detention, demurrage and accessorial charges that go through unless every invoice is checked against the contracted rate and the shipment record.
What Mirage runs for forwarders and customs brokers
One platform, several workflows. OFRET Groupe started with document automation, then quoting, then a verification and exception layer, each built on the one before.
Quote requests
Requests read from email and forms; lane, volume and equipment checked against your contracted rates and lane history; the quote drafted for a standard request.
Freight documents into the TMS
Bills of lading and the other shipment documents read in any format and written into the TMS through its own interface, with no re-keying.
Customs declarations
Commercial invoice, packing list and certificate of origin read together and cross-checked, so your team or your broker files from a verified data set.
Carrier invoices and delivery proofs
Every carrier invoice checked against the contracted rate and the shipment before payment; proofs of delivery matched to the shipment and the invoice.
In production at OFRET Groupe
OFRET Groupe is a freight forwarding group: two entities, one TMS, and a Quoting Agent built for each.
90%+
Of standard quote requests answered automatically
2
Quoting environments, one per entity, in the same TMS
- Before
- OFRET for full truckload, SWILL for groupage: one TMS, two pricing logics, two carrier networks, and every quote request priced by hand.
- Deployment
- A Quoting Agent in two separate environments, one per entity, built inside the group's Logitude World TMS through its API. Document automation first, then RFQ automation, then a verification and exception layer.
- Now
- Neither team re-keys documents or prices standard RFQs by hand any more. Anything outside the standard pattern goes to an operator before it goes out.
What stays with your team
Mirage reads, checks and drafts. Your operators decide what goes out, and every exception reaches them with the document it came from.
- Quote
- Drafted against your rates for a standard request. A request that does not match your usual shipment profile goes to an operator before anything is sent.
- TMS entry
- Written when the document agrees with the shipment. A field read without confidence is flagged on its own, with what was found, and an operator corrects that field.
- Customs
- The declaration data is cross-checked before filing, and a missing HS code is flagged, not inferred. Filing itself stays with whoever files today.
- Carrier invoice
- A charge that does not match the contracted rate is flagged before payment. Disputing it or paying it is your call.
From the first meeting to production
Mirage's engineers work on site with your team, on your own documents and systems. Every request gets an answer within two business hours, and the pilot is fixed-price: you can stop after it.
How a deployment runs
- Observe
- Map
- Build
- Run
- Expand
A proof of concept on your own documents one week after the first meeting, then the first workflow in production in 4 to 6 weeks.
See how we deploySecurity and governance
- Deploy anywhere
- Control every action
- Prove what happened
Access permissions, validation workflows and audit logs remain fully controlled by your organization. Signed NDA on request.
See security and data handlingQuestions from freight forwarders and customs brokers
It reads incoming quote requests and drafts the quote for standard ones against your contracted rates, reads freight documents and writes them into your TMS, cross-checks the documents a customs declaration is built from, and checks carrier invoices before payment. Anything outside the standard pattern goes to an operator, with the original attached.
The customs workflow reads the commercial invoice, the packing list and the certificate of origin, cross-checks them and hands your team a verified data set to file from; it does not file the declaration. Mirage has not published a deployment at a customs brokerage. Its published logistics deployments are at OFRET Groupe, a freight forwarder, and at Transwin, whose teams read freight and customs documents by hand before Mirage.
No. At OFRET Groupe, Mirage connected to the Logitude World API and built the automation inside the system both entities already used: no new software layer for either team. Where a TMS has no documented interface, Mirage's engineers build the connector during deployment.
Mirage publishes its results per client: more than 90% of standard quote requests answered automatically at OFRET Groupe, 70% less manual data entry on freight documents at Transwin. It publishes no accuracy percentage: the share of documents that need a human check is measured on your own documents during the proof of concept.
A fixed-price pilot on one workflow, which you can stop after, then an annual subscription priced by volume, not per user: from $10,000 to launch, then from $1,000 a month. The exact amount is set once we have seen your documents.
A proof of concept on your own documents one week after the first meeting, then the first workflow in production in 4 to 6 weeks. The pilot is fixed-price and you can stop after it.
Bring us the operation you need to improve.
Mirage will map the workflow, identify what can be automated and define the fastest path to production.
Start with a written plan
Tell us where your team loses time. We send back which workflows are worth automating, what a deployment involves on your systems and the shortest path to production. No commitment.