Sales failure modes with Jev
Reps leave messy notes, emails, and call snippets. The CRM still owns Opportunity stage, quotes, and SLAs. Jev judges the text you provide so code can set a next-motion field or open a human queue. It does not send outreach or update ARR.
This unofficial page is the failure modes slice of the sales motion decisions pack. Intent: apply the Jev (TypeSafe System One) decision model to sales motion decisions failure modes. Primary search language: Sales Jev failure modes. Confirm patterns on docs.typesafe.ai. This site does not sell, issue, or proxy TypeSafe keys. Use a credential you already have from the console or a documented gateway.
Independent angle (cover ≠ clone): CRM-owned objects + Jev-on-notes (next motion, AE-ready, heat) — not a clone of a sales-automation landing page or rival CRM recipe IA.
Sales use-case context
Sales motion decisions breaks in product-specific ways. This page lists those modes so you can write tests — not a generic “AI can be wrong” essay, and not a rival limitations-page clone.
Hub: Use cases. Compare, when the other tool is the real job: CRM workflows.
Failure Modes inputs
Many failures start as contract violations (distractors, missing sales note / thread snippet text). Canonical shape:
{
"note": { "id": "n-8821", "text": "CFO asked for a Q4 start; legal wants DPA first.", "source": "call" },
"opp": { "stage": "discovery", "arr_band": "50-100k", "days_in_stage": 18 },
"playbook": { "ae_ready": "Budget + timeline + next meeting, or a named blocker." }
}Decision signals and actions
- CRM workflows own objects and SLAs; they do not read messy notes (compare).
jev-1.13loses accuracy when you paste the whole Opportunity dump (jaggedness: distractors).- Treating ae_ready.noul == 0.5 as “medium ready” — it means yes/no are equally likely.
- Asking Jev to set a close date or discount percent (arithmetic / dates stay in code).
- A 200-leaf product SKU tree as one Choice — cascade or keep SKU in CRM.
HTTP vs application:
| You see | Class | Sales move |
|---|---|---|
| 401 / 422 / 429 / 529 | Documented HTTP | Fix key/body or back off — errors |
| 200 + flat confidence or Noul ≈ 0.5 | Low confidence | Hold; do not reassign the Opportunity or issue a concession |
| Empty gather | Missing evidence | Skip Jev or ask “is enough information present?” |
Do not treat a Noul of 0.5 as a “medium” sales motion decisions score — it means yes and no are equally likely. Conjunctions stay in your code.
Guardrails and escalation
Fail closed: do not reassign the Opportunity or issue a concession. Schema-safe answers are not factual correctness. TypeSafe’s confidence-gated examples use a lower bar for recoverable reads than for irreversible actions. Those numbers are illustrations. For sales motion decisions, treat ae_accept as the high bar (reassigning an Opportunity to an AE or issuing a commercial concession). Tune on labels — see offline evaluation.
Evaluation and rollout notes
Your canary set should include each bullet above.
- Auto-motion error rate at your floor (not a jev.pro leaderboard)
- False AE accepts / missed legal blocks
- Handoff rate: if everything reviews, the floor is theater
Pin jev-1.13.0 (the versioned id) after you fit thresholds. jev-latest and the marketing line jev-1.13 can move. Log the response model. TypeSafe’s published list price for jev-1.13 is $0.042 per million input tokens (vendor claim — confirm on the models page); output tokens are free on that same page. Unused distractors still bill as input.
Official Python and JavaScript SDKs read TYPESAFE_API_KEY and retry documented 429/529. This site does not sell, issue, or proxy TypeSafe keys. Use a credential you already have from the console or a documented gateway.
Pack map
| Slice | Page |
|---|---|
| Graph and primitives | decision workflow |
What may enter state |
input contracts |
| What to gather first | evidence collection |
| Atomic rules | policy checks |
| Act / review / abstain | confidence thresholds |
| Reviewer payload | human handoff |
| What to persist | audit trail |
| How it breaks | you are here |
| Labeled replay | evaluation |
| Shadow → canary | production rollout |
FAQ
If the API returns 200, is the decision good? 200 only means the call parsed. Low confidence, Noul ≈ 0.5, or a policy miss are application failures.
Where do official weaknesses live? TypeSafe’s jev-1.13 jaggedness note — distractors, arithmetic, adversarial content. We do not invent more.
Where is the rest of the Sales pack? Start with Sales evaluation and Sales decision workflow. Cluster hub: Use cases.
Does Jev replace the CRM workflow engine? No. Salesforce-class workflows still own objects and SLAs. Jev labels messy notes so those workflows can fire. See vs CRM workflows.
Can Jev draft the follow-up email in this pack? Not here. Generate elsewhere; keep this call as typed decisions so you can audit next_motion.
What this page does not claim
- No invented win-rate or cycle-time lifts.
- Schema-safe next_motion ≠ the buyer named a real budget.
- Not official TypeSafe documentation.
- Official TypeSafe status, or that jev.pro issues API keys.
- That a schema-constrained answer is automatically factually correct.
Disclaimer
This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai.
Primary documentation: https://docs.typesafe.ai. Hub: Use cases.
Sources
Public TypeSafe or adjacent documentation only. No private claims.