Remix.run Logo
▲ all2 6 hours ago

I don't understand why this isn't 'alright, pack it up and ship it and we'll send you a replacement'.

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.
▲cassianoleal 6 hours ago | parent | next [-]

> I don't understand why this isn't 'alright, pack it up and ship it and we'll send you a replacement'.

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".

▲buildbot 5 hours ago | parent | next [-]

Best thing about Dell for example, with an enterprise contract you can overnight parts based on a machines service tag and they come with a prepaid return label, super easy and simple.

▲all2 2 hours ago | parent [-]

This kind of tracking is 1 week's worth of effort away from anyone in a manufacturing environment. You can vibe code the simplest CRUD imaginable and it will handle all tracking and queries for a rather large amount of items without choking (unless your agent did a terrible job or misunderstood which kinds of information need to be extracted).

▲bombcar 5 hours ago | parent | prev [-]

I'm fine with a middle ground - either run the support questions/tests and get the prepaid advance RMA, or say "I know what the fucking problem is, give me the advance RMA and bill me for shipping if the returned part is fine and I'm a dumbass."

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.

▲philistine 5 hours ago | parent [-]

Exactly. Framework prides itself on its repairability, yet their support acts like any other PC manufacturer. If your stuff is so repairable, why can't I get billed the parts I know I need, and I can prove to you that this was necessary so you don't bill me?

▲andix 3 hours ago | parent | prev [-]

It's cheaper in the short term to just ignore complicated support issues. As long as customer demand is high and orders are coming in, it's also a successful strategy.

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.