Pega Customer Service design patterns
Portal:Customer Service Design Patterns /
Jump to navigation
Jump to search
Overview | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Overview | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
A program component that defines and implements an interface between an external application acting as a client, and a Pega Platform system acting as a server. An external system can send a request to a Pega Platform application and receive a response.
For example, the Pega Cloud Services SFTP service provides Pega Cloud clients with simple, secure file transfers to and from their Pega Cloud applications.
A digital medium through which users access your application. Depending on your business needs, you can set up various channels for the same application. For example, customers can access an application for booking flights through a browser-based web channel, or through a mobile channel that relies on a mobile app. In addition, you can also build a Facebook chatbot for customers who want to ask questions about their booking. At the same time, you can set up a second, more utilitarian web channel to accommodate professional users, such as travel agents. By making an application accessible over several channels, you can reach a wide variety of audiences, and provide each user group with the most appropriate content and user experience.