Skills RevOps

Renewal risk from the support record

A renewal conversation is usually prepared from the last few tickets and the CSM's impression. Both are dominated by recency, and both miss the thing that actually decides these outcomes: the cumulative experience, and specifically whether the things this account was promised happened.

RevOpsRevenue signalPlaybookAny helpdeskRead-only
Installnpx rulebase-skills install cx-renewal-risk-review

When to use it

Reach for this when someone says any of these — they are the phrases the skill itself triggers on:

  • prepare for this renewal
  • what has this account's support experience been
  • which accounts are at risk before renewal

How it works

The method, in the order the skill runs it. The full procedure — tables, worked examples and the edge cases — is in the skill itself.

  1. Build the record over the whole term, not the last quarter

    For the full contract term, or at least twelve months: Unresolved and repeat contacts, Complaints, formal or informal.

  2. Promises made, and whether they were kept

    This is the highest-value part of the review and it is almost never done, because it requires reading transcripts rather than aggregating fields.

  3. Whose experience is it?

    An account is several people, and their experiences differ in ways the aggregate hides.

  4. Output: a brief the account owner can act on

    The deliverable is not a score. It is a short document with evidence attached, because the CSM has to hold this conversation with the customer.

Related skills

Free and open source, and vendor-neutral — it reads the conversations from whichever helpdesk you already run. Browse all 149 skills · connect your helpdesk over MCP · source on GitHub

Review every conversation. Act on what it finds.

AI for customer operations, built for financial services. Specialist agents chase every issue to resolution and every stalled customer to activation.

Rulebase dashboard