Hello fellow Indie Hackers,
Let me give you some context, to see if I'm not looking for the wrong profile and I'm doing the right approach to this.
I'm looking into hiring the first support person ever for my product, so i's my first time hiring support staff so I'm not sure how to do this.
I want to do this because support is starting to consume some of my time, and I've reached the point where I am not learning much more about customer needs by giving it.
I know what the platform needs at this point, so I need more time to work on it.
It's not like I want to stop doing support for now, and neither for the next few years for what I can estimate. But I would like to be able to delegate some of the requests to someone else, and get some help.
I need them to have great written English skills, know a bit about the product (it's an online course platform), and know something about DNS.
One of the main tasks is to help customers set up their custom domains, so I would prefer them to know that.
The person won't have enough to keep them busy full time initially, but that is OK because I need them to also write the knowledge base from scratch, so that would be their main first task.
My first question to founders is, is this too much to ask for a support person?
I mean to be able to:
know how to write good English documentation
give support to a product similar to a web hosting platform, but specialized in online courses
know how to use DNS to set up a website
Or do you think I need different people for these tasks?
A second question, where do you find support workers?
Are there specialized websites for support workers, besides the generic Upwork?
I would prefer a simple job board, so that I can hire them directly and spare the platform rates.
But if you don't hire them directly, what platforms do you use?
Thank you for any insights and for sharing experiences in this matter, I would love to hear from the community.
Kind Regards,
Vasco
Hi @cavalheirov!
I have some experience hiring people but for eCommerce, I'll give you the process I used, will probably give you some insights.
-------
0) FIRST
-------
💬 Language. If your support is in English, you'll be able to hire someone in the Philippines, which is my #1 reco for hiring people! I had amazing experience with PH people so far, and while it's not the cheapest compared to other countries, you usually get very hardworking people
-------
-------
## Scorecards:
For the hiring process the first thing to do is to define clearly the job. By clearly, I mean with numbers.
"Doing customer support" is vague.
"Handling 100 tickets per week" is precise.
You can create a scorecard describing what would be peak performances in the job.
The scorecard got two things:
## Job post:
Once you've defined the job, you'll have to write (and publish) a job listing.
Reminder: You're trying to sell the job, so make sure it's both interesting and compelling to read!
Here is how I structure my job posts:
-------
2) SELECTION
-------
## Filtering applications
If you've done a good job post, you can now filter through the applications! Depending on where you posted and how good the job is, you'll get more or less replies. How picky you are will depends on how many replies you have and how much time you can allocate to interviewing people.
I used to receive 200+ replies so I had to filter BEFORE getting on a call.
The best for that is to eliminate as much people as possible as soon as possible.
For that, I usually send an email to everyone who replied quickly with a 5-10 questions that help me eliminate who don't have the personality / skills / other I'm looking for.
It also allows you to test how fast people answer. I send multiple batch of questions if I still get too much applications.
Ask question about them, what they like, what they read, their plans in life, and usually a quick practical case (something very short tho, respect their time. Can be a customer ticket example to see how they'd answer)
IMPORTANT FOR LATER: Ask them to send you their "work history". Doesn't need to be a C.V, just a list of their previous jobs.
## Interviews
So, here is the time-consuming part. Depending of how many candidates you have, you should make more or less interviews. Ideally, you want 10 people max, since each interview is very long.
If you have more, you can also do a quick screening interview to filter out. Just ask questions similar to the ones you sent by emails, or ask more precision to see if their answer is aligned with the job.
For the final interview, it takes around 1 hour for each person.
Basically, you're going to go trough every job they had, and ask them those questions:
**
So, once you're done with that, you should have a better understanding of the candidate and his history. Send a few emails/call some references of the candidate, ask them what are the good thing about them and areas for improvements.
Then, you'll have to make a choice!
------
Obviously hiring is a very depth subject and there is way more to it, but it would take hours to write it here haha. But that gave me a great idea for my next articles in IH, as I have a LOT of things to say about that haha
Also, the formatting of this answer is probably not the easiest to read, it's 22:00 here and I'm mainly taking stuff from my HR operation procedures, but if you need any clarification, let me know!
You can contact me anytime, my contact infos are in my IH bio! :)
P.S. If you're finding yourself always answering the same questions, I'm currently working on an A.I to handle customer support, if you're interested, feel free to check it here, as I think you're totally my target audience, I'd love to get your feedback! 😄