Convert incomplete adoption and service signals into neutral hypotheses and verification actions without predicting churn. 제공할 내용: Usage and service evidence, Customer context and commitments, Review boundaries. 예상 결과: An evidence-bounded renewal risk register with questions, owners, and non-coercive next steps.
1
맥락 추가
텍스트는 이 브라우저에 유지됩니다. AILesson Prompts는 이를 모델이나 서버로 보내지 않습니다.
2
프롬프트
채워지지 않은 필드는 플레이스홀더로 표시되므로 프롬프트를 복사하고 편집할 수 있습니다
Identify renewal-related risks that require verification, using customer usage information as signals rather than intent.
Dated metrics, definitions, denominators, entitlement, trends, tickets, milestones, gaps, and account changes:
[usage]
Goals, stakeholders, feedback, criteria, contract timing, commitments, constraints, and unknowns:
[relationship]
Risk categories, inference limits, privacy, authority, escalation, and prohibited predictions or pressure:
[review]
Audit metric comparability, coverage, seasonality, instrumentation, user lifecycle, entitlement, and missing baselines before interpreting change. Never infer satisfaction, value, decision authority, budget, or renewal intent from logins alone. Separate observed signal, plausible explanations, counterevidence, missing evidence, and verification question. Cover outcome fit, adoption breadth/depth, workflow dependency, unresolved support, stakeholder/owner change, implementation commitments, commercial timing, security/compliance, and measurement quality only where evidence exists. Rank by potential renewal relevance and time to verify, not fabricated churn probability. Propose respectful discovery, enablement, support, or internal actions; do not manufacture urgency, threaten loss, or recommend dark patterns. Return a risk register, no-risk/positive evidence, measurement caveats, sequenced verification plan, accountable internal owners only when supplied, and escalation conditions.
기본적으로 비공개프롬프트 구성은 브라우저에서 로컬로 이루어집니다. 조직에서 허용하지 않는 한 기밀 정보를 AI 서비스에 입력하지 마세요.
입력에서 결과까지
적용 예시
구체적인 맥락이 이 레시피를 바로 사용할 수 있는 결과로 바꾸는 방법을 확인하세요
실제 입력
Usage and service evidence
Account has 120 licensed seats. Monthly active users: Apr 76, May 81, Jun 79, Jul 48. July collection ended 20 Jul due analytics migration; earlier months are full calendar months, so not comparable. Core approval workflow weekly active teams: 8 of 10 in Apr, 9 in May, 9 in Jun; July unavailable. Export feature used by 3 users monthly. Two open tickets: SSO group mapping since 12 Jun, workaround accepted temporarily; dashboard timezone bug opened 2 Aug. Training attendance 14 of 20 invited managers. No outcome metric instrumented.
Customer context and commitments
Customer bought to standardize approvals across 10 teams. Operations sponsor Priya moved roles 15 Jul; successor unknown. IT owner Marco confirmed workaround until 5 Sep. Renewal date 30 Nov; notice terms not supplied. CSM promised an SSO update by 28 Aug but no status is recorded. Customer has not stated satisfaction, budget, or renewal intent.
Review boundaries
Internal customer-success planning. Do not score churn probability, infer individual performance, or contact users without account-team approval. Risks: outcome, adoption, support, stakeholder, delivery, commercial timing. CSM owns relationship; support owns tickets; legal/procurement confirm terms. Escalate missed commitment or security-impacting SSO issue.
예시 출력
Measurement caveat: July MAU cannot be compared with full months, and July workflow-team data is absent. Therefore the apparent 79-to-48 decline is not a verified adoption drop. Export use is not interpretable without whether export is expected. Positive evidence: 9 of 10 teams used the core workflow weekly in May/June, close to the stated rollout scope.
Verification risks: R1 stakeholder continuity—sponsor changed and successor is unknown; CSM should ask who now owns the approval-standardization outcome and whether criteria changed. R2 unresolved SSO dependency—the workaround expires 5 Sep and the promised 28 Aug update has no status; support must confirm current impact, resolution plan, and whether security escalation criteria are met. R3 outcome evidence—no metric shows whether approvals became standardized; ask customer which observable workflow evidence matters and whether a safe baseline can be agreed. R4 adoption completeness—one of ten teams was not weekly active in May/June; ask neutrally whether that team was in scope, delayed, or uses another process. R5 commercial timing—notice terms are missing; legal/procurement must retrieve them without inventing a deadline.
Sequence today: verify the missed SSO update internally; then CSM confirms successor and outcome criteria in the next agreed contact; repair July measurement before trend discussion; retrieve notice terms. Nothing supplied establishes dissatisfaction, budget risk, or renewal intent.
효과가 있는 이유
1
Signal–hypothesis separation prevents telemetry from being mistaken for customer intent.
2
Verification actions support a useful renewal conversation without manipulative pressure.
결과 확인
Are usage definitions, denominators, entitlement, instrumentation, and time windows checked before conclusions?
Is each risk a hypothesis with alternatives, counterevidence, and a neutral verification question?
Do actions respect customer choice, privacy, authority, and known commitments?
안심하고 사용하세요
자주 묻는 질문
이 레시피를 언제 사용해야 하는지, 무엇을 제공해야 하는지, 그리고 어떤 부분에서 사람의 검토가 여전히 중요한지에 대한 실용적인 답변
What should I prepare before using “Identify renewal risks to verify from customer usage information”?
For “Identify renewal risks to verify from customer usage information,” prepare Usage and service evidence, Customer context and commitments, and Review boundaries. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.
When is the “Identify renewal risks to verify from customer usage information” result not ready to use?
The result is not ready if it does not yet deliver the stated outcome—An evidence-bounded renewal risk register with questions, owners, and non-coercive next steps—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.
Which AI tools have recorded tests for “Identify renewal risks to verify from customer usage information”?
The published test record for “Identify renewal risks to verify from customer usage information” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.
ChatGPT
