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

JT123803

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/JT123803/inquiry.eml

    ok
    From: Per Enok Hanssen
    Subject: Tilbud JT113975
    Body: 134 chars
    Attachments: Tilbud JT113975.pdf, Datablad MV110.pdf, Datablad MS2500.pdf, image001.gif, image094716.gif, image405498.png
    Show full email body
  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": null,
    "contact_email": null,
    "phone": null,
    "vat_number": null,
    "address": null
  },
  "items": [
    {
      "line_no": 1,
      "quantity": null,
      "unit": null,
      "product_reference": "Flowmålere (flow meters)",
      "manufacturer": null,
      "manufacturer_part_no": null,
      "cross_ref_to": null,
      "specs": {
        "dimension": null,
        "pressure_rating": null,
        "material_body": null,
        "material_seal": null,
        "actuation": null,
        "voltage": null,
        "torque_or_flow": null,
        "temperature": null,
        "thread_or_connection": null,
        "other": []
      },
      "missing_fields": [
        "quantity",
        "unit",
        "manufacturer",
        "manufacturer_part_no",
        "specs.dimension",
        "specs.pressure_rating",
        "specs.material_body",
        "specs.material_seal",
        "specs.actuation",
        "specs.voltage",
        "specs.torque_or_flow",
        "specs.temperature",
        "specs.thread_or_connection"
      ]
    }
  ],
  "application_context": null,
  "attachments_referenced": [],
  "delivery": {
    "location": null,
    "deadline": null,
    "incoterms": null
  },
  "previous_reference": {
    "is_update_of": "JT113975",
    "notes": "Quote response to prior agreement"
  },
  "completeness": "unusable",
  "missing": [
    "customer.company",
    "customer.contact_name",
    "customer.contact_email",
    "delivery.location",
    "delivery.deadline",
    "items.quantity",
    "items.unit",
    "items.specs.dimension",
    "items.specs.pressure_rating",
    "items.specs.material_body",
    "items.specs.material_seal"
  ]
}
  3. 3

    Completeness verdict: unusable

    Step 03

    Missing: customer.company, customer.contact_name, customer.contact_email, delivery.location, delivery.deadline, items.quantity, items.unit, items.specs.dimension, items.specs.pressure_rating, items.specs.material_body, items.specs.material_seal

    ok
    unusable
    • customer.company
    • customer.contact_name
    • customer.contact_email
    • delivery.location
    • delivery.deadline
    • items.quantity
    • items.unit
    • items.specs.dimension
    • items.specs.pressure_rating
    • items.specs.material_body
    • items.specs.material_seal
    Rule trace (deterministic)
    Verdict: unusable · no customer identity (need company name or contact email)
    • item 1: × needs follow-up — no quantity
  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 →