Support ops improvement program

Support

Use when the numbers should drive the fixes: run the support dashboard, benchmark SLAs, and own the improvement backlog to measured done.

by AutoGPTNewUpdated 12d ago

Instructions

Instructions your experts follow when using this skill.

Use this when the numbers should drive the fixes. Run the support dashboard, benchmark SLAs, and own the improvement backlog to measured done.

What you need

The ticket and call data, the dashboard home and benchmark source from prefs, the current backlog, and the last review's decisions.

Run the program

Read the dashboard in one pass — one speed, one outcome, one sentiment, the cost metrics: volume by channel, first-response and resolution times, SLA hit rate, CSAT (with response rate), first-contact resolution (FCR), reopen rate, abandon rate, occupancy, customer-effort score, net promoter score, and cost per contact and per resolution — each with trend and period. A metric with no source is cut, never estimated. Read average handle time (AHT) alongside FCR, never alone; resolution is not deflection.
Benchmark SLAs against the agreed source (last quarter, peer team, or published standard): where the team leads, where it lags, and the gap in plain numbers. Report SLA compliance (answered-within-SLA / eligible requests, with start/stop rules and exclusions stated) alongside the median and p90 tail — averages hide breach tails. Name the benchmark on every comparison; an unsourced "industry standard" is UNKNOWN.
Mine the top three drivers behind the worst metric: repeat themes with counts and quoted threads, root causes with owning teams. Size each fix: effort, expected lift, owner. Rank by lift over effort.
Stage the backlog moves: the one fix to launch this week with its measure, the one to pilot, the one to kill. Each fix carries a dated numeric target (e.g. cut first-response time by 5s by next quarter). Launches go to the owner for yes with the rollback line attached. Never declare a fix done without its before-and-after numbers.
Log decisions, owners, and dates. Offer the weekly one-pager: metrics, benchmark deltas, backlog moves, next review date. Refresh internal numbers weekly; refresh external benchmarks quarterly.

Output

The dashboard read, the benchmark comparison, the ranked backlog, and the staged launch with its measure.

Fallbacks

No data access means a metrics-UNKNOWN read naming the missing source, with the backlog ranked by owner judgment only. Never chart guessed numbers.

Triggers7

Phrases that help your experts find this skill.

support dashboard readSLA benchmarksupport improvement backlogCSAT trendfirst contact resolution ratecost per contactweekly support one-pager

More skills

Research

Product marketing context

by AutoGPTFrom coreyhaines31/marketingskills/skills/product-marketing

When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing.md` that all other skills reference for product, audience, and positioning context.

1 installedView

Research

Competitor profiling

by AutoGPTFrom coreyhaines31/marketingskills/skills/competitor-profiling

When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.

1 installedView

Research

Customer insight research

by AutoGPTFrom coreyhaines31/marketingskills/skills/customer-research

When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.

1 installedView