Release Date: 06/25/24: 

CX Manager

• We fixed an issue where opening a Case from the Chat Tile would sometimes display the Contact field on the Case Details screen as blank, even when a Contact was assigned to the Case. The Contact field will now always populate when opening a Case from a Chat Tile.
• We fixed an issue where a user creating a new Case using the global Create Case button from an existing Case would see the Case Details from the previous Case while selecting the Customer for the new Case. The Case panel will now be blank while going through the Create Case workflow.
• We fixed a bug where navigating from an open to a closed Case would periodically show the messages from the previous Case. Now when you access a Closed Case, no messages will show in the communications panel and the communications will be available in the Transcript files on the Case.
• We fixed an issue where users would paste a new Case link into the URL bar and press enter while currently on a different Case and the case screen would not update to the new Case. Now the user will be directed to the new Case after entering a case URL and pressing enter.
• We fixed an issue where the Events panel on a Case would periodically fail to load the events. 
• We fixed an issue where users would periodically experience inconsistent loading of Case details and communications while navigating between multiple chats via the chat tiles.
• We fixed an issue where a user seraching for a Case Ref ID in the global search bar would see 'undefined' in the search results when they navigated to the Cases tab. Users will now see the correct matching case(s) when navigating to the Cases tab on global search results.
• We fixed an error where some users on Windows using version 126.x of Chrome would experience a fatal error when opening and creating Cases inside CXME.

Knowledge

• We fixed an issue where after bulk editing Knowledge Articles, the order of the list would change, but the order of the selected Articles would remain the same. Now after you bulk edit Articles, the selected Articles will remain the same. This will make it easier to make multiple bulk edits in a row to the same Article set.
• We fixed an issue in the Article Editor where using shift + arrow keys or ctrl + shift + arrow keys was not properly highlighting text. 
• We fixed an issue in the Article Editor screen where a user was unable to press the left arrow key at the beginning of a line to go to the end of the line above it.

Settings

• We fixed an issue where after a user accessed Alert Templates in Settings and then navigated to My Profile, they ran into an error requiring a page refresh.

Releasing June 2024

We're excited to announce that our product is now fully compliant with the Web Content Accessibility Guidelines (WCAG) 2.1 at the AA level, following the guidelines set forth by the Americans with Disabilities Act (ADA). This achievement signifies our commitment to providing an inclusive and accessible experience for all users, regardless of their abilities. This work applies to the Knowledge, Reports, Settings, and Messenger products. 

What does this mean for you?

By achieving ADA WCAG 2.1 compliance, our product offers a variety of benefits for users with disabilities, including:

• Improved Color Contrast: Enhanced color contrast ensures text and graphics are clearly visible for users with low vision or color blindness.
• Enhanced Screen Reader Compatibility: Our product now seamlessly integrates with screen reader software, allowing users who are blind or visually impaired to navigate and interact with the content effectively.
• Optimized Keyboard Navigation: Full keyboard navigation allows users to access all features and functionalities without relying on a mouse. This is particularly helpful for individuals with motor impairments or who use assistive technologies.
• Clear and Concise Language: We've strived to use clear and concise language throughout the product, making it easier for users with cognitive disabilities to understand the information presented.

Benefits of ADA Compliance

Beyond its ethical importance, ADA compliance offers several advantages for your organization:

• Increased User Base: A more accessible product opens doors to a wider audience, potentially increasing your user base and customer satisfaction.
• Reduced Legal Risk:  WCAG compliance helps mitigate potential legal risks associated with accessibility lawsuits.
• Enhanced Brand Reputation:  Demonstrating a commitment to accessibility strengthens your brand image and positions you as a leader in inclusive design.

We believe that everyone deserves an equal opportunity to access and benefit from our product. This update reflects our ongoing dedication to creating a user-friendly and inclusive experience for all.

For any further questions regarding our ADA WACG 2.1 compliance, please don't hesitate to contact our support team.

We are excited to announce the addition of a new activity type in our Journeys product: API Activity.

