Hello, @Hann Chiad Hooy.
Just adding, I would avoid using only one-word utterances like "Outlook", "Word", "Teams", or "Visio" as the main training examples. They can work in some cases, but they can also create ambiguity and false positives, especially with words like "Teams" and "Word", which can appear in normal sentences with different meanings.
In my opinion, the design depends on what you want to do after identifying the product.
If all Microsoft Office products follow the same path, I would keep one intent, something like "Microsoft Office Products", and use slots to capture the specific product, such as Outlook, Word, Teams, Visio, Excel, etc. Then you can route or personalize the response based on the slot value.
But if each product has a very different process, different troubleshooting steps, different routing, or different teams responsible for support, then separate intents may be cleaner, like Microsoft Outlook Support, Microsoft Teams Support, Microsoft Word Support, and so on.
Either way, I would train the bot with full user phrases, not only product names. For example: "I need help with Outlook", "Teams is not opening", "I cannot access Word", "I have an issue with Visio". That gives the model more context and usually improves intent detection.
------------------------------
Arthur Pereira Reinoldes
------------------------------