2 ms·
Customer support for every company is going to be different; there just isn't a formula. Some companies can utilize more automation because the types of questio
by lunaru 10y ago
Customer support for every company is going to be different; there just isn't a formula. Some companies can utilize more automation because the types of questions fielded are going to be very similar (e.g. "where's my package?" or "how come there's a flashing red light?"). A team of 8 just about anywhere can scale to fairly high volumes.
But since we're talking about the Bay Area, and it sounds like specifically for a technically focused company (I'm thinking startup) the good news is that the core team is likely already fielding support because talking to customers is so important to the growth and direction of the product. Yes Bay Area salaries are high, but hopefully you're hiring high quality team members that are more than just front-line support -- they should be an invaluable part of your product and customer development process. You can't really put an outsourcing price tag on that.
Lots of companies have a process where the developers are insulated from day-to-day support roles -- and if that's working, great. But, the best companies have developers who want to talk directly to (or at least have support access to) customers and understand their problems first hand. This is where the high salaries more than pay for themselves.
- fapi1974 10y agoI definitely don't think it makes sense for early stage startups to work with a vendor - there is too much iteration happening during the search for PMF. Where we see it start to make sense is when the company is hitting acceleration. At that point it doesn't scale to do side-by-sides for training. It becomes necessary to manage large number of high-turnover employees and become really good at hiring and training them. It's really specialized. Most tech companies that have scaled - Uber, Amazon, Google etc etc use outside providers. Which isn't to say that even when we get brought in (usually at around the 6 person mark in the blog post) that we don't spend a TON of time making sure that the communication between the front line agents and product/engineering isn't really good.