Noble Systems Corporation

Noble Systems Coporation

James K Noble, Jr

Christopher S Haggerty

Jason P Ouimette

Karl H Koster

Chad Hitchcock

Marcin Pycko

Ellwood I Neuer, Iii

Ruby Amastha Fields

A communications handler manages incoming communications of different channel types and determines an appropriate contact center agent to receive the communication, based on which communication type and the number of sessions for each type, that an agent can handle. The performance of the agent handling the various communication sessions across the channel types is measure and monitored. If the agent's performance crosses a threshold indicating an unacceptable decrease in performance, a channel type/session may be de-assigned in order to improve the agent's performance. If the agent's performance is stellar and allows, then a further channel type or communication session of a channel type may be added. Various graphical user indications for managing the channel type performance and de-assignment are presented.

Managing multiple agent communication sessions in a contact center

Answering machine detection ('AMD') processes in a contact center are improved by obtaining and storing AMD meta-data about a known greeting from an automatic voice messaging capability ('AVMC') on a telephone call to a known number. The AMD meta-data is used in subsequent calls to that known number and the greeting detected is analyzed using the AMD meta-data to make a comparison determination if AMD meta-data obtained from the current greeting matches that stored so as to determine whether the current greeting originated from an AVMC or from a live person. In certain embodiments, a real-time speech analytics (&#x201c;RTSA&#x201d;) system is used for processing the greeting to obtain the AMD meta-data which is stored and used when comparing subsequently obtained AMD meta-data. Calls to telephone numbers for which there is no stored AMD meta-data results in analyzing the greeting in order to obtain and store AMD meta-data.

Answering machine detection ('AMD') for a contact center by using AMD meta-data

A telephone call to a remote party may encounter a number of abnormal conditions, which prevents the call from being offered to the remote party's interface. These conditions may be indicated to the calling party using call progress information conveyed as out-of-band information, in the form of signaling elements and/or as in-band information, in the form of audio information. The audio information may include a special information tone and/or an intercept announcement. The call handler originating the outbound call may provide the audio information to a speech analytics component that analyzes the audio information. The analyzed audio information may be reconciled with the out-of-band information. Various rules can be applied to ascertain how to disposition the call in instances where the in-band and out-of-information are inconsistent. Once reconciled, accurate call disposition information can be recorded in the call record for that call.

Accurate dispositioning of a telephone call by reconciling cause codes with in-band audio information

Various embodiments of the invention provide methods, systems, and computer program products for handling an audio path failure and/or non-conformant QoS for a call between a contact center agent and remote party. Specifically, an audio path is established to a first telephony device being used by the agent and a call is bridged onto the audio path so that audio can be streamed back-and-forth between the first telephony device and a second telephony device being used by the party. Accordingly, various embodiments of the invention involve monitoring the audio path to detect an audio path failure and/or non-conformant QoS for the audio and bridging the call onto a second audio path when a failure or non-conformant QoS is detected so that the call is not disconnected from the second telephony device and a third device (e.g., IVR) can stream audio over the second audio path to the second telephony device.

Handling audio path failure and poor quality of service for voice calls in a contact center

Modifications to the call acceptance process in a call handler allows determination of how to process a call before the call is answered. In one embodiment a call handler receives an incoming call notification message that include call related information, such as the calling and called telephone numbers. A call acceptance timer is started after the incoming call notification message is received. Prior to accepting the call, the call handler uses the call related information to ascertain an appropriate queue and an available agent in that queue. If an appropriate agent is available, the timer is stopped, the call is accepted, and the call is routed to the appropriate agent. If an agent is not available, then upon expiry of the timer, the call is accepted and an announcement may be played to the calling party, while awaiting for an agent to become available.

Telephone call processing modifications related to call acceptance for an incoming call received at a contact center

A predictive dialer in a call center may originate a number of outbound calls on behalf of agents for an outbound call campaign. Since many calls may fail to connect with the right party, the predictive dialer may originate several contemporaneous calls in order to provide a single call to an available agent. A pacing algorithm in the predictive dialer determines how many calls are to be made based on various factors, conditions, and rules. In some instances, the predictive dialer may attempt to originate more calls than there are available trunks. In such instances, the number of originated calls is limited by the number of available trunks causing a trunk-related deficiency condition, which can adversely impact the agents' performance. Various embodiments of the invention detect such conditions and address them to attempt to minimize current and future trunk-related deficiency conditions.

Addressing trunk-related resource deficiencies for a predictive dialer using a dynamic pacing algorithm

Technologies are disclosed for determining a best time to contact a party over a plurality of contact periods of time to achieve at least one of a desired outcome and a desired result. In various embodiments, the party has multiple contact types that can be utilized to contact the party. Accordingly, an optimal contact type for the party for each contact period is selected that identifies the contact type with a probability having the highest likelihood of achieving at least one of the desired outcome and the desired result by utilizing the contact type to contact the party during the contact period. A best time to contact the party is then identified as one of the contact periods based on the optimal contact types selected for the party for each contact period and associated probabilities.

Best time to communicate with parties having multiple contacts

Best time to call parties having multiple contacts

Various embodiments of the invention provide methods, systems, and computer-program products for charging a battery of a first mobile device from a battery of a second mobile device. In particular embodiments, a request is received identifying an amount of charge to provide from the battery of the second device to the battery of the first device. Accordingly, a determination is made as to whether the amount of charge requested is likely to result in a battery charge of the second device dropping below a threshold value before the battery of the device is recharged based on historical battery charge usage data of the device over a past period of time. If the amount of charge is not likely to result in the battery charge dropping below the threshold value, then the battery of the first device is charged with the amount of charge from the battery of the second device.

Growing community of inventors

Marietta, GA, United States of America

James K Noble, Jr