avlesh-singh

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.