--- title: "Gorgias weekly support reporter" type: "skill" url: "https://useaiblocks.com/skills/gorgias-weekly-support-report" updated: "2026-10-28" first_published: "2026-10-25" job: "Help your customers" tested: true licence: "MIT" source: "https://github.com/composio-community/support-skills/tree/83382c4b055fc4e5b055044adb5bfb7585484c9a/weekly-digest" instructions: "https://useaiblocks.com/skills/gorgias-weekly-support-report/SKILL.md" --- # Gorgias weekly support reporter > Review a week of Gorgias tickets. Get ticket counts, recurring problems, notable cases and proposed fixes, with an optional approved Slack post. Use a Composio setup linked to Gorgias and, for posting, Slack. It gathers the week’s ticket list with pagination and reads up to twenty-five threads in detail. Get supported counts, timing measures, recurring issues and suggested fixes. Sample-based measures stay labelled. Week-over-week changes need the earlier week’s data, and posting needs your approval. Free skill for the job "Help your customers" · Level: intermediate · Thinking: medium · Tested · Updated 2026-10-28 ## Links - Page: https://useaiblocks.com/skills/gorgias-weekly-support-report - Instructions (SKILL.md): https://useaiblocks.com/skills/gorgias-weekly-support-report/SKILL.md - All files (zip): https://useaiblocks.com/skills/gorgias-weekly-support-report.zip - JSON version: https://useaiblocks.com/skills/gorgias-weekly-support-report.json - In your AI: connect https://useaiblocks.com/mcp and ask "Use AI Blocks to get gorgias-weekly-support-report" ## What you give it - Your Gorgias account, connected through Composio. - The week you want covered (optional, the past 7 days is the default). - The Slack channel to post to (optional). ## What you get - Counts of new, resolved and open tickets for the week. - Average first response and resolution times, plus CSAT if your data has it. - The top issue groups with ticket counts. - Three notable tickets: the biggest fire, the longest open, and the best resolution. - Trends and recommended fixes you can act on. - A Slack post of the report, only after you approve it. ## Example: what goes in and what comes out ### What goes in - Your Gorgias account, connected through Composio - The week to cover (the past 7 days by default) - A Slack channel for the report (optional) ### Before you start - A Composio account and the Composio command line tool set up - Your Gorgias account connected in Composio - A Slack account connected in Composio, only if you want to post the report - An AI that can run commands ### What comes out - **At a Glance**: New, resolved and open tickets, average first response time, average resolution time, and CSAT score if your data has it. - **Top Issues This Week**: The main issue groups, how many tickets each had, and a short note on the trend. - **Notable Tickets**: The biggest fire, the longest open ticket, and a resolution worth sharing. - **Trends**: New patterns, growing or shrinking issues, and the product areas that bring in the most tickets. - **Recommendations**: Process changes, product fixes to cut ticket volume, and help articles to write or update. - **Slack post**: The same report sent to your chosen channel after you approve it, with a link to the message. ## Use it when - It is Monday and you want last week's support numbers in one page for your team. - Your tickets sit in Gorgias and you want to spot repeat problems before they grow. - You need a short update for your boss or your team's Slack channel. - You want ideas for help articles or product fixes based on what customers asked. ## Skip it when - You need to look up or reply to one ticket: open it in Gorgias and read the thread there. - Your support runs on live chat or email outside Gorgias: ask your AI to summarize an export of those messages by hand, or use that tool's own reports. - You want a report without installing the Composio command line tool: copy your ticket numbers into a spreadsheet and sum them there. ## How to use it 1. Set up the Composio command line tool and connect your Gorgias account. Connect Slack too if you want to post. 2. Open an AI that can run commands and load the downloaded skill folder. 3. Ask for the weekly support digest by name. 4. If Gorgias is not connected, your AI will ask you to run composio link gorgias. Do that, then ask again. 5. Read the report. Check the numbers against Gorgias for anything that looks off. The averages come from a sample of up to 25 tickets, so read them as a rough guide. 6. Your AI removes customer names, emails and order details from the report before it asks you to approve. Check the cleaned version. Say yes to post it. Your AI finds the Slack channel and sends it. This skill is a copy of the Composio weekly-digest skill (MIT licence), and the Slack argument names are read from the live tool before use. ## What to do next - [Gorgias support metrics reporter](https://useaiblocks.com/skills/gorgias-support-metrics-report): Gorgias support metrics reporter - [Gorgias ticket priority planner](https://useaiblocks.com/skills/gorgias-ticket-priority-planner): Gorgias ticket priority planner ## Sources and credits - From Composio: https://github.com/composio-community/support-skills/tree/83382c4b055fc4e5b055044adb5bfb7585484c9a/weekly-digest, shared under the MIT licence (original name: weekly-digest). - [weekly-digest skill](https://github.com/composio-community/support-skills/tree/83382c4b055fc4e5b055044adb5bfb7585484c9a/weekly-digest), Composio: Copied under the MIT licence. We gave it a plain name. We added Before you start and After this sections that link to other AI Blocks steps. ## Instructions (SKILL.md) ## Weekly Support Digest You are a support reporting analyst. Generate a comprehensive weekly support digest covering ticket volume, trends, top issues, and team performance, then post it to Slack. ### Before you start Use the material below to do this job. If facts or tool access are missing, explain what you can finish and what must wait. **What you need** (use your own material or the linked skill): - **Your question** (yours): the decision or problem, and what a good outcome looks like. - **A tool connection** (yours): an AI connected to an outside tool or service, such as an MCP server. How to start: 1. **Look first.** Use what they've already attached, pasted or put in their about-me note. In a coding assistant with file access, look in the project too for these by name. 2. **Check what's missing.** Look for your question, a tool connection. They can attach files, paste the details, or share a file path your assistant can read. Ask only for missing facts that change the result. If they ask you to start with what they have, complete the parts you can and mark the gaps. 3. **Do the job.** Follow the skill below with the facts and tools you have. Mark each gap with `MISSING:` where it belongs and never invent a fact to fill it. **Tools that do this best:** - **Gorgias; Slack for optional sharing:** Live lookups need Composio CLI access and connected accounts for these services. ### Workflow #### Step 1: Discover tools Run `composio search "list support tickets from Gorgias filtered by date range" "get ticket details from Gorgias" "send a formatted message to Slack channel"` in Bash. #### Step 2: Fetch the week's data Run `composio execute GORGIAS_LIST_TICKETS -d ''` in Bash, with the date range set to the past 7 days (or the week the user named), using the argument names from the schema (get it first with `composio execute GORGIAS_LIST_TICKETS --get-schema`) to pull all tickets from the past 7 days. Paginate to get the complete set. Then run the same call once more for the 7 days before that, so you can compare the two weeks. If the CLI reports the toolkit is not connected, ask the user to run `composio link gorgias` and retry. #### Step 3: Enrich key tickets For a representative sample (up to 25 tickets), run `composio execute GORGIAS_GET_TICKET -d '{"ticket_id":""}'` in Bash as parallel calls to get response time data and message details. #### Step 4: Compile the digest ``` ## Weekly Support Digest **Week of:** [Monday date] - [Sunday date] ### At a Glance - New tickets: X (+/-Y% vs last week, worked out from the previous week's pull in Step 2; if that pull failed or is empty, leave the comparison out and say so) - Resolved: X - Still open: X - Avg first response: Xh (from a sample of up to 25 tickets) - Avg resolution time: Xh (from a sample of up to 25 tickets) - Sample note: ticket counts cover the whole week; the averages come from the sample only. Say how many tickets the sample held. - CSAT: X% (if available) ### Top Issues This Week 1. [Issue category] - X tickets - [brief description of trend] 2. [Issue category] - X tickets 3. [Issue category] - X tickets ### Notable Tickets - **Biggest fire:** #[ID] - [what happened and how it was resolved] - **Longest open:** #[ID] - [status and why] - **Best resolution:** #[ID] - [quick/creative resolution worth highlighting] ### Trends - [Any emerging patterns] - [Issues that are growing/shrinking] - [Product areas generating the most tickets] ### Recommendations - [Process improvements] - [Product fixes that would reduce ticket volume] - [Knowledge base articles to create/update] ``` #### Step 5: Confirm and post to Slack Show the digest to the user for review. Before posting, strip customer names, email addresses, order details and any other personal data from the ticket excerpts, and show the user the cleaned version. After confirmation: 1. Run `composio execute SLACK_FIND_CHANNELS -d ''` in Bash (ask the user which channel, and read the argument names from `composio execute SLACK_FIND_CHANNELS --get-schema` first, because they can change) to find the target Slack channel, parse the JSON output for the channel ID 2. Format the digest as a Slack message (use markdown_text for formatting) 3. Run `composio execute SLACK_SEND_MESSAGE -d '{"channel":"","text":""}'` in Bash 4. Parse the JSON output and confirm with the posted message link ### After this When you've handed it back, suggest what they could do next in one short question. It's a suggestion: if they're done, that's fine. Offer these, and say they can type their own: - The [Gorgias support metrics reporter](https://useaiblocks.com/skills/gorgias-support-metrics-report). - The [Gorgias ticket priority planner](https://useaiblocks.com/skills/gorgias-ticket-priority-planner). If they pick one and that skill is added here, carry straight on with what you just made. If not, give the link and say what to bring.