Hiring a tech for support, based in US
-
@olivier said in Hiring a tech for support, based in US:
@dustinb3403 Nope, what do you think would be a acceptable range for something like this?
I honestly couldn't give you a realistic idea.
Being Tier 1 support for the platform could begin at as low as minimum wage (in the states) or be at $20+ per hour. . . it really depends on what is required.
Being you want the person to have a basic understanding of an IP stack and XS and XOA working, my idea would be in the $20+ range.
-
Would this position work directly with the customer (IE pick up the phone and say "XOA Support, how can I help you?")
-
Or would the position have a help desk queue and they simply jump on all tickets that come in, remote in, investigate the logs, PEBCAK issues etc and escalate as required?
-
No phone support, only live chat and tickets. And yes, directly with the customer.
-
@olivier said in Hiring a tech for support, based in US:
No phone support, only live chat and tickets. And yes, directly with the customer.
So they don't need to be comfortable talking to strangers (good for a junior tech for sure).
-
@dustinb3403 said in Hiring a tech for support, based in US:
@olivier said in Hiring a tech for support, based in US:
No phone support, only live chat and tickets. And yes, directly with the customer.
So they don't need to be comfortable talking to strangers (good for a junior tech for sure).
Yeah, no "voice" contact with customers. Everything behind a screen and keyboard, that's all. But it's not easy either to deal with people who can't RTFM
-
@olivier said in Hiring a tech for support, based in US:
@dustinb3403 said in Hiring a tech for support, based in US:
@olivier said in Hiring a tech for support, based in US:
No phone support, only live chat and tickets. And yes, directly with the customer.
So they don't need to be comfortable talking to strangers (good for a junior tech for sure).
Yeah, no "voice" contact with customers. Everything behind a screen and keyboard, that's all. But it's not easy either to deal with people who can't RTFM
That is why you're looking to hire
-
Well, we estimated that I could handle up to 250 customers myself, which was relatively correct. I can push this to 300, but it's a bit hard to do anything else. Because we are beyond this number today, it affects also the rest of the dev team, which is partly good (to get quickly why something they did is wrong) but it's now too much to handle.
-
@olivier said in Hiring a tech for support, based in US:
Well, we estimated that I could handle up to 250 customers myself, which was relatively correct. I can push this to 300, but it's a bit hard to do anything else. Because we are beyond this number today, it affects also the rest of the dev team, which is partly good (to get quickly why something they did is wrong) but it's now too much to handle.
So the expected customer volume per day is 250 tickets/chats?
This part I don't understand
which is partly good (to get quickly why something they did is wrong) but it's now too much to handle.
-
@dustinb3403 no volume is NOT that high. I counted the total number of customers, not the ticket number.
Regarding the last part, I wanted to tell that having devs doing a bit of support is not a bad thing. But until a certain level.
-
@olivier said in Hiring a tech for support, based in US:
@dustinb3403 no volume is NOT that high. I counted the total number of customers, not the ticket number.
Regarding the last part, I wanted to tell that having devs doing a bit of support is not a bad thing. But until a certain level.
Yeah, more effective things for them to be doing.
-
Oh so you have 250 active customers, and occasionally DEVs are stepping in to resolve issues, but you don't want them too. (obviously) they should be developing XOA.
-
@dustinb3403 No I said I can handle something around 250 customers/subscriptions in terms of support. Beyond this, it's a fulltime job. So because I couldn't do only this, I delegated a bit of this to our devs. Which was a good idea until 300/350 customers. But we are now even beyond that, and it starts to be bad for productivity!
-
@olivier said in Hiring a tech for support, based in US:
@dustinb3403 No I said I can handle something around 250 customers/subscriptions in terms of support. Beyond this, it's a fulltime job. So because I couldn't do only this, I delegated a bit of this to our devs. Which was a good idea until 300/350 customers. But we are now even beyond that, and it starts to be bad for productivity!
Ok sorry I guess I misunderstood.
This person would be entirely supporting all of your customers as T1 support.
-
@dustinb3403 Yes, and obviously we can train him/her slowly but surely
-
You said you were open to part time to start as well, correct?
What hard requirements for the position would you have (I may know some young kids who could be interested).
-
@dustinb3403 said in Hiring a tech for support, based in US:
Here is a great place to start looking.
Post the job details, what the expected duties are and pay etc.
You're applying right?
-
@scottalanmiller said in Hiring a tech for support, based in US:
@nerdydad said in Hiring a tech for support, based in US:
@dustinb3403 said in Hiring a tech for support, based in US:
@olivier how do you want people to contact you about the position? Email, phone, SMS?
Carrier pigeon with CV attached.
Hogwarts' Owl
you against all the other wizarding schools out there? or private owls?
-
Are you looking for this to be full time? Or perhaps a few people doing it part time?
What's the typical SLA on returning support requests?Great way for someone green to get some legs quick - color me interested, but full time at Dustin's listed wages I couldn't be.
-
@dashrender said in Hiring a tech for support, based in US:
color me interested, but full time at Dustin's listed wages I couldn't be.
Same.
