Machine learning model setup and behavior
Summarize
Summary of Machine Learning Model Setup and Behavior
This guide provides instructions on setting up machine learning models to predict field values and sentiment within Customer Service Management using the Task Intelligence Admin Console. The ability to train models on extensive data sets helps ensure statistically significant predictions for new customer service cases.
Show less
Key Features
- Field Prediction Model: Users with the mladmin role can create and train models using data from the Email, Case, and Interaction tables, including attachments. The model predicts output fields like Category and Priority based on input fields such as email subject and body text.
- Attachment Processing: The system parses text from supported attachments for categorization, enhancing prediction accuracy.
- Multi-Language Support: The model can categorize data in various languages and stores the predicted language in the Predictor Result table.
- Case Sentiment Model: This pre-trained model analyzes communication patterns from customer emails and case comments to assess sentiment. It updates predictions based on ongoing interactions.
- Customization: Users can select specific tables to run sentiment analysis, including the Case table and its extensions.
Key Outcomes
By implementing these machine learning models, ServiceNow customers can enhance their customer service operations through improved data-driven insights, accurate field value predictions, and refined sentiment analysis, leading to better case management and customer interactions.
Set up models to predict field values and sentiment for customer service cases.
Training a model
Training a machine learning model is when the model learns patterns in past data to make predictions for new data. Models are trained using a lot of data so that they can learn patterns and the large data set makes the learned patterns statistically significant.
Setting up a field prediction model
Users with the ml_admin role can create and train a machine learning model to predict field values from the Task Intelligence Admin Console.
- Email [sys_email] table
- Case [sn_customerservice_case] table
- Tables that extend the Case table
- Interaction [interaction] table
- Output fields are the fields that you want your model to predict. For example, the Category and Priority fields for cases.
- Input fields are the fields that the model uses as a basis for predictions. For example, text in the subject and body of an email.
You can use the recommended input fields or you can modify these fields and add your own preferences.
- The system checks the record for attachments with supported content types and file extensions. It ignores the attachments that have unsupported file extensions.
- If the record has attachments in a supported format, the system parses the text and sends it as an input to the categorization model, along with text from the input fields.
- If the record does not have attachments, or no attachments in a supported format, the system sends text from the input fields to the categorization model.
Supported content types and file extensions are stored in the sn_csm_ml_task.categorization.allowed_content_types system property. For more information, see Components installed with Task Intelligence for Customer Service.
Supporting multiple languages
Categorization supports multiple languages including attachments, if the models are configured to include attachments. The categorization model returns the predicted language and stores it in the Detected Language field in the Predictor Result [ml_predictor_results] table.
Setting up a case sentiment model
- Email: The model uses the text in the subject and body of the initial email to predict sentiment when the case is created. Text from the body of subsequent emails is used to update the prediction.
- Cases: The model uses the text in the case short description and description to predict sentiment when the case is created. Comments added to the case are used to update the prediction.
- The Case table
- Tables that extend the Case table