Jev meeting commitment check

Read how a prospect responds to a meeting invitation

Compare the invitation with the reply. Distinguish a scheduled meeting, willingness to talk, a request for information and a decline without interpreting any of them as buying intent.

meeting commitment checkLive API
Try an example

The person has not yet agreed to meet.

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 meeting commitment: Unclear first if the invitation or referent is missing, or evidence conflicts.

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

Meeting readiness is narrower than sales qualification. A person can be ready to schedule without having budget, authority or purchase intent. A request for documentation can also be useful without being a meeting commitment.

The output preserves those distinctions as labels. It does not parse an exact timestamp, resolve timezones, check availability or create an invitation.

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 meeting invitation replies.

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

    Add the information to check

    Compare the invitation with the reply.

  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 No, Information, Open, Schedule, 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
Send details firstInformation100%
Willing to talkOpen96.0%
Offers a slotSchedule100%
Accepts the offerSchedule100%
No meetingNo100%
Detached acknowledgmentUnclear72.0%

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

Meeting invitation replies: 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

  • Organizing invitation replies for a person
  • Separating document requests from meeting consent
  • Testing ambiguous short acknowledgments

Outside this demonstration

  • Booking a meeting
  • Inferring buying authority or budget
  • Resolving dates without a calendar policy
Example FAQ

Using this example

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

Does Schedule mean a confirmed event exists?

No. It means the text proposes or accepts a time. A calendar event would still need availability, timezone handling and a separate authorized action.

What if a reply only says yes?

Include the invitation. Yes to receiving a brochure is different from yes to a proposed meeting time.

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.