Hi — I’m Abe. Small teams often have to answer three basic questions quickly: which desk should own this, how urgent is it, and does a billing message look like a duplicate-charge claim? I built Local ticket triage to make that first pass explicit.
Paste a support or invoice ticket and it returns:
- a queue suggestion (billing, technical, account, or other) with probabilities
- an ordinal urgency score from low to critical, with probabilities
- a “charged twice” strength from 0–1
The demo is intentionally local and narrow: no helpdesk integration, no shell access, and it is not a security product or firewall. The cards on the demo page are fixed fixtures from a local run, so the numbers are illustrative rather than a production-accuracy claim.
Private beta for people who handle support or billing queues and can say where this routing is useful — or misleading. Feedback on the labels, confidence display, and the “charged twice” signal is especially welcome.