Skip to main content

    Filter by idea status

    Filter by product

    1294 Ideas

    sujit gaikwadKnown Participant

    Prioritization of Custom Use Cases in Bot Responses1. New

    Problem Statement:Currently, the bot dynamically selects plugins to respond to user queries. However, even when custom use cases are available, they are not consistently prioritized. Multiple plugins often result in custom use cases appearing as secondary or tertiary options, while articles are sometimes prioritized instead. This behavior diminishes the importance of business-aligned custom use cases and negatively impacts efficiency.Description:We propose an enhancement to the bot's functionality to prioritize and trigger custom use cases (Creator Studio use cases) first, ensuring they take precedence in responses. This prioritization would then be followed by forms and articles, aligning with business-critical needs and enhancing the user experience.For any user utterance, the bot should always check CREST use cases first, followed by forms, and then articles if the bot lacks confidence in a CREST use case.In scenarios involving multiple plugin responses, if a CREST use case is available for the user utterance, it should always appear at the top (as the first record), followed by forms and articles. If no CREST use case is available, forms should be prioritized over articles.Plugin Priority Sequence:Creator Studio use cases Forms ArticlesCurrent Behavior:Custom use cases (Creator Studio use cases) do not consistently appear at the top of multi-plugin responses. The bot selects plugins dynamically based on its interpretation of the user's query, with no predefined priority sequence. This leads to unpredictable response ordering, which does not prioritize business-critical workflows.Expected Behavior:Custom use cases (Creator Studio use cases) should always be prioritized and triggered first in bot responses, ensuring alignment with business objectives. If no relevant custom use case is available, the bot should prioritize forms and then articles, based on the confidence score. This adjustment will ensure that business-critical workflows are given precedence, minimizing user frustration and improving overall efficiency.