Release Date: 10/30/23: 

CX Manager

Performance

• We removed some component queries to improve the performance of the following actions when editing a Case: 1. Viewing the Events tab in column 2, 2. Viewing the Files tab in column 2, 3. Opening and deleting a file from the Files tab, and 4. Adding a Product using the + button in column 1.
• We removed some extraneous route calls to our old Cases product to improve the performance and load times of Cases. 
• We removed unused stores from the Case edit screen to improve performance and load times when editing a Case. 
• We improved the speed and reliability of chat tiles that appear in the top navigation bar of the application when a new chat is created. Chat tiles now appear up to 65% faster.
• We improved the overall view rendering logic of Cases to improve load times.
• We optimized the performance of saving a Case which will allow users to save cases faster. This will also increase the speed of starting new chats in Messenger and creating cases via the Phone APIs.

Bug Fixes

• We fixed a bug where the Open Case count in the Customer panel on the Case edit screen was incorrect. Any Cases with the following statuses will now be counted as Open Cases: New, Ready, Waiting, Scheduling (Work Order), Scheduled (Work Order), En Route (Work Order), and Job In Progress (Work Order).
• We fixed a bug where when you click on View All Cases in the Customer Panel on a Case, it was showing incorrect information. The Case counts at the top of the View All screen are now correct. The number of pages are correct and the pagination controls work as expected. Also, only Cases associated with the Location will appear in this list. 
• We fixed a bug that prevented organizations from using custom Product picklist fields in Automations on Location updates. You can now use custom Product picklist fields as filters in Automations and properly select the product from the dropdown option.
• We fixed a bug where surveys that were automatically being sent for private label teams were not using the appropriate branding the same way they were when they got manually sent. Now, if a Team has the appropriate branding, is private labeled, and their organization has Auto-send Survey enabled, anytime a case that is sponsored by that team gets resolved, a survey is sent with the appropriate branding.

Journey Orchestration

• We launched a new Journey Analytics Dashboard, which provides significant new insights into customer experiences as they progress through a Journey. This includes high-level metrics, time spent in each activity, risk and churn prediction, journey improvements over time, and much more. You can read the full release notes here. 
• We added Relative Due Dates to Tasks in Journeys. This allows teams to set due dates relative to when the Task gets created in order to better manage SLAs and keep journeys on track and progressing successfully. 
• We removed the requirement of selecting an Automation when adding an Automation Activity to a Journey in the Journey builder screen. This will allow teams to build Journey outlines more quickly and come back to add the details later on. We have added an error reminder when the Journey is published if any Automation Activities are missing an Automation.

Tasks

We launched several enhancements to Tasks, including:

1. Task Templates - the ability to create and reuse templates of Tasks that can be applied to Cases to ensure consistency processes.
2. Task Relative Due Dates - the ability to set due dates relative to when a Task is created in addition to setting a specific date and time.
3. Tasks on My Work - we now show all Tasks assigned to you at the bottom of your My Work screen so you always know if a new Task gets assigned to you or your teams.
4. Task Analytics - we added robust analytics and new a Task Dashboard to bring more visibility and insights into Tasks, including ownership, due dates, and more.

You can read the full release notes on the Task updates here. 

Knowledge

• We fixed a bug where users were not able to tab to accordions in certain Articles. 
• We removed the "Shared with me" option in the new Insert Article modal found in the Knowledge Editor. 

Virtual Assistants

When deploying a Virtual Assistant that has less accuracy than a previous revision, we now show a warning pop-up notification rather than an error. This allows users to continue with deployment and not get blocked.

Admin & Settings

We introduced a feature improvement for the "Issue Creation Email Forwarding Addresses" field which is found in "Settings > Communications Settings". Originally this field had a maximum number of characters set to 255 and it was behaving to spec. However, this 255 character limit significantly reduced the number of forwarding email addresses you could add to that field. The new maximum character limit is now 1023 so users can add more forwarding addresses.

Release Date: 09/14/23: 

CX Manager

