Jev prospect responsibility match

Identify a prospect's explicitly stated responsibility

Read the person's explicit responsibility statement. Distinguish technical evaluation, procurement and operational rollout, preserving absent or competing roles rather than guessing from a job title.

Which project conversation does this contact own?Live API
Try an example

Original synthetic input. Edit the task or evidence to make a new API request.

Source: Workflow inspiration on X

Source and example scope

The inputs, rubric and preview are original. This window demonstrates the stated decision only; it does not reproduce the source application or its measurements.

Read responsibilityStatement.

Decision rules and labels
Technical evaluationProcurement reviewOperational rolloutNo assigned roleNeed role statement
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

How does Jev prospect responsibility match use the supplied evidence?

Jev prospect responsibility match matches an explicitly stated project responsibility to a conversation track. Jev separates technical evaluation, procurement and operational rollout from an observer and an unresolved role. The packet proposes a fixed follow-up topic without scoring the prospect’s readiness.

A marketing-session post named lead qualification as a Jev application. This original demonstration isolates one narrower step: ask the right project question based on duties the contact actually supplied. It neither reproduces the webinar nor claims its presenters tested this implementation.

A title such as director does not prove purchase authority, and responsibility for testing an integration does not prove budget approval. The original messages name their assigned duties and, where relevant, exclude other responsibilities. That lets a reviewer inspect the exact basis for the track.

The fictional project has no customer account, deal value or purchase deadline. Multiple responsibilities without a primary one stay unresolved. No message is drafted or sent, and the returned track cannot qualify a lead or authorize contact.

Original Jev prospect responsibility match workflow diagram showing supplied evidence, a typed decision and the local preview.
Original workflow illustration. The output is a local preview, not an executed action or source screenshot.
How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for prospect responsibility matching.

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

    Read the person's explicit responsibility statement.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between Technical evaluation, Procurement review, Operational rollout, No assigned role, Need role statement. Edit the choices only when testing your own rule.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

    Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review Procurement review, Need role statement before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

What the six original inputs returned.

What the six original inputs returned.
Original test inputFixture expectationObserved labelLeading probability
The contact owns integration testingTechnical evaluationTechnical evaluation100%
The contact owns vendor-term reviewProcurement reviewProcurement review100%
The contact owns staff rolloutOperational rolloutOperational rollout99%
An observer without an assigned roleNo assigned roleNo assigned role100%
Multiple roles without a primary oneNeed role statementNeed role statement61%
Technical evaluation stated another wayTechnical evaluationTechnical evaluation100%
  • 6 of 6 original fixture expectations matched. Contrary outputs are preserved in the table and downloads; these checks are not held-out accuracy or production suitability.
  • Measured adapter round trips: 461-1197 ms. Estimated input cost: $0.00002461-$0.00002503 per request. These observations are not a latency guarantee or invoice.

6 actual Jev API calls on October 4, 2026. Original synthetic inputs check this rubric and handoff; they do not establish held-out accuracy. Probabilities are model outputs.Verified

Understand the results

The contact owns integration testing

The first contact explicitly owns API integration testing and assigns purchasing and rollout elsewhere.

Read the example notes

Technical evaluation proposes discussing the integration contract. It does not infer technical competence or purchase authority. The packet uses the stated project duty only, with any real sales process remaining outside this original example.

The contact owns vendor-term review

The second contact owns vendor terms and paperwork while excluding testing and training.

Read the example notes

Procurement review proposes discussing that declared track. Reviewing terms is not proof of signing authority or approved spending, so those claims do not appear in the output. The fixed local packet sends no communication.

Rollout responsibility covers training and daily adoption

The rollout contact owns training and daily adoption, with other people handling evaluation and purchasing.

Read the example notes

Operational rollout proposes asking about that work. The model does not infer how many users exist, whether rollout has been approved or whether the product is suitable. Those facts would require separately supplied evidence.

The observer explicitly owns none of the three listed responsibilities

The observer explicitly owns none of the three listed responsibilities.

Read the example notes

No assigned role preserves that statement without judging the person’s value or buying potential. It avoids forcing every interested contact into a sales track. A real application should retain this evidence and decide its own permitted follow-up policy.

