[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 Tidio support tickets by what the customer wrote

> Set priority, tag and department on new Tidio tickets by what each customer wrote, and leave unclear ones for you. Runs daily from Claude Code or n8n.

Source: https://cotlet.dev/integrations/tidio-api-mcp-server/triage-support-tickets

New email tickets land in the Unassigned folder in Tidio, and someone has to open each one, read it and decide who gets it and how urgent it is before any reply is written.

Cotlet does it in your own Tidio account with list\_tickets, get\_ticket, list\_operators and update\_ticket, called by your AI agent, an n8n workflow or a script.

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

Hosted · nothing to install or maintain

## Can Tidio do this on its own?

Tidio Workflows check a ticket's status, tag or assigned agent and can change the status, add a ticket tag or remove the assignee (checked 17 Oct 2026). They act on fixed conditions, not on what the customer wrote. The OpenAPI has an update ticket endpoint on Plus and Premium, and no official MCP server can call it. Nothing in Tidio reads a ticket and picks priority, department and tag from its content, which is the gap this job fills.

## How you do it in Tidio today

1. An operator opens the Inbox from the icon in the top-left corner of the Tidio menu bar and opens the Unassigned folder, one of the three default folders next to My open and Solved.
2. In each ticket, the top bar shows the current assignee, status and priority, and the operator changes whichever is wrong.
3. To send a ticket to a team, the operator picks a department from the Assignee button or the three-dots menu; only agents of that department then see it in Unassigned.
4. Under the Info tab, Add ticket tag attaches a tag from Settings > Tags, which the custom ticket views then filter on.
5. The same read-and-sort repeats for every new ticket, and a Monday backlog is the slowest part.

## How to triage Tidio support tickets by what the customer wrote

Prompt

```
Go through the Unassigned tickets in Tidio. Set the priority from what the customer wrote, put refund requests with the Billing department and add a tag, and leave anything unclear for me.
```

1. 01  
### Collect the unassigned queue  
list\_tickets runs on the unassigned folder and pages through the cursor until it ends, so a long backlog is triaged as one batch and not only its first page.
2. 02  
### Read each ticket  
get\_ticket brings the subject and the messages, so priority comes from what the customer wrote and not from the subject alone. A message that asks for a refund, a chargeback or a cancellation is a billing ticket.
3. 03  
### Find the right people  
list\_operators returns operators with their departments, so the agent assigns only to names and departments that exist in your account and never invents one.
4. 04  
### Apply the change, once  
update\_ticket sets priority, department and tags in one call per ticket. It changes nothing the customer sees, and a wrong call is undone by calling it again with the old values.
5. 05  
### Keep unclear tickets for you  
A ticket with no clear topic, a mixed question or a language the agent does not read stays in Unassigned with a one-line reason in the report.

### What you get back

Example data

```
Unassigned tickets: 14
Priority urgent 2 (site down, double charge)
Sent to Billing 4 and tagged refund
Sent to Support 6, priority normal
Left for you 2:
- #10491 "Question" (empty body)
- #10497 (mixes a refund and a feature request)
```

### Other ways to ask

- Every morning at 8, set priority on new tickets and show me a count per tag.
- Tag every ticket that mentions an order number with orders, and change nothing else.
- List tickets that are Pending for more than a week and tell me which customers went quiet.

## What Tidio allows, and what to know first

- A Tidio ticket has three statuses: Open, Pending and Solved. Pending means you wait for the customer, and a customer reply moves it back to Open.
- A ticket sent to a department shows in the Unassigned folder, and only agents of that department see it and can assign it to themselves.
- Ticket tags belong to the ticket thread only; customer tags belong to the contact, so triage tags do not leak onto the contact.
- The OpenAPI lists a ticket priority as low, normal or urgent, and a ticket status as open, pending or solved.

update\_ticket changes only your own Tidio data and reach no one else, so it runs without asking first.

Sources: [Tidio Help: Email (Ticketing)](https://help.tidio.com/hc/en-us/articles/5465389809948-Helpdesk-Ticketing) · [Tidio Help: Workflows](https://help.tidio.com/hc/en-us/articles/19937584118940-Workflows) · [Tidio Help: Custom ticket Views (Email)](https://help.tidio.com/hc/en-us/articles/12504280832668-Custom-Ticket-Views-Helpdesk) · [Tidio developers: Get tickets](https://developers.tidio.com/reference/get%5Ftickets.md)

## Call update\_ticket from a script

curl

```
curl -X PATCH https://cotlet.dev/api/v1/tidio/tickets/10477 \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"priority":"urgent","department":"Billing","add_tags":["refund"]}'
```

Example response

```
{
"ticket_id": 10477,
"status": "open",
"priority": "urgent",
"assignee": null,
"department": "Billing",
"tags": [
"refund"
]
}
```

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

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

## Tidio tools this automation uses

__Cotlet Tidio tools used to triage Tidio support tickets by what the customer wrote__
| Tool | Parameters |
| --------------- | --------------------------------------------------------------------------- |
| list\_tickets | folder, status, limit, cursor |
| get\_ticket | ticket\_id |
| list\_operators | none |
| update\_ticket | ticket\_id, status, priority, assignee, department, add\_tags, remove\_tags |

[All 14 Tidio tools with descriptions](https://cotlet.dev/integrations/tidio-api-mcp-server.md#tools)

## Frequently asked questions

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

Yes. You sign in to Tidio yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Tidio 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 Tidio automations

- [Reply to waiting Tidio tickets with AI](https://cotlet.dev/integrations/tidio-api-mcp-server/reply-to-support-tickets.md)
- [Update Tidio contact properties and tags in bulk](https://cotlet.dev/integrations/tidio-api-mcp-server/update-contact-properties.md)
- [Tidio API and MCP server: every tool](https://cotlet.dev/integrations/tidio-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Tidio.

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

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

---

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 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.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.