Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      


Updated on December 3, 2021

Mobile Messaging SDK architecture supports synchronous and asynchronous communication between CSRs and customers that use Android and iOS apps.

Pega Customer Service Implementation Guide

The following figure shows the Mobile Messaging SDK architecture and explains how the data interacts with multiple components when mobile app users and Pega Customer Service communicate.

Mobile Messaging SDK architecture
Mobile Messaging SDK architecture

Mobile Messaging SDK uses secure HTTPS connections to authenticate a user session, upload files, and download requests. After the system sets up the session, the system exchanges the subsequent real-time messages with a secure WebSocket connection by using the Pega Messaging API. The system uses encrypted local SQLite database instances to cache messages and the user session details locally on the device.


Pega Customer Service 8.7 Pega Customer Service for Communications 8.7 Pega Customer Service for Financial Services 8.7 Pega Customer Service for Healthcare 8.7 Pega Customer Service for Insurance 8.7

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us