菜单
A recurring helpdesk hygiene audit — redundant or inconsistent tags, stale macros, mismatched agent permissions, and gaps in your rules. Use monthly or quarterly to keep your Gorgias setup clean as it grows.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | monthly-helpdesk-hygiene |
| description | A recurring helpdesk hygiene audit — redundant or inconsistent tags, stale macros, mismatched agent permissions, and gaps in your rules. Use monthly or quarterly to keep your Gorgias setup clean as it grows. |
Helpdesk setups rot quietly. Tags multiply, macros go unused, permissions drift, rules develop blind spots — and messy tags are exactly why your reporting stops being trustworthy. This recipe runs a structured audit so cleanup is a 20-minute monthly ritual instead of a once-a-year archaeology dig, and so the numbers you present upward actually hold up. It only suggests — you decide what to clean.
| Variable | Example |
|---|---|
{{STALE_DAYS}} | "90 days" — how long unused = stale |
{{SECTIONS}} | which checks to run (default: all four below) |
Using the Gorgias MCP, run a helpdesk hygiene audit on my Gorgias account. For each section, give me a short list with a clear recommendation — don't change anything.
- Tag taxonomy. Flag tags that are redundant, inconsistently named (e.g.
returnvsreturnsvsReturn), or used on almost no tickets. Suggest merges and renames.- Stale macros. Find macros not used in the last {{STALE_DAYS}}. For each, tell me whether to update or retire it.
- Agent permissions. Flag any agents whose permissions don't match their apparent role.
- Rule gaps. Are there gaps in my helpdesk rules that could let tickets fall through the cracks (no assignment, no tag, no routing)?
Prioritize the list: what would you clean up first, and why?
Nothing by default — it produces a cleanup plan. Approve specific items and ask it to act (e.g. "Archive the 6 stale macros you listed").
weekly-voc-digest: untagged themes it surfaces are candidates for new tags here.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.