• We improved the UI when resolving a Case so the Select Survey dropdown and Send Survey button in a Case will be disabled if the Sponsor Team or the Owner Team of the Case have the 'Disable Customer Emails' flag turned on or if the Contact on the Case does not have an email address.
• We updated the logic on the Cases list screen to load new users to the Open Cases View instead of All Cases by default. The View you last accessed will continue to load as you navigate around CXME.
• We removed the Time Zone Mismatch modal that would appear if you logged in and your local computer time differed from the time zone in your profile.
• We updated the logic of our Ready and Waiting Statuses to only apply to Case Type = Support. We also Renamed the Remote Status to now be called Ready. This will enhance performance across the platform where status filters are used.
• We fixed a bug where creating a custom View in Cases that contained a custom field as one of the filters was causing a runtime error. You can also now export that custom view to Excel or switch between it and other views without receiving an error.
• We fixed a bug where fields added to the Location Block found in the Customer panel were not being displayed properly.
• We fixed a bug where if you resolve a Case as you create it and then reopen the Case, the edit button would disappear until you refresh the page. If you reopen a Case that you resolved upon creation, the edit button will now be immediately available.
• We fixed a bug where new Contacts were not being created if the Customer Contact fields were being filled out when creating a new Location from the Customer panel in a Case.
• We fixed a bug where updating custom Views that were grouped would display no or inaccurate results.
• We improved the load time of opening a Case from the My Work or a Case View. Cases now load 20% faster. We will continue to optimize slow-loading screens with each subsequent release.

Automations

• We fixed a bug where Automations with a Modify Data Action that updates the Tag field was not functional. Now you can update the Tag field on a Case through an Automation.
• We fixed a bug with the Send to Others function as part of the Send Email Alert Action in Automations. Previously, the recipient would receive multiple copies of the email, now they only receive a single copy of the selected email.

Knowledge

• We updated the Article editor to default to the To Do tab if there are any Comments added to an Article. Whenever you click on an Article from Knowledge Home, if that Article has at least one Comment added to it, the To Do tab will be selected by default instead of the Details tab.
• We updated the Discard Draft and Unsaved Changes modals in the Knowledge Editor for ADA compliance. Both will now be announced by a screen reader.
• We fixed a bug where tabs in articles were not working properly. They were showing the content of all tabs instead of the selected tab.
• We fixed a bug where there was a delay after clicking Submit when adding a comment that allowed you to click the Submit button more than once and create duplicate comments. The Cancel and Submit buttons will now be disabled after clicking the Submit button once to prevent duplicate comment additions.
• We fixed a bug in the new Insert Article modal where you would only receive results if the phrase you searched for matched exactly. We also moved the Embedded checkbox to the top of the modal to improve the UX workflow of the new modal.

APIs

Updated our OBO (On Behalf Of) Headers to allow Service Provider Organizations to access api/v3/schema/list endpoints for the Organizations that they provide services to.

Messenger

• We updated Messenger to retain the state and screen that the user is on as they navigate between various pages of a website or application that has Messenger embedded. This means that if the user is actively chatting, Messenger will remain open on the chat as they navigate through the site.
• We added functionality that remembers if a user closes the welcome pop-up message in their Messenger session. This will prevent the welcome pop-up message from showing on every page load during a session after a user has already closed out the pop-up message once.
• We fixed a bug that was preventing CSAT ratings (1-5 stars) added at the end of a chat session from being saved onto the Case.

Virtual Assistants

• We fixed a bug where manually changing the Contact on a Case during an active Chat session with a Virtual Assistant would cause the Virtual Assistant to say that the team was not available, even when the routing action was set to Always Route.
• We fixed a bug that was causing Training failures for phone and email entity types.

Reports

• We fixed a bug that was causing a Runtime Error when the filter “Created” with the operator “Is Before” or “Is after” was selected.
• We fixed a bug that prevented users from using custom picklist fields as filters on Reports. 
• We fixed a bug that prevented the "In Last # Days" and "In Last # Months" operators from working on Report filters.
• We fixed a bug where the Forms Report export was not properly filtering the data based on the provided start and end dates.

Admin & Settings

