← All examples 85 / 100

Jev Objection classification Code Example

Separate price concerns from trust or implementation concerns.

We like it, but moving ten years of data sounds risky.

Message We like it, but moving ten years of data sounds risky.

What concern should the response address?

0% Migration risk.

Migration risk 91%

Price 6%

Missing feature 3%

Let the application migration risk.

Code

// Conceptual pseudocode — not Jev SDK syntax
const state = {
  "message": "We like it, but moving ten years of data sounds risky."
};

const decision = await evaluateDecision({
  state,
  question: "What concern should the response address?",
  options: ["Migration risk","Price","Missing feature"],
});

// Your adapter normalizes the provider response.
// Tune this example threshold on labelled data.
if (decision.outcome === "Migration risk"
    && decision.probability >= 0.85) {
  selectObjectionPlaybook(decision);
} else {
  queueForReview(decision);
}

This adapter illustrates the decision boundary. Check the official Jev docs for current API syntax.