3 ms·

I think it is better to build your own brand name rather than relying on another one. An 'autoupdating FAQ system' is a better description/tagline than calling

I think it is better to build your own brand name rather than relying on another one. An 'autoupdating FAQ system' is a better description/tagline than calling it Posterous for customer support. Posterous is famous but what if a small online flower retailer wants to use your product and he has no idea what Posterous is? It is better to directly explain what your product does rather than relating it to another one. On the other hand, if a tech blog writes PilarHQ is the posterous for customer support, that is well and good!

hajrice 16y ago
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.
- StavrosK 16y ago
  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 :/
  - hajrice 16y ago
    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!
    - StavrosK 16y ago
      Ah, I see, thanks. That does sound handy!
    - ideaverse 16y ago
      Sounds kind of cool!
- gaiusparx 16y ago
  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.
  - hajrice 16y ago
    You're very right. Lesson learned!

hajrice 16y ago

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.

StavrosK 16y ago
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 :/
- hajrice 16y ago
  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!
  - StavrosK 16y ago
    Ah, I see, thanks. That does sound handy!
  - ideaverse 16y ago
    Sounds kind of cool!
gaiusparx 16y ago
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.
- hajrice 16y ago
  You're very right. Lesson learned!