Build better products with our product team.
Occasionally, some unexpected behavior will arise from an Agent Studio plugin, built in functionality, etc. Today I was picking through the logs for a plugin that ran earlier this week and found which log identified the break, but it’s not expected to me based on previous testing. I prepared to open a support ticket and thought: It would be nice to have a quick/deep link of some sort to open a ticket directly from this log entry I’m viewing, with the log automatically attached to the support ticket.The same functionality could be useful on the Raw Interactions table in the Analytics module as well.
The ProblemToday, the Moveworks bot in Microsoft Teams (and Slack) only has a Chat and Shared tab. All notifications — ticket updates, approval requests, pending actions, comms — land directly in the Chat conversation alongside regular bot interactions.This creates a real problem:Notifications get buried. As soon as a user sends a new message to the bot, older notifications scroll out of view. There's no way to see a consolidated list of pending items without scrolling back through the chat history. Busy managers lose track of approvals. Managers with high approval volumes can't efficiently triage what needs attention. They're not going to have a back-and-forth conversation with a chatbot to filter down pending requests — they'll just open ServiceNow directly, which defeats the purpose of the bot. The problem gets worse at scale. The more notification types you enable (ticket concierge, approval reminders, comms, visitor alerts), the noisier the chat becomes, and the more likely critical notifications are missed.As one of our store managers put it when testing Bolt visitor notifications:" it kind of got lost between two others, so not necessarily obvious." What We WantWe'd love Moveworks to adopt the same tab structure that other Teams apps (like Workday) already use:Tab Purpose App Dedicated notification feed — ticket updates, approval requests, pending actions, comms. Structured, scannable, persistent. Chat Conversational interaction with the bot — questions, lookups, form submissions. Shared Shared files and links (already exists). The Workday Teams app is a great reference. Its "App" tab shows Quick Actions, tasks, and calendar events — completely separate from the "Chat" tab where users interact with the Workday bot. Notifications like time-off approvals appear in Chat, but the persistent task list lives in App. This separation keeps things clean and actionable.Why This MattersYou've already solved this on the web. The Moveworks Web Assistant (/assistant) has a dedicated Notifications panel — separate from the chat. It works well. But it pulls users away from their primary collaboration platform (Teams/Slack) and requires additional SSO app assignment (e.g. Okta), which is more admin overhead. Microsoft Teams supports this pattern natively. The Teams platform provides Activity Feed Notification APIs and supports custom tabs within bot apps. The technical capability exists. Meet users where they are. Moveworks' own mission is to "meet employees where they are." For most enterprises, that's Teams or Slack — not a separate web portal. The notification experience should live there too. Approval velocity. Managers need a glanceable, structured view of what's pending — not a chat transcript to scroll through. A dedicated tab would significantly reduce approval turnaround time and friction.What This Could Look LikeNotification feed in the "App" tab — filterable by type (approvals, ticket updates, comms, reminders). Badge count on the App tab showing unread/pending notifications. Actionable cards — approve/reject, acknowledge, or deep-link to ServiceNow directly from the notification. Persistent state — notifications remain visible and accessible until actioned, not buried by new chat messages.Who This ImpactsThis isn't a niche request. Every Moveworks customer on Teams or Slack that uses ticket notifications, approval workflows, or employee comms is affected. The challenge scales with org size — the more users and notification types you enable, the worse the chat-noise problem becomes.TL;DRCurrent State Desired State All notifications land in the Chat tab Notifications in a dedicated App tab Notifications scroll away with new messages Persistent, scannable notification feed Managers must scroll or ask the bot to filter Structured view with filters and badge counts Web Assistant has this — Teams/Slack doesn't Parity across all surfaces Web Assistant requires separate SSO/Okta app Keep the experience in Teams/Slack If you're dealing with this same challenge — please upvote and comment. The more visibility this gets, the more likely it makes it onto the roadmap. 🙏Here’s what it could look like
Please enhance the Unily connector so that content marked as Hidden in Unily is not ingested or used by Moveworks, even if it is published.Current BehaviorContent with isHidden: true is still ingested because the connector filters on isPublished and isTrashed, but does not currently account for the Hidden flag.Why This MattersWe use the Hidden status in Unily to:Temporarily disable content Prepare content for future release Quickly turn features/widgets on or offIngesting Hidden content causes unintended exposure of content that is intentionally suppressed.Expected BehaviorContent marked as Hidden in Unily should be excluded from Moveworks ingestion and usage.
Support Vetted Content in Assistant experience
AI Assistant as an agent within the Microsoft Copilot experience
Making the Slack app available via the Slack Marketplace Store
Use the Slack pop-up to manage the MW Reference modal and Global Actions
Today, any change to a user’s email address—the universal join key in our instance—causes Moveworks to create a new user record and deactivate the previous one. This breaks analytics continuity, as historical interactions remain tied to the old user ID and metrics such as first_interaction_time and latest_interaction_time reset under the new record. This behavior can also be triggered when a user updates their first or last name in Entra, since those updates often result in an email address change.Proposed solution: Introduce a stable, canonical user identity that is independent of mutable attributes like email address and use that identity to preserve analytics continuity across profile changes.
Can we have interactive buttons available again for Agent Studio?Previously, this feature was only supported in Classic Studio, which is being phased out soon. We’ve been developing several use cases that rely on active user input, and the lack of buttons is creating friction in the experience.More teams are requesting approval workflows through our chatbot. While the interactive button options can be done natively with ServiceNow, it won’t be possible for other API-based use cases, which could make the experience inconsistent and confusing for end users.Additionally, many of the plugins showcased in the AI Agent Marketplace display buttons as part of their interface. Does this indicate there’s already a roadmap for bringing this functionality back to Agent Studio?
We'd like the ability to filter Unily content ingestion by page/content type.Currently, all content types are ingested without the option to exclude specific categories. This creates a practical problem: content types like news articles have a short shelf life and, once stale, can cause the assistant to return inaccurate or outdated responses. The only current option is to exclude entire site sections, which is too blunt when the issue is type-specific.A page type filter — ideally configurable per connector instance in the admin UI — would allow teams to include only the content types that are appropriate for AI assistant retrieval (e.g. policies, how-to guides, FAQs) and exclude those that aren't (e.g. news, announcements, event pages).This would improve response accuracy and give admins more precise control over what the assistant surfaces to users.
Hi ,As we have multiple Moveworks instances within our organization, I would like to explore the possibility of configuring distinct color schemes for each instance. This would enable quick visual identification at a glance. Regards,Rajeev
Major upgrades to Data Crawling Viewer and Control Center with crawled records view, failed API call insights, record activity logs, improved indexing terminology and Redesigned UI/UX.
Address issues with GPT-5.2 that lead to verbose & system-level dialogs
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK