Customer support

Finds the top contact drivers in a ticket export and ranks deflection opportunities by volume and effort, with root cause and owner. Use for a monthly or quarterly support review.

Builds reusable support macros from real ticket samples, with personalisation slots, internal actions and rules for when not to use each. Use to speed up replies without sounding canned.

Builds a support quality scorecard with weighted criteria, scoring examples, auto-fail rules, calibration steps and coaching use. For support managers reviewing ticket and chat quality.

Acts as a B2B customer success manager who drives adoption and outcomes, spots churn risk early, runs value reviews and turns customer insight into product feedback.

Designs a support escalation process - tiers, severity definitions, routing, handover templates, SLAs and how engineering is engaged. Use when tickets bounce between teams or urgent issues stall.

Designs a help-centre structure from support ticket topics and existing articles - categories, an article list, naming, search terms, and the gaps to write first ranked by ticket volume.

Designs a support chatbot or AI agent flow - intents, answers grounded in help content, escalation triggers, human handover and quality checks. Use when adding automation to a support team.

Plans B2B customer onboarding from kickoff to first value - milestones, owners, training, success criteria and risk signals, with kickoff and check-in agendas. For customer success teams.

Estimates support staffing from ticket volume, handle time and service-level targets, with a coverage plan by hour, shrinkage, and every assumption and formula stated.

Prepares a customer quarterly business review - outcomes against their goals, usage insights, issues and fixes, relevant roadmap and agreed next steps. For account managers and CSMs.

Writes a public reply to an online review - positive, mixed, unfair or fake-looking - that stays calm, specific and privacy-safe and offers an offline path to resolve it.

Role-plays a difficult customer for support-agent training - angry, confused or demanding a refund - stays in character, then scores the agent's handling against a rubric with examples.

Standing rules for every customer support reply - acknowledge first, plain words, no blame, honest limits, and a specific next step with a timeline.

Writes a task-based help-centre article from a feature description or a support ticket, with numbered steps, screenshot placeholders and troubleshooting. Use to answer a common question once, well.

Writes a customer support reply that resolves the issue or sets a clear next step and timeline, using only the facts and policy you give it, in the brand's tone. Use for email, chat or ticket replies.