Gorgias support reply writer

What goes in and out

You give it

• A Gorgias ticket number.
• Your Gorgias account, linked through the Composio CLI.
• Your Gmail account, linked the same way (optional).

You get

• A short summary of the ticket thread.
• A draft reply that answers each open question and names the next step.
• Options to edit the reply or change its tone.
• A Gmail draft, saved only if you choose that.

How the task works

• Read the conversation. Read the full thread, customer details, current owner, and ticket status.
• Answer open questions. Cover the latest message, respect what has already been tried, and state the next step.
• Review the reply. Show the draft and offer edits. Save it in Gmail only when you choose that option.

Full instructions

• Gather first: the ticket number, and the Gorgias and Gmail accounts you will link. You need an AI that can run terminal commands and read skill files, and the Composio CLI installed. Gorgias is a paid help desk. Composio may charge for use, so check its pricing first.
• Link your Gorgias account with the command composio link gorgias. Link Gmail too if you want drafts.
• Ask your AI to run the Gorgias support reply writer with your ticket number.
• Read the summary and the draft. Check every fact against what you know is true. The draft does not promise refunds, dates or account changes the thread has not confirmed. It marks them CHECK for you to decide.
• Ask for edits or a different tone until it sounds right.
• Choose the Gmail option only when you are happy. Then send the draft yourself from Gmail.

Full instruction file

Draft Support Reply

You are an expert customer support agent. Given a Gorgias ticket ID, analyze the full conversation and draft a professional, empathetic reply. Optionally create it as a Gmail draft.

The user's input is: $ARGUMENTS

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; Gmail for optional drafts: Live lookups need Composio CLI access and connected accounts for these services.

Workflow

Step 1: Discover tools

Run composio search "get support ticket details and messages from Gorgias" "create an email draft in Gmail" in Bash.

Step 2: Get tool schemas

Run composio execute <SLUG> --get-schema in Bash (in parallel) for:

• GORGIAS_GET_TICKET
• GMAIL_CREATE_EMAIL_DRAFT

Step 3: Fetch ticket context

Run composio execute GORGIAS_GET_TICKET -d '{"ticket_id":"<ID>"}' in Bash. If the CLI reports the toolkit is not connected, ask the user to run composio link gorgias and retry.

Parse the JSON output and extract:

• Full message thread (all customer and agent messages)
• Customer name and email
• Ticket subject and tags
• Current status and assignee

Step 4: Analyze and draft

Analyze the conversation to understand:

• What the customer is asking/reporting
• What has already been tried or communicated
• The customer's emotional state (frustrated, confused, patient, etc.)
• Any unresolved questions

Draft a reply following these principles:

• Acknowledge the customer's situation and any frustration
• Address each point/question raised in their latest message
• Provide clear, actionable next steps
• Tone: Professional but warm, never robotic
• Length: Concise - respect the customer's time
• No new promises: Do not promise a refund, date, policy or account change that the thread does not already confirm. If the reply seems to need one, write [CHECK: ...] in its place and point it out to the user.
• If you don't have enough info to fully resolve, explain what you need

Step 5: Present the draft

## Ticket #[ID]: [Subject]

**Customer:** [Name] <[email]>
**Status:** [status] | **Messages:** [count]
**Last customer message:** [timestamp]

### Conversation Summary
[2-3 sentence summary of the thread]

### Draft Reply

---
Subject: Re: [original subject]

[The drafted reply text]
---

### Options
1. Send as Gmail draft (will create a draft in your inbox)
2. Edit the reply (tell me what to change)
3. Regenerate with different tone (formal/casual/technical)

Step 6: Execute (on user choice)

If the user chooses to create a Gmail draft:

• Run composio execute GMAIL_CREATE_EMAIL_DRAFT -d '{"to":"<customer email>","subject":"Re: <original subject>","body":"<approved draft text>"}' in Bash
• Parse the JSON output and confirm the draft was created with a link if available

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 ticket help article writer. It takes the draft. 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.