3 ms·
<a href="mailto:..."> Just using email is not only easier to implement, it is easier for the user to use, makes the user feel better about the process (web for
by saurik 2y ago
<a href="mailto:...">
Just using email is not only easier to implement, it is easier for the user to use, makes the user feel better about the process (web forms are almost always designed to prevent feedback: an email address might still connect to a ticketing system but mentally implies a human will read and triage the message), and gives them context and history for their message (as the user has a copy of what they sent in their client).
- mmarian 2y agoI did that before and I ended up being sentenced to bombardment by spam on that address for forever.
- rrr_oh_man 2y ago> easier for the user to use, makes the user feel better about the process I'd nope out of there in a millisecond if a "give feedback" button would be a mailto.
- saurik 2y agoReally? You find it more likely that some form POST is going to result in a useful response?!? I have to often coordinate things with a ton of people who work on random projects or with the customer support of various companies, and FWIW my experience doesn't match that at all :/.
- rrr_oh_man 2y agoI'm going against the grain here probably, but I love those customer chat tools where the customer service is not a half-baked "AI" bot, but a direct line to someone knowledgeable. Or a Whatsapp/Telegram link. E.g. over the years, Raidboxes.io has frequently answered to my questions on a Sunday, in the am, in less than 15 minutes. That's an outlier, but it has anchored my expectations for the future. At the last startup I worked at we have tried to implement a similar responsiveness by utilizing a distributed team across the globe. If you funnel your customer comms into one more or less decent system (most are different shades of crappy), it can work pretty well for both customers & team.