{
  "version": "1.0.0",
  "last_updated": "2026-08-20T00:00:00Z",
  "slug": "logistics-ops",
  "customer_anonymized_id": "nz-logistics-mid-market-001",
  "deployment_notes": [
    "Audit Agent runs in week 1: catalogues 18 repeatable ops processes and scores each on a 0-100 automation opportunity scale; dispatch-to-dispatch surfaces as the top scorer.",
    "Dispatch-scheduling AI employee goes live in week 3, layered on top of the Audit Agent's process catalog; reads live order volume, driver availability, and equipment readiness to surface the next dispatch decision for a human reviewer.",
    "Exception-handling AI employee reaches production in week 6, splitting into two role entries: customs broker handoff SLA and dispute triage response (driven dispute baseline down from 9 minutes to 38 seconds)."
  ],
  "roles": [
    {
      "name": "dispatcher",
      "title": "Dispatch-scheduling AI employee",
      "week_live": "Week 3",
      "status": "Roadmap",
      "system_prompt_stub": "Operate as the dispatch coordinator. Read live order volume, driver availability, and equipment readiness; surface the next dispatch decision for a human reviewer; never send instructions to drivers without human sign-off.",
      "output_contract": {
        "fields": ["recommendation", "confidence", "rationale", "links"],
        "example": "{ \"recommendation\": \"assign_driver_42_to_route_auckland-north_06:30\", \"confidence\": 0.86, \"rationale\": \"Driver 42 nearest dep, route within 4% of ETA target, equipment confirmed available.\", \"links\": [\"#/dispatch/orders/ord_9182\", \"#/drivers/drv_42\"] }"
      },
      "metric_impact": "62% drop in dispatch-scheduling cycle time across the first 90 days"
    },
    {
      "name": "customs_broker_liaison",
      "title": "Customs SLA AI employee",
      "week_live": "Week 6",
      "status": "In build",
      "system_prompt_stub": "Operate as the customs broker liaison. Triage inbound broker handoff packages, track each against the SLA window, and surface the next action to keep handoffs inside the window; never issue broker-facing comms without a human reviewer.",
      "output_contract": {
        "fields": ["recommendation", "confidence", "rationale", "links"],
        "example": "{ \"recommendation\": \"escalate_broker_handoff_bh_4421_priority_high\", \"confidence\": 0.91, \"rationale\": \"Handoff outstanding 18m against a 30m SLA window; broker B acknowledged unresponsiveness.\", \"links\": [\"#/customs/bh_4421\", \"#/brokers/alpha-freight\"] }"
      },
      "metric_impact": "94% within-shift customs broker handoffs completed inside SLA window"
    },
    {
      "name": "dispute_triage",
      "title": "Dispute triage AI employee",
      "week_live": "Week 6",
      "status": "In build",
      "system_prompt_stub": "Operate as the dispute triage responder. Read each inbound dispute, classify it against the ops taxonomy, and surface the next response for a human reviewer; never send customer-facing replies without human sign-off.",
      "output_contract": {
        "fields": ["recommendation", "confidence", "rationale", "links"],
        "example": "{ \"recommendation\": \"classify_dispute_dp_7734_category_delivery_window\", \"confidence\": 0.88, \"rationale\": \"Customer-supplied tracking and ops log corroborate 38s window between flag and reply; no SLA breach.\", \"links\": [\"#/disputes/dp_7734\", \"#/customers/cust_551\"] }"
      },
      "metric_impact": "Typical dispute triage response down from 9-minute baseline to 38 seconds"
    },
    {
      "name": "finance_reconciliation",
      "title": "Finance reconciliation AI employee",
      "week_live": "Later",
      "status": "Roadmap",
      "ready_when": "Customer signs off on the Audit Agent dispatch + customs + dispute roadmap after week 9.",
      "system_prompt_stub": null,
      "output_contract": null,
      "metric_impact": "Aim for $0 lost invoice value write-offs in the first 90 days, replacing the prior three-quarter trend."
    }
  ],
  "integrations": [
    {
      "system": "TMS",
      "purpose": "Transportation management system read/write for live dispatch decisions and equipment readiness telemetry",
      "version": "1"
    },
    {
      "system": "WMS",
      "purpose": "Warehouse management system read for equipment readiness, location state, and shift roster context",
      "version": "1"
    },
    {
      "system": "Email",
      "purpose": "Ops inbox for the daily digest and exception escalations routed back to the customer's ops team",
      "version": "1"
    },
    {
      "system": "Google Sheets",
      "purpose": "Shared spreadsheet used by dispatch coordinators today; persists as the source of record during the Audit Agent week-1 process map",
      "version": "1"
    }
  ],
  "output_schema_version": "1"
}