Tag Archives: mobile optimized

Happy November! Here are the latest fixes…
  • Fixed an issue where iOS users of our mobile app weren’t receiving push notifications.
  • Fixed an issue where the saving of agent survey data could in extremely rare cases also affect other data collected during the chat.
  • Fixed a bug with Enterprise accounts where users were not able to add a new widget without being sent to the upgrade page. You are now able to create up to 100 widgets with your account level, happy widget-creating!
  • Improved the communication fallback mechanism in the Chat Portal when there are network local connectivity issues.
  • Fixed an issue where sound notifications were not playing in Chrome when the Chat Portal tab was in the background or not selected.
[…]

Full Article →

Happy Friday once again, For this week we have made the following changes: New:
  • Tweaked Team Chat so that a space is automatically added after using an @mention
  • Made some backend changes to the way we handle user statuses to support our upcoming mobile application.
Fixes:
  • Made sure the page titles in the Admin Dashboard are always correct.
  • Resolved a connection problem with our our Jira integration.
  • Addressed an transfer issue where the receiving agent wouldn’t always be altered to the incoming chat.
Cheers! […]

Full Article →

Your customers are mobile, and now so are all of your favorite SnapEngage chat features Our newly improved mobile-optimized visitor chat window automatically detects when users are on a mobile device and allows your visitors to seamlessly interact with your agents. And better yet, your admin dashboard settings allow you to customize the look-and-feel of your mobile chat window to best represent your brand. Proactive Chat Support Now you can send targeted proactive chat invitations to mobile website visitors in addition to desktop users. And the best part is that the same rules that you set up for desktop chat automatically carry over to mobile, so you only need to configure your rules once. […]

Full Article →