Skip to main content
subhashchandraBose.kondapalli
New Participant
March 14, 2024
4. Future Consideration

Enhanced User engagement in Queries API Labelling

Related products:Agent Studio
  • March 14, 2024
  • 5 replies
  • 43 views

In the Queries flow, the API Labelling section is right now showing the data from API as it is, but there could be situations where we have to conditionally show more information based on the values coming from API. In such cases, adding markup’s and rules so that we can add colors or emojis to make it more user engaging could help us better.

We have  an option to add text response in Path’s flow where we can add markup in the text. Similarly if we have markup and rules to operate on API field values, it would make it more user friendly.

For example:
Current field: Battery Health(%): battery_health_percentage
Expected field: Battery Health(%): (valueOf(battery_health_percentage)<20? <b>valueOf(battery_health_percentage) + “❌” </b>: valueOf(battery_health_percentage))

Current Answer: Battery Health(%): 20
Expected Answer: Battery Health(%): 20❌

    5 replies

    Ajay Merchia
    Ajay Merchia
    Community Manager
    March 22, 2024

    Hi @subhashchandraBose.kondapalli 

    You should be able to do this today in your iPaaS – bear in mind that in a generative AI future, there is no ability to control copilot dialogs like this – the copilot is conversational and it adapts to the user’s conversation.

    It sounds like what you really want to do is inform the user if their battery health is poor, and offer them the ability to act on that? Can you clarify what the purpose of the ❌ is?

    Ajay Merchia
    Ajay Merchia
    Community Manager
    March 22, 2024
    1. New→5. Not Enough Info to Make Decision
    subhashchandraBose.kondapalliAuthor
    New Participant
    March 26, 2024

    Hi Ajay,

    I appreciate and understand that the conversational style of copilot adapts to the context. The intention of the above example is to help user identify that out of all the fields the API is showing, we intent to highlight fields in critical state to look immediately like the Battery health, with added emojis, so that the user quickly grabs the attention of these fields.

    This is also a suggestion we received from the end users since they may have to look at the whole response output, inorder to understand which fields are critical/out of safer limits. While copilot might able to understand the data, adding little things like these might help it understand the conversational intentions better is what I feel. Open to suggestions.

    Thanks for the support

    Ajay Merchia
    Ajay Merchia
    Community Manager
    June 24, 2024

    Got it. I think this might be relevant for more structured card displays. We’ll keep this under consideration.

    Ajay Merchia
    Ajay Merchia
    Community Manager
    June 24, 2024
    5. Not Enough Info to Make Decision→4. Future Consideration
    Terms & ConditionsAccessibility statement