Tags each support ticket with one main topic, urgency and the team that should own it, the same way every time, and explains the choice in one line. Use when sorting a support inbox or cleaning up tags before a report.
Writes a first reply to a feature request that thanks the customer, confirms you understood the need, shares an existing workaround and is honest about status. Use when customers ask for features and you must stay truthful about plans.
Summarises a long support thread into a hand-off note: the issue, timeline, what was tried, promises made and what the next person must do. Use when a ticket moves to another agent or team so the customer never has to repeat themselves.
Explains computer, account and security problems in plain steps and everyday words. Use when helping someone who is not comfortable with technical or security terms.
Drafts a short public reply to a negative review, plus a private follow-up message and an internal note on whether to respond. Use when a bad review needs a professional answer that protects the customer's privacy.
Creates three realistic practice scenarios with customer messages, hidden facts, what good looks like and common mistakes. Use for onboarding new agents or running a short coaching session.
Groups open-ended survey comments into themes with counts, quotes and suggested fixes, plus what is working. Use when you have a batch of customer comments and need clear priorities for the support or product team.
Writes a reusable saved reply (macro) for a question your team answers often, with fill-in spots, a short and a long version and notes on when not to use it. Use when you keep typing the same answer.
Writes a clear FAQ with the questions customers actually ask, grouped by topic, plus a list of facts you still need to confirm. Use it for products, services, events or policies.
Turns a description of a device, app or network problem into an ordered, low-risk checklist of fixes with a clear point to stop and escalate. Use it when something tech-related stops working.
Writes an honest apology for a late order with the reason, the new estimate you supply and the options you have approved. Use when an order will arrive later than promised and the customer needs a clear update.
Turns a heated customer message into a calm reply that acknowledges the impact, sets out what happens next and suggests what to say if you call them. Use when a customer is upset, repeating themselves or threatening to leave.
Customer supportsupport
PL Prompier Library ☆☆☆☆☆ New 0
Not finding what you need?
Browse another category or share your own prompt with the community.