Jev outreach reply disposition

Classify an outreach reply before following up

Compare a reply with the original outreach. Distinguish interest, a later follow-up, a redirect, an objection and automated responses, giving explicit stop-contact requests priority.

outreach reply dispositionLive API
Try an example

The response engages with the offered discussion.

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.

Classify outreach replies in order: Stop for an explicit no-contact request; Away for an automatic temporary-absence reply; Automated for other system replies.

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

Different replies need different human follow-up decisions. An out-of-office message is not a rejection, and a ticket acknowledgment is not interest. Providing the original outreach also helps interpret short replies.

The Stop label is a safety exit in this example, not a complete contact-permission system. The page does not send mail, change a suppression list or grant permission to contact a referred colleague.

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 outreach reply classification.

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

    Add the information to check

    Compare a reply with the original outreach.

  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 Interest, Later, Wrongperson, Objection, Away. 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
Relevant interestInterest100%
Later in the yearLater100%
Different ownerWrongperson99.0%
Automatic absenceAway100%
Plain refusalObjection95.0%
Stop despite praiseStop100%

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

Outreach reply classification: 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

  • Reviewing a small reply queue
  • Distinguishing absence from timing objections
  • Testing a clear opt-out precedence rule

Outside this demonstration

  • Sending or scheduling outreach
  • Bypassing suppression or consent policies
  • Treating a referred name as permission to contact
Example FAQ

Using this example

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

Does Later schedule another email?

No. It describes the reply. A separate process must check contact permissions, suppression rules and the appropriate timing before any action.

How does this differ from the unsubscribe example?

This page sorts an entire reply queue into several dispositions. The dedicated unsubscribe example examines opt-out meaning more closely; use it when that is the task you need to test.

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.