This powerful new feature significantly enhances the functionality and flexibility of the Journey builder. Users can now seamlessly integrate external APIs into their journey flows, enabling the automation of data transfers and actions between OvationCXM and third-party systems directly from Journey Timelines. This integration ensures smoother operations, reduces manual intervention, and ultimately leads to faster and more efficient customer service.

Sample Flow:

1. Creating an API Endpoint with API Library

2. Adding the API Endpoint as API Activity on Journey Builder

3. Journey Timeline Progressing with API Activity on a Case

Key Features:

• Integration with API Library: API endpoints created from the API library are now available as activities within the Journey builder. This allows users to seamlessly incorporate API calls into their journey flows and enables them to send data from OvationCXM to any third-party system. This feature supports various business processes by automating data updates and actions without requiring agents to log into external systems.
• Configuration and Customization: Users can choose from various Cases, Customer, Contacts, and Locations data fields to map as part of the data payload sent through the API endpoints. These fields are automatically populated from the data retrieved from the Case to which these Journeys are attached for a customer.
• Automated Journey Progression: The Journey automatically progresses once the API activity is completed. This ensures a smooth and efficient workflow, enhancing the overall experience for both internal agents and customers.

Use-Case Examples:

• Automatically provision a customer account when they sign the necessary forms.
• Directly send required customer data to a KYC platform for validation.
• Keep your internal systems in sync with the latest customer information.
• Update your pipeline in Hubspot for sales team visibility when the onboarding is complete.
• Trigger an AdobeSign document to be sent to the customer as part of their sales or activation journeys.
• Trigger an email campaign on Marketo as part of your marketing outreach.
• Create and send shipping labels for a product that needs to be delivered.
• Schedule a training session via Calendly as part of your go-live activation.
• And many more..

These use cases illustrate the versatility and power of the API Activity feature, enabling seamless automation and integration across various platforms and workflows.

Benefits:

• Increased Efficiency: Agents no longer need to log into third-party systems to update data or trigger actions. API Activity handles these tasks automatically, saving time and reducing the potential for errors.
• Improved Customer Experience: By automating data transfers and actions, customers receive quicker and more accurate service, leading to higher satisfaction levels.
• Enhanced Business Value: Organizations can streamline their operations and ensure that all necessary data updates and actions are performed consistently and accurately through automated workflows.

We believe that the API Activity will significantly enhance your workflow capabilities and improve the overall efficiency of your processes. As always, we are committed to providing you with the best tools to support your business needs.

Roll Out Plan:

The following feature is part of our New Journeys Suite. We are 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.

Thank you for choosing OvationCXM!

Release Date: 05/16/2024: 

Knowledge

This release enhances the accessibility of interactive elements across the Knowledge editor, ensuring consistent and clear announcements through screen readers. All checkboxes, toggle switches, buttons, input fields, and other controls now properly announce their names, roles, values, and available actions when focused. This includes elements like the Restore button on previously published versions, checkboxes in filter menus, title/subtitle fields, embedded article options, token insertion, thumbnail navigation in File Manager, and related article controls. Proper keyboard accessibility has also been implemented for previously inaccessible components. These improvements align with WCAG 2.0 guidelines for providing programmatically determinable information, allowing users to effectively understand and interact with on-screen elements through assistive technologies. The standardized announcements create a more inclusive and seamless experience for all users.

This release further enhances the accessibility of interactive elements throughout Knowledge Home by standardizing announcements for screen readers and other assistive technologies. Clear buttons in filters now convey their associated actions. The Page field at the bottom of the list is accessible via keyboard with proper announcements. On the Templates page, the clear button in the search bar, column headers, and row actions are all properly announced. When modals open, the auto-focused close button correctly states its purpose. The buttons within modals like Clone, Archive, and Delete are accurately labeled for clear communication. These improvements ensure users can effectively perceive the available interface components and interactions through auditory cues, aligning with WCAG 2.0 guidelines around providing programmatically determinable names, roles, and values. The consistent and descriptive announcements create a more inclusive experience across all user workflows.

