Components installed with Task Intelligence for Customer Service
Several types of components are installed with the Task Intelligence for Customer Service application, including tables, roles, properties, flows, and scheduled jobs.
Tables
The Task Intelligence for Customer Service application uses the following tables.
| Table | Description |
|---|---|
| ML Solution [ml_solution] |
The ML Solution table stores trained machine learning solutions. Activating the Task Intelligence for Customer Service application (com.snc.csm_ml_task) creates a record in this table for the pre-trained sentiment analysis machine learning solution: ml_x_snc_global_global_sentiment. |
| ML Sentiment [ml_sentiment] |
This table stores machine learning sentiment information and includes the
following fields:
|
| Predictor Result [ml_predictor_results] |
This table stores prediction results and feedback for record categorization, sentiment analysis, and language detection. This includes skipped and failed predictions that result from prediction requests. For case categorization:
For sentiment analysis:
For language detection:
The Predictor Result table includes the Skipped field, which is a true|false field.
Note: The Predictor Result list includes a filter on the Capability field, which displays results where the capability is Classification. Remove this filter to display all of the
prediction results. |
| Case [sn_customerservice_case] |
The Case table stores customer service case records. This table is the
recipient for case categorization predictions. The Language field has been added to the Case table. This field is a reference to the Language [sys_language] table. This field is populated with the prediction made by the language detection spoke and stores the language that was used to create the email or case. The Case table is added with the Customer Service (com.sn_customerservice) plugin. |
| Task [task] |
The Task table is one of the core tables provided with the ServiceNow base system. The sentiment analysis feature adds the Sentiment column to the Task table. This column is a reference to the Task ML Sentiment [task_ml_sentiment] table. |
| Task ML Sentiment [task_ml_sentiment] |
This table stores sentiment predictions. The reference to the prediction record is stored in the Sentiment field in the Task table. This table is an extension of the ML Sentiment [ml_sentiment] table. The Task column in the Task Sentiment table is a reference to the Task [task] table and is used for domain separation. |
| Task Skills [task_m2m_skill] |
The Task Skills table stores skills for the Customer Service Management application. The language detection feature links language skills to new customer service cases by saving the detected language in the Task Skills table. The Task Skills table lists customer service cases and the language skill detected and assigned to each case. |
| Prediction preference | Top 1 prediction | Top 3 (at least 1 prediction) | Skipped |
|---|---|---|---|
| Autofill | Yes | Yes | False |
| Empty | Yes | True | |
| Recommendations | Yes | Yes | False |
| Empty | Yes | False | |
| Empty | Empty | True | |
| Monitor only | Yes | Yes | False |
| Empty | Yes | False | |
| Empty | Empty | True | |
| Prediction unsuccessful | NA | NA | True |
| Prediction error | NA | NA | True |
Tables installed with Document Intelligence for Customer Service
| Table | Description |
|---|---|
| DocIntel Use Case [di_task_definition] |
Stores Document Intelligence use cases for the Case table (sn_customerservice_case) or case type tables that extend the Case table. |
| DocIntel Task [di_task] |
Stores Document Intelligence tasks. The is_stp field controls straight through processing. When this field is set to true, straight through processing is enabled for the task. The agent_input field is set to true if an agent makes
changes to predicted values in the DocIntel tab. Note: You can track tasks from
the ML Solusions table (ml_solution.list). |
| Integration Setup [di_integration_setup] |
Stores use case filters that are applied to cases. The Target Table field stores the target for the predicted fields, either the Case table (sn_customerservice_case) or a case type table. |
| Field [di_key] |
Stores the keys to be extracted by Document Intelligence. |
| Field Value [di_extracted_value] |
Stores the extracted values for the keys in a use case task. |
Roles
| Role | Description | Contains roles |
|---|---|---|
| Task Intelligence admin [sn_csm_ml_task.ti_admin] |
Can create, train, and retrain machine learning models. This role can also deploy and delete models. |
|
| Task Intelligence analyst [sn_csm_ml_task.ti_analyst] |
Can create, train, and retrain machine learning models. |
|
[sn_ti_admin.tia_admin] |
|
|
[sn_ti_admin.tia_analyst] |
ml_admin | |
[sn_ti_admin.tia_user] |
ml_report_user | |
| Task sentiment viewer [task_ml_sentiment_viewer] |
Provides read access to records in the Task Sentiment [task_ml_sentiment]
table if the user has read access to the associated task records. This role is
added to the following roles:
|
Properties
The Task Intelligence for Customer Service application includes the following properties.
| Property | Description |
|---|---|
| sn_csm_ml_task.logging.verbosity | The log verbosity for the Task Intelligence for Customer Service application.
This property has the following values:
The default setting is info. |
| Categorization properties | |
| sn_csm_ml_case.case.categorization.mlpredictor.enabled | Enables categorization predictions for customer service cases. The default setting is false. |
| sn_csm_ml_task.categorization.attachment.max_size | Determines the maximum size of an attachment that can be parsed by categorization machine learning models. The maximum supported size is 500kb. The default setting is 450kb. |
| sn_csm_ml_task.categorization.allowed_content_types | Controls the content types and file extensions that are supported by the ML predictor for categorization with attachment. By default, the following attachment types can be used with attachment-based case categorization predictions: pdf, xls, xlsx, docx, and csv. To configure content types:
|
| sn_csm_ml_task.categorization.flow_start_time.threshold | Sets the max waiting threshold for categorization predictions that include attachments. The default value is 10 minutes. If the call to the API does not return a prediction before the maximum waiting threshold is reached, predictions are made without the attachment text. These predictions are based on text from the subject and body of the email or the case short description and description. |
| sn_csm_ml_task.categorization.case.delay_attachment_fetch | Adds a 1-second delay before fetching valid attachments for Task Intelligence when cases are created from email. |
| sn_csm_ml_task.case.categorization.enable_inactive_filter | Enable this property to remove inactive field choices from predictions. The default setting is false. |
| Sentiment analysis properties | |
| sn_csm_ml_task.case.sentiment.mlpredictor_enabled | Enables sentiment predictions for customer service cases. The default setting
is false. To enable sentiment predictions, set this property to true. Note:
This
property is automatically set to true when a sentiment model is trained and
deployed from the Task
Intelligence Admin
Console. |
| Language detection properties | |
| sn_csm_ml_task.case.language.mlpredictor.enabled | Enables language detection for customer service
cases. The default setting is false. To enable language detection, set this
property to true. Note: This property is automatically set to true when a
language detection module is tested and deployed from the Task Intelligence Admin
Console. |
| sn_csm_customerservice.case.ml.language.detection.threshold | Controls the threshold for language prediction. The default value for this property is 0.70. Predictions with a confidence level greater than the threshold are saved in the Predictor Results (ml_predictor_results_task) table and the Task Skills (task_m2m_skill) table. Predictions with a confidence level less than the threshold are only saved in the Predictor Results (ml_predictor_results_task) table. |
| sn_csm_ml_task.case.languagedetection.default_confidence | Stores the confidence level threshold for the language detection feature. The default value is 0.7. |
| Document Intelligence properties | |
| sn_csm_ml_task.case.docintel.mlpredictor.enabled | Enables Document Intelligence for Customer Service Management. Note: This
property is activated automatically when the user creates a use
case. |
| sn_csm_ml_task.case.docintel.parsing_supported_types | Contains a list of the supported attachment types: image/png,image/jpeg,application/pdf |
| sn_csm_ml_task.straight_through_processing_max_waiting_threshold | Defines the maximum waiting time for a straight through processing task to finish. The default time is 5 minutes. If a use case is configured to use the straight through processing prediction mode, the agent can see the relevant fields on the Case form automatically populated within 5 minutes of case arrival. If this threshold is exceeded, the values are skipped. However, the agent can still view the task in the DocIntel tab and manually extract the values. |
| sn_csm_ml_task.case.delay_attachment_fetch | Waits for several milliseconds before fetching valid attachments for Task
Intelligence for Customer Service when a case is created from email. Note: This
property is disabled by default. If you notice that attachments are being missed
for cases created from email, enable this property. |
Flows
| Flow | Description |
|---|---|
| Task Intelligence Sentiment [new_task_intelligence] |
This flow is inactive out of box and is activated after setting up models on the Task Intelligence Admin Console. |
| Task Intelligence Sentiment Case Update [task_intelligence_case_update_flow] |
This flow is inactive out of box and is activated after setting up models on the Task Intelligence Admin Console. |
| Task Intelligence Inbound Email
Reply [task_intelligence_inbound_email_reply] |
This flow is inactive out of box and is activated after setting up models on the Task Intelligence Admin Console. |
| Task Intelligence Case Language
Detection [task_intelligence_case_language_detection] |
Language detection determines the language used to create a case. Depending on configuration, the system can add this value to the Language field on the Case form. This field is a reference to the Language [sys_language] table. It can also add the language as a skill to the Task Skills related list on the Case form. This flow is automatically activated when a language detection module is trained and deployed from the Task Intelligence Admin Console. |
| Task intelligence - DocIntel at case creation | This flow is inactive out of box. |
| Task Intelligence - DocIntel Process Extracted Values | This flow is inactive out of box. |
Machine learning models
The sentiment analysis feature uses the ml_x_snc_global_global_sentiment machine learning model. This model is provided with the Task Intelligence for Customer Service application.
Scheduled job for categorization solution training
| Parameter | Description |
|---|---|
| trainNewSolution | Set to true to train a new solution. Set to false to retrain a solution and add the name of the solution in the existingSolutionName parameter. |
| inputFields | The fields that are used to train the model. For
example:
|
| outputFields | The fields to be predicted. For
example:
|
| encodedQuery | The query that is applied to the data used for training. |
| existingSolutionName | The name of an existing solution. Add a name to this parameter if retraining a solution. |
To determine when a solution is ready to be used for categorization predictions, the system administrator can check the status of the scheduled job. Once the state is Solution Complete, the solution can be used for predictions.
Scheduled job for publishing previously deployed models
The system administrator can run the Deploying Task Intelligence for Customer Service Management after upgrading the Task Intelligence for Customer service plugin.
This scheduled job verifies if there are previously deployed models for record categorization, sentiment analysis, language detection, and Document Intelligence and publishes these models.