Skills RevOps
Handing a revenue signal from support to the account owner
Detecting expansion and churn signal in support is the easy half. Almost every programme fails on the other half, and it fails in one of two directions.
npx rulebase-skills install cx-support-to-revenue-handoffWhen to use it
Reach for this when someone says any of these — they are the phrases the skill itself triggers on:
- “route upsell leads from support to sales”
- “support-sourced pipeline process”
- “should agents flag opportunities”
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.
The one structural rule
Agents flag. Agents do not sell.
Never do these
Each of these has a specific failure attached.
Make flagging cost nothing
The flag has to be cheaper than not flagging, or it will not happen on a busy day.
Close the loop, or it dies
This is the fix for the decay failure, and it is the single highest-leverage part of the design.
Measure the programme, including its cost
Four numbers, and the fourth is the one that gets forgotten: Flag rate, per agent and per team. Watch for the two failure shapes, Conversion, The guardrail.
When to shut it down
Say this up front, because it makes the programme safer to start: Acceptance rate stays low after a precision fix, The guardrail metric degrades and does not recover, Flag rate collapses despite a working feedback loop.
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
