I'm not a framework customer but am EXACTLY the target demo, and between this and the other horror stories I'm taking real, customer experiences to heart and not ordering your product.
This shouldn't just be you posting in an HN thread, this should be a "We fucked up. We know we fucked up. Here are all of the things we're going to do to never, ever, ever fuck up like this again."
This reads as "We know things aren't great and we're working to improve, have patience"
Nah, fuck that. On a multi-thousand dollar system patience for shit like the issue OP is reporting is exactly none.
Agree support leaves a lot to be desired based on this thread, but the gp I responded to was overly harsh, particularly when they aren't even a customer themselves.
my framework laptop arrived with a broken lcd. they only accepted my claim once I provided significant photographic evidence, and then dispatched a replacement screen. the entire process took around 2 months from initial delivery (including shipping of the replacement part). Is it a "hate comment" to complain I want better service after I had already spent ~£4k on the device?
I did have a hardware failure. Reported it. NEXT DAY they sent a tech to meet me at my house, and did the repair right there, parts in hand.
Am I expecting 1 day turnaround for Framework? No. But the runaround and multiple months delays is a very common complaint.
If I had bought from them with these failures on arrival, I'd be charge backing and opening up a small claims suit.
No, you get a 3000 euro botique laptop that's DOA, and get strung months? Fuck that and fuck anybody responsible who thinks that's even remotely acceptable.
My wife was needing a good laptop. I chose NOT framework. I read 3 other times of the same type of runaround.
Once is a runoff. 3x is corporate policy.
I'm all for supporting small business, but a business being small doesn't mean it's good or ethical.
Let me give a good example: A few years back SCANOSS, a company that I believe had 50 or so employees at the time, made a github bot that opened a ton of tickets on repos with swear words in the source telling them to remove them. Obviously, pretty much every projcet that got these had the same "Fuck off" response, because, like, it's their free work up for public use, not there for a business to police, let alone by a bot.
SCANOSS's response would matter a lot in how this is remembered though. They could've said "Our bad, that violated TOS, we messed up, it'll never happen again"
That's not what happened. Instead, the CEO clapped back with this,
""" Our experiment was based on issuing automatic contributions to some components using bad language (detecting and suggesting the removal of such language). The purpose? Contributing to the adoption of those Open Source components. For your information, bad language is banned in most organizations and, therefore, if you are interested in having adoption of your Open Source, it is good practice to avoid such language.
We really don’t need to put any mechanisms in place for this not to happen again. This isn’t something we do on a regular basis and, as I mentioned, anyone could contribute to any repo as long as it adheres to Github’s ToS.
If you are not willing to receive contributions from the community, if you are not interested in your Open Source contribution gaining adoption, or if you prefer people to sign special agreements to make contributions, perhaps you are better off closing down your repository, making it private.
Hope this helps. Ciao! """
Now, this story continues - you can go read the full drama at https://opguides.info/posts/scanoss/ - but that's not the point. The point is the response is what mattered. I don't care if it's Google or Mom & Pop Software Co., the communication matters.
The response here, to me, given the sheer amount of frustration they caused for OP, while not on that level of SCANOSS CEO level of tone-deaf, reads to me like damage control, not damage acceptance. That's why I said "Words.". That's what it reads as, to me, is trying to damage control via words. Sure, he says they're improving processes, but this is one of many Framework horror stories I've read over the last year, all from HN, all with this same divide of praise/defense for Framework and people saying "Yeah, I've been burned".
If they're improving processes, they need to it faster, and until it's under control, make communication channels absolutely top tier. Not bounce arround to multiple support agents. What happened here isn't something that should ever, ever have been able to happen in the first place on a multi-thousand dollar machine. Any response short of "Holy shit, I am so sorry, I will PERSONALLY be handling this, here are all the concrete steps we're doing, here's a blog post about all the things we're doing, with dates of review for follow though" isn't enough.
This isn't a hate comment to the CEO's response here, it's a comment I think that's adequately reflective of the fact that it's still a company and they're clearly not doing good enough.
If it's a difficult space, then this isn't the way to win.
I'm sorry that you don't think people have a right to want better service with expensive hardware and to advocate to a public-facing CEO making a bad apology for some vague version of functional customer support, but it's frankly fucking weird to get on here and shame them for it.
Also it seems to me that if the author of this blog post was so upset, he could at least take the time to write it himself. Pangram says it's 56% AI.[1]
1. https://www.pangram.com/history/78c0efb8-fb27-4e59-b41b-c646...
There are basically no stories about good support, except for people whose issues were the ones caught on the first 1-2 steps of their 47-step support scripts, and who don't realize what was in wait for them if they weren't lucky.
There may be (valid) "horror stories", but what percentage of cases do they represent? (Nobody notices when things go right.)
As I have experience working customer support in IT for a few years, I know good support is both hard and time-consuming. Systemic change is hard too. And to add to the list of difficult to impossible tasks: Staying always truthfull, while providing helpfull support-replies is like near-impossible for most organisations.
Best of success for your endeavours!
Your customer base are above average technical people, yet you insist on treating them like clueless noobs.
Thankfully, your products in general are great when they work, but so is every other brand.
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.
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.
The state of hardware is about as bad as the state of software lately.
I do have a T470S which works perfectly well, a Macbook Pro M1 16GB and hopefully soon a Mcbook Pro 2019 i7 64GB, so I'll do fine.
I have interacted with support before when a usbc thing I got was bunk. Two emails, and then they sent a replacement. Support might be better in Taiwan though, for all I know. Certainly shipping is fast here...
I think this feels like it must be true, but is it actually, in practice? Plenty of SW people don't know a ton about HW.
I recognize that maybe all those people are on Macs :)
I have no experiences or relations with Framework whatsoever nor I intend to have, but having seen some support exchanges about products with supposedly above average technical customer base in the past I'd be willing to side with them on this particular point.
I am not disagreeing on support quality, but the price is very steep and ultimately paid by the customers.
To my surprise, ChatGPT replied immediately with "When you said 'refund', I assume you meant 'discount', so I've taken the liberty of issuing you a new coupon, please use it for your next order and I'm sorry for the problem".
I was blown away, I fully expected four days of back-and-forth while I explain my issue with my discount code that wasn't working.
Often enough customers are wrong about the root cause and their insight into fixing the problem is fairly shallow.
But knowing how you’ve treated them will make everything easier regardless. And your coworkers in any kind of service role are almost adversarial. If they weren’t incompetent you wouldn’t be dealing with a repeat customer.
When the customer is correct all along and you’ve exponentially increased how badly you’ve treated them.
So far, I'm happy with my Framework purchase... but haven't needed any support yet.
I can't imagine how frustrating the experience would've been had I not had another machine to use for work.
Also their business practices seem extremely sketchy to me, one of the first things I asked when it arrived broken was if I could return it for a refund. They refused claiming that the return window had expired, and the window does not start when you receive the item, but instead when you order it (it took ~4 months after order to ship to me).
It was a real learning experience. Now I record every support conversation I have.
You know your customer service is bad when you are unable/unwilling to accept a sale for several thousand dollars.
If you want actual support for your thinkpad, you need to pay the premium for on-site support. The pricing for 1-2 years is usually not that bad (relative to the price of a moderate thinkpad). The techs are hit or miss, but at least they come to your place with the parts (sometimes requiring 2 visits but it beats sending the laptop away for weeks/months).
So, experience with support was very good. I have no clue what that support option costs. It's either expensive as hell or a bad business for Lenovo if I am not an absolute exception with my failure rate.
Why?: because most of the time (>75%) its a clueless noob issue that is solved quicker by doing that.
That being said, there are ways to do it that doesn't make the person on the other side feel like you are being condescending... And it is important to strike that balance...
This story may not be big, but it's strongly indicative, because the problems reported show systemic issues, not one-off flaws or unlikely coincidences. Hardware has one-off flaws and unlikely coincidences. A process of handling things that revalidates an address for over a week and makes repetitive demands of customers troubleshooting the same issue is a systemic failure that is avoidable if any one of the many agents handling the issue gave a shit. This is relevant to me specifically because this kind of failure is not bad luck, it is about how the support organization is run.
Given that this encounter was super recent, it must have been even worse. Hard to imagine.
I love everything about framework as a company, but the approach to customer support has left a very sour taste.
An amazing product with terrible support is something I would not buy again.
I have companies that are still on my shit list because of how badly support dropped the ball such that I don't care how good the product is they'll not get another order (WinWing most recently earnt their spot on the shit list).
But it sounds like the process is not working here. Support people were not identifying the glaring issues, even with the keyboard at hand
This does not inspire confidence
It's not like selling to a country is just changing the address on the label...
I bought a chasis kit recently and the touchpad is faulty, or acting faulty ( physically getting stuck depressed), and the amount of back and forth for the serial number of part X, then Y, then firmware of Z, etc.. maybe there's a technical reason for that but i just considered myself beat into submission and gave up.
after mainboard upgrades, touchscreen upgrades, and various other upgrades over the years and being excited about framework, it's weird to have all of my enthusiasm get derailed over support for a touchpad.
This should be a case of the engineering team getting the faulty device for debug (and ideally getting all the relevant information so they can do the work with some semblance of parity with the customer's setup) -- and the other half is the customer gets a functional piece of hardware to swap in.
If Framework is worried about sending out hardware before receiving hardware, the policy is a simple one; when we get the hardware, we'll ship your replacement.
---
and the amount of back and forth for the serial number of part X, then Y, then firmware of Z, etc.. maybe there's a technical reason for that but i just considered myself beat into submission and gave up.
This is the standard 'debug over the phone' thing and engineers will do this while collecting information to try and recreate the problem you're having. It may be because the engineers are too close to the process? If you think about it, the RMA process is actually a sales process. You're essentially selling an already sold user on continuing to be a user.Oh no. It should be "we have sent you a replacement - once it's installed and confirmed working, pack up the broken one and send us in the provided box with the provided pre-paid return label".
In reality many people will NOT take the second option, but will be happy it was there, and the company probably never bothers billing for incorrect advance RMAs.
For example Dyson is known to provide exceptional support for their vacuums. They often even replace damage for free that was clearly the user's fault. But their products are really expensive. Probably not much more expensive to manufacture than their competitor's products for half the price. They probably don't even lose money if they have to send a replacement once.
Buuuut, I'll argue against the point that these are faulty units. Everyone gets the same PSU in their Desktop. That thread (and many others like it) are full of people claiming that their _specific_ PSU fan is loud and defective and demanding that Framework should replace it. And then are surprised when the replacement sounds exactly like the old one.
I bought the Framework Desktop anyway after reading these threads, and after owning it for almost a year, I have to say that the fan noise doesn't actually bother me. I have had laptops and desktops with FAR noisier fans that ran either constantly or intermittently so I guess I'm just thankful that modern PCs don't sound like vacuum cleaners anymore.
Then take action internally.
You need to touch some ground, your work doesn't end after the sale is made.
Malice / incompetence etc. etc.
And this will go on for many, many steps. And when you finally get to the end of it, they'll say "sorry, you'll need to replace this keyboard, and it's out of warranty, so you'll need to pay for it yourself" and you'll have spent many hours over a period of weeks just to get the answer that you were 95% certain you were going to get in the first place.
It is true that they were out of warranty and couldn't reasonably expect a free keyboard. It is true that your support helped them identify that the keyboard was the issue, so it was a successful diagnostic in some sense. But the experience for the customer is super terrible and infuriating.
What would you want as a customer in that situation? What I'd want is to get an email like "Hey, I'm really sorry you're having that problem. As you probably know, you're out of warranty. There's a pretty good chance that you're going to just have to replace the keyboard, but if you're interested in trying to debug it to make sure the keyboard is the problem, we're happy to work with you on that." And then if I did want the debugging, I'd love to get a single document containing the debug steps that I could work through in one sitting.
That's why I think your insistence on "let me see your case to identify if any steps were done wrong here" is off-point. The problem isn't any particular debugging step or any individual case, it's that your whole process is fucked and customer-hostile in its conception.
Really? This was the drastically improved process? :D
I'm rooting for you guys. Framework is a great concept and I want it to succeed. Good luck.
It's a bit fun the first time to assemble from scratch, but it's annoying the second time, and it would mean you know the laptops actually work when they get sent out! The article's issue for example would've been caught if someone had assembled the laptop and powered it on, and not then disassembled it again for the experience of assembling a DIY laptop kit. My understanding is that this is actually the process Framework uses — that is, assembling and then disassembling — and I can't imagine disassembling has a zero percent fault rate, nor does asking the customer to re-assemble.
Your laptops are really nice and I want you to succeed. There's a reason everyone else ships assembled laptops though, and I think you should do it too. It wouldn't harm repairability, or compromise your principles: I think it would just reduce churn and support tickets from broken parts and laptops, and reduce customer frustration.
I love your company's philosophy. I love your products. I am typing this comment on a 13 Pro, and I own two other 13s. I've upgraded the display in one, and I've sold an empty case off to someone who had a motherboard that they wanted to turn into a whole system. It's all great.
But when something goes wrong (like the motherboard that caused me to have an empty case in the first place), the experience is so deeply unpleasant that it makes me mad all over again thinking about how absolutely useless the support is, and how much process and rigmarole they make you go through. "Take your system apart to do this annoying thing." nope, didn't fix it "Okay, now take it apart in a slightly different way to do this other annoying thing." Repeat over and over for many cycles until finally "sorry, we're not going to actually do anything to help you, even though there are many other people on forums reporting this exact same problem indicating a defect."
If you look at the r/framework Reddit, like half the posts there are people being angry about support. It's genuinely bad, and a real problem for your company. Which sucks, because the products are so great and deserve premium support.
I tried to resolve this through support, asked for a manager, suggested a refund or replacement and ended warning I’d go public when I ran out of options to break out of the support loop hell. I didn’t anticipate this would hit HN so I feel bad for you and will unlink shortly to stop the shitstorm.
If you genuinely care about customers, fix the problem: keep the laptop we sent you and send a replacement unit which has been properly tested, basically do what anyone would expect in a similar situation.
I will still not buy new hardware nor recommend you, but at least you will have shown that you fix your mistakes and I’ll publicly acknowledge it in good faith.
Anyways, I don’t have high hopes, surprise me
The final post was: The head of our support team has been driving the process improvements today and is also reaching out to you directly to share more about what happened and how we're going to make sure you have a fully working laptop. Apologies again for the compounded misses on this.
Will stick with used MacBooks (haven't had any of the 3 I have bought over the last 10 years now), Apple silicon desktops for the next few years until I can order custom board, display, battery to go in a 3D printer housing
Good luck staving off Chinese offerings that wrap the Framework idea in AI production pipeline
It's been great for me because I never want to talk to "support", I love that there is an official place to buy replacement parts for fair prices, and fix it myself. Some keys on the keyboard failed after 2 years, got replacement keyboard for $40, fixed, nice. Also good troubleshooting help from other technical users in the forums: usb ports died once, reboot didn't fix it, force battery disconnect/reconnect fixed it.
But Framework has a problem with support employees, and firmware development/release management. Probably great people who work hard, but just not smart enough.
I've seen a number of very believable stories about support asking for a bunch of screenshots and sending replacement part after replacement part, for what is a firmware bug or hardware design flaw that is by that point well known and characterized by expert users on the forums (and with home-grown hacky fixes which demonstrate the precise original flaw). The framework desktop PSU fan, the FW12 chassis cracking, usb-c charger compatibility, original FW16 heatsink with liquid metal ...
How about the Intel 12th gen year-of-firmware-struggle where there were silly file mixups - the left vs right retimers in the linux package, the windows beta release needing a "hotfix" for the model detection, but then the final release being the original un-fixed installer, for a few days until the community complaints got through. Sloppy EFI shell update script. Just basic failures of skill and attention, where external expert users are able to diagnose and fix it.
FWIW I also isolated a minor bug in the ACPI code to a particular couple bytes: https://github.com/FrameworkComputer/SoftwareFirmwareIssueTr... ... but no movement in a year. Not a big deal in the grand scheme, but you gotta be able to at least fix the easy stuff!
1. Why was our personal information being stored with Metabase in the first place WITHOUT any indications that you would do so, at the time of signing up for a Framework account, or at the time we provided our PII?
2. Even if you had legitimate reasons to use Metabase, why was our PII not anonymised or salted? That way even if there was a leak, the attacker wouldn't get anything of worth.
3. Why was my PII still stored with Metabase even after I cancelled my Laptop 13 Pro order well before the Metabase breach? If you don't need my PII, don't store it.
4. Exactly how many other thirdparty providers are you using to store my PII, how are you using it, and how is being stored and processed? How is the life cycle of my PII being managed?
Had the usage of Metabase been declared up-front, I would've never signed up for an account. You breached our trust in Framework, and you still haven't provided an explanation or a proper apology even months after the incident. Unless I get answers to these questions, I'm never going to buy a Framework product.
Would you please look into properly supporting USB-PD 15W (i.e. 3A current) power profile for the USB4 ports on Framework Desktop? It has never been working/working correctly since debut, and is causing stability issues and data corruption for high power devices like external USB4 NVME drives.
- Advertise 15W profile to the devices. Don't make devices negotiate (because they don't/can't). Lenovo laptops handled this nicely.
- Make it work whenever a device is plugged in (not only for the ones plugged in at boot)
- There is no need for the "Force power supply on in standby" BIOS config. It doesn't make sense (especially for desktops). Lenovo managed to do support that on their laptops so there is no reason a desktop can't.
https://github.com/FrameworkComputer/SoftwareFirmwareIssueTr...
BTW I'm looking forward to the new keyboard.
While I cannot recommend that particular XPS, the customer service is a benchmark for me.
Having good customer support might be expensive, but what do you think how much this story cost you? (in terms of lost revenue and brand perception)
There are several changes we made earlier this year to drastically shorten the number of back-and-forths to issuing replacement parts when submitting a support request, and we’re working to streamline that further. We’re also improving the RMA->quality->engineering pipeline to make sure we capture learnings and make fixes from field failures.