Multiple roles without a primary one

Two responsibilities without a primary one do not identify one conversation track.

Read the example notes

Need role statement proposes asking which role matters for this discussion. Taking the first mentioned duty would lose the unresolved intent. The full distribution and exact original statement remain visible rather than hiding this boundary behind a confident label.

Technical evaluation stated another way

The final contact describes integration evaluation without using the first sample’s wording.

Read the example notes

Technical evaluation should follow the meaning of the assigned task. Purchasing and onboarding remain explicitly outside that task. This paraphrase fixture checks the declared rubric only and cannot establish broad accuracy across real organizational roles.

Source and example scope

Fixture expectations are authored before the calls. Any contrary model choice remains visible beside its expectation and complete distribution; no repeated judgment is used to obtain a preferred label.

Using the result in your application

Download the exact sample requests and saved observations below.

Read the example notes

Expected labels are original fixture checks and stay outside the request sent to Jev. The observation file preserves the complete probabilities and the hash of each exact request. Editing a task, rubric or candidate requires a fresh response; a matching sample name does not make an older answer current.

Using the result in your application

The JavaScript runner makes one independent SDK request for a chosen sample ID.

Read the example notes

It reads TYPESAFE_API_KEY privately from the environment and has no automatic retry. The Python consumer operates offline: it checks the rubric, labels, unique sample identities, request hashes and valid probability distributions before selecting a fixed local preview. A tied leading result remains pending for review.

Source and example scope

The page reports measured adapter round trips and estimated input cost for the recorded calls.

Read the example notes

Those values describe these requests, not a provider latency guarantee or a billing statement. Six deliberately authored fixtures can check the stated behavior, but they do not establish accuracy on an unseen dataset. Keep disagreements and missing-input examples when testing an integration.

Runnable offline example

Replay one request and inspect the saved preview.

View the code example
Replay commands
npm install @typesafe-ai/sdk@0.6.0
# Set TYPESAFE_API_KEY privately in your shell.
node run-choice-sample.mjs samples.json 1
python preview_choice_workflow_v2.py samples.json saved-api-results.json
Runnable offline example

The first request and its recorded local output.

View the code example
Exact first sample and local preview
{
  "input": {
    "task": "Review the supplied evidence under the explicit rule, preserving any missing or unresolved facts.",
    "responsibilityStatement": "My job in this project is to test the API integration. Another person handles purchasing and rollout."
  },
  "localOutput": {
    "sampleId": "1",
    "leaders": [
      "Technical evaluation"
    ],
    "probabilities": {
      "Technical evaluation": 1,
      "Procurement review": 0,
      "Operational rollout": 0,
      "No assigned role": 0,
      "Need role statement": 0
    },
    "action": "review_technical_evaluation_topic",
    "payload": {
      "reviewLabel": "Technical evaluation",
      "externalActionPerformed": false
    },
    "pending": true
  }
}
Scope of this demo

Where does this decision fit?

Useful with explicit supplied evidence

  • Match a contact’s explicitly supplied primary project duty to a technical, procurement or rollout conversation track, preserving observers and unresolved multiple roles without scoring readiness or inferring authority.
  • Inspecting the original task and a fixed output before integrating external tools.
  • Comparing an explicit expected label with the complete recorded distribution.

Needs separate implementation or evidence

  • Inferring facts absent from the supplied input.
  • Treating a semantic selection as authorization to act.
  • Executing an external action or generalizing six fixtures into an accuracy claim.
Example FAQ

Questions about this original decision workflow.

Keep relevance, compliance and execution separate.

Does this qualify a lead?

No. It identifies a stated responsibility for a conversation. Need, budget, authority and timing remain unassessed.

Can a job title establish purchasing authority?

No. This rubric uses explicit project duties and keeps missing or multiple roles unresolved.

Does the output send a sales message?

No. The local packet proposes a fixed topic and remains pending. It drafts or sends nothing.

Are these profiles inferred from X accounts?

No. All responsibility statements are original fictional inputs. The X post supplies attributed workflow inspiration only.

Try a task from your own workflow

Change the supplied task or evidence here, then inspect the live response. Playground supports another explicit decision.