2 years ago8/30/2023

Updates & Bug Fixes

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.

Alan Finlay

2 years ago8/25/2023

Case Summarization (Powered by OvationCXM AI)

Today, we are proud to announce the launch of our new feature: Case Summarization (powered by OvationCXM AI). The Case Summary option will help anyone quickly get the full context of the Cases, including details from notes, conversations with customers, events timeline, resolution steps, and any fields that are filled out on the Case. If a Case is blocked/waiting, the summary will include the last conversation and a brief explanation of what’s preventing the Case from progressing.

How Summaries are Generated

This new feature is powered by our proprietary Generative AI (GenAI) architecture integrated with world-class GPT models. GenAI uses advanced algorithms to analyze all data related to a Case and summarize it in an easily understandable way. It eliminates the need for manual analysis and writing out robust notes and can significantly improve the speed and accuracy of creating Case summaries.

How you can Create a Case Summary

• To get started, log into your CXME account, go to the selected Case you want to summarize, and click the “Create Summary” button under Actions.
• Once the summary is generated, you can review, edit, and even regenerate the content to refresh the phrasing before saving it.
• Once saved, the generated summary can be accessed under a new summary block inside the details section on your Case Layout.
• The following new summary block can be added to the Cases screen from the Layout option under the settings section. Detailed article on adding Summary field here

Workflow Video of Creating a Summary on the Case Screen

Case Summarization.mov - Google Drive

Error 403 (Forbidden)!!1

403. That’s an error.

We're sorry, but you do not have access to this page. That’s all we know.

Request a review

Learn more

Signature pending

Sign

Reject

View details

Review

Not Spam

Remove forever

Not Spam

Loading…

{"id": "1Vam01c6WKFLsibaJZ5fvC2gZQgF7Wt0J", "title": "Case Summarization.mov", "mimeType": "video\/quicktime"}

Loading…

Play (k)

Play (k)

Picture-in-picture is in beta

You can still use it while work is being done. Click anywhere to open it.

Open

Playing in picture-in-picture

Closing this window will close the player

YouTube

0

Play (k)

Rewind 10 seconds (j)

Fast forward 10 seconds (l)

Unmute (m)

Subtitles/Closed captions (c)

1x

Playback speed

Settings

Full screen (f)

Loading…

Displaying Case Summarization.mov.

Why did we Build Case Summarization?

• With Case Summarization, users can quickly and accurately summarize all conversations, data, and other information related to a Case, allowing them to make decisions and take action quickly. Saving valuable time for teams so they can spend more time helping customers.
• Enable managers and other team members to understand what is happening (or what happened) on a Case, including what the issue/question was, what was done to resolve the issue, what’s blocking the Case from progressing (if anything), and what the final outcome was (if it was complete). This significantly reduces the time users spend digging into engagements to understand what happened.
• Case summaries also make finding common patterns for improvement easier with reporting on the summaries.

How to Get Access to the Case Summarization Feature

We understand that this can save a significant amount of time for businesses, and we are confident that this new feature will help you make the most of your data and conversations.

We will be rolling out the Create Summary on Cases option in phases, and if you would like to get early access, please let us know by emailing at product@ovationcxm.com. We hope you enjoy this new feature and look forward to hearing your feedback!

Vaibhav Gupta

2 years ago8/17/2023

Journeys Launch

We are excited to announce the launch of our new Journeys Product!

Journeys help you connect disparate interactions across teams and organizations and orchestrate them into unified experiences to delight your customers.

OvationCXM’s new Journeys product includes several significant enhancements over our current Journey product that make it easy to use and adds powerful functionality to optimize customer experiences. We’ve detailed the specifics of these enhancements in the following video releases showcasing Journeys:

1. 2 minute overview
2. 20 minute walk through

In addition to a new architecture built for performance, reliability, and scale, it has a number of major upgrades to help you orchestrate customer journeys. Here are a few of the updates:

New Drag-and-Drop Journey Builder

We’ve transformed our Journeys module so it’s a simple no-code drag-and-drop interface that anyone in the organization can use to orchestrate customer experiences. All of the pieces of a well-orchestrated Journey, from communications to automations to tasks, are included in this single tool. No complex configuration, custom code,  or developers needed to build a Journey. If you can envision the experience, you can build it. And in just a few minutes with a few clicks.

