Jump to: navigation, search
(Automated save: adding PEC_Migrated template.)
(Modified comment string {{Template:PEC_Migrated}} with __NOINDEX__ {{Template:PEC_Migrated}})
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
= Standard Response options=
 
= Standard Response options=
  
 +
__NOINDEX__
 
{{Template:PEC_Migrated}}
 
{{Template:PEC_Migrated}}
  
Line 9: Line 10:
 
|title=
 
|title=
 
|text=You can format custom field codes to represent agent attributes using <tt>Agent.<CustomAgentAttr></tt>, or any custom attribute by dropping the agent modifier and using <tt><CustomFieldCode></tt>. Enter a '''Display Name''' and the corresponding '''Value''' for each field code.
 
|text=You can format custom field codes to represent agent attributes using <tt>Agent.<CustomAgentAttr></tt>, or any custom attribute by dropping the agent modifier and using <tt><CustomFieldCode></tt>. Enter a '''Display Name''' and the corresponding '''Value''' for each field code.
|media1=ASStandardResponseOptions.png
+
|media1=ASStandardResponseOptions_GAPI21275.png
 
}}
 
}}
 
[[Category:V:PSAAS:Public]]
 
[[Category:V:PSAAS:Public]]

Latest revision as of 12:32, October 2, 2020

Standard Response options

Important
This content may not be the latest Genesys Engage cloud content. To find the latest content, go to Genesys Engage cloud for Administrators.


In the Standard Response section, you can specify custom field codes, such as agent nicknames, roles, departments, and email signatures.


1

You can format custom field codes to represent agent attributes using Agent.<CustomAgentAttr>, or any custom attribute by dropping the agent modifier and using <CustomFieldCode>. Enter a Display Name and the corresponding Value for each field code.

This page was last edited on October 2, 2020, at 12:32.
Comments or questions about this documentation? Contact us for support!