This release standardizes the announcements for interactive form fields throughout Knowledge Home, improving accessibility for users of screen readers and other assistive technologies. Dropdowns like Libraries, Status, Visibility, Tags, Products, and Shared With now properly announce their label, role as a collapsed or expanded listbox, current selection state, and available operations like text editing or navigating options. This consistent pattern of "Label, Role, State, Operation" ensures fields are comprehensively conveyed, allowing users to easily identify and interact with them solely through audio cues. These enhancements align with WCAG 2.0 guidelines for providing programmatically determinable name, role, and value information, creating a more inclusive and seamless experience across all user interfaces.

This release introduces significant improvements to the accessibility of the tree element across Knowledge. Previously, these interactive components did not adhere to WCAG standards for keyboard operability and screen reader announcements. With this update, the tree elements in the Details tab and the Insert Article modal when editing an article now fully comply with the recommended keyboard navigation patterns and programmatic announcements. Users can seamlessly traverse the tree structures, expand/collapse nodes, and understand the current context through clear and consistent screen reader feedback. 

This release resolves multiple accessibility issues identified across Knowledge when using the JAWS screen reader. Checkboxes throughout Knowledge are now operable via keyboard and announced correctly by JAWS. When visiting a page within Knowledge that contains a table with JAWS enabled, pressing "T" properly announces the table contents. Additionally, all main pages (Knowledge, Reports, Settings) now have an H1 header that is announced when pressing "H" with JAWS on, helping users identify their current context. Lastly, the sub-menu options accessed through the three-dot menu throughout Knowledge are fully keyboard accessible and announced accurately by JAWS. 

This release introduces significant enhancements to the accessibility of modals across the Knowledge, Settings, and Reports areas of the application. Previously, screen readers did not provide any announcements when modals were opened, limiting the ability for users relying on assistive technologies to effectively navigate these interfaces. With this update, the focus is now properly set to the first interactive element within each modal, and the modal's title is clearly announced.

We fixed an accessibility bug with the "Discard Changes" modal in the Knowledge editor. Previously, when using a screen reader, the modal's contents were announced incorrectly, with the title, description, and buttons being repeated multiple times. With this fix, the screen reader will now properly announce the modal's title and description, followed by each button's accessible name individually. This ensures users relying on assistive technologies can clearly understand the purpose of the modal and interact with its controls in a logical, streamlined manner. 

Journeys

Over the next few weeks we will be rolling out the new version of our Journeys product. This will include access to the Journey API Activity powered by the API Library as well as new backend engine with improved reliability at scale.

Messenger (Web & SDK)

We updated Messenger to be loaded from a CDN, improving the load performance of Messenger on websites and in applications. 

Reporting & Dashboards

We improved the loading performance for the reporting tables that power the Customer and Case data in our dashboards. This will ensure the dashboard data is updated on a more timely and consistent cadence.

This release addresses accessibility issues across the Reports section of the application Teams section in Settings by providing descriptive and unique labels for all interactive elements, ensuring compliance with WCAG 1.3.1 guidelines. Buttons such as "Add Team," "Search Filters," "Edit," "More Options," as well as various actions within team management modals like "Edit Team," "Add Hours," "Edit Additional Info," "Add User to Team," and "Add New User" now have clear labels that accurately convey their purpose. Additionally, the irrelevant tab label in the "Add New User" modal has been removed for clarity. These improvements create a more inclusive experience, enabling all users, including those using assistive technologies, to effectively navigate and interact with team-related settings and functionalities. The consistent labeling enhances the overall usability and comprehension of Reports interface.

Admin & Settings

We improved the performance of loading the Teams page under Settings.

This release addresses accessibility issues across the Teams section in Settings by providing descriptive and unique labels for all interactive elements, ensuring compliance with WCAG 1.3.1 guidelines. Buttons such as "Add Team," "Search Filters," "Edit," "More Options," as well as various actions within team management modals like "Edit Team," "Add Hours," "Edit Additional Info," "Add User to Team," and "Add New User" now have clear labels that accurately convey their purpose. Additionally, the irrelevant tab label in the "Add New User" modal has been removed for clarity. These improvements create a more inclusive experience, enabling all users, including those using assistive technologies, to effectively navigate and interact with team-related settings and functionalities. The consistent labeling enhances the overall usability and comprehension of the Teams interface.

