Microsoft Teams

Microsoft Teams is where most Microsoft 365 shippers run their dispatch day: one channel per site, one per customer, a chat with every planner. Connected to Cargofy, those channels receive load events, exceptions get decided there, and a digital worker answers status questions. The head of dispatch usually switches it on, with IT registering the app in Entra ID.

What teams use it for

Decide on detention before it costs a day

A detention alert by email or phone often reaches the dispatcher an hour into the clock. With Teams connected, the exception fires in Tracking and lands in the dispatch channel as an Adaptive Card: load number, carrier, dock time and three buttons. The dispatcher taps confirm, assign carrier or escalate. The click goes back to Cargofy and the decision is written to the load, so the record and the channel agree.

Answer a status question from the chat

A customer service rep is asked where a shipment is and types the load number to the Cargofy bot in Teams. The digital worker reads Tracking and replies in the thread with the current status and ETA, and the rep forwards the answer. The question and answer stay visible for the next person on shift.

See quote requests in the pricing channel

A customer's rate request lands in Sales. Cargofy posts it to the pricing channel you chose as a card with lane, equipment and dates. One analyst replies in the thread that she has it and prices the request in Sales. The thread shows who took it and when, and the channel holds every open request in one place.

Post the signed POD where the team is looking

When a delivery closes and the driver's signed POD is in Documents, Cargofy posts the file to that customer's channel with the load number. Customer service tells the customer the load delivered. The AP clerk reading the same channel knows the load is ready to invoice and starts the bill in Finance. The file stays on the load in Documents; the post is the signal.

Follow a customer's loads without a status meeting

Each status change on a customer's load in Tracking (picked up, in transit, delivered) posts to that customer's channel with the load number and new status. The account manager reads the channel and stops asking dispatch twice a day. When a change needs a decision, such as a late pickup, the same channel holds the Adaptive Card with the buttons, and the dispatcher acts on it there.

How it fits your stack

Your Microsoft 365 tenant stays yours: Cargofy does not create teams or channels or manage members. It writes messages, cards and files into the channels you map, and reads clicks and chat messages back over Graph change notifications, without polling. Setup is per installation. There is no shared Cargofy app, so your admin registers one in Entra ID and grants admin consent in your tenant. The integration runs on Graph API; classic Office 365 and Incoming Webhook connectors are not supported.

Who it is for

Shippers on Microsoft 365 with a dispatch or customer service team that works in Teams. Dispatchers act on cards, customer service asks the bot, and the IT admin owns the app registration. Freight forwarders and 3PLs running ops channels use it the same way.