5 ms·
Hey Chris, Thanks for your comment. Regarding pricing, this is all we've said publically : http://docs.intercom.io/#PricePlans http://docs.intercom.io/#PricePl
by destraynor 15y ago
Hey Chris,
Thanks for your comment. Regarding pricing, this is all we've said publically : http://docs.intercom.io/#PricePlans http://docs.intercom.io/#PricePlans - if it's a big obstacle and concern for you, mail me and I can give you some loose bracket to inform your decision
Along with messaging, the JS library tracks web application activity sending us useful data such as "last seen" which in turn let's us email "users not seen in the past 30 days".
You can use our API if you prefer http://docs.intercom.io/api http://docs.intercom.io/api but the client works really well for lots of this stuff.
- chrisacky 15y agoThanks des. We are relying heavily on caching, and I noticed that you require the users email and created at to be available in the page with each snippet? Could you explain this a little more? Is this just for the initial signup for the user, or is this for every request that the user makes. I mainly ask because it would seem odd to pass the "created_at: 1234567890" in every request.
- destraynor 15y agoHey Chris, You can do this via the API instead -> http://docs.intercom.io/api http://docs.intercom.io/api We're constantly improving the way this works, but in short the reason behind the current behaviour is simply that we wanted the initial sign-up experience to be both easy and powerful. Soon it won't be necessary to pass it after the initial call (and for what it's worth it's only useful so that we can distinguish your existing users from your new signups) Hope that makes sense, Des