| name | handle-complaint |
| description | Handles an incoming customer complaint end-to-end — pulls context, drafts a response, and suggests an operational fix. Accepts optional email or ticket ID argument. |
| allowed-tools | Read, WebFetch, Bash |
Run the complaint resolution workflow by chaining two skills. Read the complaint, gather context, draft a response, and suggest a fix so it doesn't happen again.
Parse arguments:
EMAIL_OR_TICKET_ID (optional) — Gmail thread ID, HubSpot ticket ID, or "latest" to pull the most recent unresolved complaint. If omitted, ask the owner to paste the complaint text.
Step 1 — Load the complaint (ticket-deflector)
Using the ticket-deflector skill workflow:
- If an ID was given: pull the full thread from Gmail or HubSpot.
- If "latest": pull the most recent unresolved HubSpot ticket or Gmail thread tagged as complaint/support.
- If neither: ask the owner to paste the complaint text directly.
- Identify: customer name, order/account info, what they're upset about, what they're asking for.
Step 2 — Pull context
- Search HubSpot for the customer's history: past purchases, prior complaints, deal stage, lifetime value.
- Search PayPal for relevant transaction: order status, refund history, dispute status.
- Summarize: "This is a {new/returning} customer, ${lifetime_value} in purchases, {0/N} prior complaints. Their current issue is {one sentence}."
Step 3 — Draft response (ticket-deflector)
Using the ticket-deflector skill workflow for tone-matched response:
- Draft a reply matched to the severity and the customer's history:
