Pega Platform Reviews

Good for customer service to use instead of DOS like black screens, but bad for trying to train customer service (no sandbox environment, at least for us) since they can’t “completely” perform a task prior to going to a live environment. The knowledge is fairly good, except you can’t search the body of an article which is weird.

Pega may be very helpful if your company wants to move beyond just marketing automation and into integrating marketing with all internal processes. In our company we see marketing as more than just branding and advertising, but really as a way to facilitate great customer experiences. Pega works well if you share this vision. If you're only looking for a platform to run your advertising and campaigns than Pega may be too much for you.

I think Pega is an excellent platform for any transactional, repeatable task that is currently managed manually by agents needing to be automated.

Well suited for handling customer queries via service requests (which are called cases). These cases can be viewed/ worked upon at multiple stages by multiple teams before resolutions in Pega Platform.

Pega Platform will specifically come in handy and will be very useful if your business needs are to be dealing with a lot of data collection, in considerably large data completion forms. It is less appropriate in fulfilling some complex business needs like invoking APIs that are hosted by an external server. Or if the business needs to have a lot of mobile development.

If you need a good CRM for your customer service team to track customers interactions and you like to manage it without coding, it is a perfect option. It is very good for any case with multiple steps. For example, a bank, health insurance company, or auto insurance quote application.

I am using Pega to automate our desktop or web application. This is the perfect platform to scale the work on demand. The average developer can extend the functionality.

Pega is well suited for developing applications that manage fairly straightforward stages and steps based workflows. Complex workflows can be built but are more difficult to maintain and modernize, particularly when required to deviate from basic out of the box features and writing custom code. This risk is mitigated by experienced Pega architects setting and enforcing design practices.

It is highly recommended ats workflow/case lifecycle management systems. Customer Service, Claims processing, warranty support systems, etc.. It is highly recommended as an enterprise service bus for offering the services across different applications. Robotics are recommended for robotic processing.

Pega is very well suited to automate existing business process which requires a moderate amount of automation. A solution built with it can be deployed in quick time and since the learning curve is low, newbies can be easily integrated into the team to work on development. But specialist professionals are hard to come by when more advanced requirements are the need of the hour. The documentation is surprisingly sparse, pdn being the only primary reference.

Pega can be addressed as BPM engine, Thanks to its powerful integration mechanisms; with its vertical customization (Insurance, Claim, etc...), it allows a very positive experience in a more complex end-to-end experience. I think that Pega has to enforce its CRM features and CPQ.

A business friendly toolkit for defining applications. Unlike traditional BPM tools, there are much less complicated, technical syntax to handle in modelling processes and hardly any hard-coded programming. A well-trained business user can be trusted to create a business application from the PegaSystems BPM framework if desired.

Build a Banking Application where customers can check for loan, insurance status based on the loan numbers provided. Customers register with bank, login to the portal and search for the loan status. Create a portal for applying loan / insurance claim which is routed to manager for approval upon successful background verification. Once approved, email customers for notification. Invalid applications go to false claims table for rejection. Also create a portal for banking payments to other banks for existing customers via NEFT/IMPS

Pega is well Suited for

• Building business process applications which have assignments, routing and escalations.
• Best suited for customer care applications.

Less suited for

• applications which have the system of records in some other system (ie) For claims application the claims details has to be in pega, if the info has to be fetched from some other system it makes the application slow.

Best suited for:
1. Business Process Automation
2. Rules-based Decision Making
3. Managing middle-office/ back-office operations

Not suitable for: Customer facing application and management.

Our customers' businesses are with healthcare and insurance domains which have multiple business ends and all of them needs to connect to business processes in the end. Pega achieved this goal of designing them and now most of the processes are running on Pega Platform. It also replaced the existing manual intensive business processes.

Pega Platform is the best BPM tool with more modularity, scalability and best case management features. Very much suitable for Banking, health insurance, and Finance projects. The platform is used by analysts, developers and a number of other roles within a single Pega implementation project. The Pega product enhancements launched every year reduces a lot of customization. Pega is not suitable for Reporting type projects because reporting is not enhanced.

Pega is very well suited for projects with big user bases. It's not suitable when we need to hold large chunks of data for processing.

Pega is perfect to implement Process Management for any kind of company, by using each process as a case type, they all can be managed in one single system. This eliminates the need to maintain several systems in parallel.

Less time, robust code situations, good performance.

Process intensive systems can best use Pega. If there is a process, there can be Pega :)

It is very well suited for the workflow process and implementing business process across companies. It is not well suited for transaction-based processing.

Any application that requires some type of case management with approvals from a manager entity after a requester has submitted a case.

Pega Platform is well suited for web applications and quickly set up the workflows. Less appropriate for mobile as what we experienced so far.