Rate requests, structured before anyone prices them
Incoming quote requests can be read and turned into a structured brief: origin, destination, mode, weights and dimensions, Incoterms and ready date. Anything missing triggers a polite draft asking the customer for it. Your team still sets the price and approves every quote.
Illustrative example: an email asking for “a price for 4 pallets to Rotterdam next week” becomes a draft request with the pallet count and destination filled in, and a ready-to-send reply asking for weights, dimensions and the collection postcode.
Shipment updates that don't need chasing
Draft status updates generated from the milestones already in your system, so customers hear about departures, arrivals and delays before they ask. “Where's my shipment?” emails can be matched to the right job with a suggested reply. You decide which messages go out automatically and which need a person to approve them.
Customs paperwork checked for gaps
Documents received for a job can be checked against your own checklist: commercial invoice, packing list, EORI, commodity codes present, values and weights consistent across documents. Gaps get chased with the shipper. The automation doesn't choose commodity codes or submit declarations. Classification and the declaration in the Customs Declaration Service stay with your qualified people.
Illustrative example: a commercial invoice arrives showing a different gross weight from the packing list. The job is flagged to the customs team with both figures side by side, and a draft query to the shipper is ready to send.
Less re-keying between systems
We connect to the tools you already use where they offer an API or integration. CargoWise offers an integration module (eAdaptor) to licensed customers, Descartes runs an API portal with approved access, and Microsoft 365 or Google Workspace email can be connected. Tell us your stack and we'll say honestly what can be linked.