Pega Customer Decision Hub vs. Pypestream

PRPC is a BPM and Case management suite from Pega Systems. Pega is a comprehensive suite which offers a unique theme of BPM development in the market. A no-coding approach based on rules with inheritance makes Pega a very powerful product but is very difficult to learn. Even, if we go to Pegasystems for training, we have to work on a project at least for a year to have some confidence. Areas where it requires improvements: 1) One of the first things that client's IT department questions about is proprietary BLOB column in PRPC, for them, it is a disadvantage, but as we all know BLOB is what makes the highly complex data model of any BPM application fit inside to a common schema which eliminates the help of a DBA. 2) Another area of improvement is: when using the wizards to generate rules (such as the connector wizards) you have to be careful about the level of coupling between the work object's data model and the interface's data model. This can also create maintenance issues. 3) The complete Pega suite of products have a long time to develop and deploy and it can be easily done using other low-cost software.

Incentivized

Pypestream is suited for standard chatbot and conversational flows versus more multi-departmental scenarios. They do very well with guided flow bot services which are great for agent bots within a contact center, but less so for those implementations that have a large document management implementation for FAQs. They do well with service integrations; however, at times troubleshooting edge cases that are impacting performance and adoption can take a while to remedy. I want to believe that better monitoring tools on the platform side would alleviate this for them.

Incentivized

• Ability to design custom integrated campaigns
• Analytics to provide key insights and ability to tune your campaign accordingly
• Ability to design agent workflows

Incentivized

• Native live agent platform
• Managed services for service creation and maintenance
• Custom analytics

Incentivized

• Pega Customer Engagement Suite is ready to use out of the box with several features, but custom development is always needed.
• Although new features can be quickly implemented, they have to go through a screening Business analysis process, QA screening and SCRUM based development.
• Pega eliminates the need for custom code, but there are rare cases where an specific requirement has little to no support from Pega, and implementing custom code can break OOB functionality and make the system unstable.

Incentivized

• Generative AI - Large Language Model Support
• Standardized Reporting
• Custom UI Support
• Developer Tools

Incentivized

I explained in detail in previous questions.

In comparison to Microsoft Bot Framework or now Azure AI service structure, where Pypestream is better suited is in those organizations who want to truly have a partner in development. Pypestream allows the flexibility for your Dev teams to do it themselves, or to be in a managed service where you provide requirements and information and they build and allow you to test and give approvals. They are more willing to work directly with you versus a Microsoft where you will eventually get pushed off to a 3rd party partner to help with advanced implementations.

Incentivized

• Cost savings on print marketing and email due to better targeting
• More timely campaigns to reach customers at the right time

Incentivized

• Enabled the contact center business lane to grow a chat agent support channel that has a 2 to 1 (customer to agent) support ratio
• Provides an alternate channel for training, marketing information, and data services which help grow our business and support different value streams

Incentivized