I am not sure if we do customer support well or not, but I feel like the sum of #Amethyst + the Amethyst Users chat + my DMs are working ok for now. I see many users replying when the team is not available, which is great! We could integrate creating issues from gitworkshop.dev directly in the app to facilitate tracking, but I am not convinced these Product Management formalities make great user interactions. Ideas?

nostr:nevent1qqs26tn7y0tuzfx2cyr6ecrxs7w5v7q2dcveaezuz6kmz8u7gatya0cpzpmhxue69uhkummnw3ezuamfdejsygzmuezx429rrsgm8dznh7x6ljdngmln9rgl5ydqlgp2rejxra4fkypsgqqqqqqspdr7l8

Reply to this note

Please Login to reply.

Discussion

V4V

PURA VIDA!

ABSOLUTELY!

WILL WORK FOR SATS!!!

I don't want to post about it yet, but I'm kind of working on something along that vein.

Looking forward to it. Just don't make it corporate. :)

It's definitely going to be as grassroots as possible.

I told you people want this 🔥😂

The #amethyst street team approach has been wildly successful because you & your team do a great job of educating & informing users, as well as addressing problems when you can. Damus seems to have the same thing going on. I imagine as the user base grows that will become harder to keep up with.

Would a comprehensive user guide be helpful, as in one that addresses basic features, hidden features, and common faq? I started writing one then put it aside. I could finish that & link to issue reporting. I don't know if you would want to direct to that in-app but it could be an easy reference for the street team, especially if I can get a decent domain name.

Love you guys. You quickly respond and implement even quicker. I like just DMing devs, but i do hope it's not too much burden when I do it