Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags
(1 edit)

Thinking about this more, here’s what I’d suggest changing as soon as possible. I think the main issue is the https://itch.io/support page, because it has a catch-all email and a few narrow solutions below that. This is creating one big opaque queue for almost everything else, with a fingers crossed approach that some of the other text below will be read, to alleviate a tiny amount of message flow.

I’d redo that page immediately, and add these things:

  1. A publicly visible number of the current count of requests in the queue. Maybe also how many were handled over the last few days, so we can get a sense of the time-frame for support right now.

  2. Hiding the support email address behind a small survey-like system, for organizing requests and solving common problems immediately. All of the other information on that page could go into this. (i.e. “Feedback or problem?” > “Are you a player or developer?” > “Is your problem related to…”) Then you can only show the support@itch.io email address if the survey fails to resolve the question, and it’s more likely people will read through and organize themselves. Add as much as you can to this survey later, every extra answer reduces load on the system.

  3. Unique email addresses for specific kinds of support. At a minimum, dev-support@itch.io and shop-support@itch.io. You could also possibly do this via title filtering, with codes that the survey gives you at the end with the contact email. As in “Please add ‘D105 Requesting CSS Access’ to the title of your email, to help us resolve your issue more quickly.”

Of course, none of this helps with the underlying problems of the currently unsorted and overloaded queue. But that gives you a starting point for bandaging this from further breakage, and makes the support delays more transparent for the time being.

The next thing I’d suggest is sorting all requests that don’t need back-and-forth contact into separate lists, and maybe making it someone’s full time job to just organize the current queue for a couple weeks. Then assembly-line the rest of support, so they encounter similar tasks as often as possible. I’m sure there’s more that could be done, but this would be a start.

I think there’s a lot that can be done quickly and would help tremendously with the current support delays, which seem to be happening to a lot of people right now. The lack of any contact for weeks is probably causing many duplicate requests in the queue as well.