Try our new research platform with insights from 80,000+ expert users
Nitin-Agarwal - PeerSpot reviewer
Delivery Manager (Intelligent Business Automation) - Pega at Persistent Systems
Real User
End-to-end solution that reduces duration of call times and ensures first time resolution of issues
Pros and Cons
  • "It also reduces the duration per call, and it ensures a first time resolution of the issue."
  • "For many of the clients, they have a separate system or separate layer of UI and a separate layer of the business rules engine, which Pega has taken care of in the recent releases."

What is our primary use case?

The Pega CRM use case is end-to-end. You have a customer center where people are reaching out for their self-service portal, self-service request, or some change requests in their account, or they want to check on their balance or different things. They reach out to a customer care executive and get authenticated during the call by using their account number, credit card number, debit card number, or their applicant number.

As soon as the executive receives the call, because it's an authenticated person, all the details are already popped up in the stream for that user, like the account information and personal information. Instead of browsing all 10 different systems, there would be a desktop that gets all the information from all the different upstream systems and downstream systems. Then they ask how they can help and create service cases and resolve them or proceed further.

In the transaction, if the person needs assistance, the call would get transferred to another person and all the details and data will also get transferred to the other person's desktop so they can take care of the request. This is all about one use case where we are basically orchestrating all the different systems into one system and making sure that all the information is presented on one page, which improves the efficiency and results in a good experience for the customer.

It also reduces the duration per call, and it ensures a first time resolution of the issue. In these kinds of use cases, there are many variances. In some places, like if it's a credit card company, they will get to know why you have called them and if it's related to some charges or something. Then out of your profile, they will get options from the system for the retention of customers. This happens mostly either in the banking industry or telecommunication industry where you have a phone or internet connection.

What needs improvement?

For many of the clients, they have a separate system or separate layer of UI and a separate layer of the business rules engine, which Pega has taken care of in the recent releases. The performance is also better. But developers should be properly trained so that the solution is developed properly.

For how long have I used the solution?

I have been using Pega for 16 years. Currently, I'm managing a Pega engagement.

What do I think about the stability of the solution?

It's very stable.

Buyer's Guide
Pega CRM
November 2024
Learn what your peers think about Pega CRM. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.

What do I think about the scalability of the solution?

It's scalable. If the designers have followed Pega's best practices, it is very scalable and there are no design issues.

How are customer service and support?

I would rate technical support 4.5 out of 5.

Which solution did I use previously and why did I switch?

I have been using Pega for the last 16 years, from the beginning of my career. I am familiar with solutions like Appian and OutSystems. But for enterprise-level solutions, Pega is the best.

How was the initial setup?

Since Pega has promoted cloud, it is not as cumbersome as it was earlier when we used to manage their servers in-house. If you want to use another cloud, then Pega will configure it on another cloud. It won't take that much effort, but it is much more secure and much more reliable.

Since Pega Deployment Manager came into picture, deployment is very easy. It won't take a lot of time. Based on the number of rules or size of deployment and how big the release is, it won't take more than a couple of hours or even less. It's very smooth. If you're deploying small packages, it's almost done in real time.

What was our ROI?

Pega claims that the ROI is 300%. People get ROI very early.

What other advice do I have?

I would rate this solution 9 out of 10.

The results are good from implementing this product. My advice is that you need to have a well-trained and experienced team. If you have that with a quick turn-around time and the requirements are clear, then you will see the magic.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
PeerSpot user
CEO with 1,001-5,000 employees
Vendor
First Look: Pegasystems Update 2013

Pegasystems had good years in 2011 and 2012 they say, with Q4 2012 being particularly strong and good results from their decision management products. They have over 2,000 employees as they go into their 30th year and are targeting $500M this year. Pegasystems maintains its focus on a platform business with a number of specific verticals although with an increasing focus on channels. They continue to leverage widespread frustration with IT and legacy software to focus customers on a new platform for technology-led innovation. Pegasystems is expanding and improving its channel partners – certified partner are up and a number of partners are beginning to sell directly with a number of large SIs taking the lead in growing a much larger partner pipeline. Pegasystems’ focus remains its integrated platform (BPM, Case Management, CRM, application development and Decision Management) across marketing, sales and service with a particular focus on companies that are moving to next best action. They continue to add industry applications outside their traditional industries (like manufacturing and CPG for instance) and deliver both on premise and in the cloud.

For 2013 they (again) want to make the product twice as easy to use and twice as fast to deploy – a constant challenge they set themselves. Social, mobile and case management are focus areas, combined with next best action everywhere. The mobile capabilities include a full app development platform that takes advantage of the rules in Pegasystems to better manage the user interface experience (location and device-aware). Solution-wise, Next Best Action Marketing and SFA were released in 2012 (adding to existing Customer Service options) as new solutions based on the stack taking advantage of next best action engine.

