Your transportation team lives in Microsoft Teams all day. So why does managing freight mean logging into another system?
Watch a planner for an hour and you’ll see the pattern. A question arrives in Teams: what will this order cost, has the carrier accepted, where is the truck? The planner switches to the TMS, looks it up, copies the answer and pastes it back into the chat. Multiply that by every order, every carrier and every person on the team, and a surprising share of the day goes to moving information between two windows.
We connected Zoree TMS directly into Teams. Here’s what that looks like in practice — one shipment, start to finish, without leaving the chat.
Type rate and the order number. Zoree runs the rate shopping and drops every carrier option into the conversation: cost, transit time and delivery dates, ranked, with LTL and Truckload side by side. Each option has a button to plan with that carrier.
One click, and the shipment is planned in Zoree. Dock door and loading window included — the same rules Zoree applies when a planner builds the load on screen — and the order flips to Planned.
Straight from the chat. When the carrier accepts, the acceptance flows through exactly as it would from the web: the shipment and its orders update, and the change is recorded.
Teams pulls the live shipment status directly from Zoree TMS. Ask for a shipment and you get its full detail plus buttons for the next step, like moving it to In Transit or Delivered.
You don’t need to memorize a command syntax. Filler words are ignored, so “plan order 1234 with this carrier” and “plan 1234” both work. A few things you can ask:
Teams works with Zoree in three ways, and teams can use any of them on their own:
Cards post to a Teams channel when a tender is sent, accepted or rejected, with a button to open the load in Zoree. The whole team sees carrier responses the moment they land, without anyone forwarding an email.
Rate, plan, tender and track from a chat or by mentioning Zoree in a channel, as shown above.
The full Zoree web app inside a Teams tab, for the work that needs the whole screen — bulk planning, rate management, reporting — without switching apps.
Moving work into chat only helps if it is held to the same standard as the TMS itself. Actions taken from Teams run through the same endpoints as the web app, so role permissions apply and every change lands in the same change history. Planning from Teams follows the same dock door and loading-window rules, and a tender accepted from Teams behaves exactly like one accepted on screen, including freezing the order dates once the tender is accepted.
The result is one record of what happened to every load, whether someone clicked a button in the TMS or typed a message in Teams.
Transportation runs on response time. A carrier that doesn’t get a tender in time takes another load. A customer who doesn’t get an ETA calls back. When the answer is one message away instead of one login away, the team answers faster and spends its time on the loads that need judgment.
Book a demo and we’ll walk through rating, planning, tendering and tracking a shipment from Teams.