Skip to main content

​
Oversight Agent

⚪ Planned (Phase 4) The oversight agent is the always-on watcher. It doesn’t drive any individual workflow — it watches all of them and surfaces what’s slipping. Managers get the visibility they currently have to assemble by hand from email threads.

​
What it tracks

For every RFQ that’s ever entered the pipeline:
  • Which have a style record
  • Which have a BOM draft
  • Which have a true cost draft
  • Which have a quotation
  • Which quotations were sent
  • Which clients replied
  • Which inquiries went cold
  • Which staff are delayed

​
Why this matters

Today, missed opportunities at VinMake come from:
  • Staff replying slowly
  • RFQs not being followed up
  • Clients stopping mid-thread
  • Inquiries going cold with nobody noticing
  • Managers lacking clean visibility
  • Email threads being too long and fragmented to scan
The oversight agent exists to make those failure modes visible before they cost an order.

​
Pipeline view

The oversight dashboard surface (in the Inbox / Task / Engine UI) shows every active RFQ as a row: Managers can filter, sort, and drill into any row.

​
Risk detection

The agent flags specific risk patterns and routes them to the right person: Thresholds (N hours, N days) are configurable per workflow stage.

​
Manager alerts

Example surfaced alerts:
“Jaspal style J26WGW153 has a tech pack and style record, but no true cost draft after 2 days.”
“Quotation was sent to Lulus 7 days ago with no client reply. Recommend follow-up.”
“3 RFQs are waiting for human approval before style creation.”
Alerts route to:
  • The owner for normal-priority slips
  • The manager for ownership gaps or extended cold inquiries
  • The Inbox as a Risk tagged item that anyone with the right role can see

​
What it doesn’t do

The oversight agent doesn’t take action on its own. It surfaces, it flags, it recommends. Following up with a client, reassigning an RFQ, or escalating a price issue are human decisions.