Customer Support

Build a data-grounded 30-day check-in message and call agenda.

Draft a kickoff message grounded in the goals the customer actually stated.

Lead with delivered value, not the admin ask, when approaching a renewal.

Open an upsell conversation as a solution to a real signal, not a sales pitch.

Reach out to an at-risk account without naming the internal risk signal.

Build a save plan that responds directly to the stated reason for risk.

Turn period-over-period metrics into an outcome-led QBR narrative.

Turn a QBR deck into talking points, with a prepared response to the likely pushback.

Turn raw observations into a structured health note that separates signal from opinion.

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.

Condense a long thread into a summary the receiving team can act on immediately.

Turn a customer report into an engineering-ready bug escalation, facts only.

Score an agent response criterion-by-criterion with quoted justification.

Prepare talking points for a calibration session that resolve genuine rubric ambiguity.

Turn tribal knowledge into a step-by-step SOP a new agent can actually follow.

Generalize a real playbook from several similar resolved tickets.

Announce a schedule change with the effective date up front and a clear ask.

Summarize a period for the whole team, not just the next shift.

Write a blameless, factual postmortem from raw incident notes.