Connect to Other Bots
Best Practices
Many enterprise business systems will publish their own tier-one copilot with pre-built integrations that you'll want to connect to Moveworks (a tier-four copilot).
This is typically done with a technique called messaging brokering, where messages from one copilot can be sent through another copilot (i.e. allow Moveworks to use another bot on the user's behalf).
Tier-one copilots are not extensible
However, as an industry practice, these tier-one copilots are not extensible. They DO NOT expose any APIs for message brokering through tier-four copilots like Moveworks.
The Solution
The correct way to build integrations to these enterprise business systems is through REST APIs (ideally the same ones those tier-one copilots rely on).
Reusing Tier-One Copilots
If you want to reuse tier-one copilots, you'll need to describe their capabilities in a Moveworks FAQ. Our best practice recommendation is to add a deep link so you can redirect users to those bots.