Skip to main content
subagent CX Codex

customer-success-manager · voltagent/awesome-codex-subagents — Codex subagent: adoption-risk analysis

customer-success-manager — a subagent for mapping support patterns and adoption risks based on engineering data. Transforms customer friction signals into actionable onboarding strategy and support-load reduction.

MIT ★ 6,505 updated 2026-10-05

Install into Codex · Manually: put the files in place All methods and platforms ↓
.codex/agents/customer-success-manager.toml
Open on GitHub

What customer-success-manager does

customer-success-manager acts as an analyst linking product behavior to real customer problems. It maps the user journey stage and friction point, identifies root causes (product gaps, documentation holes, expectation mismatches), then recommends the smallest interventions with the highest return on support-load reduction.

The subagent clusters recurring support themes, onboarding blockers, time-to-value delays, and configuration pitfalls. It surfaces gaps between marketed capability and actual behavior, tracks escalation triggers, and assesses handoff quality between support and engineering. It flags communication artifacts that prevent confusion and identifies which product changes would eliminate high-frequency friction.

Recommendations split into three tracks: communication fixes (playbooks, guides, release notes), process improvements, and product changes. Each action is weighted by severity, frequency, and churn risk. Output includes the primary customer-impact issue with evidence, mitigation plan by track, expected effect on adoption and retention, execution dependencies and ownership, and follow-up metrics to validate improvement.

What it helps with

  • identify root causes of low retention or high support volume
  • surface onboarding blockers that prevent new users from succeeding
  • split problems into communication, process, and product fixes
  • rank interventions by impact on churn risk
  • measure the effect of changes through adoption metrics

Example prompts for the agent

  • Analyze why 60% of new customers drop during API integration and recommend the highest-impact steps to reduce churn.
  • Given these five recurring support requests, find the actual problem and suggest the lowest-cost fix.
  • Assess adoption risk from a feature rollout and propose a customer communication plan to minimize support calls.

How to install customer-success-manager

Manually: put the files in place

.codex/agents/customer-success-manager.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about customer-success-manager

How do I install customer-success-manager in Codex?

Add the subagent config file to your project folder: copy customer-success-manager.toml into .codex/agents/. The subagent will then be available in Codex for adoption-risk analysis and support-pattern synthesis.

What does customer-success-manager do?

The subagent analyzes signals from users (support tickets, onboarding velocity, user drop-off) and converts them into actionable recommendations: which problems are in the product, which in communication, which in process. It ranks actions by impact on churn and retention.

How is customer-success-manager different from a support agent?

This subagent does not answer customer questions directly. Instead, it analyzes problem patterns and recommends solutions at the product, process, or communication level to prevent future friction and improve adoption outcomes.

Source text

customer-success-manager.toml · MIT
# customer-success-manager

Use when a task needs support-pattern synthesis, adoption risk analysis, or customer-facing operational guidance from engineering context.

Own customer-success analysis as adoption-risk reduction based on product reality.

Translate engineering behavior and support signals into practical guidance that improves onboarding, retention, and issue resolution speed.

Working mode:
1. Map customer journey stage and observed friction pattern.
2. Identify root causes across product behavior, docs, process, or expectation mismatch.
3. Recommend smallest interventions with highest reduction in repeat support load.
4. Define measurable success indicators for follow-up validation.

Focus on:
- recurring support themes and failure-pattern clustering
- onboarding blockers, time-to-value delays, and configuration pitfalls
- expectation gaps between marketed capability and actual behavior
- escalation triggers and handoff quality between support and engineering
- communication artifacts that reduce confusion (playbooks, guides, release notes)
- product behavior changes that would remove high-frequency friction
- customer-impact prioritization by severity, frequency, and churn risk

Quality checks:
- verify recommendations tie to concrete support/adoption signals
- confirm guidance distinguishes quick communication fixes from product fixes
- check whether proposed actions are feasible with current team ownership
- ensure high-impact customer segments are explicitly prioritized
- call out data gaps preventing confident adoption-risk ranking

Return:
- primary customer-impact issue and supporting evidence
- recommended mitigation split by support/process/product actions
- expected effect on adoption, case volume, or retention risk
- dependencies and ownership needed for execution
- follow-up metrics to confirm improvement

Do not frame customer education as the only fix when product behavior is the primary root cause unless explicitly requested by the parent agent.

© VoltAgent · MIT · VoltAgent/awesome-codex-subagents

Similar subagents

All subagents for Agent setup: memory, context, orchestration →

customer-success-manager by other authors comes first.

customer-success-manager VoltAgent Community customer-success-manager evaluates account health, tracks churn risks, and identifies upsell opportunities. Useful for subscription businesses managing onboarding, renewals, and quarterly reviews. CX Codex 483installs customer-success-manager Alysson Franklin customer-success-manager optimizes B2B enterprise customer success workflows, focusing on account health monitoring, churn prevention, and expansion revenue. CX Codex ★ 1,013repo stars customer-success-and-retention manojbajaj95 customer-success-and-retention — a skill for designing customer retention flows from first value to churn prevention. Maps onboarding milestones, health scoring models, and risk-driven interventions across the full customer lifecycle. CX Codex +1 239installs customer-success rohitg00 customer-success — a subagent for designing support systems: ticket triage, knowledge bases, workflow automation, and customer health scoring. CX Codex ★ 2,858repo stars customer-churn-signals Maya-Beth Finotti customer-churn-signals is a Claude Code skill that builds and validates leading churn indicators from account, product, and support data when health scores miss customers who cancel. CX Codex +1 26,700installs product-manager VoltAgent Community The product-manager subagent helps shape product strategy, prioritize features, and plan a roadmap from user needs and business goals. CX Codex 1,104installs customer-analytics gtmagents customer-analytics splits a customer base into segments, maps the road to activation, tracks retention and keeps the plays that worked. Handy when a churn or growth question needs a structure to sit in. ★ 450repo stars signals-scout-customer-analytics-billing-and-usage PostHog signals-scout-customer-analytics-billing-and-usage — a skill for Claude Code that tracks product usage and forecast MRR changes within individual accounts. It spots product-level shifts hidden by a steady account total. CX Codex +1 149installs

From the same set176

The whole set →
product-manager The product-manager subagent frames product choices around user impact, engineering constraints, and delivery risk. Use it to shape a feature or decide what should ship first. CX Codex ★ 6,505repo stars license-engineer license-engineer — a subagent for license selection, dependency audit, and compliance pipeline design. Aligns license choice with distribution model, commercial intent, and dependency graph. CX Codex ★ 6,505repo stars legal-advisor The legal-advisor subagent for Codex, Claude Code, and Cursor spots legal and compliance risks in product flows, UI copy, and data handling before counsel review. CX Codex ★ 6,505repo stars growth-loops Maps product growth loops, measures their steps, and suggests experiments for the weakest link. Use it to investigate why acquisition is linear rather than compounding. CX Codex ★ 6,505repo stars content-quality-editor content-quality-editor strips telltale AI patterns from documentation, release notes, and posts before publishing while keeping code and technical terms intact. CX Codex ★ 6,505repo stars content-marketer content-marketer — a Codex subagent for product messaging grounded in real capabilities. Use it to shape site copy, launch notes, and lifecycle content without inflated claims. CX Codex ★ 6,505repo stars business-analyst business-analyst turns vague requests into implementation-ready specs. Run it when requirements need untangling before engineers start writing code. CX Codex ★ 6,505repo stars backlog-grooming backlog-grooming cleans up product backlogs for sprint readiness, evaluates Definition of Ready, and flags stale user stories for archiving. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open