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.
Writes a short, warm follow-up that checks the fix is holding and makes it easy to reply, plus a chat version and a note on when to stop. Use a few days after you close a ticket.
The assistant plays a non-technical customer with a realistic problem so a support agent can practice, then gives structured feedback when asked. Use for onboarding and coaching sessions.
Writes a kind, clear reply when you have to say no to a refund, exception or special request, explains the reason in plain words and offers what you can do instead. Use for email or chat support.
Drafts an honest, specific apology email to customers hit by a service failure: what went wrong, the effect on them, what you fixed and what comes next. Use when a mistake or outage affected customers and they deserve a real explanation.
Customer supportcommunicationcustomer-service
PL Prompier Library ☆☆☆☆☆ New 0
Not finding what you need?
Browse another category or share your own prompt with the community.