Fox Studios logo Fox StudiosGame projects, devlogs and Scratch builds
Studio

Handling Player Support as a Two Person Game Studio

Our second game sold about 1,200 copies in its first three weeks, and we were not ready for the mail that came with it.

A laptop showing a shared support inbox with labelled bug report emails beside a notebook listing known issues

Our second game sold about 1,200 copies in its first three weeks, and we were not ready for the mail that came with it. Eighty three emails, somewhere near sixty direct messages on Discord, and a handful of people who found Reyansh on an old social account and asked him there. One of those emails was a save corruption bug on a specific Windows locale setting. It sat unanswered for nine days because I assumed somebody else had it. The player refunded, left a review that mentioned the silence rather than the bug, and he was right to.

Support is the part of shipping nobody writes a devlog about. It is also the part where a two person studio can lose more goodwill in a week than a year of posting clips builds up. What follows is what we changed after that launch, with the volumes we actually see, because the advice I found online was written by people handling either five messages a month or fifty thousand.

What actually arrives, sorted

I tagged every incoming message for four months so we could stop guessing. Per 1,000 copies sold, we get roughly 60 to 75 contacts, and they are not evenly interesting.

TypeShare of messagesMedian time we takeNeeds a human?
Bug report with no details29 percentSame day, one question backNo, a template works
Bug report with details11 percentSame day, then as long as the fix takesYes, always
Controller or input not detected17 percentSame dayNo, it is the same four causes
Refund or purchase question9 percentSame dayNo, point at the store policy
Free key requests, mostly not from press14 percentTwo to three daysNo
Feature requests and balance arguments16 percentWeekly, in one batchSometimes
Hostile messages4 percentNeverNo

The number that surprised me was the first row. Nearly a third of bug reports say some version of it crashed and nothing else. No system, no step, no screenshot. Those are not bad players, they are people who have never filed a bug and do not know what we need. A short reply asking three specific things converts about half of them into something fixable, and the other half never write back, which tells you something too.

Running support in Discord is worse than it looks

Every guide for small studios says to put support in your Discord, because that is where your community already is. We did that for a year and it was the wrong call for us.

Discord is good at conversation and bad at tracking. A message scrolls away. There is no unanswered state, no way to tell at a glance what is still open, and no history you can search six months later when the same bug comes back after an engine update. Worse, direct messages go to one person. Reyansh had eleven open support conversations in his DMs that I could not see, so I could not pick any of them up when he was travelling.

What replaced it is boring and it works. One email address on the store page and in the game's pause menu, going to a shared inbox both of us can open. A pinned known issues post in the Discord that links to that address instead of inviting replies. A channel where people can talk about bugs with each other, which is useful, with a line in the topic saying it is not monitored as support.

The second piece of common advice I would push back on is the idea that canned responses are impersonal and you should write every reply fresh. Ours are the opposite of impersonal. A template that answers a controller problem in six minutes is kinder than a bespoke paragraph that arrives in four days. We keep nine of them, each one short, each one signed with a real name, and every one ends with an invitation to write back if it did not help. Roughly one in five people do, and that is when the actual conversation starts.

The templates we use most are the controller detection one, the save file location one, the please send me these three things one, and the yes that is a known bug and here is where to watch for the fix one. Those four cover more than half of everything.

The setup that fits two people

We spend about 40 minutes a day on support in the two weeks after a release and maybe 20 minutes a week after that. Getting there took four changes.

A known issues page, updated the day we learn about something, with a plain list and a date next to each entry. It cut our incoming bug mail by somewhere between a quarter and a third, because people check it before writing. It also stops two people from investigating the same report.

A bug form with exactly four fields: what happened, what you did right before, your operating system, and a file upload. Four fields get filled in. We tried eight and the completion rate fell off a cliff.

In game logging that writes a small text file next to the save, with the build number, the graphics device and the last twenty events. Asking a player to attach one file is far easier than asking them to describe a crash, and it has saved me days. Our log file sits under 40 kilobytes so nobody worries about sending it.

