[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)

# Resolve solved SysAid tickets with AI

> Close SysAid tickets once the requester wrote that the fix works, with the solution taken from the notes. Runs daily, you keep the unclear ones.

Source: https://cotlet.dev/integrations/sysaid-api-mcp-server/resolve-solved-tickets

Tickets sit in Pending after the fix because the requester answered with one line, and nobody goes back to write the solution and close them.

Cotlet does it in your own SysAid account with search\_service\_records, list\_service\_record\_notes, get\_service\_record and resolve\_service\_record, 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 has escalation rules that perform actions on service records when predefined criteria are met, and the API has a resolve endpoint (checked 23 Oct 2026). A rule matches fields and times, not what the requester wrote, so nothing reads the reply to see that the fix worked or writes the solution from the notes.

## How you do it in SysAid today

1. The agent filters the queue to the waiting status, for example Status is Pending, and opens each record.
2. In the Journey, the Highlights view lists notes, messages and status changes, so the agent can find the requester's last reply.
3. To resolve, the agent adds a Resolution card from the toolbar and fills in Status, Closure Information and Solution, the last two required.
4. Share with Request User is off by default, so the agent turns it on when the requester should read the solution, and can switch on Add to Knowledge Base.
5. Alternatively the agent changes the status to a closed one from the Status chip and clicks Resolve.

## How to resolve solved SysAid tickets with AI

Prompt

```
Find SysAid tickets in Pending where the requester wrote that it works now. Resolve each with a short solution from the notes and list the ones where the answer is unclear.
```

1. 01  
### List the waiting records  
search\_service\_records runs with the waiting status of your queue and sorts by oldest first, following next\_cursor to the end. Records created today are skipped, because the requester has had no time to answer.
2. 02  
### Find the last word  
list\_service\_record\_notes returns the notes oldest first. The agent resolves only when the last note is from the requester and says the issue is gone. A last note from an agent, or an unclear reply, puts the record on your list.
3. 03  
### Write the solution  
The solution is one or two sentences built from the agent's own notes, in the words of the fix, for example "Reinstalled the VPN client and reset the profile". get\_service\_record supplies the category for the closure information.
4. 04  
### Resolve  
resolve\_service\_record sets the solution, the closure information and a closed status. It waits for your OK by default, because closing can email the requester a survey link.
5. 05  
### Report what stayed open  
Records with no reply, a reply that says it still fails, or a status the agent cannot close are listed with a reason, so the queue does not hide them.

### What you get back

Example data

```
Pending records read: 9
Resolved 5, e.g. #48417 VPN client reinstalled, requester confirmed
Left for you 4:
- #48402 requester wrote "better but still slow"
- #48390 no reply since 3 days
```

### Other ways to ask

- Every Friday, resolve Pending tickets where the requester has not answered in 7 days and say so in the solution.
- Resolve confirmed tickets but keep Share with Request User off.
- List the Pending tickets where the requester answered, with the answer, and resolve nothing.

## What SysAid allows, and what to know first

- The SysAid Resolution tab requires Solution and Closure Information.
- Share with Request User is disabled by default on the Resolution tab, so a solution stays internal unless it is switched on.
- SysAid separates Solution, a short summary usually shared with the request user, from Resolution, a detailed technical description for other agents.
- When the survey is enabled under Settings > Service Desk > General, closing a record emails the request user a survey link.
- Agents with Edit permission can resolve a record, and agents with View permission can only read the resolution.

resolve\_service\_record asks for your OK by default. To run it daily without you, switch confirmation off for that tool in your dashboard.

Sources: [SysAid Documentation: Resolving a Service Record](https://documentation.sysaid.com/docs/resolve-a-service-record) · [SysAid Documentation: Survey Introduction](https://documentation.sysaid.com/docs/survey-introduction) · [SysAid Documentation: Escalation Rules](https://documentation.sysaid.com/docs/escalation-rules) · [SysAid Documentation: Service Record Journey](https://documentation.sysaid.com/docs/journey-docs)

## Call resolve\_service\_record from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/sysaid/records/48417/service-record/resolve \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"solution":"Reinstalled the VPN client and reset the profile. The requester confirmed the connection holds.","closure_information":"Solved On-site","share_with_requester":true}'
```

Example response

```
{
"id": 48417,
"status": "Closed",
"closure_information": "Solved On-site",
"shared_with_requester": true,
"resolved_at": "2026-10-23T09:05:00Z"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is sysaid\_write → resolve\_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 resolve solved SysAid tickets with AI__
| Tool | Parameters |
| ---------------------------- | ------------------------------------------------------------------------------------ |
| search\_service\_records | query, type, status, priority, assignee, created\_since, sort\_by, sort\_dir, cursor |
| list\_service\_record\_notes | record\_id, cursor |
| get\_service\_record | record\_id |
| resolve\_service\_record | record\_id, solution, closure\_information, status, 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

- [Triage new SysAid tickets with AI](https://cotlet.dev/integrations/sysaid-api-mcp-server/triage-new-service-records.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.