方法与优势
把紧急程度和具体处理动作分开判断。客户催得急,并不意味着已经具备退款条件;草稿会同时说明客户诉求、已知订单事实及主管需要决定的事项,方便接手的人直接处理。
这项客服工单分类 Skill 帮 Shopify 团队把堆积的售前、物流和售后消息整理成清晰的处理队列。提供客户原话、已确认的订单信息及店铺政策后,它会给出优先级、回复草稿和升级处理说明,让客服知道先处理哪件事、还需补充什么资料。
Shopify Support Triage 会先读客户在问什么,再对照订单事实、店铺政策和团队分工,把问题整理为四个优先级。例如,物流延误、收到破损商品和一般产品咨询,可以分别列出需要查询的资料与下一步处理方式。
交付内容包括客服回复草稿、待补充信息和转交对象。团队可以据此安排处理顺序,减少反复翻找聊天记录;工单分配与邮件发送仍在原来的客服系统中完成。
把紧急程度和具体处理动作分开判断。客户催得急,并不意味着已经具备退款条件;草稿会同时说明客户诉求、已知订单事实及主管需要决定的事项,方便接手的人直接处理。
适合交接班整理消息、集中处理配送延误,以及把复杂投诉转交主管。输入店铺实际政策和岗位分工后,同一批消息会按统一规则整理,客服可以直接核对并修改草稿。
脱敏客户消息、已确认的订单事实、店铺政策和团队分工。
可先在模型对话中用这些指令起草。真实系统访问或文件修改需另行配置工具。
收录文本没有 Shopify 连接器或工单分配程序。订单事实和处理时限需由你提供,赔付须经批准。
可直接在聊天中使用这些指令,也可让 Codex / Claude Code 保存为个人 Skill,方便重复处理同类任务。
请在我正在使用的应用中,将「Shopify Support Triage Agent」设置为可重复使用的个人指令模板。
1. 阅读 https://ecomagenttools.com/skills/shopify-support-triage 页面的“收录的指令模板”部分,只使用其中完整指令,不要把评论、FAQ 或安装说明当成 Skill 正文。无法取得完整文本时,请让我粘贴,不要猜测内容或安装其他同名第三方包。
2. 列出需要我补充的假设、占位符和访问条件,保留收录指令的任务内容。这是本地适配模板,不是原作者发布包。
3. 如果你是能访问本机文件的 Codex 或 Claude Code,创建名为 shopify-support-triage-local 的个人 Skill:Codex 放到 ~/.agents/skills/shopify-support-triage-local/SKILL.md,Claude Code 放到 ~/.claude/skills/shopify-support-triage-local/SKILL.md。缺少时补齐合法的 name、description 前置信息,正文保留收录指令并标注本地适配,不覆盖已有 Skill。只有聊天能力时就在当前对话中使用,不声称已安装到本机。
4. 返回保存位置或当前对话的配置结果,以及适用于这个任务的启动提问。列出尚未配置的工具或资料,不把保存模板说成已经接通账号、API 或完成实际业务测试。网络搜集,无确切作者来源。复核了收录文本,但尚未将它与可核对的原始发布条目关联。这不代表官方安装包不存在;本页示例仅依据已收录文本。
You are a Shopify customer support triage agent for an ecommerce store. Your role:
1. Analyze each incoming customer message and classify it:
- 🚨 URGENT: Refund requests, chargebacks, legal threats
- ⚡ HIGH: Shipping delays, damaged items, wrong orders
- 📋 NORMAL: Product questions, sizing help, stock availability
- 💡 LOW: General feedback, feature requests, thank-you notes
2. For each ticket, draft a response with:
- Empathetic acknowledgment of the issue
- Specific next steps based on category
- Estimated resolution timeline
- One personalized detail from their order history
3. Suggest which team member should handle it based on:
- Order value (high-value → senior agent)
- Issue complexity
- Customer history (repeat issues → manager)
Your tone is warm, professional, and solution-oriented. Never make promises about refunds or compensation — defer those to human approval.以下是主要功能的用例提示词,可以直接复制使用。
将每条消息分为紧急、高、普通或低优先级,说明理由和缺失信息。 适用于:分级客服队列。请准备:脱敏客户消息、已确认的订单事实、店铺政策和团队分工。
请按上方收录指令。任务:将每条消息分为紧急、高、普通或低优先级,说明理由和缺失信息。。输入:[INPUT]。限制:[CONSTRAINTS]。先检查缺失信息,再输出可审查的结果、依据、假设和下一步。收录文本没有 Shopify 连接器或工单分配程序。订单事实和处理时限需由你提供,赔付须经批准。[INPUT][CONSTRAINTS]根据已确认的物流信息致歉并起草下一步说明,不编造送达日期。 适用于:起草物流延误回复。请准备:脱敏客户消息、已确认的订单事实、店铺政策和团队分工。
请按上方收录指令。任务:根据已确认的物流信息致歉并起草下一步说明,不编造送达日期。。输入:[INPUT]。限制:[CONSTRAINTS]。先检查缺失信息,再输出可审查的结果、依据、假设和下一步。收录文本没有 Shopify 连接器或工单分配程序。订单事实和处理时限需由你提供,赔付须经批准。[INPUT][CONSTRAINTS]按订单金额、复杂度和重复问题建议负责人,列出人工需确认的事实。 适用于:准备升级交接。请准备:脱敏客户消息、已确认的订单事实、店铺政策和团队分工。
请按上方收录指令。任务:按订单金额、复杂度和重复问题建议负责人,列出人工需确认的事实。。输入:[INPUT]。限制:[CONSTRAINTS]。先检查缺失信息,再输出可审查的结果、依据、假设和下一步。收录文本没有 Shopify 连接器或工单分配程序。订单事实和处理时限需由你提供,赔付须经批准。[INPUT][CONSTRAINTS]HarborMug 的模拟订单 A100 于 10 月 20 日签收,11 月 3 日申请退货,商品价 $24、未拆封。输入包含 30 天退货政策与客服分工,任务是判断优先级并准备首次回复。
案例输入资料:business-inputs.zip
Use the shopify-support-triage Skill.
Our support queue has a return request for order A100. Decide its priority and owner from the return policy and team responsibilities, explain eligibility, and draft the first customer reply with the information we still need. Give the next internal action and escalation condition.
The attached business materials are:
- inputs/brief.json
- inputs/merchant.json
Deliver a complete result.md report that the operations team can read, plus any finished files needed for this task. Keep supporting calculations and evidence with the deliverables. Write the report in English; use the requested target language for customer-facing copy. The business datasets are fictional examples unless the brief explicitly names a live public website.下方直接展示本次 Prompt 产生的主要文件,保留实际输出语言。
Priority: URGENT. Owner: Mia, frontline support lead. Ticket SYN-N001 explicitly requests a refund, which the Skill classifies as urgent. The input case label “normal” does not override that rule. This is a routine return involving one $24 item, below the supplied $200 senior-agent threshold, with no prior issues recorded. Alex, the escalation lead and senior agent/manager, is the escalation owner.
All case information is synthetic. This report is a proposed handling decision and an unsent reply; no account action, return authorization, or refund has occurred.
The customer reports that the blue 500 ml stainless-steel insulated cup is unopened. The request was received on November 3, 2026, 14 calendar days after delivery on October 20. Under the supplied test assumption that the 30-day return period starts at delivery, the request is within the window, with 16 days remaining at receipt. The calculated 30-day boundary is November 19; it is not a confirmed customer deadline because the actual policy does not specify its start point or boundary handling.
Provisionally eligible for review, subject to confirming the item is unused and human approval. Unopened is the customer's report, not an inspected condition. The merchant explicitly requires manual refund approval. The materials do not establish a return address, authorization process, return postage responsibility, refund amount, refund processing time, or whether the window applies to requesting or receiving a return. Mia must confirm these before providing return instructions. Outbound dispatch and delivery estimates do not establish a return or refund timeline.
林女士,您好!理解您想为 A100 订单中的蓝色 500ml 不锈钢保温杯办理退货退款,感谢您告知商品尚未拆封。
根据现有记录,订单于10月20日签收,您在11月3日提出申请。按本次审核暂以签收日起算30天的口径,申请仍在期限内;具体退货资格和退款需由商家人工审核确认。
为便于审核,请您补充确认:杯子是否完全未使用,商品及原包装目前是否完好?如有破损或其他情况,也请一并说明。
收到完整资料后,我们预计在1个工作日内进行首次人工审核,并向您说明下一步。该时间是预计审核时间,不代表退款获批或最终处理完成时间。请先保留商品和包装,待我们确认退货地址及寄回要求后再寄出。
感谢您的配合!
Mia should mark the ticket urgent and pending customer information, record the request date and reported unopened condition, and use the draft above to request the missing condition details through the team's approved process. No need to ask the customer again for the order number or delivery date already supplied.
In parallel, Mia should verify the return-clock interpretation, request-versus-receipt cutoff, return instructions, postage responsibility, and designated human refund approver with the merchant. Once the condition details are complete, route the case for its first manual review, targeting one business day as an estimate. Only communicate approved return instructions and refund terms after human review; do not invent a refund amount or promise compensation.
Escalate to Alex if condition evidence conflicts with the unused-return rule, the return-clock ambiguity affects eligibility, the customer disputes the decision, repeat issues emerge, or Mia cannot obtain the necessary approval or instructions within the estimated review window. Route refund authorization to the merchant's designated human approver; Alex can coordinate this, but the supplied roles do not establish that Alex personally has refund authority. Senior handling is not triggered by the current $24 value.
eligibility-calculations.json: date arithmetic, value threshold check, and assumptions.evidence.md: source-to-decision trace and unresolved policy details.The review target and delivery-based return clock are explicitly supplied synthetic operating assumptions, not verified merchant service guarantees. No final eligibility or refund decision can be made from these materials alone. Weekly sales context is marked unused in the input and is unnecessary for this ticket.
案例中的商家经营资料为模拟数据;涉及网站检查时,报告中的页面观察来自所列公开网址。
收录文本没有 Shopify 连接器或工单分配程序。订单事实和处理时限需由你提供,赔付须经批准。
网络搜集,无确切作者来源。复核了收录文本,但尚未将它与可核对的原始发布条目关联。这不代表官方安装包不存在;本页示例仅依据已收录文本。
使用获授权输入,不把密钥贴入提示词。采用前检查面向客户的声明、计算、代码改动及任何拟议的外部操作。
对客服消息分级、起草回复,并建议由谁接手。四级优先级规则把紧急程度、下一步动作和升级负责人分开整理。
将下方收录指令复制到模型对话或项目指令中。 按实际情况替换假定的系统权限、默认政策、样例数字和占位符。 附上一份小型脱敏样本,使用下方示例提问,实际采用前检查草稿。
分级客服队列;起草物流延误回复;准备升级交接
收录文本没有 Shopify 连接器或工单分配程序。订单事实和处理时限需由你提供,赔付须经批准。
网络搜集,无确切作者来源。复核了收录文本,但尚未将它与可核对的原始发布条目关联。这不代表官方安装包不存在;本页示例仅依据已收录文本。
该 Skill 的完整可用内容已被收录和审查;公开网络资料暂未列出原作者。作者信息不影响其目录展示或基于内容的推荐资格。
网络搜集,未列出确切作者来源。该标签仅说明署名状态,不代表能力、可见性或推荐资格。
暂无评论。