(Automated save: adding PEC_Migrated template.) |
(Update with the copy of version: draft) |
||
| Line 9: | Line 9: | ||
|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= | + | |media1=ASStandardResponseOptions_GAPI21275.png |
}} | }} | ||
[[Category:V:PSAAS:Public]] | [[Category:V:PSAAS:Public]] | ||
Revision as of 17:35, July 16, 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.
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.
Comments or questions about this documentation? Contact us for support!