We updated the verbiage from "Issues" to "Cases" in Settings > Roles & Permissions to be consistent with the platform-wide Cases concept.

Release Date: 06/15/23: 

CX Manager

• We enhanced our application cache to improve overall load times.
• When a screen reader is focused on the phone case button, it will now announce it as the current phone case button.

Knowledge

• We updated the View Articles and Labels permission so Users in a role with that permission enabled are able to view all published Articles in their organization and not just Public articles.
• We updated the Clear Filters button in Knowledge Home so it will now be disabled if no filters are applied. 
• We updated the way Search Terms work in Knowledge so you can add phrases to Search Terms. If you add a phrase as a Search Term, the Article it was added to will only show up in the results if the entire phrase is searched for.  
• We added a feature that allows you to show or hide Sections on your external Knowledge Library homepage based on whether or not Users are logged in. Checking the Internal box next to a section will only display that Section and the Labels it contains when Users are logged in. Leaving it unchecked will show the Section and Labels regardless of whether Users are logged in or not. 
• We updated the behavior of inserting an Article as a link so the link stays in line with the rest of the text and does not break to a new line.
• We updated the default URL when you clone an Article. Instead of using the backend ID of the article, the default URL will now be the title of the Article with "-CLONE" added to the end of it. 
• We fixed a bug where you needed to refresh the page after performing certain bulk actions in Knowledge Home. 
• We fixed a bug where the Save button was disabled in the Article editor after pasting an image. 
• We fixed a bug where new Labels were not immediately showing up as available when editing or creating new Articles.
• We added the Session Timeout Warning modal to the External Knowledge Library so if you are logged in and your organization is set up to log you out after a specified idle time, you will now see the same modal you see in the platform.
• We updated the styling of the Session Timeout Warning modal to be ADA-compliant. 
• We fixed a bug where the toolbar that appears in the editor when you select an image, video, etc, disappears when you scroll. 
• We improved the behavior of removing a Label avatar. If you have any Labels on your home page that do not have custom avatars or had their custom avatars removed, only the label text will be displayed. We also updated the Edit Label modal to streamline the workflow of changing Label avatars so you can just select the image you want rather than having to first click Browse, then Upload. 
• We made updates to the content of an Article when in the view state for ADA compliance. The Article now has an accessible name, paragraph styling now matches the editor and external library, and all interactive content is reachable and operable by keyboard. 
• We removed the search bar at the bottom of the Articles list in Knowledge Home since we already have a search bar in the header.

Integrations & APIs

We added new API v3 endpoints to allow a user to create webhooks via APIs.

Messenger

We fixed a bug where disabling and re-enabling a Messenger (Web Connect) channel would remove any configured Availability settings. 

Virtual Assistants

We fixed the issue on Virtual Assistants which was causing Training Failure for some of the entity types.

Reporting & Dashboards

• We fixed an issue with Reports where exporting and downloading reports were empty when built with custom fields.
• We added user email, first name, and last name as part of reporting fields on our dashboards.

Hello, OvationCXM world!

We are thrilled to announce the release of the Topic Modeling Flow for training unhandled responses in the OvationCXM Virtual Assistant. Unhandled responses are phrases that your customers type when interacting with a Virtual Assitant that don't match to a response you have defined.

The following feature is now available under the clustering section on the VA navigation panel. This innovative feature empowers users to enhance the VA's understanding and response accuracy by leveraging advanced clustering and modeling techniques to efficiently organize and train unhandled conversations.

Overview:

The Topic Clustering Flow is a powerful feature that empowers users to efficiently train unhandled and missed user responses. With this feature, our state-of-the-art AI embedding model will create clusters of unhandled phrases for users to map them to intents, and train the system for improved response accuracy.

The Flow:

Key Features:

Cluster Creation: The Topic Modeling Flow automatically generates and names the clusters of unhandled phrases. By clicking on "Populate Clusters," users can quickly view and organize unhandled responses based on common topics and patterns. Users can also manually create new clusters to categorize relevant unhandled phrases into it

