Use case demo

Complaints

Tone, trauma-sensitive cues and a closed Choice of acknowledge / escalate / specialist. Never auto-close. Frontier may draft; humans 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.

    DecisionHow serious is this complaint, and does it need a specialist route?
    State Jev seesComplaint text, channel, topic, prior contact count, any recorded adjustments.
    Questions
    • Score How severe is the complaint (1–5)?
    • Noul Does the text contain cues that call for a trauma-informed response?
    • Choice Acknowledge, escalate or send to a specialist team?
    First action code may takePlace the case in a queue with an SLA; a frontier model may draft an acknowledgement for a person to send.
    Stays with a personSending any reply, every closure, anything involving conduct or safeguarding.
    Measure firstSpecialist cases found in the first pass; days to acknowledge; ombudsman escalations.
    Microsoft surfaceDynamics 365 Customer Service or case list in Dataverse; Teams card for specialist handoff.
    Out of scopeAuto-closing, auto-sending, deciding redress.