Every day your support queue receives messages that are, read correctly, expansion intent: "is there a way to do X?" (X is in the next tier), "we're hitting a limit on Y," "can this connect to Z?" These are customers telling you what they'd pay more for. In most companies, support resolves the ticket and the signal evaporates, because support and expansion are different teams with different systems and no path between them.
Why the signal is lost. Support is measured on resolution and speed, not revenue. An agent answers "can I do X?" with "not currently" and closes the ticket — correctly, by their metrics. Nobody routes the underlying signal ("this customer wants X, which is a paid upgrade") to anyone who can act on it. The expansion intent was captured and then discarded.
The cost. These are the warmest expansion signals you'll ever get — self-generated, specific, in the moment. A customer asking how to do something is far more expansion-ready than one receiving a cold upsell email. Letting those signals die in the support queue while running outbound upsell campaigns is doing expansion the hard way and ignoring it the easy way.
The fix. The signal and the expansion conversation should live in the same place. When the layer handling support also recognizes expansion intent, "we're hitting a limit on Y" becomes a helpful in-the-moment conversation about what the next tier unlocks — service, not a sales pitch — instead of a closed ticket. The warmest signals get acted on where they occur.
Frequently asked questions
What are expansion signals in support tickets?
Customer questions that reveal upgrade intent — asking for a feature in a higher tier, hitting a plan limit, or needing an integration — which are warm, self-generated expansion opportunities.
Why are these signals usually missed?
Because support is measured on resolution, not revenue, and there's no path routing the underlying intent to anyone who can act on it, so the signal dies with the closed ticket.