Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Olark launches "Targeted Chat"

olark.com

Post reply on HN
Print view View original

31–40 of 65 posts

Re: Olark launches "Targeted Chat"

#31

Post by bryanh »

bcx wrote: post #30
bryanh wrote: post #28

We at Zapier love Olark. Rarely a day goes by where we don't proclaim to each other our undying love for all that is Olark. Its invaluable. Oddly enough, it is one of the most expensive SaaS apps we pay for, and if they doubled prices, we'd still pay for it. One humble request: a REST API that just spits out recent conversations. Basically a JSON version of https://www.olark.com/transcripts . Lots of Zapier customers…

If you guys create a tutorial for [1] we'll promote it on our blog and twitter. To do the json version of http://www.olark.com/transcripts we'd need to expose an Oauth endpoint and do a few other things that would probably take a while :-) (Also have you looked at http://www.olark.com/help/webhooks )

Wasn't aware of the webhook integration. Very cool! I think we can use that.

Re: Olark launches "Targeted Chat"

#33

Post by corkill »

Super useful, just trying it out.

Using it inside my web app and so want to pop up a chat when the user is on the settings page. e.g. clientname.app.com/settings, anyway to do this? I tried */settings but no luck.

I also think it would be useful if I can say if the client visits any page 5 times start a chat (not a specific page).

Also is their a way I can exclude all the people that are already users of my app from a rule, as I use the chat both on website and in the app.

Re: Olark launches "Targeted Chat"

#34

Post by nbashaw »

corkill wrote: post #33

Super useful, just trying it out. Using it inside my web app and so want to pop up a chat when the user is on the settings page. e.g. clientname.app.com/settings, anyway to do this? I tried */settings but no luck. I also think it would be useful if I can say if the client visits any page 5 times start a chat (not a specific page). Also is their a way I can exclude all the people that are already users of my app from…

Nathan from Olark here - make sure you give us the full URL (e.g., "http://clientname.app.com/settings). That should fix your issue.

The second rule you wanted to use probably can't happen just yet, but we'll look into adding it!

The third rule you can do if you use our Javascript API: www.olark.com/developer

Thanks for the feedback, and you can always email us at support@olark.com if you have any other questions!

Re: Olark launches "Targeted Chat"

#35

Post by mnutt »

latchkey wrote: post #27
bcx wrote: post #24

Earlier quoted context omitted.

I am not sure how long ago you tried Olark out, but we've made a lot of improvements in how the RPC servers work. I am still a little concerned about a slow request blocking your page though. What's your URL? Do you know if you are using JSONP?

Again, it isn't the async stuff. It is: http://server.not.responding.com> ; That causes the browser to block waiting for a response. It was a couple months ago, but I think it was olark19 not responding. While I appreciate what you guys are doing a lot, I'm not willing to be a beta tester for your networking. Stuff like that absolutely needs to be hosted on an architecture that just doesn't go down. Ever.

Many browsers support an async/defer attribute on script tags now, which will cause them to load without blocking.

Re: Olark launches "Targeted Chat"

#36

Post by corkill »

nbashaw wrote: post #34
corkill wrote: post #33

Super useful, just trying it out. Using it inside my web app and so want to pop up a chat when the user is on the settings page. e.g. clientname.app.com/settings, anyway to do this? I tried */settings but no luck. I also think it would be useful if I can say if the client visits any page 5 times start a chat (not a specific page). Also is their a way I can exclude all the people that are already users of my app from…

Nathan from Olark here - make sure you give us the full URL (e.g., " http://clientname.app.com/settings ). That should fix your issue. The second rule you wanted to use probably can't happen just yet, but we'll look into adding it! The third rule you can do if you use our Javascript API: www.olark.com/developer Thanks for the feedback, and you can always email us at support@olark.com if you have any other questions!

Thanks, the client name is dynamic, if a wildcard could be used it would help.

btw anyone not using this to get feedback from their app users is missing out!

Re: Olark launches "Targeted Chat"

#37

Post by pbreit »

noelwelsh wrote: post #10

Scaling is the issue I have with things like Olark. One-to-one chat is an expensive way to get customers. Does anyone have experiences on the effectiveness and cost of customer acquisition using something like Olark? [Let me say I love the concept of Olark. I'm just not sure how it plays out in practice.]

I don't understand this sentiment. I would kill to be able to talk to prospective customers.

Re: Olark launches "Targeted Chat"

#39

Post by daniellemswank »

corkill wrote: post #36
nbashaw wrote: post #34

Earlier quoted context omitted.

Nathan from Olark here - make sure you give us the full URL (e.g., " http://clientname.app.com/settings ). That should fix your issue. The second rule you wanted to use probably can't happen just yet, but we'll look into adding it! The third rule you can do if you use our Javascript API: www.olark.com/developer Thanks for the feedback, and you can always email us at support@olark.com if you have any other questions!

Thanks, the client name is dynamic, if a wildcard could be used it would help. btw anyone not using this to get feedback from their app users is missing out!

Danielle from Olark here. I'm one of the engineers on this project.

We have a "contains" selector that works like a wildcard. So in order to do what you want, your rule conditions would look like: "Current Url" "contains" "settings".

Re: Olark launches "Targeted Chat"

#40

Post by latchkey »

mnutt wrote: post #35
latchkey wrote: post #27

Earlier quoted context omitted.

Again, it isn't the async stuff. It is: http://server.not.responding.com> ; That causes the browser to block waiting for a response. It was a couple months ago, but I think it was olark19 not responding. While I appreciate what you guys are doing a lot, I'm not willing to be a beta tester for your networking. Stuff like that absolutely needs to be hosted on an architecture that just doesn't go down. Ever.

Many browsers support an async/defer attribute on script tags now, which will cause them to load without blocking.

As far as I can tell, the olark js block we are asked to copy into the page doesn't set this on the script element that is pushed into the dom.
Post reply on HN