Info |
---|
Exceptions are used to handle specific actions outside of regular service hours within a queue. There are three types of exceptions: Exception, Exception when closed, and Emergency exception, each serving different purposes. |
Table of Contents |
---|
minLevel | 1 |
---|
maxLevel | 6 |
---|
outline | false |
---|
style | none |
---|
type | list |
---|
printable | true |
---|
|
Exception logic diagram
This diagram illustrates the process of call progression when a caller joins the queue. Initially, it will check for any emergency exceptions. If no emergencies are detected, it will then consider exceptions when open. In the event that your Queue/IVR contains such an exception, the caller will be notified and disconnected. Additionally, the service hours of the Queue will be verified. If the queue is operational, the caller will proceed as usual. However, if the queue is closed and uses an exception when closed, the Queue/IVR will be opened outside of regular service hours. If none of the above conditions apply, the queue is closed, leading to the disconnection of the caller.
Drawio |
---|
mVer | 2 |
---|
zoom | 1 |
---|
simple | 0 |
---|
zoominComment | 10 |
---|
inCommentcustContentId | 02892988427 |
---|
pageId | 2892595222 |
---|
custContentIdlbox | 28929884271 |
---|
diagramDisplayName | Untitled Diagram-1725870350885.drawio | lbox | 1 |
---|
contentVer | 1 |
---|
revision | 1 |
---|
baseUrl | https://benemen.atlassian.net/wiki |
---|
diagramName | Untitled Diagram-1725870350885.drawio |
---|
pCenter | 0 |
---|
width | 271 |
---|
links | |
---|
tbstyle | |
---|
height | 661 |
---|
|
...