Small decisions. Interesting possibilities.Submit contentSubmit

How it uses Jev

The call coach transcribes a live sales conversation in the browser and sends the recent transcript to Jev after each sentence. Jev returns a next-action Choice, a buying-stage Score, and seven Noul signals; local decision code applies confidence, smoothing, and hysteresis settings to display coaching guidance.

What Jev decides

Illustrative next-action questionExample answers · not a recorded Jev response · Source ↗
Question 1 · next best action
YOUR APP
INSTRUCTION

Choose the sales rep’s next action based on the customer’s most recent transcript statements.

STATE

The request state contains `sales_call_transcript`, populated with the recent transcript turns. No particular call transcript or observed answer is claimed.

JEV · CHOICE
  1. send_pricing
  2. book_demo
  3. loop_in_decision_maker
  4. handle_objection
  5. send_proposal
  6. ask_discovery_question
  7. nurture_follow_up
  8. no_action

App workflow

  1. Capture and transcribe speech

    Use browser speech recognition to produce a shared transcript for the call.

  2. Request call judgments

    Send the recent conversation turns to Jev for next action, buying stage, and signal assessments.

  3. Apply local coaching rules

    Use confidence thresholds, smoothing, and hysteresis to stabilize the decision and choose matching playbook guidance.

  4. Show the rep what to do next

    Display the action and confidence in the call-coach interface; the README limits the request to the latest 40 turns.

Why it is interesting

It uses a single structured request to produce several kinds of sales-call judgments, while a separate playbook maps decision keys to coaching tips. The user remains aware that browser speech recognition and conversation text are sent to external services.