Support-to-Expansion Goldmine Playbook 2026

Three tags do all the work: feature-request, plan-limit, and api-limit. The play fires when a ticket wears one, carrying the topic, the requester's role, how many times this account has asked, and the plan they're on.

• Tag hygiene is the whole play. A 15-minute weekly triage of untagged tickets beats any AI classifier you won't maintain — one support lead, Friday morning, sweep the week's closed tickets for misses.
• Limit-hit tickets are the purest signal in the queue: nobody complains about a ceiling they aren't touching.
• Capture the requester's role at tag time. An admin asking about SSO and an intern asking about SSO are different tickets wearing the same tag.

A feature request is only pipeline if the account behind it is thriving. The tagged ticket picks up four fields from Accoil before anyone routes it:

• Engagement score — is this account genuinely using what they already pay for? A request from a 75-scoring account is expansion; the same request from a 30 is a save conversation wearing a sales costume.
• Active-seat trend — growing seats plus a limit-hit ticket is the strongest expansion combination in the book.
• Feature the ask maps to — which tier, add-on or SKU actually answers it. If nothing on the price list does, it's feedback, not pipeline.
• Plan gap — the distance between what they're on and what the request requires. A one-tier gap closes in a call; a three-tier gap needs a deal.

The classic mistake this step kills: chasing requests from struggling accounts asking for parity features. They're not buying more — they're explaining why they might leave. Route those to the risk play, not the AE.

One rule, readable by anyone: engagement score above your healthy bar, seats flat or growing, and the request maps to something you sell. All three true → PQL. Anything else → the feedback pile. Write the rule down and put it in the runbook; the moment routing needs a judgment call, tickets start dying in the queue while people debate them.

Post to #expansion-pqls and tag the account's AE or CSM. The message carries the ticket verbatim — not a summary — plus the usage context: score, seat trend, current plan, and the plan gap. The verbatim matters because it's the opener; a paraphrase launders out the urgency the customer wrote in themselves. A shared channel beats a DM: unclaimed PQLs are visible, and the sales lead can see the queue producing pipeline in real time.

Not-qualified requests still matter; they're just not pipeline yet. File them to the product feedback pile with the account context attached — plan, score, segment — so product can weigh requests by the revenue behind them instead of counting raw votes. And keep the tag history: an account whose "no" turns into three requests in a quarter re-enters the play with frequency as the signal.

The AE's opener writes itself: "You asked whether the API limit can go higher — here's what the next tier unlocks." No discovery call, no "checking in," no pitch deck. The customer stated the need; the AE's job is to answer it.

• 5-day SLA from ticket to first touch, and track it. The window matters because the customer's problem is still hot — at day 5 they're comparing options, at day 30 they've built a workaround and the deal is dead.
• Reference the ticket number in the outreach. It signals the org actually reads what customers write, which is worth more than the feature.
• If the request needs product work that's genuinely coming, say when. A dated "Q3" beats an evasive "on the roadmap" every time.

Create the opportunity in Salesforce with a dedicated source value — support-sourced — not "outbound," not "customer success," not whatever the default is. This is the step most teams skip and it's the one that changes the org: once "support-sourced pipeline" is a first-class number on the revenue dashboard, support stops being a cost center in the org's head. Attach the ticket link to the opportunity so the deal review can read the original ask.

Roll it up quarterly: dollars of pipeline sourced from support, conversion rate from tagged ticket to opportunity, and average time-to-first-touch. Most teams running this play find the ticket-sourced deals close faster than outbound-sourced ones — the customer opened the conversation, after all. When that shows up in the data, the case for staffing support properly makes itself.