Microsoft Outlook

Microsoft Outlook is the ops inbox for most shippers on Microsoft 365, and the Microsoft Graph API gives Cargofy the same view of it your team has. With the shared mailbox connected, a digital worker reads each message as Graph notifies it, links it to a load, files the attachments and drafts the reply. Customer service and dispatch work from Load Hub. IT usually switches it on, because the app registration lives in your Microsoft Entra tenant.

What teams use it for

Answer a tracking question from a draft

A customer emails the shared mailbox asking where their load from Atlanta to Miami is. Graph notifies Cargofy, and the worker matches the PO number in the subject to the load in Load Hub and drafts a reply with the last position and ETA from Tracking. Customer service opens Drafts, reads it and hits send. The answer takes a minute, and the thread stays on the load.

File the POD by conversation, not by filename

That afternoon the carrier replies on the same thread with the signed POD. Cargofy links it by conversationId, files the PDF to Documents on the same load and moves the thread to the Delivered folder. No one has to rename a scan or guess which of three loads it belongs to, and Finance has the POD it needs to release the carrier invoice.

Turn a rate request into a Sales quote

A prospect writes to the mailbox asking for a price on a lane. The worker recognises a rate request, looks up the lane in Sales and drafts a quote in Outlook with your standard terms. Procurement or sales reviews the draft, adjusts the number if the market moved, and sends it. The request and the quote both sit on the thread in Tracking when the order arrives.

Book the rate confirmation without retyping it

The carrier sends the signed rate con. The worker classifies it, files the PDF to Documents and extracts the rate, pickup date and reference into Load Hub. The dispatcher sees the load move from covered to confirmed, and the category applied in Outlook tells the team the email is handled.

Catch up after an outage

If the Graph subscription expires over a weekend, or the mailbox goes offline for an evening, notifications stop. Cargofy detects the gap and marks the connection degraded in Settings. When the mailbox is reachable again, it runs a delta query that returns every change since the last one it saw. The worker processes each message once: attachments filed to Documents, drafts written to Outlook, threads linked to loads. On Monday the dispatcher finds the weekend's mail handled in Load Hub, and IT sees the connection healthy in Settings.

Keep one thread per load for disputes

A consignee disputes a damage claim two weeks after delivery. Every email on that load was tied to it by conversationId on arrival and read into Tracking as the load's log, with the carrier, the customer and the consignee in one conversation. The dispatcher opens the load in Tracking, finds the driver's message about the pallets and the consignee's reply that day, and forwards both from Outlook to the claims handler.

How it fits your stack

Outlook stays the mailbox, and the originals never leave it; Load Hub and Documents hold the extracted fields and copies of attachments. Cargofy reads messages, attachments and threads, and writes folders, categories and drafts back, sending from the same mailbox. Setup is per installation: your admin registers the Cargofy app in Microsoft Entra, sets Mail.Read, Mail.Send and Mail.ReadWrite, and grants consent on your tenant. This covers mail only. Calendar, Teams and SharePoint are separate integrations.

Who it is for

Shippers and forwarders on Microsoft 365 with freight traffic in a shared ops mailbox. Dispatchers and customer service work the classified inbox, procurement reviews drafted rate replies, and the IT admin owns the Entra app registration and consent.