IVR 2.0/I call flow interface
Table
Application cell functions
Step | Description |
|
|
Cell 1 | The ANSW cell answers the incoming call. |
|
|
Cell 2 | The GDAT cell plays a prompt requesting the caller to |
| enter an account number. The number entered is |
| stored in the ACCOUNTNUMBER buffer. |
|
|
Cell 3 | The MENU cell plays a prompt instructing the caller to |
| press 1 to get an account balance, or press 2 to get an |
| account update. |
|
|
Cell 4 | When the caller presses “1” on the telephone, the COMI |
| cell starts the transaction. |
| According to the COMI cell parameters in Figure |
| the action template specified in the COMI cell |
| parameter window is “getbalance”. (This template is |
| used in the sample transaction described in Chapter 3: |
| Getting started, specifically Figure |
| The COMI cell provides the contents of the |
| ACCOUNTNUMBER buffer to the host computer |
| application. |
|
|
Cell 5 | According to the COMO cell parameters in Figure |
| on page |
| balance from the BALANCE buffer. |
|
|
Cell 6 | The contents of the BALANCE buffer is played to the |
| user. |
|
|
Cell | When the caller presses “2” on the telephone, an |
| account update is given because the application |
| communicates in a similar manner. |
|
|
Cell 10 | The caller hangs up and the application ends. |
|
|
If the caller hangs up before the transaction is completed, the COMA cell in the
Meridian IVR VT100 Gateway Development Guide Product release 2.0/I