eServices Manager Administrator's Guide

From Genesys Documentation
Jump to: navigation, search
This manual is for version Current of eServices Manager.


Search the table of all articles in this guide, listed in alphabetical order, to find the article you need.

Related documentation:

Article Description
Article Description
Create a Standard Response Create standard responses that agents can use as automatic replies to emails, chats, social engagement, and SMS.
Create and Insert Field Codes Learn how to create field codes and include them in your standard responses.
Create and test screening rules Create, manage, and test screening rules that you can use to screen messages.
Field Code Examples View examples of the use of field codes.
Field Code Variables Learn how you can use system variables, custom variables, and your own data in standard responses.
Field Codes Create a wide range of field code types, which you can use to customize the standard response sent to a particular customer.
Get started with eServices Manager Learn how to get started with eServices Manager.
Managing and working with objects Learn how to manage and work with eServices Manager objects such as categories, standard responses, field codes, and screening rules.
Plan and build a Category Tree Plan and build a category tree to provide the hierarchy for your standard responses.
Screening Rule reference View the functions, arguments, and regular expressions that you can use in screening rules, and how they operate to screen messages.
Screening rules Screening rules enable you to analyze messages so that you can decide how to handle them. This page describes screening rules and provides examples for common purposes.
Standard Responses Default responses, known as standard responses, enable you to send welcoming, helpful answers to frequently-submitted queries from customers.
Using Formulas in Field Codes View formula usage in field codes.

Retrieved from "https://all.docs.genesys.com/PEC-ES/Current/Administrator (2024-12-10 01:58:30)"
Comments or questions about this documentation? Contact us for support!