New Organizational Hierarchy

Our new Journeys product has expanded its hierarchy from stages, which provided a high-level view, to a three-tier hierarchy that gives you additional levels of organization, visibility, and control.

1. Stages - Major sections or milestones in a Journey that shows high-level progress toward completion.
2. Steps (New) - A way to organize groups of activities into a single bucket, typically owned by a single team.
3. Activities (New) - The atomic unit of a Journey. These are the parts of a Journey that are completed to progress the Journey. For launch, we will have Automations and Tasks.

Automations - Automated workflows that are triggered as the Journey progresses. These automations can send emails, update data fields, create Cases, and more across the organization and ecosystem partners.

Tasks - To-do actions that can be assigned to Teams and/or Users. Tasks need to be manually completed by the assignee to progress the Journey.

We will be adding Forms and API activities shortly which will trigger journey progression and further streamline and automate Journey flows.

Separate Side-by-side Customer and Internal Work Streams

Our new Journey Builder allows you to create unified journey experiences that seamlessly weave between internal and customer-facing actions while having complete control over visibility and driving toward a shared outcome.

You can define Public and Internal names for every Stage and Step so even if your internal team is completing an action, you can give your customers insight (in language that makes sense to them) into what’s happening behind the scenes.

A major part of a journey is bringing the customer along for the ride. Giving them visibility into what is happening, what’s next, and setting expectations for when the next step may be completed. This reduces inbound call volume and increases customer satisfaction.

Drafts and Publishing Workflows

Journeys will now offer the ability to create drafts and iterate on your journeys without disrupting any journeys currently in progress.

This solves one of the big challenges we see with journey mapping and orchestration today. Typically, it’s often a one-time exercise that remains static for years once developers implement it because it’s hard coded and hard to change. Set it and forget it. This is a failing strategy because processes and customer expectations are constantly changing and your journeys need to keep up. Organizations must have agile tools that empower responsiveness to competitive pressures, market changes, and customer needs in real-time

Journeys can be tweaked and optimized easily at any time without impacting existing customers already traversing active journeys. Users create and edit journey drafts, and once they are published, new customers can enter those journeys. Even as new revisions are published, Previously Published revisions are retained for a complete audit trail of every journey that has been published. You can clone, revert, and publish any revision at any time without disrupting any active customer journeys, providing the control to adjust and improve journeys over time.

Our Journey Analytics also presents data across each revision so you can track progress, friction points, and areas for improvement over time. Stay tuned for a separate, more in-depth post on Journey Analytics.

New Interactive Journey Timeline

To match the new Journey hierarchy, we are also launching a new Journey Timeline in the second column on the Cases screen.

The Journey Timeline will make it more efficient to manage journeys while in the Cases screen:

1. The new timeline will visually display the Stage, Step and Activity hierarchy.
2. The timeline is interactive and Tasks can be completed inside the timeline.
3. Activity Actions allow you to Cancel Tasks or Automations (current or future) that you don’t want to complete (we will also be adding the ability to complete, skip, or replay activities as well).
4. New icons provide additional visibility into what’s in progress, if any actions have been canceled, and if any automations failed to run.

We will be rolling out the new Journeys product in waves and if you would like to get early access, please let us know by emailing product@ovationcxm.com. We can’t wait to help you build more delightful customer experiences and to hear your feedback on how we can improve the product for you.

Alan Finlay

2 years ago8/2/2023

Updates & Bug Fixes

Release Date: 08/08/23

CX Manager

• Reduced the load time for the Customer panel in the 4-panel CX Management view (note that we will be rolling this out separate from the release).
• Fixed an issue where the counts next to each section on the My Work screen were sometimes inaccurate.
• Fixed a bug where clicking between closed and open Cases in the Customer panel (column 1) would make the Edit button disappear in the Case panel (column 2).
• Fixed a bug where clicking on a Case in the My Work page would cause a brief redirect to the Cases page before taking you to the actual Case.
• Fixed a bug where if you enabled the Resolve Case switch and set the Resolution Status to anything but Not Set, then disabled the Resolve Case switch, and saved the Case, it would still resolve the Case. Now enabling, then disabling that switch will not resolve the Case.
• Fixed a bug where the default option for Resolution Status was Not Set instead of Completed when you enable the Resolve Case switch when editing a Case.
• Fixed a bug where the Events tab in a Case was blank after initially creating a Case in the platform.
• Fixed a bug where a user was being taken back to a previous Case whenever they searched for a Location and then accessed a Case from that Location.
• Fixed a bug where moving a Location from one Customer to a different Customer sometimes failed to remove the Location from the original Customer.

