What is the easiest to use customer support platform for founding startup team?

If I understand you correctly, you're saying a customer agreed to pay you for services (product and/or support), either through posted prices and a shrink-wrapped license or through a written contract, and then you provided those services, and then they didn't pay? And you're asking whether it's "OK" that they didn't pay? Of course it's not OK! Is there any business who could operate in that fashion? The way it affects the customer relationship is you don't have a customer relationship. You have a situation where they are taking advantage of you. A relationship goes in two directions.

HelpScout, ZenDesk or Desk.com. HelpScout (help desk software) would be a great start – less options but even when I ran a 6 person customer support team (with over 500 emails a day), we never needed the complex features of Desk.com. Have one person create 'saved replies' to quickly answer your customers in a cohesive voice and with consistent responses. (However, encourage your entire team to inject some of their personality!) This seems like a huge task, but if they dig through their sent emails, it can be done pretty quickly. Good luck!

In my opinion, phone support is frequently requested but hardly ever needed. I worked at Twilio and as part of my role as a Developer Evangelist I responded to help desk tickets part of the week. We didn't do any phone support and we were able to help people effectively. The key is to be very detailed, thorough and courteous in all your correspondence and also to ask for clarification if you don't understand their questions. You should also have a library of online resources like documentation, frequently asked questions and forums that you can refer people to so they can easily find answers for themselves once you point them in the right direction. One caveat to all that though: I worked at another company that provided phone support but it was something you had to schedule and pay for in advance. At first, I thought it was crazy but our phone support people were busy all day helping customers. It wasn't a lot and it didn't even cover our costs but it prevented your phone from ringing off the hook and people calling to ask really stupid questions. Hope that helps! Also, if you're looking for technical advice on setting up phone support options I'd be glad to help you... over the phone! :)

Most customer service jobs are going overseas, but this is a great website with only remote jobs that might be useful: https://www.remoterocketship.com/?page=1&sort=DateAdded It's a relatively new site, but they're doing a great job.

I've helped lots of SaaS companies improve their onboarding processes over the years, but I just published my best (high-level) piece on doing this right: http://sixteenventures.com/customer-onboarding The bottom line is (though I suggest reading the entire article) you need to know what success looks like for your customer - what their Desired Outcome is - and then reverse engineer the steps necessary to get there. Going through that process will reveal the steps necessary to get them to that Desired Outcome outside of the product; we're not talking about functional steps within the product yet. Map this out using flow charts, line lists, mind map, white board, etc. The tool isn't important as much as doing this right. Now, once you understand the process required to move them from Step 0 - deciding to take action to reach their desired outcome to Step z - achieving their (at least initial) Desired Outcome, you can start laying out, designing, and building the in-product processes necessary to achieve those success milestones and ultimately, their Desired Outcome. You should then peg your email (or other lifecycle messaging) flow to those success milestones (rather than doing a timed follow-up), where each message is sent like this: "have they done this milestone? yes, then send this message to get them to the next one." Since each user and customer will achieve success on their own cadence, it's best to not have a timed autoresponder sequence but to actually trigger based on milestones reached. The good news is that this is relatively easy to do given the availability of lifecycle messaging services. See this post for more on this topic: http://sixteenventures.com/email-follow-up-sequence Hopefully this helps, but if you want more details or - more importantly - want to figure out how to apply this thinking directly to your situation, request at least a 15-minute call with me.