ixp
latest
false
Important :
Communications Mining is now part of UiPath IXP. Check the Introduction in the Overview Guide for more details.
UiPath logo, featuring letters U and I in white

Communications Mining user guide

Last updated Aug 1, 2025

Training chat and calls data

User permissions required: ‘View Sources’ AND ‘Review and annotate’.

Note: Users will be able to see chat and calls data if they have ‘View Sources’ AND see labels if they have ‘View labels’ permissions, but they will require the ‘Review and annotate’ permission in order to actually apply labels.

Overview

Chat/calls data are commonly trained for analytics and monitoring-based use cases to gain a detailed understanding of the processes, issues, and sentiments within a conversation.

Some examples of questions you can answer for these communication types:

  • How many conversations start with a customer asking us about a topic, a complaint, etc.?
  • What are the top topics customers are contacting us about?
  • How long does it take to resolve a conversation about a given topic?
  • What is the quality of service that agents are providing for our customers?
  • What is the sentiment when a certain topic is mentioned?

Layout

A chat/call thread
docs image

Layout explained:

  1. This is used to indicate that a message has been marked as uninformative
  2. This indicates that a label has been added onto a message
  3. This allows a user to mark a message as uninformative
  4. This allows a user to add a label onto a message
  5. This allows a user to play back an audio recording, control the speed/volume, or download a call.

Model training

Note: If you have sentiment analysis enabled on your chat/calls data, the differences when annotating are the same as annotating with sentiment for other communications channels (i.e. - assigning a sentiment each time you assign a label, using neutral label names, etc.). See here for more details on annotating with sentiment analysis.

Training chat/calls data is very similar to training other message types, where a user would go through the Discover, Explore, Refine phases to train their model further.

The key distinctions are:

  1. Thread layout - With chat/calls data, messages between all parties in a given conversation are automatically compiled into a single thread view, but labels are still assigned to individual messages (i.e. - turns in the conversation).
  2. Uninformative messages - A message in a chat/call can be marked as 'uninformative' if it does not add context or value to the given conversation. By marking a message as uninformative, you are teaching the model that none of the labels are applicable, and therefore the model will learn that similar messages should not be expected to have label predictions.
    Note: When applying labels to a message ('message A'), the model will automatically mark the previous message Message B as uninformative if no labels are applied to it. It's therefore important to read the previous message and apply labels to it if relevant. This feature helps to build up the necessary training data for 'Uninformative', without too much additional annotating.
  3. Coverage - When assessing coverage for chat/calls data, in addition to assessing the proportion of messages covered by informative (i.e - meaningful) label predictions, it also incorporates the proportion of messages that are predicted to be uninformative. For more information on how coverage is determined, select here.
Validation factor card for coverage for a chat or calls datasetdocs image
  • Overview
  • Layout
  • Model training

Was this page helpful?

Get The Help You Need
Learning RPA - Automation Courses
UiPath Community Forum
Uipath Logo
Trust and Security
© 2005-2025 UiPath. All rights reserved.