This release addresses accessibility issues on the My Profile page in Settings, ensuring compliance with WCAG 1.3.1 guidelines for providing descriptive and unique labels across interactive elements. Previously, buttons such as "Edit contact info," "Switch role," "Add to team," and others lacked proper labeling, hindering users' ability to understand their purpose and relationships. Additionally, the "Back" and "Save & Exit" buttons on subsequent screens suffered from the same issue. With this update, all buttons now have clear, descriptive labels that accurately convey their functionality. The styling of the "Back" and "Save" buttons has been updated to align with the visual treatment of similar Settings options, further enhancing consistency and usability. These improvements create a more inclusive and seamless experience for all users navigating and managing their profile settings.

This release enhances the accessibility of the Knowledge settings interface by providing descriptive labels for interactive elements, addressing violations of WCAG 1.3.1 guidelines. On the main Knowledge page, the action buttons and search filters now have associated aria-labels for clear identification. When editing a Knowledge library, all buttons within that interface are properly labeled. Additionally, the "Browse" button for custom branding options has received an appropriate aria-label. These improvements ensure that all users, including those relying on assistive technologies, can effectively perceive and interact with the various Knowledge settings and configurations. The consistent labeling creates a more inclusive and comprehensible experience throughout this critical area of the application.

Release Date: 04/08/24: 

CX Manager

Cases

• We improved the performance of creating new Cases and editing existing Cases.
• This release improves the visual consistency and clarity of chip displays across various components of the Customers and Cases pages. When viewing the Details tab of a Case, the Product chips now match the green shade used on Case Cards and in Knowledge, while Tag chips adopt the familiar blue color from those pages. Other chips maintain a uniform grey styling aligned with Knowledge. Crucially, chips in view states no longer include the "X" button, reserving that functionality for edit modes. Conversely, when editing a Case, all chips retain their designated colors (green for Products, blue for Tags, grey for others) and display the "X" button for removal. This update extends to Location details within Cases, ensuring Team chips follow the same grey styling without "X" buttons in view mode. These enhancements provide a cohesive and intuitive experience when interacting with case and location information.
• We fixed a bug related to the display of Collaborating Teams and Collaborating Users chips in the Case view state. Previously, these chips incorrectly showed an "X" button, which could be confusing or misleading when not actively editing the Case. With this update, the bug has been resolved by removing the "X" button from the Collaborating Teams and Collaborating Users chips when in the Case view state, reserving its functionality for the edit state only. Additionally, a consistent grey styling has been applied to these chips, aligning with the visual treatment of other Team and User-related chips across the application. This bug fix ensures a clear and intuitive user experience when viewing Case details.
• We added "BaaS" (Banking as a Service) to our Product categories.

Communications

• We continued to improve the logic for matching inbound email, phone, and SMS cases. You can find the full matching logic in this Article.
• We fixed an issue with the saved pdf communication transcripts on resolved cases where the customer’s name was showing as ‘Boomtown’ instead of the name of the Contact. The proper name will now show on the saved transcripts.
• We improved the performance of our email inbox integrations when processing emails with large file attachments.

Knowledge

