Quick answer: Lean on automatic grouping and occurrence ranking so a volume spike collapses into a short ranked list, and watch for issues that only new players hit. A sale spike is a temporary flood, the same triage that handles launch handles it: group first, rank by impact, work the top.
A big sale, a Steam seasonal event, a deep discount, a feature, brings a surge of new players, and with them a surge of bug reports. Many are from people experiencing your game's onboarding for the first time, hitting rough edges your existing players moved past long ago. If your support is organized for a trickle, a sale spike overwhelms it. The fix is the same discipline that handles a launch: let tooling collapse the volume into a short, ranked list you can actually work.
A Sale Spike Is a Launch in Miniature
A sale floods you with new players all at once, which means a flood of reports concentrated in time, often about the same early-game issues. The dynamics mirror a launch: high volume, lots of duplicates, and a few issues that account for most of the pain. Treating a sale spike with the same triage discipline as a launch, rather than as business-as-usual that suddenly got loud, is what keeps you organized.
The good news is that a sale spike is temporary and the issues are usually concentrated. A handful of fixes to the most-hit problems typically absorbs most of the surge, after which volume returns to baseline. You do not need to scale your whole operation, you need to survive a defined burst.
Let Grouping and Occurrence Ranking Carry the Volume
The thing that keeps a spike organized is not working harder, it is grouping. Automatic deduplication collapses a wave of reports into a short list of distinct issues, and occurrence counts immediately show which ones the surge is concentrated on. Instead of reading every new report, you watch a ranked list of distinct problems and how fast each is growing.
Bugnet's occurrence grouping does this automatically: a sale-driven flood arrives as a handful of grouped issues sorted by how many players hit each, so the spike that would have buried an inbox shows up as an organized, prioritized list. A saved view of 'top issues by occurrence' keeps the short list in front of you through the surge.
Watch for New-Player and Returning-Player Issues
Sale players are disproportionately new to your game, so they surface onboarding and early-game bugs your veteran players long ago worked around or stopped noticing. Watch specifically for issues clustering in the first hour of play, those are the ones a sale exposes, and fixing them improves the experience for the whole influx at once.
Sales also bring back lapsed players on old saves or old habits, who can hit version-transition and save-compatibility issues. Tag reports by what part of the experience they touch so you can tell a genuine new bug from an onboarding rough edge from a returning-player save issue. Once the spike passes, the issues you identified become a clear, prioritized list to address before the next sale brings the next wave.
A sale spike is a launch in miniature. Group the flood, rank by occurrence, fix the early-game rough edges first.