Knowledge

• We improved the UI of the Insert Article modal when editing an Article in Knowledge. You will now be able to navigate through your libraries to find specific Articles using the same tree navigation you use for Labels. You will still be able to search for Label Names, Titles, & Sub-titles and corresponding results will be highlighted.
• We made updates to the Article Information panel and tabs in the knowledge editor for ADA compliance. The button to collapse/expand the panel and each of the tab options are now focusable with accessible names and are reachable and operable by a keyboard.
• We made updates to the Details tab of an Article when in a view state to be ADA compliant. Tab indexes have been removed, static content is no longer reachable by keyboard, interactive content is reachable and operable by keyboard, and all buttons have accessible names, focus states, and correct structures.
• We updated the Article Editor for ADA compliance by providing a title for the page, improving the responsiveness of the page, improving the header structure by making the Title of the Article an H1, and adding a skip link to the header that allows users to go directly to the content of the Article.
• We updated the Events tab in an Article to be ADA compliant. All of the tab orders are now correct, static items are no longer listed as buttons, buttons and dropdowns are now accessible and operable by keyboard, and the log itself is in a list structure.
• We updated the top bar buttons when in the edit state of an Article for ADA compliance. All buttons have accessible names and are reachable and operable by a keyboard.
• We updated the top bar buttons when in the view state of an Article for ADA compliance. All buttons have accessible names and are reachable and operable by a keyboard.

Alan Finlay

3 years ago6/30/2023

Updates & Bug Fixes

Release Date: 07/13/23:

CX Manager

Navigation

• Updated the main navigation dropdown menu for small screens so that if you are in a specific section and you click on that section again, it brings you back to the main list. For example, if you are on a Case and click Cases from the navigation, it will return you to the Cases list.
• We fixed an issue where the text was being cut off in the main navigation dropdown menu.

Cases

• We fixed a bug where the Files tab was periodically disappearing from the Case panel in the CX Manager if a user pressed Cancel or Edit directly after uploading a file.
• We fixed an issue where the navigation text was being cut off in the main navigation dropdown menu on small screens.
• We updated colors in several areas of the application to be ADA compliant.

Automations

• We updated the filter options on Case Automations to include the Case Name field.

Knowledge

• We improved the behavior of adding or changing a Label icon in Knowledge. You will no longer have to click Browse and Upload. When you click on the Add Icon or Change Icon button, you will be able to select a new image from your computer and it will automatically upload (you will still need to click the Save button in the modal to implement the icon change).
• We added a modal that appears when the Session Timeout Warning modal reaches 0 that informs the user they have been logged out.
• We made the Sort button in Knowledge Home ADA compliant by improving the way screen readers announce each option and the way the list is sorted.
• We made updates to the Knowledge home page for ADA compliance. Both the filters and recent comments panels are now collapsible and expandable. They will auto-collapse on smaller screens. We also made the header options more responsive by combining them into a menu when the screen size gets too small.
• We updated the Comments in the To Do tab to be ADA compliant. All buttons have accessible names and are reachable and operable by keyboard.
• We updated the Labels section in Knowledge Home for ADA compliance. All expandable/collapsible elements now have accessible names, button roles, and announcements when they are expanded or collapsed.
• When editing a Label in Knowledge, we changed the naming of Label Avatars to Label Icons. This is a more accurate naming convention for this particular concept.
• We fixed a bug where resolving a Comment in Knowledge was updating the Comment log and not creating a separate log. When you resolve a Comment, there will now be a Comment Resolved log in the Events tab.
• We fixed a bug where Users were sometimes getting a TypeError when using the Insert Image or Insert Link options in the Knowledge Editor.

Journey Orchestration

With this release, we will begin to roll out our new Journeys product to select customers. We will share a separate post dedicated to the new Journeys product and all the new functionality that will come with it. If you would like early access to the new Journeys product, please let us know.

APIs & Webhooks

We added functionality to allow a user to create webhooks on the Customer Contact object.

Reporting & Dashboards

