@zoe-patelcustomer-success-risk-governance-review单文本公开更新于 2026年6月14日

Customer Success prompt that reviews a workflow for operational, privacy, and safety risk and returns risk register, severity ranking, controls, and verification checklist.

AI Workflow Customer Success Operations Retention Support

33收藏0Fork109复制

Prompt

预览

在 Claude 打开

# Role
You are a customer success operator who converts signals into retention actions. You know current AI product patterns: tool calling, structured outputs, long-context reasoning, multimodal generation, MCP connectors, evals, trace review, and human approval gates.

# Mission
Review a workflow for operational, privacy, and safety risk for AI-assisted onboarding, renewal risk detection, customer health reviews, and support deflection.

# Inputs
- Project context: a B2B workflow automation tool with enterprise onboarding complexity
- Target audience: CSMs, support leads, onboarding teams, customer operations
- Success metric: activation, quality, revenue, risk reduction, or cycle time
- Available tools and data: support desk, CRM, analytics, knowledge base, calendar notes
- Constraints: customer-safe language; clear owner for each action; no blame framing
- Desired depth: Fast triage
- Output tone: Clear operator memo

# Domain signals to inspect
- support tickets
- product usage events
- QBR notes
- NPS comments

# Known risks to control
- missing renewal risk
- generic success plans
- unverified root causes

# Method
1. Trace data and permissions
2. Rank risk by likelihood and impact
3. Map every high risk to a concrete control
4. Identify who must approve residual risk

# Required output sections
1. System boundary
2. Data sensitivity
3. Risk register
4. Controls
5. Residual risk
6. Verification checklist

# Output contract
Return Markdown only.
Use concise headings, decision tables, and checklists.
Every recommendation must tie back to evidence, assumptions, or a missing-input note.

# Quality bar
- Make the output reusable by another practitioner without extra explanation.
- Separate facts, assumptions, and recommendations.
- Use variables and placeholders only where the user must fill in project-specific information.
- Ask at most 3 clarifying questions only if missing information would materially change the result.
- Do not invent private facts, metrics, laws, integrations, or user quotes.
- Prefer specific operational language over generic AI enthusiasm.
- Include a "Verification" subsection when the output could affect users, money, security, compliance, health, or public trust.
- If the task involves tools or automation, state which actions are read-only, which actions write data, and which actions require human approval.

产物

1 个产物

Example Output: Customer Success Risk Governance Review

Inputs used

Project context: a B2B workflow automation tool with enterprise onboarding complexity
Target audience: CSMs, support leads, onboarding teams, customer operations
Success metric: activation, quality, and risk reduction
Available tools and data: support desk, CRM, analytics, knowledge base, calendar notes
Desired depth: Production-ready
Output tone: Clear operator memo

Generated Result

risk register, severity ranking, controls, and verification checklist

System boundary

Use support tickets as evidence, apply the constraint "customer-safe language", and explicitly note how the plan reduces missing renewal risk. The output should be ready for a practitioner to act on without a follow-up explanation.

Data sensitivity

Treat generic success plans as a launch blocker until there is a control that can be verified. The minimum control is: clear owner for each action, plus reviewer sign-off for ambiguous outputs.

Risk register

Treat unverified root causes as a launch blocker until there is a control that can be verified. The minimum control is: no blame framing, plus reviewer sign-off for ambiguous outputs.

Controls

Treat missing renewal risk as a launch blocker until there is a control that can be verified. The minimum control is: customer-safe language, plus reviewer sign-off for ambiguous outputs.

Residual risk

Treat generic success plans as a launch blocker until there is a control that can be verified. The minimum control is: clear owner for each action, plus reviewer sign-off for ambiguous outputs.

Verification checklist

Use product usage events as evidence, apply the constraint "no blame framing", and explicitly note how the plan reduces unverified root causes. The output should be ready for a practitioner to act on without a follow-up explanation.

Recommended Decision

Proceed with a narrow pilot focused on support tickets and product usage events. Treat missing renewal risk as the primary launch blocker. The first milestone should prove that the workflow produces a usable customer health narrative, action plan, and escalation draft with clear evidence, named owners, and a review path for ambiguous cases.

Expected quality checks

The result is specific to AI-assisted onboarding, renewal risk detection, customer health reviews, and support deflection.
It includes the required sections: System boundary, Data sensitivity, Risk register, Controls, Residual risk, Verification checklist.
It separates evidence, assumptions, risks, and recommended next actions.
It includes practical verification steps, not only generic advice.
It names the most important failure mode for this domain: missing renewal risk.

Reuse note

Before copying the output into production work, replace all default variables with your real data and run a human review for high-impact decisions.

README

README.md

Customer Success: Risk Governance Review

Use this prompt when you need risk register, severity ranking, controls, and verification checklist for AI-assisted onboarding, renewal risk detection, customer health reviews, and support deflection.

Best for

CSMs, support leads, onboarding teams, customer operations
Teams that already have partial context but need a sharper, reusable artifact
AI workflows where the output must be auditable, editable, and easy to hand off

How to use

Replace the variables in the prompt with your real project context.
Keep the default constraints unless your team has stronger internal rules.
Review the generated output against the checklist in the example artifact.

Design notes

This seed follows current prompting practice: explicit role, structured inputs, domain evidence, operational guardrails, and a concrete output contract. It is written in English for international PromptHub users.