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
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.
| Decision | How serious is this complaint, and does it need a specialist route? |
|---|---|
| State Jev sees | Complaint text, channel, topic, prior contact count, any recorded adjustments. |
| Questions |
|
| First action code may take | Place the case in a queue with an SLA; a frontier model may draft an acknowledgement for a person to send. |
| Stays with a person | Sending any reply, every closure, anything involving conduct or safeguarding. |
| Measure first | Specialist cases found in the first pass; days to acknowledge; ombudsman escalations. |
| Microsoft surface | Dynamics 365 Customer Service or case list in Dataverse; Teams card for specialist handoff. |
| Out of scope | Auto-closing, auto-sending, deciding redress. |