Last week I argued that the old support model doesn’t deserve saving, and that support has little standing to justify its existence as it operates today. It comes across as hard—but that’s why this series exists: to offer an unfiltered view of the support industry as I see it.

It’s easy to make bold claims, and irresponsible to say stop doing what you’re doing without offering a path forward.

If you buy into my observation that AI will increasingly take on the triage, troubleshooting, and resolution of a greater portion of support’s current workload; and that the fundamental economics of the tech sector will transition to outcome-based pricing where customers pay for what they use and the outcomes they achieve, then I hope you concur that support must change, quickly.

Change to what is the key question.

I have outlined the future destination—a concrete picture of what reinvented support actually does. Not a vision statement, but a description of the work support needs to transition to.

Be open-minded as you read it. This type of change is not easy, but it is necessary. Most support teams already do some of the work that will lead them into the future—proactive outreach and friction pattern detection. But these are not the core of what support does; they get starved because reactive demand consumes the capacity. That is the real obstacle—and the pivot is committing to break this reactive cycle.

Reinvention isn’t an iteration of the current model. It’s changing the fundamental core of what support does, at scale—prevention and proactive, outcome-driven work as the mission, with ticket management as a means to handle this work, not the work itself.

Support reinvented: it engages before the customer asks

Today’s support waits. A customer hits a wall, opens a case, and the clock starts. The model is fundamentally reactive—it cannot act until something has already gone wrong.

Reinvented support engages before the customer hits the wall. It watches for the signals that a customer is stalling—dropping usage, an abandoned configuration, a feature bought but never adopted—and reaches out while the problem is still small. The unit of work shifts from the case the customer opened to the outcome the customer is trying to reach.

Support reinvented: it closes technical gaps at scale

Today’s support resolves issues one at a time. A customer struggles, support helps that customer, the ticket closes, and the issue may be documented as a technical article for the knowledge base—but the same source of customer friction continues to generate issues for other customers.

Let’s face it: knowledge bases are a band-aid. They offer the possibility of a solution, provided the customer can find the right article, then interpret and apply it correctly. A knowledge base scales the delivery of an answer—the same answer to many customers—but it never solves the root cause of the friction.

Reinvented support treats a recurring technical gap as a problem to eliminate, not a ticket to re-close or a knowledge article to write and update. It identifies the friction patterns blocking adoption across many customers, and it closes them at the source—through proactive enablement and product improvements aimed at eliminating friction, not just adding features. Support’s ability to detect patterns and drive action turns one customer’s struggle into every customer’s prevented problem.

Support reinvented: it drives consumption and outcomes, not satisfaction

Today’s support optimizes for a satisfied customer. But satisfaction measures the interaction—was it pleasant, was it fast—not whether the customer is any closer to the value they bought the product for.

Reinvented support optimizes for the outcome. Did the customer adopt the capability? Are they consuming what they purchased? Did the engagement move them toward the result that makes them renew and expand? A customer can be perfectly satisfied with a courteous interaction and still be nowhere—and in an outcome economy, that customer is a churn risk regardless of the high CSAT score.

Support reinvented: it proves its value in the language of revenue

Today’s support reports activity—volume, speed, cost. It speaks in the language of operations to an executive team that makes decisions in the language of revenue. The translation never happens, so support is heard as a cost.

Reinvented support measures and proves the value it creates: the revenue protected when it stabilizes an at-risk account, the consumption driven when it closes an adoption gap, the expansion enabled when it gets a customer to an outcome. It walks into the business review with evidence of customer outcomes delivered, not activity. You cannot make this pivot until support can prove, in terms the business acts on, that it plays a vital role in the AI economy.

Support is built for this

Reactive becomes proactive. One-at-a-time becomes at-scale. Satisfaction becomes outcomes. Activity becomes proven value.

None of these are possible with a reactive, break-fix-focused model. Each is a different orientation—toward the customer’s result, the business’s revenue, and support’s own evidence of impact. That is what reinvention means. Not a better-run ticket queue.

Support must reimagine itself as a function built to drive growth—and it is the right function to do it.

As AI makes products more capable and more complex, the gap between what a customer bought and what they can actually make it do becomes a technical gap—and closing it takes technical depth. That is support’s ground—work that functions optimized for relationship management are not built to do.

The capability already exists inside most support teams: the technical expertise, the customer knowledge, the pattern recognition. What’s missing isn’t capability. It’s the decision to point it at the work that matters, and the data to prove it works.

That decision is yours to make. The picture above is what’s waiting on the other side of it.