Write a saved reply for a common support question
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.
32 reviewed prompts.
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.
Reviews an executive's upcoming calendar and request backlog against their priorities and recommends what to keep, delegate, shorten, or decline, with draft replies. Use for weekly planning by executives or the people who support them.