4 ms·

Ask HN: How do you handle support during weekends and holidays?

• sharth 14y ago
  I guess I'm confused why you need 24x7 support for a "social game". What would happen if it took 48 hours to respond? Very few companies that I deal with respond much quicker than that.
  • babuskov 14y ago
    Well, the game is highly competitive on a daily basis, so players would get mad. I also run public Facebook pages for these games, and if I do not answer some stuff for hours, mayhem happens. It is not in English, otherwise I would given links to see for yourself. I also believe that prompt support and solving customers problems within a short period of time would mean a lot to users. If you are in a middle of highly addictive game and you get stuck because of our error, you might cool down and not be in the same mood to play it next time.
• ScottWhigham 14y ago
  I have one full-time CS employee and he works 39 hours(ish) per week during weekdays and one hourish over the weekend. That was in the job description and we talked about it during interviews. It was a deal breaker, for me, if the candidate was unable to commit an hour over the time between "Friday and the next work day" to manage answering tickets and helping customers. But going from zero employees of any kind to two full-time CS employees so that you can save time is foolhardy, at least in the short term. If you think you have no time to code now, just wait until you have employees yet have no training plan/manual for them to follow. I'd suggest you find one "all around" person and have them do CS as part of their job. The other parts of their job are various admin duties - mail, filing receipts, etc. If you find that, after 3-6 months, you need another employee, then you have a built-in trainer for the new person.
  • deleted 14y ago
    [deleted]
• rdwallis 14y ago
  Reach out to your most active users and ask them if they want to help moderate for you. Give them premium content or even just cool badges that other users can see in exchange. Make it personal. Email them and ask for their advice. Listen to it even if you don't implement it all. People love to help and they love to be heard. If you do it right they'll like your game even more.
  • babuskov 14y ago
    Not a bad idea. Although, in my case, support also involves support regarding user payments, so it's a little bit sensitive issue to allow users to even access this data for other players. I'll have to think about this. Maybe just provide support for payments myself, and leave rest to most engaged users. Thanks.
• mbeale 14y ago
  Personally I think 24x7 support for something that is not "Mission Critical" is overkill. Unless you are a hosting company, Point of Sale, or payment processor, I think 24x7 support is a lot to ask. How many times have you got a support request over a weekend or at midnight that "had" to be answered immediately and could not wait until the morning. I think on holidays and weekends it would be nice if someone just checked the support Q for any emergencies and let the rest wait until the next business day. Most businesses are not 24x7 and I would not expect a support request for a game sent on Saturday to be answered that day. [edit] Also good practice to not do any code deploys on Fridays or day before a holdiay
  • babuskov 14y ago
    Well, we do support for payments as well (part of payments goes through Fortumo, and it is their requirement that we handle support), so I guess this counts as "payment processing"?
• trapexit 14y ago
  Consider outsourcing your customer support to a company that specializes in it. If you just hire two full-time employees, you're still going to be picking up the slack on weekends or when someone gets sick, goes on vacation, or resigns. A vendor that specializes in customer service will be able to train multiple employees on your product and rotate them as necessary to give you 16/7 or 24/7 coverage if that is what you need. Set the goal of having your customer service vendor handle 100% of first-line support inquiries. They should have a manual that tells them what to do in any conceivable situation that could arise. Obviously, it's a lot of work to write this manual, or even to think up/research all of the possible problems a customer might have. Start by just identifying the top 4 or 5 issues and writing down what you currently do when someone has that issue. Give this info to the CS vendor and tell them that it is their job to maintain the manual and to contact you whenever a situation arises that is not covered by the manual. When they call you, tell them what to do, and insist that they record this in the manual and handle all future situations of that type in the same way. You should never do customer support unless either you like doing it, or because you are concerned about getting out of touch with your customers' wants, needs, and desires. And if you really want your business to grow, you should find someone else to write code and fix bugs for you, too. You're not a developer anymore. You're an entrepreneur. Yes, you can be both, but you can't simultaneously be excellent at both. You've figured out how to get 300,000 users for your games, and you're apparently making enough money to pay for employees, which is phenomenal. Wouldn't all of that talent and skill that you have be better spent identifying new products to create, new ways to monetize your existing products, strategic partnerships you could form, new ways to get customers, etc.? An excellent book on this subject is "The E-Myth Revisited" by Michael Gerber. He talks about how a business needs three personalities: a technician, a manager, and an entrepreneur. Most people who start businesses get stuck in the "technician" role all day and keep working in their business instead of on their business. A successful, sustainable business has employees who do most (or all) of the day-to-day work and supervision, with the founder/leader free to think and act strategically.
  • babuskov 14y ago
    Great advice. I guess I really have more to think about here than just "how to handle support". Thanks Brian.