Channel connection

When you approach your business architecture from the center out, it means that you're not starting top-down embedding logic in your channels or bottom-up embedding it in your systems. You're starting in the center with your customer, the outcomes that the customer wants to try to achieve, the Microjourney® that's going to connect the customer to that outcome. And you make that happen by adding a brain so that you can guide your agents and your customers through that process. You can apply rules and regulations. You can figure out the next best action in real time to drive the right outcomes for your customers and your business. And then, you use case management to actually drive and automate the processes that are involved and manage the customer context, so you know exactly where the customer is at every step of the journey. You do that by capturing the stages that you want that process to flow through. So you can both be transparent but also automate the work that's going to get the customer to the outcome they want.

And once you have that logic defined centrally, you then need to connect it up to your channels. Now, the fact that your brain is in the center means that you're going to have a consistent experience across your channels. If you make an offer to the customer and the contact center and they say no thank you, the brain can learn from that, so you don't actually hit them with it again via e-mail or on the web. And the case can maintain the state of a customer context. So if a customer starts a process up on the website and then calls in to the contact center, the case helps the agent pick up exactly where the customer was, so they don't have to reexplain themselves to the poor agent on the other side of the phone. So, you get great value in your channels from having your logic defined centrally.

But the way you connect that logic up to the channels matters. In some cases, that front end may just actually be Pega. We might use our user experience for front ends using what we call the Cosmos design system, where we're able to provide a rich design experience for end users, even for customers all built with low code. But in other cases, you may have user experiences that are built with other technologies. You may be using JavaScript technologies like Angular or react to build your website. You may have a Salesforce CRM front end. You may have Adobe Experience Manager that's managing part of your digital experiences for clients. And for those cases, Pega provides what we call the DX API. And what's important about the DX API or the Digital Experience API is that it's not static.

You see, when you have a static API that connects the decisions and your process up to your channels, you ultimately have to recode the process in the channel. So for every step in the process, I have to have a step in the channel with a screen across each step of the process. And if I make a change in the process, I have to go up and make a change in the channel. If I add a field to the process, I have to go rebuild the screen, and if I'm doing that across multiple channels, that can be really hard and expensive. That's one of the reasons why making changes in the channels is so complicated and so slow. What the DX API allows you to do is it actually allows the process in the case to inform the channel, to let it know exactly what fields are needed, exactly what step the process is on. And the way the DX API informs the channel if the case needs a new piece of information, if we change a step to add a field, or if we even add a new step or stage to the process, the case can inform the channel, and the channel almost magically adjusts. My logic stays centrally, but you still get the power to use the front end you want to deliver that experience. That's how you maintain your center of business logic, even across all of your channels.

A great example of a customer that did this is a Dutch bank called Rabobank. They use Pega to manage all of their commercial lending, and they do that both with users using Pega inside of Rabobank but also by providing front-end experiences on their digital channels, which are built using tools like Angular and react. Rabobank uses the DX API to expose the same processes that their internal users use out to their customers. And by engaging their customers in that process and applying a streamlined approach, they've actually been able to save $80 million a year in processing costs because their processes are more efficient and faster for the customer. A better customer experience, a more efficient process, and consistency across channels by using that Center-out™ architecture.

So once you've got your brain and your case connected up and into your channels, the next thing to do is connect that Center-out business logic back into your data.

You have reached the end of this video.