This is true of most jobs. That doesn't mean I expect companies where the job is required to routinely fail at them, mostly because they are unwilling to invest proper resources.
Framework is not unique in having shitty support. It is an absolute epidemic, which is why companies are able to get away with it. But the fact that almost everyone sucks at it doesn't mean we shouldn't call the problem out loudly when we see it.
Completely useless comment.
At no point did I suggest not to do support, and Framework is indeed supporting its customers.
This is unfortunate because, especially for technical folk, support interaction is the backbone of user experience.
If they could innovate here a lot of things could be overlooked. Costco + early Amazon often did this pretty well tho.
This is the primary reason i buy used iphones - someone else pays the apple tax, i take the phone to apple and for a reasonable price, i get a new battery and i keep the value of the phone and battery for around six years. No other phone manufacturer offers that proposition.
I also chat with the apple staff while i wait and they are paid decent wages. I certainly think they deserve higher wages, but their wages are not bottom of the barrel. The strongest evidence is that staff turnover is relatively low.
One of my early jobs was working in support for a web-hosting company just after the dot-com boom. They did a lot of things wrong (or at least cheap), but they also got a lot right, especially their support teams. They understood that customer service is the face and reputation of any business, not just a cost center.
They provided good training, fostered a positive atmosphere in a variety of ways (important when your job is a constant stream of unhappy customers), and supplied a lot of free food and company outings. I wouldn't say it was an _awesome_ job, but it was a good one, especially for where I was at the time. There certainly are parts of it I miss. (Mainly some of the unique characters I got to work with. It feels like everyone in modern tech companies all have the same personality.)
The quick fix for any company in this situation is to require that technical people across the company take responsibility for customer support. Of course, they don't want to, hardware designers and software engineers can't imagine anything worse, but they've got to be exposed to how real customers are experiencing their work to have any hope of doing a good job. The exposure can be direct (in a crisis) or indirect (through technical support staff relaying).
If I were the Framework CEO, I'd be taking over customer support myself. A nightmare, but necessary to understand why their support is so bad.
And this is how it should be: an enthusiastic developer can churn support tickets in their free time much much faster than dedicated support staff does full time.
Louder for the people on the back
In the same way a bad medical diagnosis makes things harder later on, or bad legal advice, etc
But especially in the "silly" cases, this is extra disappointing. The case in TFA is not "you're holding it wrong" or "weird technical bug that happens once in a very while", it's a very clear issue of "should do A and it doesn't"
I like your idea but I can also imagine that quite a few technical people will not have the necessary communication skills for being in customer support. They will need additional training if you want to unleash them onto your paying customers.
‘Oh, yeah we have been seeing this bug, tell the customer to flash this version.’
That’s a known issue and the fix is going through Qa
Sounds like there was an issue with that part, rma.
The amount of tickets your pros can clear while skipping the script is insane.
Additionally, it can turn up or handle bugs that aren’t handled by the script.
We all read the diagnosis on this post and knew the part was bad about 3 minutes in and it’s not even our project.
Products are priced and launched with an initial BOM cost and anticipated labor cost for repairs. Prior to the AI buyout, service and support was already running into real issues with the costs of labor increasing very quickly. Now, the cost of service parts has also skyrocketed. This means that the initial overhead in the cost of the machine is no longer able to cover the intended dollars put aside for repair.
This is not just happening in computers. This is everywhere. Support and service were struggling everywhere coming out of COVID, prior to the jump in component costs due to labor. Now it is a bloodbath as logistics costs have also jumped due to fuel costs. Add into this that the vast majority of manufacturers build in lower-cost labor environments, but repair generally happens locally near customers. In these situations they are facing repairs that can cost more than building a new machine.
The future of support is going to be grim for the coming years.
I had a similar issue with Apple once and that was their recommendation (as it was within their return window).
Perhaps that approach isn't practical today, but maybe there are some useful threads in there to pull on.
I wonder if it's because it is a small enough team that they have the correct person respond to support calls each time, but it was the best experience I ever had.
Also I had to make videos and photos and then email them which couldn't handle large files so I had to organise my own hosting and share links.
Basically they don't seem to have thought it through yet
Since you seem to have experience with this, the principle that I've seen work "best" in my own limited experience (and I wonder how it matches with your experience) is to keep the barriers between support and product development as low as possible:
1. keep the company as small as possible in general (which lowers all communication barriers everywhere, and helps with cash flow—fewer salaries, smaller office, low overhead)
2. Early on, have the same engineers doing product development and support. Later, have heavy, regular communication between the teams (including managers and senior ICs on both sides. Maybe rotating the managers would work? I don't know. Once you have more than one level, I don't know anymore, but maybe do the same thing with directors and senior managers?). This hurts growth, because you're understaffed to begin with, and you're impeding the staff you have by giving them tons of unplanned support work. But IME it means that product development is happening at the right level of abstraction.
If the product you're building requires big company support (or training or product development), and the revenue it brings in can only support a small company, then you should change what you're building. It's very hard to change what you're building if the company is very big.
So if, for example, support is boiling because your product is flaky, and engineering is too small and too busy to fix all the problems at a reasonable pace, you probably have a design problem(s) and expanding will make it more entrenched. Instead, you should simplify the product. Then expand (with an understanding of the real costs of different parts of your vision), and repeat.
If you need to have strong technical people in support, you’ll be overspending in salaries for people that will likely move fairly soon to better positions (a lot of tech people started in support, i did myself).
If otherwise you don’t spend enough you get to keep the books in check but then you have support people that are not very technical and mostly read from a script.
And there are a ton of other things that happen behind the curtains as well.
Support seem easy but trust me, it isn’t.