Hacker News new | past | comments | ask | show | jobs | submit login
Ask HN: How do you deal with support for your young project?
1 point by ramijames 10 days ago | hide | past | web | favorite | 1 comment
We have been working diligently on Scatter (https://get-scatter.com/) for the last year or so. Entirely bootstrapped and fairly successful, but not successful enough to hire a dedicated support team. It sucks a lot of time and energy from us and well, I'm wondering how you guys have dealt with this kind of situation.





Every app will be different, but I found (at first) that doing support myself, and doing a light "first principles postmortem" on every email that came in was a good way to drive support down over time. Essentially asking "what do we need to do to make this the last time anyone writes in with this question?"

Sometimes that means better documentation and self-serve content. Or adding better search terms to your support content so people can find it more easily. (If someone writes in on a question your help center doesn't cover, copy your answer to them and paste it into your help center CMS. If someone writes in with a question you already answer, pull phrases and keywords from their email and add them to the answer / tags in the CMS.) Sometimes it's making it clearer within the UI what your app will or won't do. Sometimes it's writing a new feature to appease people.

You want to maximize the number of ghost tickets — the ones that never come in, because they never had to get written in the first place. As with code, "No ticket is faster than no ticket."

Making your support content more present within the app itself, or hooking up your "need support?" request flow so the customer has to go through the support content first can also help. (Obviously, there's a balance between making them jump through hoops and just having an open line to you.)

Eventually I hired one of my most vocal customers (opinionated, but polite) to handle support part-time. Hiring her at an hourly rate meant I didn't have to worry about a lot of the normal staffing issues that come with a full-time employee.

If you do go the route of hiring someone, I highly recommend looking for someone with a librarianship/infoscience background. They're trained to communicate well, to discern the question behind the question, and to do self-directed research. They're also in a market where jobs are harder to come by.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: