メニュー
Get your helpdesk and AI Agent ready for a seasonal event — BFCM, holidays, a big sale, a product drop. Drafts the temporary Guidance and Macros you'll need for the surge, and flags what to revert afterward. Drafts only.
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 | seasonal-prep |
| description | Get your helpdesk and AI Agent ready for a seasonal event — BFCM, holidays, a big sale, a product drop. Drafts the temporary Guidance and Macros you'll need for the surge, and flags what to revert afterward. Drafts only. |
Peak is when CX is most visible to the whole company — and most likely to drown. Every season brings the same predictable surge — WISMO ("will it arrive by [date]"), extended return windows, shipping cutoffs, sale-price adjustments. This recipe gets your AI Agent and macros ready before the wave hits, so your team isn't writing the same answer 500 times, and reminds you what to roll back when it's over. Drafts only.
| Variable | Example |
|---|---|
{{EVENT}} | "Black Friday / Cyber Monday 2026" |
{{TEMP_POLICIES}} | "extended 90-day returns; order-by Dec 18 for Christmas delivery; code BFCM30" |
{{KEY_DATES}} | "sale Nov 28–Dec 1; shipping cutoff Dec 18" |
{{EXPECTED_SPIKES}} | "WISMO, discount-not-applied, return-window questions" |
Using the Gorgias MCP, help me prep my Gorgias account for {{EVENT}}. Temporary policies in effect: {{TEMP_POLICIES}}. Key dates: {{KEY_DATES}}.
- Anticipate the surge. Based on {{EXPECTED_SPIKES}} and what happened in past peak periods, list the question types likely to spike.
- Draft seasonal Guidance. For each, draft Guidance reflecting the temporary policies — clearly marked as seasonal so it's easy to find later.
- Draft seasonal Macros. Canned replies for the team for the same scenarios (shipping cutoffs, promo issues, extended returns).
- Flag the rollback. List everything you created and the date/condition to revert or disable it, so temporary policy doesn't silently become permanent.
- Create Guidance and Macros as drafts for me to review and publish.
seasonal-{{EVENT}} so cleanup is one search later.policy-change-sweep in reverse to revert temporary policies cleanly.