Support-to-Expansion Goldmine Playbook 2026
When a customer asks support for a higher limit or a missing feature, they have written down what they want to buy. This play catches the tagged ticket, compares the account with your successful customers, and puts the move on the account in your CRM with the ticket attached: an upgrade conversation, an add-on or seats offer – or no move, with the ask passed to product.
When a customer writes to support asking whether the API limit can go higher, they've put in writing exactly what they want to buy. It's easy to close that ticket with a macro and file it under product feedback.
This play catches those tickets. Asks from accounts at or near your successful customers' benchmark, for something you sell, land on the account in your CRM as a drafted move with the customer's words attached. The rest go to product with the account context.
Measure it on how many tagged asks become a deal, days from ticket to the owner's answer, and support-sourced pipeline and expansion revenue.
How it works10 steps
01SignalTag the tickets that ask for more
Two tags do the work: feature-request and limit-hit. The tagged ticket
brings the ask in the customer's own words and who asked. The ask check
adds their role, how many times the account has asked in the past 90 days,
and its plan and ARR.
- A support lead spends fifteen minutes each Friday sweeping the week's closed tickets for missed tags.
- Record the requester's role. An admin asking about SSO and a trial user asking about SSO are different tickets.
- Only these two tags feed the play. Bug reports and how-do-I tickets never do, and agents solve every ticket exactly as before.
02ScoreCompare the account with your successful customers
Build the benchmark once, refresh it quarterly:
- Comparison customers: same segment (plan tier, size band), 12+ months as customers, renewed at the same or higher revenue. Aim for 20; with fewer, label it low confidence.
- What they do and pay: the median of weekly active users against seats, weekly use of the feature or limit the ask is about, and median ARR. Your CS lead approves it.
- At or near: default, 80% or more of the benchmark on both usage measures, in three of the last four weeks.
The benchmark play has the full method. Check each tagged ticket within two business days (default), against the records:
- Price-list match: a plan, an add-on or more seats that answers it, and its list price – that's the gap value. If nothing on the price list answers it, it's feedback.
- Already paid for? Your account owner confirms whether the contract covers it and records the answer in the CRM. If it does, support answers with a how-to.
- Deal, renewal or cuts: open deals, renewal date and 90 days of notes.
Say an admin at an account paying $12,000 a year writes, "We hit the API limit again – can it go higher?" The account runs at the benchmark, and the higher API tier is a $3,000 add-on. The $3,000 is a comparison, not a forecast. (The numbers are illustrative.)
Under about a hundred accounts, do it by hand.
03DecisionDecide whether there's a move worth making now
Leave it alone if any of these hold (defaults): usage below 80% of the benchmark, nothing you sell answers it, it's already paid for, a deal is open or renewal is inside 60 days (the ask goes into that conversation), or there was a cut or escalation in the last 90 days. Everything else picks a move.
04ActionLeave it alone, and pass the ask to product
Set Recommended move to No move, write the reason in one line, and set Review date. Log the ask to product with the account's plan, ARR, usage against the benchmark and the verbatim, so product can weigh asks by the revenue behind them. An account well below the benchmark asking for more isn't ready to buy – it's telling you what's in the way. Its gap belongs in the weekly check. A third ask in 90 days brings it back for a fresh look (leave it alone).
05DecisionPick the move that answers the ask
- Plan: the answer is a bigger plan. Run it as the PQL handoff runs an upgrade.
- Add-on: the answer is one add-on or more seats. Run it as the seat and add-on play runs it.
If both answer it, draft the cheaper one (default). Seats for a new team belong to the second-department play; usage running past its band before an invoice, to the bill-shock play.
06ActionDraft an upgrade conversation with the ticket attached
A deal on the HubSpot record: current plan to next plan, the price difference as the amount, the requester as contact, Deal source set to Support ticket, and the ticket verbatim and link in the description.
07ActionDraft an add-on or seats offer with the ticket attached
The same, with the add-on or seats named and priced. The verbatim is the opener; don't paraphrase it.
08ActionPing the owner in Slack
One line to the owner in #expansion-asks, linking to the record. The record holds the move; the ping just means nobody waits.
09Human stepYour team decides and answers the ask
The AE or CSM reads the evidence and runs it as drafted, changes it, or passes. Answer within five business days (default) of the ticket, while the need is fresh, and quote the ticket number. Before acting, record the success measure and the review date (default: eight weeks on). A call booked is progress; a paid upgrade or add-on is the result.
10OutcomeReview what changed, then sharpen the benchmark
On the review date, record three answers: did they buy, are they using it, and what else played a part? If nothing moved, change the move, stop it, or give it time – the eight-week review has the full method. Each quarter, report support-sourced pipeline as its own number, and check whether the 80% default is sorting ready accounts from the rest.
Setup and templates
Sources: tags, ask, requester and ticket link from Zendesk: a Zendesk trigger on the two tags sends each ticket (ask, requester, link) to the ask check by webhook, and the ask check writes it to the company record, with the 90-day count from a Zendesk search; usage against the benchmark from a weekly saved query in PostHog, Amplitude or Mixpanel; plan, ARR, deals and notes from the CRM; the price list. Account-level numbers need your analytics tool's account add-on (group analytics in PostHog, Accounts in Amplitude, Group Analytics in Mixpanel) and a group call in your app. Save the query, then subscribe to it (in Amplitude, add it to a dashboard and subscribe to that) so the result lands in your inbox or Slack on the schedule you set. By hand: twice a week, list the new tagged tickets in a sheet beside each account's usage, plan and ARR.
Company properties in HubSpot (Starter or above; free HubSpot allows 10 custom properties in total), or your CRM's account object:
| Property | Type | Filled by |
|---|---|---|
| Latest ask | Multi-line text (verbatim) | Ask check |
| Ask ticket link | URL | Ask check |
| Asks, last 90 days | Number | Ask check |
| Usage vs benchmark | Number (%) | Weekly check |
| Ask maps to | Dropdown select: Plan · Add-on · Seats · Not sold | Ask check |
| Gap value | Number (currency) (list price of the move) | Ask check |
| Recommended move | Dropdown select: Upgrade conversation · Add-on or seats offer · No move | Ask check |
| Move reason | Single-line text | Ask check |
| Success measure | Single-line text | Account owner |
| Review date | Date picker | Ask check, then account owner |
| Review result | Dropdown select: Bought, in use · Bought, not used yet · Didn't buy · Stopped | Account owner |
The automation here uses HubSpot workflows (any Professional hub). On Free or Starter, run the same saved view and create the tasks by hand. Add a Deal source dropdown to deals with a Support ticket value. The weekly list is a saved view: Recommended move is known and Review date is this week or overdue. In HubSpot that's two filter groups: Review date is This week, or Review date is before Today. Each move creates a task for the owner, "Support ask: [move]", with the draft in the body. Slack messages come from a HubSpot workflow (Professional or Enterprise) with the HubSpot Slack app; add the app to any private channel. Only use the "teams your size usually" line if your benchmark supports it; otherwise, describe what you saw on their account.
Upgrade conversation (Plan):
Hi [name] – thanks for ticket [number] about [ask]. [Plan] gives you [what it adds], and teams your size usually move up about here. Worth fifteen minutes to see if it fits, and what it would cost?
Add-on or seats offer (Add-on):
Hi [name] – you asked in ticket [number] whether [ask]. [Add-on or n seats] does that, for [price]. Want me to set it up, or walk you through it first?
Slack ping: "[account] asked for [ask] – [move] drafted on the record: [link]."
Product log: [account] · [plan], [ARR] · usage [x]% of benchmark · asked [n] times in 90 days · "[verbatim]".
No move: "No move – [reason]. Ask passed to product [date]. Recheck [date]."
How Accoil fits
Accoil is a customer-success consultancy with our own tooling, and this is a play we run with you, not for you. We build the benchmark with your team, and you approve it. Every week we check every account in the agreed segment, new tagged asks included, and the recommended move and its evidence land on the account record in your CRM – we recommend HubSpot – at a pace your team can actually run. Your support lead owns the play's two-business-day ticket check, unless you'd like us to take it on. Your team makes every call. Nobody from Accoil contacts your customers. After the agreed window we review what changed together, and you keep the playbook, the benchmark and the analysis.
Running it yourself? Swap Zendesk for Freshdesk (Growth or above) or Help Scout, with a tag rule that sends the same webhook, and HubSpot for Salesforce or Pipedrive. On Salesforce or Pipedrive, the ask check fills Latest ask, Ask ticket link and Asks, last 90 days the same way. The play stays the same. On Salesforce, the field writes need API access (Enterprise and up, or an add-on on Professional). On Pipedrive, automations and date triggers need the Growth plan.
Thirty minutes with Kate, Simon or Peter on one example segment: what a successful customer looks like, where the gaps are, and whether there's work worth doing this quarter.
Talk to a founder →Keep reading
Expansion Signal to PQL Handoff Playbook 2026
Your customers who upgraded showed you what ready looks like before they asked. This play checks every account against them each week, confirms the records before anyone calls it ready, and puts the move on the account in your CRM: an upgrade conversation for your AE, an in-app prompt your team chose to automate – or no move, with the reason noted.
Seat & Feature-Adoption Upsell Playbook 2026
Accounts show what they'd pay more for by how they use what they have. This play compares each account in a segment every week with the customers who bought your add-on or added seats, checks the records before calling it a gap, and puts one move on the account in your CRM: an add-on deal, a seat true-up – or no move, with the reason noted.
Renewal-Risk Radar Playbook 2026
Renewals go best when the account already looks like your customers who renewed. From 90 days out, this play compares every renewing account with them each week – usage and revenue – checks the records, and puts one move on the account in your CRM: an expansion look, a value review, a save plan with the CSM – or no move, with the reason noted.
Every playbook, one download
All 32 workflows as print-ready playbooks — diagrams included. Plus every new workflow as we publish it.