J.S.Cock · AI Inquiry Demo
← All inquiries · Inquiry detail view
End-to-end flow

JT121549

One inquiry, all stages. Each box below is the actual artifact persisted by the pipeline — not a mockup. The brief asks: "does Kine actually work?". This page is the answer.

4 stages
  1. 1

    Email arrives in M-Files inbox

    Step 01

    Inquiry stored at .tmp/jscock_mfiles/JT121549/inquiry.eml

    ok
    From:
    Subject: #most
    Body: 134 chars
    Attachments: image001.png, image411465.gif
  2. 2

    AI extracts structured JSON

    Step 02

    1 item(s) detected · language=no · intent=update_quote

    ok
    Norwegianupdate quote1 item(s)
    Show extracted JSON
    {
  "language": "no",
  "intent": "update_quote",
  "customer": {
    "company": null,
    "contact_name": "Morten Steinset",
    "contact_email": null,
    "phone": null,
    "vat_number": null,
    "address": null
  },
  "items": [
    {
      "line_no": 1,
      "quantity": 1,
      "unit": "stk",
      "product_reference": "BRA00513 (catalog SKU); customer correcting size from DN100 to DN300",
      "manufacturer": null,
      "manufacturer_part_no": "BRA00513",
      "cross_ref_to": null,
      "specs": {
        "dimension": "DN300",
        "pressure_rating": "PN16",
        "material_body": null,
        "material_seal": null,
        "actuation": null,
        "voltage": null,
        "torque_or_flow": null,
        "temperature": null,
        "thread_or_connection": null,
        "other": []
      },
      "missing_fields": []
    }
  ],
  "application_context": "Internal note from JS Cock staff (Morten Steinset) correcting an existing customer order: size is DN300 (not DN100) for catalog SKU BRA00513 at PN16. Customer identity is not stated in the email body — it sits in the parent thread.",
  "attachments_referenced": [],
  "delivery": {
    "location": null,
    "deadline": null,
    "incoterms": null
  },
  "previous_reference": {
    "is_update_of": null,
    "notes": "Size correction (DN100 → DN300) on an existing JS Cock customer order"
  },
  "completeness": "unusable",
  "missing": [
    "customer identity (referenced as 'kunden' but not named in body)"
  ]
}
  3. 3

    Completeness verdict: unusable

    Step 03

    Missing: customer identity (referenced as 'kunden' but not named in body)

    ok
    unusable
    • customer identity (referenced as 'kunden' but not named in body)
    Rule trace (deterministic)
    Verdict: unusable · no customer identity (need company name or contact email)
    • item 1: ✓ quotable — manufacturer part-no or cross-ref present (catalog-resolvable)
  4. 4

    Route to human

    Step 04

    Inquiry too sparse — sales engineer should handle manually.

    skip

Process map: see how this aligns with JS Cock’s diagram →