• This release enhances keyboard accessibility and operability for various input fields across the Knowledge Home and Knowledge Edit pages. The remove chip buttons for Tags, Products, Shared With entities, Labels, Restrict Team access, and Share With Organizations have been relocated outside of the input fields, ensuring compliance with WCAG 2.1.1. Users can now seamlessly navigate to and interact with these chips using keyboard controls. Additionally, the ability to remove Team, Organization, Customer Segment, Product, Tag, and Search Term chips via keyboard has been implemented. This improvement ensures all interactive elements are accessible and operable solely through keyboard navigation, providing an inclusive experience for all users.
• This release further enhances the accessibility of interactive elements throughout Knowledge Home by standardizing announcements for screen readers and other assistive technologies. Clear buttons in filters now convey their associated actions. The Page field at the bottom of the list is accessible via keyboard with proper announcements. On the Templates page, the clear button in the search bar, column headers, and row actions are all properly announced. When modals open, the auto-focused close button correctly states its purpose. The buttons within modals like Clone, Archive, and Delete are accurately labeled for clear communication. These improvements ensure users can effectively perceive the available interface components and interactions through auditory cues, aligning with WCAG 2.0 guidelines around providing programmatically determinable names, roles, and values. The consistent and descriptive announcements create a more inclusive experience across all user workflows.
• This release improves the focus order and styling of focused elements on the Knowledge Edit page for an enhanced user experience. The focus state visibility issues with the Primary buttons (Edit, Restore, Save, etc.) and the Publish button have been resolved. Users can now clearly distinguish the focused element, as the focus state is no longer obscured or cut off at the top and bottom. This fix ensures a logical focus order and consistent styling across interactive components, adhering to the Web Content Accessibility Guidelines (WCAG) 2.4.3 for better accessibility and usability.
• This release resolves a focus trap issue in the Knowledge Edit page's Related Articles section when tabbing through elements in edit state with multiple manually added articles. Previously, users could get trapped within the clear buttons, unable to navigate further via keyboard. The fix ensures seamless tabbing throughout the page, adhering to WCAG 2.0 accessibility guidelines. Key improvements include setting the next focus after clear buttons to the "Search for Articles" dropdown, and the previous focus on Shift+Tab to the "Auto Generate" switch, allowing full keyboard accessibility compliance.
• We fixed an issue where Messenger was not always showing on external knowledge sites when configured from the Knowledge Settings screen.

APIs & Connectors

APIs

We added the getBy endpoints to the Product object. This allows organizations to lookup customers from unique IDs that live on the related Products that the customer users.

Connectors

• We added a new event when a Case is deleted. This will allow 3rd party connectors (e.g. Salesforce) to map and update the Case Status field when a Case is deleted in CXMEngine. Previously, a Case would fail to show it was deleted and would require manual intervention to close it out in the 3rd party system.
• We updated our Microsoft Dynamics connector to use the getBy endpoints. This allows more flexible customer matching options when syncing data to OvationCXM from Microsoft Dynamics.

Security

We continued to improve the security of the platform against cross-site scripting (XSS).

Release Date: 03/8/24: 

CX Manager

Cases

• We fixed a bug where the Categories field on a Case was not displaying any options after a Case was set to Waiting. Now when a Case is set to Waiting, the Category field will populate with all available options when you edit the Case.
• We fixed a bug where inaccurate Location information was loading in column 1 when creating a new case. If you create a new Case and select a Location to create the Case under, that Location’s information will properly load in column 1. 
• We fixed an issue where users that had the Edit All Cases Permission were receiving an error when accessing a Case that was not related to a Team the user was on. Now when a user has the Edit All Cases Permission, they will no longer receive an error access a Case owned by a Team they are not on.

Communications

• We fixed an issue where an inbound email would periodically update the Customer Name to the From email address when the email matched to an existing email address in an Organization’s data. Inbound emails will no longer update the Customer Name for any existing customers.
• We updated our inbound email restrictions to allow emails to create Cases when they have an Auto-Submitted: Auto-Generated header included. Previously we ignored these emails from creating cases to help prevent potential spam.
• We fixed an issue where inbound emails from existing customers were not always matching to the correct Customers, Locations, and Contacts. Note that if you have more than one instance of the same email address in your Contact list, it will not automatically match to the correct customer.
• We improved the customer matching logic for inbound phone calls to more accurately match to the correct Location when the phone number on the Location matches.
• We improved the customer matching logic for inbound SMS messages to ensure that an inbound SMS message from a customer attaches to the correct Customer, Location, and Contact when the relevant data is available in an Organization's CXMEngine instance.

Knowledge

• We addressed an ADA compliance issue in Knowledge by making sure all elements have a unique descriptive label.
• We improved the ADA compliance of the Knowledge home screen and article editor by making sure all buttons are accessible and operable by keyboard. 
• We made sure that all elements on the Knowledge home page had appropriate focus state styling and that the focus order was appropriate for ADA compliance. 

Integrations & APIs

• We added new 'getBy' endpoints to all core object APIs to enable users to lookup any record by custom field data. This will add additional flexibility to the inbound customer and case matching workflows and allow organizations to use custom fields (where field type = identifier) in addition to the External ID and MID fields.

