Screen 36 — Notes

Ticket-level notes shown as a chat thread. Two tabs: Thread (every message in chronological order, voice-first capture) and AI summary (a regenerated digest across all notes — TL;DR, key events, decisions, open items, people).

← Back

Tab A · Thread

11:22

‹

NotesWO-000046-1 · 3 people

⋯

💬 Thread 8

✨ AI summary

HVAC Maintenance

Adriaan House · Adam Wilson

Active

Today

MB

Maxwell · 10:12 AM

Arrived on site. Found the control board scorched — will replace contactor first and see if heat cycle stabilises.

ME

You · 11:08 AM

Contactor swap didn't fix it. Going to need the AX44 control board. @dispatch can you expedite from warehouse?

LB

Layla · Dispatch · 11:14 AM

Confirmed. PO-000112 raised, ETA 45 min. Customer notified.

PO-000112Customer notified

S

System · 11:16 AM

Activity paused. Timer on hold until part arrives.

🎤

Push to record a note · tap @ to mention someone

Tab B · AI summary

11:22

‹

NotesWO-000046-1 · 3 people

⋯

💬 Thread 8

✨ AI summary

✨ AI summary Updated just now · 8 notes

Contactor swap didn't resolve heat-cycle issue; tech needs the AX44 control board. Dispatch raised PO-000112 and customer was notified — ETA 45 minutes. Timer paused; work resumes on delivery.

Key events

10:12

Maxwell arrived on site, diagnosed scorched control board.

10:45

Contactor swap attempted — did not stabilise heat cycle.

11:08

Requested AX44 control board from dispatch.

11:14

PO-000112 raised · customer notified · 45-min ETA.

11:16

Ticket paused pending board arrival.

Open items

!

Await AX44 board delivery

PO-000112 · ETA 11:59 AM

!

Verify heat cycle after install

Confirm 2 full cycles before closeout

People

MB

Maxwell

Tech

LB

Layla

Dispatch

AW

Adam

Customer

Why a thread?

Notes are shown as a chat thread rather than a flat list so it's easy to follow the ticket over time — who said what, when, and in response to what. Work orders often involve multiple technicians, dispatchers and office staff across days or even a full revisit, and a thread keeps the human back-and-forth readable instead of burying it in a grid of rows. Alternating self/other alignment lets the current tech find their own contributions instantly.

Why an AI summary?

When a technician picks up a ticket — especially one another tech started, or one they're returning to after a few days — scrolling the whole thread is expensive. The AI summary tab gives them a one-glance overview: TL;DR, key events on a timeline, open items still needing action, and who's involved. They can be up to speed in seconds instead of minutes, and tap Regenerate any time new activity lands.

Jigx component mapping

One jig.composite with a jig.tabs segmented control at the top. Tab A (Thread) is a message jig.list with a docked composer (text-field + mic + send). Tab B (AI summary) is a jig.default with an AI card (TL;DR), a timeline jig.list, an open-items jig.list, and a people jig.gallery.

AI summary behaviour

Generated across every note in the ticket — what happened, what was decided, what's still open, who's involved. Regenerates on tap when the tech wants a fresh digest after new activity. Copy-to-clipboard is the secondary action so the tech can paste it into closeout, a handover message, or a customer note.

Primitives used

jig.tabs — Thread / AI summary
Tab A: message list-item rows with alternating alignment for self vs other, pills inside message bodies for cross-links (PO, status)
Tab A composer: text-field + mic + send button — voice-first, no chip shortcuts
Tab B TL;DR: AI card with glow accent and "updated just now" meta
Tab B timeline: list-item with a coloured dot + time column + body
Tab B people: jig.gallery of tappable people chips

What improved vs v1

Renamed from Notes & Escalation to just Notes — escalation isn't a separate feature, it's a property of individual notes (@mentioning dispatcher creates a linked PO automatically).
New AI summary tab — one tap to see the whole ticket story without scrolling the thread.
Timeline presents the AI-extracted events with coloured status dots (amber = blocker, green = resolved) for at-a-glance scanning.
Open-items list is actionable — the tech can use it as a personal checklist before closeout.
Copy summary + Regenerate exist as first-class dock actions on the AI tab.

Voice

Voice notes are captured on the thread and transcribed. The AI summary is built from the transcribed text (English or Spanish auto-translated), so the tech never has to re-type anything to get the digest.

M"Add a note that customer wants a return visit to rebalance vents after the board swap."

M"Summarise this ticket for handover."