TriagePilot

TriagePilot helps service-desk agents turn the visible content of one ticket into explainable, policy-based classification and priority advice. After an explicit click, the extension reads the visible ticket title and text, or visible fields from a work queue. Processing happens entirely inside the extension. Ticket data is not sent to the publisher, analytics services, advertising networks, or other third parties. Core capabilities: - Distinguishes Incidents from Service Requests with separate deterministic policy paths. - Produces an exact P1-P4 recommendation or an honest range when decisive facts are missing. - Asks only a question that can still change a governed outcome. - Supports English, Dutch, and governed CRV terminology. - Shows source-backed evidence, policy rules, confidence as evidence coverage, and a copyable note. - Reviews visible work-queue rows locally for priority/type mismatches, SLA risk, and likely duplicates. - Can update one exact Halo priority path and one governed intake stage after confirmation. - Includes a read-only Halo readiness diagnostic and privacy-safe JSON export. TriagePilot is fully deterministic. It contains no generative model, OpenAI integration, API key, remote code, telemetry, advertising, or background browsing. The same ticket evidence, answers, rule version, and policy bundle always produce the same result. The extension requests temporary access to the active tab only after the user clicks its toolbar action or the scan button. It declares no persistent host permissions. Paste mode remains available when tab access is unavailable or inappropriate. Halo priority and workflow updates are deliberately conservative. They require the expected ticket, one unambiguous control or exact action, and visible confirmation. Availability depends on the organisation's Halo configuration and agent permissions. TriagePilot does not bulk-update tickets and does not declare a Major Incident automatically.