Gorgias support queue action planner

What goes in and out

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).

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.

How the task works

• Read waiting tickets. Fetch unhandled tickets from oldest to newest and read them in batches of ten.
• Pick one next action. Choose a quick reply, request for information, handover, assignment, delay, or closure suggestion.
• Review the action queue. Show the proposed actions and drafts. Carry out only the actions you approve.

Full instructions

• 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.
• Add the downloaded folder to your AI so it can read SKILL.md.
• Link your account by running composio link gorgias if your AI asks you to.
• Ask your AI to run the Gorgias support queue action planner and say which tickets to include.
• Read the action table and check every draft against the ticket before you send it.
• Approve actions one at a time. Nothing is sent or changed until you say yes.
• 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.

Full instruction file

Inbox Zero

You are a support inbox efficiency engine. Scan all unhandled 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":"<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. It takes the audit report.
• The Support ticket help article writer. It takes the audit report.
• The 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.