Cluster Details and Metrics: Users can access a dedicated view that provides comprehensive information about each cluster. This includes overall impact metrics, top keywords, the status of each cluster, and the intent it is mapped to. This overview helps users understand the relevance and importance of each cluster.

Phrase Acceptance and Rejection: Users can review the phrases within each cluster and accept or reject them accordingly. Accepting a phrase indicates that it should be mapped to the associated intent while rejecting a phrase excludes it from the training process and maps it to an ignored phrases pool.

Cluster Management: Within the cluster view, users have the flexibility to perform various actions. They can rename clusters, map them to specific intents, and interact with the phrases within each cluster.

Drag and Drop Functionality: To further customize the clusters, users can easily drag and drop phrases from one cluster to another. This feature allows for intuitive organization and refinement of the unhandled responses.

Training Process: Once all the clusters are prepared, users can initiate the training process. This step ensures that the phrases within each cluster are properly mapped to the corresponding intents. After training, the system is reset and ready for the next round of virtual assistant training.

Benefits:

Enhanced Training Accuracy: By mapping phrases to specific intents and training the system, users can significantly improve the Virtual Assistant's response accuracy. This leads to a more seamless and satisfactory user experience.

Efficient Cluster Management: The Topic Modeling Flow simplifies the organization and management of unhandled responses by automatically creating clusters based on similar topics. Users can easily navigate and interact with clusters, saving time and effort.

Intuitive User Interface: The drag-and-drop functionality and user-friendly cluster view make it straightforward for users to customize and refine the clusters according to their requirements.

Streamlined Training Process: The automated training process ensures that phrases are accurately mapped to intents, eliminating manual intervention and reducing the risk of errors.

We are excited to introduce the Topic Modeling Flow in the OvationCXM Virtual Assistant and we would appreciate your feedback as we continue to enhance our VA platform.

For more information or assistance, please contact our product team at product@ovationcxm.com.

Note: This release note provides a high-level overview of the Topic Modeling Flow features. For detailed instructions on how to utilize this feature, We will be adding relevant knowledge articles and documentation.

Hello, OvationCXM world!

We’re pleased to announce a new feature for OvationCXM Virtual Assistants: Sentiment Analysis! This new capability provides valuable insights into the conversations your virtual assistant (VA) is having with customers.

Our Sentiment Analysis feature offers an effortless and accurate way to measure customer sentiments. It uses a combination of natural language processing and artificial intelligence to classify the conversations into three emotions:

• Positive
• Negative
• Neutral

Now with Sentiment Analysis as part of OvationCXM’s VA Analytics suite of tools, you can better understand customer sentiments that can be used to improve customer engagement and drive operational efficiency.

We are adding visualization on the VA Analytics dashboard to quickly and easily understand the sentiment of your customers’ conversations with your virtual assistant.

Some of the visualizations we have added:

1. Overall Customer Sentiments: To provide an overview of the overall sentiments of the customers talking to VAs. It will enable you to get the full view of your customers' experience chatting with your virtual assistants.

2. Sentiments on Cases: To connect the user sentiments on VA conversations with the Cases they relate to. This will provide valuable analytics on how the sentiment of users impacted each case resolution.

3. Sentiment of Specific User Messages: To get a granular understanding of each message and the user sentiment at that time. This will help you to identify and analyze particular messages and why the occurred so you can better handle similar messages in the future.

4. Sentiments on Intents, Entities, and Flows: To provide analytics on customer sentiments with each VA intent, entity, or flow created. This will help you improve the particular intents, entities, or flows that are creating more negative sentiments and promote the ones that are creating positive sentiments.

Rollout Plan:

We will be adding the Sentiment Analysis Visualizations on the Virtual Assistants Analytics Dashboards following the 4/18 release. Please email product@ovationcxm.com if you would like access to User Sentiment graphs on your VA Analytics Dashboard.

Release Date: 04/18/23: 

Starting with this release, we shifted to monthly software releases. Here are the updates going live with this release:

CX Manager

• Fixed a bug where the phone screen pop icon was sometimes routing the User to an incorrect case
• Fixed a bug where Users were receiving an error message after editing and saving Form responses
• Reduced load times for screens containing Customer data

