21–30 of 140 posts
Hey all! Co-founder of HUM here, and happy to answer any questions you may have about it. We've been cranking away on this product for the better part of the past year and are very excited to be rolling it out over the coming weeks.
What's Hum's relationship with Email? Will it be integrated in any capacity? Also, not in a technical manner, but how will Hum be different than any other chat program?
Why announce the product before shipping? I added my email to the list, but I probably won't remember what the product is when you finally release it. The copy could use some work, you should be able to pare down a lot of the text. Also, you could increase the font size for maximum comfort. Why is the product name capitalized? When I see HUM I think "H. U. M."
Putting aside my own aversion to yet another opportunity to ramp up my continuous partial attention deficit, this strikes me as a solution looking for a problem. One of my smartest friends noticed that when his support team answered emails quickly, the customer would treat this as an implicit invitation to shift the support thread into a support chat, via email. They added a 3-hour delay before support sees any email…
Why announce the product before shipping? I added my email to the list, but I probably won't remember what the product is when you finally release it. The copy could use some work, you should be able to pare down a lot of the text. Also, you could increase the font size for maximum comfort. Why is the product name capitalized? When I see HUM I think "H. U. M."
I'm sure the email you receive when it launches will give you all the information you need to remember what it is.
Putting aside my own aversion to yet another opportunity to ramp up my continuous partial attention deficit, this strikes me as a solution looking for a problem. One of my smartest friends noticed that when his support team answered emails quickly, the customer would treat this as an implicit invitation to shift the support thread into a support chat, via email. They added a 3-hour delay before support sees any email…
You make some excellent points about using email in a support organization. To be fair though, Hum isn't designed to be used by employees in a call center. Instead, Hum addresses a much more fundamental shift in communication patterns that is already in full swing. Conversations are getting shorter and shorter, and more to the point. Most teens I know never check their email. Many of them don't even have email addres…
While it's true that they don't use email as a primary communication medium (yet) it seems likely that this is because they also don't have jobs (yet) and that it's currently easier to talk to their friends via Instagram, WhatsApp and Tumblr.
And yet they all have email addresses, because otherwise there's no way to access most of the stuff on the web. You have to sign up, and unless you're talking about a phone-centric app like WhatsApp, there's no practical way to avoid email.
Even if you can login with Facebook Connect, you still need email to use Facebook.
So, can we dispel the myth that "teens don't have email" please?
----
As for my referencing a support operation delaying email, I used it as an example because I wanted to demonstrate that it wasn't a half-baked notion based on anecdotal evidence from one guy.
Meanwhile, conversations are most certainly NOT getting shorter. Each message in an exchange might itself be quite short, but the conversation itself really never ends.
Ask yourself what is more distracting: a long email or a series of 80 individual "short, to the point" texts, where each one vibrates your pocket and you have no idea when the next one is coming. You already know the answer. Often times you give up trying to do anything else and just stare at the messaging interface, waiting for the next message/fix to arrive.
Don't get me wrong; I use iMessage constantly and vastly prefer texting to calling people for most trivial things. But I also gave up IRC and ICQ (dating myself) cold turkey because eventually I was forced to acknowledge that it was holding me back in life. It was not more productive; it was incredibly counter-productive.
Am I missing the differences between this and HipChat?
Putting aside my own aversion to yet another opportunity to ramp up my continuous partial attention deficit, this strikes me as a solution looking for a problem. One of my smartest friends noticed that when his support team answered emails quickly, the customer would treat this as an implicit invitation to shift the support thread into a support chat, via email. They added a 3-hour delay before support sees any email…
Heaven forbid that businesses might engage with customers...
All this particular business did was tell people that if they have a time-sensitive problem, call them and get immediate help.
Delaying replies to emails solved a number of problems and streamlined the exchange. Everyone seems happy.
Putting aside my own aversion to yet another opportunity to ramp up my continuous partial attention deficit, this strikes me as a solution looking for a problem. One of my smartest friends noticed that when his support team answered emails quickly, the customer would treat this as an implicit invitation to shift the support thread into a support chat, via email. They added a 3-hour delay before support sees any email…
You make some excellent points about using email in a support organization. To be fair though, Hum isn't designed to be used by employees in a call center. Instead, Hum addresses a much more fundamental shift in communication patterns that is already in full swing. Conversations are getting shorter and shorter, and more to the point. Most teens I know never check their email. Many of them don't even have email addres…
Are they mostly talking to friends via email? Probably not--I don't think that's ever been the case with teens--but I can't imagine that they just flat out do not have an account anywhere.
In Firefox, scrolling down the page below the cover image causes a Youtube embed of what I assume is the trailer to get stuck blocking a large portion of the content of the page.