The other keyboard, the one the customer already had, was the one that was obviously not working perfectly.
_
> if a customer complains about a keyboard issue that we can't reproduce, we replace the keyboard anyway.
The obvious thing to do. Not doing this is the mistake Framework made.
_
> shouldn't have to pay for the replacement part out of pocket, that's literally the entire point of a warranty.
An in ideal world, no one should have to do anything.
From a logistical standpoint, competent people know how to make results happen. As someone operating in a business I would order a new keyboard.
Could just send the entire laptop back.
_
What I can say for sure, when I have had to make sure that developers and other users are operational, not a single person went with more than a day of downtime just because one (or even two or three) laptops had issues.
Framework is awesome. I am personally responsible for more than one dozen of Frameworks being deployed and will probably be responsible for many more.
All these guys had to do was order a new keyboard. If they demanded a refund for the not-working keyboard they'd get one. I know, from experience having handled dozens of Framework laptops, Framework absolutely will do this.
You'd think someone offering consulting services would be a bit sharper..
The criticisms of the ticket ownership posture are helpful (depending on how accurate they actually are), I have forwarded this along to someone high up in Framework's support branch of its org chart I have a good connection with.