We are adding detailed Journey Analytics to our dashboards. These analytics will display data from the new Journeys product and we will share more detail on the capabilities and insights they will provide in an upcoming post.

Alan Finlay

3 years ago6/1/2023

Updates & Bug Fixes

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.

Alan Finlay

3 years ago5/31/2023

Deprecation Notice: Connect Application on iOS, Android, Poynt, Clover

As OvationCXM grows and evolves, we have shifted our mobile focus from generally available support applications to more flexible, configurable, and developer-friendly mobile support SDKs to provide you with the ability to design and implement the exact customer experience you want to deliver on mobile.

With this in mind, we have decided to deprecate our Connect mobile applications on iOS, Android, Poynt, and Clover.

Effective June 30, 2023, the mobile applications will be removed from the Apple App Store, Google Play Store, Poynt Marketplace, and Clover Marketplace. The application will continue to function until September 30, 2023, at which point it will be shut down.

To facilitate a smooth transition, we recommend taking the following actions:

1. Remove References to Connect: Identify all references to downloading the Connect application on your website and documentation and remove these references.
2. Migrate to Mobile SDKs: If you still use the Connect application to support your customers, you can use our mobile SDK to create more integrated and customized experiences for your customers on iOS, Android, or Cordova. If you are interested in our SDK for Clover, please contact us.
3. Reach out for assistance: If you encounter any challenges during the migration process or have questions regarding our SDKs, our support team is ready to assist you. Feel free to contact us through our support channels, and we will be glad to help you.

We understand that these changes may require some effort on your part, but we believe they will contribute to a more robust and streamlined experience within OvationCXM. By deprecating these mobile applications, we can focus our resources on enhancing other areas of our product to better serve your needs.

Thank you for your understanding and cooperation as we continue to improve OvationCXM. We are confident that the updated mobile experiences will provide you with a more efficient and secure platform. If you have any questions or concerns, please don't hesitate to contact us.

Alan Finlay

3 years ago5/31/2023

OvationCXM API V3 for Service Provider Organizations

We are excited to announce the latest update to our V3 API suite. This update will allow the service providers orgs to utilize a subset of API endpoints on behalf of one or many standard organizations in their ecosystem. This feature enhances the flexibility and functionality of OvationCXM, enabling service providers to interact with customer data efficiently. Please read below for more details on this update.

The OvationCXM API has been enhanced to provide a subset of endpoints for service provider organizations. While the API was initially designed for standard organizations to interact with their data, this new functionality allows service providers to perform certain actions on behalf of a standard organization.

To take advantage of this use case, the following conditions must be met:

1. The standard organization, on whose behalf the service provider is acting, must be the rightful owner of the customer data being accessed.
2. An ecosystem relationship between the service provider organization and the standard organization must be defined within CXMEngine.

New HTTP Header: X-Boomtown-OBO

To utilize the subset API endpoints, service provider organizations are required to include an additional HTTP header in their API calls. The header, X-Boomtown-OBO, should contain the unique ID of the standard organization on whose behalf the API calls are being made. This ensures proper authorization and linkage between the service provider and the associated standard organization.

Please note that the availability of specific endpoints and their functionalities may vary based on the subset API access granted to service provider organizations.

We believe that this feature enhancement will greatly benefit service providers by enabling them to offer more comprehensive and efficient services to their customers. It strengthens the collaboration between service providers and standard organizations, fostering a seamless customer experience.

For more information on how to implement and utilize the subset API access for service providers, please refer to the updated API documentation and guidelines provided by OvationCXM.

If you have any questions or require further assistance, please don't hesitate to reach out to our support team.

Best regards,

The OvationCXM Team

Prayas Tiwari

3 years ago5/26/2023

Deprecation Notice: Transitioning from API v2 Suite in OvationCXM

As part of our commitment to delivering a secure and efficient platform, we constantly review and update our offerings. With this in mind, we have decided to deprecate the v2 APIs within the OvationCXM platform.

Effective September 1, 2023, API v2 will be deprecated. Please note that once these APIs are deprecated, we will no longer provide technical support or further updates for them. If you are not using any of the v2 APIs, you can safely ignore this message. Otherwise, updating your integrations and applications to leverage the latest API versions available within OvationCXM is essential.

To facilitate a smooth transition, we recommend taking the following actions:

