Positive users praise Gumroad's 300ms support goal and 2-minute response times for transparency and simplicity, while negative users dismiss the target as unrealistic for code deployments and harmful to engineers.
Based on 10 visible X reactions from 26 accounts; directional sample.
Ask a question below.
Published answers will appear here.
There is no worse experience than having an AI bot instantly respond to your question that you already understood from reading the troubleshooting guides Or a response from a human where they haven’t understood the question and the context of your question. Why not solve for satisfied customer the same day instead of optimising for a 300ms response time.
@shl I really appreciate how transparent you are with all of this stuff. It's refreshing to see and inspirational to learn about how you're doing all of this.
@shl This is huge. You are definitely building the next product, actually doing customer support much better than branded products like @sierraplatform
@shl 300ms for tickets that need a production deploy is basically asking your engineers to never sleep theres ambitious and then theres unrealistic
@shl 300ms for tickets that need code deployed is wild That’s not ambitious it’s ignoring how deployment pipelines actually work
@GergelyOrosz Good to know! Will investigate. We should add a proper form to the Help Center as an option and maybe other pages should have a way to trigger. (I prefer mailto: so I can trigger from any surface and have a record in my inbox) @gumclaw create issue and PR
Our new goal is 300ms for all customer support tickets, including those that require a bug fix to be deployed to production. (If we didn’t have ambitious goals, we’d have 0 need for humans.)
Positive users praise Gumroad's 300ms support goal and 2-minute response times for transparency and simplicity, while negative users dismiss the target as unrealistic for code deployments and harmful to engineers.
Based on 10 visible X reactions from 26 accounts; directional sample.
Ask a question below.
Published answers will appear here.
@shl My ticket took 7-8 minutes to respond back fwiw Good job, tho why email only with a mailto:link? That feels somewhat archaic