Skills RevOps
Expansion signal in support conversations
Customers tell support things they never tell sales. They hit a plan limit, ask whether a feature exists on a higher tier, mention a new team that wants access, or ask an integration question that only makes sense if they are about to scale up.
npx rulebase-skills install cx-expansion-signalWhen to use it
Reach for this when someone says any of these — they are the phrases the skill itself triggers on:
- “find upsell opportunities in support”
- “customers hitting plan limits”
- “which accounts are asking about enterprise features”
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.
Signal classes, strongest first
Capacity and limit signals — hit a usage cap, seat limit, rate limit, or storage quota. The strongest class: it is objective, it is in the product data as well as the conversation, and the customer has already experienced the constraint.
The frustration test
The same sentence is an expansion signal or a churn signal depending on context, and getting it backwards is the expensive error.
Hard exclusions
Build these before the detector, not after the first complaint: Any account with an open complaint or unresolved escalation, Any account that has given notice, or asked about cancelling, Any conversation on a regulated topic where a sales approach would be.
Measure outcomes, not signals
Signal count is a vanity metric. The chain that matters.
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