A rule about hours. We answer between about ten in the morning and six in the evening on weekdays, and the auto reply says so. Before that rule I was replying at one in the morning, badly, and then having to correct myself the next day. Nobody has ever complained about the hours. Several people have thanked us for answering at all.

If you are planning a launch and have not thought about any of this, the support address and the known issues page belong on the release checklist alongside the store page work. The hosting and tooling costs are small enough to disappear into the numbers in what our first year actually cost, which is to say under 30 dollars a year for us.

Refunds, and the messages to let go

On Steam the refund decision is not yours, which is a relief once you accept it. A player under two hours and fourteen days gets their money back whether you agree or not. Arguing about it costs you a review and gains you nothing. We say we are sorry it did not work out, point at the refund page, and ask one optional question about what went wrong. About a third answer, and those answers have been more useful than any survey we have run.

On itch the decision is yours and I default to yes. The money is small and the alternative is someone telling a story about us for free.

The four percent of hostile mail is the part I handle badly if I am tired, so I have a rule instead of a judgment. If a message contains an insult, I do not reply at all. If it contains a threat, I screenshot it, block, and report it to the platform. I used to try to win those conversations. I have never once seen it work, for us or for anyone whose feedback threads I follow in our studio notes.

One habit I would start sooner next time. Every Friday, read the week's messages in one sitting and write down the three most common complaints. Not bugs, complaints. For our platformer the top one was that the second area felt unfair, and it took five weeks of reading mail one at a time to notice a pattern that was obvious in a single list.

FAQ

Do we need a help desk tool?

Not at our size. A shared mailbox with three labels, open, waiting and done, has handled everything so far. The free tier of a proper help desk starts to pay off somewhere above roughly 50 messages a week, mostly because of the reporting rather than the replies.

Should the support address be a personal one?

No, and this is the mistake I would undo first. Use an address at your studio domain that two people can read. A personal address means support stops when that person is unavailable, and it follows them around forever after they leave the project.

How fast is fast enough?

Same day on weekdays is plenty, and an honest holding reply counts. People are patient when they know they were heard. The thing that generates bad reviews is silence, not delay, which is exactly what our nine day email taught us.

What about non English messages?

About 12 percent of ours arrive in another language. Machine translation is good enough for support text, and I say in the reply that it was translated. Nobody has minded. Translating our known issues page into two extra languages took an afternoon and cut repeat questions noticeably.

DF
Diego Fenn

Diego covers finished builds and the community around them, and runs the feedback threads that shape what the studio makes next.

More posts by Diego

More in Studio

01doorganico 084goad 3hot8 4465456 after5internprogram ahandfulofblessings ahmadpc ahomcybersecurity allodialresources annodex antiquesandperiodcollectibles aotc asianworldkashmir beedlectrics bloggertemplatefree bluefeatheragency bodyweightsolution campaign08blog carfixadvisor catstreetcollective cbstvsports cnfanspurchasing committeeof500yearsofdignityandresistance covertopsdjs cs-kaiyuangame cuestacomunicaciontotal cxoutlet dancebetgame deskgearhub destinyvillastay detectmagazine di33 diamondsteelbuildings donmo dyanadropship emarsysfinance emimattl escapechan eskitarih evautoplay everythingweddings-orlando farmzone feedviewerapp gamevui123 gleasongrade greetingsday hacklabasu haskell iw-kaiyun jagoanproperti jilidskripsi joltbusinessfinance juegodepokergratis juegospucca kaeru-festival latestmehndidesigns lestanzediottaviano litemagazines localcommunityhero lustrsazan mariashebets menswheels newwebstechs1 nikkit ootheday oxigenvpn plurfitness prefetial probudgetcarpetcleaning psychicmrsmartin pyaten qvantor rejoignezlogis rexzbot riselayouts ruchin rwxqsgd5 sakaltime shibiaowang shop-bot skrtips spotlesshaven strcoding tetapatrium topselller uneplanteartificielle vipertechcr webtech1223411 wo-kygaming yamaha-mekar yeknava yoybuysheets zenunwa yamaha-mekar jilidskripsi ankertoto ankertoto ankertoto