Jev sales qualification evidence

Check whether sales notes establish a qualification fact

Supply call notes and one qualification criterion. Distinguish concrete evidence from a passing mention or an undiscussed subject, keeping conflicting notes visible rather than inferring qualification.

sales qualification evidenceLive API
Try an example

The fictional note supplies both a baseline and target.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This original text demonstration adapts a decision in a repository linked by the cited X post. The examples and explicit uncertainty outcomes are ours. The post is a directory reference, not proof that its author built every linked project. No third-party benchmark, business outcome or external action is reproduced.

Apply the supplied dimension criterion to the notes: Established if its required concrete evidence is present; Mentioned if the subject is discussed but required detail is missing; Notdiscussed if the notes never address it; Unclear if the notes or criterion are missing or contradictory.

Decision rules and labels
EstablishedMentionedNotdiscussedUnclear
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

What the decision checks

This example covers one evidence method across several MEDDPICC-style dimensions. The criterion is part of the input: metrics need a measure, a budget owner needs stated authority, and a champion needs an observed internal action.

Established means the supplied notes meet the supplied criterion. It does not verify that the speaker was truthful, that the notes are complete or that the opportunity will close. Keep the underlying notes available for a human review.

This original text demonstration adapts a decision in a repository linked by the cited X post. The examples and explicit uncertainty outcomes are ours. The post is a directory reference, not proof that its author built every linked project. No third-party benchmark, business outcome or external action is reproduced.

Illustration of routing a message into one of several label groups
Illustration of the decision flow.
How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for sales qualification evidence.

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

    Add the information to check

    Supply call notes and one qualification criterion.

  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 Established, Mentioned, Notdiscussed, Unclear. 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 Unclear before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
Measured targetEstablished100%
Vague improvementMentioned83.0%
Budget owner confirmedEstablished100%
Friendly contactMentioned97.0%
No procurement discussionNotdiscussed100%
Conflicting authorityUnclear100%

These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified

Understand the results

Sales qualification evidence: six recorded examples

The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.

Using the result in your application

The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.

Runnable offline example

Run one sample, then inspect the local packet

View the code example
Single-request replay
npm install @typesafe-ai/sdk@0.6.0
# Set TYPESAFE_API_KEY privately in your shell.
node run-choice-sample.mjs samples.json case-1
python preview_choice_workflow.py samples.json saved-api-results.json
Scope of this demo

Where this decision fits

Useful scope

  • Checking qualification notes for missing specifics
  • Comparing dimension-specific evidence requirements
  • Creating a list of questions for the next call

Outside this demonstration

  • Predicting revenue
  • Verifying a real person’s authority externally
  • Scoring people or inferring unstated personal traits
Example FAQ

Using this example

The input contract and these limits define what the result means.

Why keep several dimensions on one page?

They share the same evidence-checking method. Change the dimension and criterion together, then compare what the notes establish rather than treating every label as a different workflow.

Does a senior title establish the economic buyer?

No. Under the supplied criterion the notes must name a person and explicitly establish budget control. A title by itself is insufficient.

Does the leading probability measure accuracy?

It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.

Will a result change an external system?

No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.

Test a different input

Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.