What's new in Customer Journeys?

Connect and learn more! ×
Dispute functionality using Default Collector — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Dispute functionality using Default Collector

Received Response


We would like to test and understand whether business users will be able to raise disputes even for customers that are having profile class with only DEFAULT COLLECTOR who does not have any employee tagged to it

Content (please ensure you mask any confidential information):

Test 1 : We have an employee who is a collector. This user has both AR transactional as well as collection agent & collection manager roles. We created a transaction using this ID with customer who has only the "Default Collector" assigned at customer profile class level. After this, when we go and try to "Submit a Dispute" for that transaction, we are not able to do and it is greyed out. We believe this is due to customer belonging to this transaction has "Default Collector" without employee being tagged. Please correct if my understanding is correct.

Howdy, Stranger!

Log In

To view full details, sign in.


Don't have an account? Click here to get started!