Hacker News Reader

Comment by hajrice | Hacker News Reader

Hi there. Thanks for your comment and to be honest, this is still a test whether or not I should release this to the public and build it into a product. That being said, I totally agree with ya. So many people want a posterous for support. An autoupdating faq system is slightly vague, a posterous for support is much more descriptive from my perspective.

View on HN

I don't understand what "Posterous for support" means. Posterous is a blog, how can I use that for support? Also, how does this autoupdate? There's nothing on the front page about it :/

Sure. I made a bad decision using this way of explaining an idea. Sure wont do it again. Here's a simple flow from your customer's perspective.

- goes to your website

- Search's your help page, if cant find it, email you

- You get an email, you respond to it, customer is notified

- IF you forward that email to a special cool email which we give you, it's published on your support page(which is embeddable to your website).

- Next person searching for this question doeesnt have to email you as they're problem's solved!

Ah, I see, thanks. That does sound handy!

Sounds kind of cool!

Posterous is really not too well known outside of tech circle. Even for people who know and use it, more will think of it as a blog rather than "email to blog". To understand your product, people need to learn what is Posterous first. Its best to avoid such association in marketing.

You're very right. Lesson learned!

Reply on news.ycombinator.com