--- sourceDocument: Xanadu Customer Service Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/customer-service-management Release : - xanadu ft:locale : - en-US ft:publication_title : - Xanadu Customer Service Management ft:clusterId : - csm bundleId : - csm workflow : - Customer and Industry --- # Record categorization # Record categorization {#ariaid-title1} * Release version: Xanadu * * Updated August 1, 2024 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read The record categorization feature included with Task Intelligence for Customer Service uses machine learning models to evaluate text, predict field values, and automatically populate fields on case and interaction records. Record categorization supports multiple languages and can scan attachments in addition to evaluating text from emails and records. Use this feature to categorize cases, case types, and interactions from multiple channels including email, web, and chat. You can use the results of the categorization to automatically route records to the right service desk, which prevents the need for multiple email inboxes and RPA bots. Auto routing also frees up your employees to work on other tasks. Figure 1. Case form with predicted and recommended field values ## Predicted field values {#case-categorization-overview__section_d11_5fb_4yb} On case and interaction records, the fields that contain predicted values are identified with an AI icon and label (![generative AI sparkle icon and label]()). These fields also include an information icon that displays a message with additional context about the predicted values. Note: in CSM Configurable Workspace, the AI icon is persistent over the lifecycle of the record. In Core UI, the AI icon is removed when the agent changes the field value. In CSM Configurable Workspace and Core UI, the fields on the record that contain predicted values are identified with the Predicted or Recommended messages. ## Recommended field values {#case-categorization-overview__section_f1s_ngb_4yb} Fields that are predicted by AI include recommended values. When an agent selects a predicted field, the system displays a dropdown list that includes the top three recommendations at the top of the list followed by all other values. This feature is available for the following types of fields: * Choice lists * Single lookup * Multi lookup * Single and multi text fields {#case-categorization-overview__ul_brl_zgb_4yb} If the top three recommendations are not available, the system displays a message in the Top Recommendations section of the dropdown list that no predictions are available. The other values follow this message. The agent can select any value from the dropdown list, either one of the top three recommended values or one of the other values. The agent can also type in the field and filter the results in the dropdown list, with the exception of the top three recommendations which are always displayed. Note: The top three recommendations remain in the dropdown list through the case lifecycle regardless of the selected field value. ## Filtering inactive field values from predictions {#case-categorization-overview__section_ipc_mkt_d1c} Enable the sn_csm_ml_task.case.categorization.enable_inactive_filter to remove inactive field values from predictions. The default setting for this property is false. ## AI prediction banner {#case-categorization-overview__section_yfx_lsb_4yb} When a case record includes a categorization prediction, the system displays a banner at the top of the record. The banner is displayed when there is at least one field with autofill predictions in categorization models. The banner is displayed for records in the Case table and extensions of the Case table. Note: The banner is displayed in CSM Configurable Workspace and in the Core UI. The system displays the banner when there is at least one field with an autofill prediction in categorization models or when one of the extracted fields has not been reviewed by the agent. The banner is displayed for records in the Case table. Note: If the agent changes the predicted value, the banner is removed. If all predicted fields are recommended, the banner is not displayed. The banner can be enabled or disabled by the sn_csm_ml_task.ui.banner.enabled system property. ## Prediction feedback {#case-categorization-overview__section_lvk_gdc_yyb} The system stores feedback on prediction results in the Predictor Result \[ml_predictor_results\] table. Users with the ml_admin role can access the table and view the results. * Autofill: a value is considered to be predicted correctly (set to true) if the predicted value and the final value are the same. * Recommendation: a value is considered to be predicted correctly if any one of the predicted values matches the final value. {#case-categorization-overview__ul_py2_h2c_yyb} The Predictor Result table also stores information about skipped and failed predictions. For more information about this table, see [Components installed with Task Intelligence for Customer Service](https://servicenow-prod.fluidtopics.net/iHwRZhMT~aKvSvgb7C5TZw "Several types of components are installed with the Task Intelligence for Customer Service application, including tables, roles, properties, flows, and scheduled jobs."). ## Multi-lingual record categorization {#case-categorization-overview__section_xvp_gn4_f5b} Use a machine learning model that understands the following languages to evaluate text in emails and records created in different languages and to predict and automatically populate fields on cases, case types, and interactions. * English * French * German * Spanish {#case-categorization-overview__ul_qsz_v2b_h5b} Multi-lingual record categorization uses one machine learning model that is trained to understand multiple languages. This model can: * Understand the text in emails and records. * Evaluate the text and predict field values. * Add the predicted values to fields on cases, case types, and interactions. {#case-categorization-overview__ul_p1w_yz3_d5b} Multi-lingual record categorization can support the following additional languages on demand: * Arabic * Chinese (PRC) * Chinese (Taiwan) * Dutch * Italian * Japanese * Korean * Polish * Portuguese * Russian * Thai * Turkish {#case-categorization-overview__ul_ccw_rmh_f5b} Note: If you need to evaluate emails or cases in these additional languages, reach out to the product team for support. ## Attachment-based record categorization {#case-categorization-overview__section_pry_kn4_f5b} Attachments can include valuable signals that help support desks to categorize and route records automatically. To take advantage of attachment information, you can use a machine learning model to parse email and record text and attachments and automatically populate fields on cases, case types, and interactions based on signals contained in the text. The model can predict information about a case based on: * Text in the subject line and body of a customer email. * Text in the short description and description of a case or interaction. * Text in email and record attachments. {#case-categorization-overview__ul_uwd_vf3_f5b} Note: The model can be configured to use different fields for prediction. Attachment-based categorization uses all of this information to predict field values. As a result, you can automatically route records to the appropriate service desk based on these values. **Related concepts** * [Configure record categorization](https://servicenow-prod.fluidtopics.net/DRIOsSe8VoJx38Y3A3Yt5g "Activate the required plugins, import training data, and create and train a model to predict field values for case and interaction records.") * [Task Intelligence Admin Console](https://servicenow-prod.fluidtopics.net/pYS8Y8i68iZDxM8kY7qgmA "Use the Task Intelligence Admin Console to create, train, and deploy machine learning models that predict different types of information for case and interaction records.") * [Create a model to predict record fields](https://servicenow-prod.fluidtopics.net/l3oGyWOM6Fj~MwK8ZBONOQ "Create and train a model to predict fields for case and interaction records.")