Adobe Journey Optimizer is a customer engagement solution, enabling brands to orchestrate and deliver personalized customer engagement across all channels — including email, web, app, mobile, and more — in the moments that matter to customers.
N/A
Pypestream
Score 7.0 out of 10
N/A
Founded in 2015, Pypestream created the Customer Engagement Center (CEC), a conversational AI solution where the core product, the Customer Engagement Center (CEC), is an all-in-one, cloud-based suite of 12 components designed to transform any business into a fully automated digital brand. With headquarters in New York, Pypestream has a customer base that includes Shell, Chase, Procter & Gamble, Google, Sling, and HBO Max. Pypestream provides customer engagement in several key industries,…
AJO is best suited for advanced Martech teams who are already bought into the Adobe ecosystem through the use of RTCDP, AA, AAM, etc. Organizations that are starting their Martech journey are good candidates, as well as those who are reevaluating all of their marketing channel vendors near the same time. Success in AJO is highly dependent on the number of marketing channels added. Close coordination with database teams is essential for success. Many of the offline data requirements benefit from modeling of the data. Having dedicated resources developing AJO (RTCDP)-specific views will reduce the amount of QA required to bring the solutions to market
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.
At times, Adobe Journey Optimizer offers too many options, making things less user-friendly than I would personally prefer. As mentioned earlier, there is a tendency to encounter decision paralysis with the increase in available options. While having options is excellent, in typical Adobe fashion, too many can be overwhelming for users
They both have their pros and cons, I feel it depends on the users that the products are targetting, SFMC is has more specialized customizations, Adobe does offer similar but require a higher technical knowledge which is not something that is provided bt the other product
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.
Multichannel onboarding journey improving the engagement of freshmen in the business, resulting in a decrease in the dropout rate.
Separate business of anticipation of receivables from suppliers that used to be manual and now I have connected this entire operation via the S3 connector, less manual work and significant gains in conversions and payments
