Customers Do Not Call for an Update When They Can Already See One

No. Your TMS handles execution - planning, routing, carrier management, and settlement. Salesforce handles the commercial and service layer: quoting, customer relationships, exceptions, and self-service. Integrating them gives your sales and service teams live operational visibility without asking them to learn the TMS, and without asking the TMS to become a CRM.

With a parent shipment record and child leg records, each carrying its own carrier, mode, milestones, and documents. Status roll-up logic determines what the customer sees at the shipment level. This matters because a customer wants one answer about their freight, not four answers about four legs.

In our experience the bulk of inbound service contact in freight is status enquiry, document retrieval, and invoice queries - all of which a portal handles without human involvement. Portals do not deflect exceptions, and they should not: those are the conversations where your service team adds real value. The point is to free up capacity for them.

Yes. We integrate EDI feeds through middleware rather than trying to parse them inside Salesforce, which keeps the CRM clean and the mapping maintainable. Common transaction sets for booking, status, and invoicing are well-trodden ground; unusual partner-specific formats we scope individually.