[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Triage new SysAid tickets with AI

> Set priority, category and assignee on new SysAid tickets by what each requester wrote, with a note for why. Runs daily, you keep the edge cases.

Source: https://cotlet.dev/integrations/sysaid-api-mcp-server/triage-new-service-records

New tickets pile up in the SysAid queue overnight, and each morning an agent opens them one by one to read the description, pick a priority and a category, and hand each to someone.

Cotlet does it in your own SysAid account with search\_service\_records, get\_service\_record, list\_service\_record\_notes, list\_field\_values, list\_agents\_and\_groups, update\_service\_record, assign\_service\_record and add\_note, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=sysaid) [All SysAid tools](https://cotlet.dev/integrations/sysaid-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can SysAid do this on its own?

SysAid sorts tickets with rules you define in advance (checked 23 Oct 2026). Routing rules assign records to agents or groups by conditions, priority rules set priority from agreement, company, department, user or asset, and Category Suggest proposes a category from the title and description. None of them sets priority and assignee together from what the requester wrote, and the API has no MCP server for an agent to do it.

## How you do it in SysAid today

1. In SysAid Spaces, the agent narrows the queue with the Assignees and Statuses quick filters above it, or with Filters, for example Status is Open.
2. The agent opens a record by clicking its ID and reads the description in the Journey.
3. Priority, Status and other fields can be edited in the queue grid itself and save automatically; the Template Designer sets which fields an agent may edit.
4. To hand a record over, the agent selects it and uses Assign in the action bar at the bottom of the queue, choosing a user, a group, or both.
5. If your admin requires an audit trail for manual priority changes, every priority change asks for a reason, so triage is slow by design.

## How to triage new SysAid tickets with AI

Prompt

```
Go through new SysAid tickets. Set priority and category from what the requester wrote, assign network problems to the Network group and access requests to IT Support, and leave an internal note with the reason. Leave unclear ones for me.
```

1. 01  
### Collect what is new  
search\_service\_records runs with the status your queue uses for new records and follows next\_cursor until it comes back empty, so a Monday backlog is triaged as one batch and not only its first page.
2. 02  
### Read before judging  
get\_service\_record brings the full description, requester, company, department and current priority. list\_service\_record\_notes shows whether an agent already wrote to the record, and such a record is left alone.
3. 03  
### Match your rules to real values  
list\_field\_values returns the priorities and categories your account has, and list\_agents\_and\_groups its groups and agents. A rule that names a group or category that does not exist is reported to you, not guessed.
4. 04  
### Set priority and category  
update\_service\_record sets both on the clear cases and adds the reason when your SysAid requires one. It sends nothing to anybody, so it does not wait for your OK.
5. 05  
### Assign  
assign\_service\_record hands the record to the group or agent your rule names. The assignee gets an instant message, so each call waits for your OK until you switch confirmation off for it.
6. 06  
### Leave the reason, skip what moved  
add\_note writes one internal line per record on why it got that priority and assignee. Before writing, the agent reads the record again; one that a colleague is editing is locked, so the write fails and is logged as already handled.

### What you get back

Example data

```
New tickets read: 14
Triaged 11:
- 4 to IT Support, Priority 3 (access and mailbox requests)
- 3 to Network, Priority 2 (VPN and Wi-Fi errors)
- 4 to IT Support, Priority 4 (how-to questions)
Left for you 3:
- #48244 mentions a data leak
- #48251 is one line, "it does not work"
```

### Other ways to ask

- Every hour, find tickets where the requester wrote "down" or "everyone" and raise them to Priority 1, then list them for me.
- Set the category of every uncategorized ticket from its description and change nothing else.
- Show me how you would triage today's new tickets as a table and write nothing to SysAid.
- Triage only unassigned tickets older than 2 hours.

## What SysAid allows, and what to know first

- SysAid runs routing rules by specificity: the more specific a rule is, the earlier it runs, so a rule you set by hand can be overridden by a more specific one.
- When a Category Driven template is enabled, the template decides the assignee and not the routing rule.
- SysAid applies priority rules in one of two ways, highest matching priority or first match holds, so a priority an agent sets can differ from what the rules would give.
- A SysAid note is internal unless the author shares it with the request user, and it holds up to 5,000 characters without emojis.
- Every field edit is recorded in the Journey, and status and assignee changes also show in the Highlights view.

assign\_service\_record and add\_note ask for your OK by default. To run it daily without you, switch confirmation off for those tools in your dashboard.

Sources: [SysAid Documentation: Working with the Service Record Queue](https://documentation.sysaid.com/docs/working-with-the-queue) · [SysAid Documentation: Routing Rules List](https://documentation.sysaid.com/docs/routing-rules-list) · [SysAid Documentation: Priorities](https://documentation.sysaid.com/docs/priorities) · [SysAid Documentation: Reading & Writing Notes](https://documentation.sysaid.com/docs/read-and-write-notes) · [SysAid Documentation: Category Suggest](https://documentation.sysaid.com/docs/ai-categorization)

## Call update\_service\_record from a script

curl

```
curl -X PATCH https://cotlet.dev/api/v1/sysaid/records/48230/service-record \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"priority":"Priority 2","category":"Access > VPN"}'
```

Example response

```
{
"id": 48230,
"title": "VPN drops every hour",
"status": "Open",
"priority": "Priority 2",
"impact": "Medium",
"category": "Access > VPN",
"modified_at": "2026-10-23T08:41:00Z"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is sysaid\_write → update\_service\_record. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/sysaid-api-mcp-server.md#automations)

## SysAid tools this automation uses

__Cotlet SysAid tools used to triage new SysAid tickets with AI__
| Tool | Parameters |
| ---------------------------- | ------------------------------------------------------------------------------------ |
| search\_service\_records | query, type, status, priority, assignee, created\_since, sort\_by, sort\_dir, cursor |
| get\_service\_record | record\_id |
| list\_service\_record\_notes | record\_id, cursor |
| list\_field\_values | field |
| list\_agents\_and\_groups | kind, query |
| update\_service\_record | record\_id, title, description, priority, impact, category, reason |
| assign\_service\_record | record\_id, assignee, group |
| add\_note | record\_id, body, share\_with\_requester |

[All 12 SysAid tools with descriptions](https://cotlet.dev/integrations/sysaid-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect SysAid to Cotlet?

Yes. You sign in to SysAid yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get SysAid once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More SysAid automations

- [Resolve solved SysAid tickets with AI](https://cotlet.dev/integrations/sysaid-api-mcp-server/resolve-solved-tickets.md)
- [Merge duplicate SysAid tickets with AI](https://cotlet.dev/integrations/sysaid-api-mcp-server/merge-duplicate-tickets.md)
- [SysAid API and MCP server: every tool](https://cotlet.dev/integrations/sysaid-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to SysAid.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with SysAid.

[Sign up free](https://cotlet.dev/app/signup?app=sysaid)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.