--- title: "Gorgias support queue action planner" type: "skill" url: "https://useaiblocks.com/skills/gorgias-support-queue-action-planner" 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/inbox-zero" instructions: "https://useaiblocks.com/skills/gorgias-support-queue-action-planner/SKILL.md" --- # Gorgias support queue action planner > Review Gorgias tickets in small batches. Get one suggested next step per ticket, with reply drafts and gaps to check before acting. Use a Composio setup linked to Gorgias. It reads waiting tickets in batches of ten and proposes a reply, information request, escalation, closure, assignment or follow-up. Get a review queue with reasons and draft text. Approved actions depend on the tools available and are confirmed one by one. Missing product facts and unresolved issues should stay visible before replies or closure. Free skill for the job "Help your customers" · Level: intermediate · Thinking: medium · Tested · Updated 2026-10-28 ## Links - Page: https://useaiblocks.com/skills/gorgias-support-queue-action-planner - Instructions (SKILL.md): https://useaiblocks.com/skills/gorgias-support-queue-action-planner/SKILL.md - All files (zip): https://useaiblocks.com/skills/gorgias-support-queue-action-planner.zip - JSON version: https://useaiblocks.com/skills/gorgias-support-queue-action-planner.json - In your AI: connect https://useaiblocks.com/mcp and ask "Use AI Blocks to get gorgias-support-queue-action-planner" ## What you give it - Your Gorgias account, connected through Composio. - The filter for which tickets to read, such as open status, age or team (optional). - The names of your teams, so tickets can be assigned (optional). ## What you get - A table of waiting tickets, oldest first, with one suggested action each. - Short reply drafts for simple questions. - Info requests for tickets that lack details. - A count of tickets to reply to, close, assign, pass on or follow up later. ## Example: what goes in and what comes out ### What goes in - Your open Gorgias tickets, read through a connected Gorgias account - The latest message on each ticket - Your team names for assigning tickets (optional) ### Before you start - A Gorgias account with open tickets - An AI that can run the Composio command line tool - Your Gorgias account linked to Composio ### What comes out - **Inbox Zero Queue**: A table of waiting tickets with number, customer, age, suggested action and a short preview of the reply. - **Quick reply drafts**: One or two sentence answers for simple questions with an obvious answer. - **Needs info messages**: Short requests asking the customer for the details you need to solve the issue. - **Escalate, close, assign and defer notes**: A short reason for each ticket to pass on, close, hand to a team or follow up later. - **Quick Stats**: Counts of quick replies, info requests, escalations, closeable and deferred tickets. ## Use it when - Your Gorgias queue has many open tickets and you want a fast first pass. - You start the day and need to know which tickets can be cleared quickly. - You want draft replies for simple questions without writing each one. - You need to sort tickets into reply, close, assign or pass to another team. ## Skip it when - You have one ticket to answer: read it and write the reply yourself, or ask your AI to draft it from the pasted text. - A ticket needs a refund, policy or exception decision: pass it to a person on your team who can make the call. - You do not use Gorgias: use your own help desk's export and ask your AI to sort it by hand. ## How to use it 1. Use an AI that can run commands, such as Claude Code. You need the Composio command line tool installed (see Composio's install guide). Gorgias is a paid help desk. Composio may charge for use, so check its pricing before the first run. 2. Add the downloaded folder to your AI so it can read SKILL.md. 3. Link your account by running composio link gorgias if your AI asks you to. 4. Ask your AI to run the Gorgias support queue action planner and say which tickets to include. 5. Read the action table and check every draft against the ticket before you send it. 6. Approve actions one at a time. Nothing is sent or changed until you say yes. 7. Next, send the approved replies from Gorgias. Pass escalations to the person or team who handles bugs, since the /escalate command the skill mentions is not included here. Run the planner again at the start of the next shift. ## What to do next - [Support issue cause investigator](https://useaiblocks.com/skills/support-issue-cause-investigator): Support issue cause investigator - [Support ticket help article writer](https://useaiblocks.com/skills/solved-ticket-help-page-writer): Support ticket help article writer - [Escalation brief writer](https://useaiblocks.com/skills/escalation-brief-writer): Escalation brief writer ## Sources and credits - From Composio: https://github.com/composio-community/support-skills/tree/83382c4b055fc4e5b055044adb5bfb7585484c9a/inbox-zero, shared under the MIT licence (original name: inbox-zero). - [inbox-zero skill](https://github.com/composio-community/support-skills/tree/83382c4b055fc4e5b055044adb5bfb7585484c9a/inbox-zero), Composio: Copied under the MIT licence. We gave it a plain name and updated the description to list the six actions and the approval step. We added Before you start and After this sections that link to other AI Blocks steps. ## Instructions (SKILL.md) ## Inbox Zero You are a support inbox efficiency engine. Scan all unhandled [Gorgias](https://composio.dev/toolkits/gorgias) tickets and help the agent power through them with AI-suggested quick actions for each. ### 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:** Live lookups need Composio CLI access and connected accounts for these services. ### Workflow #### Step 1: Discover tools Run `composio search "list open unassigned tickets from Gorgias" "get ticket details from Gorgias"` in Bash. #### Step 2: Fetch unhandled tickets Run `composio execute GORGIAS_LIST_TICKETS -d '{...open, order oldest first...}'` in Bash to get all open tickets that need attention. If the CLI reports the toolkit is not connected, ask the user to run `composio link gorgias` and retry. #### Step 3: Quick-scan each ticket For each ticket (batch of 10 at a time), run `composio execute GORGIAS_GET_TICKET -d '{"ticket_id":""}'` in Bash as parallel calls to read the latest message. #### Step 4: Generate quick actions For each ticket, suggest ONE primary action: - **QUICK REPLY** - Simple question with obvious answer. Draft a 1-2 sentence response. - **NEEDS INFO** - Can't resolve without more details. Draft an info-request message. - **ESCALATE** - Bug or issue needing engineering. Flag for `/escalate`. - **CLOSE** - Already resolved, duplicate, or spam. Suggest closing. - **ASSIGN** - Needs specialist attention. Suggest which team. - **DEFER** - Waiting on something external. Note what and when to follow up. #### Step 5: Present the action queue ``` ## Inbox Zero Queue **Tickets to process:** X | # | Ticket | Customer | Age | Action | Preview | |---|--------|----------|-----|--------|---------| | 1 | #123 | alice@co | 2h | QUICK REPLY | "Yes, you can reset it in Settings > ..." | | 2 | #124 | bob@co | 4h | NEEDS INFO | "Could you share your browser version?" | | 3 | #125 | eve@co | 1d | ESCALATE | Bug in checkout flow | | 4 | #126 | dan@co | 1d | CLOSE | Duplicate of #120 | | ... | | | | | | ### Quick Stats - Quick replies: X (can clear in ~Y minutes) - Need info: X - Escalations: X - Closeable: X - Deferred: X Process all quick replies? (y/n) ``` Execute approved actions one by one, confirming each. For quick replies, draft the response. For escalations, suggest using `/escalate`. ### 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 [Support issue cause investigator](https://useaiblocks.com/skills/support-issue-cause-investigator). It takes the audit report. - The [Support ticket help article writer](https://useaiblocks.com/skills/solved-ticket-help-page-writer). It takes the audit report. - The [Escalation brief writer](https://useaiblocks.com/skills/escalation-brief-writer). It takes the audit report. 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.