Knowledge

• We are excited to announce a new feature that allows users to restore Previously Published versions of Articles as editable Drafts. With this update, you can easily retrieve any version that you have published in the past and restore it as a Draft for further editing and/or publishing. If you already have a Draft version of the Article, you will receive a prompt letting you know that restoring the Previously Published version will delete your current Draft.
• We updated the way Insert Articles look in the new editor. If you insert an Article and do not choose to embed it, there will be a link to the Article that looks and behaves the same way inserting a link would. If you embed the Article, you will be able to see the entire embedded Article as if you were viewing it in the external Library. 
• Added a Load More button to the Version Picklist when in the view state of an Article. This will improve overall load times by limiting the list to 25 versions.  If you have more than 25 versions of an Article, you can click on the Load More button at the bottom of the list to access the remaining versions. We also fixed a bug where the Published and Draft versions were not always listed at the top of the list. 
• Added the ability to delete the entire Article to the more options menu when you are in the view or edit state of the Article
• Fixed a bug where inserting a file into an Article was not displaying the name of the file
• Fixed a bug where the Labels section while editing an Article would sometimes get stuck in a loading state. The issue was occurring due to Sub-labels not being deleted completely. We improved the behavior of deleting Labels and Sub-labels.
• Fixed a bug where Users were sometimes being logged out due to inactivity without receiving a notification
• Fixed a bug where archived Articles were appearing in the list of selectable Articles when inserting an Article

Virtual Assistants

We are excited to announce the launch of our Topic Modeling update to our Virtual Assistants, which will allow you to easily enhance and fine-tune how your Virtual Assistants respond to customer inquiries. We will share a full detailed post on topic modeling soon, but here is a preview of the new functionality: 

• Added a default view page to review each individual cluster. This page will enable users to get relevant information/analytics on each of the phrases, select/ignore phrases, rename the cluster and map the cluster to relevant intents for training.
• Created a new page under "Clustering" section of Virtual Assistants to run the Topic Modeling flow which automatically creates the clusters with unhandled user responses for mapping them to VA Intents. 
• Added a default view page to review all the created clusters under "Clustering" section of the VAs. The page will enable users to get relevant information, select/ignore phrases under each cluster and map the cluster to relevant intents for training.
• Integrated BERT Topic Model with our VA classification models to capture, classify and train any unhandled/unclassified user responses
• Added a static Ignored cluster which will collect all the user-ignored phrases. The following Ignored cluster can also be mapped to an Intent
• Added the capability to collect the user responses from Messenger instances as training data for the Topic Model
• Added Cluster Table Creation functionality where Topic Model will group the unhandled responses into relevant clusters and populate the tables with the generated cluster details
• Fixed an error, which sometimes prevented the Bots Activity table from successfully loading on the Analytics Dashboard

Connectors & APIs

• Fixed a bug where the customers/location/get endpoint on APIv3 was not returning the filtered location

Admin & Settings

• Fixed a bug where adding conditional logic to Custom Fields on Case and Location layouts was not working as expected. You should now be able to apply Show/Hide logic to Custom Fields based on one or more requirements. 
• Fixed a bug where all of the text became distorted after creating a new Tag in Settings
• Fixed a bug where Users were allowed to update Tags with Teams that they were not on

ADA WCAG 2.1

We made several color and styling enhancements throughout the platform to continue on our path of becoming ADA WCAG 2.1 compliant. These color and styling updates were applied to input fields, switches, the main navigation menu and dropdown, text, and button borders. 

Release Date: 03/23/23 

CX Manager

• Added a toggle to the IMAP email integrations to optionally ignore the auto-generated email headers and thus allow auto-generated emails to create cases in your CXME
• Added additional monitoring and alerting on IMAP email integrations to alert teams if an email integration connection fails
• Reduced load times for screens that contain Customer data
• Fixed a bug where custom date fields on the Location Layouts were not always displaying correctly
• Fixed an issue where Automations did not always trigger when the proper criteria were reached
• Updated colors throughout the application from teal to blue

