- Introduction
- Setting up your account
- Balance
- Clusters
- Concept drift
- Coverage
- Datasets
- General fields
- Labels (predictions, confidence levels, label hierarchy, and label sentiment)
- Models
- Streams
- Model Rating
- Projects
- Precision
- Recall
- Annotated and unannotated messages
- Extraction Fields
- Sources
- Taxonomies
- Training
- True and false positive and negative predictions
- Validation
- Messages
- Access Control and Administration
- Manage sources and datasets
- Understanding the data structure and permissions
- Creating or deleting a data source in the GUI
- Uploading a CSV file into a source
- Preparing data for .CSV upload
- Creating a dataset
- Multilingual sources and datasets
- Enabling sentiment on a dataset
- Amending dataset settings
- Deleting a message
- Deleting a dataset
- Exporting a dataset
- Using Exchange integrations
- Model training and maintenance
- Understanding labels, general fields, and metadata
- Label hierarchy and best practices
- Comparing analytics and automation use cases
- Turning your objectives into labels
- Overview of the model training process
- Generative Annotation
- Dastaset status
- Model training and annotating best practice
- Training with label sentiment analysis enabled
- Training chat and calls data
- Understanding data requirements
- Train
- Introduction to Refine
- Precision and recall explained
- Precision and Recall
- How validation works
- Understanding and improving model performance
- Reasons for label 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™
- Developer
- Overview
- Creating a connected app
- Salesforce integration
- Exchange Integration with Azure service user
- Exchange Integration with Azure Application Authentication
- Exchange Integration with Azure Application Authentication and Graph
- Fetching data for Tableau with Python
- Elasticsearch integration
- Self-hosted Exchange integration
- UiPath® Automation Framework
- UiPath® Marketplace activities
- UiPath® official activities
- How machines learn to understand words: a guide to embeddings in NLP
- Prompt-based learning with Transformers
- Efficient Transformers II: knowledge distillation & fine-tuning
- Efficient Transformers I: attention mechanisms
- Deep hierarchical unsupervised intent modelling: getting value without training data
- Fixing annotating bias with Communications Mining™
- Active learning: better ML models in less time
- It's all in the numbers - assessing model performance with metrics
- Why model validation is important
- Comparing Communications Mining™ and Google AutoML for conversational data intelligence
- Licensing
- FAQs and more
Communications Mining user guide
In order to provide Communications Mining™ access to your Salesforce instance, a Salesforce administrator will need to create a Connected App.
It's worth familiarizing yourself with the concepts of Connected Apps, but to set up the Communications Mining Salesforce Integration the following steps should be sufficient. These steps should be completed using the same account that the Connected App will be authenticated with.
INTEGRATION USER
Any Salesforce user with the right access to the data you'd provide to Communications Mining can be used to authenticate the integration. In general, it's recommended to use a dedicated integration user for this so that the Salesforce Integration is not tied to a specific person's account. You can read more about Salesforce's recommendations on the matter here.
- In your Salesforce Setup, under Apps, select App Manager and click on New Connected App.
Create a new Connected App in Salesforce
- Follow the guidance from Salesforce and fill in the required information, such as App Name, API Name and Contact Email. The following is an example:
Example required information
- Select the checkbox Enable OAuth2 Settings, this will open up a new section of options.
-
Make sure that the application does not require Proof Key for Code Exchange (PKCE).
-
- Under Callback URL, insert the following line, replacing
<mydomain>with your tenant domain:https://<mydomain>.reinfer.io/external/salesforce/oauth2/callback. - The following scopes are required for the Salesforce Integration to work. Add them to Selected OAuth2 Scopes.
OAUTH2 SCOPES Manage user data via APIs (api) Perform requests on your behalf at any time (refresh_token, offline_access) The required OAuth2 settings for the Connected App - You do not need to change any of the other settings. Click Save at the bottom of the page to create the Connected App.
- Take note of the Consumer Key and Consumer Secret of the Connected App you just created. You will need to send them to us to set up the integration.
Consumer Key and Consumer Secret
