跳到主内容
智客 ZICQ

技能库 智客分类:数据与分析 Zendesk Automation

Zendesk Automation

通过Zendesk售票管理、路由和分析,自动实现客户支持工作流程

3941 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

通过Zendesk售票管理、路由和分析,自动实现客户支持工作流程

何时用

官方 description 未单独写出 Use when。按规范,代理会在用户任务与这段 description 的关键词匹配时激活本技能。

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Zendesk Automation、Core Workflows、1. Ticket Triage Pipeline、2. Routing Rules、3. Priority Matrix、Auto-Response Templates。 其中含规范建议的小节:分步指令。

文件分析

文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。

官方 description(原文)

Automate customer support workflows with Zendesk ticket management, routing, and analytics

Zendesk AutomationCore Workflows1. Ticket Triage Pipeline2. Routing Rules3. Priority MatrixAuto-Response TemplatesCommon Issue ResponsesTicket ManagementMacro LibraryBulk OperationsSLA ManagementSLA Policies

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
Zendesk Automation
description
Automate customer support workflows with Zendesk ticket management, routing, and analytics
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「Zendesk Automation」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-2e1577a7bccd0815-Zendesk-%E8%87%AA%E5%8A%A8%E5%8C%96.html
请存为 .cursor/skills/zendesk-automation/SKILL.md 或 .claude/skills/zendesk-automation/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/claude-office-skills/skills' --list

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版

name: Zendesk Automation description: Automate customer support workflows with Zendesk ticket management, routing, and analytics version: 1.0.0 author: Claude Office Skills category: support tags:

  • zendesk
  • helpdesk
  • tickets
  • customer-support
  • automation department: support models:
  • claude-3-opus
  • claude-3-sonnet
  • gpt-4 mcp: server: helpdesk-mcp tools:
    • zendesk_create_ticket
    • zendesk_update_ticket
    • zendesk_search
    • zendesk_macros capabilities:
  • Ticket creation and routing
  • Auto-response generation
  • SLA monitoring
  • Agent assignment input:
  • Support requests
  • Ticket data
  • Customer information
  • Priority criteria output:
  • Ticket responses
  • Routing decisions
  • Performance reports
  • SLA dashboards languages:
  • en
  • zh related_skills:
  • slack-workflows
  • customer-success
  • intercom-automation

Zendesk Automation

Comprehensive skill for automating Zendesk support workflows and ticket management.

Core Workflows

1. Ticket Triage Pipeline

INCOMING TICKET FLOW:
┌─────────────────┐
│  New Ticket     │
└────────┬────────┘
         ▼
┌─────────────────┐
│  AI Analysis    │
│  - Intent       │
│  - Sentiment    │
│  - Urgency      │
└────────┬────────┘
         ▼
┌─────────────────┐
│  Categorize     │
│  - Type         │
│  - Product      │
│  - Skill needed │
└────────┬────────┘
         ▼
┌─────────────────┐
│  Route & Assign │
│  - Team         │
│  - Agent        │
│  - Priority     │
└────────┬────────┘
         ▼
┌─────────────────┐
│  Auto-Response  │
│  (if applicable)│
└─────────────────┘

2. Routing Rules

routing_rules:
  - name: billing_issues
    conditions:
      - field: subject
        contains: ["billing", "invoice", "charge", "refund", "payment"]
      - field: tags
        includes: ["billing"]
    actions:
      - set_group: billing_team
      - set_priority: high
      - add_tags: ["billing_routed"]
  
  - name: technical_support
    conditions:
      - field: subject
        contains: ["error", "bug", "not working", "crash"]
      - field: product
        equals: "software"
    actions:
      - set_group: tech_support
      - set_priority: normal
      - add_tags: ["technical"]
  
  - name: enterprise_escalation
    conditions:
      - field: organization
        tier: enterprise
      - field: priority
        equals: urgent
    actions:
      - set_group: enterprise_team
      - set_priority: urgent
      - notify: slack_channel

3. Priority Matrix

| Customer Tier | Issue Type | Response SLA | Resolution SLA | |--------------|------------|--------------|----------------| | Enterprise | Critical | 15 minutes | 4 hours | | Enterprise | High | 1 hour | 8 hours | | Business | Critical | 1 hour | 8 hours | | Business | Normal | 4 hours | 24 hours | | Standard | All | 8 hours | 48 hours |

