Skip to main content
MindTouch Success Center

Integrate with your customer engagement software

Your support agents are the highest yield beneficiaries of your MindTouch content. By integrating MindTouch with your customer engagement software, you can give your agents instant access to valuable information that reduces the mean time to resolution, increases customer satisfaction, and leads to ticket deflection. Integrating MindTouch with your customer engagement software, is the first step to realizing the Knowledge Centered Support (KCS) methodology. The KCS methodology enables a customer support environment in which your agents use and promote knowledge from a centralized source to drive customer self-help, expertise and self-sufficiency. Through this cycle, the KCS methodology derives meaningful and actionable data that further contributes and strengthens the cycle. To help you complete the cycle and create the ultimate customer support environment, integrate with the following applications:

  • Support ticketing system
  • Chat software
  • Customer relationship management (CRM) software


API integration points

Enable customer agent collaboration in MindTouch to add value to your customer engagement software. Each of these interactions provides data back to MindTouch that is then used to fine-tune search, create new content, and identify valuable and non-valuable content.  

 Ticket deflection

Before you enable your agents through an integration with your CES, it's an absolute necessity to set up deflection interfaces on all your customer entry points. Each entry point provides an opportunity to drive your customers to a self-help article and lower customer effort and faster resolution time.  

Essentially, you need to connect one of your text fields (typically subject) in your entry point forms to a MindTouch search recommendation widget.  

Entry points include:

  • Your ticket/case submission form
  • "Start a chat" form
  • "Suggest article" form
  • Search form

API:  /@api/deki/site/opensearch?q=QUERY&dream.out.format=jsonp&limit=5&dream.out.pre=callback&callback=?

Doc:  Integrate a "Suggest Article" feature

Dev: Use jQuery with the $.getJSON function to conduct cross domain calls against the MindTouch API. The MindTouch API is built on DREAM which supports JSONP. Make sure you use both the dream.out.format and dream.out.pre parameters to retrieve the data cross domain.  





The most natural collaboration opportunity with MindTouch and your customer engagement software is with search. MindTouch uses both your agent and user interactions with search to refine the accuracy of future searches.  

In fact, this is perhaps the most crucial part of the KCS methodology. Providing your agents access to a centralized content resource that they can share with your customers is the best way to:

  • reduce support inquires (increase self-service)
  • drive new buyers, accelerate sales and lower costs
  • standardize agent messaging
  • seize the market! (create product experts and brand advocates)

API:  /@api/deki/site/search?q=XYZ&limit=5   (GET)

DOC: Integrate MindTouch Search

DEV:  Use the jQuery Ajax GET function to query the MindTouch search API on KeyDown. Make sure you include a query parameter for q and a limit. You can also add advanced search queries in the constraint query parameter.


 Create article

Your support agents spend all day interacting with your customers. They're typically the first to know about a trending issue and, if leveraged properly, can be your front-line in ticket deflection and customer satisfaction.  

Providing your agents with a channel to create content, no matter how basic the content, gives you a direct line to information that commonly remains tribal. If you successfully tap this wealth of knowledge, you will experience improvements in mean time to resolution, customer satisfaction and customer engagement.

Templates are optional but are very effective at prescribing a content layout for agents. 

URL:  /parentpage?action=addsubpage&template=XYZ  (HREF)

Doc:  Integrate MindTouch Search

Dev:  You should keep the parent page consistent so all agent articles are created in the same location. We also recommend that you make the parent page private or semi-private so new agent content is not made public without review. Authors should subscribe to page notifications on the parent page to monitor and enhance all agent contributions. Agents need to be authenticated by pro-members to create articles.


Engagement data

The following examples demonstrate methodologies to deliver valuable MindTouch information back to your support agents. These integration points keep your agents informed, increase awareness and reward agent contribution.

 User view and search history

MindTouch records the page view and search activity for all users to help your support agents make more informed decisions and provide targeted advice.  

You should make the page view and search history immediately visible to your support agents. This will allow agents to quickly glance at a customer's search history before engaging with that customer. 

Color coding your activity based on the timeframe provides agents with a quick way to digest the history information. The example to the right demonstrates effective color coding. 

This data is not only excellent for support agents, it also allows your sales team to understand customers and buyers better. This understanding leads to:

  • improved customer renewal
  • improved product experience
  • increased revenue

API:  /@api/deki/events/support-agent/=USERNAME?limit=5 (GET)

Dev: You can use either the MindTouch username or the user token to retrieve user history. If you don't have access to the MindTouch username, we recommend adding a ticket submission form to your MindTouch site and passing the user token in the ticket. You can add the user token to your ticket submission form by extracting it out of the user.activityuri.path DekiScript function.


 Top search terms

Search activity provides your support agents an opportunity to spot trends based on collective agent activity. By presenting your agents with a 24-hour search term cloud, you will make sure that critical activity is quickly noted and agent awareness increases.  

The key to success with your search term activity is to make it visible and easy to consume. We recommend formatting your search activity into a tag cloud to quickly call attention to more significant activity. 

API:  /@api/deki/site/query/log/terms (GET)

Dev:  Each search term includes a count attribute that you can use to determine the side of the word in your tag cloud. If you dynamically set the since parameter to yesterday, you will have a 24-hour view into the trending search activity, providing you with the latest in agent activity.


  • Was this article helpful?