Complaint Resolution
Customer support skill, available on Zeplik
Complaint Resolution is a ready-to-run customer support skill on Zeplik. Pulls customer history, drafts a tone-matched response for approval, and flags pattern complaints with a fix. Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer. It returns a structured document you can keep and reuse: Document artifact -- structured written deliverable with headed sections and a TL;DR (see artifact-templates/document.md).
The Complaint Resolution skill loads automatically when your request matches it, or you can invoke it directly by typing /handle-complaint in any chat. It works with attachments, connectors, and any model that supports the task, so you get the same expert method every time without setting anything up.
What the Complaint Resolution skill can do
- Pull full complaint thread from Gmail or HubSpot by ID or latest
- Summarize customer history, lifetime value, and prior complaints
- Draft a tone-matched response held for owner approval before sending
- Flag recurring complaint patterns with a suggested operational fix
Try these prompts on Zeplik
Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.
How the Complaint Resolution skill works
Run the complaint resolution workflow. 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
- 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
- Draft a reply matched to the severity and the customer's history:
- First-time complainers with high LTV → empathetic, generous
- Repeat complainers → professional, firm, solution-focused
- Abusive tone → professional, brief, boundary-setting
- Include: acknowledgment, explanation (if known), resolution offer, next step.
- Present the draft to the owner. Do NOT send.
Step 4 — Suggest operational fix
- Check if this complaint matches a known theme (from similar past complaints in HubSpot).
- If it's a pattern: "This is the {Nth} complaint about {issue} this month. Consider: {specific operational change}."
- If it's isolated: "This looks like a one-off. No pattern detected."
Connector failures
If Gmail and HubSpot are both unreachable, ask the owner to paste the complaint text — the skill works with manual input. If PayPal is missing, skip transaction lookup and note "PayPal not connected — order status unavailable, working from complaint text only."
Approval gates
- Never send a response without explicit owner approval. Drafts only.
- Never issue refunds or credits automatically. Present the option; the owner decides.
- Never close tickets or resolve disputes without owner confirmation.
Output
Present the customer context summary, the drafted response, and any pattern-based operational suggestion. Ask: "Want to send this response, edit it, or handle it differently?"
How to use the Complaint Resolution skill
Sign in to Zeplik
Create a free Zeplik account or sign in. New accounts start with free credits, so you can try the Complaint Resolution skill right away.
Describe your customer support task
Ask in plain language, or type /handle-complaint to invoke the skill directly. Zeplik recognizes the Complaint Resolution skill and applies its method.
Review and refine the result
Zeplik returns a structured document you can edit, download, and reuse. Ask follow-ups to refine it.
Source and credit
- Author
- Anthropic
- License
- Apache-2.0
Adapted from the open-source anthropics/knowledge-work-plugins project and tuned to run natively on Zeplik. View source on GitHub.
Frequently asked questions
- What is the Complaint Resolution skill?
- Complaint Resolution is a ready-to-run customer support skill on Zeplik. Pulls customer history, drafts a tone-matched response for approval, and flags pattern complaints with a fix. Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer. It returns a structured document you can keep and reuse: Document artifact -- structured written deliverable with headed sections and a TL;DR (see artifact-templates/document.md).
- How do I use Complaint Resolution on Zeplik?
- Sign in to Zeplik and ask in plain language, or type /handle-complaint in any chat to invoke it directly. The skill applies its method and returns a result you can refine in the same conversation.
- Which AI model does the Complaint Resolution skill use?
- Any model you choose. Zeplik works across every model in one chat, so the Complaint Resolution skill runs on your preferred model for the task.
- Where does the Complaint Resolution skill come from?
- The Complaint Resolution skill is adapted from the open-source anthropics/knowledge-work-plugins project (Apache-2.0) and tuned to run natively on Zeplik. The original source is linked on this page.
- How much does the Complaint Resolution skill cost?
- Using the skill is free to start. You only spend Zeplik credits when the assistant runs, and new accounts begin with free credits.
Related customer support skills
- Customer Feedback PulseUse when the user wants to know how customers feel overall -- 'what are customers complaining about lately', 'summarize this month's reviews and tickets' -- themes with verbatim quotes and a top-3 fixes list with drafted replies. Not for one account (use customer-research) or escalations (use customer-escalation).
- Customer ResearcherUse when a support agent needs to research a customer question or account history -- "has this bug been reported before", "what did we tell this account previously", "look this up before I reply". Multi-source research with source attribution. Not for sales prospect intel (use account-research).
- Escalation HandlerUse when a support issue must be escalated -- a bug needs engineering attention, multiple customers hit the same issue, a customer threatens to churn, or an SLA is blown: "escalate this to engineering", "package this for leadership". Builds a full-context escalation.
- Help Center Article WriterUse when the user wants a knowledge base or help-center article written from a resolved issue -- "turn this ticket into a KB article", "document this workaround", "this question keeps coming up, write a help doc", "publish a known-issue notice".
- Support Reply DrafterUse when the user needs a customer-facing support reply drafted -- "customer is furious about a double charge, help me respond", answering product questions, outage or escalation responses, delivering bad news like a delay or won't-fix, declining feature requests, billing replies.
- Ticket TriageUse when the user asks to triage or prioritize a support ticket -- "triage this ticket", "what priority is this issue", "who should handle this", "is this a duplicate or known issue". Categorizes, assigns P1-P4 priority, and routes to the right team.
More on Zeplik
Try Complaint Resolution on Zeplik
Every model, one chat. Bring the Complaint Resolution skill into your next conversation and let the assistant do the work.