Demo 02 · Email automation
Seven messages of chaos. One clean tracker.
This prototype shows a synthetic email chain organised into a summary, task list, status tracker and reviewable reply. It demonstrates the output structure, not a live mailbox connection.
Input - email chain (7 messages)
synthetic sampleOutput 1 - summary
pipeline outputPO-4471 (12-way switchgear) has slipped from the 21st to the 24th due to breaker back-orders. Site can absorb the delay if the crane booking moves to the 25th - crane must be confirmed by Thursday or the slot is lost. Supplier has offered witness testing (+1 day, certs on delivery). Three calls to make: accept ETA, move crane, decide on witness testing.
Output 2 - tracker
synced to sheet / CRM| Item | Status | Owner | Due |
|---|---|---|---|
| PO-4471 revised ETA (24th) | decide | Lena | Wed |
| Crane booking to 25th | critical | Ahmed | Thu |
| Witness testing decision | decide | Lena | Wed |
| Breaker modules to PowerFab | in progress | PowerFab | Thu |
| Assembly & factory test | queued | PowerFab | Fri |
Output 3 - response, drafted
ready to sendTo: PowerFab Supplies · Subject: RE: PO-4471 - revised ETA accepted, witness testing confirmed
Hi team,
Thanks for the update and the transparency on the back-order.
Confirming: we can work with dispatch Monday / delivery on the 24th. Please proceed with witness testing - certificates on delivery are worth the extra day, so we'll take delivery on the 25th to align with our crane window.
One condition: if the breakers slip past Thursday, we need to know same-day, as our crane slot depends on it.
Could you confirm the witness-testing date so our engineer can attend?
Regards,
Lena
SYNTHETIC DEMONSTRATION · Prebuilt sample information and example outputs. A production workflow would require source access, privacy review, integration design and acceptance checks.
