Remix.run Logo
▲ reticulates 3 hours ago

I have extensive support experience, you're right, support is not easy, that said, there is a very easy win: hire enthusiastic support staff that are overqualified. Customers don't like slow support but slow support is forgivable if it is good support. Framework's support as described in the post is a disaster, the worst type of support. Bad support compounds: if your support agents are doing the bare minimum to move a ticket along, they're pissing off customers and missing insight that would be valuable to the teams responsible. A customer support team of 2 technical people will deliver more for the company than a customer support team of 10 untrained people.

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.

▲egorfine 2 hours ago | parent | next [-]

I have been a chief developer of a large service (think millions of daily users) and I had a habit of opening the support inbox and replying to users. In a typical evening hour I would clear the inbox and successfully resolve a mountain of tickets. Not to mention the important insight I was collecting from real users' feedback and real bug reports.

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.

▲exographicskip an hour ago | parent | next [-]

You're doing the lord's work

▲jfsebastian an hour ago | parent | prev [-]

[dead]

▲vaylian 2 hours ago | parent | prev | next [-]

> The quick fix for any company in this situation is to require that technical people across the company take responsibility for customer support.

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.

▲jethro_tell an hour ago | parent [-]

That’s ok, I’ve done a thing where they pick up a 1 or 2 hour shift and look through the tickets that have high message count so or have been open too long. They get paired up with a support tech.

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

▲anentropic 2 hours ago | parent | prev | next [-]

This ^

▲raverbashing 2 hours ago | parent | prev [-]

> Bad support compounds

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"