We’ll get onto the C4C integration shortly but before I do, let’s quickly cover off some of the key features of Transversal Prescience.
First and foremost, Prescience leverages patented machine intelligence based on multi-layered Bayesian algorithms to interpret the intent of questions, answer them automatically, and learn from interactions. This means that a Prescience user, whether they be a contact centre agent, web self-service user or employee, can ask natural language questions and have the most likely “right” answers returned to them automatically.
Furthermore, the user’s next likely questions can be anticipated and presented to them. Prescience automatically predicts what users are likely to ask next, mimicking their “train of thought”. This capability requires zero administration since it is generated automatically and dynamically by the system. Ultimately this minimises a user’s research effort. It is also able to provide users with a prioritised list of suggested questions as they type even where the exact words do not match the content of the knowledge base, further reducing the effort required to get to the answer they need. Prescience is able to apply its conceptual understanding to analyse incoming, real-time data streams, such as email correspondence and social media feeds to anticipate emerging trends, enabling administrators to pre-empt issues requiring attention.
Finally, Prescience performance improves over time. Content is optimised by self-learning algorithms as the content is maintained. Throughout an interaction, user ratings and feedback can be captured and used to enhance the next interaction. Prescience provides insight into the effectiveness of the content, for example, search accuracy and knowledge gaps enabling administrators to ensure it always fit-for-purpose.
Transversal integration for SAP C4C
So, how does Prescience integrate into an SAP C4C environment? As a use case let’s consider the integration of the following Transversal Prescience functionality into the SAP C4C Ticket using the Prescience API:
- Contextual Knowledge – Knowledge base content is populated based on the Agent field selection, surfacing knowledge where and when it is required through the user journey.
- Predictions – As the Agent types a description, Prescience anticipates their question, triggering an automated search against the specified Ticket enquiry type/sub-type.
- Article Type Filter – The Agent can sort search results list by article type.
- Notifications (Announcements) – Knowledge managers can publish alert notifications which are conceptually mapped to ticket enquiry type/sub-types.
- Popular Articles – Knowledge base content is ordered by popularity, providing the Agent with an ordered list of articles by Ticket usage, enhancing the findability of contextually relevant articles required to resolve Tickets.
- Recently Updated Articles – The Agent can see those articles that have been recently updated, filtered against the enquiry type/sub-type.
- Smart Links (Relevant Articles) – Conceptually related articles are automatically and dynamically displayed beneath the article being viewed by the Agent, without any requirement for manual linking
- Guided Assistance (Decision Trees) – Decision trees provide Agents with the ability to diagnose and resolve Tickets through intuitive step-by-step processes supported by additional guidance.
To support this even further, we’ve also enabled the following functionality
- Add to Ticket – The Agent can add the article copy or URL to a Ticket.
- Email Article – The Agent can send the article copy to the customer via email.
- Agent Feedback – The Agent can provide article specific feedback via thumbs up/down together with pre-defined reasons using quick tags or free text.
- Agent Favourites – The Agent can add articles to a list of favourites.
- Quick Links – Knowledge managers can publish links to articles/webpages/resources.
- Agent History – The Agent can navigate quickly to articles previously viewed.
- Knowledge Creation from Ticket – The Agent can request an article is created when saving a Ticket. Key Ticket information, including ticket ID, category/sub-category and notes are captured on submit then passed into a queue owned by knowledge managers.
Here are a some screenshots that show the look and feel and capability of our Transversal integration for SAP C4C.
Transversal versus MindTouch
In my opinion, Transversal’s key strengths lies in its focus on delivering contextual knowledge when and where it is needed, without many of the administrative overheads associated with alternative approaches. Transversal’s common knowledge repository can provide different answers for contact centre and web self-service users according to your needs. Additionally, the product has powerful knowledge administration functionality (Knowledge Feedback, Knowledge Admin and Knowledge Insight). Transversal already has strong capability and an established user base in contact centre, web self-service and HR with many customers using it for more than one of those scenarios.
MindTouch by contrast is focused on content management and product documentation and this is perhaps reflected by the fact that 70% of their customers are in the technology sector. MindTouch is predominantly used in web self-service although the integration into SAP C4C suggests ambitions across multiple interaction channels.
Ultimately, I believe that Transversal’s cognitive knowledge capabilities of understanding, anticipation and improvement put it some way ahead of the competition.
If you are a side by side comparison type of person, then check out Forrester’s excellent, “Vendor Landscape: Knowledge Management For Customer Engagement”.