Zoho Desk ticket priority planner

What it does

Your Zoho Desk queue fills up and everything looks urgent. This Zoho Desk ticket sorter reads the open tickets, opens the 15 newest ones in full, and ranks them so an outage does not sit behind a feature request. Each ticket gets a priority from P0 (critical) to P3 (low) and a type: bug, billing, question, feature request, account or other. The list is grouped by priority, and every row shows the department, the contact and how long the ticket has waited. It ends with next steps for the urgent ones. The skill only reads. It does not reply to, close or change any ticket. It reaches Zoho Desk through Composio, a separate service, so the ticket text passes through it.

What goes in and out

You give it

• Your Zoho Desk account, linked through Composio
• Your open tickets, which your AI reads for you
• A department to focus on (optional)

You get

• A queue grouped from P0 critical to P3 low
• Each ticket tagged as bug, billing, question, feature request, account or other
• Department, contact and age for every ticket
• A short list of next steps for the urgent tickets

How the task works

• Find the right tools. Your AI searches Composio for the Zoho Desk actions that list tickets and read one ticket with its threads.
• Fetch open tickets. It pulls your open tickets, newest first, and tells you to link Zoho Desk if it is not connected.
• Read 15 in full. It opens the full thread for up to 15 tickets so it judges the message, not just the subject.
• Rank and tag. Each ticket gets a priority from P0 to P3 and a type such as bug, billing or question.
• Show the queue. It lists tickets by priority with department, contact and age, then adds next steps for urgent ones.

Full instructions

• Check you have a Zoho Desk account and a Composio account with its command line tool. Composio is a separate service, so check its current plan and what it costs.
• Open an AI that can run commands and read skill files, such as Claude Code. Add the downloaded folder.
• Ask it to run the Zoho Desk ticket priority planner.
• If it says Zoho Desk is not connected, run composio link zoho-desk in your terminal and ask again.
• Open the P0 and P1 tickets in Zoho Desk and check them against the list before you act.
• No command tool? Paste up to 15 tickets with their threads into your AI and ask for the same grouping.

Words used in this task

• Composio: A separate service that links your AI to apps such as Zoho Desk. Your ticket text passes through it.
• Command line tool: A program you control by typing commands, not by clicking.

Full instruction file

Zoho Desk Triage

You are a support triage specialist. Pull open tickets from Zoho Desk, classify them, and present a prioritized view.

Before you start

• This skill reads tickets through the Composio command line tool (composio). It needs a Composio account with Zoho Desk linked. Composio is a separate service, and ticket text passes through it. Tell the user this once, and let them stop if that does not fit their privacy rules.
• This skill only reads. Never reply to, assign, close or edit a ticket. If the user asks for a change, show what you would do and wait for their yes.
• Optional: the user may name one department to focus on. If they do, keep only that department's tickets.
• No composio command in this environment? Do not guess ticket data. Ask the user to paste up to 15 tickets with their message threads, then run Steps 3 and 4 on the pasted text.

Workflow

Step 1: Discover tools

Run composio search "list open tickets from Zoho Desk" "get Zoho Desk ticket details with threads" in Bash. Pick the tool that lists tickets and the tool that gets one ticket with its threads. The search returns real tool slugs. Use those wherever a step below shows <SLUG>, <LIST_TICKETS_SLUG> or <GET_TICKET_SLUG>.

Step 2: Get tool schemas and fetch tickets

Run composio execute <SLUG> --get-schema in Bash (in parallel) for each of the returned Zoho Desk slugs, then run composio execute <LIST_TICKETS_SLUG> -d '{...open, sort by creation date...}' in Bash to fetch open tickets, newest first. Fill the {...} from the schema you just read. If the CLI reports the toolkit is not connected, ask the user to run composio link zoho-desk and retry. If there are no open tickets, say so and stop.

Step 3: Get details and classify

Run composio execute <GET_TICKET_SLUG> -d '{"ticket_id":"<ID>"}' in Bash as parallel calls for the top 15 tickets. If there are more than 15 open tickets, say how many you did not read in full and list them by subject at the end. Classify each of the 15:

Priority: P0 Critical, P1 High, P2 Medium, P3 Low Categories: Bug, Billing, Question, Feature Request, Account, Other

Use this as a guide. P0 is an outage, data loss or a security problem. P1 is a broken feature, a billing problem or an angry escalation. P2 is an everyday question or a small bug. P3 is a feature request or general feedback. Zoho Desk's own priority field is a signal, not the answer. Judge the message itself.

Work only from what the tickets say. If a field is missing, such as the department or the contact, write "not shown" instead of guessing. Work out age from the creation date.

Step 4: Present

## Zoho Desk Triage Dashboard

### P0 - Critical (X tickets)
| # | Ticket ID | Subject | Category | Contact | Department | Age | Summary |
|---|-----------|---------|----------|---------|------------|-----|---------|

### P1 / P2 / P3
...

### Recommended Actions
- [Next steps for urgent tickets]

Keep each Summary to one line. Under Recommended Actions, give a next step for every P0 and P1 ticket, such as who should answer and what to check first. End by telling the user to open the P0 and P1 tickets in Zoho Desk and check them before acting.

After this

When you've handed it back, suggest what they could do next in one short question. It's a suggestion: if they're done, that's fine. Offer these, and say they can type their own:

• The Support issue cause investigator. It takes the audit report.
• The Escalation brief writer. It takes the audit report.
• The Support ticket help article writer. It takes the audit report. If they pick one and that skill is added here, carry straight on with what you just made. If not, give the link and say what to bring.