Documente Academic
Documente Profesional
Documente Cultură
Contents: Predictive Dialers Answering Machine Detection (AMD) Traditional Dialers Answering Machine Detection (AMD) 3CLogics Implementation of V-TAG
3CLogic.com
White Papers
Predictive Dialers
A predictive dialer is used for automating the outbound dialing process in a call center. It increases the efficiency of the Call Center by preventing calls with busy signals, answering machines, fax machines, network messages, and no answers, from reaching agents. The predictive behavior results from multiple call attempts made by the dialer on behalf of agents available to handle calls. The number of calls dialed ahead by the dialer is forecast automatically by the dialer based on available agents and the average call handle duration. This process results in an increase in dial rates and agent productivity. The effectiveness of a predictive dialer is measured by its pacing ratio. The pacing ratio is the number of simultaneous calls outstanding per agent. For example, a pacing ratio if 2:1 means that for each available agent, the system will dial two calls. As these calls are made the dialer monitors each call and determines the outcome. The system strips out any unproductive outcomes, such as busy calls (these are usually queued for automatic redial), no answers & invalid numbers and routes only the good calls to available agents. Answering Machine Detection (AMD) Some predictive dialers incorporate answering machine detection, which tries to determine if a live person or answering machine picked up the phone. The system may automatically re-queue calls answered by answering machines or leave a message. If a human is detected, the dialer transfers the call to an available agent. Predictive dialers are usually implemented in specialized machines with extensive hardware. The machines are expensive to acquire and maintain and dont scale easily as more
agents are added in the call center or when it is necessary to increase the pacing ratio. System outages can cause large downtime for the call center. This is typically one of the reasons why most call centers are unable to go beyond a pacing ratio of 2. Another problem is the delay caused when connecting a call to a live agent. The system on which the dialer runs is typically an isolated system which may be deployed in the call center or hosted outside. A call which connects must be transferred to a live agent and this typically results in a delay or clicks heard by the called party. This taints the overall experience of the call as heard by the called party. When answering machine detection is running, this delay can be as much as 4 seconds before the call is transferred to an available agent. Traditional Dialers Most traditional predictive dialers rarely match their advertised performance levels. This is because the peak performance is reached when a lot of conditions are met and this can be hard in practice in a real call center environment. For example, if not enough calls are made ahead, agents will sit idle, whereas if there are too many calls made and there are not enough agents to handle them, then the call is typically dropped. A high level of performance may require a sufficiently large critical mass of agents. Conversely, it may be increasingly difficult to maintain a high talk time percentage with a lower number of agents without increasing dropped calls. A sophisticated system will need to manage calls more appropriately to deal with these situations. It will also need to use many operating characteristics that it learns during the calling process for each campaign. These statistics can be used to make important predictions to minimize agent idle time while controlling
3CLogic.com
White Papers
occurrences of nuisance calls. An advanced predictive dialer should be able to maintain the ratio of nuisance calls to answered calls at less than a fraction of one percent while still dialing ahead.
of client server is an FTP server where the client and server programs are quite distinct, and the clients initiate the download/uploads and the servers react to and satisfy these requests. An important goal in distributed networks is that all clients provide resources, including bandwidth, storage space, and computing power. Thus, as nodes arrive, and demand on the system increases, the total capacity of the system also increases. This is not true of client-server architecture with a fixed set of servers, in which adding more clients could mean slower data transfer for all users. The distributed nature of system or network also increases robustness in case of failures by replicating data over multiple systems by enabling PCs to find the data without relying on a centralized index server. In the latter case, there is no single point of failure in the
3CLogic.com
White Papers
system.
3CLogic.com