菜单
Generate a shareable support performance report for your team or leadership — volume, automation rate, top intents, CSAT, and trends — formatted for a Slack post or doc. Read-only. Best-effort while analytics are in beta.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | performance-report |
| description | Generate a shareable support performance report for your team or leadership — volume, automation rate, top intents, CSAT, and trends — formatted for a Slack post or doc. Read-only. Best-effort while analytics are in beta. |
Every month you have to show leadership what CX actually delivered — and pulling the numbers together by hand is the part that eats your afternoon. This recipe assembles the metrics and the narrative into something you can paste straight into Slack or a board doc, so CX lands as a value center, not a cost line. Read-only.
Heads up: Gorgias MCP analytics are in beta. Figures here are directional and may differ slightly from your in-product Statistics dashboard. Use it for narrative and trends, and cross-check exact numbers in Statistics before reporting them up.
| Variable | Example |
|---|---|
{{PERIOD}} | "May 2026" |
{{COMPARE_TO}} | "vs April 2026" |
{{METRICS}} | "volume, automation rate, CSAT, first response time, top 5 intents" |
{{AUDIENCE}} | "leadership" — sets tone and depth |
{{FORMAT}} | "a Slack post" or "a one-page summary" |
Using the Gorgias MCP, build a support performance report for {{PERIOD}} ({{COMPARE_TO}}), for {{AUDIENCE}}, formatted as {{FORMAT}}.
- Headline metrics: {{METRICS}}. Show each with the change vs the comparison period.
- What drove volume: the top contact reasons, and any notable shifts.
- AI Agent impact: automation rate and where it's helping most / struggling most.
- One win and one watch-item for the period.
- Add the disclaimer that figures are directional pending the in-product dashboard.
Keep it tight and skimmable — numbers with a one-line "so what" each, not a wall of stats.
Nothing. Read-only.
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.
