Token导航 LogoToken导航

Agent Skill · 研究检索

customer-support-integration(客户支持集成)

customer-support-integration 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

customer-support-integration 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 56,028。

总安装 465周安装 19GitHub Stars 19下载 150核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:customer-support-integration(客户支持集成)
来源仓库:https://github.com/finsilabs/awesome-ecommerce-skills
仓库路径:skills/customer-support-integration
安装命令:
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill customer-support-integration
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill customer-support-integration

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

客户支持集成技能连接帮助台系统与电商/CRM 平台,自动填充客户上下文。适用于 Shopify、Zendesk 等生态,减少客服切换系统造成的效率损失。自动关联订单历史、退款记录与购买偏好至每张支持工单。推荐使用 Gorgias 等原生集成方案,定制开发仅用于深度双向同步。

需配置 API 密钥并测试数据映射准确性,避免信息错乱。

来源仓库内路径:skills/customer-support-integration

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill cus…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

customer-support-integration 怎么安装?

在终端执行 npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill customer-supp…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

customer-support-integration 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

customer-support-integration 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

customer-support-integration 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

customer-support-integration 用的人多吗?

公开数据是累计安装 465 次,近一周安装 19 次,下载 150 次,GitHub 19 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

customer-support-integration 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
customer-support-integration

客户支持集成 · 本页

46519需要联网未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Customer Support Integration

Overview

Connecting your helpdesk to your store automatically surfaces order history, tracking information, and customer spend inside every support ticket — reducing average handle time by 40–60% because agents don't switch between systems. For Shopify, Gorgias is the purpose-built helpdesk that's native to the platform. For other platforms and for Zendesk/Intercom users, dedicated integration apps connect the systems. Only build a custom integration if you need deep two-way automation (auto-create tickets from order events, VIP routing, CSAT sync back to CRM) that off-the-shelf apps don't provide.

When to Use This Skill

  • When support agents repeatedly ask customers for their order number because it doesn't auto-populate in the ticket
  • When implementing Zendesk Sunshine Apps or Intercom Canvas Kit to show order details inside the agent interface
  • When automating ticket creation from order events (failed delivery, fraud hold, backorder)
  • When routing tickets by order value to prioritize VIP customers
  • When syncing support CSAT scores back to your CRM for customer health scoring

Core Instructions

Step 1: Determine platform and choose the right helpdesk

PlatformBest HelpdeskWhy
ShopifyGorgiasPurpose-built for Shopify; deep order data access, macro variables that pull order info, 1-click actions (refund, cancel, reorder) from within the ticket
ShopifyZendeskGood for teams that already use Zendesk; install the Shopify app for Zendesk from the App Store
WooCommerceGorgias or FreshdeskGorgias supports WooCommerce; Freshdesk + WooCommerce plugin for teams on Freshdesk
BigCommerceGorgias or ZendeskBoth have BigCommerce integrations in their app marketplaces
Custom / HeadlessZendesk or Intercom with custom integrationBuild a sidebar app to inject order context into tickets

Step 2: Platform-specific setup


Shopify

Option A: Gorgias (recommended for Shopify)

Gorgias is the most widely-used Shopify support helpdesk with the deepest platform integration.

  1. Install Gorgias from the Shopify App Store
  2. Authorize Gorgias to access your Shopify store data
  3. Gorgias automatically pulls order history, customer details, and shipping status into every ticket when a customer emails from the address on their Shopify account

What Gorgias shows agents automatically:

  • Customer name, email, total spent, order count
  • All past orders with status, items, and tracking
  • Live chat history across all channels

Setting up automation rules:

  1. Go to Gorgias → Automation → Rules
  2. Create rules like:

- Auto-tag tickets with "VIP" when customer lifetime value > $500 - Auto-assign VIP tickets to a senior support team - Auto-reply with order status when ticket contains "where is my order"

1-click actions from within Gorgias:

  • Refund, cancel, or duplicate an order directly from the ticket sidebar
  • Apply discount codes to orders without leaving Gorgias
  • Create a draft order for a replacement

Gorgias macros (template responses with dynamic variables):

  • Create macros that pull in order data automatically: Your order {{order.name}} is currently {{order.fulfillment_status}}
  • Go to Settings → Macros to create and manage macros

WooCommerce

Gorgias for WooCommerce:

  1. Install the Gorgias WooCommerce plugin from WordPress.org or connect via Gorgias integrations
  2. Connect your WooCommerce store — Gorgias pulls order history automatically

Freshdesk for WooCommerce:

  1. Install Freshdesk Help Desk for WooCommerce from the WordPress plugin directory
  2. The plugin creates Freshdesk tickets from WooCommerce order events
  3. Freshdesk agents see customer order details in the ticket sidebar via the integration

Manual integration with Zendesk:

  1. Install Zendesk for WooCommerce from the Zendesk App Marketplace
  2. Agents can search for customers by email and see their order history in the ticket sidebar

BigCommerce

Gorgias for BigCommerce:

  1. Install Gorgias from the BigCommerce App Marketplace
  2. Connect your store — same deep integration as Shopify

Zendesk for BigCommerce:

  1. Install the BigCommerce app from the Zendesk App Marketplace
  2. Agents see customer details and order history in the ticket sidebar

Custom / Headless

Build a Zendesk Sunshine App (sidebar panel) or Intercom Canvas Kit app that injects order context into every ticket:

Zendesk sidebar app — data endpoint:

