Our organization is using Moveworks Copilot and Gemini. I am wondering if it is possible to merge both to build something similar to 'Quick GPT,' where users can go to our Moveworks Copilot and ask Gemini for answers.
I am thinking of building an Agent Studio plugin and adding triggers like 'Ask Gemini,' but I am wondering if there is a better and more straightforward way.
Also, is it possible to build a fallback mechanism where, if the bot cannot find an answer in the internal KB or Forms, it suggests the Gemini plugin?
Best answer by rgeroulo
@mmasiulis the update that the FDE/Support can provide would be more of a system prompt within your Moveworks reasoning engine. The prompt would be something simple like:
Always call the AskGemini tool if smart_handoff_plugin is being served. Again, only serve the AskGemini tool if there is no other relevant tool and smart_handoff_plugin is going to be called. AskGemini should be a catch all along with smart_handoff_plugin to serve the user a GPT response.
As you can see, this would be a prompt that your Moveworks assistant will see and will have to reason with. This prompt would be a powerful change to your environment and would be seen during every user interaction. With that said, it is important to determine if something like this is actually desired or needed.
This prompt would not be domain specific as it will be seen in every interaction. If that is a requirement, then this approach might not be the best option.
Building an Agent Studio plugin to leverage the Google Gemini API, specifically the generateContent endpoint, would be the path forward. It is very common to connect internal GPTs or other generative models to Moveworks via Agent Studio.
In regards to your ask about having this plugin be a “fallback”, this is possible in a certain form. This is not something that is currently serviceable in the platform today so you would have to engage your FDE or Support for assistance. Your ask and logic would be to have the Moveworks reasoning engine call your AskGemini plugin when the SmartHandoff plugin is called.
SmartHandoff is the situation where there are not any resources to serve the user so the bot will serve the File a Ticket or Live Agent Chat options as the catch all. You would want your AskGemini plugin to fire before this is offered.
Maybe you have examples how SmartHandoff would look here? From what I understand FDE or Support can help us to setup SmartHandoff to point where bot will call AskGemini plugin? As we talking about SmartHandoff does that mean we also can ensure that plugin will be triggered just for specific domain? We want to be careful and make sure that Gemini only responds to specific domain queries.
Cool idea, we have experimented with this internally, and we’ve had some good success.
I am not sure what you mean by a more “straightforward” way of building it, but the way to do it would be the following:
Have a plugin with several utterances such as “Hey Gemini”, “Hey Gemini, how do I XYZ”. I would add a few of these.
A conversation process where you call the Gemini API as an HTTP action. You should pass the user query, and you may be able to also pass the conversation context.
When it comes to triggering this plugin when the assistant cannot find an answer, unfortunately, that is not something built in that can be set up today.
@mmasiulis the update that the FDE/Support can provide would be more of a system prompt within your Moveworks reasoning engine. The prompt would be something simple like:
Always call the AskGemini tool if smart_handoff_plugin is being served. Again, only serve the AskGemini tool if there is no other relevant tool and smart_handoff_plugin is going to be called. AskGemini should be a catch all along with smart_handoff_plugin to serve the user a GPT response.
As you can see, this would be a prompt that your Moveworks assistant will see and will have to reason with. This prompt would be a powerful change to your environment and would be seen during every user interaction. With that said, it is important to determine if something like this is actually desired or needed.
This prompt would not be domain specific as it will be seen in every interaction. If that is a requirement, then this approach might not be the best option.
For current customers who manage their engagement with Moveworks, please login or create your account with the customer button below. For Moveworks Partners, please login or create your account with the partner button below.
For current customers who manage their engagement with Moveworks, please login or create your account with the customer button below. For Moveworks Partners, please login or create your account with the partner button below.
