Bring back ‘buttons’ for Agent Studio

Hi Diana, we do plan to bring this back into the assistant experience. We don’t have a target date on our roadmap for this yet, but it is something that we are planning for.

We’ll keep you in the loop as we get closer to this.

+1 to what Ajay said. Buttons are coming back to the assistant experience. No target date yet, but it's planned.

Some context on the direction we're exploring: a generative UI layer where the agent can surface interactive elements when they actually help (approvals, confirmations, quick selections). The key is making it feel native to the conversation, not a throwback to classic chatbot flows.

We want the agent to be smart about when to use buttons vs. when natural language is faster. For something like "approve John's timecard," you probably don't need a button. The agent can just do it. But for "which of these 5 expenses do you want to submit?", buttons would shine.

Still early, but that's the thinking.
 

Hi ​@Kevin Mok ​@Ajay Merchia - any updates on this item? We have a lot of interest in creating agents with customized buttons to help us speed up the flow.

Hey ​@DIANA.TWC -  We currently support buttons when using the notify compound action expression. Use cases like this, where you have approval requests triggered from an external platform, then you should be able to have buttons.

But if you're looking to add buttons in a conversation process, that's still not something that we support and I don't have any updates for you at this time. We believe in agentic conversation flows and we have noticed that buttons can be hard coded and not very flexible sometimes although I will still circle back internally 

Hi ​@Kevin Mok ,

I strongly believe this enhancement makes sense to implement, primarily from an end user experience perspective.

Currently, Moveworks uses buttons for both notify and confirmation policies - so the natural next step is to extend button support to compound actions as well. It would also allow flows to be more deterministic when needed.

The inconsistency today creates a friction point: a user begins an interaction using buttons (confirmation policy), but after a dynamic slot resolver is presented with a numbered list (yes or no for example). This shift is unintuitive and disrupts the overall experience flow.

I also explored using Notify as a workaround - for example, to collect user feedback after an action completes and present buttons at that stage. However, this approach falls short:

• It breaks the conversational flow
• It generates too many messages
• The overall experience feels disjointed

Aligning compound actions with the same button driven pattern used elsewhere in Moveworks would create a consistent, seamless experience from start to finish.

Just my view thanks!