Call Scenarios and Applications
Outbound Call Management — Predictive
Dialing (Destination Busy and No Answer)
Customer | Agent |
|
|
| Agent |
Phone | Phone | Switch | Adjunct Processor | Terminal | |
B | A |
|
|
| A |
|
|
|
|
| Agent uses data |
|
|
|
|
| terminal to login |
|
|
|
|
| into application |
|
| Request Feature - Agent Login |
|
| |
| Agent logged into | (A, ACD Split) |
|
| |
| Request |
|
| ||
| ACD Split |
|
|
| |
|
|
|
|
| Agent ready to |
|
|
| Application initiates | receive calls | |
|
|
|
| ||
|
|
| 3rd Party Make Call |
|
|
|
| (dest=B, orig=ACD Split, return ack) |
|
| |
| Switch initiates |
|
| ||
|
| call | 3rd Party Make |
|
|
|
|
|
|
| |
Destination busy |
| Call Ended (cause=busy) |
|
| |
|
| Application saves number | |||
|
|
|
| ||
|
|
|
| to be called back after a | |
|
|
|
| few minutes |
|
|
|
| Application initiates |
| |
|
|
|
| ||
|
|
| 3rd Party Make Call |
|
|
|
|
| (dest=B, orig=ACD Split) |
|
|
Destination alerts | Switch initiates |
|
| ||
| call |
|
|
| |
|
| Alerting Event Report (B) |
|
| |
|
|
|
|
| |
|
| No answer |
| Application saves number | |
|
| Call Ended (cause=no answer) | |||
|
| to be called back after a | |||
|
|
|
| ||
|
|
|
| few hours |
|
The application in the adjunct processor requests Third Party Make Calls with the alert_dest_first, service circuit =
Note that the agent is not notified of calls that receive busy or are not answered. The application stores the call outcomes (for example, busy, no answer, SIT tone) for later call processing.
Issue 7 March 1998