Customer Support

Resolve the issue without sounding scripted; preserve brand voice.

Acknowledge specifically, take responsibility, offer concrete remedy.

Decide refund / partial / decline with policy-grounded reasoning.

Brief the next agent without making the customer repeat themselves.

Turn 5 recurring tickets into one clear FAQ entry.

Clear, dated, no jargon, no over-promising.

Turn a vague customer "it's broken" into a reproducible engineering ticket.

Reply to a Customer Effort Score survey response — close the loop without being defensive.

Specific, non-desperate winback email to a customer who churned for a real reason.

Turn 10-30 similar tickets into one searchable, scannable KB article with clear scope.

Public-facing support reply: acknowledge in public, resolve in DM, no corporate-speak.

Evidence-grounded chargeback response that wins on facts, not on tone.

What happened, what we did, what we will change. Honest, not defensive.