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

JT122170 · Equinor ASA

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

    ok
    From: khuse@equinor.com
    Subject: RFQ 6090396036
    Body: 1383 chars
    Attachments: RFQ 6090396036.pdf, image513645.gif
    Show full email body
  2. 2

    AI extracts structured JSON

    Step 02

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

    ok
    Norwegiannew inquiry1 item(s)
    Show extracted JSON
    {
      "language": "no",
      "intent": "new_inquiry",
      "customer": {
        "company": "Equinor ASA",
        "contact_name": "Kristine Huseby",
        "contact_email": "khuse@equinor.com",
        "phone": "+47 93443569",
        "vat_number": null,
        "address": "Sandsliveien 90, Sandsli, Norway"
      },
      "items": [
        {
          "line_no": 1,
          "quantity": null,
          "unit": null,
          "product_reference": "Items per RFQ 6090396036 (specs in the original RFQ document, not in this follow-up email)",
          "manufacturer": null,
          "manufacturer_part_no": null,
          "cross_ref_to": "Equinor RFQ 6090396036",
          "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": [
              {
                "key": "rfq_number",
                "value": "6090396036"
              },
              {
                "key": "industry",
                "value": "offshore oil & gas (Equinor)"
              }
            ]
          },
          "missing_fields": [
            "all spec fields — original RFQ document is the source"
          ]
        }
      ],
      "application_context": "Follow-up: customer sent the RFQ earlier in autumn and has not heard back. Asks if JS Cock can deliver. The actual specs live in the original RFQ document referenced by number.",
      "attachments_referenced": [
        "original RFQ 6090396036 (sent separately, not attached to this follow-up)"
      ],
      "delivery": {
        "location": null,
        "deadline": null,
        "incoterms": null
      },
      "previous_reference": {
        "is_update_of": "Equinor RFQ 6090396036",
        "notes": "Original RFQ was sent earlier in autumn 2025. JS Cock needs to locate and respond to the original RFQ document."
      },
      "completeness": "unusable",
      "missing": [
        "the original RFQ document (referenced by number, not attached here)",
        "all item specs",
        "quantities",
        "delivery location"
      ]
    }
  3. 3

    Completeness verdict: unusable

    Step 03

    Missing: the original RFQ document (referenced by number, not attached here), all item specs, quantities, delivery location

    ok
    unusable
    • the original RFQ document (referenced by number, not attached here)
    • all item specs
    • quantities
    • delivery location
    Rule trace (deterministic)
    Verdict: partial · 1 of 1 items need clarification
    • item 1: × needs follow-upno 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 →