Security

• We implemented a re-scan process for files that did not successfully complete virus scans on initial load.
• We improved security related to CORS header reflection.

Release Date: February 2024

CX Manager

• We fixed a bug where creating a Case from a Customer with 80+ locations would sometimes add the Case to the wrong location. If you have a Csutomer with 80+ Locations and create a new Case for one of those Locations, it will now get added to the Location you chose. 
• We improved an issue where sometimes the Category dropdown was not working when editing a Case due to computer/network performance issues. The Category field should now be available when editing a Case even when performance is degraded. There are still a few workflows that can cause the Category field to show up blank and we are continuing to improve this.
• Previously, SMS surveys would be automatically sent when a Case was resolved and the Contact on the Case was missing an email address. Since there was no way to disable this automated SMS survey, we have disabled SMS surveys for all Cases. Surveys are still sent via email when that option is enabled.
• We fixed an issue where certain logos on email alert templates were showing as broken images rather than the actual image.

Knowledge

We added H2 tags (in addition to H1 tags) to the 'What's In This Article' quick jump component on the right side of Articles in external Knowledge sites.

Journeys

• We add added pagination on the Journey Template list view. Users can now navigate between different pages to access historic Journey Templates.
• We added dual visibility for Step names on the Journey Template Builder. Users can now see the public name of the internally assigned steps under the customer column and vice-versa. The aim is to provide a better understanding of how internal and customer-side Journeys Timeline will look once that journey is live.

AI

We are beginning to roll out our new customer summaries, powered by generative AI. These customer summaries aggregate data from every interaction you have had with a customer and provides a qualitative summary, overall sentiment, engagement level, and opportunities to improve the customer expereince. We will share more information on these summaries in the next post.

Security

• We added additional file scanning to all files uploaded to CXM Engine to identify malicious files and prevent attacks. We also blocked all javascript within PDFs to ensure they will not execute in previews.
• We improved the security of our application through an enhanced Cross-Origin Resource Sharing (CORS) policy.
• We improved the security of our application through enhanced cross-site scripting (XSS) controls.

Release Date: 01/26/24

CX Manager

Cases

• We launched Embedded Apps. You can now embed data from the third party system within CXME and access it directly from the CX Manager screen.
• We improved overall load times of the application by adding additional caching for certain library files. 
• We fixed a bug where setting Cases to Waiting with a return date and time was not adhering to daylight savings time. Now, when you set a Case to Waiting and apply a return time and date, that time and date will adhere to daylight savings time when applicable. 
• We fixed a bug where Cases were periodically returning from Waiting to Ready before they were supposed to. 
• We fixed a bug where you were able to toggle between Card and Table view while in a Group By view on the Cases page that was breaking the view. We disabled those options while in that particular view and enabled them when you actually click on a Group and a list of Cases is displayed. 
• We fixed an issue where the last activity was not showing on the right side of all Case Cards in a Case list. The Case cards will now show the latest event for the Case on the Card.
• We updated the list of Contacts in the Customer panel of the CX Manager screen to filter to the specific Location that you are viewing rather than showing all Contacts across all Locations under the Customer profile.
• We fixed a bug where the Insights on the My Work page were being displayed twice. Each Insight will only be displayed once on the My Work page.
• We fixed an issue where a chat tile would not disappear from a user’s screen when someone else on their team claimed that chat. This occured only when a user had specifically one chat tile in their chat tile list and it was claimed and the list should have gone to zero. Now when a chat is claimed by another user, the chat tile will disappear in all scenarios.
• We fixed a bug where sometimes the Categories dropdown was not working when editing a Case due to computer/network performance issues. The Categories field should now be immediately available when editing a Case even when performance is degraded. 

Customers

• We fixed a bug where you were not able to create a new Customer while on the Customers page. Now, if you are on the Customers page and click Create > Customer, you will be able to create a new Customer.
• We optimized the list of Teams available in the Team Association field on a Location to increase the security of ecosystem connections.
• We fixed a bug where the Case counts in column 1 were incorrect when you were viewing a Location from the Customers page. The Case and Open counts will now accurately reflect the total number of Cases and Open cases assigned to the Location.
  
  
  

