Date of Release: March 14, 2019
- Latest version of Safari, Chrome, Firefox, or Microsoft Edge
- Instabot Account
The below enhancements are new functionality items in this version.
Previously you could access bot analytics from a few different places in the portal. We understand this might have been confusing when navigating the site.
We have taken this to heart and are working towards a better Analytics product. As our first step we have consolidated access to bot analytics to a single place. From the Analytics page in the navigation menu, you can view the bot metrics for every version of all bots that have been published.
Stay tuned for more changes to come that will help you visualize the success of your bot campaigns!
Now that the scheduling node is doing all the work to book your meetings, we wanted to step it up a bit. Now you can sync these events right with your integrated service (Salesforce, Oracle Eloqua, or Zapier)
For Salesforce or Eloqua, the option to send meeting data to your CRM will be part of the Advanced Options on any scheduler node if the integration is set up.
When this check box is enabled and the bot published, any time an event is confirmed in the bot conversation, the lead and event will be created in your CRM.
For Zapier, all of the meeting details are available to add to any action by searching for Scheduled as the keyword. All available properties will be filtered to select from.
You can send this scheduled meeting data to any Zapier action, not just a CRM. For example you can include these details in an email or Slack notification as well.
Just a small update, but we are working to make the meeting scheduler more friendly. So now all bot confirmation messages will include the profile image of who the meeting will be confirmed with.
Make sure to upload your image within your Instabot profile to personalize the meeting confirmation for your end users.
The below issues are fixed items related to known issues in previous versions.
- Resolved Live Chat sessions were not moved to the closed conversation list
- Teaser preview was showing incorrect color settings
- Two nodes were able to be added with the same name
4.Viewing the on-boarding screens on a small resolution hid action buttons.