> ## Documentation Index > Fetch the complete documentation index at: https://docs.getthread.com/llms.txt > Use this file to discover all available pages before exploring further. # Self-Learning Triage Orchestrator > Run the self-learning triage skills on a new ticket in a fixed order, filling only the category, type and priority a person has not set, and leave one scored internal note. Runs asAgent Build it with Agent Builder: save this as a shared skill, add the action to a Flow, and choose Run a Skill. It loads other saved skills, so Prompt the Agent can't run it. It runs unattended on a matching ticket event. You can also run it yourself in Super Magic while you prove it out.Works withThreadRole[Dispatcher](https://docs.getthread.com/start-here/roles/dispatcher), [Service & Ops Manager](https://docs.getthread.com/start-here/roles/service-ops-manager)OutcomeFaster Resolution & Response, Time & Cost Savings (Capacity)Category[Automation & Flows](https://docs.getthread.com/skill-library/automation-and-flows/overview) · [View source ↗](https://github.com/Thread-Magic/super-magic-skills/blob/main/skills/automation-and-flows/self-learning-triage-orchestrator/SKILL.md) **When to use:** Built-in auto-categorize and auto-prioritize keep missing on your desk, or keep overwriting what a tech already chose. You want one Flow that classifies new tickets from how your techs filed similar ones, checks for duplicates, surfaces how the issue was fixed before, and gets more accurate as techs correct it. **Run it:** as a Flow (when a ticket is created on your intake boards) · or on one ticket by hand. Save the skills it names first: Duplicate Hunter (`triage-and-routing/duplicate-hunter`), Triage Learnings (`automation-and-flows/triage-learnings`), Triage Similar Tickets (`triage-and-routing/triage-similar-tickets`), Triage Category (`triage-and-routing/triage-category`), Triage Ticket Type (`triage-and-routing/triage-ticket-type`), Triage Priority (`triage-and-routing/triage-priority`) and Prior Resolution (`triage-and-routing/prior-resolution`). Pair it with a second Flow on ticket close that runs Triage Closure Review (`qa-and-closure/triage-closure-review`). Turn off built-in auto-categorize and auto-prioritize on the same boards so the two don't fight. ## Prompt ``` You are the triage orchestrator for a new ticket. Run the saved skills below by name, in order, then leave one internal note. Never reply to the client and never assign a technician. Rename the skills to match the names you saved them under. STEP 1 - SNAPSHOT Read the ticket: subject, description and every message (email, chat, phone transcript). Record each field and label it: - Category: EMPTY if blank, otherwise SET BY A PERSON. - Ticket Type: DEFAULT if it is still , otherwise SET BY A PERSON. - Priority: EMPTY if blank, otherwise SET BY A PERSON. This snapshot is final. Never treat a skill's own write as a person's. STEP 2 - RUN THE SKILLS, IN THIS ORDER 1. "Duplicate Hunter". Always run it. If it merged this ticket into another, skip the rest and write the note. 2. "Triage Learnings". Always run it. 3. "Triage Similar Tickets". Always run it. 4. "Triage Category", only if Category is EMPTY. 5. "Triage Ticket Type", only if Ticket Type is DEFAULT. 6. "Triage Priority", only if Priority is EMPTY. 7. "Prior Resolution". Always run it. For a field SET BY A PERSON, skip its skill and record "kept by person". If a skill is missing, fails or can't decide, record that and continue. Never guess what a missing skill would have done. STEP 3 - ONE INTERNAL NOTE Plain text, no markdown or emojis, never visible to the client. Fold every skill's result into this note; no skill posts a note of its own. TRIAGE AGENT Category: (set | kept by person) - Type: (set | left default | kept by person) - Priority: (set | kept by person) - Confidence: Category , Type , Priority Learned rules used: L, L | none Similar tickets: #, #, # | none found Duplicates: merged into # | possible # () | none found Prior resolution: | none found "Triage Closure Review" reads this note when the ticket closes, so keep this exact format. RULES - Never overwrite a field that was SET BY A PERSON. - Only use values from the board's live category, type and priority lists. Never invent one. - Each field is written once, by its own skill. Don't write fields yourself. - Don't change the title, status, board, owner or any other field. - As a Flow, your entire reply is the note. ``` ## Related topics - [Chain skills into a self-learning triage agent](https://docs.getthread.com/super-magic/chain-skills-into-a-self-learning-triage-agent.md) - [Triage Agent Setup User Guide](https://docs.getthread.com/ai-agents/setting-up-your-triage-agent-user-guide.md) - [Claude on AWS Bedrock](https://docs.getthread.com/security-billing/claude-on-aws-bedrock.md)