Words by Marko Avramovic
Reading time 9 min
Look at where the industry actually spends its calendar now. The reveals still pull the crowd, but the work that keeps a game alive lands after the credits roll. Single-player epics ship roguelike modes and full expansions months past launch. Free-to-play titles run on a battle-pass clock. Even a game you “finished” wants you back for the next season, the next event, the next patch. The one-and-done release is close to extinct.
Which is the point. Nobody talks about the day after launch, and the day after launch is where a game is won or lost.
A launch, then a season, then another season. An event, a hotfix, a comeback weekend, a crossover nobody saw coming. A modern game does not ship once; it keeps shipping. The credits stopped being the finish line. And players grade every drop within minutes, in the patch-notes thread and the review score, before the servers have even settled.
Here is the number that should keep every live service team honest. Across more than 16,000 mobile games measured by GameAnalytics in 2025, the median title kept barely one in five players to day two, and fewer than one in a hundred to day thirty. On PC, the median game held under one in ten to day two. The best live service games retain many times that.
When the median game loses four in five players in a week, the distance between the median and the best is no longer a design gap. It is an operations gap.
That gap is the reason the Live Service Gaming Summit lands in London next week. The event bills itself as the leading show for building, operating and growing games that last. Building and operating take most of the stage time. Growing, the part where you keep players long enough to matter, is where player support lives.
Because every season, event and patch arrives with its own wave of players who need something. A login that will not hold. A purchase that did not land. A rule change that lit up the community overnight. Live service does not spread that demand evenly. It stacks it into spikes, right at the moments retention is most fragile.
Delivery, Not Deflection
Talk to any Ops Director running support for a live title and you hear the same line. The hard part is not answering a ticket. It is delivering the same quality of answer, in the right language, at the right hour, on the day everything happens at once.
The money already moved to the model that never stops. The summit’s own State of Live Service Gaming report puts the market at roughly US$13.6 billion in 2026, climbing to about US$22.2 billion by 2031. Growth on that scale does not come from a fresh wave of blockbusters. It comes from keeping the games we already have alive, and spending, for longer. That makes every post-launch player moment a revenue moment.
5CA’s own research across more than 750 gaming companies points the same way. Roughly one studio in three that runs active player support now leans on a specialist partner, and those tend to be the studios with the biggest, most always-on communities. What they hand over is never the thinking. Strategy, product knowledge and community context stay in-house. What they buy in is the part that is hardest to build alone: the languages, the coverage across every timezone, and the surge capacity for the day the live calendar goes off all at once.
On the same data, close to seven in ten of the people doing live service player support today sit with those partners rather than inside the studio whose players they help. That share climbs in a market still working through its cuts. The summit report counts more than 10,000 games industry layoffs in 2023 alone, with more to follow. Leaner internal teams are being asked to cover the same global, always-on demand. Something has to absorb the spikes.
Six Delivery Moments That Test a Live Service Operation
If a live game is a series of launches, support is a series of delivery tests. These six are where an operation that scales pulls away from one that buckles.
1. The Season Drop
A new season goes live. Weeks of marketing land in a single afternoon. Lapsed players flood back, first-timers arrive, and everyone hits the servers, the store and the patch notes at once.
Why it matters for delivery: A season is a mini launch, so it re-runs the retention test from scratch, on players you already paid to win once. Teams that treat the live calendar as a staffing calendar absorb the surge. Teams that staff for the average day turn the best content moment of the quarter into a queue.
2. Prime Time on the Far Side of the World
Your support floor is winding down for the night. Halfway around the world it is peak hours, and a player deep in an event has just hit a wall they can only describe in Korean, or Portuguese, or German.
Why it matters for delivery: Asia-Pacific alone is more than half the world’s players, and the top ten gaming markets, spanning at least seven languages, make up close to four fifths of global revenue. A late shift built around one timezone and one language is a late shift built for a minority of your game.
3. The Store Goes Down Mid-Season
The store update ships. A price is wrong, an item does not grant, or a bundle charges twice. In a live economy money moves constantly, so a small store bug becomes a wave of trust problems in minutes.
Why it matters for delivery: When in-game purchases carry the business model, a broken store is not a support ticket. It is an interruption to revenue. Fast, clear billing help protects the money and the reputation at once. Slow help turns a pricing glitch into refunds, chargebacks and a review score nobody wanted.
4. The Update-Night Lockout
A major patch rolls out overnight. Buried in the release, a batch of accounts will not authenticate the next morning. These are not first-timers poking at a demo. They are the long-haul crowd, the ones with the deep progress and the collection they would be gutted to lose.
Why it matters for delivery: The report is blunt about where the money sits. A sliver of players, somewhere between two and five percent, can drive more than half of a live game’s revenue. Those are exactly the players most likely to be locked out on update night, and exactly the ones a live game cannot afford to lose. Secure, patient account recovery, delivered fast and at scale, is retention work wearing a security badge.
5. The Patch That Splits The Room
A balance change, a ban wave or a monetization tweak drops, and the reaction is instant. A thread starts, the clips travel, and the community begins writing the story before the studio has posted a word.
Why it matters for delivery: In a persistent community, trust is tested in public and in real time. Moderation, trust and safety, and community management have to move at the speed of the feed, with consistency, or the room decides the story for you.
6. The Signal in the Tickets
One odd issue turns up in the queue. Then it turns up again, and again. The support floor can tell something is off well before it ever trends.
Why it matters for delivery: Long before an issue trends, it shows up as a shape in the queue. An operation that reads that shape early and routes it straight to LiveOps hands the studio a chance to patch a small problem before it becomes the season’s headline and bends the retention curve the wrong way. The queue is a telemetry feed. Most teams only read it as a backlog.
Delivery Is The Difference
Notice what these six moments share. Not one is the story of a studio that failed. On a live title there is always something mid-change: a season landing, a store updating, an account locking, a community reacting to a patch. That is not the operation going wrong. That is the operation running.
What separates the studios that keep their players from the ones that quietly leak them is not how rarely these moments happen. It is how well the team delivers in the minutes and hours right after. When the median game loses four in five players inside a week, the ones that beat it are almost never the ones with fewer incidents. They are the ones that handle each incident better. And as the summit report notes, even small gains in retention compound straight into lifetime value. That is why, on a live game, player support has stopped being a back-office cost and become part of how the game is run week to week, across the whole lifecycle rather than a launch window.
The operations that deliver best do not choose between people and technology. They run both, in a clear order. The repetitive load, the language barriers, the first flicker of a spike in the queue: that is where automation, translation and trend detection earn their place, clearing the path so specialists can spend their attention on the tickets that carry money, emotion or a player’s trust. Used that way, the tech makes human support faster and more available. It does not stand in for it.
That is where 5CA comes in. Since 1998, across 35+ languages and 80+ countries, our gamer-led teams have delivered player support for live games through exactly these moments, because our agents have lived through most of them as players too. We call it Fan-Made CX, and it exists to do one thing. Keep players in the game.
Heading to the Live Service Gaming Summit? Find the 5CA team and tell us which of these delivery moments your live game hits hardest. Odds are we have already carried another studio through the same one.
8 October 2026
20 August 2026
7 August 2026
