avlesh-singh

I am glad you liked the video. We engaged an agency for getting the video done.

We are different from UserVoice because we are a private feedback tool (no concept of community). Also, there are dynamic fields and the cool screenshot feature in the feedback form. Try the tab on our site.

We are different from Qualaroo, because customers can "target" our surveys at specific audiences on their websites. More here - http://webengage.com/survey/features/targeting-rules.html#ta....

You'd love to use Notifications. There's so much you can do with it. Plus, like surveys, they too can be targeted in a similar manner.

Thanks! Answers to your questions underneath -

>1. Feedback opens up and makes requests every time it loads. Can that static form be downloaded on page load and saved?

Tricky, because there's a whole lot of configuration, settings, fields etc that can be changed. We tried to avoid a db roundtrip as much as we could, but ...

>2. The Notification push message, takes Significant Real estate of my browser window(on my 11 inch Mac) and the size is not proportional to the browser window.

Very valid. We are on to it.

>3. Screenshot attachment for specific parts of the web page will be cool.

In our wishlist. Soon.

This file integrates as a widget code on customer websites. We don't expect our customers to change this code often. However, we do continue to change the underlying code (to push updates, new releases etc). The idea is that visitors on our customer websites get the new code whenever it changes.

I do agree that the number (10mins) could be a bit scientific. But you get the idea as to why we kept it as such.

It is a classic dilemma early stage companies face. I have seen a whole lot of founders stuck with this question. I am not trying to influence your decision here, but the ones that succeeded, did so by having a very clear cut focus. You either build a consumer internet company or an enterprise internet company. Trying to do both at the same time takes your focus away. I'd say stick to one.

Fixed both. Thanks :)

Yeah, for the blog use-case you can call us similar. But yes, we will let you tweak the snippet (title, description etc) for the notification once generated.

Yes, there is one. We'll build smart notifications on top of the API. Once we gain some confidence using our own API, we'll make it publicly available.

In a couple of ways -

1. WebEngage notifications can be "targeted" - it means you can choose to pop the message only to visitors meeting certain criteria. E.g. only to visitors coming from Google search, only to visitors spending 30 seconds on pricing page etc.

2. Smart notifications will automatically fetch updates from your Twitter/Blog/FB etc and create a notification out of it.

3. WebEngage notifications will have a definite call-to-action and the analytics will be focused on proving you a lot of BI around clickthrough rates.

Fixed. Thanks.

To begin with, we'll roll it out for all our customers with restrictions on the number of clickthroughs for each of our plans - http://webengage.com/pricing .. later, we plan to roll out each of our products separately with their own pricing as well. The basic paid version of Notifications will be priced in the range of $10/mo.

You missed our note towards the end of the blog :). It says the same thing.

Hahaha. Hope this thread doesn't become a Ruby/Java battlefield.

Nothing beats this!

You mean this? - http://www.metrolic.com/wp-content/uploads/2010/09/borat-mer...

Hahaha. Good one. Can you point me to the graphic of a cute look Gorilla?

How about a Giraffe? :)

Yes, but somewhere down the line. We are of the opinion that being creators of the tool, we are the most qualified and equipped to sell/market it. However, scaling that up will definitely be a problem. That said, whenever we hire sales people, we'll make sure we hire the ones fit to do "technical sales".

I am definitely missing something here. So, this is what I understand - users can send the client side info to webmasters. But how do I get to know that email id? Ain't that the only reason why services like UserVoice or WebEngage exist? All these services automatically capture the client side info (most of the info that is presented on SupportDetails) everytime someone submits a feedback on their corresponding websites.

Disclaimer: I co-founded WebEngage (http://webengage.com). And here's a shamless plug - WebEngage not only provides you all this client side info, it also captures a screenshot of the current page (on your website) the visitor is on.

Wow, that's a nice first post to launch PluggdIn TV. Congratulations team. IMO, apart from interviews etc, product showcases on the TV product might be a good idea too.

Absolutely! And see the funny reasons people have been citing in favor of such an act - http://www.quora.com/Why-does-Quora-redirect-to-URLs-in-a-wa...

Of course there is zero incentive for anyone to do it. And if everyone chose to link the way Quora does, you get a Google Analytics dashboard which cannot tell you what all URL's are sending traffic to your site/blog. I find it really difficult to imagine.

Someone finally asked the question on Quora - http://www.quora.com/Why-does-Quora-redirect-to-URLs-in-a-wa...

That's the point. It is okay as long as they play nice with HTTP headers and other info which needs to be passed downstream.

Absolutely! The post might have got some attention from Quora in that case :)

Sending an incorrect site referrer to a downstream website doesn't solve the identity problem! HTTP headers have existed even before all these applications came into being. One just has to abide by some of those basics.

A tweet was sent to Quora engineering - https://twitter.com/#!/Sengupta/status/160044848697704448. Could not find any question on Quora though.

Tracking helps you build great analytics. I, as a developer, would have otherwise no idea of what's happening in my app.

Seems you saw a Quora survey on our site? We had to change the targeting rules to make it a generic "referring site starts with Quora.com" kinda rule instead of specific URL's :(

Not sure if I understood this correctly. If Quora chose to send a Location: some-url and Status: 302, it would have definitely worked as expected.

Thanks Sampad for those kind words.