Knowledge

• Updated the way you select multiple Articles on Knowledge home screen. You no longer have to click the Select button to make checkboxes appear. They will always be visible as long as you have a specific Library or Label selected.
• Updated the user workflow for adding Comments to an Article
• Added an "Articles" header above the list of Articles when you are viewing a page in the external library that has both labels and Articles listed
• Added the ability to include alt text when uploading an avatar to your external knowledge library
• Fixed a bug where changing multiple Article's Access Controls with the multi-select action did not properly change Internal Articles to Public
• Fixed a bug where labels containing public Articles would disappear after a User logged into the external library
• Fixed a bug where error messages were being displayed when attempting to insert legitimate image files into the body of an Article
• Fixed a bug where article stats were no longer updating properly

Integrations & APIs

Added extended standard field and custom field support to the Case Created and Case Updated Webhooks

Virtual Assistants

Added the ability to create a lead in Salesforce directly from the Virtual Assistant conversations. When enabled in a Flow, your Virtual Assistant can capture the user information and send it directly to Salesforce to create a new lead.

Admin & Settings

Fixed a bug on active Custom Fields that showed the Field Type field as editable even though it was not editable

Release Date: 03/07/23

CX Manager

• Enhanced the performance of loading customer profiles, including the Customer panel of the Case screen
• Fixed an issue where a user wasn't properly navigated to the correct Case when using Global Search from My Work
• Fixed an issue where the conditional logic on the Case Layout was not working when setting a field to Show when X is not Empty
• Improved the performance of running Automations
• Fixed a bug where Custom Fields were not showing up in Case Layouts unless the Ecosystem box was checked
• Fixed a bug where the Custom URL Field type did not open URL links
• Fixed a bug where Users were being suggested Internal shared Articles in Cases 
• Fixed a bug where you had to delete a Case twice in order for it to be properly deleted

Knowledge

• Drafts will now automatically be saved whenever the Session Timeout Warning modal appears so any changes you make get saved before you are logged out for being idle in the platform
• We updated the functionality of Tokens to allow multimedia and more rich text options
• We added Inter as the default font option when creating a new library. We also added Roboto and Montserrat as font options
• Fixed an issue related to sub bullets in numeric and bulleted lists. You can now indent sub bullets as well as change the list type in a nested list
• Fixed a bug where tagging Search Terms to a Knowledge Article would prevent that Article from showing up in search results
• We fixed a bug where inserting a token into an Article would cause a line break that put the token text on a separate line

Integrations & APIs

We added new GET and POST API endpoints for Automations, which will enable teams to get all their existing automations as well as trigger Automations via API. These new APIs will be available in our API documentation at developers.goboomtown.com/api.

Virtual Assistants

• Sentiment Analysis is now available as part of Virtual Assistant Analytics. Your Virtual Asissant will now be able to classify user responses into the following sentiments: Positive, Neutral, Negative.
• Made some small styling enhancements to the bot builder to add a bit more space for the bot builder interface
• Updated the background color of the selected left navigation item in the Bots section
• Updated the interface to minimize the main Settings navigation when in the Bots section
• Fixed an issue where embedded flow nodes all contained the text, "invalid" after initital creation
• Improved the performance of deleting Virtual Assistants

Reporting

• Fixed a bug where not all users could see all Folders under Reports.

Release Date: 2/10/23

CX Manager

Cases

• Fixed an issue where the conditional logic on the Case Layout was not working when setting a field to show when X is not Empty
• Fixed an issue where the Location Name was missing from the Location overlay on the Case screen
• Fixed an issue where if an organization has Custom Ecosystem Fields in their Case layout, users in their ecosystem but outside of their organization could not see these fields when they are creating a new Case
• Updated the tab name from Integrations to Connectors on the Solutions panel of a Case

Communications

• Fixed an issue where users would see a message with a snippet of code in the communications panel when a customer clicked End Chat in Messenger

Knowledge

• Fixed an issue where the page would sometimes fail to load when creating a new Article while actively editing another Article

Virtual Assistants

