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

JT124031

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

    ok
    From:
    Subject: #most
    Body: 79 chars
    Attachments: image001.jpg, image117277.gif
  2. 2

    AI extracts structured JSON

    Step 02

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

    ok
    Norwegianreorder1 item(s)
    Show extracted JSON
    {
      "language": "no",
      "intent": "reorder",
      "customer": {
        "company": null,
        "contact_name": null,
        "contact_email": null,
        "phone": null,
        "vat_number": null,
        "address": null
      },
      "items": [
        {
          "line_no": 1,
          "quantity": 1,
          "unit": "stk",
          "product_reference": "Camlock complete — same as the one purchased last year",
          "manufacturer": null,
          "manufacturer_part_no": null,
          "cross_ref_to": "previous Camlock order (last year)",
          "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": "valve_type",
                "value": "Camlock"
              },
              {
                "key": "configuration",
                "value": "complete (assembly)"
              }
            ]
          },
          "missing_fields": [
            "dimension",
            "material_body",
            "thread_or_connection",
            "all specs — must be pulled from prior order history"
          ]
        }
      ],
      "application_context": "Reorder of the same Camlock complete the customer purchased last year. All specs must be pulled from prior order history.",
      "attachments_referenced": [
        "image001.jpg (likely image of the Camlock)"
      ],
      "delivery": {
        "location": null,
        "deadline": null,
        "incoterms": null
      },
      "previous_reference": {
        "is_update_of": "previous Camlock order from last year",
        "notes": "No customer identity provided in body — JS Cock salesperson Morten Steinset forwarded with #most tag. Customer identity must be inferred from the original (un-forwarded) email or salesperson context."
      },
      "completeness": "unusable",
      "missing": [
        "customer identity (company, contact email)",
        "specific Camlock spec — must look up prior order"
      ]
    }
  3. 3

    Completeness verdict: unusable

    Step 03

    Missing: customer identity (company, contact email), specific Camlock spec — must look up prior order

    ok
    unusable
    • customer identity (company, contact email)
    • specific Camlock spec — must look up prior order
    Rule trace (deterministic)
    Verdict: unusable · no customer identity (need company name or contact email)
    • item 1: ✓ quotablemanufacturer 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 →