Skip to main content

Logging a customer inquiry during an interaction

Suggest edit Updated on September 12, 2020

Associates convey information when interacting with customers. For example, an associate can remind customers when their next payment is due. You do not want to create a process for this, but you do want to capture the information conveyed to the customers.

  1. In the Retail User Portal, in the bottom right-hand corner, click Toggle runtime toolbar > Toggle Live UI and determine the section where you want to log information.
  2. Add a UI element in the section where you want to log the conveyed information.For example: Checkbox
  3. Click the Open property panel icon to configure the UI element.
  4. In the Cell Properties dialog box, click Change to modify the control type used.
  5. In the Custom section, click Other
  6. In the first field enter CPMHistory.
    The first field is named based on the name of the UI element that you have added in step-2.
  7. Click the Parameters tab and enter the field details.
    • FieldName - Type of the Field Value property to use. For example, pyMessageLabel, pyCaption, and pyHistoryMemo.
    • FieldValue - Value of the Field Value property to use.
    • PrintableFieldValue - Value that displays during chat interaction when a CSR selects the field.
    • ReasonFieldValue - In the Wrap Up, this option displays in the Reason for interaction list.
    • ToolTipFieldName - Type of Tool Tip Field Value property to use.
    • ToolTipFieldValue - Value of the Tool Tip Field Value property to use.
    • ToolTipFieldValueOnCheck - Value of Tool Tip Field Value property after a CSR selects the field and reviewed it.
  8. Click OK.
  9. Save your changes.
  • Previous topic Launching a service case from the composite
  • Next topic Implementing the security model and organization structure
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us