Jev email solicitation check

Separate sales pitches from account-service emails

Provide the email and its account context. Distinguish an optional purchase pitch, service notice and a message that includes both, without trusting urgency or a personal greeting.

email solicitation checkLive API
Try an example

A name and urgent wording do not create an account obligation.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Classify the supplied email and context.

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

An inbox policy often needs the message's purpose separately from its importance. A legitimate service notification may include marketing, and a sales pitch may use the same urgent language as a billing notice.

The source-linked builder article treats commercial solicitation as one of several independent email judgments. This example isolates that question with fictional messages. Its labels do not establish that a sender is genuine or that an account request should be followed.

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Illustration of one spreadsheet row producing two separate classification results
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 email solicitation.

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

    Add the information to check

    Provide the email and its account context.

  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 Solicitation, Service, Mixed, Review. 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 Review 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
Personalized promotionSolicitation100%
Payment failureService100%
Notice with offerMixed100%
Support responseService99.0%
Vague account claimReview92.0%
Cold proposalSolicitation100%

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

Email solicitation: 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.

Replay options

Inspect saved outputs or request a new decision

View the code example
Two independent commands
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json

# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.
Scope of this demo

Where this decision fits

Useful scope

  • Separating promotional purpose from sender-based preferences
  • Keeping substantive account information visible in mixed mail
  • Testing personalized outreach and automated support notices

Outside this demonstration

  • Authenticating senders or checking links for phishing
  • Calculating urgency or deciding payment obligations
  • Deleting, suppressing or replying to mail
Example FAQ

Using this example

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

Is every automated message promotional?

No. A requested export, receipt or account notice can be a Service message. Automation is not the purpose of the email.

Should Mixed mail be suppressed?

That is a separate application decision. Mixed preserves the fact that a message contains service information as well as an offer; this demo does not hide or delete it.

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.