How to Use Claude to Triage IT Requests Before a Human Sees Them

Every IT request arriving pre-sorted, with a priority, a category, and a suggested first response already attached, is what triage looks like when Claude reads the queue first. Your team opens tickets that are ready to work instead of tickets that need ten minutes of reading before anyone can start.

Quick answer:

• Define a compact triage format: priority, category, and a one-sentence summary
• Test the prompt in the Claude Console until the output is consistent
• Wire it into your help desk with an automation rule that calls the Claude API on every new request

Verified against Jira Cloud automation documentation and the Anthropic Claude API on 2026-07-24.

Prerequisites

• A help desk that supports outbound web requests from automation rules. This guide uses Jira Service Management Cloud; the same pattern works in Zendesk, Freshservice, and HaloPSA.
• A Claude API key from the Claude Console
• Project admin access to create automation rules

Step 1: Define the Triage Output

Decide what a triaged ticket contains before writing any prompt. A format that covers most SMB help desks:

• Priority: Highest, High, Medium, or Low, matching your Jira priority scheme exactly
• Category: a short fixed list such as access, hardware, software, security, or other
• Summary: one sentence a technician can read in five seconds

Keep the category list short. Claude classifies reliably against five clear options and drifts against twenty vague ones.

Step 2: Create the API Key

1. Sign in to the Claude Console and open the API Keys page.
2. Select Create Key, name it after the automation (for example, jsm-triage), and copy the key once. It is not shown again.
3. Store it in your password manager. You will paste it into a hidden header value in Step 4.

Step 3: Test the Prompt Before Wiring Anything

In the Claude Console workbench, draft the system prompt and run your last ten real tickets through it. A working starting point:

You triage IT help desk tickets. Given a ticket subject and description, reply with exactly one line in this format: Priority|category|one-sentence summary. Priority is one of: Highest, High, Medium, Low. Category is one of: access, hardware, software, security, other. Output nothing else.

Set temperature to 0 so identical tickets triage identically. Adjust the prompt until all ten test tickets come back in the exact format with sensible priorities. The pipe-delimited single line matters: it is what the automation rule will split apart.

Step 4: Build the Automation Rule

1. In your service project, open Project settings → Automation and select Create rule.
2. Choose the trigger When: Work item created.
3. Add the action Send web request and configure it:
   • Web request URL: https://api.anthropic.com/v1/messages
   • HTTP method: POST
   • Headers: x-api-key (paste your key and mark the value Hidden), anthropic-version: 2023-06-01, and content-type: application/json
   • Web request body: Custom data, containing your model choice, max_tokens, the system prompt from Step 3, and a user message built from the smart values {{issue.summary}} and {{issue.description}}
4. Check Wait for response (the option reads "Delay execution of subsequent rule actions until we've received a response for this web request"). Without it, the response is empty when the next action runs.
5. Add the action Edit work item and set Priority to {{webResponse.body.content.first.text.split("|").get(0)}}.
6. Add the action Comment on work item with an internal note: Claude triage: {{webResponse.body.content.first.text}}.
7. Name the rule and select Turn it on.

Verify

• Create a test request describing a locked account. The ticket should pick up a sensible priority within seconds and carry an internal triage comment.
• Create a second test request that is clearly low stakes, such as a request for a second monitor, and confirm it triages to a lower priority than the first.
• Check the rule's audit log under Automation to confirm the web request returned a success status.

Troubleshooting

Priority field does not change: The value Claude returned does not exactly match a priority name in your scheme. Tighten the allowed list in the system prompt to your exact priority names.

The smart value resolves to nothing: The Wait for response option is unchecked, or the response was not JSON. Re-open the Send web request action and confirm both.

Claude adds explanation around the answer: Strengthen the final instruction to "Output nothing else." and re-test in the workbench before saving the rule.

Costs concern you: Triage calls are short. Set max_tokens low, use a small fast model, and review usage in the Claude Console after the first week.

Triage That Scales From Day One

This pattern is worth configuring for scale from the start, and if your queue is already busy with untriaged tickets, it is not too late to add it. ScaleIt builds AI triage like this into help desks for startups and SMBs as part of its managed IT plans, tuned to your priority scheme and escalation paths. If you would rather have it running this month than build it between other duties, book a free call and we will scope it with you.

Verified against Jira Service Management Cloud automation (Send web request, Edit work item) and the Anthropic Claude Messages API on 2026-07-24. Vendor docs: support.atlassian.com/cloud-automation, platform.claude.com/docs.