- Getting started
- Communications Mining™ overview
- How businesses can use Communications Mining™
- Getting started using Communications Mining™
- Balance
- Clusters
- Concept drift
- Coverage
- Datasets
- General fields (previously entities)
- Labels (predictions, confidence levels, hierarchy, etc.)
- Models
- Streams
- Model Rating
- Projects
- Precision
- Recall
- Reviewed and unreviewed messages
- Sources
- Taxonomies
- Training
- True and false positive and negative predictions
- Validation
- Messages
- Administration
- Manage sources and datasets
- Understanding the data structure and permissions
- Create a data source in the GUI
- Uploading a CSV file into a source
- Create a new dataset
- Multilingual sources and datasets
- Enabling sentiment on a dataset
- Amend a dataset's settings
- Delete messages via the UI
- Delete a dataset
- Delete a source
- Export a dataset
- Using Exchange Integrations
- Preparing data for .CSV upload
- Model training and maintenance
- Understanding labels, general fields and metadata
- Label hierarchy and best practice
- Defining your taxonomy objectives
- Analytics vs. automation use cases
- Turning your objectives into labels
- Building your taxonomy structure
- Taxonomy design best practice
- Importing your taxonomy
- Overview of the model training process
- Generative Annotation (NEW)
- Understanding the status of your dataset
- Model training and annotating best practice
- Training with label sentiment analysis enabled
- Train
- Introduction to Refine
- Precision and recall explained
- Precision and recall
- How does Validation work?
- Understanding and improving model performance
- Why might a label have low average precision?
- Training using Check label and Missed label
- Training using Teach label (Refine)
- Training using Search (Refine)
- Understanding and increasing coverage
- Improving Balance and using Rebalance
- When to stop training your model
- Using general fields
- Generative extraction
- Using analytics and monitoring
- Automations and Communications Mining
- Licensing information
- FAQs and more
Getting started using Communications Mining™
The list below describes key steps required to set up and deliver a Communications Mining™ use case:
Automation Cloud users
If you are an Automation Cloud user and have AI units enabled, Communications Mining™ can be accessed via the Automation Cloud. If you don't have any AI units but want to start using Communications Mining™, please contact your account manager.
To access Communications Mining™ on Automation Cloud, the following conditions must be met:
- Communications Mining™ must be enabled as a service on your Automation Cloud tenant by an Admin. To do this, an enterprise licence is required, and your Automation Cloud organization must have AI units available
- You must be an existing user on the Automation Cloud tenant - If you are not an existing user, please ask an Admin on your Automation Cloud tenant to add you
For further information on how to access Communications Mining™ on Automation Cloud for the first time, click here.
For further information on how to manage your account on Automation Cloud, click here.
Legacy users
You don't need to be an Automation Cloud user to access Communications Mining™. Once your account has been requested by the Admin, you receive an automatic email with guidance on how to setup your account. Please note that this email contains a link that is valid for 24 hours before expiring.
For further information on how to access Communications Mining™ for the first time, click here.
For further information on how to manage your account, click here.
Projects can be thought of as restricted workspaces. Each dataset and data source is associated with a specific project, with users requiring permissions in those projects to be able to work with the data within them. Datasets in one project can be made up of data sources multiple projects. Users will just require permissions in both projects to view and annotate the data.
For more information on data structure, click here.
For Automation Cloud users, every tenant has a 'Default Project' that all users within the tenant have access to. Before uploading data, creating datasets and training models, it's strongly recommended to create a new project with access limited to only those individuals who require access to that data. Once created, it's difficult to move data sources and datasets into different projects.
To create a new project, follow the steps here.
Access to Communications Mining™ tenants, projects, data sources and datasets is controlled by strict user permissions. Permissions need to be allocated per-user. They can provide access to sensitive data and allow users to perform a range of different actions in the platform. Users should only be given permissions they need to fulfil their roles. See here for a more detailed explanation of user permissions.
To create a new legacy user, follow the steps here.
To add a user to a project, follow the steps here.
To update user permissions, follow the steps here.
Data sources are collections of raw unannotated communications data of a similar type (e.g. emails from a shared mailbox or a collection of NPS survey responses).
Creating a source in the GUI essentially sets up an empty source with defined properties, that data can then be uploaded to via the API. The setup of this source can also be done via the API.
Once the source is created, data can be uploaded via:
- Integration (i.e. Exchange integration, Salesforce integration, etc.)
- Static CSV upload
To create a new data source in the GUI, follow the steps here.
To upload a CSV file into a source, follow the steps here.
For integration guidance and technical documentation, click here.
Datasets are comprised of 1 or more data sources (max 20) and the model that you train.
Please note that sources can sit in a different project to a dataset. As long as users have the appropriate permissions in each project, they will be able to view & annotate the data as usual.
If there are multiple sources in a dataset, they should share a similar intended purpose for your analysis or automation.
When you create a new dataset, you can choose to create a copy of a pre-existing dataset. This means that you copy over the same sources, general fields, sentiment selection, labels and reviewed examples.
To create a new dataset, follow the steps here.
For more information on using multilingual datasets and sources, click here.
Prerequisites before you start training a Communications Mining™ model include:
- Defined objectives and success criteria
- Designed taxonomy of labels and fields
- Business SMEs with domain-specific knowledge
- Ring-fenced time to train the model
Any model that is being used in production needs to be effectively maintained to ensure continued high-performance. This includes a) preventing concept drift, and b) creating an exceptions process.
For further model training information, see the links below:
- Preparing for model training
- Model training:
- Model maintenance
The platform has built-in reporting and analytics capability that can help you identify potential issues and improvement opportunities across your communications channels, for example:
- Requests that are transactional in nature can be good candidates for automation or self-service
- Requests that get no response or follow-up can potentially be eliminated
- No-action required emails (i.e. OOO, spam, auto-generated emails, thank you emails) can potentially be deleted from a mailbox
- Urgent queries that need to be prioritised and resolved immediately
- Root causes that are driving customer dissatisfaction, escalations, chasers
For more information on generating insight and building reports, click here.
The platform enables downstream automation by creating a queue of communications that can be read by a robot.
These queues are driven by the confidence thresholds levels. Setting a threshold means that for the message to enter the queue, the platform must predict that label with a confidence that is equal to or greater than the threshold you set.
For more information on creating and managing streams (formerly known as triggers), click here.
For detailed overview of the UiPath®<>Communications Mining™ automation framework, click here.
