32 reviewed prompts.
Turns an unclear message like "it is not working" into a short set of easy questions and a ready-to-send message. Use when a customer has not given enough detail to start troubleshooting.
Writes a clear email telling a customer their refund is approved, how much, where it goes and what happens next, using only the details you give. Use when you approve a refund and want the customer to feel looked after.
Drafts a respectful reply to a customer who wants to cancel: it confirms how to cancel, and offers only the alternatives you have approved, without pressure. Use when a customer asks to cancel and you want to keep them only if it genuinely helps them.
Writes a personal, low-pressure check-in message for a customer showing signs of drifting away, based on real account signals. Use before a renewal or after usage falls.
Drafts an honest, kind reply that says no clearly, offers any real workaround and never promises a future feature. Use when a customer asks for something your product does not do.
Drafts a calm, accurate reply to a customer message, classifies the issue, and adds an internal note saying whether to escalate and what information is missing. Use for email or chat support on any software product.
Turns the questions customers keep asking into a clear help article outline with headings, what each section must answer and what to leave out. Use when the same tickets keep arriving and you want a help page to link to.
Turns your incident notes into a clear status page update plus a short social post: what is wrong, who is affected, what to do now and when the next update comes. Use when something is down or degraded and customers are waiting.
Writes a genuine thank-you with a gentle, optional invitation to leave a review, with no pressure or incentives. Use after a customer expressed real satisfaction with your help.
Explains a charge in plain words: what it is, why it happened, what the customer's options are and what you will do next. Use when a customer writes in surprised or upset about an unexpected charge.
Drafts a polite reply that asks for the right proof before changing or revealing anything on an account, without exposing account details. Use when someone asks for an email change, reset or access to an account.
Turns technical engineering notes into a clear, honest message a non-technical customer will understand, with what changed and what they need to do. Use when a fix is done and the notes are full of jargon.
