菜单
Find and update every place a business policy lives across your Gorgias account — Guidance, Macros, and helpdesk rules — when that policy changes. Use when a return window, shipping cutoff, warranty term, or any stated policy is updated and you need it reflected everywhere consistently.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Build a targeted win-back segment from support signal — customers who hit a problem, left low CSAT, or went quiet after a bad experience — as a list you can hand to your email/SMS tool. The most qualified re-engagement audience you have is in your tickets. Read-only.
Turn the last 7 days of Gorgias tickets into an executive-ready weekly CX digest — analyzed across five business functions (Product, Marketing, Ecommerce/Revenue, Product Marketing, Leadership) with a TLDR, signal-status tagging, a PDP-gap table, and owner-tagged actions. Read-only; optionally publishes to Notion.
Build a back-in-stock demand list from customers who asked about out-of-stock or discontinued products — ranked by demand, with a per-product notify list — to drive back-in-stock campaigns and inform the next buy. Read-only.
Turn recurring customer language, objections, and praise from tickets into marketing angles, FAQ content, and on-site or ad copy — written in your customers' own words. The best copy you'll write is already in your inbox. Read-only.
Find the products generating the most pre-sales questions and post-purchase confusion, and get a concrete list of what to add to each product page. Turns support tickets into PDP improvements that lift conversion and cut returns. Read-only.
Cluster why customers actually return products — sizing, quality, expectation gaps — by product, from ticket and return language, so you can fix the root cause instead of just processing the refund. Returns are a margin killer; this finds where they start. Read-only.
| name | policy-change-sweep |
| description | Find and update every place a business policy lives across your Gorgias account — Guidance, Macros, and helpdesk rules — when that policy changes. Use when a return window, shipping cutoff, warranty term, or any stated policy is updated and you need it reflected everywhere consistently. |
When you change a policy, the old version is usually hiding in a dozen places: an AI Agent Guidance, three Macros, a helpdesk rule. Miss one and your AI Agent contradicts your team — which means wrong answers, CSAT hits, and repeat contacts landing right back in your queue. This recipe finds every reference and updates them in one pass — with you approving each change.
This is the kind of sweep that's painful by hand and impossible through the REST API alone (Guidance has no bulk REST surface). The MCP is the only supported route.
Replace these with your real values:
| Variable | Example |
|---|---|
{{OLD_POLICY}} | "30-day return window" |
{{NEW_POLICY}} | "60-day return window" |
{{EFFECTIVE_DATE}} | "starting June 15, 2026" (optional) |
Paste this into your connected AI client, with your values filled in:
Using the Gorgias MCP, sweep my Gorgias account for a policy change. We changed our policy: {{OLD_POLICY}} → {{NEW_POLICY}} ({{EFFECTIVE_DATE}}). Sweep my whole account for the old policy and prepare updates. Specifically:
- Search my Guidance for any mention of the old policy or its specifics (the old number, dates, terms). List each match with its title.
- Search my Macros for the same — canned replies often hard-code the old wording.
- Check my helpdesk rules for conditions or actions tied to the old policy.
- For each match, show me the current text and a proposed edit side-by-side. Don't change anything yet.
- Once I approve, apply the updates — Guidance as drafts for me to publish, Macros and rules updated directly.
Nothing changes until you've seen the before/after and said go.
