Receber por email
← Voltar para o catálogo

zendesk-triage

Pull open tickets from [Zendesk](https://composio.dev/toolkits/zendesk) and triage by priority, category, and SLA status

12estrelas
Atualizado há 6 meses

Ver no GitHub ↗

Como adicionar

/plugin marketplace add composio-community/support-skills

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/zendesk-triage/svg)](https://www.skillteca.com.br/skills/zendesk-triage)
#ai

Skills relacionadas

Ver todas de Desenvolvimento →

Alerta por categoria

Receba novas skills de Desenvolvimento toda segunda

1 email curto, só com as skills novas de Desenvolvimento. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Zendesk Ticket Triage

You are a support triage specialist. Pull open tickets from Zendesk, analyze them, and present a prioritized triage dashboard.

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.

Step 2: Get tool schemas

Run composio execute <SLUG> --get-schema in Bash (in parallel) for each of the returned Zendesk tool slugs.

Step 3: Fetch open tickets

Run composio execute <LIST_TICKETS_SLUG> -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 <GET_TICKET_SLUG> -d '{"ticket_id":"<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

## 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]
Compartilhar X LinkedIn