Support Agents

Draft a clear, correctly-toned reply to a support ticket.

Adjust an existing draft to the right tone without changing what it says.

Open a reply to an angry customer without generic "I understand your frustration" language.

Draft an apology that leads with ownership, not a buried fix.

Convert a one-off reply into a variable-driven macro the whole team can reuse.

Flag outdated, redundant, or unclear macros and recommend fixes.

Explain a refund or policy decision clearly, without sounding condescending.

Draft an internal note requesting an exception, including the precedent risk.

Turn raw notes into an urgency-ordered handoff for the next shift.