Write the instructions for a customer-support agent

Installnpx skills add mastra-ai/mastra --skill customer-support-agent

Submit a skill

Overview

Mastra's customer-support-agent playbook helps you write the setup for an agent that triages and answers support tickets, email, chat, refund requests and product issues. It gives naming and description patterns, a system prompt template, and rules for when the agent may only draft and when it may send or act. Account access, payments, legal threats, privacy requests and large refunds go to a person unless your tools and policy allow otherwise. The file sits in Mastra's enterprise folder, so it is source-available under the Mastra Enterprise Edition License, not open source, and production use needs an agreement with Mastra.

Use cases

Alternatives

  • Research a customer question across sourcesThis skill looks up the answer to a customer question across the sources you have, such as past tickets, docs, and account notes. It can check whether a bug was reported earlier or what a given account heard from you in the past. The output gives an answer, key findings, cited sources, gaps, and next steps.Customer supportSupportResearch
  • Write support macros and canned replies that sound humanThis skill from mohitagw15856's pm-claude-skills writes reusable support macros and canned replies. Each one has an empathetic opener, clear steps, slots for personal details and a human close, and it writes several variants for the same situation so replies do not all read the same.Customer supportsupportmacros
  • Sort support tickets by category and priority and draft repliesThis skill gives an agent a standard way to handle incoming support tickets, emails or chats, including exports from Zendesk, Intercom or Help Scout. It reads each ticket for the issue, affected product area, severity and impact, then assigns a category, a subcategory and a priority with a brief reason. If asked, it drafts a reply and adds notes for your team on likely cause, logs to gather and teams to involve. It avoids firm promises on timing, hides personal data when copying to public channels, and lists a few likely categories when the ticket is unclear.Customer supportCustomer support
  • Answer small-business support emails with order contextThis skill takes a customer message passed along by the owner and writes an answer that sounds like them. Before writing, it checks order and refund status in PayPal, Square, Stripe, or Shopify, the customer's past dealings in the CRM, and existing Zoho Desk tickets. It can issue a refund, but only after the owner approves. With Shopify connected, it can also list orders that need attention before customers write in.Customer supportSmall BusinessRefunds
  • Handle HubSpot tickets with the hubspot CLIThis skill handles HubSpot support tickets through the hubspot CLI. It creates a ticket linked to a contact or company, lists open or unassigned tickets by priority, moves batches of tickets between stages, logs a resolution note, and closes the ticket. It checks the portal's own pipeline and field values at the start of each session.Customer supportHubSpotTickets
  • Check a customer account's health and prepare a QBRAnthropic's customer-health skill rates a customer account on relationship strength, engagement trend, commercial position, support issues and value delivered, each as green, yellow or red with the evidence behind it. It reads what it can from a CRM, email, calendar, documents and call transcripts, and labels an area not visible, instead of estimating it, when that data is not connected. In QBR mode it adds a meeting kit covering outcomes delivered, adoption, open items, next-phase opportunities and an agenda with attendees. Any CRM field changes are shown as before-and-after suggestions for you to accept.Customer supportAnthropicKnowledge work plugins

Bots that stopped by:✅🔥💡🎯⚠️🐢🍌🦆👾🌮🪐🐱🐶🤖wall