Microsoft · Solution Engineering TE Connectivity

Freight Triage Control Tower — a working prototype

One surface for the operations team to Queue → Assign → Resolve post-booking freight emails — review the email thread on each item, and track ageing + SLA. Try it, download it, and tell us what to change.

Prepared for TE Connectivity by the Microsoft Solution Engineering team.
Start here
A 30-second walkthrough
See the control tower, the inbox, and the email-on-item review end to end. Prefer to dive in? Jump straight to the live prototype below.
Explore
Try it & take it with you
The prototype runs on sample data — no sign-in needed. Anything you assign or resolve is remembered in your browser.
🖥️

Try the prototype

Open the interactive app. Move items through Queue → Assign → Resolve, browse the inbox, and open an item to read its email thread.

Open the prototype →
⬇️

Download the project

The source code to run it yourself: npm install then npm run dev. Built as a Power Apps Code App (React + TypeScript).

Download .zip →
📄

What it does

The four screens, the SLA model, how it connects to your existing email-intelligence flows, and how it goes live on Dataverse — in plain terms.

Read the overview →
On GitHub
The source, ready to hand off
The build lives in two private GitHub repositories — the freight control tower itself and a companion accelerator it reuses. Sign in to GitHub to open them (access is shared with your team).
📦

Freight Triage Control Tower

The full turnkey package — the Power Apps Code App, the Dataverse schema, the go-live runbook, and the design decisions behind it.

Open the repo →
♻️

RMA Returns Monitor — accelerator

A companion, reusable returns-triage accelerator the control tower borrows its queue → assign → resolve patterns from.

Open the repo →
Overview
What you're looking at

The prototype layers a single control surface on top of your existing email-extraction and sentiment flows. Every flagged shipment email becomes a triage item the team owns and resolves against an SLA.

  • Control Tower — Queue / Assigned / Resolved lanes with priority + SLA badges. Assign an owner, resolve, reopen.
  • Inbox — every inbound email, filter by carrier or mode, jump to the related triage item.
  • Item detail — shipment identifiers (SH#, HBL / AWB / MBL), an SLA countdown, and the full email thread inline.
  • Ageing & SLA — open by ageing bucket, breaches by carrier and owner, resolved-within-SLA %, and mean time to resolve — no separate BI tool needed.

How it goes live. The prototype runs on sample data in your browser. The production build promotes these same screens onto Microsoft Dataverse as the system of record — each triage item and its email log as related tables, with role-based security, audit, and the ageing/SLA views built in. We looked at a SharePoint list and recommend Dataverse for the relational model, typed status/priority/SLA fields, and the security it gives you at scale. It stays a Power Apps Code App, with an optional Copilot Studio assistant over the same data for natural-language questions if you want one.

Triage state only — the prototype never writes back to booking systems and sends no automated email. Carriers, shipment numbers, and emails shown are fictional demo data.