From Bright Pattern Documentation
| Line 2: | Line 2: | ||
The logic of automated interaction processing is defined in [[contact-center-administrator-guide/ScenariosOverview|scenarios]]. Execution of a scenario with respect to a specific interaction is triggered by an interaction arrival at a specific ''access point'' (e.g., a phone number in the case of inbound calls, or a web page in the case of web chats). The logical entities that associate specific scenarios with access points are called ''scenario entries''. | The logic of automated interaction processing is defined in [[contact-center-administrator-guide/ScenariosOverview|scenarios]]. Execution of a scenario with respect to a specific interaction is triggered by an interaction arrival at a specific ''access point'' (e.g., a phone number in the case of inbound calls, or a web page in the case of web chats). The logical entities that associate specific scenarios with access points are called ''scenario entries''. | ||
| + | |||
| + | [[File:CCA-Scenario-Entries-Overview-53.PNG|800px|thumb|center|Scenario Entries overview]] | ||
| + | |||
| + | |||
| + | == Section Articles == | ||
The following is a list of configurable scenario entries found in this subbook: | The following is a list of configurable scenario entries found in this subbook: | ||
*[[contact-center-administrator-guide/ScenarioEntries/Dial-in | Dial-in]] | *[[contact-center-administrator-guide/ScenarioEntries/Dial-in | Dial-in]] | ||
Revision as of 17:42, 19 March 2019
Scenario Entries Overview
The logic of automated interaction processing is defined in scenarios. Execution of a scenario with respect to a specific interaction is triggered by an interaction arrival at a specific access point (e.g., a phone number in the case of inbound calls, or a web page in the case of web chats). The logical entities that associate specific scenarios with access points are called scenario entries.
Section Articles
The following is a list of configurable scenario entries found in this subbook: