Skip to main content
4. Future Consideration

Enable more control on default functionality

Related products:Agent Studio
  • April 6, 2026
  • 3 replies
  • 14 views

Forum|alt.badge.img+2

As someone who is not using a lot of the OOB functionality (ticketing, approvals, access, etc) and instead building it in Agent Studio, the OOB functionality is still shown to the users which creates a poor user experience. Can we have more control to turn this functionality off or control how it works?

Examples:

  1. I initiate a generic approval flow to a user to approve something. Once they approve or deny, they have buttons to see next approvals/all approvals. They would expect this to actually show all approvals in all systems which is not the case. Instead it is just what moveworks is aware of which may be stale as records are kept for 30 days. The best workaround I was provided by support was to have the buttons instead respond with a message saying what to type to initiate the plugin for approvals.
  2. I have a plugin to comment on a ticket. When I attempt to use it, instead the default functionality to comment is initiated and says I don’t have access as it is disabled.
  3. For “Get more help” on a error, I can have it do default ticket creation or a link. I would like it to be able to call a plugin instead. For a link, the button instead opens up a moveworks site which gives the link.

3 replies

Ajay Merchia
Forum|alt.badge.img+3
  • Community Manager
  • April 6, 2026

Hey Andrew. Thank you for this feedback.

  1. You are able to push approvals into the approval queue so they show up alongside the built-in approvals experience. (see cookbook here). Any feedback / challenges with that approach?
  2. Our system should be able to handle both situations. Could you share maybe some example conversation IDs with our support team and we can take a look.
  3. We’ve heard this “plugin as a backstop” idea before. It’s not supported today, but we’ll keep it under consideration: one of the things that we've seen other customers do is to include text instructions in the smart handoff that tell the user to use a certain invocation phrase that calls that specific plugin.

Ajay Merchia
Forum|alt.badge.img+3
  • Community Manager
  • April 6, 2026
Updated idea status 1. New4. Future Consideration

Forum|alt.badge.img+2
  • Author
  • Inspiring
  • April 6, 2026
  1. In one system we are using a listener to pull in approvals, but there are stale approvals if approved outside of moveworks. In another system that was setup earlier, we only have approval if it was initiated from moveworks as a listener functionality is not available as of yet. A 3rd system should have a listener soon. The stale and duplicate records is the concern here as well as systems not being completely aligned. Allowing to disable the buttons would be preferred as it presents confusion currently.
  2. Maybe we have something misconfigured then; I’ll ask for professional services to investigate.
  3. Thank you, the plugin backstop would be preferred way of moving forward. I’ll try testing out the text solution to see how it can work for us in the meantime.