As far as Decision Management goes Pegasystems has spent the last couple of years truly integrating the old Chordiant decision management capabilities into the process/case management platform based on Pegarules. The decision strategy editor is now browser based and integrated with the rest of the Pega editors. Decision tables and decision trees from Pega have been retained and elements from the Chordiant product, like champion/challenger rules, added. The integrated environment supports 5 main decision rule types are:

  • Predictive Model rules (from Predictive Analytics Director or built externally)
  • Scorecard rules
  • Decision Strategies defined using the editor
  • Adaptive Models that learn while predicting
  • Interactions.

The Decision Strategy editor has been revised and allows a complete decision flow to be laid out with predictive models or adaptive models, decision tables or trees, champion/challenger etc. Strategies can be chained or drilled down into more detail. Every element has version control, security and access controls.

Decisions in process flows can be directly linked to a decision design in the Decision Strategy editor. Processes can also be flagged to capture responses to decisions made later in the process, potentially after a long time, and automatically feed these responses back into adaptive models.

Recent updates in Decision Strategy Manager since last year’s first release of a unified decisioning platform include support for large scale batch decisioning, increased PMML support, forecasting in Visual Business director and more advanced segmentation.

As noted Pegasystems has had success selling the new integrated Decision Management capability with a number of new wins in retail banking and other direct to consumer businesses such as TV and Telecommunications. One example customer (a telco) identified several benefits from the use of the Pegasystems Decision Management product including more relevance in offers (real-time context that includes customer intent, optimized logic across all potential actions including built in champion-challenger testing), more intelligence (handling business constraints such as service problems or busy call centers) and more control (real-time reporting and dashboard-based control of logic using Visual Business Director). This particular customer identified hundreds of millions in revenue from using the Pegasystems Decision Management product as well as a significant improvement in net promoter score each time new decision management capabilities were rolled out – more sales and an improvement in net promoter score thanks to more targeted, more personalized micro decisions. This use case, like most use cases for decision management, is focused on customer decisions but Pegasystems reports an increasing number of customers focused elsewhere such as incident severity and suitable responses to problems.

The unified Pegasystems platform:

  • The unified platform is based on a single enterprise repository (all cases being processed are managed in a unified case database also).
  • The base of the stack is a set of persistent object services that handle the object-relational mapping for the repository and cases.
  • Business rule services sit on top of these objects for handling user interface, forward and backward chaining etc.
  • Decision Management Services layer this with capabilities around predictive scorecards, decision trees and support for predictive models (both those built off-line and others using adaptive analytic technology).
  • Business Process Management Services can consume these decision management services and can be called by them.
  • Dynamic Case Management extends this set of capabilities to manage unstructured or dynamic processes and can also consume the decision management capabilities to guide case workers, for instance.
  • A layer of presentation capabilities supports various channels from portals to social and mobile.
  • Continuous improvement capabilities in terms of business activity monitoring etc wrap it up.
  • The system is available on the Cloud and can be licensed both on premise, on the cloud or in a hybrid deployments

The design environment remains browser based and a set of APIs for integration and event monitoring are available. Pegasystems’ domain-specific solutions use the stack and use cases include fraud detection, routing, escalation and case management tuning, automated approval across various industries.

One of the key elements of the Decision Management stack is Visual Business Director. This is now available as part of the Pegasystems platform and anything running on the Pegasystems platform can be instrumented for use in VBD. This allows process volumes and details to be presented alongside decision information for example. Sections of processes can be identified for simulation, allowing a change in decision making to be simulated in terms of its impact on a defined subset of the process than is executed as a consequence of the decision. What-if analysis can now include process implications of a change in decision-making.

Predictions and forecasts have also been extended. VBD could previously support back-testing, comparing a new strategy with what was seen in the past, and can now be used to simulate and forecast likely consequences of, for instance, outbound campaigns in terms of business results as well as call center loading and volumes. This uses projections from historical data.

Pegasystems’ Predictive Analytics Director is a capability for building predictive analytic models that supports the entire model creation process (though it is targeted more at business analysts rather than expert modelers) while Adaptive Decision Manager is for model tuning (and can automatically tune models built in Predictive Analytics Director as well as those brought in from a third party tool). ADM can also, and typically does, build models from scratch.

Since I last wrote about Predictive Analytics Director, they have improved the validation process by allowing a user to compare models based on various data sets at any point in model building and deployment. The final validation can be done against data never used in the modeling process and detailed reports generated. The process has been templatized so that projects can decide where they want to be on the default-settings to custom analytic project scale, supporting a wide range of potential users. Usability and visualization has been improved too but the major focus has been on integrating fully with the Pegasystems stack so that, for instance, all the model meta data is carrier forward to both document the model and support its automated monitoring and tuning.

Future plans reflect their focus on multi-channel solutions and include more sophistication in attribution (to allow adaptive models to correctly attribute what convinced a customer to the right channels) as well as support for managing the interaction history of a customer more centrally.

Pegasystems is one of the vendors in our Decision Management Systems Platform Technologies report and you can get more information on them here.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user259692 - PeerSpot reviewer
it_user259692Managing Director at a marketing services firm with 51-200 employees
Vendor

Very thorough and detailed review.