1. Update your integrations: Identify all instances where the deprecated APIs are being used and update them to utilize the recommended alternatives. Our documentation and developer resources will be updated to guide you through this process.
2. Test and validate: After making the necessary changes, thoroughly test and validate your integrations and applications to ensure they function as expected with the new APIs. This step is crucial to maintain seamless operation and avoid any disruptions to your workflows.
3. Reach out for assistance: If you encounter any challenges during the migration process or have questions regarding the updated APIs, our support team is ready to assist you. Feel free to contact us through our support channels, and we will be glad to help you.

We understand that these changes may require some effort on your part, but we believe they will contribute to a more robust and streamlined experience within OvationCXM. By deprecating these APIs, we can focus our resources on enhancing other areas of our product to better serve your needs.

Thank you for your understanding and cooperation as we continue to improve OvationCXM. We are confident that the updated APIs will provide you with a more efficient and secure platform. If you have any questions or concerns, please don't hesitate to contact us.

Prayas Tiwari

3 years ago5/19/2023

Training Flow for Unhandled Phrases on Virtual Assistants

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:

Screenshare - 2023-05-19 1_58_33 PM.mp4 - Google Drive

Error 403 (Forbidden)!!1

403. That’s an error.

We're sorry, but you do not have access to this page. That’s all we know.

Request a review

Learn more

Signature pending

Sign

Reject

View details

Review

Not Spam

Remove forever

Not Spam

Loading…

{"id": "1OaC0ap59r5QNJJcDApbQ1bhyJVQGd37W", "title": "Screenshare - 2023-05-19 1_58_33 PM.mp4", "mimeType": "video\/mp4"}

Loading…

Play (k)

Play (k)

Picture-in-picture is in beta

You can still use it while work is being done. Click anywhere to open it.

Open

Playing in picture-in-picture

Closing this window will close the player

YouTube

0

Play (k)

Rewind 10 seconds (j)

Fast forward 10 seconds (l)

Unmute (m)

Subtitles/Closed captions (c)

1x

Playback speed

Settings

Full screen (f)

Loading…

Displaying Screenshare - 2023-05-19 1_58_33 PM.mp4.

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.

Vaibhav Gupta

3 years ago5/17/2023

Deprecation Notice: Upcoming Changes to OvationCXM APIs

As part of our commitment to delivering a secure and efficient platform, we constantly review and update our offerings. With this in mind, we have decided to deprecate certain APIs within the OvationCXM platform.

Effective from September 1, 2023, the following APIs will be deprecated:

1. /api/v3/customers/password_reset
2. /api/v3/customers/users/sso/{user_id}
3. /api/v3/customers/sms_invite
4. /api/v3/org/users/sso/{user_id}
5. /api/v3/reports/technicians
6. /api/v3/reports/org
7. /api/v3/reports/kpi_issues_by_geography
8. /api/v3/reports/kpi_average_time_to_scheduled
9. /api/v3/reports/kpi_parner_owned_issues
10. /api/v3/reports/kpi_time_onsite_by_location
11. /api/v3/reports/kpi_issues_by_location
12. /api/v3/reports/kpi_active_support_minutes
13. /api/v3/reports/kpi_issues_time_to_completion
14. /api/v3/reports/kpi_issues_remote_vs_onsite
15. /api/v3/reports/kpi_issues_by_category
16. /api/v3/reports/kpi_issues_over_time
17. /api/v3/reports/kpi_open_issues
18. /api/v3/reports/kpi_issues_by_age

Please note that once these APIs are deprecated, we will no longer provide technical support or further updates for them. If you are not using any of the above-mentioned APIs, you can safely ignore this message. Otherwise, it is essential to update your integrations and applications to leverage the latest versions and functionalities available within OvationCXM.

To facilitate a smooth transition, we recommend taking the following actions:

Thank you for your understanding and cooperation as we continue to improve OvationCXM. We are confident that the updated APIs will provide you with a more efficient and secure platform. If you have any questions or concerns, please don't hesitate to reach out to us.

Prayas Tiwari

3 years ago5/8/2023

Thinkrelay.com Domain Deprecation - September 1, 2023

[Action Required for users of api.thinkrelay.com]

OvationCXM is in the process of sunsetting the thinkrelay.com domain in conjunction with our move to Google Cloud Platform and as required under trademark law. The final outstanding reference to the thinkrelay.com domain is the use of api.thinkrelay.com. If you are not using api.thinkrelay.com you can safely ignore this message.

