Skip to main content

    Filter by idea status

    Filter by product

    1293 Ideas

    kaushik.muralidaran
    kaushik.muralidaranKnown Participant

    Enable Native Image Support in Bot Conversations (Beyond iFrame Rendering in MS Teams)4. Future Consideration

    I would like to propose enhancing the bot experience by enabling native image support within bot conversations, rather than rendering images through an iFrame in MS Teams.Key Benefits: Improved User Experience for IT Support Use-Cases Allowing images within conversations will help visually guide users through resolution steps especially useful for IT-related issues where screenshots can simplify instructions and reduce confusion. Support for Image Generation via LLMs Enabling image rendering would unlock use-cases such as internal branding or design content creation, where images are generated based on user input using integrated LLMs. Downloadable Visual Assets Native support would allow users to download images directly from the chat, which is currently not possible with the iFrame-based rendering. This also adds better control over image formatting and display. Proven Feasibility This is technically achievable, as seen in the current implementation of “Employee Communications” messages, where the bot can display images alongside text. Extending this functionality to AAE plugins, Paths, Events, FAQs, etc., using HTML formatting or inline support, would bring consistency across all bot experiences. This enhancement will make bot interactions more intuitive, visually engaging, and functional across a broader range of enterprise use-cases.

    kaushik.muralidaran
    kaushik.muralidaranKnown Participant

    Enable Graph and Tabular Data Rendering in Bot Conversations4. Future Consideration

    I’d like to propose a feature enhancement to allow bots to natively render graphs and tabular data within conversations, rather than returning plain text responses. This would significantly improve the clarity and usefulness of data-centric interactions.Key Benefits: Improved Data Visualization Displaying charts, graphs, and tables directly in the chat would allow users to better understand trends and summaries, making responses more actionable and insightful. Dynamic Output from Excel or Backend Data When bots fetch data from Excel files or backend databases, having the ability to render that data visually can greatly enhance comprehension and reduce the need to switch between tools. Support for Business-Critical Use-Cases Functions like Sales, Finance, and Operations often rely on structured data. Rendering information visually within the conversation can boost productivity and reduce interpretation errors. Modern and Intuitive User Experience Providing rich, visual responses aligns with evolving user expectations from conversational platforms and makes data interactions more intuitive and engaging. Suggested Areas of Application: Response generation based on uploaded spreadsheets Output from API calls or internal dashboards KPI or metric summaries within structured workflows This feature would open up a wide range of data-driven automation and support scenarios, making chatbot interactions far more powerful and user-friendly.

    gurmanpreet singhNew Participant

    Customizing Fields in My Assistance Notification UI for HR Case Tickets – Limitations & Request for Enhancement1. New

    We're currently working on customizing the notification UI for HR Case tickets in the My Assistance interface, specifically for scenarios when:An HR Case operator comments on a ticket A ticket is awaiting acceptance from the userGoal:We would like to display only the following fields in these notification states:When HRC Operator comments: HRC Number & Title Status Last Activity When ticket is awaiting user acceptance: HRC Number & Title Status Last Activity Current Behavior:Moveworks currently displays standard ticket fields in all such notifications if those fields have values — even if some of them are not relevant to our users in this context.We reached out to Moveworks support and learned that:These fields are mapped at the platform level, and not customizable at the individual use-case level. Steerability was tested, but the model couldn't override the field inclusion. Therefore, removing or limiting fields displayed in the notification UI for particular use case isn't currently supported.Why This Matters:Customizing visible fields based on ticket state or context would:Improve clarity for end users. Reduce visual noise in the notification UI. Increase adoption and satisfaction with the My Assistance interface.Request:If others have found workarounds or custom configurations to manage visible fields in ticket notifications, please share your experiences. If this is a common need, we’d love to see Moveworks consider adding this as a platform-level enhancement