Auto-Response Templates

Common Issue Responses

auto_responses:
  password_reset:
    trigger:
      keywords: ["password", "reset", "forgot", "login"]
    response: |
      Hi {{ticket.requester.name}},
      
      I understand you're having trouble accessing your account. 
      Here's how to reset your password:
      
      1. Go to {{settings.login_url}}/forgot-password
      2. Enter your email address
      3. Check your inbox for the reset link
      4. Create a new password
      
      If you don't receive the email within 5 minutes, 
      please check your spam folder.
      
      Let me know if you need any further assistance!
    
    actions:
      - add_tags: ["auto_replied", "password_reset"]
      - set_status: pending

  shipping_inquiry:
    trigger:
      keywords: ["shipping", "tracking", "delivery", "order status"]
    response: |
      Hi {{ticket.requester.name}},
      
      Thanks for reaching out about your order!
      
      I've looked up your recent order and here's the status:
      {{#if order.tracking_number}}
      - Order #: {{order.id}}
      - Status: {{order.status}}
      - Tracking: {{order.tracking_number}}
      - Estimated Delivery: {{order.estimated_delivery}}
      {{else}}
      Your order is being processed and tracking information 
      will be available within 24 hours.
      {{/if}}
      
      Is there anything else I can help with?

Ticket Management

Macro Library

macros:
  - name: request_more_info
    actions:
      - add_comment: |
          Thank you for contacting us. To better assist you, 
          could you please provide:
          1. Your account email
          2. Steps to reproduce the issue
          3. Any error messages you're seeing
          4. Screenshots if possible
      - set_status: pending
      - add_tags: ["awaiting_info"]

  - name: escalate_to_engineering
    actions:
      - add_internal_note: "Escalated to engineering team"
      - set_group: engineering
      - set_priority: high
      - add_tags: ["escalated", "engineering"]
      - notify: engineering_slack

  - name: close_resolved
    actions:
      - add_comment: |
          I'm glad we could resolve this for you! 
          
          If you have any other questions, feel free to 
          reach out anytime. We're here to help.
          
          Have a great day!
      - set_status: solved
      - add_tags: ["resolved"]

Bulk Operations

bulk_actions:
  - name: close_stale_tickets
    schedule: "0 0 * * *"  # Daily
    conditions:
      - status: pending
      - last_update_days: 7
    actions:
      - add_comment: "Closing due to no response. Please reopen if needed."
      - set_status: solved
      - add_tags: ["auto_closed"]

  - name: escalate_breaching_sla
    schedule: "*/15 * * * *"  # Every 15 min
    conditions:
      - sla_breach_in_minutes: 30
    actions:
      - set_priority: urgent
      - notify: team_lead
      - add_tags: ["sla_at_risk"]

SLA Management

SLA Policies

sla_policies:
  - name: enterprise_sla
    conditions:
      organization_tag: enterprise
    targets:
      first_reply:
        urgent: 15  # minutes
        high: 60
        normal: 240
      resolution:
        urgent: 240
        high: 480
        normal: 1440

  - name: standard_sla
    conditions:
      default: true
    targets:
      first_reply:
        urgent: 60
        high: 240
        normal: 480
      resolution:
        urgent: 480
        high: 1440
        normal: 2880

SLA Dashboard

SLA PERFORMANCE - THIS WEEK
═══════════════════════════════════════

First Reply SLA:
Enterprise  ████████████████████ 98% ✓
Business    ██████████████████░░ 94% ✓
Standard    █████████████████░░░ 89% ⚠

Resolution SLA:
Enterprise  ████████████████████ 96% ✓
Business    █████████████████░░░ 91% ✓
Standard    ████████████████░░░░ 85% ⚠

TICKETS AT RISK:
┌──────────┬──────────┬───────────┐
│ Ticket   │ Customer │ Time Left │
├──────────┼──────────┼───────────┤
│ #45231   │ Acme Corp│ 12 min    │
│ #45198   │ TechStart│ 28 min    │
│ #45156   │ DataFlow │ 45 min    │
└──────────┴──────────┴───────────┘

AI-Powered Features

Sentiment Analysis

sentiment_analysis:
  enabled: true
  actions:
    negative:
      - add_tags: ["negative_sentiment"]
      - set_priority: +1  # Increase priority
      - notify: team_lead
    
    frustrated:
      - add_tags: ["frustrated_customer"]
      - route_to: senior_agents
      - add_internal_note: "Customer appears frustrated"

Intent Detection

intent_detection:
  categories:
    - name: billing_inquiry
      keywords: ["charge", "invoice", "refund", "bill"]
      confidence_threshold: 0.8
    
    - name: technical_issue
      keywords: ["error", "bug", "broken", "crash"]
      confidence_threshold: 0.75
    
    - name: feature_request
      keywords: ["wish", "would be nice", "suggest", "feature"]
      confidence_threshold: 0.7
    
    - name: cancellation
      keywords: ["cancel", "stop", "end subscription"]
      confidence_threshold: 0.85
      actions:
        - route_to: retention_team
        - set_priority: high

Integration Workflows

Slack Integration

slack_integration:
  notifications:
    - trigger: new_urgent_ticket
      channel: "#support-urgent"
      message: "🚨 New urgent ticket: {{ticket.subject}}"
    
    - trigger: sla_warning
      channel: "#support-alerts"
      message: "⚠️ Ticket #{{ticket.id}} approaching SLA breach"
    
    - trigger: negative_csat
      channel: "#support-feedback"
      message: "📉 Low CSAT received for ticket #{{ticket.id}}"

JIRA Integration

jira_integration:
  sync_rules:
    - zendesk_tag: bug_confirmed
      create_jira:
        project: DEV
        issue_type: Bug
        priority_map:
          urgent: Highest
          high: High
          normal: Medium
        sync_fields:
          - description
          - attachments
        link_back: true

Analytics & Reporting

Key Metrics

SUPPORT METRICS DASHBOARD
═══════════════════════════════════════

Volume:
Today's Tickets: 156 (+12% vs avg)
Open Tickets: 234
Backlog: 45

Performance:
Avg First Reply: 42 min (target: 60 min) ✓
Avg Resolution: 4.2 hrs (target: 8 hrs) ✓
One-Touch Resolution: 34%

Satisfaction:
CSAT Score: 4.6/5.0 ⭐
NPS: +45
Response Quality: 92%

Agent Performance:
┌────────────┬────────┬──────────┬──────┐
│ Agent      │ Solved │ Avg Time │ CSAT │
├────────────┼────────┼──────────┼──────┤
│ Sarah      │ 28     │ 3.1 hrs  │ 4.8  │
│ Mike       │ 25     │ 3.5 hrs  │ 4.7  │
│ Lisa       │ 22     │ 4.0 hrs  │ 4.6  │
└────────────┴────────┴──────────┴──────┘

Best Practices

  1. Quick First Response: Acknowledge tickets quickly, even if resolution takes longer
  2. Use Macros Wisely: Personalize templated responses
  3. Tag Consistently: Enable better routing and reporting
  4. Monitor SLAs: Set up alerts before breaches
  5. Capture Feedback: Send CSAT surveys after resolution
  6. Regular Training: Update agents on common issues

相关技能

数据与分析

Marketing Skills

TL; DR:23个营销剧本(CRO,SEO,拷贝,分析,实验,定价,发布,广告,社交). 用于快速获取清单+副本/粘贴可交付品.

数据与分析

Crypto & Stock Market Data (Node.js)

免费等级不需要 API 关键值 。 专业级别的密码货币和股票市场数据集成,用于实时价格、公司概况和全球分析。 由Node.js提供动力,外部依赖性为零.

数据与分析

Azure Storage

Azure存储服务包括Blob存储,文件共享,等式存储,表存储,和数据湖. 解答关于存储访问级别(热,凉,冷,存档),何时使用每个级别,以及级别比较的问题. 提供对象存储,SMB文件共享,async消息,NoSQL密钥-值,和大数据分析. 包括生命周期管理。 USE FOR: b…

数据与分析

Azure Kusto

Azure Data Explorer(Kusto/ADX)中使用KQL进行日志分析,遥测和时间序列分析的查询并分析数据. When: KQL 查询, Kusto 数据库查询, Azure Data Explorer, ADX 集群, 日志分析, 时间序列数据, IoT 遥测, …