Opser gives every desk an agent that reads the inbox, quotes the lane, creates and updates the shipment, works the exceptions, and reconciles at delivery, in Customers, Sales, Freight, Finance, Inbox, and Knowledge, on top of the TMS and carrier portals you already run.
A booking arrives by email. The rate request goes out by email. The carrier confirms by email. The details get typed into the carrier portal, then into the shipment file, then into the invoice. Documents live in threads. Delays show up when the customer asks where the container is.
Transport management systems are built for the biggest forwarders and priced that way. Opser starts from your lanes, your carriers, and your customers, and puts an agent on the inbox so the team works exceptions instead of re-keying.
Each one is a job your team does today by hand across several tools. On Opser one agent does it across the apps below and the systems you keep, and you approve.
A rate request means emailing three carriers, waiting, and assembling the quote in a spreadsheet.
The agent sends the rate requests, reads the replies, builds the comparison with surcharges and transit times, and drafts the customer quote for approval.
Get rates for 2 pallets Milan to Rotterdam next week and draft the quote for Lindqvist.
Booking details are re-typed from email into the system, then into the carrier portal, then into the invoice.
The agent creates or updates the shipment from the email, attaches the documents, prepares the carrier booking, and syncs it to your TMS.
Open a shipment from this booking, prep the carrier booking, and push it to the TMS.
Delays show up when a customer asks where their container is.
The agent reads carrier emails and tracking updates, flags late or stuck shipments into one exception queue, and drafts the customer notice with the new ETA.
Which shipments are running late this week, and who needs to know?
Commercial invoices, packing lists, and declarations sit in email threads and shared drives.
Every document is classified and attached to its shipment. The agent builds the customs file, checks what's missing, chases the shipper, and hands the file to your broker.
What's missing for customs on the Shenzhen shipment? Chase the shipper.
Invoices go out late and carrier bills are checked by hand, if at all.
When the shipment delivers, the agent drafts the invoice from the quote and the actual legs, matches the carrier invoices to the bookings, and flags the differences.
Invoice the delivered shipments and flag any carrier invoice that doesn't match the booking.
Each app owns a business domain and comes configured for this industry. Open any of them to see the screens inside. The last card is the workflow we haven't built yet, because it's yours.
Consols, container tracking, demurrage alerts, driver apps, proof of delivery, customs declarations in your broker's format. The apps your operation needs that no generic system has. Describe them and they're built into your system.
Build a demurrage watch: for every container, free days, discharge date, days left, and an alert to the customer at 3 days.
Because bookings, carriers, shipments, documents, and customers live in one system, an agent can turn an email into a shipment, a carrier reply into a rate line, and a delay into a customer notice, under your approval.
Every person gets their own agent; teams can share one. Sensitive actions wait for approval, and every action is logged with the data it used and the outcome.