Jev unsubscribe request intent

Read the scope of an unsubscribe request

Read the message to distinguish stopping all contact from stopping one named topic. Preserve ambiguous scope and messages with no stop request before applying changes in a separate contact system.

What communication does this person ask to stop?Live API
Try an example

Original input for the All contact stop outcome. Edit the evidence to send a new request.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This is an original synthetic demonstration adapted from the cited workflow discussion. It does not reproduce the source application or verify its performance, adoption or security claims.

Read the explicit stop-request scope.

Decision rules and labels
All contact stopTopic stopNo stop requestUnclear scopeNeed evidence
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

Declining a meeting is not an all-contact opt-out.

A person can decline one meeting while asking for follow-up notes. The classifier follows the explicit communication request rather than turning a negative reply into a permanent stop instruction.

Topic stop preserves a narrower scope, such as promotional messages, while All contact stop reflects an explicit broad request. The quoted-example fixture keeps a reproduced sentence separate from the speaker’s own request.

The source describes an inbox workflow with stop-contact judgments. This example does not adopt its thresholds or make a legal consent determination. It returns a pending text label and changes no contact list.

This is an original synthetic demonstration adapted from the cited workflow discussion. It does not reproduce the source application or verify its performance, adoption or security claims.

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 unsubscribe request scope.

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

    Add the information to check

    Read the message to distinguish stopping all contact from stopping one named topic.

  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 All contact stop, Topic stop, No stop request, Unclear scope, Need evidence. 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 scope, Need evidence 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
All messagesAll contact stop100%
Promotion onlyTopic stop100%
Meeting declinedNo stop request100%
Vague stopUnclear scope93.0%
Quoted requestNo stop request77.0%
Message absentNeed evidence100%

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

Source and example scope

Compare each saved result with its authored expectation. A disagreement remains in the fixture review; the call is not repeated to obtain a preferred label.

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

  • Reviewing explicit stop requests in an inbox
  • Preserving limited scope and quoted examples
  • Replaying the exact synthetic requests and inspecting their distributions

Outside this demonstration

  • Making a legal consent decision from this classifier
  • Automatically suppressing contact from ambiguous text
  • Treating six fixture expectations as measured production accuracy
Example FAQ

Questions about unsubscribe request intent.

The rubric explains the decision; the application owns the next step.

Is Topic stop permission to send everything else?

No. It describes the requested stop scope. Existing permissions, user preferences and applicable communication policy still govern any future contact.

Why include the quoted example?

A stop sentence quoted for discussion is not necessarily the speaker’s own request. The supplied context explicitly distinguishes those meanings.

Does the leading probability measure production accuracy?

No. It is the model distribution for this one request. The six examples are functional checks with authored expectations, not a representative benchmark. Inspect disagreements and evaluate your own examples before using the label.

What happens when the API fails?

The window shows an error and supplies no fresh judgment. The downloadable runner sends one request without retries. Need evidence is a valid outcome about incomplete input; it does not stand in for a network or provider failure.

Try your own unsubscribe request intent input

Edit the evidence above or use the Playground to test another bounded question.