Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Manikandan Madhu (Manikandan M)
Tata Consultancy Services Limited

Tata Consultancy Services Limited
IN
Manikandan M Member since 2017 11 posts
Tata Consultancy Services Limited
Posted: Jan 2, 2024
Last activity: Jan 8, 2024
Posted: 2 Jan 2024 3:31 EST
Last activity: 8 Jan 2024 1:19 EST
Closed
Solved

Pega smart dispute and CS framework installation

Dear Team,

I would like to leverage web chat bot in SD work flow. Web chat bot(Digital messaging interface) can be installed with out customer service framework or Do I have to I install both smart dispute and customer service framework on base product?

 

Regards

Mani


***Edited by Moderator Rupashree to add Capability tags***
To see attachments, please log in.
Pega Customer Service for Financial Services 8.8
Chat and Messaging

Accepted Solution

Posted: 1 year ago
Updated: 1 year ago
Posted: 4 Jan 2024 2:18 EST
Updated: 16 Jan 2024 5:21 EST
Eswar Kumar Paravada (parav1)
PEGA
Principal Technical Support Engineer, Customer Service
Pegasystems Inc.
IN

@Manikandan M

Hi Mani ,

https://docs.pega.com/bundle/customer-service/page/customer-service/uikit-implementation/chat-messaging/digital-messaging.html

https://docs.pega.com/bundle/platform-88/page/platform/conversational-channels/configuring-digital-messaging-channel-security.html

you can go through this article (UI implementation or constellation implementation) webChatBot is installed with the pega customer service framework .

So on top of CS ,smart dispute framework needs to be present so that you can add the chatbot in the SD workflows.

Thank you

 

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice