Agent skill · marketing growth · anthropics
ticket-deflector
Reads a forwarded customer email or ticket, pulls order/refund status from PayPal and account history from HubSpot, drafts a tone-matched reply in the owner's writing voice, and can issue a PayPal refund with explicit owner approval. Use when the user says "draft a response," "answer this customer," "where's my order," or "I want a refund.
Why this skill is useful
Adds a complete automated workflow for handling customer inquiries and refunds, integrating with PayPal and HubSpot, which the AI cannot generate on its own.
What it needs
Requires gmail installed locally. Requires hubspot, paypal account access. About 3k tokens when loaded. Last updated 2026-08-07. 23,345 stars on the source repository.
What this skill does
Ticket Deflector Quick start Forward or paste a customer email — Claude pulls order status from PayPal, looks up the customer in HubSpot, and drafts a reply in the owner's voice. If a refund is needed, it stages the details and waits for explicit approval before issuing anything. Workflow 1. Read the customer message. Accept a forwarded Gmail thread or pasted text. Extract: customer email address, name, order or transaction ID (if present), and the core issue — refund request, order status question, or general complaint. If multiple issues are present, address them in the order they appear. 2. Pull order status from PayPal. Search PayPal transactions by customer email or transaction ID. Capture: amount, date, status, and whether a refund has already been issued. If PayPal is not connected, note it in the draft and continue. If no transaction matches, flag it — do not guess at a match. PayPal rate limit: If the customer provided a transaction ID, use it — single-record lookups avoid throttling entirely. If searching by email, use a 7-day window (not 30 days). PayPal's transaction list endpoint throttles aggressively on wide date-range queries; back-to-back tickets in the same session will hit this limit if the window is too broad. If Intercom is connected, check for open support tickets from this customer. If Square is connected, check Square transaction history as a secondary source. If multiple transactions match, surface all of them and ask the owner which one applies before drafting. 3. Pull customer history from HubSpot. Search contacts by email address. Pull: lifecycle stage, notes, open deals, and recent activity. If no contact exists, note it and offer to create one after the reply is sent — do not create during the response workflow. 4. Draft the reply. Write in the owner's writing voice. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills anthropics/ticket-deflector