Journeys

• We Added functionality to close out a Journey. If a customer going through the journey churns out then the Journey can be closed for the customer. It will be part of Journey Analytics to provide insights on Journey completion rates and details on where customers are most commonly churning out from the Journey. You can read the full release notes here.
• We fixed an issue where the "Complete" checkbox on Tasks was still visible on the Journey Timeline even after that Task was canceled.
• We fixed an issue where we were showing Public Name of the Journey on Timelines attached to the cases rather than Internal name. Now internal timeline will have Internal Journey Name visible.
• We fixed a bug where the Journey Timeline would sometimes load the timeline from the previous Case.

Knowledge

• We fixed an issue with the Suggestions that appear in the external Knowledge library when you return zero search results. We removed the “Suggestions” heading from the unordered list of suggestions that follows for ADA compliance. 
• We updated the Last Updated date format on external Articles from mm/dd/yyyy to Month Day, Year. 

Messenger (Web)

• We fixed an issue in Google Chrome where Messenger would periodically disconnect from the chat and future chat messages would fail to send. This occured when Chrome would disable the tab and put it in an inactive state. We added new functionality to keep the chat session alive even when the tab goes inactive so that messages continue to send after the session is reactivated. 

Tasks

• We fixed a bug that prevented users from selecting PM when adding a Task due date. You can now select AM or PM when adding a due date and time.

Salesforce Connector

• We added a toggle on the Salesforce integration to allow data to sync from all Teams across your Organization rather than being limited to a single selected Team. You can still optionally filter the connector down to specific Teams if desired.

Settings

• We removed the Auto Assign First Contact and Auto Assign Sponsor fields from Team settings.

Security

• We added additional security controls around user password encryption.
• We improved the security controls around cross-organization ecosystem Cases being created from the Phone API. Cases can no longer be created with cross-organization relationships when the Sponsor Team ID is left blank.

We are thrilled to announce the release of the 'Journey Close Out' feature, a significant enhancement to the customer Journey management capabilities. This latest update allows users to proactively manage and close out customer Journeys directly from the timeline view, addressing the dynamic needs of both the business and its customers.

Key Features of the Journey Close Out:

Close Out from Timeline View: Users can now conveniently close out a customer's Journey directly from the timeline view. This is particularly useful in scenarios where a customer has churned from a Journey or when the Journey is no longer relevant to their needs.

Journey Analytics: The feature will also be part of robust Journey Analytics, providing critical insights into the overall Journey completion rate, the churn rate of Journeys, and the potential risk factors associated with each Journey.

Enhancements to Customer Journey Timelines:

• The 'Journey Close Out' feature empowers businesses to adapt their strategies in real time, ensuring that customer engagement remains relevant, efficient, and effective.
• By identifying and addressing churned or irrelevant Journeys, companies can refocus their efforts on the most impactful customer interactions.

Adding valuable Insights for Businesses:

Journey Completion Metrics: Track the rate at which customers complete their Journeys.

Churn Rate Analysis: Identify and address the reasons behind customer drop-offs in specific Journeys.

Risk Factor Assessment: Evaluate and mitigate potential risks associated with different customer Journeys.

Roll Out Plan:

The following feature is part of our New Journeys Suite. We are 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. 

Today we are excited to announce a new feature in OvationCXM – the ability to embed an app into your customer experience platform. This new capability allows you to access sensitive data via an API without actually storing it within the platform itself.

Using this feature, you can get customer banking data, for example, without ever leaving OvationCXM. This means that you can now get the data you need to make better decisions, without compromising the security of your data. With this powerful new feature, you can quickly and easily access the data from an external API and display it alongside your case data in the solutions panel. 

Key Features

• Connect with an external API. 
• Set up your data mappings with a data grid view.
• Use your Embedded data alongside your customer and case data. 

Roll-out Plan

The Embedded Apps product is currently in beta, allowing data embedding in the cases screen in a grid view. Reach out to your account manager today to get early access. If you have any questions about how to use the feature, please don't hesitate to reach out to our support team who will be happy to help.