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 ta

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.