Virtual Assistant Connectors

We made the Virtual Assistants more actionable by adding the ability to capture and send user data through connectors/API integrations during conversations. Users can add connector actions on their Virtual Assistant flows to send data from conversations to third-party connectors. As part of the first release, we are launching lead generation on Salesforce through these conversations. With connector actions, the Virtual Assistants can now act as a single access point connecting different services internally and externally.

• Added a Connectors Icon on the Virtual Assistant Builder Canvas to add and connect connector actions on Flows. Supported connectors that are integrated and authenticated on OvationCXM platform will be available for the users to choose from the connector list.
• Added functionality to directly create a new lead on Salesforce from the Virtual Assistant conversations. Available for organizations having Salesforce connector pre-authenticated and integrated on their OvationCXM platform.
• Added ability for users to map entities/customers/locations/cases/manual input to the following fields (Channel, Name, ,Email Address, Phone Number) for "Create a new Lead" action with Salesforce connector
• Added the ability to display the required and optional fields that can be sent to perform the selected action from the selected connector. Users can map entities, locations, cases or customers to these field or can add a static manual input
• Added the connector fields to the reporting data for Virtual Assistant analytics
• Added the functionality to test a connection while "Create a new Lead" on Salesforce as action for a Virtual Assistant flow. Test Connection button will create a dummy lead object with dummy values on Salesforce for users to verify the connection link and field-object mapping.

Additional Updates

• Fixed an issue that prevented Virtual Assistant from getting initialized and responding to the messages coming from the SMS channel
• Added Sentiment Analysis as part of Virtual Assistant Analytics. Virtual Assistants will be able to classify user responses into the following sentiments: Positive, Neutral, Negative.

Reporting & Dashboards

• Fixed an issue where the MID field wasn't being updated on report data after being updated from its original value

Admin & Settings

• Fixed a bug where changing information on a Team in the Platform would remove that team from any Custom Alert Templates previously used by that Team
• Fixed an issue where the link sent within the password reset emails was not always working

Release Date: 01/20/23

CX Manager

• Made an update to automatically refresh the Case List View when clicking the back button from a Case Four Panel back to a Case List View to ensure the most up-to-date information is shown on the Case List View
• Updated the Case Layout logic to make the Owner Team field on any Case or Work Order Layouts required to save or resolve the Case
• Fixed an issue where the correct Resolution Status was not always showing
• Fixed an issue where the expand/collapse button on the Case Panel (Panel 2) of a Case was not collapsing the panel back to its original size
• Fixed an issue where clicking Cancel during the Change Customer flow on a Case was brought back to the Case List instead of remaining on the Case
• Fixed an issue where the Escalated icon did not display on a Case until after a user refreshed their browser
• Fixed an issue where clicking the Edit and/or Resolve button on the Journey Tab of a Case didn't work
• Fixed an issue where Section and Blank Spaces on Layouts were not showing on our updated Case Management screens
• Fixed an issue where the Location card in Panel 1 of a Case was blank if the Customer had more than one location associated to it
• Fixed an issue where creating a Case from the Customer Card ellipses menu > Create Case or Create Work Order didn't display the Case Events or Case Details on Panel 2 of the Case until you manually refreshed your browser

Knowledge

We fixed a bug where adding a word in between curly brackets was not showing up in the external article because it was being confused for a token.

Integrations & APIs

Fixed a bug where Notes were not being added to theh Events timeline from the Phone API. Notes can now be added for the AgentAnswer, AgentHangup, and QueueExit API calls.

Messenger SDK

Fixed a bug where the mobile SDK would sometimes hang or crash on the customer rating screen.

Virtual Assistants

• Added the new Sentiment Analysis logs to the Bots Activity Table
• We made Bots Training more consistent in terms of memory usage and time to completion by now training in batches
• Fixed an issue where Bot trainings were failing for large Bots ("Training Timed Out") due to a large load from the confusion matrix
• Fixed an issue where Bots were giving entity type errors when trying to again train the pre-trained entities
• Fixed an issue where Bots were showing the same flow name as two different options when clarifying topics in conversations