--- title: "Zendesk ticket priority planner" type: "skill" url: "https://useaiblocks.com/skills/zendesk-ticket-priority-planner" updated: "2026-11-03" first_published: "2026-10-25" job: "Help your customers" tested: true licence: "MIT" source: "https://github.com/composio-community/support-skills/tree/83382c4b055fc4e5b055044adb5bfb7585484c9a/zendesk-triage" instructions: "https://useaiblocks.com/skills/zendesk-ticket-priority-planner/SKILL.md" --- # Zendesk ticket priority planner > Sort your open Zendesk tickets into a priority list from P0 to P3, with type, age and response deadline status, so you know what to answer first. Link your Zendesk account and ask which tickets need attention first. It reads your open and pending tickets, then up to fifteen full threads. You get a queue from P0 to P3, a type for each ticket, and next steps. Free skill for the job "Help your customers" · Level: intermediate · Thinking: medium · Safety checked · Updated 2026-11-03 ## Links - Page: https://useaiblocks.com/skills/zendesk-ticket-priority-planner - Instructions (SKILL.md): https://useaiblocks.com/skills/zendesk-ticket-priority-planner/SKILL.md - All files (zip): https://useaiblocks.com/skills/zendesk-ticket-priority-planner.zip - JSON version: https://useaiblocks.com/skills/zendesk-ticket-priority-planner.json - In your AI: connect https://useaiblocks.com/mcp and ask "Use AI Blocks to get zendesk-ticket-priority-planner" ## What it does A Zendesk queue sorts by date, but the oldest ticket is not always the most urgent. This Zendesk ticket priority planner reads the tickets and ranks them by what is at stake. P0 is for outages, data loss, security problems and escalations from VIPs. P1 is for broken features, billing disputes and people who have written more than once. P2 and P3 hold questions, minor bugs, requests and feedback. Each ticket also gets a type, such as bug, billing, how-to, feature, account or integration. You see its age and whether it is near its response deadline. It reads the 15 most recent tickets in full, then ends with the next steps for the urgent ones. It does not reply or change tickets. ## What you give it - Your Zendesk account, linked through Composio - Open and pending tickets, read for you (up to 15 in full) - Your response targets or ticket due dates (optional) - Names of VIP customers, if you want them flagged (optional) ## What you get - Tickets ranked from P0 critical to P3 low - A type for each ticket - Each ticket's age and response deadline status - A short list of next steps for the urgent ones ## Example: what goes in and what comes out ### What goes in - Your Zendesk account, linked through Composio - Open and pending tickets, read for you (up to 15 in full) - Your response targets or due dates (optional) - Your VIP customer names (optional) ### Before you start - An AI that can run commands, with Composio CLI installed - A Zendesk account linked in Composio - Ticket text is sent through Composio, so check this suits your privacy rules ### What comes out - **P0 - Critical**: Outages, data loss, security issues and VIP escalations, with ID, subject, type, requester, age and deadline status. - **P1 - High**: Broken features, billing disputes and repeat contacts, in the same table. - **P2 - Medium / P3 - Low**: General questions, minor bugs, feature requests and feedback, in their own tables. - **Recommended Actions**: Specific next steps for the tickets that need attention first. ## Use it when - Your Zendesk queue has grown and you need to know what to answer first. - You start the day and want a ranked list instead of a long inbox. - A manager asks which open tickets are urgent right now. - You want to spot billing disputes and bugs hiding in the queue. ## Skip it when - You use Gorgias, Freshdesk or Zoho Desk. Use the Gorgias ticket priority planner, the Freshdesk ticket priority planner or the Zoho Desk ticket priority planner. - You have a pasted batch of emails, not a Zendesk queue. Use the Support ticket sorter. - You want to rate how upset one customer is. Use the Customer message tone and urgency reviewer. - You have only a few tickets. Use your Zendesk views and sort them by hand. ## How to use it 1. Check you have a Zendesk account, and a Composio account with its command line tool. Check your own plans for any cost. 2. Open an AI that can run commands and read skill files, such as Claude Code, and add the downloaded folder. 3. Ask it to run the Zendesk ticket priority planner. If it says Zendesk is not connected, run composio link zendesk and ask again. 4. Open the P0 tickets in Zendesk first. Check that each one is really urgent. 5. No command line? Paste up to fifteen tickets with their threads into your AI and ask it to follow the skill. You get the same dashboard. ## What to do next - [Support issue cause investigator](https://useaiblocks.com/skills/support-issue-cause-investigator): Support issue cause investigator - [Support ticket help article writer](https://useaiblocks.com/skills/solved-ticket-help-page-writer): Support ticket help article writer - [Escalation brief writer](https://useaiblocks.com/skills/escalation-brief-writer): Escalation brief writer ## Sources and credits - From Composio: https://github.com/composio-community/support-skills/tree/83382c4b055fc4e5b055044adb5bfb7585484c9a/zendesk-triage, shared under the MIT licence (original name: zendesk-triage). - [zendesk-triage skill](https://github.com/composio-community/support-skills/tree/83382c4b055fc4e5b055044adb5bfb7585484c9a/zendesk-triage), Composio: Copied under the MIT licence. We gave it a plain name. We added Before you start and After this sections that link to other AI Blocks steps. ## Instructions (SKILL.md) ## Zendesk Ticket Triage You are a support triage specialist. Pull open tickets from Zendesk, analyze them, and present a prioritized triage dashboard. ### Before you start - Live use needs an AI that can run commands (Bash), the Composio CLI, a Composio account, and your Zendesk account linked to it. Ticket text passes through Composio. Check your own plans for any cost. - If you cannot run commands, ask the user to paste up to 15 tickets with the full thread, requester, created time and any due date. Do Step 5 on that text and skip the Composio steps. - SLA status needs a due date or a response target. Use the due date in the ticket data, or the target the user gives. If there is neither, write "not available" in the SLA column. Never guess it. - Say how many tickets were open or pending and how many you read in full. ### Workflow #### Step 1: Discover tools Run `composio search "list open support tickets from Zendesk with priority and status" "get Zendesk ticket details with comments"` in Bash. Note the tool names it returns. #### Step 2: Get tool schemas Run `composio execute --get-schema` in Bash (in parallel) for each of the returned Zendesk tool slugs. Use the slugs from Step 1 in place of the angle-bracket names below. #### Step 3: Fetch open tickets Run `composio execute -d '{...open/pending, newest first...}'` in Bash to fetch recent open/pending tickets. Paginate if needed. If the CLI reports the toolkit is not connected, ask the user to run `composio link zendesk` and retry. #### Step 4: Get ticket details For the top 15 tickets, run `composio execute -d '{"ticket_id":""}'` in Bash as parallel calls to fetch full details including comments/conversations. #### Step 5: Triage and present Classify each ticket: **Priority:** - P0 CRITICAL: Service outage, data loss, security, VIP escalations - P1 HIGH: Feature broken, billing disputes, repeated contacts - P2 MEDIUM: General questions, minor bugs, how-to requests - P3 LOW: Feature requests, feedback, non-urgent inquiries **Categories:** BUG, BILLING, HOWTO, FEATURE, ACCOUNT, INTEGRATION, OTHER Only call a ticket a VIP if the ticket data or the user says so. ``` ## Zendesk Triage Dashboard ### P0 - Critical (X tickets) | # | Ticket ID | Subject | Category | Requester | Age | SLA Status | Summary | |---|-----------|---------|----------|-----------|-----|------------|---------| ### P1 - High (X tickets) ... ### P2 - Medium / P3 - Low ... ### Recommended Actions - [Specific next steps for urgent tickets] ``` This skill reads tickets and sorts them. It does not reply to tickets or change them. ### 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](https://useaiblocks.com/skills/support-issue-cause-investigator). It takes the audit report. - The [Support ticket help article writer](https://useaiblocks.com/skills/solved-ticket-help-page-writer). It takes the audit report. - The [Escalation brief writer](https://useaiblocks.com/skills/escalation-brief-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.