adoption-recovery

Estrelas0

Forks0

Atualizado13 de julho de 2026 às 22:05

Re-engage an account whose product usage has dropped or stalled, recovering adoption before it becomes churn risk.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

scadam

scadam/csm-aiteammate

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Especialistas em gestão de projetosNegócios e Operações Financeiras·SOC 13-1082

SKILL.md

readonly

name	adoption-recovery
description	Re-engage an account whose product usage has dropped or stalled, recovering adoption before it becomes churn risk.
when_to_use	Use for adoption_gap signals, declining logins, or a licensed feature with low seat usage.
allowed-tools	["detect_signals","decide_next_best_action","get_account_context","search_knowledge_base","get_engagement_history","query_csm_database","build_draft","trigger_in_product_message","create_review_task","search_microsoft_365","ask","remember"]

Adoption recovery

A guided-recovery play for accounts where usage has dipped or a feature was never adopted. The goal is to restore momentum with a low-friction, value-first nudge — not to sell.

How to think about it

Anchor on the value, not the feature. Lead with the outcome the customer cares about (time saved, risk reduced), then name the feature as the means.
Make the next step tiny. Offer a 20-minute walkthrough or a single concrete tip the user can try today. Never a multi-step ask.
Use what they've already told you. If VOC or prior notes mention a goal or a frustration, reference it so the outreach feels personal, not templated.
Respect prior contact. Check engagement history; do not repeat content the user has already been shown.

Guardrails

High-influence, frustrated, or strategic accounts → route to CSM review; do not auto-send.
Ground every product claim in approved content only.
Keep it to a few sentences, in the CSM's voice.

Signals this fits

adoption_gap, declining logins, licensed-but-unused features, onboarding stalls.

Mais deste repositório

mesmo repositório

ai-teammate-solution-builder

scadam/csm-aiteammate

Build complete Agent 365 AI teammates from variable scenarios: real Microsoft 365 Agents SDK hosting, OBO and agentic-user identity, A365 observability, generated skills and typed tools, existing MCP or OpenAPI-derived MCP integrations, workflows, review gates, and manager/fleet control planes.

2026-07-170

enhancement-match

scadam/csm-aiteammate

Connect a newly released product enhancement to an account that previously asked for it, turning a release into a credible, welcome update.

2026-07-130

escalation-triage

scadam/csm-aiteammate

Decide what needs the human CSM and how urgently, routing the right items to review and letting routine ones flow at scale.

2026-07-130

renewal-risk-brief

scadam/csm-aiteammate

Prepare a concise risk brief for an at-risk account approaching renewal, so the CSM can intervene with the full picture.

2026-07-130

voice-matched-outreach

scadam/csm-aiteammate

Draft customer outreach that genuinely sounds like the assigned CSM, using their accepted-message style as the anchor.

2026-07-130

name	adoption-recovery
description	Re-engage an account whose product usage has dropped or stalled, recovering adoption before it becomes churn risk.
when_to_use	Use for adoption_gap signals, declining logins, or a licensed feature with low seat usage.
allowed-tools	["detect_signals","decide_next_best_action","get_account_context","search_knowledge_base","get_engagement_history","query_csm_database","build_draft","trigger_in_product_message","create_review_task","search_microsoft_365","ask","remember"]

Adoption recovery

A guided-recovery play for accounts where usage has dipped or a feature was never adopted. The goal is to restore momentum with a low-friction, value-first nudge — not to sell.

How to think about it

Anchor on the value, not the feature. Lead with the outcome the customer cares about (time saved, risk reduced), then name the feature as the means.
Make the next step tiny. Offer a 20-minute walkthrough or a single concrete tip the user can try today. Never a multi-step ask.
Use what they've already told you. If VOC or prior notes mention a goal or a frustration, reference it so the outreach feels personal, not templated.
Respect prior contact. Check engagement history; do not repeat content the user has already been shown.

Guardrails

High-influence, frustrated, or strategic accounts → route to CSM review; do not auto-send.
Ground every product claim in approved content only.
Keep it to a few sentences, in the CSM's voice.

Signals this fits

adoption_gap, declining logins, licensed-but-unused features, onboarding stalls.