A customer service team wants to analyze thousands of support tickets to automatically categorize them into predefined topics like 'billing', 'technical issue', and 'account management'. They have a small set of labeled tickets for each category. Which Azure AI Language feature should they use?
Custom Text Classification is a feature of Azure AI Language that lets you build a tailor-made model by training on a labeled set of support-ticket excerpts. After you upload examples tagged as 'billing' or 'technical issue,' the service learns distinctive word patterns and assigns your own category labels to new tickets. Because it handles multi-class or single-class output, it scales to thousands of incoming conversations and directly solves the team's need for topic-based analysis.
Why this answer
The Custom Text Classification feature of Azure AI Language allows you to train a model using a small set of labeled tickets to automatically categorize text into predefined topics like 'billing', 'technical issue', and 'account management'. This feature is specifically designed for scenarios where you have labeled data and need to classify documents into custom categories, making it ideal for analyzing support tickets.
Exam trap
The trap here is that candidates may confuse Custom Text Classification with pre-built features like Sentiment Analysis or Key Phrase Extraction, assuming any NLP feature can categorize tickets, but only Custom Text Classification allows training on your own labeled data for custom categories.
Why the other options are wrong
Option A is not a valid Azure AI Language feature; the correct feature for custom text classification with predefined topics is Custom Text Classification (part of Azure AI Language).
This option is wrong because the question requires a custom text classification model trained on labeled data, not a pre-built entity extraction or language detection feature.
The question requires categorizing tickets into predefined topics using labeled data, which is a text classification task. Option D (e.g., 'Conversational Language Understanding') is designed for intent and entity extraction from conversational utterances, not for categorizing long-form text like support tickets into fixed categories.