Skip to main content

Trackers (Beta)


In Beta Phase

This feature is in the Beta phase. If you have any questions, ideas or suggestions please reach out to us at devrelations@symbl.ai.

Trackers allow you to track the occurrences of any characteristics or events in a conversation with just few examples. This allows you to track critical moments in conversation across several use cases in both real-time as the conversation is in-progress as well as asynchronously after the conversation is over from recordings. Few interesting use cases for Trackers would be when customer is unhappy, when someone is rude, potential sales opportunity so you can identify emerging trends and gauge the nature of interactions.

It's important to note that the Trackers don't simply look for keywords or phrases you provide, but rather uses the examples you use to define tracker to generalize the "meaning" of those samples. These could be anything from a single word keyword, phrases or even complete sentences depending on what you'd like to track in a conversation. Symbl will generalize the meaning of those samples you provide and create a fully fledged tracking context, which mean even if you have not specified similar or alternative samples they will be tracked.

For example, “I don’t have any money” is contextually similar to “I ran out of budget” as both represent similar inherent meaning, but Symbl can generalize this scope of meaning and contextually evaluate occurances of whenever there's a mention of running out of money to give you tracking mechanism that's absolutely easy to use and lightning fast in real-time with Streaming API.

Symbl removes the complexity by reading into contexts and returning messages that are not only an exact match of the key words or phrases that you have defined but are also closely or contextually similar. Further, the offset parameter shows you the extent to which the match has occured.

Using Trackers you can introduce various capabilities such as triggering workflow on tracker event in real-time or asynchronously, help users communicating in real-time, or learn from the characteristics of conversations and so on. The possibilities are really limitless and can be very tailored to specific needs of your application.

Examples#

The tracker names used in the example below are only for explanatory purposes. You can create any tracker for your usecase and assign any name you like.

  • Sandra is the training head of the Sales team in her company. She uses the insights from the Intro Tracker to look at how great sales agents start conversations and Pricing Tracker to understand how they share the pricing details. She then uses these insights to train other agents.The Intro Tracker Sandra uses tracks contextually similar phrases such as:
         "Thank you for taking some time to speak with me",
         "Have you ever noticed”,
         “Have you ever considered”.
  • Tom is the Chief Quality Assurance Manager and wants to see how many agents are using negative phrases on the customer calls. He gets insights from the Negative Phrases Tracker by tracking the following contextually similar phases:
         “I am not interested”,
         “This makes me uncomfortable”,
         “Not so good”,
         “I am skeptical”,
         “My only problem is”,
         “My only issue is”,
         “This does not fit”.
  • Samuel uses insights from Leads Tracker for all the dial out calls at his car insurance company. By tracking phrases that show buying intent, enquiry about policy options, quotes, discounts, etc., he generates more leads for his business. The Leads Tracker tracks the following contextually similar phrases:
          “I need”,
         “Policy options”,
         “Require”,
         “Use case”,
         “Fits our requirement”,
         “Quotes”,
      “Discounts”.

Key Features#

  • Ability to create Trackers for commonly used terms or phrases without worrying about the contextual relevancy.
  • Bulk creation of Trackers in a single operation.
  • Updating or deleting Trackers.
  • Ability to get Trackers (using trackerId or name) which can then be consumed in the Symbl APIs.
  • Ability to track a Conversation that contains keywords or phrases of the Tracker.
  • Ability to define the extent to which the keywords match in a message.
  • Easy management (POST/PUT/GET/DELETE) of Trackers using Management API.

Trackers API#

For step-by-step instructions on how to use Trackers API see the Using Trackers API page. The Tracker API endpoints are given below:

OperationEndpoint
Create TrackerPOST v1/manage/tracker
Create Trackers in BulkPOST v1/manage/tracker
Get Tracker with IDGETv1/manage/tracker/{trackerId}
Get Tracker with nameGET v1/manage/trackers?&name={trackerName}
Update TrackerPUTv1/manage/tracker/{trackerId}
Delete TrackerDELETEv1/manage/tracker/{trackerId}
info

Currently, Trackers is supported with Symbl’s Async APIs and Streaming APIs.

Tracker consumption with Management API#

The Trackers APIs can be consumed via the Management API, which takes the onus of maintaining these entities from the developer and shifts it to Symbl’s backend. The Management API provides an easy-to-consume REST interface for managing these entities.

Click here to read about the capabilities of Management APIs.

Related Topics#