// GET /api/support/zendesk-context?email=customer@example.com
export async function getZendeskContext(req: Request, res: Response) {
  const customerEmail = (req.query.email as string)?.toLowerCase();
  if (!customerEmail) return res.json({ customer: null, orders: [] });

  const [customer, recentOrders] = await Promise.all([
    db.customers.findByEmail(customerEmail, { include: ['segmentScore'] }),
    db.orders.findMany({
      where: { customerEmail },
      orderBy: { createdAt: 'desc' },
      take: 5,
      include: { lineItems: { include: { product: true } }, shipments: true },
    }),
  ]);

  res.json({
    customer: customer ? {
      lifetimeValue: customer.totalSpentCents / 100,
      orderCount: customer.orderCount,
      segment: customer.segmentScore?.segment,
      tags: customer.tags,
    } : null,
    orders: recentOrders.map(o => ({
      number: o.orderNumber,
      status: o.status,
      total: o.totalCents / 100,
      createdAt: o.createdAt,
      trackingUrl: o.shipments[0]?.trackingUrl,
      items: o.lineItems.map(i => ({ name: i.product.name, quantity: i.quantity })),
    })),
  });
}

Route high-value tickets to VIP queue:

// Called when a new Zendesk ticket is created (via Zendesk webhook)
export async function applyTicketRouting(ticketId: string) {
  const ticket = await fetchZendeskTicket(ticketId);
  const customerEmail = ticket.requester?.email?.toLowerCase();
  if (!customerEmail) return;

  const customer = await db.customers.findByEmail(customerEmail, { include: ['segmentScore'] });
  if (!customer) return;

  const isVIP = ['champions', 'cannot_lose_them'].includes(customer.segmentScore?.segment ?? '');
  const isHighValue = customer.totalSpentCents >= 100000;  // $1,000+

  if (isVIP || isHighValue) {
    await fetch(`https://${process.env.ZENDESK_SUBDOMAIN}.zendesk.com/api/v2/tickets/${ticketId}.json`, {
      method: 'PUT',
      headers: { Authorization: getZendeskAuthHeader(), 'Content-Type': 'application/json' },
      body: JSON.stringify({
        ticket: {
          priority: 'urgent',
          group_id: process.env.ZENDESK_VIP_GROUP_ID,
          tags: [...(ticket.tags ?? []), 'vip-customer'],
        },
      }),
    });
  }
}

// Auto-create ticket on delivery failure
export async function onDeliveryFailed(shipmentId: string) {
  const shipment = await db.shipments.findById(shipmentId, { include: ['order.customer'] });
  await fetch(`https://${process.env.ZENDESK_SUBDOMAIN}.zendesk.com/api/v2/tickets.json`, {
    method: 'POST',
    headers: { Authorization: getZendeskAuthHeader(), 'Content-Type': 'application/json' },
    body: JSON.stringify({
      ticket: {
        subject: `Delivery failed — Order #${shipment.order.orderNumber}`,
        comment: { body: `Delivery attempt failed on ${new Date().toDateString()}. Carrier: ${shipment.carrier}. Tracking: ${shipment.trackingNumber}.` },
        requester: { email: shipment.order.customer.email },
        priority: 'high',
        tags: ['delivery-failure', 'auto-created'],
      },
    }),
  });
}

Step 3: Set up ticket routing rules for VIP customers

Ensure your most valuable customers get faster responses by routing their tickets to your best agents.

Gorgias routing rules:

  1. Go to Automation → Rules → Create Rule
  2. Condition: Customer → Total spent → is greater than → $500
  3. Actions: Add tag → vip, Assign to → VIP Support Team, Set priority → Urgent

Zendesk trigger:

  1. Go to Admin → Business Rules → Triggers → Add trigger
  2. Conditions: ticket tag contains "vip-customer"
  3. Actions: assign to group (VIP Support), set priority to Urgent

Define SLA targets:

  • VIP customers: first response within 1 hour
  • Standard customers: first response within 24 hours
  • Set these in Gorgias → Settings → Business hours and SLAs or Zendesk → Admin → SLAs

Best Practices

  • Use Gorgias for Shopify stores — it's the purpose-built solution; the time saved on setup and the depth of integration are worth the subscription cost
  • Never store helpdesk API tokens in client-side code — Zendesk and Intercom API tokens have write access to all tickets; always proxy requests through your server
  • Attach the order ID to every ticket — this is the key that links your support system to your commerce database and enables two-way sync and automation
  • Keep order context fresh in the sidebar — cache data for 60 seconds maximum; an agent seeing stale order status is worse than a loading spinner
  • Log every agent action taken on an order — maintain an audit trail of refunds, order changes, and status updates initiated from within the helpdesk

Common Pitfalls

ProblemSolution
Agent sees wrong customer because email lookup is case-sensitiveNormalize all emails to lowercase before lookup; Jane@example.com and jane@example.com must resolve to the same customer
Webhook payload not verifiedImplement HMAC signature verification using the Zendesk/Gorgias webhook signing secret before processing any payload
CSAT sync creates duplicate customer recordsAlways look up by email first; never create a new customer record from a support webhook — link to existing or skip
Auto-created tickets missing order contextSet the order ID in a custom ticket field at creation time; this enables bidirectional sync and accurate routing

Related Skills

  • @live-chat-commerce
  • @customer-segmentation
  • @customer-lifetime-value

平台分布

Codex

33.76%
按下载量换算51

Claude

31.41%
按下载量换算47

Cursor

17.58%
按下载量换算26

Gemini CLI

8.23%
按下载量换算12

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills