What is our primary use case?
Regarding the best features of Pega Robotic Process Automation, it is easy to integrate with because it's built-in. We recommend using bots only when there's no immediate roadmap for service-based interactions to make them modularized or API-based. We implement Pega Robotic Process Automation bots for tactical approaches to gain immediate benefits, but over time, we transition to API-based integration instead of using Pega Robotic Process Automation.
We have not widely used Pega Robotic Process Automation in customer service operations for automating data entry processes. Most of the data entry in customer service involves identifying the customer and retrieving data from various systems using the Customer 360 format. When Customer 360 is accessed by the agent dashboard, all necessary data is already available. We do not employ RPA for this purpose; instead, we focus on MDM implementation or customer data management for interactions. I have not encountered many use cases for applying RPA in customer service data retrieval, nor do we recommend it.
How has it helped my organization?
We have some customers while we are helping them to implement RPA mainly on repetitive, rule-based tasks like data entry, system navigation, or report generation, auto login/log-off, start my day, close my day, automate data entry etc
What is most valuable?
With Pega Robotic Process Automation, after the acquisition of OpenSpan, they are using embedded OpenSpan as one of their RPA products, but Pega Robotic Process Automation using OpenSpan has a very low adoption because it does not provide the flexibility that UiPath or Automation Anywhere offers. Pega RPA is most powerful when integrated with Pega BPM; as a standalone RPA tool, it lacks some advanced features found in competitors like UiPath or Automation Anywhere. While low-code, Pega Robot Studio can be complex for beginners, especially those without .NET or Windows automation experience. Primarily designed for Windows desktop applications; limited support for cross-platform or web-based automation compared to other RPA tools. Managing large bot fleets and ensuring version control, exception handling, and orchestration can become complex without mature DevOps practices.
Regarding the best features of Pega Robotic Process Automation, Seamlessly integrates with Pega’s BPM platform, enabling end-to-end automation that combines bots with human workflows, Supports both attended bots (assist agents in real time) and unattended bots (run background tasks without human input), Easily automates tasks across mainframes, desktop apps, and web systems without requiring APIs, supports on-premise, hybrid, and cloud-native deployments, including integration with Pega Cloud.
What needs improvement?
1. Enhanced Cross-Platform Support
Currently optimized for Windows-based applications. Needs better support for web, cloud-native, and non-Windows environments (e.g., Linux, macOS).
2. Simplified Development Experience
Pega Robot Studio has a steep learning curve, especially for non-developers. Could benefit from a more intuitive, drag-and-drop interface and prebuilt automation templates.
3. Stronger AI/ML Integration
Bots rely heavily on rule-based logic. Native integration with AI/ML models (e.g., for document understanding, sentiment analysis) could make bots smarter and more adaptive.
4. Improved Debugging & Testing Tools
Debugging complex automations can be time-consuming. Needs better simulation, logging, and error tracing tools for faster troubleshooting.
5. More Scalable Bot Orchestration
While Pega Robot Manager is powerful, managing large bot fleets can become complex. Could improve auto-scaling, load balancing, and dynamic resource allocation.
6. Broader Integration Ecosystem
Limited out-of-the-box connectors compared to competitors like UiPath. Expanding the integration library (e.g., for SaaS apps, APIs, databases) would reduce custom development.
7. Licensing Flexibility
Licensing can be cost-prohibitive for smaller teams or departments. More modular or usage-based pricing could improve adoption.
For how long have I used the solution?
I am using it for last 8 years
What do I think about the stability of the solution?
Concerning stability and scalability, Pega Robotic Process Automation is not that scalable.
What do I think about the scalability of the solution?
Pega Robotic Process Automation is not very scalable.
How are customer service and support?
Pega RPA is Windows-centric, and support for cross-platform automation is limited, which can be a challenge for diverse IT environments.
How would you rate customer service and support?
How was the initial setup?
Initial setup of Pega RPA can be complex and time-consuming, requiring skilled resources and sometimes additional support. Lack of a dedicated sandbox environment for training and testing, which can slow down onboarding.
What about the implementation team?
We implement by our own RPA team
What was our ROI?
We have seen 28–42% reduction in labor costs by automating repetitive, rule-based tasks. Automation helped eliminate manual errors, saving up to $1.2 million annually in error-related expenses. Process cycle times were reduced by 50–65%, significantly improving customer response and service delivery. Automated workflows maintained 75–79% efficiency even at 20x transaction volumes, outperforming manual processes.
What other advice do I have?
This review has a rating of 5 out of 10.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?