Skip to content
Shonin
Beta

Support Triage Desk

Every support message classified and routed in under a second; refunds and angry customers always reach a person.

The split

LLM writes
Drafts replies for the specialist routes
System One decides
Intent, complexity, frustration, refund requested
Code executes
Order lookups, SLAs, assignment

Engine

One System One call per message (intent, complexity, frustration, refund requested) routes it to code, a specialist LLM, or a person.

Rulebook

What correct means here, and the mistakes we've already caught. It grows one job at a time.

  1. R01Refunds are prepared and approved by a person, always.
  2. R02A very angry customer reaches a person first, whatever the category.
  3. R03Order-status questions are answered by code from the order system, never by a model.
  4. R04Pidgin and local-language messages route as reliably as English, or go to a person.

Intake

  • Support channels: email, WhatsApp, in-app
  • Categories and who owns each
  • Refund and escalation policy
  • 500 past tickets to calibrate against
UNIT
Per 1,000 messages triaged
REVIEW LAYER
Weekly audit of 50 random routes; every misroute becomes a rulebook entry.
DELIVERY
Routing live in your helpdesk, plus a weekly misroute report.
TURNAROUND
5 days to live

How we find buyers

  • Fintech and e-commerce operators
  • Helpdesk vendors as partners
  • The Triage API for agent builders

Links

More like this