WO1995014342A1 - Optimization of telephone outbound calling systems - Google Patents
Optimization of telephone outbound calling systems Download PDFInfo
- Publication number
- WO1995014342A1 WO1995014342A1 PCT/US1994/013027 US9413027W WO9514342A1 WO 1995014342 A1 WO1995014342 A1 WO 1995014342A1 US 9413027 W US9413027 W US 9413027W WO 9514342 A1 WO9514342 A1 WO 9514342A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- accounts
- contact
- individual
- probability
- campaign
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
- H04M3/5158—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing in combination with automated outdialling systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/22—Arrangements for supervision, monitoring or testing
- H04M3/36—Statistical metering, e.g. recording occasions when traffic exceeds capacity of trunks
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S379/00—Telephonic communications
- Y10S379/904—Auto-calling
Definitions
- the present invention relates generally to the fields of data processing and telecommunications and, more particularly, to a system for the optimization of telephone contact campaigns by increasing the probability that an attempt to contact a party will be successful.
- Telephone communication has become ubiquitous in contemporary society with the nearly universal availability of telephones.
- the telephone provides a fast and efficient means for contacting someone any time of day or night anywhere in the country or even the world.
- telephone communications only work if the person you are trying to contact answers the telephone. If that person is unavailable and the call is unanswered or someone else answers, the call is wasted.
- the caller has to either call again later or, if a message was left, wait for the person called to call back. In those situations where the person called is unlikely to receive the message or return the call, such as telemarketing or dunning delinquent debtors for debt collection purposes, establishing contact with the desired party in the first instance is often the only way to make a connection.
- automated outbound dialing systems are used to expedite the contacting of as many people as possible by telephone in a limited time period.
- a set of telephone numbers are normally selected from a database in the computer and downloaded directly into the automated dialer before the start of the work day.
- the automated dialer begins dialing and proceeds to take the appropriate action as the telephone calls are answered.
- the appropriate action usually consists of transferring the line to a human operator. Relevant information associated with the person called is displayed on a computer terminal viewed by the human operator and the operator responds by either conveying information to or obtaining information from the person contacted. The operator then "wraps up" the telephone call, making whatever entries are necessary on the computer terminal while viewing an account record on the computer terminal. In those cases where the telephone call is unanswered, a record of the unsuccessful attempt is made by the automated dialer.
- the personal records of delinquent debtors could be selected from the database of all customers and downloaded from a mainframe computer system to be dunned on a Tuesday morning.
- the delinquent debtors' telephone numbers would be downloaded directly into an automated dialer and, if the telephone call is answered, the line will be transferred to an operator viewing the debtor's credit history and other information.
- the operator speaks to the debtor or the debtor's spouse regarding the delinquency.
- the operator wraps up the telephone call by entering a record of the action on the computer terminal. A record of the call is made by the automated dialer, the account record is updated and the operator responds to the next call.
- Predictive dialer systems do not perform an analysis of relative call priority, times of increased likelihood of contacting the desired individuals and performance-based predictions of available resources. Contact attempts are essentially made randomly, without discriminating between low and high priority contact attempts. In addition, predictive dialers are unable to address staffing problems resulting in too few operators available during peak contact times while operators are either idle or wasting time on wrong party contacts during those times of day when the persons being called are unlikely to answer the telephone. These problems of wrong party contacts, unsorted and unsortable dialer- downloads and suboptimal staffing were simply not addressed until the invention of the campaign optimizer.
- the present invention addresses the problems of wrong party contacts and limited resources by scheduling individual call attempts to both maximize the likelihood of right party contacts and account for the distribution of available staffing resources throughout the day.
- Optimized campaigns reduce the number of wrong party contacts and, by predicting when telephone contact attempts are most likely to be successful and productive, provide guidance in beneficially employing the optimal number of human operators at the times of maximum probability of right party contacts.
- the present invention further provides guidance on distributing staff resources during the day so as to maximize the number of right party contacts per paid hour.
- Account records are stored in a database stored in a host computer, each of which is associated with an individual to be contacted. Although a single individual may be associated with one or more account records, the contact probability information for that individual remains consistent, irrespective of the number of accounts associated with that individual, because individual contact probability information is maintained separately from the account records.
- a set of accounts to be processed is selected for downloading from the host computer.
- Each account record includes information about the person to be contacted, including a unique identifier such as a social security number, as well as home and work telephone numbers and information relating to account selection criteria, campaign optimization and the information viewed by a human operator when the individual is contacted.
- the set of accounts selected for teleprocessing comprises a host- download.
- a host-download is essentially an unordered set of account records that normally include the telephone number where an individual associated with the account may be contacted. Prior to this invention, unoptimized host-downloads have simply been downloaded directly from the host computer system to an automated predictive dialer system for teleprocessing.
- the set of accounts selected for processing is downloaded from a host computer system to the campaign optimizer system.
- the account records of the host-download are sorted and relative teleprocessing priorities of the individual accounts are determined.
- the sorted and prioritized account records are then temporarily saved in a master campaign file from which the separate campaigns will be generated.
- a contact history database for each individual associated with the accounts is stored in the campaign optimizer system. This contact history database retains a record of all attempts, successful and unsuccessful, to contact the individuals associated with the accounts. These contact history records, in conjunction with demographic profiles reflecting predicted behavior, are used to determine the best time to call the targeted individuals based on the relative probability of contacting that individual (i.e., making a "right party contact”).
- a contact probability vector is constructed for each individual and the sorted and prioritized account records of the master campaign file are then merged with the associated contact probability vectors.
- the augmented accounts are then separated into optimized campaigns that essentially create a chronological schedule of attempts to contact the individuals at the time each targeted individual is most likely to answer the telephone, as long as there are dialer resources available to make the call at that time. If there are not enough dialer resources to attempt contact at the time of highest probability of contacting the right party, then the attempt is scheduled to be made at the time of next highest right party contact. High priority accounts are scheduled before low priority accounts to ensure that attempts to contact high priority accounts are made at the time of highest probability of right party contact.
- the optimized campaigns are of fixed durations, normally varying from one to four hours (half-day). Each optimized campaign is divided into dialer- downloads which are downloaded into one or more predictive dialers for teleprocessing.
- the actual telephone contact campaign begins when the predictive dialer begins making contact attempts, a contact attempt consisting of dialing the telephone number. If an attempt produces a "connect,” (i.e. the telephone is answered), then the line is transferred to an available operator for further processing.
- Relevant information associated with the account is displayed on a computer terminal viewed by an operator when the call is answered and transferred to the operator.
- the operator takes whatever action is appropriate, depending on the purpose of the call and whether a right party contact or wrong party contact has been made.
- a right party contact occurs if the targeted individual or a close relative of the targeted individual (i.e., spouse) answers the telephone or is persuaded to talk to the operator.
- a wrong party contact occurs if an answering machine or another individual answers the telephone and the targeted individual is unavailable or unwilling to speak to the operator.
- the operator then wraps up the call, inputting a report on the outcome of the attempt into the computer terminal.
- the account record and the contact history database are flagged for updating and the operator responds to another call.
- the campaign optimizer can reprocess campaigns for the remainder of the day, reassessing the probabilities of right party contacts and reassigning priorities. This midday recalculation provides an opportunity to accommodate changing circumstances (i.e. changed priorities because of external events), an opportunity to schedule second contact attempts for high priority accounts and a way to effectively compensate for staffing changes. For example, a targeted individual with a very high priority can be selected for subsequent attempts following an unsuccessful earlier attempt, despite low contact probabilities.
- the campaign optimizer can also generate staffing information that provides guidance as to the optimal number of operators needed for the remainder of that day's campaigns.
- the campaign optimizer system is not necessarily limited to telephone campaigns.
- the campaign optimizer could easily provide guidance for optimal door-to-door contact campaigns, providing rosters and associated addresses instead of dialer downloads. By refocusing the optimal contact analysis on days rather than hours and appropriately varying the definition of a successful or right party contact, the campaign optimizer could also be used to optimize a direct mail campaign.
- FIG. 1 is a schematic representation of a complete system configured in accordance with the principles of the invention.
- FIG. 2 is a schematic work flow diagram showing an overview of telephone contact campaign optimization.
- FIG. 3 is a flow chart diagram of an optimized telephone contact campaign.
- FIGs. 4a, 4b, and 4c are a flow chart diagram of the campaign optimization steps that occur in the campaign optimizer.
- FIG. 5a is a database schematic of an account record.
- FIG. 5b is a database schematic of a campaign list.
- FIG. 5c is a database schematic of a schedule statistics record.
- FIG. 5d is a database schematic of a schedule parameters record.
- FIG. 5e is a database schematic of an area code classification record.
- FIG. 5f is a database schematic of a credit risk parameters record.
- FIG. 6 is a flowchart showing the process of modified non- hierarchical cluster analysis used to create and select demographic profiles.
- FIG. 7 is a graph showing the bimodal behavioral model of contact probability.
- FIG. 1 schematically illustrates a preferred embodiment of the present invention.
- Host computer 10 maintains a database 80 of account records and selectively downloads a set of account records for teleprocessing to campaign optimizer 20.
- Campaign optimizer 20 may be operated on a UNIX workstation interfaced between host computer 10 and predictive dialer system 30.
- the relative processing priorities of the downloaded account records are assessed in campaign optimizer 20 and the account records are then grouped into priority bands corresponding to specified ranges of account processing priority values.
- the prioritized account records are sorted and merged with individual contact history records.
- the individual contact histories, in conjunction with demographic profiles, are used to generate telephone contact campaigns.
- Each telephone contact campaign comprises a chronologically ordered set of attempts to contact targeted individuals. The chronological order is based on a descending order of priority, the right party contact probabilities for each targeted individual and the availability of staffing resources on an hourly basis.
- Dialer-downloads are transmitted to predictive dialer system 30 for teleprocessing.
- Each dialer-download (comprising a single campaign) is designed to be run during a specific time interval.
- the number of accounts in each campaign is based on available resources, including the number of operators available for each predictive dialer during the time interval and the forecasted performance predictions, such as utilization, T gc (time spent by an operator talking and wrapping up a good (right party) contact) and T ng (time spent by an operator talking and wrapping up a no- good (wrong party) contact).
- the predictive dialer system attempts to contact the targeted individuals associated with the selected account records at the times determined by campaign optimizer 20.
- the telecommunication line is transferred from predictive dialer system 30 to one of local telephone operators arbitrarily labeled 50a - 50n. Associated with each of the operators is one of the computer terminals arbitrarily labeled 60a - 60n. Account information corresponding to the individual targeted at remote telephone 40 is displayed on computer terminal 6Qx associated with the operator at local telephone 50* which is connected to telephone 40. The operator determines if a wrong party contact or right party contact has been made and proceeds appropriately, generally by communicating the information displayed on computer terminal 60x if a right party contact was made. The operator then wraps up the attempt by recording the outcome of the contact on computer terminal 60-*:.
- results of the contact attempts are transmitted from computer terminals 60a - 60n and predictive dialer system 30 to campaign optimizer 20 where the results are used to update the contact history database stored therein. These results are also used to update account records in database 80 stored in host computer system 10 when necessary, such as when the telephone numbers have changed.
- Campaign optimizer 20 also generates staffing information 70 indicating the "ideal" number of operators for each campaign as well as reporting operating statistics.
- Staffing information 70 includes a recommendation based upon the performance predictions and is distinct from an optimized campaign in which the number of attempts to be made at any particular time is limited by the number of available predictive dialers and operators.
- the process of telephone contact campaign optimization begins when a set of accounts are transmitted from host computer system 10.
- the transmitted accounts (host-download) are translated into a useable format, if necessary, and input to the campaign optimizer at input stage 100.
- Standard UNIX utilities (such as ftp, cron and awk) are used to establish and maintain communications and perform needed file translation.
- the accounts of the host-download are processed into one or more campaigns at 110.
- the present invention uses software written in the C++ programming language with SQL extensions to perform the needed processing.
- the processing priority of the host-download accounts is determined in accordance with the processing priority parameters of campaign parameters 120.
- Campaign parameters may be uniquely varied for each campaign or workday and are input by a campaign administrator at 210.
- the accounts are also sorted by an identifier within the account record, (e.g., the social security number of the individual associated with the account) at 110.
- the data field "Person Identifier" represents the identifier in the present embodiment. Referring to Fig. 5a, Person Identifier is found in Person 620, Account 630, Call Likelihood 640, Attempt History 650, and Phone 660 and provides a link associating these disparate data elements to a targeted individual.
- Certain account records are characterized as "must attempt" records. These accounts are not necessarily prioritized and sorted in the same manner as the remainder of the records and are segregated at 110. The normally sorted and prioritized account records and the "must attempt" records are saved as master campaign file 140.
- the master campaign file 140 is an intermediate step in the campaign optimization process wherein relative prioritization has been established but chronological scheduling has not yet been performed. Chronological scheduling accounts for temporal variations in the likelihood of contacting the targeted individual that are represented by contact probability vectors 200.
- the individual contact probability vectors 200 are constructed from individual contact histories 130 and demographic profiles 160 at 180.
- Contact histories 130 reflect the outcome of previous attempts to contact a targeted individual that are maintained using predictive dialer 30 reports uploaded into the campaign optimizer at 170 and new or changed information downloaded from host computer system 10 at 190.
- Contact histories 130 may be maintained, for example, as two 6 X 24 arrays for each individual, each array recording contact attempts for six days of the week (Monday through Saturday). The first array represents a work telephone number and the second array represents a home telephone number.
- Demographic profiles provide data for those time intervals for which there is no contact history available, perhaps because no attempts to contact the targeted individual have been made at that time on that day.
- the demographic profiles represent expected behavior patterns generally indicative of right party contact probabilities. Sets of demographic profiles are maintained for each time zone, three sets of morning, midday and evening demographic profiles for home telephone numbers and three sets of morning, midday and evening demographic profiles for work telephone numbers.
- Contact probability vectors 200 are produced by processing the individual contact histories 130 along with selected demographic profiles 160 that most closely correspond to the individual contact history. Contact probability vectors 200 are normally produced or updated before the host- download preceding telephone contact campaigns. This is necessary to ensure that the required processing can be completed in a timely fashion so as to not delay commencement of a telephone contact campaign at the start of a workday. This is particularly important because of the high contact probabilities normally associated with early morning hours.
- the contact probability vectors 200 are merged with master campaign file 140 at 220 to create an augmented campaign file.
- the master campaign file 140 and probability vectors 200 file are both sorted on an identical identifier found in both files in the present embodiment, simplifying and accelerating the merger process.
- the augmented campaign file representing, for example, an entire day's worth of accounts to be contacted, is then converted into individual campaigns at 160.
- Individual campaign size is determined by available resources based on campaign parameters 120 and performance forecasts.
- the accounts are scheduled, in descending order of priority, for contact attempts at the time of highest contact probability for which dialer capacity exists at 160.
- the "must attempt" accounts are then scheduled for contact attempts. If there is no remaining available dialer capacity, a low priority contact attempt will be "bumped" from the day's campaigns to ensure that an attempt to contact the individual associated with the "must-attempt" account is made.
- Campaigns are then transformed into a format usable by predictive dialer system 30 (dialer- downloads) using UNIX utility awk and Oracle formatting utility sqlplus and distributed amongst the predictive dialers of the predictive dialer system 30 at 150.
- a series of campaigns for an entire workday may be constructed from the initial host-download received from host computer system 10.
- the campaign optimizer can also optimize campaigns for shorter and longer periods, including half of a work day.
- the campaign optimizer can receive campaign results from dialer-upload 170 and campaign parameters 210 before or during a midday break (lunch).
- the campaign optimizer can then reschedule the campaigns for the remainder of the day, accommodating unexpected resource changes (less operators or broken predictive dialers) and rescheduling high-priority attempts which resulted in wrong-party contacts in the morning.
- contact attempts may be removed from the schedule for a variety of reasons, including changed priorities or contact initiated by the targeted individual, thereby obviating the need for a repetitive contact.
- an operator may have been informed that a targeted individual will be available at a later time and it would be highly desirable to schedule a contact attempt at that time.
- Each campaign produced by the campaign optimizer represents an optimal utilization of available resources.
- the available resources and other relevant parameters (e.g., start and finish times) for each individual campaign are input by a campaign administrator at 210.
- These campaign parameters are accepted by the campaign optimizer and translated into a useable format at 210 and saved at campaign parameters 120.
- Campaign parameters are primarily maintained as tables designed to be configured by a campaign administrator manipulating the parameters through a graphic interface such as X- Windows at 210.
- the first table is the priority scoring table used to determine the relative weight of values used in determining processing priority of the accounts. Processing priority is initially assessed using numeric fields in the downloaded accounts. Every numeric field in a downloaded account may be used for determining processing priority and has a weighting factor in the priority scoring table. Each weighting factor is multiplied by the value of the corresponding field to compute the field priority value. Fields which are not used to determine priority are zero- weighted by entering a zero in the corresponding table entry. The individual account priority value used to assign priority is the sum of the weighted products.
- Fig. 5f schematically describes various data records used for determination of processing priority in the present embodiment.
- Data units credit risk parameter 730 and credit risk category 760 include fields for "Priority Scoring Weight.” These "Priority Scoring Weight” fields are used to determine the "Priority Scoring Value” in Credit Risk Code 750 and "Credit Risk Code” in Personal Credit Parameter 720.
- Other possible fields might be number of days delinquent and amount owed as well as a must attempt field. In a credit collections environment, these fields are generally indicative of the relative urgency of contacting an account.
- the priority scoring table may also have an entry for "must attempt" accounts, those accounts for which a contact attempt must be made, irrespective of contact improbability. These accounts are placed into campaigns wherever possible and will preempt other accounts if necessary because of resource limitations.
- the second parameter table is the hourly staffing table in which the number of operators staffing each predictive dialer supported by the campaign optimizer is entered.
- the hourly staffing table information is used in the determination of various campaign parameters, including the hours during which the campaigns will be conducted, the number of accounts in each campaign and the distribution of each campaign amongst the predictive dialers.
- the hourly staffing table may also be implemented as a two-dimensional matrix with each row representing an hour, each column representing a predictive dialer and the number of operators at that dialer at during that hour appearing at the intersection.
- Fig. 5d schematically displays some of the data structures used for the hourly staffing table in the present embodiment.
- the third parameter table is the external interfaces table used to interface with the various external elements, including the host computer and the predictive dialer system.
- the external interfaces table provides support for underlying communications and is not normally accessible through a graphics user interface. In the present embodiment, this table specifies device addresses, communication protocols, pass words and specific routines to invoke to handle communications.
- the fourth parameter table is the area code / time zone table.
- the data structures incorporated into the area code / time zone table of the present embodiment is shown in Fig. 5e.
- the campaign optimizer system operates in local time, the individuals associated with the various accounts do not necessarily live or work in the same time zone.
- the campaign optimizer takes this into account through the area code / time zone table which is used to translate between local time and the time where the telephone number of the account is located.
- the area code / time zone table also compensates for daylight savings time and holidays.
- the present embodiment handles holidays using Holiday Rule 710, associating Area Code 700 with the relevant state and nation.
- the local time, local holidays and whether and when daylight savings time is in effect, as maintained in Time Zone 690, are specified for each area code.
- the fifth parameter table is the smoothing parameter table which is used for performance forecasts and contact probability determination.
- the campaign optimizer performance forecasts are produced by exponential smoothing for each hour of the day and each day of the week and the smoothing parameter, which determines how heavily weighted recent observations are, is in the smoothing parameter table. Performance forecasts are some of the reports 70 that can be produced by the campaign optimizer.
- the smoothing parameter table also holds the confidence parameters used when calculating contact probability vectors for campaign optimization.
- the confidence parameter is a target number representing the number of attempts necessary to establish a reasonably reliable prediction of contact probability at a specified time.
- the sixth parameter table is the system work schedule which tells the campaign optimizer when to perform various activities including downloading accounts from host computer 10 at 100, uploading predictive dialer data to host computer system 10 at 170, and downloading optimized campaigns to the predictive dialer system 30 at 150.
- the system work schedule may be implemented as a UNIX cron file that triggers specified processes at the desired times.
- the seventh parameter table is the campaign length table.
- Campaigns may be as short as one hour in duration, although it is generally desirable to run longer campaigns because predictive dialers are inherently more efficient when running longer campaigns.
- the data elements of the campaign length table are described schematically in Fig. 5b, which also illustrates the organization and elements of dialer- downloads in Dialer Campaign List 670 and Call To Make 680.
- predictive dialer system 30 provides comprehensive reports of the results of all contact attempts to the campaign optimizer system at 170, where the predictive dialer reports are translated into a format readily used by the campaign optimizer by the UNIX utility awk as well as prepared for uploading to host computer system 10.
- the predictive dialer system report is transmitted to host computer system 10 for use in updating account records when necessary, such as when a telephone number has been disconnected or changed.
- the predictive dialer report is used within the campaign optimizer for contact history 130 updates and for performance predictions.
- the campaign optimizer can generate a variety of reports, performance forecasts and staffing projections at 250 in accordance with report requests input by a campaign administrator at 230 where the report requests are accepted and formatted. These reports, which may be, for example, printed, displayed on a video terminal, or simply archived, are available to a campaign administrator at 70.
- Fig. 3 illustrates the conduct of an optimized telephone contact campaign. An entire day's set of optimized telephone contact campaigns is downloaded to a predictive dialer system at the start of the day, before the first of the day's campaigns is scheduled to begin at step 300. The predictive dialer system then attempts to establish telephone communications with the targeted individuals (make "connects") by dialing each targeted individual's telephone number at step 310.
- the predictive dialer system determines whether there are contact attempts remaining at step 370. If there are, the predictive dialer system dials the next telephone number.
- account database 80 stored in host computer system 10 and contact history 130 are updated with information describing the results of the attempts and contacts from the campaign at step 380.
- demographic profiles 160 are updated with the results of the campaigns that have been run. Demographic profiles 160 are updated using aged contact history data from the results that are saved for demographic profile updating.
- performance reports 70 are generated for use in future performance forecasts and may also be displayed or printed if a report is requested.
- the discrete elements of campaign optimization that are performed by the campaign optimizer are shown in Fig. 4a, 4b and 4c.
- the accounts which will comprise the campaign must be received by the campaign optimizer.
- the campaign optimizer polls host computer 10 at 400 while waiting for a subset of accounts for teleprocessing to be downloaded. Communication with the host computer system is accomplished using, for example, 3770 SNA to communicate with a mainframe computer system.
- the host-download is input into the campaign optimizer at 410.
- the host-download file is translated into a format useable in the campaign optimizer at 420.
- this translation/filtration is accomplished through the UNIX pattern scanning and processing utility "awk.”
- the process of campaign optimization begins.
- the first step is a sequential sorting of the accounts by a unique identifier field which is found in each account record at step 430.
- the social security number of the individual associated with the account is utilized for the sorting. This sorting is a necessary prerequisite to the rapid merger of the account records with the associated contact probability vectors later in the process of campaign optimization.
- Some of the account records for teleprocessing may be characterized as "must attempt" accounts.
- An attempt to contact the individual associated with the account must be made during the day, but it considered less important whether or not the individual is actually contacted.
- the processing priorities for these individual are considered irrelevant and handled separately, although each account, "must attempt” or otherwise, does have a contact history and contact probability vector.
- the campaign optimizer ensures that an attempt is made to contact the individuals associated with the "must attempt” accounts by alternative processing that ensures an attempt is made without displacing high priority accounts.
- the "must attempt” accounts are also sorted, but they are temporarily stored in a separate file 450 at 440.
- the processing priority values for the remaining account records are determined at 460.
- the priority scoring weights from the priority scoring table 120 are associated with the account record fields.
- the processing priority values are generally determined by multiplying the numeric account record fields by the corresponding priority scoring weights from the priority scoring table of campaign parameters 120.
- the priority scoring table provides a method for assessing priority variably for each campaign, computing the relative priority importance of individual numeric fields in the account records by assigning a priority scoring weight of 0 (zero) to fields that are not used and high values (e.g., 999.999) to account record fields that are significant in determining priority.
- each account record is dependent upon the account record's priority band.
- Each prioritized account record is placed into a priority band.
- These priority bands comprise user-defined inclusive ranges of processing priority values. Accounts are placed into these priority bands to facilitate the inclusion of other statistical parameters such as hour to hour distribution skewedness and all accounts in a priority band are considered to have the same priority value.
- the number of priority bands is based upon a system constant. In the preferred embodiment of the present invention, nine priority bands are used.
- Each prioritized account record is assigned to a priority band according to the following equation which produces a band number, B, in the range [0 ... N-l].
- N is the number of priority bands
- n is the number of fields and each Value is capped by its respective UpperBound.
- a contact probability vector is a vector wherein each component of the vector represents the probability of a right-party contact during a specific time interval, presently one hour.
- the number of vector dimensions ideally co ⁇ esponds to the operating hours of the teleprocessing system and a separate vector is generated for each day of the week and Saturday.
- Contact probability vectors are computed from the individual contact histories and demographic profiles in a process which is described in detail below. Contact histories and demographic profiles are not maintained for Sundays in the present embodiment of the invention, although accounting for Sundays may be easily accomplished by appropriately altering the relevant data structures without altering the underlying procedures.
- New accounts and accounts with new telephone numbers in different time zones have empty contact histories and probability vectors are necessarily computed solely from demographic profiles.
- a determination is first made as to whether each account for teleprocessing is a new account at 470. If the account is a new account, then the account is flagged for subsequent processing after creating the optimized campaign list at 480. This subsequent processing involves the initialization of a contact history for the account. A probability vector for the new account is then created from the demographic profiles corresponding to the new account time zone with the largest associated population at 490.
- the new telephone number is analyzed to determine whether the contact history co ⁇ esponding to the old telephone number should be flagged for discard and the new telephone number flagged for creation of a new contact history, similar to new accounts, at 510.
- the new telephone number is analyzed to determine whether the new telephone number is in a different time zone than the original telephone number. If the new number has the same area code or a new area code within the same time zone, the original contact history may still be reliably used.
- the existing contact history for the account is purged, the account is flagged for subsequent processing at 480 and demographic profiles for the new time zone are used to construct a new contact probability vector as if the number were a new account at 490. If the new telephone number has the same area code or a new area code in the same time zone, the existing contact history is presumed accurate and is not purged.
- Contact probability vectors are generated for accounts with valid contact history data (i.e., unchanged accounts and changed accounts where the telephone number change does not alter the expected behavior of the targeted individual), from the contact history for the individual associated with the account and co ⁇ esponding demographic profiles at 520.
- Each of the account records is then augmented by a co ⁇ esponding contact probability vector at 530.
- the set of accounts with associated probability vectors are referred to as augmented accounts.
- the augmented accounts are then sorted by processing priority at 540.
- Accounts that have been designated as “must attempt” accounts are not necessarily scheduled for contact attempts at times of highest probability and are sorted behind all prioritized accounts. Therefore, "must-attempt" accounts are not prioritized in the same manner.
- the prioritized accounts (the accounts that are not “must-attempt” accounts) are then reorganized according to the relative contact priority of each account.
- the prioritized accounts which have already been placed into priority bands according to the previously determined processing priority value (based on weighted parameters), are then further prioritized according to secondary considerations.
- Time sensitivity accounts for both skewedness and the number of other individuals with simultaneous times of high contact probability. For example, most individuals have a high contact probability associated with the time interval between eight and nine o'clock in the morning. However, relatively few individuals have a high contact probability associated with the time interval between eleven and twelve o'clock. Time sensitivity also compensates for variations in bimodal behavior, such as those individuals with several time intervals of high contact probability distributed throughout the day.
- N the number of hours for which actual or inferred experience exists and P- is the contact probability for the i ⁇ hour.
- the variance, V is scaled by the reciprocal of the mean contact probability squared according to the following equation:
- V sa ⁇ ed The scaled variance, V sa ⁇ ed is inversely proportional to the relative
- Time sensitivity a consideration of how many other individuals share the same times of high contact probability, is relevant and can account for both bimodal and multimodal contact probability distributions.
- Time sensitivity is computed by considering peakedness in relation to teleprocessing capacity. For purposes of computing time sensitivity, peaks are computed by determining times of contact probability, P p ⁇ , where the contact probability, P is exceeds a parameterized probability as shown in the following equation.
- Pp etk Pi * ⁇ X * «*. &
- P is the probability of right party contact at the i ⁇ hour
- ⁇ is a scheduling parameter, set to 2 in the present embodiment
- P median is the median contact probability for the relevant time interval (i.e. morning, midday or evening).
- the value of ⁇ co ⁇ esponds to an assumption regarding the distinction between high and normal contact probabilities, presumed to be a doubling in probability in the present embodiment.
- H the number of hours with a contact probability of P peak , H, is then determined. It is then determined whether, for the preceding day, there were more accounts optimally placed at each hour of -P peak probability then there was available teleprocessing capacity.
- the total number of hours in which teleprocessing capacity was exceeded by campaign demands during the relevant time periods is represented by the variable 'O'.
- H is the number of hours with P peak contact probability
- O is the number of hours with P, ⁇ contact probability during which,in the co ⁇ esponding hour of the preceding business day, teleprocessing capacity was exceeded by individuals with highest contact probability at that hour
- P is a scheduling parameter that is set to 2 in the present embodiment.
- a master campaign list 560 is saved at 550.
- the master campaign list includes the "must attempt" accounts, although they are not prioritized.
- the resources available to conduct the campaign are computed at 570 based on both campaign parameters 120 and performance forecasts.
- the campaign parameters input by the campaign administrator at campaign parameters 120 provide information regarding physical resources available to conduct the campaign, including the number of predictive dialers and available operators. Performance forecasts based on standard predictive dialer reporting statistics such as average connect time, good and bad contact connect times, wrap up times and the relative efficiency of operator utilization are incorporated into the processing.
- the maximum size of each campaign i.e, the number of accounts which may be effectively handled during the selected time interval
- the augmented and prioritized accounts (not including the "must attempt" accounts) are scheduled for contact attempts in descending order of priority at 560.
- An account is scheduled for an attempt to be made during the time interval of maximum right contact probability if there are resources available to make an attempt during that time interval. If there are no available resources, (i.e. all the operators on all the dialers are predicted to be fully occupied), then the attempt is scheduled to be made during the time interval of highest right contact probability when resources are available.
- the accounts with "must attempt" priority are then scheduled for attempts to be made at whatever times there are resources available for an attempt. If there are not enough available resources remaining to attempt to contact each "must attempt" priority account then the lowest priority accounts will be
- each campaign includes the contact attempts to be made during the campaign time interval, usually one hour.
- the contact attempts are distributed into separate dialer- downloads for each predictive dialer at 600.
- the size of each separate dialer-download is calculated so that an attempt will be made to contact every account in the dialer download during the campaign time interval. These dialer capacity calculations are based on performance predictions coupled with the available resources.
- the dialer-downloads are then translated, if necessary, and downloaded to the predictive dialer system for teleprocessing at 610.
- Information on every telephone attempt made during the day (or morning, if midday recalculation is being performed) is extracted from the predictive dialer system and used to update the contact history database at regular intervals, normally nightly. For each account record updated, the number of observations (attempts) is examined. For each hour of each day of the week, a determination is made as to whether the contact history contains enough data to determine the probability of a right party contact with sufficient confidence. The number of observations is a measure of confidence that the measured probability (number of successful attempts ⁇ number of attempts) closely approximates the actual probability. If the number of observations is less than a target confidence value, values for attempts and good contacts are aggregated across the same hour for the remaining weekdays.
- Processing is performed in the above manner until all hours for all days of the week have been processed. Unless there have been a sufficient number of observed contact attempts to create an adequate contact history, a demographic profile is then selected for the account and used to supplement the observed attempts of the contact history.
- the demographic profiles represent categories of behavior for the individuals targeted to be contacted with the behavior being modeled the likelihood that a phone call attempt will generate a right party contact.
- the demographic profiles are lists that for each one hour period specify the probability of an attempt resulting in a right party contact.
- Demographic profiles fill in missing data by providing data for hours for which no actual data exists for an individual and for smoothing actual result data. Selection of a viable demographic profile for an individual requires consideration of how to establish starting profiles and how to match a profile with an individual. Starting profiles must be established in the cluster analysis program, and the quality of the starting profiles affects the quality of the profiles produced and the speed of convergence.
- a portion of a demographic profile for a weekday may be thought of as shown in the following table.
- Creating viable demographic profiles begins with constructing a model of behavior which both assists in constructing the starting profiles and helps extract the maximum value from each attempt.
- the model of behavior in the present embodiment assumes that the basic contact probability curve for an individual is bimodal as shown in Figure 7.
- the basic shape of the contact curve is the same for either home or work telephone numbers.
- the shape of the contact curve for a home telephone number results from the assumption that most people are at home for some period in the morning, leave for an extended period of time and then return home, where they remain for an extended period.
- Different starting profiles reflect variations in the time for the beginning and end of the midday low-probability period.
- For work telephone numbers there tend to be periods in the early part of the day when contact probability is relatively high. Most individuals are getting ready for the business day and tend to answer their own phones, whereas the middle part of the day tends to be filled with meetings, lunch, etc., which significantly reduce the likelihood of a right party contact.
- the contact profiles for work telephone numbers are differentiated by the hours at which the high probability periods of high right contact probability begin and end. Demographic profiles are not just divided between home and work telephone numbers. The demographic profiles are also divided into three periods of the day: morning, from 8:00 a.m. to 12:00 p.m.; afternoon, from 12:01 to 5:00 p.m.; and evening, from 5:01 to 9:00 p.m. This trifurcation reflects the implicit assumption that an attempt result in any one period is relatively uninfo ⁇ native as to expected behavior in the other periods.
- Determination of the co ⁇ ect profile for an individual requires separate examination of morning, midday and evening contact data. For each separate period, the demographic profile with the minimum of the sum of the squares of the differences between the demographic profile and the probability vector components co ⁇ esponding to the profile time period is selected as shown below.
- M- is the aggregated contact probability for the i th hour for a targeted individual
- P j j is the right party contact probability for the i lh hour of .the j ⁇ profile and n is the number of hours.
- a positive contact at 9:03 a.m. implies a high contact probability during the preceding hour between 8:00 and 9:00 a.m.
- Demographic profiles are created from contact probability vectors reflecting the contact histories with the most data on the implicit assumption that past behavior, on average, is representative of the average behavior of newer accounts in the same environment and are created for each time zone encompassed by a campaign.
- Demographic profiles are created by reiterative processing of the available data set until the best set of categories for the data is produced through modified non-hierarchical cluster analysis. This technique is illustrated schematically in Fig. 6. Both the number and details of the starting vectors for the cluster analysis, known as centroids, are based upon the initial behavioral model.
- Each row of Tables 4, 5 and 6 above represents a possible starting vector in the present embodiment.
- For each contact probability vector it is necessary to determine to which cluster the vector should be assigned for processing.
- Each probability vector is assigned to the cluster with which there is the minimum n-space distance between the vector and the centroid of the cluster.
- Once vectors have been assigned to clusters the centroids are recalculated and the components of each vector are averaged, ignoring the NA components. This process is repeated until new clusters are no longer produced by the centroid recalculation. The number of contact histories in a given cluster is thus the population associated with that cluster's centroid.
- a pseudo-code implementation of the non-hierarchical cluster analysis by which demographic profiles are created is shown in the following tables wherein the variables are defined as follows.
- CENTROID (K,M) is a K X M array of real values representing the centroids of the clusters.
- K is an integer representing the number of clusters.
- M is an integer representing the number of time periods used, for example there are four time periods used for cluster analysis of the morning period.
- PROBABILITY (N,M) is a N X M a ⁇ ay of real values representing the probability vectors of the individuals to be clustered.
- N is an integer representing the number of individuals to be clustered. N may be the entire database of records from the host computer for which contact histories have been maintained or it may be a statistically valid subset, perhaps one to five thousand records.
- ASSIGNMENT (N) is a one dimensional a ⁇ ay of integer values representing which cluster each of N individuals is associated with (assigned to).
- I, J, and P are integer variables that provide loop indices of the
- BESTDIST is a real value representing the best sum of the squares distance found at that point.
- BESTP is an integer value representing an index co ⁇ esponding to the cluster with the smallest n-space distance (calculated by sum of the squares) from an individual.
- SUMOFSQS is a real value representing the sum of the squares distance between a cluster and an individual.
- KOUNT (K,M) is a K X M a ⁇ ay of integers representing the number of individuals clustered around a centroid.
- FLAG is an integer value that is set if any new clusters have been generated by the last iteration of clustering and centroid recalculation.
- KK is an integer value that is used in the reassignment of individuals to new clusters and cluster processing when new clusters are produced.
- the next table shows a pseudocode implementation of the first stage in which the individual contact probability vectors, which may have N/A entries, are clustered around specified starting centroids as shown at 810. As stated, the starting centroids specified will reinforce the behavioral model of individuals to be contacted using the campaign optimizer.
- centroids resulting from the first pass are calculated at 820 as shown in the following table. Table 9. Calculate centroids
- centroid calculation and cluster analysis 830 is repeated until no additional clusters result 840 from the centroid recalculations. It is also possible terminate the iterative cluster analysis and centroid recalculation after a specified number of iterations where processing conditions require faster processing.
- the iterative process of cluster analysis and centroid recalculation is demonstrated in the following pseudocode.
- the matrices PROBABILITY (I, J) and ASSIGNMENT (I) for all values of I and J and the matrices CENTROID (P, J) for all values of P and J are stored in the campaign optimizer and demographic profile generation is stopped at 850.
- New demographic profiles are only created (or existing demographic profiles modified) after a sufficient number of contact histories have been updated through normal campaign operations to provide a statistically significant variation in the data set (i.e., either the same contact histories with less data or significantly less contact histories) used to previously generate the demographic profiles.
- demographic profiles are generated at monthly intervals. Once a demographic profile is selected, the selected demographic profile is combined with the aggregated contact data, taking into consideration that individual data always takes precedence over demographic data. Because the number of individual observations is generally very small, a weighted blending produces better results than merely considering individual observations when available.
- a weighted blending of the probabilities in the contact probability vector with those in the selected demographic profile is made using a modified exponential smoothing in accordance with the following equation:
- V (ill x + S x n (9) n n
- Vj is the i ⁇ aggregated probability vector component used in all best-time-to-call calculations
- P ; the i ⁇ probability vector component ⁇ real customer data ⁇
- Dj is the i ⁇ probability vector component for the demographic profile
- n is the number of measurements (data points for this hour);
- « is a smoothing parameter, generally » 0.375.
- V- is set equal to D-.
- the probability vector component for the individual is set to the co ⁇ esponding value in the demographic profile without any exponential smoothing.
- the value of the smoothing parameter, « is decided on the basis of the two criteria.
- K is the number of attempts without right party contact.
- D ⁇ - is approximately 0.6 and the value for D i(min) is approximately 0.1 in the present embodiment. Therefore, the value for oc is determined by solving the equations 10 and 11 for o as shown below.
- the demographic profile selected for the contact probability vector is the demographic profile with the minimum sum of the squares of the differences between the demographic profile and the probability vector components determined from the contact history. The values from the selected demographic profile are used to fill out the undetermined values for the complete probability vector. These complete contact probability vectors are then used to augment the associated accounts in the master campaign file.
- the optimized telephone contact campaign is conducted by the predictive dialer system and the operators with computer terminals. A record of each attempt and the result thereof is maintained by the predictive dialer system. These result records are used by the campaign optimizer computer system to maintain the contact histories and demographic profiles. Contact histories and contact probability vectors are updated after each day's campaigns have been completed so the computations for the next day's campaigns and the performance forecasts are made using the most cu ⁇ ent data. After the contact phase of an optimized telephone contact campaign it is necessary to update the individual contact histories and recompute the contact probability vectors for each telephone number. This update occurs before generating a subsequent optimized telephone contact campaign so the new information will be used in determining contact probabilities for the next campaign, particularly when aggregating contact attempts across the days of a week.
- FIG. 5a is a database schematic showing a complete account record and the relations between telephone numbers, accounts and contact histories.
- Person 620 represents the individual associated with one or more accounts represented by 630.
- contact probability vectors Call Likelihood 640, contact histories, Attempt History 650, corresponding to each telephone number associated with the individual, Phone 660.
- FIG. 5b is a database schematic of a campaign -list, showing the structure of a telephone contact campaign.
- FIG. 5c is a database schematic of a schedule statistics record showing the records and fields used in the performance forecasting.
- FIG. 5d is a database schematic of a schedule parameters record illustrating storage of campaign parameters.
- FIG. 5e is a database schematic of the data structures used in conjunction with the area code / time zone parameter table of campaign parameters 120.
- FIG. 5f is a database schematic of a credit risk parameters data structure used for initial prioritization of accounts into priority bands in a debt collections environment.
- the campaign optimizer system also provides guidance as to optimal staffing levels by determining the "ideal" number of operators for a campaign, as opposed to the actual number of operators used when optimizing the campaign.
- a campaign which has been previously downloaded is optimized in a manner similar to that used for telephone contact campaign optimization.
- the optimal time interval to contact each account is determined.
- a hypothetical schedule is created and the number of accounts to be contacted during each time interval is determined.
- the optimal staff level is determined by solving equation 7 for S, the optimal number of operators, as follows.
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU11764/95A AU1176495A (en) | 1993-11-16 | 1994-11-14 | Optimization of telephone outbound calling systems |
EP95902527A EP0729683A1 (en) | 1993-11-16 | 1994-11-14 | Optimization of telephone outbound calling systems |
CA002176816A CA2176816C (en) | 1993-11-16 | 1994-11-14 | Optimization of telephone outbound calling systems |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US08/152,060 US5436965A (en) | 1993-11-16 | 1993-11-16 | Method and system for optimization of telephone contact campaigns |
US08/152,060 | 1993-11-16 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO1995014342A1 true WO1995014342A1 (en) | 1995-05-26 |
Family
ID=22541370
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US1994/013027 WO1995014342A1 (en) | 1993-11-16 | 1994-11-14 | Optimization of telephone outbound calling systems |
Country Status (5)
Country | Link |
---|---|
US (3) | US5436965A (en) |
EP (1) | EP0729683A1 (en) |
AU (1) | AU1176495A (en) |
CA (1) | CA2176816C (en) |
WO (1) | WO1995014342A1 (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1996038971A1 (en) * | 1995-06-01 | 1996-12-05 | Harris Corporation | Computer calling method and system |
EP0874508A1 (en) * | 1997-04-18 | 1998-10-28 | Harris Corporation | Communication system to provide called party location and pre-call warning |
NL1006371C2 (en) * | 1997-06-20 | 1998-12-22 | Koninkl Kpn Nv | Apparatus and method for testing the accessibility of at least one user of a telecommunication network. |
WO2000036811A1 (en) * | 1998-12-18 | 2000-06-22 | Blake Rice | Automated right-party contact telephone system |
WO2009086244A1 (en) * | 2007-12-27 | 2009-07-09 | Genesys Telecommunications Laboratories, Inc. | Apparatus and methods incorporating presence dynamics |
Families Citing this family (256)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5594790A (en) * | 1993-01-14 | 1997-01-14 | Davox Corporation | Method for selecting and controlling the automatic dialing of a call record campaign |
US6385312B1 (en) | 1993-02-22 | 2002-05-07 | Murex Securities, Ltd. | Automatic routing and information system for telephonic services |
US5436965A (en) * | 1993-11-16 | 1995-07-25 | Automated Systems And Programming, Inc. | Method and system for optimization of telephone contact campaigns |
US5592543A (en) * | 1994-06-01 | 1997-01-07 | Davox Corporation | Method and system for allocating agent resources to a telephone call campaign |
US5559867A (en) * | 1994-06-20 | 1996-09-24 | Sigma/Micro Corporation | Automated calling system with database updating |
US5594791A (en) * | 1994-10-05 | 1997-01-14 | Inventions, Inc. | Method and apparatus for providing result-oriented customer service |
US5907601A (en) * | 1995-05-26 | 1999-05-25 | Eis International Inc. | Call pacing method |
US5640445A (en) * | 1995-05-26 | 1997-06-17 | Eis International, Inc | Outbound call pacing method which statistically matches the number of calls dialed to the number of available operators |
US5742674A (en) * | 1995-12-22 | 1998-04-21 | At&T Corp. | Automatic call-back system and method using data indicating best time to call |
US5802161A (en) * | 1996-03-22 | 1998-09-01 | Austin Logistics Inc. | Method and system for optimized scheduling |
US6324274B1 (en) * | 1996-03-29 | 2001-11-27 | British Telecommunications Public Limited Company | Method and system for managing a user profile for use in a personal number service |
US5901214A (en) | 1996-06-10 | 1999-05-04 | Murex Securities, Ltd. | One number intelligent call processing system |
KR100222783B1 (en) * | 1996-06-27 | 1999-10-01 | 윤종용 | Line call handling method in a switching system |
US5953393A (en) * | 1996-07-15 | 1999-09-14 | At&T Corp. | Personal telephone agent |
US5943410A (en) * | 1996-08-02 | 1999-08-24 | Siemens Information And Communications Networks, Inc. | Automated calling of multiple numbers using directory assistance |
US5822400A (en) * | 1996-08-19 | 1998-10-13 | Davox Corporation | Call record scheduling system and method |
US5796791A (en) * | 1996-10-15 | 1998-08-18 | Intervoice Limited Partnership | Network based predictive dialing |
US5818920A (en) * | 1996-12-04 | 1998-10-06 | Telefonaktiebolaget Lm Ericsson | Apparatus for controlling communication connections based on local time |
US5896448A (en) * | 1996-12-17 | 1999-04-20 | Bellsouth Corporation | Method and apparatus for routing calls based on call success history |
US6044146A (en) * | 1998-02-17 | 2000-03-28 | Genesys Telecommunications Laboratories, Inc. | Method and apparatus for call distribution and override with priority |
US6480600B1 (en) | 1997-02-10 | 2002-11-12 | Genesys Telecommunications Laboratories, Inc. | Call and data correspondence in a call-in center employing virtual restructuring for computer telephony integrated functionality |
US6104802A (en) | 1997-02-10 | 2000-08-15 | Genesys Telecommunications Laboratories, Inc. | In-band signaling for routing |
US7031442B1 (en) | 1997-02-10 | 2006-04-18 | Genesys Telecommunications Laboratories, Inc. | Methods and apparatus for personal routing in computer-simulated telephony |
US5881138A (en) * | 1997-04-27 | 1999-03-09 | Ameritech Corporation | Method and system for detecting a change in at least one telecommunication service rate plan |
US6498840B2 (en) * | 1997-04-25 | 2002-12-24 | Ameritech Corporation | Method and system for generating a billing record |
US6239719B1 (en) * | 1997-06-03 | 2001-05-29 | At&T Wireless Services, Inc. | Method for time-stamping a message based on a recipient location |
US6711611B2 (en) | 1998-09-11 | 2004-03-23 | Genesis Telecommunications Laboratories, Inc. | Method and apparatus for data-linking a mobile knowledge worker to home communication-center infrastructure |
US6985943B2 (en) | 1998-09-11 | 2006-01-10 | Genesys Telecommunications Laboratories, Inc. | Method and apparatus for extended management of state and interaction of a remote knowledge worker from a contact center |
US6198814B1 (en) | 1997-10-17 | 2001-03-06 | Debra Ann Marie Gill | System and method for entering call outcome records in a computer database in an outbound predictive dialing application |
US6954529B2 (en) * | 1997-10-17 | 2005-10-11 | Debra Ann Marie Gill | Recordal of call results in a predictive dialing application |
US5991395A (en) * | 1997-11-04 | 1999-11-23 | Genesys Telecommunications Laboratories, Inc. | Implementation of call-center outbound dialing capability at a telephony network level |
US5991393A (en) * | 1997-11-04 | 1999-11-23 | Genesys Telecommunicaitons, Laboratories, Inc. | Method for telephony call blending |
USRE46528E1 (en) | 1997-11-14 | 2017-08-29 | Genesys Telecommunications Laboratories, Inc. | Implementation of call-center outbound dialing capability at a telephony network level |
GB9725347D0 (en) * | 1997-11-28 | 1998-01-28 | Ncr Int Inc | Database relationship analysis and strategy implementation tool |
WO1999033249A1 (en) * | 1997-12-19 | 1999-07-01 | Blake Rice | Automated right-party contact telephone system |
US6621900B1 (en) * | 1997-12-19 | 2003-09-16 | Blake Rice | Automated right-party contact telephone system |
US6278776B1 (en) * | 1997-12-22 | 2001-08-21 | Ser Solutions | Outbound switch pacing |
US6115462A (en) * | 1998-01-09 | 2000-09-05 | Gte Laboratories Incorporated | Method and apparatus for efficient call routing |
US7268700B1 (en) | 1998-01-27 | 2007-09-11 | Hoffberg Steven M | Mobile communication device |
US7907598B2 (en) | 1998-02-17 | 2011-03-15 | Genesys Telecommunication Laboratories, Inc. | Method for implementing and executing communication center routing strategies represented in extensible markup language |
US6332154B2 (en) | 1998-09-11 | 2001-12-18 | Genesys Telecommunications Laboratories, Inc. | Method and apparatus for providing media-independent self-help modules within a multimedia communication-center customer interface |
KR20010041388A (en) | 1998-02-27 | 2001-05-15 | 인게이지 테크놀로지스 | System and method for building user profiles |
US7318046B1 (en) | 1998-03-05 | 2008-01-08 | American Management Systems, Inc. | Collector's account payment promise option advisory apparatus and method |
US6278777B1 (en) | 1998-03-12 | 2001-08-21 | Ser Solutions, Inc. | System for managing agent assignments background of the invention |
US6879674B2 (en) * | 1998-04-09 | 2005-04-12 | Cim Ltd. | System and method for providing an automatic telephone call back to a telephone line being used to access a computer network |
US6373938B1 (en) * | 1998-04-15 | 2002-04-16 | Hanover Communications | Device and method for generating a list of qualified call recipients |
US6366667B1 (en) * | 1998-04-15 | 2002-04-02 | Hanover Communications | System for generating a list of qualified call recipients |
WO2000008539A1 (en) * | 1998-08-03 | 2000-02-17 | Fish Robert D | Self-evolving database and method of using same |
US6067348A (en) * | 1998-08-04 | 2000-05-23 | Universal Services, Inc. | Outbound message personalization |
US6792082B1 (en) * | 1998-09-11 | 2004-09-14 | Comverse Ltd. | Voice mail system with personal assistant provisioning |
USRE46153E1 (en) | 1998-09-11 | 2016-09-20 | Genesys Telecommunications Laboratories, Inc. | Method and apparatus enabling voice-based management of state and interaction of a remote knowledge worker in a contact center environment |
US7302051B1 (en) | 1998-09-28 | 2007-11-27 | Aspect Software, Inc. | System and method for providing an automatic telephone call back from information provided at a data terminal |
US7110526B1 (en) | 1998-10-14 | 2006-09-19 | Rockwell Electronic Commerce Technologies, Llc | Neural network for controlling calls in a telephone switch |
DE19948028A1 (en) * | 1998-11-20 | 2000-05-31 | Ibm | Request dispatch optimization method for computerized workflow management system has overall optimization function effected by local work management system for reconfiguration of remote work management systems |
US7058589B1 (en) * | 1998-12-17 | 2006-06-06 | Iex Corporation | Method and system for employee work scheduling |
US7295669B1 (en) | 1999-01-21 | 2007-11-13 | Avaya Technology Corp. | Call center telephone and data flow connection system |
US7200219B1 (en) | 1999-02-10 | 2007-04-03 | Avaya Technology Corp. | Dynamically allocating server resources to competing classes of work based upon achievement of service goals |
US7536002B1 (en) | 1999-07-09 | 2009-05-19 | Jpmorgan Chase Bank, National Association | System and method of intelligent call routing for cross sell offer selection based on optimization parameters or account-level data |
US6804346B1 (en) * | 1999-07-13 | 2004-10-12 | Interactive Intelligence, Inc. | Staged predictive dialing system |
US20050002515A1 (en) * | 1999-07-13 | 2005-01-06 | Mewhinney Brian E. | Dialing techniques for a contact center |
US7006994B1 (en) | 1999-07-16 | 2006-02-28 | American Management Systems, Inc. | Automated receivables management system |
US6587557B1 (en) | 1999-09-07 | 2003-07-01 | Concerto Software, Inc. | System and method of distributing outbound telephony services over a computer network |
US6985885B1 (en) * | 1999-09-21 | 2006-01-10 | Intertrust Technologies Corp. | Systems and methods for pricing and selling digital goods |
CN1335964A (en) * | 1999-11-10 | 2002-02-13 | 三菱电机株式会社 | Information terminal, server, information display system, and information display method |
WO2001037161A2 (en) * | 1999-11-12 | 2001-05-25 | Ericsson Inc | Intelligent system for managing profiles of subscribers |
US7929978B2 (en) | 1999-12-01 | 2011-04-19 | Genesys Telecommunications Laboratories, Inc. | Method and apparatus for providing enhanced communication capability for mobile devices on a virtual private network |
US6832245B1 (en) | 1999-12-01 | 2004-12-14 | At&T Corp. | System and method for analyzing communications of user messages to rank users and contacts based on message content |
US6798413B1 (en) * | 1999-12-03 | 2004-09-28 | Dcs, Inc. | Workflow management system |
KR100518071B1 (en) * | 1999-12-21 | 2005-09-28 | 가와테츠 죠호 시스테무 가부시키가이샤 | Method and device for call center operation |
US8805715B1 (en) * | 1999-12-29 | 2014-08-12 | Carl Meyer | Method for improving the performance of messages including internet splash pages |
US6658391B1 (en) * | 1999-12-30 | 2003-12-02 | Gary A. Williams | Strategic profiling |
US6683943B2 (en) * | 2000-01-26 | 2004-01-27 | Richard A. Wuelly | Automated mass audience telecommunications database creation method |
US7844504B1 (en) | 2000-04-27 | 2010-11-30 | Avaya Inc. | Routing based on the contents of a shopping cart |
US6954731B1 (en) | 2000-06-27 | 2005-10-11 | Ncr Corporation | Methods and system for optimizing a campaign |
US7103173B2 (en) * | 2001-07-09 | 2006-09-05 | Austin Logistics Incorporated | System and method for preemptive goals based routing of contact records |
US7142662B2 (en) | 2000-07-11 | 2006-11-28 | Austin Logistics Incorporated | Method and system for distributing outbound telephone calls |
US6697858B1 (en) * | 2000-08-14 | 2004-02-24 | Telephony@Work | Call center |
JP2002171332A (en) * | 2000-11-30 | 2002-06-14 | Toshiba Corp | Communication terminal equipment |
US8260663B1 (en) * | 2001-12-07 | 2012-09-04 | Carl Meyer | Method, algorithm, and computer program for targeting messages including advertisements in an interactive measurable medium |
US7254558B2 (en) * | 2000-12-21 | 2007-08-07 | Ge Corporate Financial Services, Inc. | Method and system for prioritizing debt collections |
US20020116336A1 (en) * | 2001-02-05 | 2002-08-22 | Athanassios Diacakis | Method and device for displaying contact information in a presence and availability management system |
US7330895B1 (en) * | 2001-03-15 | 2008-02-12 | Microsoft Corporation | Representation, decision models, and user interface for encoding managing preferences, and performing automated decision making about the timing and modalities of interpersonal communications |
US20030014336A1 (en) * | 2001-05-04 | 2003-01-16 | Fu-Tak Dao | Analytically determining revenue of internet companies using internet metrics |
US7386850B2 (en) * | 2001-06-01 | 2008-06-10 | Avaya Technology Corp. | Arrangement for scheduling tasks based on probability of availability of resources at a future point in time |
US7054434B2 (en) * | 2001-07-09 | 2006-05-30 | Austin Logistics Incorporated | System and method for common account based routing of contact records |
US7715546B2 (en) * | 2001-07-09 | 2010-05-11 | Austin Logistics Incorporated | System and method for updating contact records |
US20040170258A1 (en) * | 2001-09-26 | 2004-09-02 | Mitch Levin | Predictive dialing system and method |
US7313617B2 (en) | 2001-09-28 | 2007-12-25 | Dale Malik | Methods and systems for a communications and information resource manager |
US7774711B2 (en) | 2001-09-28 | 2010-08-10 | Aol Inc. | Automatic categorization of entries in a contact list |
US7472187B2 (en) * | 2001-09-28 | 2008-12-30 | At&T Intellectual Property I, L.P. | Communications and information resource manager |
US7007085B1 (en) * | 2001-09-28 | 2006-02-28 | Bellsouth Intellectual Property Corporation | Message log for wireline, voice mail, email, fax, pager, instant messages and chat |
AU2002334724A1 (en) * | 2001-10-01 | 2003-04-14 | Inventions, Inc. | Method of contacting a party using multiple media |
US7403923B2 (en) * | 2001-10-12 | 2008-07-22 | Accenture Global Services Gmbh | Debt collection practices |
US20030130937A1 (en) * | 2002-01-04 | 2003-07-10 | Reynolds Blake L. | Systems and methods for advancing collections on unpaid debts |
US7415417B2 (en) | 2002-03-15 | 2008-08-19 | Avaya Technology Corp. | Presence awareness agent |
US7336779B2 (en) * | 2002-03-15 | 2008-02-26 | Avaya Technology Corp. | Topical dynamic chat |
US7962644B1 (en) * | 2002-03-18 | 2011-06-14 | Oracle International Corporation | Systems and methods for handling a plurality of communications |
US7206388B2 (en) * | 2002-03-18 | 2007-04-17 | Openwave Systems Inc. | System and method for providing voice-activated presence information |
EP1363445A1 (en) * | 2002-05-17 | 2003-11-19 | Nortel Networks Limited | Method and apparatus for proactively sending a message |
US7620169B2 (en) | 2002-06-17 | 2009-11-17 | Avaya Inc. | Waiting but not ready |
US7401050B2 (en) | 2002-07-22 | 2008-07-15 | Accenture Global Services Gmbh | Method to improve debt collection practices |
US8812339B1 (en) * | 2002-07-24 | 2014-08-19 | Jack D. Stone, Jr. | System and method for scheduling tasks |
US7139389B2 (en) * | 2002-08-06 | 2006-11-21 | Daniel Neal Duncan | System and method for allocating contact resources to contact resource users |
CA2403043A1 (en) * | 2002-09-10 | 2004-03-10 | Keith Gill | Multiline dialing apparatus with interchangeable subscriber service capability |
CA2407991A1 (en) * | 2002-10-15 | 2004-04-15 | Keith Gill | Expandable multiline dialing apparatus |
US7401057B2 (en) | 2002-12-10 | 2008-07-15 | Asset Trust, Inc. | Entity centric computer system |
US7263614B2 (en) | 2002-12-31 | 2007-08-28 | Aol Llc | Implicit access for communications pathway |
US7945674B2 (en) | 2003-04-02 | 2011-05-17 | Aol Inc. | Degrees of separation for handling communications |
US7565153B2 (en) | 2003-01-22 | 2009-07-21 | Cml Emergency Services Inc. | Method and system for delivery of location specific information |
US20040148218A1 (en) * | 2003-01-29 | 2004-07-29 | Apac Customer Services, Inc. | Telephone number based sales predictor method and system |
US9818136B1 (en) | 2003-02-05 | 2017-11-14 | Steven M. Hoffberg | System and method for determining contingent relevance |
US6862540B1 (en) * | 2003-03-25 | 2005-03-01 | Johnson Controls Technology Company | System and method for filling gaps of missing data using source specified data |
US20040205127A1 (en) | 2003-03-26 | 2004-10-14 | Roy Ben-Yoseph | Identifying and using identities deemed to be known to a user |
US7280651B2 (en) * | 2003-05-20 | 2007-10-09 | At&T Bls Intellectual Property, Inc. | Method and system for performing automated telemarketing |
FR2858154B1 (en) * | 2003-07-23 | 2005-09-02 | France Telecom | INTERACTIVE VOICE SERVICE PLATFORM FOR OUTGOING CALLS, TRIGGERES AND SURVEILLANCE VIA THE INTERNET |
US20050149418A1 (en) * | 2003-08-15 | 2005-07-07 | Erbey William C. | Methods and systems for providing customer relations information |
EP1519549A1 (en) * | 2003-09-25 | 2005-03-30 | Siemens Aktiengesellschaft | Method for automatically setting up of a call |
US7770175B2 (en) | 2003-09-26 | 2010-08-03 | Avaya Inc. | Method and apparatus for load balancing work on a network of servers based on the probability of being serviced within a service time goal |
US8094804B2 (en) | 2003-09-26 | 2012-01-10 | Avaya Inc. | Method and apparatus for assessing the status of work waiting for service |
US20050075920A1 (en) * | 2003-10-01 | 2005-04-07 | Sheng Li | Projected sales |
US8155297B1 (en) | 2003-12-02 | 2012-04-10 | Jpmorgan Chase Bank | System and method for providing call-back options |
US20050131837A1 (en) | 2003-12-15 | 2005-06-16 | Sanctis Jeanne D. | Method, system and program product for communicating e-commerce content over-the-air to mobile devices |
US7415267B2 (en) * | 2003-12-15 | 2008-08-19 | Jp Morgan Chase Bank | Methods and systems for managing call reports for the financial services industry |
US7266193B2 (en) * | 2003-12-18 | 2007-09-04 | Avaya Technology Corp. | Adaptive feedback arrangement for controlling agent availability service level in a predictive dialer |
US7630905B1 (en) * | 2004-01-07 | 2009-12-08 | Ralph Reese | Call campaign methodologies |
US8472612B1 (en) | 2004-01-29 | 2013-06-25 | Avaya Inc. | Call center customer queue shortcut access code |
US7729490B2 (en) | 2004-02-12 | 2010-06-01 | Avaya Inc. | Post-termination contact management |
US8457300B2 (en) | 2004-02-12 | 2013-06-04 | Avaya Inc. | Instant message contact management in a contact center |
US8898239B2 (en) * | 2004-03-05 | 2014-11-25 | Aol Inc. | Passively populating a participant list with known contacts |
US7885401B1 (en) | 2004-03-29 | 2011-02-08 | Avaya Inc. | Method and apparatus to forecast the availability of a resource |
US8000989B1 (en) | 2004-03-31 | 2011-08-16 | Avaya Inc. | Using true value in routing work items to resources |
US7734032B1 (en) | 2004-03-31 | 2010-06-08 | Avaya Inc. | Contact center and method for tracking and acting on one and done customer contacts |
US7953859B1 (en) | 2004-03-31 | 2011-05-31 | Avaya Inc. | Data model of participation in multi-channel and multi-party contacts |
US8370269B2 (en) | 2004-06-02 | 2013-02-05 | Overstock.Com, Inc. | System and methods for electronic commerce using personal and business networks |
US7558558B2 (en) * | 2004-06-07 | 2009-07-07 | Cml Emergency Services Inc. | Automated mobile notification system |
US8073422B2 (en) * | 2004-06-07 | 2011-12-06 | Cassidian Communications, Inc. | Satellite radio warning system and method |
US8346593B2 (en) | 2004-06-30 | 2013-01-01 | Experian Marketing Solutions, Inc. | System, method, and software for prediction of attitudinal and message responsiveness |
US7590589B2 (en) | 2004-09-10 | 2009-09-15 | Hoffberg Steven M | Game theoretic prioritization scheme for mobile ad hoc networks permitting hierarchal deference |
US20060062376A1 (en) * | 2004-09-22 | 2006-03-23 | Dale Pickford | Call center services system and method |
US8234141B1 (en) | 2004-09-27 | 2012-07-31 | Avaya Inc. | Dynamic work assignment strategies based on multiple aspects of agent proficiency |
US7949121B1 (en) | 2004-09-27 | 2011-05-24 | Avaya Inc. | Method and apparatus for the simultaneous delivery of multiple contacts to an agent |
US7949123B1 (en) | 2004-09-28 | 2011-05-24 | Avaya Inc. | Wait time predictor for long shelf-life work |
US7657021B2 (en) * | 2004-09-29 | 2010-02-02 | Avaya Inc. | Method and apparatus for global call queue in a global call center |
US10248917B1 (en) | 2004-10-14 | 2019-04-02 | Capital One Services, Llc | System and method for developing and utilizing a contactability profile |
WO2006055607A2 (en) * | 2004-11-19 | 2006-05-26 | Definitive Business Solutions, Llc | Method and system for communication prioritization |
US7567653B1 (en) | 2005-03-22 | 2009-07-28 | Avaya Inc. | Method by which call centers can vector inbound TTY calls automatically to TTY-enabled resources |
US8713025B2 (en) | 2005-03-31 | 2014-04-29 | Square Halt Solutions, Limited Liability Company | Complete context search system |
US7817796B1 (en) | 2005-04-27 | 2010-10-19 | Avaya Inc. | Coordinating work assignments for contact center agents |
US8781092B2 (en) * | 2005-05-16 | 2014-07-15 | Noble Systems Corporation | Systems and methods for callback processing |
US8036374B2 (en) * | 2005-05-16 | 2011-10-11 | Noble Systems Corporation | Systems and methods for detecting call blocking devices or services |
US7587040B2 (en) * | 2005-05-16 | 2009-09-08 | Noble Systems Corporation | Systems and methods for detecting false signals on an outbound call |
US8885812B2 (en) * | 2005-05-17 | 2014-11-11 | Oracle International Corporation | Dynamic customer satisfaction routing |
US7809127B2 (en) | 2005-05-26 | 2010-10-05 | Avaya Inc. | Method for discovering problem agent behaviors |
US20080010127A1 (en) * | 2006-06-09 | 2008-01-10 | Pitney Bowes Incorporated | Intelligent mail system to coordinate direct mail with other marketing channels using mail prediction and mail control |
US7779042B1 (en) | 2005-08-08 | 2010-08-17 | Avaya Inc. | Deferred control of surrogate key generation in a distributed processing architecture |
US8583466B2 (en) * | 2005-08-09 | 2013-11-12 | Oracle International Corporation | System and method for routing workflow items based on workflow templates in a call center |
US7881450B1 (en) | 2005-09-15 | 2011-02-01 | Avaya Inc. | Answer on hold notification |
US8577015B2 (en) * | 2005-09-16 | 2013-11-05 | Avaya Inc. | Method and apparatus for the automated delivery of notifications to contacts based on predicted work prioritization |
US8116446B1 (en) | 2005-10-03 | 2012-02-14 | Avaya Inc. | Agent driven work item awareness for tuning routing engine work-assignment algorithms |
US8073129B1 (en) | 2005-10-03 | 2011-12-06 | Avaya Inc. | Work item relation awareness for agents during routing engine driven sub-optimal work assignments |
US7822587B1 (en) | 2005-10-03 | 2010-10-26 | Avaya Inc. | Hybrid database architecture for both maintaining and relaxing type 2 data entity behavior |
US10572879B1 (en) | 2005-10-03 | 2020-02-25 | Avaya Inc. | Agent driven media-agnostic work item grouping and sharing over a consult medium |
US8411843B1 (en) | 2005-10-04 | 2013-04-02 | Avaya Inc. | Next agent available notification |
US8874477B2 (en) * | 2005-10-04 | 2014-10-28 | Steven Mark Hoffberg | Multifactorial optimization system and method |
US7787609B1 (en) | 2005-10-06 | 2010-08-31 | Avaya Inc. | Prioritized service delivery based on presence and availability of interruptible enterprise resources with skills |
US7752230B2 (en) | 2005-10-06 | 2010-07-06 | Avaya Inc. | Data extensibility using external database tables |
US8577014B2 (en) * | 2005-11-04 | 2013-11-05 | At&T Intellectual Property I, L.P. | System and method of managing calls at a call center |
US8233609B2 (en) * | 2005-11-30 | 2012-07-31 | Noble Systems Corporation | Systems and methods for managing call processing for a specific agent |
US9008075B2 (en) | 2005-12-22 | 2015-04-14 | Genesys Telecommunications Laboratories, Inc. | System and methods for improving interaction routing performance |
US8238541B1 (en) | 2006-01-31 | 2012-08-07 | Avaya Inc. | Intent based skill-set classification for accurate, automatic determination of agent skills |
US8737173B2 (en) | 2006-02-24 | 2014-05-27 | Avaya Inc. | Date and time dimensions for contact center reporting in arbitrary international time zones |
US8126134B1 (en) * | 2006-03-30 | 2012-02-28 | Verint Americas, Inc. | Systems and methods for scheduling of outbound agents |
US8442197B1 (en) | 2006-03-30 | 2013-05-14 | Avaya Inc. | Telephone-based user interface for participating simultaneously in more than one teleconference |
US9247058B2 (en) * | 2006-05-30 | 2016-01-26 | Actimizer A/S | Dynamic connection distributor |
ES2524435T3 (en) * | 2006-05-30 | 2014-12-09 | Actimizer A/S | A dynamic connection distributor |
US8170930B2 (en) * | 2006-07-20 | 2012-05-01 | Metavante Corporation | System and method for automated notification |
US7936867B1 (en) | 2006-08-15 | 2011-05-03 | Avaya Inc. | Multi-service request within a contact center |
US8391463B1 (en) | 2006-09-01 | 2013-03-05 | Avaya Inc. | Method and apparatus for identifying related contacts |
US8938063B1 (en) | 2006-09-07 | 2015-01-20 | Avaya Inc. | Contact center service monitoring and correcting |
US8811597B1 (en) | 2006-09-07 | 2014-08-19 | Avaya Inc. | Contact center performance prediction |
US8855292B1 (en) | 2006-09-08 | 2014-10-07 | Avaya Inc. | Agent-enabled queue bypass to agent |
US7835514B1 (en) | 2006-09-18 | 2010-11-16 | Avaya Inc. | Provide a graceful transfer out of active wait treatment |
US8135607B2 (en) * | 2006-11-03 | 2012-03-13 | Experian Marketing Solutions, Inc. | System and method of enhancing leads by determining contactability scores |
US8767944B1 (en) | 2007-01-03 | 2014-07-01 | Avaya Inc. | Mechanism for status and control communication over SIP using CODEC tunneling |
US7948984B2 (en) * | 2007-01-16 | 2011-05-24 | Cisco Technology, Inc. | Detecting an identifier change of an endpoint |
US7873157B1 (en) * | 2007-02-23 | 2011-01-18 | Avaya Inc. | Method and apparatus for performing predictive dialing |
US8483383B2 (en) * | 2007-03-02 | 2013-07-09 | Aspect Software, Inc. | Method of scheduling calls |
US7747705B1 (en) | 2007-05-08 | 2010-06-29 | Avaya Inc. | Method to make a discussion forum or RSS feed a source for customer contact into a multimedia contact center that is capable of handling emails |
US8504534B1 (en) | 2007-09-26 | 2013-08-06 | Avaya Inc. | Database structures and administration techniques for generalized localization of database items |
US8583480B2 (en) | 2007-12-21 | 2013-11-12 | Overstock.Com, Inc. | System, program product, and methods for social network advertising and incentives for same |
US8856182B2 (en) | 2008-01-25 | 2014-10-07 | Avaya Inc. | Report database dependency tracing through business intelligence metadata |
US8385532B1 (en) | 2008-05-12 | 2013-02-26 | Avaya Inc. | Real-time detective |
US8831206B1 (en) | 2008-05-12 | 2014-09-09 | Avaya Inc. | Automated, data-based mechanism to detect evolution of employee skills |
US10375244B2 (en) * | 2008-08-06 | 2019-08-06 | Avaya Inc. | Premises enabled mobile kiosk, using customers' mobile communication device |
US8116237B2 (en) | 2008-09-26 | 2012-02-14 | Avaya Inc. | Clearing house for publish/subscribe of status data from distributed telecommunications systems |
US8473391B2 (en) * | 2008-12-31 | 2013-06-25 | Altisource Solutions S.àr.l. | Method and system for an integrated approach to collections cycle optimization |
ATE532322T1 (en) * | 2009-02-19 | 2011-11-15 | Research In Motion Ltd | PERSONAL CALL CENTER |
US8315609B2 (en) * | 2009-02-19 | 2012-11-20 | Research In Motion Limited | Personal call center |
US9747622B1 (en) | 2009-03-24 | 2017-08-29 | Overstock.Com, Inc. | Point-and-shoot product lister |
WO2010132492A2 (en) | 2009-05-11 | 2010-11-18 | Experian Marketing Solutions, Inc. | Systems and methods for providing anonymized user profile data |
US8621011B2 (en) | 2009-05-12 | 2013-12-31 | Avaya Inc. | Treatment of web feeds as work assignment in a contact center |
US8964958B2 (en) | 2009-05-20 | 2015-02-24 | Avaya Inc. | Grid-based contact center |
US8644491B2 (en) | 2009-08-21 | 2014-02-04 | Avaya Inc. | Mechanism for multisite service state description |
US8422644B2 (en) | 2009-08-31 | 2013-04-16 | At&T Intellectual Property I, L.P. | Systems and methods to redirect incoming contacts |
US8385533B2 (en) | 2009-09-21 | 2013-02-26 | Avaya Inc. | Bidding work assignment on conference/subscribe RTP clearing house |
US8565386B2 (en) | 2009-09-29 | 2013-10-22 | Avaya Inc. | Automatic configuration of soft phones that are usable in conjunction with special-purpose endpoints |
US8812482B1 (en) | 2009-10-16 | 2014-08-19 | Vikas Kapoor | Apparatuses, methods and systems for a data translator |
US9516069B2 (en) | 2009-11-17 | 2016-12-06 | Avaya Inc. | Packet headers as a trigger for automatic activation of special-purpose softphone applications |
US8306212B2 (en) | 2010-02-19 | 2012-11-06 | Avaya Inc. | Time-based work assignments in automated contact distribution |
US8358771B1 (en) | 2010-03-24 | 2013-01-22 | Jpmorgan Chase Bank, N.A. | System and method for managing customer communications over communication channels |
US20150088706A1 (en) * | 2010-05-12 | 2015-03-26 | Ontario Systems, Llc | Method, system, and computer-readable medium for managing and collecting receivables |
US8699699B1 (en) * | 2010-12-23 | 2014-04-15 | Five9, Inc. | System and methods for outbound dialing in multi-campaign and blended environment of virtual contact center |
EP2718893A4 (en) * | 2011-06-06 | 2015-01-28 | Iselect Ltd | Systems and methods for use in marketing |
US20130060587A1 (en) * | 2011-09-02 | 2013-03-07 | International Business Machines Corporation | Determining best time to reach customers in a multi-channel world ensuring right party contact and increasing interaction likelihood |
US9124700B1 (en) | 2012-01-30 | 2015-09-01 | Jpmorgan Chase Bank, N.A. | System and method for unified calling |
US8811598B2 (en) * | 2012-02-02 | 2014-08-19 | Avaya Inc. | Scheduling an agent based on a contact center history |
US8675860B2 (en) | 2012-02-16 | 2014-03-18 | Avaya Inc. | Training optimizer for contact center agents |
US9740708B2 (en) | 2012-05-01 | 2017-08-22 | Everbridge, Inc. | Systems and methods for distance and performance based load balancing |
US9391855B2 (en) * | 2012-05-09 | 2016-07-12 | Everbridge, Inc. | Systems and methods for simulating a notification system |
BR112014030975A2 (en) * | 2012-06-11 | 2017-06-27 | Interactive Intelligence Inc | method and system for increasing productivity and total throughput in a contact center |
US8675839B1 (en) | 2012-06-27 | 2014-03-18 | Noble Systems Corporation | Reporting unavailable trunk-related resources for a predictive dialer using a dynamic pacing algorithm |
US9813559B1 (en) | 2012-06-27 | 2017-11-07 | Noble Systems Corporation | Addressing trunk-related resource deficiencies for a predictive dialer using a dynamic pacing algorithm |
US9674354B2 (en) | 2012-10-03 | 2017-06-06 | ISelect Ltd. | Systems and methods for use in marketing |
US10546262B2 (en) | 2012-10-19 | 2020-01-28 | Overstock.Com, Inc. | Supply chain management system |
US10949876B2 (en) * | 2012-10-29 | 2021-03-16 | Overstock.Com, Inc. | System and method for management of email marketing campaigns |
US8909198B1 (en) * | 2012-12-19 | 2014-12-09 | Noble Systems Corporation | Customized dialing procedures for outbound calls |
US11023947B1 (en) | 2013-03-15 | 2021-06-01 | Overstock.Com, Inc. | Generating product recommendations using a blend of collaborative and content-based data |
US20140310154A1 (en) | 2013-03-15 | 2014-10-16 | United Student Aid Funds, Inc. | System and method for managing educational institution borrower debt |
US11676192B1 (en) | 2013-03-15 | 2023-06-13 | Overstock.Com, Inc. | Localized sort of ranked product recommendations based on predicted user intent |
US8738076B1 (en) | 2013-04-19 | 2014-05-27 | Noble Systems Corporation | Providing compliance enforcement for manually dialed wireless numbers in a contact center |
US9036811B1 (en) | 2013-04-19 | 2015-05-19 | Noble Systems Corporation | Dialing a telephone number subject to an autodialer prohibition in a contact center |
US10810654B1 (en) | 2013-05-06 | 2020-10-20 | Overstock.Com, Inc. | System and method of mapping product attributes between different schemas |
US9407558B2 (en) * | 2013-05-10 | 2016-08-02 | At&T Intellectual Property I, L.P. | Method and system for automatic triggering network management control for VoIP border elements |
US9258424B2 (en) | 2013-05-24 | 2016-02-09 | Avaya Inc. | Prioritize contact numbers of customers in real time |
US9483788B2 (en) | 2013-06-25 | 2016-11-01 | Overstock.Com, Inc. | System and method for graphically building weighted search queries |
US9210265B2 (en) | 2013-06-27 | 2015-12-08 | International Business Machines Corporation | Exploring multiple contact channels to determine potential for reaching customers |
US9118764B2 (en) | 2013-08-09 | 2015-08-25 | Avaya Inc. | Method and system to determine and employ best contact opportunity |
US10929890B2 (en) | 2013-08-15 | 2021-02-23 | Overstock.Com, Inc. | System and method of personalizing online marketing campaigns |
US9742919B2 (en) * | 2013-10-31 | 2017-08-22 | ARS National Services, Inc. | Outbound calling center inventory management |
US10872350B1 (en) | 2013-12-06 | 2020-12-22 | Overstock.Com, Inc. | System and method for optimizing online marketing based upon relative advertisement placement |
US11257117B1 (en) | 2014-06-25 | 2022-02-22 | Experian Information Solutions, Inc. | Mobile device sighting location analytics and profiling system |
US9767309B1 (en) | 2015-11-23 | 2017-09-19 | Experian Information Solutions, Inc. | Access control system for implementing access restrictions of regulated database records while identifying and providing indicators of regulated database records matching validation criteria |
US10534845B2 (en) | 2016-05-11 | 2020-01-14 | Overstock.Com, Inc. | System and method for optimizing electronic document layouts |
WO2018039377A1 (en) | 2016-08-24 | 2018-03-01 | Experian Information Solutions, Inc. | Disambiguation and authentication of device users |
US10373515B2 (en) | 2017-01-04 | 2019-08-06 | International Business Machines Corporation | System and method for cognitive intervention on human interactions |
US10235990B2 (en) | 2017-01-04 | 2019-03-19 | International Business Machines Corporation | System and method for cognitive intervention on human interactions |
US10318639B2 (en) | 2017-02-03 | 2019-06-11 | International Business Machines Corporation | Intelligent action recommendation |
US10970769B2 (en) | 2017-03-02 | 2021-04-06 | Overstock.Com, Inc. | Method and system for optimizing website searching with user pathing |
US10949842B1 (en) * | 2018-01-30 | 2021-03-16 | Mastercard International Incorporated | Preventing data analysis interruptions by identifying card continuity without using personally identifiable information |
US11514493B1 (en) | 2019-03-25 | 2022-11-29 | Overstock.Com, Inc. | System and method for conversational commerce online |
US11205179B1 (en) | 2019-04-26 | 2021-12-21 | Overstock.Com, Inc. | System, method, and program product for recognizing and rejecting fraudulent purchase attempts in e-commerce |
US11734368B1 (en) | 2019-09-26 | 2023-08-22 | Overstock.Com, Inc. | System and method for creating a consistent personalized web experience across multiple platforms and channels |
US11682041B1 (en) | 2020-01-13 | 2023-06-20 | Experian Marketing Solutions, Llc | Systems and methods of a tracking analytics platform |
GB2596821A (en) * | 2020-07-07 | 2022-01-12 | Validsoft Ltd | Computer-generated speech detection |
US11622041B2 (en) | 2020-12-23 | 2023-04-04 | Acqueon Technologies Inc | System and method for enhanced call progress analysis utilizing dual-prong analysis |
US11258898B1 (en) * | 2021-01-20 | 2022-02-22 | Ford Global Technologies, Llc | Enhanced personalized phone number recommender |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3989899A (en) * | 1975-04-08 | 1976-11-02 | Daniel Norwich | Telephone scheduling system |
EP0493292A2 (en) * | 1990-12-11 | 1992-07-01 | International Business Machines Corporation | Look-ahead method and apparatus for predictive dialing using a neural network |
US5155761A (en) * | 1990-01-26 | 1992-10-13 | Intervoice, Inc. | Automatic call back system and method of operation |
Family Cites Families (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4599493A (en) * | 1984-08-28 | 1986-07-08 | Tbs International, Inc. | Multi-line telephone control system |
US4833618A (en) * | 1986-02-20 | 1989-05-23 | Net Laboratories, Inc. | System for automatically reading utility meters from a remote location |
US4858120A (en) * | 1987-03-18 | 1989-08-15 | International Telesystems Corp. | System for regulating arrivals of customers to servers |
JPS6476360A (en) * | 1987-09-18 | 1989-03-22 | Hitachi Ltd | Work scheduling system |
US5151932A (en) * | 1987-11-17 | 1992-09-29 | Oki Electric Industry Co., Ltd. | Method and system for selectively communicating with a telephone or a non-telephone terminal through a public telephone network |
US4829563A (en) * | 1988-04-07 | 1989-05-09 | Teknekron Infoswitch Corporation | Method for predictive dialing |
US4881261A (en) * | 1988-06-29 | 1989-11-14 | Rockwell International Corporation | Method for predictive pacing of calls in a calling system |
US5153909A (en) * | 1989-05-25 | 1992-10-06 | At&T Bell Laboratories | Resource control and data handling for central office based automatic call distributors |
US4933964A (en) * | 1989-07-25 | 1990-06-12 | International Telesystems Corporation | Pacing of telephone calls for call origination management systems |
US5111391A (en) * | 1989-10-05 | 1992-05-05 | Mrs. Fields, Inc. | System and method for making staff schedules as a function of available resources as well as employee skill level, availability and priority |
US5197000A (en) * | 1990-07-09 | 1993-03-23 | International Business Machines Corporation | Method of scheduling meetings |
DE4023687C2 (en) * | 1990-07-26 | 2000-09-07 | Abb Schweiz Ag | Power converter arrangement |
US5164983A (en) * | 1991-01-28 | 1992-11-17 | American Telephone & Telegraph Company | Telemarketing complex performance management system |
US5185782A (en) * | 1991-02-08 | 1993-02-09 | A&T Bell Laboratories | ACD arrangement for automatically returning a call at a time specified by the original caller |
US5297195A (en) * | 1991-10-02 | 1994-03-22 | Teledirect International, Inc. | Method and apparatus for automatic telephone scheduling system |
US5179589A (en) * | 1991-11-27 | 1993-01-12 | International Telesystems Corporation | Call progress pacing |
US5343518A (en) * | 1993-01-14 | 1994-08-30 | Davox Corporation | System and method for controlling the dialing order of call record lists in an automated dialing system |
US5436965A (en) * | 1993-11-16 | 1995-07-25 | Automated Systems And Programming, Inc. | Method and system for optimization of telephone contact campaigns |
-
1993
- 1993-11-16 US US08/152,060 patent/US5436965A/en not_active Expired - Lifetime
-
1994
- 1994-11-14 WO PCT/US1994/013027 patent/WO1995014342A1/en not_active Application Discontinuation
- 1994-11-14 EP EP95902527A patent/EP0729683A1/en not_active Ceased
- 1994-11-14 AU AU11764/95A patent/AU1176495A/en not_active Abandoned
- 1994-11-14 CA CA002176816A patent/CA2176816C/en not_active Expired - Fee Related
-
1995
- 1995-06-07 US US08/486,577 patent/US5621790A/en not_active Expired - Lifetime
-
1997
- 1997-04-14 US US08/834,131 patent/US5889799A/en not_active Expired - Fee Related
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3989899A (en) * | 1975-04-08 | 1976-11-02 | Daniel Norwich | Telephone scheduling system |
US3989899B1 (en) * | 1975-04-08 | 1976-11-02 | ||
US5155761A (en) * | 1990-01-26 | 1992-10-13 | Intervoice, Inc. | Automatic call back system and method of operation |
EP0493292A2 (en) * | 1990-12-11 | 1992-07-01 | International Business Machines Corporation | Look-ahead method and apparatus for predictive dialing using a neural network |
Non-Patent Citations (1)
Title |
---|
J.HOLMGREN: "GREATER PRODUCTIVITY WITH AT&T OUTBOUND CALL MANAGEMENT", AT & T TECHNOLOGY, vol. 5, no. 4, 1990, SHORT HILLS, NEW JERSEY US, pages 6 - 13 * |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1996038971A1 (en) * | 1995-06-01 | 1996-12-05 | Harris Corporation | Computer calling method and system |
EP0874508A1 (en) * | 1997-04-18 | 1998-10-28 | Harris Corporation | Communication system to provide called party location and pre-call warning |
NL1006371C2 (en) * | 1997-06-20 | 1998-12-22 | Koninkl Kpn Nv | Apparatus and method for testing the accessibility of at least one user of a telecommunication network. |
EP0886423A1 (en) * | 1997-06-20 | 1998-12-23 | Koninklijke KPN N.V. | Device and method for testing the reachability of at least one user of a telecommunication network |
WO2000036811A1 (en) * | 1998-12-18 | 2000-06-22 | Blake Rice | Automated right-party contact telephone system |
GB2362066A (en) * | 1998-12-18 | 2001-11-07 | Blake Rice | Automated right-party contact telephone system |
GB2362066B (en) * | 1998-12-18 | 2004-01-07 | Blake Rice | Automated right-party contact telephone system |
WO2009086244A1 (en) * | 2007-12-27 | 2009-07-09 | Genesys Telecommunications Laboratories, Inc. | Apparatus and methods incorporating presence dynamics |
Also Published As
Publication number | Publication date |
---|---|
EP0729683A1 (en) | 1996-09-04 |
CA2176816C (en) | 2000-01-25 |
US5436965A (en) | 1995-07-25 |
US5889799A (en) | 1999-03-30 |
CA2176816A1 (en) | 1995-05-26 |
US5621790A (en) | 1997-04-15 |
AU1176495A (en) | 1995-06-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US5436965A (en) | Method and system for optimization of telephone contact campaigns | |
US5802161A (en) | Method and system for optimized scheduling | |
USRE46420E1 (en) | Method and system for distributing outbound telephone calls | |
US7715546B2 (en) | System and method for updating contact records | |
USRE44979E1 (en) | System and method for common account based routing of contact records | |
US5926528A (en) | Call pacing method | |
US5822410A (en) | Churn amelioration system and method therefor | |
US6859529B2 (en) | Method and system for self-service scheduling of inbound inquiries | |
EP0559979B1 (en) | Subscriber call routing process system | |
US6134530A (en) | Rule based routing system and method for a virtual sales and service center | |
US6721778B1 (en) | Unscheduled event task processing system | |
CN101997996B (en) | Method and device for queuing routing | |
CN105704335A (en) | Predictive form calling-out algorithm based on dynamic statistics process, switch dialing method and device | |
US20030018762A1 (en) | Arrangement for forecasting timely completion of a task by a resource | |
WO1995017067A1 (en) | Method of and apparatus for processing data at a remote workstation | |
WO2005020546A2 (en) | Method and system for selecting a preferred contact center agent based on agent proficiency and performance and contact center state | |
CA2256119C (en) | Time slot based call pacing method and apparatus | |
US20020186826A1 (en) | Intelligent dynamic realtime feature delivery | |
CN112399011B (en) | Intelligent call recording method and device | |
JP7370416B1 (en) | Call recipient determination system, call recipient determination method, and program | |
JP7370417B1 (en) | Call recipient determination system, call recipient determination method, and program | |
CN117499537A (en) | Data processing method and device, electronic equipment and storage medium | |
Dilini et al. | Methods for Controlling the Call Placemant Ratio for Outbound Dialing of a Call Center | |
JPH1023161A (en) | Automatic dial call distribution control system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AM AT AU BB BG BR BY CA CH CN CZ DE DK EE ES FI GB GE HU JP KE KG KP KR KZ LK LR LT LU LV MD MG MN MW NL NO NZ PL PT RO RU SD SE SI SK TJ TT UA UZ VN |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): KE MW SD SZ AT BE CH DE DK ES FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN ML MR NE SN TD TG |
|
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 1995902527 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2176816 Country of ref document: CA |
|
WWP | Wipo information: published in national office |
Ref document number: 1995902527 Country of ref document: EP |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
WWR | Wipo information: refused in national office |
Ref document number: 1995902527 Country of ref document: EP |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 1995902527 Country of ref document: EP |