37 reviewed prompts.
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.
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.
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.
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.
Diagnoses a computer, network or account problem with safe, ordered steps in plain language and says when to escalate. Use when something technical is broken and you are not an expert.
Answers an employee's question using only the policy text you provide, says plainly when the policy is silent and points to who to ask. Use when you handle repeat questions about leave, expenses or conduct.
