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.
-
@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.
-
@dashrender said in Hiring a tech for support, based in US:
@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?
That's a weird question to ask.
-
@dashrender said in Hiring a tech for support, based in US:
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.
Don't take my numbers as in anyways what @olivier will pay for the position. I just see the position as a low tier job that would offer a low tier pay rate.
-
@dashrender said in Hiring a tech for support, based in US:
Are you looking for this to be full time? Or perhaps a few people doing it part time?
He's considering even a single part time person, I believe. I think that's buried in the posts somewhere.
-
Do you have a specific time zone that the majority of your clients are in or are they spread across the US? Seeing as how there is as much as a 5 hour difference from one coast to another, you'd want one person in at least 2 of those zones I would think.
Also, have you considered us Canadians? Our dollar is weaker than the US so you could, effectively, save 25% on labour costs.
-
@manxam said in Hiring a tech for support, based in US:
Also, have you considered us Canadians? Our dollar is weaker than the US so you could, effectively, save 25% on labour costs.
I had spoken to him about the even better prices south of the US border
-
At least half of our revenue are in USD, so we would like to avoid any conversion: paying directly in USD. Our customers are roughly spread evenly coast to coast, but in general the whole America (North+South) support time starts (in my UTC+1 time) from 3PM to 11PM (so you can check with your own UTC time).
Full time would be better to part time, if possible. If there is no active support tasks, we could have side work (doc improvement, typo/bad phrasing corrected etc.)
-
@olivier Hell I'd be willing to help you update documentation. I don't know if I have the time to do support cases though full time.
