--- title: "Gorgias refund review brief writer" type: "skill" url: "https://useaiblocks.com/skills/gorgias-refund-review-brief" 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/refund-processor" instructions: "https://useaiblocks.com/skills/gorgias-refund-review-brief/SKILL.md" --- # Gorgias refund review brief writer > Share a refund ticket and policy. Get known facts, eligibility gaps, a proposed decision and a customer reply draft for review. Use a Composio setup linked to Gorgias and HubSpot. It reads the request, gathers customer context and compares it with your refund policy. Get a case for approval, with missing dates, amounts and policy details marked. You review the proposed decision and reply. The actual refund remains a separate action, and approval thresholds need to be supplied. Free skill for the job "Help your customers" · Level: intermediate · Thinking: medium · Tested · Updated 2026-10-28 ## Links - Page: https://useaiblocks.com/skills/gorgias-refund-review-brief - Instructions (SKILL.md): https://useaiblocks.com/skills/gorgias-refund-review-brief/SKILL.md - All files (zip): https://useaiblocks.com/skills/gorgias-refund-review-brief.zip - JSON version: https://useaiblocks.com/skills/gorgias-refund-review-brief.json - In your AI: connect https://useaiblocks.com/mcp and ask "Use AI Blocks to get gorgias-refund-review-brief" ## What you give it - A Gorgias ticket number or the customer's email. - Your refund policy, pasted in (optional). - Access to Gorgias and HubSpot through the Composio CLI. ## What you get - A summary of the request and the customer's history. - A table that checks the request against your refund rules. - A recommendation with the reasoning and the risk of losing the customer. - A draft reply to the customer for you to review. - A flag when the refund is large enough to need manager approval. ## Example: what goes in and what comes out ### What goes in - A Gorgias ticket number or the customer's email - Your refund policy (optional) - Your HubSpot customer record (read by the tool) ### Before you start - An AI that can run commands and read skill files - The Composio CLI, with your Gorgias and HubSpot accounts linked ### What comes out - **Request Details**: The ticket number, customer name and email, amount asked for, stated reason and date of the request. - **Customer Profile**: How long they have been a customer, their plan, lifetime value, past refunds, account status and open deals. - **Eligibility Check**: A table that marks the refund window, reason, refund history and account standing, with a note for each. - **Recommendation**: Full refund, partial refund, credit, or deny with an alternative, plus the reasoning and the risk of losing the customer. - **Draft Response to Customer**: A ready reply for either approval or denial, for a person to check before sending. ## Use it when - A customer writes in asking for money back and you need the full picture fast. - You want to check a refund request against your policy before you answer. - A teammate asks you to review a refund and you need the facts in one place. - You want a reply drafted for an approve or deny decision. ## Skip it when - You face a chargeback or card dispute: handle it with your payment provider, such as Stripe or PayPal, and their dispute steps. - The customer only wants to cancel and has not asked for money back: reply yourself or use your billing tool's cancel step. - You cannot connect Gorgias and HubSpot: paste the ticket and customer details into your AI and ask for a simple summary, or ask a teammate to review it. ## How to use it 1. Add the downloaded folder to an AI that can read skill files and run commands. 2. Link your accounts first. Run composio link gorgias and composio link hubspot if asked. Gorgias is a paid help desk. HubSpot has a free CRM plan, with paid extras. Composio may charge for use, so check its pricing before the first run. 3. Ask for the refund processor and give the ticket number or customer email. Paste your refund policy and the amount above which a manager must approve. Without them, the policy rows are left as not checked. 4. Read the eligibility table and the recommendation. Check them against your own policy. 5. Edit the draft reply, then send it yourself. The skill never issues the refund. 6. If you approve, issue the refund yourself in your shop or payment tool, such as Shopify or Stripe. Then tell the customer the amount and when to expect it, and note the decision on the Gorgias ticket. ## What to do next - [Gorgias and HubSpot customer briefing writer](https://useaiblocks.com/skills/gorgias-and-hubspot-customer-brief): Gorgias and HubSpot customer briefing writer - [Refund rate analyzer](https://useaiblocks.com/skills/refund-rate-analyzer): Refund rate analyzer ## Sources and credits - From Composio: https://github.com/composio-community/support-skills/tree/83382c4b055fc4e5b055044adb5bfb7585484c9a/refund-processor, shared under the MIT licence (original name: refund-processor). - [refund-processor skill](https://github.com/composio-community/support-skills/tree/83382c4b055fc4e5b055044adb5bfb7585484c9a/refund-processor), Composio: Copied under the MIT licence. We gave it a plain name and split the Step 2 lookup into two clear commands. We added Before you start and After this sections that link to other AI Blocks steps. ## Instructions (SKILL.md) ## Refund Processor You are a refund request handler. Gather all context around a refund request from [Gorgias](https://composio.dev/toolkits/gorgias) and [HubSpot](https://composio.dev/toolkits/hubspot), assess eligibility, and prepare the refund for approval. 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 and HubSpot:** Live lookups need Composio CLI access and connected accounts for these services. ### Workflow #### Step 1: Discover tools Run `composio search "get support ticket details from Gorgias" "search contact and deal info in HubSpot CRM"` in Bash. #### Step 2: Gather context Run these two commands. They do not depend on each other, so you can run them as two parallel Bash calls: 1. `composio execute GORGIAS_GET_TICKET -d '{"ticket_id":""}'` — Get the ticket with the refund request 2. `composio execute HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA -d '{"email":""}'` — Look up the customer in CRM If the user gave only an email, find the ticket first, then run command 1 with its ID. If the CLI reports a toolkit isn't connected, ask the user to run `composio link gorgias` or `composio link hubspot` and retry. #### Step 3: Deep dive on customer Parse the JSON output from Step 2. From HubSpot, pull: - Account tenure (how long they've been a customer) - Plan/subscription details - Total lifetime value - Previous refund history (search engagements) - Current deal status #### Step 4: Assess and present ``` ## Refund Request Assessment ### Request Details - **Ticket:** #[ID] - **Customer:** [name] <[email]> - **Requested amount:** $[amount or "full refund"] - **Reason stated:** [customer's reason] - **Date requested:** [date] ### Customer Profile - **Customer since:** [date] - **Plan:** [plan name] at $[amount]/[period] - **Lifetime value:** $[LTV] - **Previous refunds:** [count] totaling $[amount] - **Account status:** [active/churned/at-risk] - **Open deals:** [any upsell/expansion in progress] ### Eligibility Check | Criteria | Status | Notes | |----------|--------|-------| | Within refund window | Yes/No | [policy details] | | Valid reason | Yes/No/Partial | [assessment] | | Previous refund history | Clean/Flagged | [details] | | Account standing | Good/Flagged | [details] | ### Recommendation **Action:** [Full refund / Partial refund / Credit / Deny with alternative] **Reasoning:** [Why this recommendation] **Retention risk:** [High/Medium/Low if denied] **Suggested alternative:** [If not recommending full refund, what else to offer] ### Draft Response to Customer [Pre-written response for either approval or denial scenario] ``` This skill does NOT process the actual refund - it prepares the case for a human to approve. Policy rule: use only the refund policy the user pasted. If none was given, write "Not checked: no policy given" in the refund window and valid reason rows, and say what you need to complete them. Never assume a window or rule. Manager threshold: flag the refund for manager approval when it is above the amount the user named. If the user named none, say "No approval threshold given" and ask for one. ### 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 and HubSpot customer briefing writer](https://useaiblocks.com/skills/gorgias-and-hubspot-customer-brief). - The [Refund rate analyzer](https://useaiblocks.com/skills/refund-rate-analyzer). 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.