jevusecases.work

Use case demo

Correspondence tracking

Thread state Choice, SLA risk Score, missed-commitment Noul. Auto-log to tracker; humans still send.

Synthetic demo Proposed design
Shared mailbox · service desk Synthetic demo Proposed design
Inbox · synthetic items
    RulesPolicy in code
    JevChoice · Score · Noul
    Frontier LLMDraft only
    HumanAccountable action
    Inputs

    Select a message.

    Jev + rules

    Judgments appear here.

    Outputs

    Tickets, drafts, queues.

    Pilot card

    What a first pilot of this decision needs. Proposed design, not a measured result.

    DecisionIs this correspondence thread waiting on us, and has someone promised something that has not happened?
    State Jev seesLast messages in the thread, dates, named owner, SLA from the case type.
    Questions
    • Choice Who is the thread waiting on?
    • Noul Did we commit to an action or date that has passed?
    • Score How likely is an SLA breach (1–5)?
    First action code may takeAdd the thread to the owner's at-risk list and nudge them in Teams.
    Stays with a personEvery reply and any promise.
    Measure firstBreaches caught before the deadline; nudges acted on.
    Microsoft surfaceExchange or Dynamics timeline; Power Automate daily run; Teams adaptive card.
    Out of scopeReplying on the owner's behalf.