September 29th, 2014 Release notes: Several misc updates

Happy Monday everyone,

Today we have the following changes:

  • Chat Portal: We now show the version of the Chrome OS the visitor is using in the Chat Portal
  • Chat Portal – Team Chat:Image extensions for embedded images within the Team and visitor chats are now case insensitive
  • Chat Portal:The visitor email no longer has to be all lower-case when using the \email command
  • Stats: Add a breakdown of Top Countries to Visitor Information report
  • Stats: Fix for issue where Visitor Information reports did not use the multi widget selection
  • JavaScript API: If, on your own mobile-optimized website, you have an inline button that allows your visitors to start a chat with you, you may want to hide the “Floating Button.” You now have the ability to do this using the same SnapEngage.hideButton() function you would use on the desktop. (Note: Once a chat is in progress on mobile, the floating button is necessary, as this is the only way for the visitor to restore a minimized chat.) If you wish to run this conditionally, you can use SnapEngage.isMobile() to do so:
    if (SnapEngage.isMobile()) {

September 25th, 2014 Release notes: Analytics Additions, Visitor side fixes

Greetings everyone:

Below is a list of various changes that we’ve deployed over the last couple of days:

  • Added a breakdown of Top Countries to Visitor Information report
  • Fixed an issue where Visitor Information reports did not use the multi widget selection
  • Fixed an issue where javascript variables were sometimes being displayed as undefined
  • Fixed an issue where the first proactive message would sometimes not be displayed
  • Fixed an issue with the chat window state preventing chat continuation on mobile
  • Fixed an issue where User with Reporter Role gets redirected to the old version of stats

September 18th 2014 Release Notes: Bug fixes

Hello Everyone –

We’re continuing to remove minor bugs that we’ve found.

Changes today include:

  • Fixed an edge case where the phone number input didn’t get “internationalized”, meaning that the drop-down containing the countries, their flags and their prefixes wasn’t visible.
  • JS API: When using the Javascript event API for start chat event, we no longer report a reactive (manual) chat as a proactive chat.
  • The Call-Me logs could in some cases show up with multiple + signs, we also started to show the duration in minutes rather than in seconds.
  • Fixed an issue where some characters showed up as HTML escaped characters in your integrations.