Mamba ‘22: Set a New Support Benchmark with Real AI & Step Into the Proactive Era

a. KCS Support Console

A brand-new KCS Dashboard is now part of the application. It will provide everything you need to oversee and regulate your KCS initiative.

1. Simplified configuration: Setting up the app has become quicker. There’s just a three-step process that will deploy it on all your preferred search clients.

2. Evaluate KCS adoption: It now gets a dedicated space to help you see the impact of your efforts and how well KCS is incorporated into your workflow. There are four reports.

   • Overview: It shows the status of all KCS-generated articles, both published and unpublished (draft).
   • Support Effectiveness: It helps KCS practitioners see how effective KCS is proving to be in closing tickets. It gives the ratio of cases where KCS played a role (KCS-generated articles shared or attached to cases) to total cases solved.
   • Contributor Analytics: See which support mavens have been your KB MVPs. It reveals the number of articles they authored and how many times they were shared or linked to support tickets.

   • Low Impact KB Articles: Identify the KB articles that failed to leave their mark so that the managers can review them and share feedback with the respective agent, if necessary.

     

3. Extend your KCS efforts to Zendesk: The goodness of KCS Support Console has found its way to Zendesk.

b. Chatbot

The much-acclaimed chatbot has also received quite a few upgrades under the hood.

1. Analytics Dashboard: This space aims to help evaluate your chatbot’s performance. It offers insight into:

   • Overview: It outlines four things: Total Sessions, Total Conversations, Successful Conversations, and Coverage. Total sessions include all the search sessions where chatbot was engaged. On the other hand, Total Conversations are all interactions the chatbot had.
   • Successful Conversations: The primary objective of a support chatbot is to deflect tickets, right? So, when the chatbot deflects, the conversation is successful. But what is considered deflection? Well, you, the admin, can define that. There are nine criteria for your perusal.
   • Coverage: It reveals how many interactions were covered (bot successfully found intent & story). In simple words, it’s the ratio of Successful to Total Conversations. This way, it helps admins ensure their bot can effortlessly deal with all known intents.
   • Chat Transcript: Get a closer look at all the user sessions where the bot was leveraged. It displays everything about the said sessions such as intents used, last activity, coverage, user feedback, etc.

   • Intents: It provides insight into the most used intents and the most triggered utterances within an intent.

     

2. Embedded feedback mechanism: What’s the best time to ask for feedback on a chatbot conversation? Right after it ends! To that end, you now have an option to solicit feedback from the customers right after they have interacted with your chatbot. All the feedback is neatly compiled in the app along with the stories triggered, customer’s yay or nay, and description for the same.

3. Try it before you implement it: Now feel free to tinker around the chatbot with a virtual beta. You can safely preview how your reworked stories will perform in the real world. If everything checks out, you can re-train the chatbot and then push it to the live environment.

c. Escalation Predictor

Time to bid adieu to unexpected escalations! Let’s take a look at all the interesting new bits added to the Escalation Predictor.

1. Access escalation data within Salesforce: Seamlessly synchronize the data from Escalation Predictor to your Salesforce org. This way, your support managers can swiftly identify cases that need immediate attention and prevent escalations.

2. Acknowledge or overrule predictions: There can be instances where the admin feels the prediction is a false alarm. Either way, the admin can mark it as a good or bad prediction. Accordingly, the ML-based algorithm will be retrained.

d. Agent Helper

Sometimes, your service reps come across an issue that they’re unable to decipher. That’s where they need all the help they can get. And here’s how they can get it.

1. Fuel Intelligent Swarming: A Slack integration within the app infrastructure allows the agent to instantly create a channel for the issue. It will include the top SMEs and agents for the given category of issue. This way, the best minds get together to resolve it. As a by-product, the agent who was assigned the ticket also learns and evolves.

   

a. Searches with No Results captures follow-up action

This report has long played a key role in content gap analysis. Now, a field called Action Taken has been added that helps managers save the action they took to bridge the gap. This way, it simplifies reporting.

b. Solicit feedback on content & search

We already had the provision to collect feedback on content. With Mamba ‘22, we’re taking it a step further. Now, once a user upvotes or downvotes a page, they can also describe what they feel via text. Similarly, the user can share feedback on every search result as well. And there you have it: quantified search experience. Sweet, right?

a. Define the relationship of search queries

Admins can choose how they want to treat search queries by setting the default search operator as AND or OR. Let’s say I run a query “artificial intelligence.”

If the default operator is OR, the results will include content with the keywords “artificial”, “intelligence,” or both. But if the operator was AND, my results would be limited to pieces with exact matches of “artificial intelligence.” AND brings a broader stream of results whereas OR helps with specific searches and keeps confusion at bay.

b. Learn facet preferences

Help your end-users quickly find what they’re looking for. Admins can enable machine learning for facet selection. As a result, a customer who always selects “smartphone” and “system updates” will start finding these selections already made.

c. Pin your most used search client

Admins no longer need to select a search client every time they log into the console. Just pin the frequently used search client and the instance will always have that selection in place in various menus.

d. Declutter All Content tab

Cut down the clutter on All Content tab by removing facets from the search results page. This makes a lot of sense for firms that have one too many content sources. And if all of them make it to the facets, it can become confusing for the end-users.

e. Improve Agent TAT

In customer service, every second counts. To that end, this upgrade aims to save a few seconds for your agents. When they copy and paste an article link for sharing with a customer, a hyperlinked article name appears.

f. Overhauled NLP Manager

A lot of options within NLP Manager have become simpler and sleeker. Some notable examples include Stopwords, Synonyms, Merge Facets, and so forth.

a. Microsoft Teams

Now make the information residing in your business communication platform more accessible.

b. RSS Feed

Ensure the nuggets of information in your RSS feeds don’t stay hidden.

c. Seismic

Improve the findability of all the crucial information in your sales enablement platform.

d. Joomla!

Search comes to Joomla! Now, all the people using the CMS can effortlessly find relevant information from across platforms.