The trigger actions need to be more robust. There could be email-based triggers or file-monitoring triggers as well. 

The orchestrator is a legacy build. It's a bit old. They could improve the orchestrator and update it to be more user-friendly and offer more credential sections. 

The solution can be expensive. 

This solution is not very user-friendly and I would not recommend it for robotic platforms. It has limited functionality and the logging takes over 1,000 GB. As a result, each year we need to increase the size of the database and create a workaround by archiving logs. It impacts performance and is a significant pain point for us. The logging is not user-friendly from an architect's perspective. The reporting is a mess in INTELLIBOT, even the developers are struggling to identify the issues and there are also problems when there are two cases hitting the queue. 

It would be helpful to add more documentation. Currently, there are not many documents available on Google that explain each activity and how to use it or how to use the parameters and pass values. This is an area that could be improved.

If I were to add something that would make my life easier in a new release of INTELLIBOT, then it would be making improvements to the way it is interacting with Java.

The only challenge with using INTELLIBOT is the way it works with OCR, which can make creating OCR icons very challenging. In addition, there may be challenges in using the Citrix environment.

The first pain point of INTELLIBOT was with the development. Whenever the company developed any command, they published it directly onto their SQL site, and our current automation got auto-updated. The second pain point was with the action set. It could be stronger. Moreover, if I am doing UiPath automation, I have to do it with the Internal Report for now.

It can introduce strong features like automation anywhere. For example, if I want to work with Queue, with the automation anywhere feature, there are fewer steps to be followed compared to telecom. Since INTELLIBOT needs extra steps and commands, this thing can be made easy.

This should be improved in the next release.

Exception handling activities within INTELLIBOT need to improve. While working with the platform, there were instances where the bot went to a different flow than intended, even when it was supposed to decide between true and false. A couple of times, we noticed that some bugs caused the bot to go in the wrong flow. So, the aforementioned areas are to be considered for improvement in the solution.

The solution is heavily dependant on scripts, such as JavaScript or any other external script that needs to be a part of the system. If they want to grow, the scripting dependency should go away. They should have built-in libraries to pull in work from.

I would like to see the cognitive marketing platform improved.