If you are actively using api.thinkrelay.com, we ask that you please update any api.thinkrelay.com references to api.goboomtown.com as soon as possible.

A few years ago we implemented forwarding so that calls to api.thinkrelay.com automatically route to api.goboomtown.com, so the change is minimal. We have everything configured so it will be a simple find-and-replace exercise to update the references. Firewall rules will still work without any updates because the IP address is the same. We would be happy to schedule a call with you to assist with the update.

We are targeting a full shutdown of the api.thinkrelay.com hostname on September 1, 2023.

If you have any questions or concerns, please contact your account manager or email us at product@ovationcxm.com.

Alan Finlay

3 years ago5/4/2023

Updates & Bug Fixes

Release Date: 05/18/23

CX Manager

Cases

• Updated the Daily Digest email content to be more useful and scannable
• Made several performance improvements related to setting Cases to Waiting and the corresponding events that display in the Case Event timeline
• Fixed a bug where an Event was missing on the Event timeline whenever a Case changed from Waiting to Ready
• Fix a bug where setting a Case to Waiting for a specific time duration did not always return that Case to Ready after the time was reached

Automations

• Fixed a bug in the Automation Engine where emails were not being sent to the specified emails in the "Send to Others" field on the Send Email action

Navigation

• Fixed an issue where the text in the main navigation selector dropdown on small screens was being cut off

Knowledge

We made several updates to the internal and external facing screens, focusing on ADA compliance.

• Accordions in an Article are now accessible and operable using your keyboard to comply with ADA regulations
• We updated the color and styling of the Chat Case Tiles to adhere to our new color scheme and for ADA compliance
• We updated the color and styling of the Phone Case Tile to adhere to our new color scheme and for ADA compliance
• We updated the colors of tags, chips, and badges to comply with ADA regulations
• We removed the duplicate search field from the bottom pagination bar on Article lists
• The search button on the External Knowledge home page is now right-aligned and focused after the input field in order to comply with ADA regulations
• We have added an ADA-compliant skip link to the header of External Knowledge Libraries that allows keyboard users to jump straight to the main content
• We made links that open in new tabs in Articles viewed in the External Knowledge Library ADA-compliant by adding an aria-label that announces the visible text in the link as well as "opens in a new window"
• We removed the announcement of the line separating the header from the rest of the page in the External Knowledge Library to comply with ADA regulations
• We removed the logo and search buttons in the header of the external library from being announced as a list to comply with ADA regulations
• We updated the banners pinned to the bottom of Articles when you were viewing an Internal Article or previewing a Draft in the External Knowledge Library. There are now alerts above the title of the Article that are ADA compliant.
• We updated the Logo in the External Knowledge Library header to be ADA compliant by addressing its structure and the way it is announced by screen readers
• We updated the structure of Article links when viewing a Label page in the External Knowledge Library to be ADA-compliant by removing the sub-title from the link text
• We updated the structure of subtitles and timestamps when viewing an Article in the External Knowledge Library to make them ADA-compliant by removing their heading designations
• We updated the way Sub-labels are announced when viewing a Label page in the External Knowledge Library to be ADA-compliant by only announcing them as a list when there are more than 1 displayed on the page
• We fixed a bug where Tags displayed on Article cards in Knowledge Home looked like they were clickable

Integrations & APIs

APIs

• Fixed a bug where the APIv3 Move Locations endpoint was not moving the custom fields for the location and contacts object.

Admin & Settings

• Fixed a bug where users we unable to add more than 32 teams to a Tag. Users can now add up to 50 teams.
• Fixed a bug where only default fields and ecosystem custom fields were showing in the Layout previews in Settings. Non-ecosystem custom fields will now also appear.

Alan Finlay

3 years ago4/14/2023

Sentiment Analysis on Virtual Assistants

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.

Vaibhav Gupta

3 years ago4/7/2023

Updates & Bug Fixes

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.

Alan Finlay

3 years ago3/14/2023

Updates & Bug Fixes

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

Alan Finlay

3 years ago2/23/2023

Updates & Bug Fixes

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.

Alan Finlay

3 years ago1/26/2023

Updates & Bug Fixes

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

Alan Finlay

3 years ago1/10/2023

Launch of the New Article Editor

