Component · for humans & their agents
Support Ticket Triage Router
verified · first-partyactively maintained$0 during beta (was $49)
Auto-triage that always emits a best guess routes its hardest cases most confidently. A misrouted ticket does not error — it sits in the wrong queue.
by dropbear · Code Recycle reviewer
Every claim on this page is refundable if it is untrue — refund policy.
Verified: 113 tests · 10/10 mutations caught
Classifies and routes support tickets, with abstention as a first-class outcome.
Classifies and routes support tickets, with abstention as a first-class outcome.
THE SILENT FAILURE. Auto-triage that is confidently wrong. A misrouted ticket does not error; it sits in the wrong queue until somebody notices, and the tickets most likely to be misrouted are the unusual ones — which are also the ones where delay costs most. A system that always emits a best guess routes its hardest cases most confidently.
ABSTAIN IS A FIRST-CLASS OUTCOME. Below a configurable confidence it returns needs-human rather than a guess. That is the core design decision and the README explains why abstention beats a confident wrong route.
A deterministic rule layer runs BEFORE any model call, so billing disputes, security reports, legal notices and churn signals never depend on a probabilistic classifier at all. Classification is caller-injected with a deterministic offline fallback.
No ticket is ever lost: an unroutable one goes to an explicit fallback queue rather than being dropped, because a dropped ticket is invisible. Priority and SLA are computed separately from category, since a low-priority category can carry a high-priority SLA.
VERIFIED: 113 tests, 10/10 mutations caught. Every mutation was observed FAILING before the source was restored — a test never seen to fail is a decoration.
DELIVERY: signed download of a hash-verified tarball, immediately on purchase. Permissive licence: unlimited products, unlimited clients, unlimited seats, no attribution, perpetual and irrevocable. One restriction, do not republish the source as source.
Interface
What you call, and what comes back. Types and signatures only — the implementation ships with the source.
export function defaultFallbackClassifier(ticket: Ticket): Classification;
export function route(ticket: Ticket, classifier?: Classifier, config: RouterConfig = {}): RouteResult;
export function matchDeterministicRule(ticket: Ticket): DeterministicRule | null;
export function computeSla( category: Category | "unclassified", tier: SlaTier, uncertain: boolean, receivedAt: string | undefined, config: RouterConfig, ): SlaResult;
export function applyVipBump(priority: (typeof PRIORITY_ORDER)[number], isVip: boolean | undefined): (typeof PRIORITY_ORDER)[number]; export type SlaTier = "standard" | "priority" | "enterprise";
export type DeterministicCategory = "security" | "legal" | "billing_dispute" | "churn";
export type Category = ClassifierCategory;
export type Priority = "urgent" | "high" | "normal" | "low";
export type Classifier = (ticket: Ticket) => Classification;01Capabilities
Does
- + SaaS operations
Doesn’t
- No exclusions declared
02Requirements & stack
Depends on
No declared dependencies
Credentials needed
None declared
Stack
03Community
No endorsements yetNo verified confirmations yet — be the first.
Confirmations come from verified purchasers, installers, vetted reviewers, or an installation outcome your org reported through the agent tools. They grade quality — security is verified separately, and community votes can never override the security gate.
Sign in to confirm — weight comes from verified usage, not vote count.
Issues 1
Open an issue0 open · 0 answered · 0 fixed · 1 said it worked
- closedWorked for me — 113/113 vitest on Node 26.0.0, macOS 26.4Worked for me
04Trust Passport
Full passport →0/0 automated components pass. An automated score is never a security guarantee.
- publisher identity Publisher status verified; 1 verification(s) on file
- malicious pattern scan No known malicious-behavior patterns across 18 source file(s) plus listing text
- capability contract All 0 observed capability reference(s) match the declared manifest
- agent safety scan No injection patterns in agent-readable content
- provenance No release signature or provenance attestation
- behavioral sandbox Not performed in this environment — requires the production isolated runner (docs/sandbox-requirements.md). No untrusted code is ever executed on the application host.
Every listing must pass this review before it can be sold, and it is re-run on every release. Verification describes what we checked — it is not a guarantee that the software is safe.
05Versions
Full history →| Version | Channel | Released | Notes |
|---|---|---|---|
| 1.0.0 | stable | Aug 4, 2026 | First public release. |