37 reviewed prompts.
Reviews a drafted customer reply for tone, clarity and risky promises, then returns a cleaner version. Use when a support agent pastes a draft and wants it checked before it goes to the customer.
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.
Scores a support conversation against your own quality standards, with evidence for each score, strengths and one improved wording. Use when reviewing tickets for coaching or quality checks, and keep it fair and specific.
Condenses a long ticket or email thread into the problem, what has been tried, what was promised and what happens next. Use when a ticket changes hands or a manager needs the picture in a minute.
Turns a week of ticket numbers and notes into a short summary of what changed, the top issues, what customers are saying and what other teams should act on. Use for a weekly support update or meeting.
Produces spoken-style instructions, an intent table, sample dialogues and escalation rules for a phone or voice assistant. Use when setting up or fixing an automated voice line.
Converts a messy customer bug report into a ticket with a title, steps to reproduce, expected and actual results, impact and open questions. Use when support must hand a problem to engineers who cannot ask the customer.
Turns your notes on open tickets and the day's issues into a clear handover with priorities, promises to keep and things to watch. Use at the end of a shift so the next agent can start without asking.
Turns a solved support ticket into a clear self-help article with a plain title, numbered steps and what to do if it does not work, with private details removed. Use when a fix is likely to help other customers.
Drafts an apologetic, honest reply for a customer whose problem has returned, with no empty promises and a note on what to escalate. Use for repeat issues, especially when the customer talks about leaving.
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.