We have made a bunch of new and exciting updates to the way you edit an Article in Knowledge. We not only streamlined the user interface but also introduced some new features that improve the overall experience and workflow.

New Features & User Experience Enhancements

View State

You are no longer taken to the Edit State of a Draft when you click on one from the main Knowledge view. Similar to clicking on a Published Article Card, you will now be taken to the View State of the Draft. We also unified certain actions available so you can perform them whether in View or Edit State, depending on permissions. (e.g. Publish, Unpublish, Discard Draft, Comment, etc.)

Versions

We reworked the concept of Revisions. The Revisions picklist is now visible in the View State and will allow you to select what we are now calling Versions: Published, Draft, or Previously Published (formerly known as Revision). This will allow you to review different Versions individually and take appropriate action. When you unpublish a Published version, it will now convert to a Previously Published version. This not only gives you an audit trail but allows you to review the Previously Published version if you need to copy content from it. The timestamp for Draft versions is the last time the Save button was clicked. We moved the timestamp to the version picklist so you can quickly see when things were updated. The timestamp for Published and Previously Published versions is the date/time they were published.

Article Information Panel

We combined the 2 panels into 1 collapsable and resizable panel to give you more room for updating the content of the Draft. We also reorganized the Details tab and removed the individual Change/Done functionality for all of the fields in it. You can now update any of the fields directly without having to click Change first, then simply click the Save button.

To Do Tab

We created a To Do tab for adding and resolving comments and for future improvements and features such as Article Approvals.

Events Tab

We moved the Stats to the top of the Events tab and introduced a Load More Events button at the bottom. 15 event logs will load by default and 15 (or less depending upon the total number of event logs) will load every time you click it. We also cleaned up the logs themselves by getting rid of duplicate logs, removing extraneous information, and updated the verbiage to match the interface (e.g. Teams are listed by their actual name instead of their ID).

Labels

We updated the way you add Labels to an Article by mimicking the way Labels are displayed in the main Knowledge view. You can now search or simply click through the same style tree and check the boxes next to the Labels you want to add to the Article. This makes it easier to find the label you are looking for, especially if you have multiple sub-labels with the same or similar names.

Search Terms

Keywords are now known as Search Terms. Adding Search Terms will now behave more like adding Tags or Products. A removable badge will be added for every Search Term you enter. You can also add phrases for exact specific searches to improve search results.

Main Action Buttons

View State

Edit State

We moved the main buttons from the bottom right to the top bar with the Version picklist. This brings the most frequent actions you perform front and center of the editor. We broke out Publish into its own button to make the publishing process easier and faster. We also introduced a 3-Dot Menu for less frequent actions and to introduce more functionality in the future.

Cancel Button

We updated the behavior of the Cancel button. When you click Edit on a Published version that has no Draft, a new Draft gets created based on the Published version. If you don’t make any changes or click Save, clicking Cancel will discard the Draft for you and take you back to the View State of the Published version. If you do make any changes to a Draft and don’t click Save, you will receive a popup asking if you want to save your changes.

Discard Draft

You will now be presented with a confirmation popup when you click on Discard Draft to avoid accidentally deleting something you shouldn’t have.

Refresh or Close Tab/Window

If you refresh your page or attempt to close the tab/window you are working on while you have unsaved changes, you will be prompted by your browser.

Code View Saving

You can now Save any changes you make while in Code View without having to switch back to the standard view first.

File Manager

We added an option to the toolbar while you are editing an Article called File Manager. This will allow you to upload files you wish to reuse in multiple Articles throughout your entire library. Clicking on the thumbnail will insert the file into the article you are editing. Clicking the Replace icon will allow you to swap out the file and it will automatically update any Articles using the file without changing the Article status. Clicking the Delete icon will allow you to remove the file just from the File Manager itself or remove it from any Articles it is in.

Create Article Modal

We updated the way new Articles are created. When you click on Create > Article, you are now presented with a modal where you can enter the Title of your Article, select the Library it will be nested under, and optionally choose a Template. This streamlines the creation process and ensures Articles are also created in the Library they belong to.

Export to PDF

We added an option in the Three-dot Menu to export Articles to a PDF version whether you are in the View or Edit State.

If you are interested in using the new knowledge editor, email product@ovationcxm.com.

John States

3 years ago12/22/2022

Updates & Bug Fixes

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

Alan Finlay