Method and apparatus for optimizing response time to events in queue

A system for optimizing response time to events or representations thereof waiting in a queue has a first server having access to the queue; a software application running on the first server; and a second server accessible from the first server, the second server containing rules governing the optimization. In a preferred embodiment, the software application at least periodically accesses the queue and parses certain ones of events or tokens in the queue and compares the parsed results against rules accessed from the second server in order to determine a measure of disposal time for each parsed event wherein if the determined measure is sufficiently low for one or more of the parsed events, those one or more events are modified to a reflect a higher priority state than originally assigned enabling faster treatment of those events resulting in relief from those events to the queue system load.

Skip to: Description  ·  Claims  ·  References Cited  · Patent History  ·  Patent History
Description
CROSS-REFERENCE TO RELATED DOCUMENTS

The present invention application is a reissue patent application of U.S. Pat. No. 7,929,562 filed on May 16, 2003 as patent application Ser. No. 10/440,348, which is a continuation in part (CIP)) to a U.S. patent application Ser. No. 10/229,514 entitled “Method and Apparatus for Anticipating and Planning Communication-Center Resources Based on Evaluation of Events Waiting in a Communication Center Master Queue” filed on 08/27/2002, Now filed on Aug. 27, 2002 now U.S. Pat. No. 6,822,947 which is a CIP to a 6,822,945, disclosures of which are incorporated herein by reference. The disclosures of U.S. patent application Ser. No. 09/766,271 entitled “Personal Interaction Interface for Communication-Center Customers”, filed on Jan. 18, 2001, now abandoned which is a CIP to a, and of U.S. patent application Ser. No. 09/710,042 entitled “System for improved reporting of communication center presence information to prospective clients”, filed on Nov. 8, 2000, now abandoned disclosures of which, are incorporated herein in their entirety by reference.

FIELD OF THE INVENTION

The present invention is in the general field of multimedia communications including telephony. The present invention has particular application to methods and apparatus for optimizing response time for events waiting in a communication center real or virtual queue by interacting directly with the queue and assigning or modifying priority assignments to events according to a calculated estimated disposal time (EDT).

BACKGROUND OF THE INVENTION

In the field of telephony communication, there have been many improvements in technology over the years that have contributed to more efficient use of telephone communication within hosted call-center environments. Most of these improvements involve integrating the telephones and switching systems in such call centers with computer hardware and software adapted for, among other things, better routing of telephone calls, faster delivery of telephone calls and associated information, and improved service with regard to client satisfaction. Such computer-enhanced telephony is known in the art as computer-telephony integration (CTI).

Generally speaking, CTI implementations of various design and purpose are implemented both within individual call-centers and, in some cases, at the telephone network level. For example, processors running CTI software applications may be linked to telephone switches, service control points (SCP), and network entry points within a public or private telephone network. At the call-center level, CTI-enhanced processors, data servers, transaction servers, and the like, are linked to telephone switches and, in some cases, to similar CTI hardware at the network level, often by a dedicated digital link CTI processors and other hardware within a call-center are commonly referred to as customer premises equipment (CPE). It is the CTI processor and application software is such centers that provides computer enhancement to a call center.

In a CTI-enhanced call center, telephones at agent stations are connected to a central telephony switching apparatus, such as an automatic call distributor (ACD) switch or a private branch exchange (PBX). The agent stations may also be equipped with computer terminals such as personal computer/video display units (PC/VDU) so that agents manning such stations may have access to stored data as well as being linked to incoming callers by telephone equipment. Such stations may be interconnected through the PC VDU by a local area network (LAN). One or more data or transaction servers may also be connected to the LAN that interconnects agent stations. The LAN is, in turn, typically connected to the CTI processor, which is connected to the call switching apparatus of the call center.

In recent years, advances in computer technology, telephony equipment, and infrastructure have provided many opportunities for improving telephone service in publicly switched and private telephone intelligent networks. Similarly, development of a separate information and data network known as the Internet, together with advances in computer hardware and software have led to a new multimedia telephone system known in the art by several names. In this new systemology, telephone calls are simulated by multimedia computer equipment, and data, such as audio data, is transmitted over data networks as data packets. In this system the broad term used to describe such computer-simulated telephony is Data Network Telephony (DNT).

Recent improvements to available technologies associated with the transmission and reception of data packets during real-time DNT communication have enabled companies to successfully add DNT, principally IPNT capabilities to existing CTI call centers. Such improvements, as described herein and known-to the inventor, include methods for guaranteeing available bandwidth or quality of service (QOS) for a transaction, improved mechanisms for organizing, coding, compressing, and carrying data more efficiently using less bandwidth, and methods and apparatus for intelligently replacing lost data via using voice supplementation methods and enhanced buffering capabilities.

In addition to Internet protocol (IPNT) calls, a DNT center may also share other forms of media with customers accessing the system through their computers. E-mails, video mails, fax, file share, file transfer, video calls, and so forth are some of the other forms of media, which may be used. This capability of handling varied media leads to the term multimedia communications center. A multimedia communications center may be a combination CTI and DNT center, or may be a DNT center capable of receiving COST calls and converting them to a digital DNT format. The term communication center will replace the term call center hereinafter in this specification when referring to multi-media capabilities.

In systems known to the inventors, incoming IPNT calls are processed and routed within an IPNT-capable communication center in much the same way as COST calls are routed in a CTI-enhanced call-center, using similar or identical routing rules, waiting queues, and so on, aside from the fact that there are two separate networks involved. Communication centers having both CTI and IPNT capability utilize LAN-connected agent-stations with each station having a telephony-switch-connected headset or phone, and a PC connected, in most cases via LAN, to the network carrying the IPNT calls. Therefore, in most cases, IPNT calls are routed to the agent's PC while conventional telephony calls are routed to the agent's conventional telephone or headset.

A network-based system known to the inventor enables users of the system to obtain current agent-status information related to agents of an information-source facility connected to the network before initiating contact with the agent or agents of the information-source facility. The system comprises a status-server node connected to the information-source facility (communication center) and to the network, an interface-server node connected to the status node and to the network, the status-server node accessible to the interface node, a user-operated network-capable appliance connected to the network, the interface node accessible to the network-capable appliance, and a software application distributed on at least the status and interface server nodes, the software application enabling distribution of the agent-status information to the user-operated appliance. In some embodiments the system uses IMPP-IETF RFC 2778 protocol.

The user operating the network-capable appliance connects to the network and accesses the interfacing server node and requests the agent-status information, the agent-status information is then accessed from the status server node connected to the communication center by the interfacing server node and delivered to the requesting user over the operating network. Such a system saves phone costs for customers and/or agents as well as reduces utilization requirements of communication-center interface technologies such as IVR technology.

The network-based system described above can, in one aspect, enable communication center agents using the system to obtain current status information related to clients of an information-source facility connected to the network in order to optimize callback connection success from the agents to the monitored clients. The capability is incorporated as an enhancement to the system providing agent status information to clients as described further above.

The system comprises a status-server node connected to the information-source facility (communication center) and to the network, an interface server node connected to the status node and to the network, the interface node accessible to the status server node, a user-operated network-capable appliance connected to the network, the interface node accessible to the network-capable appliance, and a software application distributed on at least the status and interface server nodes, the software application enabling distribution of the client-status information to the agent-operated appliance.

An agent operating the network-capable appliance monitors the network and accesses the status server node and requests the client-status information, the client-status information is then accessed from the interface server node by the status server node and delivered to the requesting agent over the operating network. Such a system saves agent time and communication costs and reduces utilization requirements for communication center interface technologies by automatically providing agents with client real-time activity prior to initiation of service contact.

The above-described system uses a presence protocol such as IMMP-IETF RFC 2778 in order to communicate both the agent status information to a requesting client and to communicate active client status to a requesting agent. In some cases, a third party providing a hosting server within the operating network, which in that case would be the Internet network, hosts the system.

According to another aspect of the above-described system, an application is provided for enabling a client to interact with communication-center resources using IMPP. The application has an interactive client interface component operable by the client for posting client data and for receiving and displaying agent and interaction data from the communication center, a brokering component for managing client and communication center data and communication, and a status monitoring and reporting component for monitoring and reporting communication center and client status. The application is characterized in that a client using the user interface is enabled to access and alter communication center data, and also to initiate live interaction with the communication center.

While presence information is flexible and useful for reporting information about agents to clients and about clients to agents, it has occurred to the inventors that there also exists an opportunity for using such a presence protocol for managing the communication center itself in terms of internal policy, member-to-member communication within the center whether agent-to-agent, machine-to-machine, agent-to-machine, or machine-to-agent.

A presence monitoring and reporting application is known to the inventors and is used in a multimedia communication-center environment to report presence information of networked entities in real time. The application includes a software agent for generating a presence information model; a data store for storing presence information tuples; and a monitor for detecting presence information updates and for synchronizing the updates with information in the data store. In a preferred embodiment the application is deployed and integrated to a communication center infrastructure wherein any given one or more of the entities may singularly or in plural spawn one or more agents whereupon the agents each spawn a container that is populated with current targeted presence and state information in most recent updated form and wherein the updates are synchronized with data in the data store.

It is known to the inventors that multimedia communication centers work with a wide variety of differing media types and in many instances tend to separate those media types into separate queues for management reasons. For example, COST calls and IPNT calls may occupy separate queues as may e-mail and other media events. In more modern IPNT-capable centers, the concept of virtual queuing has recently been implemented in systems known to the inventor, but necessarily prior art at the time of this application. Virtual queuing is a concept of tokenizing information about media events waiting in real queues and processing those events (usually mixed) from the virtual queue by priority of event and other criteria.

It has occurred to the inventors that using presence reporting between communication-center entities can change the way queue information is monitored as well as the way information in the queue is processed with regard to notification of other human and machine entities involved in the processing and with regard to planning resources.

The inventor knows of a software application for recommending workforce resource allocation in a communication center based on requirements of events represented in a communication-center queue. The software application is deployed on a system that has a first interface for accessing information from the queue; a second interface for accessing information from a data source about workforce availability and state information; a processing component for processing queue information and workforce information; and a message generation and delivery component for generating a workforce allocation recommendation based on processing results and sending the recommendation to a target entity.

In a preferred embodiment, the application periodically accesses the queue and the data source to obtain the most recent information for processing, and generates periodic recommendations based on real-time requirements of events and availability states of resources, the recommendations are sent ahead of time before the resources are required.

The inventor knows of prioritized queuing systems both real and virtual as well as several methods for determining queue requirements and allocation or making available resources to fill those requirements. Prioritization criteria for events waiting can be based on client importance, resource availability, skill-level, predictive resource availability, time in queue, and so on.

It has occurred to the inventor that the known methods and criteria for practicing those methods do not particularly address an important problem. For example, priority of event routing of incoming events waiting in existing event-queue systems is typically based on skill level required for processing, client importance, or some combination of these and other criteria. However, messaging queues in such a system often have a persistent latency in handling because although some messages could be quickly processed, they are so low in the priority scheme that they are not attended to for an unreasonable period of time.

What is clearly needed are methods and apparatus for optimizing response time for events waiting in a communication center real or virtual queue by interacting directly with the queue and assigning or modifying priority assignments to events according to a calculated estimated disposal time (EDT). Such a system would function to minimize or eliminate persistent queue latency and provide for better resource planning.

SUMMARY OF THE INVENTION

In a preferred embodiment of the present invention a system for optimizing response time to events or representations thereof waiting in a queue by predicting an estimated disposal time for certain ones of those events is provided, comprising a first server having access to the queue, a software application running on the first server, and a second server accessible from the first server, the second server containing rules governing the optimization. The system is characterized in that the software application at least periodically accesses the queue and parses certain ones of events or tokens thereof contained therein at the time of access and compares the parsed results against rules accessed from the second server in order to determine a measure of disposal time for each parsed event and wherein if the determined measure is sufficiently low for one or more of the parsed events, those one or more events are modified to a reflect a higher priority state than originally assigned, or promoted directly out of queue, enabling faster treatment of those events resulting in relief from those events to the queue system load.

In some preferred embodiments the first server is a work force management and planning server enhanced with the addition of the software application. Also in some preferred embodiments the queue is a virtual message queue for a communication center. In still other preferred embodiments the queue is a telephony queue. In some embodiments the software application includes at least one parsing engine for parsing events, and in some other embodiments the software application includes at least one additional interface to a historical data repository.

In some embodiments the rules governing the optimization process include rules for generation of token events that represent real events. In other embodiments the data parsed includes event type, event status in queue, event routing information, and event origination information. In yet other embodiments the data parsed includes event type, event status in queue, event routing information, event origination information, and event purpose information. In still other embodiments the data parsed further includes event content or a portion thereof.

In still other embodiments of this system the data parsed further includes event content or a portion thereof, and in others an original priority status assignment of low below a certain threshold to an event or representation thereof causes the event to be parsed. In other cases the measure of disposal time determined is an estimate based on known procedure for handling the event, and in yet other cases the measure of disposal time determined is an estimate based on historical averaging of previous measurements for the same originator of an event of a same type. In yet other cases events that are modified to reflect a higher priority state are immediately promoted from the queue to an appropriate final destination queue. In still other cases events that are modified to reflect a higher priority state are immediately routed to their final destinations. In yet other cases a measure of disposal time is taken collectively for a number of events of a same media type and summed as one disposal time for the sum of events or representations thereof considered, the sum compared to available resource load before priority state modification to determine if those resources will be unreasonable taxed.

In another aspect of the present invention a software application for optimizing response time to events or representations thereof waiting in a queue by predicting an estimated disposal time for certain ones of those events is provided, comprising at least one module for determining event type and event state of events or representations thereof, at least one parsing engine for parsing event or represented event data, a calculator for weighing parsed results against pre-set rules, and an event modification module for changing event or represented event state. The application is characterized in that selected events or representations thereof are modified to reflect a higher priority state and, in some cases, different routing rules, including direct promotion from queue, than those originally assigned to those events due to a determination made that those selected events have a sufficiently high probability of efficient disposal in the system according to an estimated time of disposal for each event or representation thereof.

In some preferred embodiments of the application the queue is a virtual message queue for a communication center. In other preferred embodiments the queue is a telephony queue. In yet other preferred embodiments the at least one parsing engine parses event type, event state, and event content. In still other embodiments the application further includes at least one interface to a historical data repository. In still other embodiments the data parsed includes event routing information, and event origination information, and in yet others the data parsed includes event purpose information and event content or a portion thereof.

In yet other embodiments of the software application the criteria for event selection is all events or representations thereof having a low priority assignment valued below a certain priority threshold. In yet other embodiments the measure of disposal time determined is an estimate based on known procedure for handling the event. In still other embodiments the measure of disposal time determined is an estimate based on historical averaging of previous measurements for the same originator of an event of a same type. In some cases events modified to reflect a higher priority state are immediately promoted from the queue to an appropriate final destination queue, and in other cases events that are modified to reflect a higher priority state are immediately routed to their final destinations.

In still other embodiments of the application a measure of estimated time of disposal is taken collectively for a number of events of a same media type and summed as one estimated disposal time for the sum of events or representations thereof considered, the sum compared to available resource load before priority state modification to determine if those resources will be unreasonable taxed. In yet other embodiments the pre-set rules contain rules sets that are different for different media types, and in others some of the rules for optimization govern content to be included when generating token representation of real events.

In another aspect of the invention a method for predicting an estimated disposal time for an event waiting in a queue system comprising steps of: (a) gaining software access to an event; (b) identifying the type of event and state information of the event; (c) weighing state information against a set of rules; and (d) establishing a measure of disposal time from the results.

In some preferred embodiments of the method the queue is a virtual multimedia message queue of a communication center. In other preferred embodiments the queue may be a real multimedia message queue of a communication center. In still others the queue may be a telephony queue. In yet other embodiments of the method, in step (a), queue access is made from an external machine connected thereto by network cable. In still other embodiments, in step (b), the state information includes priority assignment status, time waiting in queue, event origination information, event destination information, event purpose information, and event routing information.

In still other embodiments of the method, in step (c), a scoring system is used to derive values, scoring achieved using an algorithm, and in yet other embodiments, in step (d), the established measure is a derived value equating to an amount of time. In some cases, in step (d), the measure is derived from known processes times. In other cases, in step (d), the measure is derived from current state information after rules comparison and augmented with a historical averaging of estimated disposal times compiled for the same media type and originator.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

FIG. 1 is an overview of a communication network wherein reporting of communication-center presence information is practiced according to an embodiment of the present invention.

FIG. 2 is a plan view of a client-side media-interface containing status information according to an embodiment of the present invention.

FIG. 3 is a flow diagram illustrating client and system procedural steps for practicing communication-center presence reporting according to an embodiment of the present invention.

FIG. 4 is an overview of a communications network wherein agent monitoring of client status is practiced according to an embodiment of the present invention.

FIG. 5 is a plan view of exemplary agent-side media-interfaces 99 and 101 containing availability status and callback parameters according to an embodiment of the present invention.

FIG. 6 is a flow diagram illustrating agent and system procedural steps for observing customer status and call back preferences according to an embodiment of the present invention.

FIG. 7 is a flow diagram illustrating agent and system procedural steps for observing customer status and call back preferences according to an embodiment of the present invention.

FIG. 8 is an overview of a communications network wherein a personal interaction-center system is utilized according to an embodiment of the present invention.

FIG. 9 is a plan view of an interactive user interface served by CIS 119 of FIG. 7 according to an embodiment of the present invention.

FIG. 10 is an architectural overview of a communication center enhanced with an IMP protocol according to an embodiment of the invention.

FIG. 11 is a block diagram illustrating function between software and hardware components of the system of the invention.

FIG. 12 is a block diagram illustrating a multimedia communication center queuing and routing system according to an embodiment of the present invention.

FIG. 13 is a process flow diagram illustrating basic steps of queue processing and resource allocation according to an embodiment of the invention.

FIG. 14 is a block diagram illustrating a multimedia communication center queuing and routing system according to an embodiment of the present invention.

FIG. 15 is a process flow diagram illustrating steps for practice of the present invention utilizing a virtual queue.

FIG. 16 is a process flow diagram illustrating steps for practice of the present invention utilizing a real master queue.

FIG. 17 is a block diagram illustrating the pre-scan software application of FIG. 14 according to embodiments of the present invention.

 DESCRIPTION OF THE PREFERRED EMBODIMENTS

In accordance with a preferred embodiment of the present invention, the inventor provides a novel software-hardware driven system for improving the reporting of communication-center presence information to prospective communication-center clients. The method and apparatus of the present invention is described in enabling detail below.

FIG. 1 is an overview of a communication network 52 wherein reporting of communication-center presence information is practiced according to an embodiment of the present invention. Communication network 52 comprises, in this example, a public-switched-telephone network (PSTN) 55, a data-packet-network (DPN) 61, a communication center 21, and an exemplary user 9.

PSTN 55, in this example, represents a preferred network connecting all connection-oriented-switched-telephony (COST) clients who call into communication center 21 for the purpose of doing business with the center. In another embodiment, a private telephone network may be utilized in place of or in combination with PSTN 55. The inventor chooses PSTN 55 because of its high public-access characteristic.

A local telephony switch (LSW) 59 is illustrated within PSTN 55 and represents automated switching capability within the network. LSW 59 may be an Automatic Call Distributor (ACD), a Public Branch Exchange (PBX), or any other type of telephony switching apparatus, in the broadest sense, including but not limited to DNT type switches/gateways as used in VotP etc. LSW 59 is enhanced for computer-telephony-integration (CTI) by a CTI processor 62 connected thereto by a CTI connection. LSW 59 and CTI processor 62 may encompass various communication functionalities made available at network level by communication center 21. For example, an instance of CTI software known to the inventor and termed Transaction Server (TS) is provided within CTI processor 62 and adapted to enable communication-center 21 to certain call-switching and routing aspects performed by LSW 59. LSW 59 is connected to a central telephony switch (CSW) 53, illustrated within communication center 21, by a COST telephony trunk 57. CSW 53 may be any one of several types of call processing switches as previously described with respect to LSW 59 above.

CSW 53 is enhanced by a CTI processor 65, which is connected thereto by a CTI connection as was described with reference to LSW 59. CTI processor 65 also has an instance of TS software provided therein and adapted to communicate with TS software of processor 62. Processors 62 (network) and 65 (communication center) are connected by virtue of a separate data network 64 enabling the above-described communication between TS instances. By using network 64 to connect processor 62 and 65, communication center 21 may, in addition to controlling call switching and routing within PSTN 55, receive information about callers ahead of actual calls arriving at CSW 53 for internal processing. This enhancement is known as double-dipping by the inventors.

DPN 61 is, in this example, the well-known Internet network and will hereinafter be termed Internet 61. Internet 61 facilitates all Internet-protocol (UP) callers reaching communication center 21 through the Internet. Internet 61 may instead be a private or corporate Wide Area Network (WAN), or any other type of DPN as long as Internet communication protocols are supported. The inventor chooses Internet 61 as a preferred network because of its high public-access characteristic. IP callers calling into communication center 21 may interface from any Internet-connected server, which provides network access to communication center 21. Moreover, there may be many such servers distributed throughout network 61, each server being a point of access.

Internet 61 has an Internet backbone 13 illustrated therein. Backbone 13 represents all the lines, equipment, and connection points making up the Internet network as a whole, including sub networks. A Web Server (WS) 15 is provided within Internet 61 and is connected to backbone 13. WS 15 is adapted as an Internet file server as is known in the art. WS 15 represents one of a possible plurality of distributed customer-interfacing servers as described above. WS 15 serves electronic information pages, termed Web pages in the art, to requesting users. WS 15 is in this example hosted by the entity hosting communication center 21 and is utilized as a customer-interfacing server.

WS 15 is enhanced with a software instance termed Web-Presence-Software (WPS) 16, which enables prospective customers of communication-center 21 to view communication-center status related to agent availability for a call before deciding whether or not to actually place a call to communication center 21. More about WPS 16 is provided later in this specification.

An exemplary user, illustrated herein as a PC icon labeled with the element number 9, is connected to Internet backbone 13 by virtue of an Internet connection-line 11. User 9 is assumed, in this example, to be accessing WS 15 through standard Internet-connection capabilities as are known in the art. Typically, user 9 would obtain access to WS 15 through a dial-up connection utilizing an Internet-service-provider (ISP) and PSTN 55. However, there are many other means which may be used to obtain an Internet session with WS 15, many of which may not require dialing, e.g. DSL, cable modems etc. User 9 may utilize some other Internet-capable appliance than the PC illustrated herein. Likewise, connection line 11 may be a wireless link, a cable-modem connection, or any other known Internet connection means.

An instance of software termed Customer-Presence-Software (CPS) 10 is provided to execute on customer-premise-equipment (CPE), which in this case is a PC operated by user 9. CPS 10 is adapted to integrate communication-center status information into a customer's electronic interface, which is typically an electronic-information-page (Web page) served to the customer by WS 15 upon the customer's request. CPS 10 is an optional implementation in this example and is described in more detail later in this specification.

Communication center 21 has an Internet Protocol Router (IPR) 25 illustrated therein and adapted to handle incoming communication events sourced from WS 15 or any other interfacing Web server over network connection 19. IPR 25 routes incoming events to agent workstations adapted to receive the events. Agent workstations 27, 29, and 31 are illustrated within communication center 21 and adapted for communication-center activity covering both IP and COST transactions.

Agent telephones 39 (workstation 27), 41 (workstation 29), and 37 (workstation 31) are provided to handle COST communication events. Telephones 39, 41, and 37 are connected to CSW 53 by internal telephony wiring 45. Each agent workstation 27, 29, and 31 has a personal computer/video-display unit (PC/VDU) provided therein and adapted for handling IP communication events and for receiving information about callers calling from PSTN 55. These are PC/VDU 33, PC/VDU 35, and PC/VDU 43 respectively.

PC/VDU's 39, 35, and 43 are connected to a Local-Area-Network (LAN) 23. LAN 23 is, in this case, enhanced for Internet communication. IPR 25 is connected to LAN 23 and functions as an event router as previously described above. Other equipment may also be connected to LAN 23 such as a customer information server (CIS), a statistical server, and other communication-center systems and equipment not shown here but assumed to be present. Processor 65 is connected to LAN 23 by a LAN connection 67. In this way, information about COST callers being handled at LSW 59 may be routed over LAN 23 to destination PC/VDUs such as PC/VDU 35 in station 29 for example. Information about COST callers can also be handled by CSW 53 and routed over LAN 23 to destinations.

It will be apparent to one with skill in the art, that there may be many more workstations manned by communication-center agents than are illustrated in this embodiment without departing from the spirit and scope of the present invention. Similarly, there may be many more CTI functions represented herein without departing from the spirit and scope of the present invention. For example, IVR capability may be present at LSW 59, as well as at CSW 53. Automated systems such as automated fax systems and e-mail systems may also be present. There are many possibilities.

A status server 49 is provided within communication center 21 and adapted to monitor agent status and availability for receiving incoming communication events. Status server 49 is connected to LAN 23 by virtue of a LAN connection and monitors status at each workstation 27-31. Software used for this purpose is not illustrated in this embodiment, but may be assumed to be present and operational within server 49. Agents manning stations 27-31 may monitored as to how many calls are in their respective queues whether they are COST queues, IP queues, or virtual queues of either type. Estimated waiting times for each queue of each agent are determined using call-handling statistics available within center 21. The information gathered to be made available to users may also be more extensive in scope, involving status of groups of agents and the like. Server 49 is capable of monitoring the status of each agent in real-time, but for practical purposes, may perform periodic status checks on a frequent basis such that real-time parameters are closely emulated. All current status information for every agent logged on to LAN 23 is compiled by server 49 and maintained as long as it is current.

An instance of Communication-Center-Presence Software (CCPS) 50 is provided within server 49 and adapted to interface with agent-monitoring software per instance of client request initiated through WS 15. Status server 49 is, in this embodiment connected directly to WS 15 by a separate high-speed data link 20. This implementation is not specifically required to practice the present invention; however the presence of link 20 enhances server-to-server communication. In the absence of data link 20, all communication between WS 15 and status server 49 would be conducted over Internet connection line 19, through IPR 25, and over LAN 23.

In practice of the present invention in one preferred embodiment, user 9 accesses Internet 61 over Internet connection line 11 and logs into WS 15. WS 15 serves a Web page as a response to a request from user 9. The Web page requested is hosted by the entity hosting communication center 21 and therefore contains information about communication center 21 including contact links, product information, telephone numbers, and any other pertinent information that may be found on a customer interface. In addition to the more typical information contained in the Web page representing communication center 21, a Web form (not shown) is made available for the purpose of taking a user's status request before requiring the user to place an actual call or initiate any contact with center 21.

The Web form, which is part of WPS 16, allows a user to enter such information as a product description, profile information, or a purpose for the desired contact with communication center 21. WPS 16, upon receiving and registering a request from user 9 sends an instant message/request over high-speed data link 20 to status server 49. CCPS 50 parses the request and obtains the most current status information from server 49 that matches the intent of the request. For example, if user 9 desires to purchase a four-wheel drive pickup, and communication center 21 is a car dealership, then CCPS 50 will only obtain status information connected to those agents within center 21 responsible for four-wheel drive sales.

Once status information is obtained by server 49, it is sent in the form of a response from server 49 to WS 15 whereupon it may be made available to user 9. In another embodiment, the status response may be sent to user 9 along with a subsequent Web page whereupon the information is caused to be a part of the web page at the location of user 9. In this case, CPS 10 would incorporate the information into the display of the subsequent Web page.

In still another embodiment, CCPS 50 may obtain all of the current agent-status information available from communication center 21 and send it to WS 15 over link 20 on a periodic or real-time basis. WPS 16 would, in this case, the enhanced with a filtering capability of filtering status information that closely matches a user request. Also in this case, an instant message would not need to be sent from WS 15 to status server 49. In a simple embodiment, status information viewable by user 9 would include any listed agents, number of calls in their queues, and estimated time waiting for agent availability with respect to each queue. For example, agent JIM may have 5 COST calls waiting, 5 IP calls waiting, and 8 unanswered e-mails. Therefore, agent Jim may be considered unavailable for immediate service. An estimated time waiting for Jim to respond may be averaged over all his media types, or maybe specified for each media type. User 9 may initiate a refresh action in order to obtain an update of status information. Contact links and other options may be presented in association with listed agents and agent status figures.

An interface of the type described above enables users to essentially browse agent-availability statistics before initiating any type of contact with communication center 21. In the event that a response message or downloaded interface reveals an available agent, user 9 could initiate contact with that agent using provided contact links or information.

It will be apparent to one with skill in the art that there are many configuration possibilities that exist with respect to reporting agent-availability status of agents within communication center 21 to requesting user 9 without departing from the spirit and scope of the present invention. Instant messaging or embedding the information into Web pages before or after download are techniques which may be employed to practice the present invention. Likewise, the status information may be made a part of a Web browser's tool bar or caused to open in an interactive window that pops up on a user's screen when the data is ready for display. In still another embodiment user station 9 may contact IPR 25 via connection 11, 13, 19 and retrieve pertinent information maintained through CCPS 50. This data may be displayed independently or integrated with a Web page from server 15. The functionality of WPS 16 at Web server 15 in retrieving information from communication center 21 via CCPS 50 is but a single example of how a system according to the present invention may function. It has been described that similar functionality may be provided by CPS 10 at a client station, and that there is no limitation to the client station operating only through a Web server. In a broad sense, the means of communication of client station 9 with communication center 21 is not limiting to the invention. The cooperation of gathering software (CCPS 50) at a communication center with an interface software (CPS 10) at a client station is novel.

In a further aspect, there are a variety of ways that the client stations in such a system may become enabled. In the system wherein retrieval of communication center status info is by software (WPS 16) at server 15, there is no need for additional software at the client station. A conventional browser will do. In the cases wherein software CPS 10 is enabled at a client station, that software may be sent to a client on a CD (for example), sent to the client in the background on accessing a Web page at server 15, downloaded intentionally by a client at station 9 as a plug-in to a Web browser, and in other ways as well.

FIG. 2 is a plan view of a client-side media-interface 69 that contains status information according to an embodiment of the present invention. Interface 69 is an exemplary representation of a customer interface displaying agent-availability status after it has been requested and delivered. Interface 69 may be an integrated part of a Web page (incl. e.g. script, Java, Java script, X-Windows script, plug-in etc. etc.), a pop-up information window, an instant message interface, or any other mechanism of computerized display.

In one embodiment, interface 69 is a product of CPS 10 of FIG. 1. In this embodiment, WPS 16 of FIG. 1 sends agent-availability information to user 9 over Internet connection 11, 13, 19, and CPS 10 incorporates information into an interactive display-window or into the actual Web page served by server 15. In another embodiment, interface 69 is a product of WPS 16 in FIG. 1 and is embedded into the actual Web page before it is served to user 9. In still another embodiment, interface 69 is a product of WPS 16 and is served to user 9 in the form of a standard instant-message interface using any of several known protocols. In this basic example, agent-availability status is generalized to a group of agents and displayed as 3 parameters. These are a number of available agents 71, a number of calls waiting 73, and an estimated hold time 75. In this case the information represents the most basic information available for the target group of agents. In this case there are 12 available agents that are handling the subject of request resulting in interface 69. There are 25 calls waiting in a queue shared by the 12 available agents. The average estimated hold time for one of the 12 agents to respond to an immediately placed call is 2 minutes and 10 seconds. In this example, three interactive options are presented within interface 69, in this case, below the agent-availability information. A contact option 72 is provided to allow a viewing customer to initiate an IP-to-IP telephone call, or an IP-to-COST telephone call. A contact option 74 enables a viewing customer to send an e-mail, which would be routed to one of the 12 available agents. A contact option 76 enables a viewing customer to initiate a callback from one of the 12 available agents. Using callback option 76 enables an invoking user to be entered into a virtual queue. A user in this case may expect a callback at approximately 2 minutes and 10 seconds after initiating the contact. In actual practice, the availability and variety of interactive contact options is dependent upon enterprise rules and available media. One with skill in the art will recognize that there are many alternative display scenarios which may be used with interface 69.

In a more advanced case, interface 69 may contain much more detailed information including information that a specific to a user request invoking the interface. For example, each of the available agents 71 may be listed separately instead of collectively as illustrated herein. The number of calls waiting may be broken down to reflect the exact number of calls waiting for each available agent. Furthermore, estimated hold times may be determined individually for each busy agent. Likewise, additional information about agents may be listed such as skill levels, language preferences, ranking within the organization, and so on. The level at which detailed agent-availability data may be compiled and presented depends entirely on the sophistication and configuration of agent monitoring software in use within communication center.

FIG. 3 is a flow diagram illustrating client and system procedural steps for practicing communication-center presence reporting according to an embodiment of the present invention. At step 77, the user logs onto a DPN, which in a preferred case, is the Internet network. At step 79, the user of step 77 navigates to a Web site hosted by a communication center that the user desires to contact. At this point, a Web form may be present on a main Web page of the Web site navigated to in step 79. Such a Web form would prompt a user for his or her intent or reason for the desired contact. These reasons are as wide-ranging as are enterprises that might host such a Web form. For example, a list of product descriptions may be presented for selection. Levels of contact priority may be established in the case of priority queuing, amongst others possibly based on user ID. Available options are limited only by enterprise rules.

At step 81, a user enters the information solicited from him or her by the above-described Web form. At step 83, the user submits the Web form. At step 84, a Web presence server analogous to Web server 15 of FIG. 1 receives the request sent by the user of step 83. At step 85, the Web presence server forwards the request received in step 84 to a communication-center presence server analogous to server 49 of FIG. 1.

At this point, software analogous to CCPS 50 of FIG. 1 analyzes the received request and pulls the most current agent-availability data for the purpose of servicing the request. At step 86, the applicable data is sent in the form of a response back to the Web presence server of step 85. It is noted herein, that this communication between servers may occur over a separate high-speed data line as was described in reference to FIG. 1 above. Moreover, the server-to-server transaction may follow known request/response models used in Internet transactions.

When the applicable data is received at the Web presence server, software analogous to WPS 10 of FIG. 1 may integrate the information into a subsequent Web page to be sent back to the user of step 77, or it may formulate the response as an instant message, which is immediately dispatched act to user 77. At step 87 then, the applicable data is delivered to the user of step 77 and is displayed as an interactive interface analogous to interface 69 of FIG. 2 at step 89. At this point, the user of step 77 may initiate contact with the target communication center or wait for a better time for contact initiation based on user-analysis of the received data. It is also noted herein that the user requesting the data may refresh his or her request periodically to obtain the most current agent-availability data during a session period. In some cases, the requesting user may receive streaming data in real-time showing continual changes in agent-availability status over the time spent viewing the interface.

It will be apparent to one with skill in the art, that the customer/system process steps illustrated in this example may be altered in description and order without departing from the spirit and scope of the present invention. For example, the Web presence server of step 84 may have a local access to the most current agent-availability data at the instant of receiving a request. This was described an embodiment wherein agent-availability data from the target communication center is periodically pushed or continually streamed to the Web presence server. Moreover, the agent-availability data may be integrated into a Web page at server side or client side dependent upon software implementation. In one embodiment, the entire transaction process from request to response and display is conducted using an instant message protocol.

The method and apparatus of the present invention may be practiced on the Internet, a private or corporate WAN or LAN network or in any combination thereof. Web server 15 of FIG. 1 may be hosted by a single communication center or shared by a plurality of communication centers. In the latter case, it is more likely that agent-availability data will be pulled from the providing communication centers rather than pushed to the central location.

Client-Status Monitoring Capabilities

In another aspect of the present invention an enhancement is provided that enables agents operating from within communications-centers to monitor client availability status for the purpose of callback optimization. In particular, in cases where the client has many media available, a collection of all media statuses is generated, and then presented as an amalgamated status to an agent or robotic agent. Additionally, the preferred mode and time for a back connection may be available as well.

In one aspect of the system, client on-/off-line status information and the client's callback preferences are obtained at the same time using the same protocol. In another aspect of the system, client on-/off-line status information and the client's callback preferences are obtained independently, for instance using a presence service such as ICQ™ for the on-/off-line status information and HTTP or WAP for obtaining the client's callback preferences, or for instance during a previous communication between the client and an agent of the communication center.

In one aspect of the system, client-status information is obtained from a single client terminal, such as a PC. In another aspect of the system, partial client-status information is obtained from multiple independent client terminals, such as a PC and a cellular phone, and combined to provide complete client-status information to the subscribing agent. In one aspect of the system, client on-/off-line status information is obtained concerning a single terminal device, such as a PC. In another aspect of the system, client on-/off-line status information is obtained concerning multiple independent terminal devices, such as a PC and a cellular phone, and combined to provide complete client on-/off-line status information.

In one aspect of the system, client-status information is obtained using a single protocol, such as ICQ™. In another aspect of the system, partial client-status information is obtained using multiple protocols, such as ICQ™ and MSN Messenger Service™, and combined to provide complete client-status information to the subscribing agent. In one aspect of the system, client-status information is obtained via a single network, such as the Internet network. In another aspect of the system, partial client-status information is obtained via multiple networks, such as the Internet network and the cellular network, and combined to provide complete client-status information to the subscribing agent.

FIG. 4 is an overview of a communications network 92 wherein agent monitoring of client status is practiced according to an aspect of the present invention. Communication network 92 is somewhat analogous to communications network 52 of FIG. 1 above in terms of basic architecture and software implementation. Elements of network 52, which are not modified for the purpose of enabling the present invention, are not reintroduced with new element numbers. Newly provided or modified elements used in the practice of the present invention are introduced herein having new element numbers.

Communication network 92 comprises PSTN 55, DPN 61, communication center 21, and an exemplary user 9 as described above with reference to network 52 of FIG. 1.

PSTN 55, as described in the example of FIG. 1, represents a preferred network connecting all connection-oriented-switched-telephony (COST) clients whom call into communication center 21 for the purpose of doing business with the center. In another case, a private telephone network may be utilized in place of or in combination with PSTN 55. The inventor chooses PSTN 55 because of its high public-access characteristic.

LSW 59, illustrated within PSTN 55 and represents automated switching capability within the network. LSW 59 may be an Automatic Call Distributor (ACD), a Public Branch Exchange (PBX), or any other type of telephony switching apparatus, in the broadest sense, including but not limited to DNT type switches/gateways as used in Voice over IP (VoIP) etc. as was previously described. LSW 59 is CTI enhanced by CTI processor 62 connected thereto by a CTI connection. TS software provided within CTI processor 62 enables communication center 21 to control certain call-switching and routing aspects performed by LSW 59 as was described in FIG. 1.

LSW 59 is connected to CSW 53, illustrated within communication center 21, by COST telephony trunk 57. CSW 53 may be any of several types of call processing switches as previously described with respect to LSW 59 above. CSW 53 is enhanced by CTI processor 65, which is connected thereto by a CTI connection as was described with reference to LSW 59. CTI processor 65 also has an instance of TS software provided therein and adapted to communicate with TS software of processor 62. Data network 64 provides a capability of double dipping described in FIG. 1 above. Internet 61 facilitates all Internet-protocol (IP) callers reaching communication center 21 through the Internet. Internet 61 may be a private or corporate Wide Area Network (WAN) or any other type of DPN as long as Internet communication protocols are supported. The inventor chooses Internet 61 as a preferred network because of its high public-access characteristic, as stated with reference to FIG. 1. IP callers calling into communication center 21 may interface from any Internet-connected server, which provides network access to communication center 21. Moreover, there may be many such servers distributed throughout network 61, each server being a point of access. Internet 61 is represented by Internet backbone 13, which represents all the lines, equipment, and connection points making up the Internet network as a whole, including sub networks.

Status server 49 is illustrated in this example as having a communication-center-presence-server CCPS 94 (software) installed therein, which is an enhanced version of CCPS 50 described in the example of FIG. 1. CCPS 94 not only provides clients with agent status information over the WWW, but also allows agents working within center 21 the capability of subscribing to client status information. More detail regarding the just-described enhancement is provided below.

In this example, there are 2 exemplary file servers illustrated as connected to Internet backbone 13. These are a customer presence server (CPS) 95 and a foreign presence server (FPS) 93. It is noted herein that CPS 95 effectively replaces WS 15 of FIG. 1 and can be assumed to provide the formerly-described functionality of server 15 and associated web presence server (WPS software) 16 of the same example. CPS 95 functions as a file server enhanced with an instance of software (SW) 97, which may be described, in this embodiment as CPS software 97. CPS server 95 is, in this example, hosted by the same entity hosting communication center 21 and is utilized as a customer/agent interface.

CPS SW 97 is enhanced for the purpose of allowing an agent to subscribe to real-time customer availability information as it applies to the remote station occupied by the customer. In this case, the station refers to remote PC 9, also referred to as user 9 in this specification. User 9 is connected to backbone 13 by Internet-access line 11, as was described with reference to FIG. 1. CPS 95 is optional in this example and not specifically required in order to practice the present invention. CPS 95 represents a collection server that is utilized for collecting and organizing user status-states, which may be subscribed to or otherwise accessed by agents of center 21.

FPS server 93 is adapted as a third-party server similar to those employed by well-known chat and instant messaging services. FPS 93 may be assumed to have software installed therein, and is adapted to organize instant communication between clients using a supported instant messaging service operating under a known protocol such as RFC2778 as was described in the example of FIG. 1. It is noted in this example, that CPS server 95 is connected to status server 49 within communication center 21 by high-speed data connection 20. A second high-speed data connection 19 is provided for connecting FPS server 93 to status server 49. In this respect, status server 49 has access capability to both CPS 95 and FPS 93. It is similarly noted herein, that high-speed data-access lines connecting server 49 to servers 95 and 93 are not required in order to practice the present invention. Server 49 may instead of adapted to connect to Internet backbone 13 using a 24×7 or a switched Internet connection.

In this embodiment, CPS 95 is hosted by center 21 and adapted to function in much the same way as FPS 93. That is to say that CPS 95 is a central facility for interaction. In one embodiment of the present invention, CPS 95 is not present and CPS SW 97 is instead distributed directly to client machines, as in this case, CPS SW 97 illustrated as installed in PC 9. It is noted herein that the functionality of CPS 10 of FIG. 1 is included in the enhanced version, or CPS SW 97 shown on PC 9. In the absence of server 95, with client machines enhanced by SW 97, CCPS 94 interacts directly with the customer.

User 9 may be assumed, in this example, to be accessing either FPS 93, or CPS 95 for the purpose of determining agent status information as described in FIG. 1 and for making status information available to subscribing agents.

IPR 25 handles incoming message events sourced from FPS 93 and/or CPS 95. Other than enhanced functionality represented by server 49 running CCPS 94 and dual connection capability from server 49 to CPS 95 and FPS 93, communication center 21 operates identically to the center (21) described in FIG. 1 including the configuration of agent's workstations and so on. Therefore, detailed re-description of the agent's operating environment (workstations, LAN connectivity, etc) need not be provided in this example.

In one embodiment of the present invention, PC 9 has a known instant-messaging software application installed therein and adapted to use FPS 93 as a centralized communication server. An example of one such messaging service would be the well-known ICQ™ service. In this case, CCPS 94 running on status server 49 is adapted to support the particular instant-messaging application employed by user 9 and supported at FPS 93. The instant-messaging application is, of course, assumed to be executing on the client machine, shown here as FPS-SW 97. For example, CCPS 94 may be adapted to recognize various descriptive states-of-activity represented at FPS 93 and associated with real-time communication states of connected users, in this case user 9. Examples of such states available through instant messaging services include indications of whether user 9 may be off-line or online. Other status indications such as “user is away” or “do not disturb” may also be included as standard status indications available with known messaging services.

CCPS 94 may be adapted to integrate an enhanced package of status indicators associated with communication-center use into software running on FPS 93 and on user station 9 such that user station 9 may communicate a variety of enhanced status messages to subscribing agents within communication center 21. It is also noted herein, that the functionality of agent-status indication as taught in FIGS. 1-3 above may be integrated into software at FPS 93 and at user station 9 without departing from the spirit and scope of the present invention. One example of an enhanced user-status indication that may be associated with communication center 21 may be an indication that user 9 is temporarily away and preferred contact is by cellular phone during this status period. Of course, the cellular phone number of user 9 would be provided as part of the indication. A communication-center agent, for example, an agent operating PC 43 within workstation 31 may subscribe to FPS 93 utilizing LAN 23, server 49, and high-speed data link 19.

In this case, the agent in question may be in various states of communication with a plurality of users connected to have FPS 93. According to a push model, user-status indications may be pushed in the form of periodic instant messages to PC 43, where they may be viewed by the monitoring agent. The monitoring agent may decide which callback options are appropriate based on user-status indication contained within the content of the instant message. That may be done by other protocol than just IM, e.g. HTTP, WAP, IPNT etc.

According to a pull case, the agent operating PC 43 may subscribe to an interface (not shown) served by FPS 93 such that current status indications are contained within the interface and viewable on PC 43. In this embodiment, status server 49 executing CCPS 94 provides interactive interfaces for both clients and agents for the purpose of viewing status. Also in this embodiment, status server 49 executing CCPS 94 may facilitate COST outbound dialing from agent to client through CSW 53 by virtue of connection 51.

An agent operating at one of connected workstations 27-31 may subscribe to real-time status reports associated with a plurality of users connected to FPS 93. Subscription may be defined as an active state of dialog established between an agent and the connected users. The dialog states may be initiated and established by users contacting agents through the method of the present invention. Therefore, users who have connected to FPS 93 and have initiated contact with an agent of communication center 21 may be considered for status reporting until the purpose of the dialog is achieved or the user is no longer connected to FPS 93.

In some cases, the agent user will not be a human agent but will be a special purpose server (not shown) providing some very specific services. One example of such a special server is a callback server that automatically initiates callback calls to a customer 9 based on that user's callback preferences and routes the call to an agent after the customer answers. Another example of such a special purpose server is a server that monitors the communication center's status and, on request of the customer 9, sends an alert to the customer when the communication center's status matches specific conditions, for instance when the average waiting time is smaller than three minutes.

In a preferred embodiment, there can be multiple FPS and CPS servers in network 92. There can for instance be one FPS 93 for every third-party presence service that is being used in the communication center. There can be for instance an FPS 93 that is able to obtain the cellular on-/off-line status of the customer's mobile (not shown).

In another embodiment, the customer can have multiple terminal devices such as a PC 9 and a cellular phone (not shown). For each type of terminal equipment there can be a different FPS 93 to obtain the on-/off-line status of the customer. By combining these partial statuses (SW not shown), for instance in CCPS 94, a complete customer status can be presented to the subscribing agent. In one aspect, the CCPS 94 can combine the presence information of the customer. In another aspect, the customer's PC 9 can combine the presence information. Take for instance the case where the PC is equipped with a modem-board and where the customer's telephony is also connected to that same modem-board. In this case, the client's PC 9 can combine the client's on-/off-line status for the customer's fixed line and for the customer's internet access and his ability to participate in a chat session or a net-meeting, etc.

In some cases the agent doesn't necessarily have to subscribe for agent status info to the CPS or FPS, the CCPS could take over this job (e.g. agent doesn't use IMPP to subscribe but proprietary protocol). In the latter case the CCPS could subscribe to the CPS or FPS. Generally, it is better to have a call center node subscribe to all different types of CPS and FPS nodes, because there is a need or preference, to combine the customer status information from those different nodes into one presentation for the agent. In some other cases, this CCPS functionality could run on a dedicated node, could be combined with other functionality on a separate node (e.g. embedding the status information in web-page), could run on the agents workstation (or node in case of automated agent), etc.

In another aspect of the present invention, CPS 95 executing CPS SW 97 functions as a status broker in much the same way as FPS 93. The exception being that CPS 95 is provided as a dedicated customer interface for the sole purpose of communication with communication center 21. In this aspect, the instant messaging application, SW 97, is proprietary and contains all of the status options and communications options supported by center 21 and does not have to be integrated with an existing instant messaging service. Provision of CPS 95 executing CPS SW 97 enables an agent operating one of workstations 27-31 within center 21 to subscribe to a single interface containing real-time or periodically updated status reports concerning all of the connected users which may be in dialog with the agent. In one embodiment, instant messages may be propagated in a push model as described above, instead of having subscription to an interactive interface.

Although in many cases the agent will not be communicating synchronously with the customer while receiving these customer's status info, it is possible to allow that, for example in cases where both the agent and the client need to do something, while communicating as well.

As previously described above, CPS 95 is optional and is intended to represent the central “place of status exchange” between agents and users, including but not limited to requests, etc. for dialog. According to another embodiment of the present invention CPS SW 97 is distributed directly to client PC stations similar to PC 9 as illustrated herein. In this case, status server 49 executing CCPS 94 functions as an instant message broker (i.e. proxy) between agents operating workstations 27-31 and users represented herein as user 9. In this case user 9 would log into a web server analogous to web server 15 of FIG. 1 for the purpose of initiating contact with communication center 21. Because and interfacing server is used to interface a plurality of users to communication center 21, both instant message type status reports and status reports contained with an electronic information pages (web pages) are possible.

In some cases, signaling may be sent over the IM protocol, although typically, the other media will provide their own protocol, which will be used respectively, such as H.323 or SIP for IPNT.

In still another embodiment, user 9 initiates direct contact to communication center 21 by virtue of a client-installed version of CPS SW 97, which would contain all of the appropriate contact mechanisms needed to effect IP-to-IP or IP-to-COST connections over the appropriate network paths to center 21. In this embodiment, server 49 executing CCPS 94 may still be used as an agent-interface server, to which agents operating stations 27-31 may subscribe to be in order to view current user status, including but not limited to IP-to-IP events. It is noted herein, that IP-to-COST events would arrive at communication center 21 after having been routed through PSTN 55 through an appropriate gateway. However, when such events arrive at CSW 53 for internal routing, a channel may be opened from server 49 to the node, which is in this case PC 9, from which the incoming event originated if the addressing information is included in the arriving COST event. In this scenario, an agent may interact with a user from a COST telephone and view that user's status information simultaneously. If for some reason the agent must terminate the call, the agent may still subscribe user's online status through the connection established to PC 9 by server 49. Even though there is no active communication between the contacted agent and the initiating user status regarding connectivity state, callback instructions, and so on is immediately available to the contacted agent. Similarly, agent availability and estimated time of response reports associated with the contacted agent are available to user 9 as long as the connection between user 9 and server 49 is open.

In another embodiment, the on-/off-line status information for user 9 will reach the communication center 21 independently from the callback preference information for that user 9. In one aspect, user 9 can be invited to fill out some form on a web page in order to specify callback preferences. In still another aspect, an agent can be feeding the customer preferences to the system during a communication with that customer 9. In these aspects, the callback preference information can be combined with the on-/off-line status information. In one aspect, the web page can be accessed by the customer using a PC. In another aspect, the web page can be accessed using a mobile device that is for instance WAP enabled. In one aspect, the web-page can be hosted by the FPS 93 or the CPS 95. In another aspect, it can be hosted by another server (not shown).

In still another embodiment, the customer's preferred third-party presence service can be part of the callback preferences. There are many third-party presence services such as, but not limited to, ICQ™ and MSN Messenger Service™. A user 9 that is a member of one these presence services, can allow agents of the communication center to monitor it's presence status by communicating it's preferred presence service to the communication center. In an aspect of the invention a customer that isn't a member of a third-party presence service can be allowed by the communication center to download the tools for a communication center specific presence service.

FIG. 5 is a simplified logical connection diagram illustrating functionality of principally software elements in an embodiment of the present invention. In FIG. 5 CCPS 119 is illustrated as operable in a communication center 117 for receiving status from client devices and other information to be provided to agents. As described above, the agents may be live agents or robotic agents.

In FIG. 5 there are two clients (persons) labeled Client 1 and Client 2. There are four client devices 129, 133, 137, and 125, shown in FIG. 5. Client 1 has a PC 129 at his home, which executes an instance of FPS-SW 131, which is, in this case, AOL. Client 1 also has a PC 137 at his office executing an instance of CPS-SW 195. CPS-SW 139 is provided by the host of communication center 117. Further, Client 1 has a WAP telephone 125 executing an instance of FPS-SW 127, provided by Sprint in this example. Lastly there is a second client (Client 2) operating a PC 133, the PC executing an instance of FPS-SW 135, in this example also AOL.

A first Foreign Presence Service Server (FPSS) 121 monitors both instances of AOL (and any other instances at client premises not shown), and provides presence information to CCPS 119, which is enabled for AOL and is executing in communication center 117. A second FPSS 123 monitors WAP telephone 123. CCPS 119 monitors CPS-SW 139 executing on PC 137, although alternatively, there may be an intermediate Client Presence Service Server between PC 137 and CCPS 119, not shown here. Furthermore, in some cases additional servers maybe inserted as proxies etc. between for example FPSS 121,123 and CPSS 119 etc., not shown here.

It may be assumed, for example, that Client 1 in FIG. 5 may move between his PCs and carry his WAP telephone with him, being variously connected and available through the three client devices 125, 129, and 137. Real time monitoring of all of these devices by CCPS 119 directly and through FPSS instances provides valuable information to a real or robotic agent associated with Center 117, together with client preference information which may be achieved by any of several paths, as described above, in real time or according to pre-programmed preferences. The ability of agents, real or robotic, to respond to client's needs is therefore greatly enhanced. The skilled artisan will recognize that both FIG. 4 and FIG. 5 are greatly simplified illustrations, and there may be many more clients, client devices, and instances of FPS and CPS servers and software involved in many ways. The diagrams and accompanying descriptions are provided to convey the essentials of the invention and its functionality.

It will be apparent to one with skill in the art, that the method and apparatus of the present invention may be applied to a variety of connection scenarios without departing from the spirit and scope of the present invention. Similarly, the software of the present invention may be provided in a variety of functionalities ranging from an extendable application program interface (API) to an existing instant-messaging service to a fully functional server-driven service application including client-side and server-side components.

It will also be apparent to one with skill in the art, that instant messages following standard instant message protocol can be sent back and forth between subscribing agents and clients without departing from the spirit and scope the present invention. In addition to instant messaging, status alerts may take the form of pager messages or other types of known alerts when a client status is determined to be off-line.

FIG. 6 is a plan view of an exemplary agent-side media-interfaces 99 and 101 containing availability status and callback parameters according to an embodiment of the present invention. Interface 99 may take the form of instant message, a messaging window integrated into an electronic information page (web page), or any other graphics interface that may be propagated over network lines to subscribing devices. In this simple example, Joe Customer has a status of ONLINE and the requested callback medium of voice over Internet protocol (VoIP). Other callback mediums listed in interface 99 include a COST medium and a Pager medium.

In a one case, an agent subscribes to the status of Joe Customer during a dialog session typically initiated by Joe Customer. Interface 101 is analogous informed to interface 99 with the exception that the indicated status is OFFLINE. The status depicted in interface 101 is an indication to a subscribing agent that Joe is no longer connected to an interfacing server on the network. If Joe is connected to the network but no activity is recognized for a predetermined period of time, Joe's status may be determined to be AWAY. In this example, interface 101 depicts a pager medium as a preferred callback option.

In another case of the invention, a single agent may subscribe to a plurality of customer status messages simultaneously such that he or she may manage outbound calling in a more optimal fashion. Moreover, because the messaging is bi-directional Joe may receive alerts or messages indicating estimated waiting time for a callback, or perhaps instant message data that resolves the current dialog between Joe and an agent. In the latter case, instant messaging may be used to dispose of calls.

FIG. 7 is a flow diagram illustrating agent and system procedural steps for observing customer status and call back preferences according to an embodiment of the present invention. At step 107, a communication-center agent subscribes to customer presence server 95 of FIG. 4, in this case, through status server 49 within communication center 21 described in FIG. 4. It is assumed in this step that the subscribing agent already has at least one customer who has initiated contact with the subscribing agent through server 95. It may be that the subscribing agent is working with a plurality of customers also connected to server 95.

At step 109, the subscribing agent is served one or more instant messages containing customer status information. In one embodiment, a single interface such as a web page containing status data categorized for each customer the agent is working with is served at step 109. In this case, status information related to each customer the agent is subscribing to may be contained in separate windows or lists available within interface. In another embodiment, the subscribing agent may select a customer and receive an instant message regarding that customer's status.

At step 111, the subscribing agent observes the customers' status relating to whether the customer it is online or off-line. At step 113, the subscribing agent observes the customer's call back preferences, which may very according to the customer's connection status. Call back preferences may include but are not limited to IP phone, cellular, e-mail, pager, COST telephone, interactive chat, and so on. At step 115, the subscribing agent takes action based on the customer's status and stated call back preferences.

In one case of the invention, CPS 95 may be facilitated as sort of a callback queue wherein a plurality of the agent's customers may be directed to if the agent of contact happened to be busy at the time of contact. During the period of waiting, customer status and call back preferences are propagated to the subscribing agent and estimated times of response and other information they be propagated to the waiting customers. Flexibility exists in this embodiment in that unlike any normal call-waiting queue, the customer is free to move about and even disconnect from the network and go about normal business while waiting for a callback.

In the case of a customer terminating his connection with server 95, the subscribing agent will be served an instant message reflecting the customer's off-line status and a medium wherein the agent may contact the customer off-line such as a COST telephone, a pager, or some other off-line medium.

In another case of the invention, a priority state may be applied to the plurality of customers waiting for a response from a particular agent. In this embodiment, the customers may subscribe to estimated-waiting time alerts regardless of whether they are online or off-line. For example, a customer may indicate that an alert be sent to his or her paging device approximately five minutes before an agent is estimated to respond by calling the customer on his or her cell phone the event that the customer has gone off-line from the interfacing server. The subscribing agent is served the off-line status, which includes the preferred call back medium and the appropriate cell phone number to call. The page alert to the customer they be propagated by the interfacing server if the server is equipped with outbound dialing capability into a telephony network. In this case the server has the communication-center status information of the agent including the estimated times for the agent to handle his or her calls in queue.

The method and apparatus of the present invention may be practiced over a communications network comprising any combination of Data-Packet, COST, and wireless networks utilizing appropriate gateways without departing from the spirit and scope of the present invention. Moreover, many variations of customer states and agent states may be included as options for configuration into the software the present invention. For example, a client may configure as many devices into the system as desired for enabling agent callbacks under a variety of circumstances. Similarly, an agent may subscribe singularly or in a plural sense to specific customer states.

In still another case of the invention, a central server such as CPS 95 of FIG. 4 may be dedicated to communication-center 21 such that all interfacing customers have status interfaces which are available to all subscribing agents. In this case, subscribing agent may browse and subscribe to selected customer states based on agent/customer match-up. For example, a subscribing agent specializing home loans for example, may log into the system and subscribe to any customers connected the system who have initiated an inquiry to communication center 21 regarding loans. There are many variant possibilities.

Personal Interaction Client-Center Interface

According to another aspect of the present invention, a personalized client-center interface is provided, which in addition to accommodating the agent/client presence services described above, provides an interactive capability to clients for the purpose of enabling the client to perform a number of communication-center related tasks without involving agent interaction. In one embodiment, for example, the client is enabled to access information at the communication center, and to check thereby the status of a transaction. In this and other embodiments a client can access a variety of other information, and interact with communication center capabilities in a number of ways. The method and apparatus of the present invention is enabled in various embodiments by the teachings presented below.

FIG. 8 is an overview of a communications network 177 wherein a personal interaction-center system is utilized according to an embodiment of the present invention. Communications network 117 is somewhat analogous to communications network 92 of FIG. 4 above in terms of basic architecture and software implementation. Elements of network 92 which are not modified for the purpose of enabling the present invention are not re-introduced with new element numbers. Communications network 117 comprises PSTN 55, DPN 61, communication center 21, and an exemplary user 9 as described above with reference to network 92 of FIG. 4.

PSTN 55, as described in the example of FIG. 4, represents a preferred network connecting all COST clients who call into communication center 21 for the purpose of doing business with the center. PSTN 55 is connected to the communication center 21 through COST telephony trunk 57 and data network 64.

In this example there are 2 exemplary file servers illustrated as connected to Internet backbone 13. These are a customer presence server (CPS) 95 and a customer interaction server (CIS) 119. It is noted herein that CPS 95 is identical with CPS 95 described in FIG. 4, and can be assumed to provide the formerly described functionality of server 95 and associated web presence server software 97 of the same example. CPS server 95 is, in this example, hosted by the same entity hosting communication center 21 and is utilized as an agent/customer interface.

CIS 119 is provided as a single example of a way in which the functionality of the present invention may be implemented. There are a number of other ways within the spirit and scope of the invention that this may be done, such as by utilizing the functions described above provided by WS 15 of FIG. 1 with those of FPS 93 of FIG. 4. The overall functionality may also be provided by utilizing the functions of WS 15 with those of CPS 95. Further, there is no implication here that the user interface, in the case of a Web page, by hosted by a third party. The descriptions of the functions of CIS 119 in great detail in the following material is to be construed in this light, that there needs be an interface, and that described is exemplary, and that the functions may be provided differently within the spirit and scope of the invention.

CPS SW 97 is enhanced for the purpose of allowing an agent to subscribe to real-time customer availability information as it applies to the remote station occupied by the customer. In this case, the station refers to remote PC 9, also referred to as user 9 in this specification. User 9 is connected to the Internet backbone 13 by access line 11, as was described with reference to FIG. 4. CPS 95 represents a collection server that is utilized for collecting and organizing client status information, which may be subscribed to or otherwise accessed by agents of communication center 21. CPS 95 is optional in this example and not specifically required in order to practice the present invention as will be described below.

It is noted in this example, that CPS server 95 is connected to status server 49 within communications center 21 by high-speed data connection 20. A second high-speed data connection 22 is provided for connecting CIS server 119 to status server 49. In this respect, status server 49 has identical high-speed access capability to both CPS 95 and CIS 119. It is similarly noted herein, that high-speed data-access lines connecting server 49 to servers 95 and 119 are not required in order to practice the present invention. Server 49 may instead be adapted to connect to Internet backbone 13 using such as a switched Internet connection.

In this embodiment, CPS 95, enhanced by CPS SW 97, is hosted by communication center 21 and adapted to function in much the same manner as CIS 119. That is to say that CPS 95 is a central facility for interaction. Agents 27, 29 and 31 may be assumed, in this example, to be accessing either CIS 119, or CPS 95 for the purpose of determining client status information and for making status information available to servicing agents.

IPR 25 handles incoming message events sourced from CIS 119 and/or CPS 95. Other than enhanced functionality represented by server 49 running CCPS 94 and dual connection capability from server 49 to CPS 95 and CIS 119, communication center 21 operates identically to the center (21) described in FIG. 4 including the configuration of agent's workstations and so on. Therefore, detailed re-description of the agent's operating environment (workstations, LAN connectivity, etc.) will not be provided in this example.

Agents 27, 29 and 31 may be assumed, in this example, to access either CIS 119, or CPS 95 for the purpose of determining client status information in a similar manner as that described in FIG. 4 above so that the information can be used for optimizing call-back scenarios. It is again noted that in the absence of CPS 95, its function may be assumed to be provided to server 119.

IPR 25 handles incoming message events sourced from CIS 119 and/or CPS 95. Other than enhanced functionality represented by server 49 running CCPS 94 and dual connection capability from server 49 to CPS 95 and CIS 119, communication center 21 operates identically to the center (21) described in FIG. 4 including the configuration of agent's workstations and so on. Therefore, detailed re-description of agent's operating environment (workstations, LAN connectivity, etc.) will not be provided in this example.

A distributed software application is provided to reside in one part on server 119 as software (SW) 121 and in one part as software (123) residing at remote station 9. SW 121 is adapted to enable a user operating station 9 through SW 123 to subscribe to a personalized and interactive activity interface (SW 121). It is noted herein that while not required, SW 121 may incorporate the presence reporting capabilities taught in the examples of FIG. 4 (SW 97) and of the example of FIG. 1 (WPS 16). The inventor intends that the three capabilities taught, customer presence reporting, agent presence reporting, and personalized client interaction capabilities may be combined, if desired, into a single distributed software implementation namely SW 121 and SW 123. However, one with skill in the art will recognize that each capability taught may be separately implemented by both hardware and software provisions.

In one embodiment of the present invention, SW 123 residing on PC 9 is known instant-messaging software adapted to enable client connection to CIS 119 as a centralized communication server. An example of one such known messaging service would be the well-known ICQ™ service. In this case, CCPS 94 running on status server 49 would be adapted to support the particular instant-messaging application employed by user 9 and supported at CIS 119 by SW 121. In this case server 119 may be hosted by the entity hosting general IM services and through special arrangement, may provide personalized interfaces enabling client interaction to common clients of center 21 and the entity hosting server 119.

In a preferred embodiment, SW 121 provides interactive activity interfaces of the form of dynamic WEB pages complete with instant messaging capabilities. In this embodiment, SW 123 at station 9 represents a thin client application that may operate in a stand-alone fashion or be plugged into a client's browser application.

In another embodiment, server 119 is hosted by the same entity that hosts center 21. In this regard, SW instances 121 and 123 are dedicated applications enabling client interaction capability with various communication-center resources.

CCPS 94 running on status server 94 is adapted to handle brokering of all of the targeted resource information from center 21 as well as all of the client presence data from a plurality of clients. For example, CCPS 94 is adapted to integrate and distribute to SW 121 an enhanced package of client-accessible and researchable data resources associated with communication-center activity as it pertains to a requesting client in a personalized manner. Such data, incorporated into a dynamic interface by virtue of SW 121 running on CIS 119, is accessible to clients operating SW 123, in this case, running on user station 9. In addition to providing interactive access to communication-center resources, instant messaging may be employed such that agents 27, 29 and 31 may be able to communicate a variety of enhanced status messages to communicating clients being served by communication center 21. It is also noted herein, that the functionality of agent-status indication as taught above with reference to FIGS. 1-3, may be integrated into software at CIS 119 and accessible from user station 9 without departing from the spirit and scope of the present invention. A communication-center agent, for example, an agent operating PC 43 within workstation 31 may subscribe to CIS 119 utilizing LAN 23, server 49, and high-speed data link 22 for the purpose of determining client presence, as well as for assisting a client with interactive tasks, if required.

In a preferred implementation of the present invention, a client (9) can verify a current interaction status between himself or herself and communication center 21 without initiating a call to the center. Center 21 can also verify the status of client 9 without initiating a callback. The further goal of this specification is to enable client 9 to perform a variety of center-related tasks, which may be performed without agent involvement. Such tasks may include, but are not limited to, checking current status of an order-in-progress, reviewing interaction history regarding events leading to an order-in-progress, modifying or canceling orders-in-progress, researching available product data, initiating contact with entities of center 21, subscribing to personalized notices of events including special sales and promotions, changing personal contact and status information, requesting a callback from the communication center specifying a specific medium and specifying a specific time, initiating a communication with the communication center and so on.

In one embodiment, client interaction at CIS 119 is open such that any subscribing agent in question may monitor states of activity of a plurality of users actively connected to CIS 119. According to a push model, user-status indications may be pushed in the form of periodic instant messages to, for example, PC 43, where they may be, for example, viewed by a monitoring agent working station 31. In this case, a monitoring agent may decide whether or not to become actively involved in interaction with a client. For example, if a client is reviewing interaction history regarding a particular product of interest handled by a monitoring agent, that agent may invite the client to a pre-scheduled chat session about the product, or perhaps an impromptu chat, which may lead to an additional sale. There are many possibilities when one considers full instant messaging and chat capability.

According to one embodiment, an agent operating PC 43 may subscribe to an interface (not shown) served by CIS 119 such that current status indications are contained within the interface and viewable on PC 43. In this embodiment, status server 49 executing CIS 119 provides interactive interfaces for both clients and agents for the purpose of viewing status and as a predecessor to impending dialogue. Also in this embodiment, status server 49 executing CCPS 94 may facilitate COST outbound dialing from agent to client through CSW 53 by virtue of connection 51.

An agent operating one of the connected workstations 27, 29 or 31 may subscribe real-time status reports associated with a plurality of users connected to CIS 119 as previously described. Subscription may be defined as an active or inactive state of dialog established between an agent and the connected users. The dialog states may be initiated and established by users contacting agents through the method of the present invention or by agents contacting users.

Although the present specification teaches a personalized interaction capability whereby clients may interact with various communication-center hosted resources, it will be clear to one with skill in the art that bi-directional status reporting as taught in the cross-referenced specifications, disclosure of which is encompassed by description of FIGS. 1-6, may also be provided through the same interface. An example of such an enhanced interface is presented below.

FIG. 9 is a plan view of an interactive user interface 125 served by CIS 119 of FIG. 8 according to an embodiment of the present invention. In this example, the Personal Interaction User Interface (PIUI) 125 is composed of two sub-elements or sections. These are a section labeled Add/Edit Information and a section labeled View Status. In this embodiment, the Add/Edit Information element is made up of four basic categories of data used to create a dynamic multifaceted profile of a client that is accessible to communication center entities. These four categories represent interactive add/edit functions illustrated in this example, by an element number 127 (critical account and personal data), an element number 129 (network-capable appliance communication information), an element number 131 (personal agenda information), and an element number 133 (personal interests data). The information described in sub-element 133 lends itself to life style and preferences of a client and therefore is established in a manner as to be updated as often as is necessary.

The section of interface 125 labeled View Status comprises two basic categories. These categories are illustrated herein by element number 135 (view interaction history) and element 137 (view communication center status). The information described in category 135 relates to current and past interaction history between a client operating interface 125 and entities of a communication center. Entities as defined herein may also be assumed to include automated systems. The information described in category 137 relates to status information made available by the center upon request and, in some cases, dependant on the nature of the request.

In addition to the above, element 139 is for viewing the status of individual agents as personal account managers, allowing a user to monitor calls holding for the agent, estimated hold time, and to submit a call-back request. Element 141 allows the user to initiate a communication in any one of a variety of formats, as indicated. As can be seen in this example, interface 125 covers all of the functionality described in the embodiments introduced by FIGS. 1 and 4 above.

In a preferred embodiment of the present invention, every client subscribing to the system of the present invention is provided with at least an identification parameter (member ID number). In this way, data obtained and stored from internal and external sources is easily identifiable to a particular client. In addition, passwords and log-in requirements may be instituted depending on enterprise rules. Much profile information about clients may be automatically compiled using on-going historical data resulting from ongoing relationships with clients. Such data, if available, may automatically appear in the described Add/Edit Information section of interface 125 when first created. It is important to note herein that the data categories 127, 129, 131, and 133 may be populated using automatic interaction recording methods during communication center interaction events.

Referring now to personal data category 127, this information is illustrated herein as divided into various basic subcategories. These subcategories are listed from top to bottom as: login name, password, address, and age, marital status, etc. Each category may be further divided into more subcategories as deemed appropriate. As data is automatically compiled about a client over time, the client's profile becomes more and more accurate. Interface 125 enables a client to manually add or edit information at any time.

Element 129 provides information relating to the network-capable appliance capabilities of the client. This element is divided into various subcategories befitting the status of the client. In this example, the subcategories are Email, cell phone, telephone, and pager. This element may be edited continuously in keeping with the changing requirements of the client. Additional communication capabilities may include but are not limited to IP phone, PC applications such as specific chat interfaces, file-share programs, and so on.

Element 131 reflects personal agenda information provided by a client and is divided into various subcategories that pertain to the client's personal preferences relative to time and date available for communicating with agents at the communication center and preferred method or methods of communication. Personal agenda information may be edited frequently as a client's personal state changes.

Element 133 pertains to personal interests of a client and is divided into multiple subcategories. In this example, the subcategories listed include interest lists, subscriptions, and product updates. Category 133 is, in this example, a vehicle through which a client may communicate general desires to agents of a communication center. For example, interest lists may detail all of a client's particular interests whether related to communication-center business or not. By knowing interests of a client, agents may be better able to relate to the client on a personal level. Moreover, interests may be taken into consideration when serving the client. Subscriptions may include client subscriptions to communication-center provided material as well as to materials provided by other sources. Product updates may include requests to add notifications of when new or newly enhanced products offered by the communication center are available. Frequent client editing and addition of new data through category 133 is expected.

In the View Status section of interface 125, element 135 enables client access to personal interaction history as previously described. Subcategories of category 135 represented herein include a date of last interaction, an update option, and a cancel option. Information accessed through interaction within category 135 is compiled over time and is personalized to the client. Such available history data may include separate interaction records pertinent to separate communication mediums. Interaction records may be further divided by product, agent interacted with, and so on. Moreover, interaction with automated systems of a communication center may be included. In one embodiment, a client may be provided with various options for ordering interaction history records. For example, a client may order a combined record including all communication-center interaction presented according to data and time. In another embodiment, partial records may be ordered through a search function (not shown) provided in interface 125. There are many possibilities.

Element 137 pertains to communication center status reflecting information pertinent to a client when desiring contact with an entity of a communication center. It is noted here that a client may access and view agent status without initiating a contact event. However, in some embodiments, a client may submit an instant message summarizing an intent of a pending communication event whether it will be initiated by a client or by an agent calling the requesting client. Subcategories represented herein include calls holding, agents available, estimated hold time, and submit call back request. These and various other available options provide information for the client relative to the status of the communication center, and availability of services before connecting to the communication center or requesting a contact event from the center.

It will be apparent to one with skill in the art, that there may be more categories and subcategories described in interface 125 without departing from the spirit and scope of the present invention. The inventor has outlined basic categories and basic subcategories and deems them sufficient for illustrative purposes. Furthermore, as an interactive interface, it may be assumed that appropriate secondary interfaces will display for clients interacting with interface 125 such that selective viewing, data entry, editing, and so on may be accomplished. Such secondary interfaces may be linked to each category and subcategory through hyper linking or other known methods.

It will be apparent to one with skill in the art, that the method and apparatus of the present invention may be applied to a variety of connection scenarios without departing from the spirit and scope of the present invention. Similarly, the software of the present invention may be provided in a variety of functionalities ranging from an extendable application program interface (API) to an existing instant-messaging service to a fully functional server-driven service application including client-side and server-side components.

It will also be apparent to one with skill in the art, that instant messages, following standard instant message protocol, can be propagated back and forth between subscribing agents and clients without departing from the spirit and scope of the present invention. In addition to instant messaging, status alerts may take the form of pager messages or other types of known alerts when a client status is determined to be off-line. In addition, multiple protocols may be used, including IMPP, HTTP, WAP, and other known protocols, either alone or in combination.

Communication-Center Management Using IMPP

According to another aspect of the present invention, IMPP is used within a communication center for state management and other typical and a-typical center functions. The method and apparatus of the invention is detailed below.

FIG. 10 is an architectural overview of a communication center 1003 enhanced with presence detection and reporting according to an embodiment of the invention. Communication center 1003 represents a state-of-art center operating according to dual capabilities of processing COST communication events and multimedia IPNT communication events. In one embodiment however, center 1003 may be a pure IPNT capable center. In this example, center 1003 is part of a preferred communications network 1000 that includes a COST network 1001 and a digital network 1002 through which clients of the center 1003 gain access to offered services of the center.

Center 1003 may be assumed to have all of the presence capabilities described with reference to center 21 of FIG. 8. That is to say that clients may monitor presence information of entities including agents within center 1003 and agents may monitor presence information about clients accessing the center enabled by the equipment and software illustrated in that example.

COST network 1001 may be any type of telephony network as known in the art. In a preferred embodiment, a PSTN network is illustrated because of its high public use characteristics. Network 1001 will hereinafter be referred to as PSTN 1001. Digital network 1002 may be any type of data-packet-network known in the art such as a private WAN, corporate WAN or public WAN. In a preferred embodiment, digital network 1002 is the well-known Internet network and will be referred to hereinafter as Internet 1002.

A local telephony switch (LSW) 1004 is illustrated within PSTN 1001 and represents a telephony switch local in the network to center 1003. LSW 1004 represents a last routing point in PSTN 1001 for COST communication events destined for routing to center 1003. In this embodiment, LSW 1004 is CTI enabled by virtue of a connected processor 1008 running CTI telephony software and an instance of Instant Message and Presence Protocol (IMPP). Processor 1008 may also contain software for voice interaction with customers (IVR software) as well as routing software proprietary to center 1003.

LSW 1004 has connection to a telephony switch 1007 illustrated within center 1003 by virtue of a telephony trunk or trunks 1006. Switch 1007 is referred to herein as a central switch (CSW) of center 1003 and will hereinafter be referred to as CSW 1007. CSW 1007 represents a final routing point within center 1003 for incoming COST events from PSTN 1001 before internal routing to an agent or system for call resolution. CSW 1007 is CTI enabled by virtue of a connected processor 1011 running an instance of CTI telephony software and an instance of IMPP. Processor 1011 may also have additional software conventions as mentioned in the description of processor 1008 above.

Processors 1008 within PSTN 1001 and 1011 within center 1003 are connected for data communication by a data network link 1024. In this way certain routing rules and protocols, including IMPP may be extended from center 1003 into the level of the PSTN network wherein selected telephony switches may be controlled in terms of interaction with clients attempting to reach center 1003 as well as event handling of those interactions. Thus, data about calls and call originators pertinent to calls waiting for transfer from switch 1004 to switch 1007 can be passed ahead to center 1003, in many cases to the final routing point or destination of the call for preview before the actual event arrives.

Internet 1002 has a backbone 1009 illustrated therein and extending geographically there through. Backbone 1009 represents all of the lines, equipment, and connection points making up the Internet network as a whole. A network server 1005 is illustrated within Internet 1002 and is connected to backbone 1009. Server 1005 is adapted to serve electronic information pages, in the case of the Internet, Web pages in HTML and other types of suitable and known markup languages applicable to a variety of Internet access devices (client devices not shown). Server 1005 represents an access server maintained on Internet 1002 and hosted by center 1003.

Clients operating Internet capable devices may access center 1003 through server 1005 and an Internet access line 1010 set up between an illustrated Internet protocol router (IPR) 1014, maintained within center 1003 and sever 1005. IPR 1014 is adapted as a data routing server and routes events including all types of multimedia sessions to appropriate agents and systems working within center 1003. IPR 1014 is IMPP-enabled as suggested by label.

Communication center 1003 has a local area network (LAN) 1022 provided therein for center system and member (agent) connectivity requirements. LAN 1022 may be assumed to be adapted with all of the appropriate protocols supported within Internet 1002 including TCP/IP and so on. LAN 1022 is directly connected to IPR 1014 and serves as a routing conduit for data events routed to systems or agents from router 1014.

Agents are represented in this example by illustrated agent workstations 1015 and 1016. Each workstation 1015 and 1016 contains, at minimum, a LAN-connected PC and a COST telephone (illustrated by appropriate icons within each station). Telephones in each station 1015 and 1016 are connected to CSW 1007 by way of internal COST telephony wiring 1013. PCs illustrated within station 1015 and 1016 are LAN connected. In this example, agents take COST calls using a typical telephone and IPNT events are LAN-delivered to agent PCs. Digital data associated with COST events is LAN-delivered to agent PCs ahead of ringing events.

In another center station architecture known to the inventor, IP telephones replace COST telephones and all COST events are converted to data-packet-events before final routing to agents. In this case the IP phones are LAN-connected, or PC connected through soundcard installation procedures known to the inventor. Illustration of both COST and IPMNT capability with respect to center 1003 is for discussion purposes to more clearly describe the invention.

Each agent station 1015 and 1016 is enabled to support IMPP protocol. This may be accomplished in a conventional sense through known software applications or through proprietary presence applications. IMPP applications within stations 1015 and 1016 are accessible through interface using PC monitor and keyboard function as is well-known in the art.

Processor 1011 has a direct LAN connection and may be accessed and programmed or updated through LAN networking. Agent groups operating in concert with each other or one or more systems (automata) can be configured for LAN connection as destination points for both COST and IPNT-type access initiated by clients or other internal communication center entities whether human or machine. Such a group or system implementation is illustrated herein by a LAN-connected block 1017 labeled Groups/Systems. Groups/Systems 1017 is IPP enabled similarly to other previously described communication center entities.

A state server 1019 is provided within center 1003 and connected to LAN 1022. Server 1019 is IMPP-enabled and is adapted to serve current data regarding resources of the center and for synchronizing data with various systems. A data store 1023 is illustrated as connected to server 1019. Data store 1023 stores resolute information about agents and/or systems operating within center 1003. The information is presence-reportable information including particular state information blocks associated with database tuples with resolution down to real-time status snippets of agents and systems as may be affected by ongoing center activity.

In this example, a remote agent 1018 is illustrated outside of immediate center domain such as outside of an assigned workstation, but has a wireless connection 1021 to LAN 1022 that enables limited database access and therefore limited skill availabilities that would otherwise be available. Agent 1018 is IMPP-enabled and may be operating a cellular telephone, a personal digital assistant (PDA) or another network-capable device.

In practice of the invention, agents, systems, and groups can spawn generation of presence information models specific to targeted entities. The information is updated and stored as database tuples and state information blocks related to availability states of database supported skills and accessible media types that may be affected by activity states of an agent or system within center 1003 or external from the center but connected to the center network through a remote device. In a preferred embodiment the method of the present invention includes access to tuples and their current states for agents seeking information about other agents, clients seeking information about agents, clients or agents seeking information about systems, systems seeking information about clients, and systems seeking information about other systems. Information sharing between the just-described entities is accomplished using instant message and presence protocol. Some calibration is required if known IMPPs are employed in order to tune the protocol to the schema used to organize database tuples and their various possible states. In another embodiment, a proprietary protocol can be provided that is constructed around the parameters of database architecture and center activity protocols.

FIG. 11 is a block diagram illustrating function between software and hardware components of the system of the invention. In a preferred application of the invention, a principle 1101 is presented herein as terminology equated by the inventor to a requesting user. Principle 1101 may be a single user such as an agent, client or single machine (system) or application. In another embodiment, principle 1101 represents a group of agents or more than one system, application or perhaps a client group.

When principle 1101 needs to obtain current information about another entity or principle within the system it initiates an activity 1102 that spawns a software agent 1103. Software agent 1103, also termed user agent, is a software gopher that has access through various links to system information and can return that information to principle 1101.

User agent 1103 initiates a request/response activity 1104 to whatever target principle 1101 it is seeking information about. For example if principle 1101 is an agent of the center and he or she is seeking redirection information about a second target agent in the system then user agent 1103 will endeavor to obtain and return that information. A software form termed a presentity by the inventor and given the element number 1105 is spawned through activity 1104 initiated by agent 1103. Activity 1104 may be a targeted request/response activity. In some cases activity 1104 includes a search function that locates a target principle and confirms an up state of the entity within the system before requesting information.

Presentity 1105 has many aspects to it. In a preferred embodiment presentity 1105 is a generic form or model and is unique to a particular center entity only after it is populated with data. Presentity 1105 may be thought of logically as a picture or object model of a presence data report about a center entity. For example, presentity 1105 owns a presence 1109, which is a confirmation of the existence of an active presence summary associated with a principle. If the principle in question is not operational or logged into the communication center system, then presence 1109 would inform of unavailability status or (not currently logged in).

Presentity 1105 also owns all of the current information illustrated herein as presence information 1106 associated with presence 1109. Presence information 1106 has all of the appropriate presence tuples (database blocks) 1107 that are current for any given period of time of access and reporting of the information.

Individual tuples 1107 each have one or more state data blocks 1108 associated therewith that are data snippets that help completely describe the current state of any given tuple of presence information. State blocks 1108 may be thought of as properties associated with individual tuples 1107. Aggregation and construction of all of state blocks 1108 and tuples 1107 complete a presence information model represented as presence information 1106. Therefore, any change in state information of a tuple changes the tuple, which in turn changes the presence information model 1106 of presentity 1105. IMPP is used in this example as the messaging protocol for data synchronization required to provide most recent real-time snapshots of presence information 1106.

Presentity 1105 as a form is continually updated in real time by data synchronization as described above. IMPP synchronization is performed by a monitor 1110 and/or by a global presence entity 1111 between a provided data store 1112 with server capability and presentity 1109.

In one embodiment, as principles log into the communication center system of the invention, their current states are first reported and stored in data store 1112. After initial login, a given principle's activity and therefore availability states will begin to change and evolve over time. For example, if a principle is an agent working in the center, he or she may begin the day by answering e-mails. Therefore the principle's activity states reflected by presence information 1106 may show that the principle is currently unavailable for COST communication, is available for IPNT communication including e-mail, and has full access to customer information systems, multimedia, etc. Therefore, the skills of the principle are fully enabled except for COST communication.

In the above-case scenario IMPP reporting mechanisms at the agent's workstation can be activated to report state changes as they occur changing presence information model 1106. Such reporting mechanisms can be aggregated in an IMPP display set up on the desktop computer and may report as events occur (event driven) or may be monitored for change based on a pre-determined periodic interval. In such a display, all of the agent's media and communication components are represented as domains in control of the agent. The agent may, in some cases be responsible for manually changing state of a domain by signing out of a queue and working e-mails instead of answering calls or, perhaps, by logging out of the system when leaving his or her work station and so on. In other embodiments automated detection mechanisms may be employed within the operational software of each communications medium or domain to determine current state of activity within the specific domain.

In the case described above, presentity 1105 may be maintained in memory at a workstation or system memory (automata) or in a central database. In this case presentity 1105 has the state changes first as a result of driving events (agent activity). The updates to presentity 1105 can be communicated to data store 1112 through monitor 1110 or global presence 1111 for tracking purposes and to perform computations related to agent accessibility (full, partial, or none) to a full range of skills supported by data store 1112 based on results gleaned from presentity 1105.

In one embodiment a requesting principal may first access data store 1112 to enquire current status of another principle. In this case monitor 1110, also termed a watcher by the inventor, or global presence entity 1111 would access the appropriate presentity 1105 and upload the most recent information to the database. It is noted herein that it is not necessary to continually update and report an entities current presence information if there are no events that result in a need for the updated information. If an event does occur all updating and synchronization of data with a data store can be performed at the time of the request. For example if the target principal is an automated outbound dialing system restricted by a number threshold of outbound calls in queue, then the current updated state of number of calls left in queue can be synchronized to the data store when an event occurs that requires the information. The presence model for the system can be generated on the fly. In this way unnecessary database writes and synchronization operations are eliminated.

In a preferred embodiment, as events occur requesting any given principle's presentity operating within the system domain any updated data newer than data of a last access are synchronized to data store 1112, which may then compute and add some new availability information (state) based on the current state of events so that a requesting principle may simply access the appropriate presentity to obtain the updated information.

Using the system of the invention, state information can be gleaned from presentity 1105 as it occurs. The state information can be used to determine routing routines, choice of media in communication, queue planning, system initiation, resource allotment, load balancing, and other communication center functions. Traditional telephony and IPNT software applications can obtain updated presence information from data store 1112 without any modification required. Furthermore, certain specific principals that may be interleaved in one or more communication center activities may access each other's presentity models directly for resolving internal communication-center issues that do not require event routing or other normal treatments. An example would be a single agent transfer to another agent such as a supervisor. Before initiating the transfer the first agent may, from his or her desktop, access the presentity of the supervisor and make a determination of whether to proceed with the transfer based on the returned information. Even in this case, the presentity information may be synchronized with the data store to enable computation and return of additional data to the model about resources that based on the information in the model may be fully, partially, or non-available to the supervisor at the time of transfer depending on the activity state of the supervisor. The transferring agent can, after accessing the information, make an informed human decision as to whether or not the transfer is likely to be of help to the client.

In one embodiment, a principle such as an agent may be logged into the communication center system (LAN) using a device that is not capable of full database access. While he is not at his station, he or she is not completely logged out of the system because there is still some availability at some functional level. In such a case, his presentity model will reflect that he is away from his workstation but is answering his cell phone and has limited access to the database through a LAN-connected PDA.

By accessing his presentity information, routing software (as an accessing principle) can be set up to route only calls destined to that particular agent that are waiting in queue wherein such calls can be successfully resolved given the agents current means of communication and limited accessibility to the database. Those calls in queue waiting for that particular agent wherein full customer service and product support are required to facilitate successful resolution can be re-assigned to another agent whose presentity shows full skill availability.

One with skill in the art will appreciate that IMPP can be used as communication between all center members whether human or no or whether they are aggregated as groups or not. Members can include database software and traditional communication-center functional applications like routing software, tracking software, queuing software, and the like. Using IMPP with database resolution down to individual state blocks enables an accurate and current picture of activity state and availability of any given communication center principle. Instant messages propagated back and forth between entities can be response notifications based on requests of a principle, or pushed as periodic status change notifications to a monitoring application. For example, as a principle evolves in activity state, each actual state change can be considered an event in an event-driven system such that a current presence report is always immediately available. Accessing the presence information is also event driven. For example, if there are no requests logged or active within the communication system dealing with a particular principle, then there is no activity spawned to access information about the principle. This concept is event-driven access. An example of events in this case would be a number of calls waiting in queue for a particular agent. Each call as it comes up for treatment will be an event that spawns activity, for example, of a routing application to request and obtain most recent presence information on the agent before final routing determination.

In one embodiment, the system of the invention can be used as an event driven notification system to report state changes resulting from components that have failed or are down for maintenance. For example, if a principle is an e-mail server wherein a portion of mails designated for center processing require automated e-mail responses, and the automated response server is down for repair, then the presence information of that response system will be reported as down and the mails may be directed instead to live agents assigned to take over for the down machine.

The method and apparatus of the invention can be applied to any type of communication center that supports digital processing and communication. Applicable networks include the Internet, Ethernets, WANs, LANs and proprietary networks. Resolution of COST events in a CTI sense can be directed according to presence reporting in terms of routing, queuing, data forwarding, automated response, creative interaction through IVR, and so on.

In one embodiment, a COST event may trigger presence information reporting that results in a creative IVR interaction informing the caller that the agent he is trying to reach can take the call on a cell phone outside of the center and has limited access to order information, would this state still be acceptable or do you wish to transfer to another agent with access to a full skill set?

IMPP for Queue Processing and Resource Allocation

In another unique aspect of the present invention, IMPP or another suitable presence protocol (PP) is used for interacting with a master virtual queue and using information from the queue to plan resources required to optimally handle the queued events.

FIG. 12 is a block diagram illustrating a multimedia communication center 1200 including a queuing and routing system according to an embodiment of the present invention. Multimedia center 1200 is analogous in most respects to multimedia communication-center 1000 of FIG. 10, with an exception of how incoming events are processed in queue and what resources are used for final destinations for event routing within the center.

Center 1200 has a LAN 1206 operational therein and adapted for full multimedia event delivery and full Internet protocol support including IMPP protocols. LAN 1206 connects communication center resources for data access and share as well as providing a conduit for center/client communication over a wide variety of media types.

In this example, there are 2 illustrated resource groups connected to LAN 1206. These are group 1 and group 2. Groups 1 and 2 may be human agents working in the center or they may be automated systems or a combination of agents and automated systems. For the purpose of discussion, it will be assumed that groups 1 and 2 are organized as separate resource groups such as, for example, a customer account management resource (assume group 1) and a technical support resource (group 2). One with skill in the art of resource management will appreciate that in actual practice combinations and groupings of center resources are virtually unlimited in description and allocation.

In the case of live agents and following the example presented herein, group 1 consists of a plurality of LAN-connected agents that are dedicated to helping clients with their account information such as billing questions, collection operations, new account set-up, taking orders, and so on. Group 2 consists of a plurality of live agents dedicated to provision of technical support, trouble-shooting, and the like in this example. Each agent in both groups 1 and 2 may be assumed to be stationed in a LAN-connected workstation having, at bare minimum, a LAN-connected PC with a video display unit (VDU). Other types of equipment not shown such as IP telephones, fax machines, mobile devices, pagers, and so on may be present and may compliment agent capabilities within and externally from any given stationary workstation.

Communication center 1200 has a multimedia-capable virtual queue 1201 provided therein and adapted to receive tokenized information about real incoming events within the communication centers event-receiving and handling (routing) system or systems. In this example, queue 1201 is illustrated as full of events A-N with events O, P, and Q in the process of being queued or just entering queue 1201. It will be appreciated that events A-Q may represent events of any type of media supported within center 1200 such as telephone calls, IP voice calls, e-mails, chat initiation events, facsimiles, video mails, conference requests, IMPP-based communication events, and so on. Each represented event is tokenized with selected information associated with the event. Information included in token representation of the events may include but is not limited to event origination identification, routing destination identification, media type identification, purpose-of-event information and in some cases client presence information for call-back purposes.

There may be a variety of priorities set within the domain of queue 1201. Priority assignment may be based on any one or more of several criteria including media type, client identification, purpose-of-event information, contribution value from the client, and other criteria. There are many possibilities. Queue 1201 is mixed in the sense that represented events may include any or all media types supported by center equipment. Actual routing of events may be carried out by different routing systems connected to real queues within the center that are represented by virtual queue 1201. Such sub-queues in a preferred embodiment of the invention take immediate direction from disposition of events within virtual queue 1201. For example, if there are COST telephony events waiting at a queue associated with a central telephony switch and those events are represented in queue 1201, then the processing performed on the token events facilitates and orders the routing routines and system for making the connections to the final destinations, which could be COST telephones in agent workstations.

A virtual router 1202 is provided within center 1200 and is connected for event processing to virtual queue 1201. Like queue 1201, router 1202 works with representations of real events and orders appropriate routers within center 1200 to route their media types according to determination made in conjunction with queue 1201. However, in one embodiment wherein center 1200 is a pure IPNT center, router 1202 may be an actual IP router and can route all events in a pure multimedia sense. In this case, all events are routed with notification over a LAN connection illustrated between router 1202 and LAN 1206. Final destinations in this example are the connected agents organized in groups 1 and 2.

A T-server 1203 (which is a Computer Telephony Integration {CTI} server) is provided within communication center 1200 and is connected directly to router 1202 and to LAN 1206. T-server 1203 executes all of the routing rules and routines required for successful routing of all media types in this case. T-server 1203 may also have an external connection to a similar server at network level such as within a telephony network as described with reference to communication center 1000 of FIG. 10 above. The connection between T-server 1203 and LAN 1206 enables configuration and update of the server (via LAN) and extends routing routine execution capability to individual agent desktop computers in one embodiment known to the inventor.

LAN 1206 also supports an agent workstation 1207 to be operated by a supervising agent (SUP). An agent at workstation 1207 has overriding capabilities to perform resource allotment changes and other configurations typical of resource management capabilities. In this example, it may be assumed that the supervising agent has set up the resource allocation parameters for groups 1 and 2. Therefore, if necessary, the supervising agent can change, modify and reallocate those resources. It is noted herein that the supervising agent has assigned a larger number of agents to perform technical support (group 2) and a smaller number of agents to perform account management (group 1). This decision is primarily based on current event handling load in typical communication center environments, and is determined after event processing has occurred. In other words, in a very busy environment, supervisor 1207 is always playing catch-up to insure enough of the right resources are available to handle the event load as it occurs.

A state server 1204 is provided within center 1200 and adapted to serve real-time state information about communication center resources. State server 1204 is analogous to state server 1019 described with reference to FIG. 10 above. Server 1204 is IMP-enabled and is adapted to serve current data regarding resources of the center and for synchronizing data with various systems. A data store for actually storing the data is not illustrated but may be assumed to be present. Server 1204 serves resolute information about agents and/or systems operating within center 1200. The information is presence-reportable information including particular state information blocks associated with database tuples with resolution down to real-time status snippets of agents and systems as may be affected by ongoing center activity. Server 1204 has a direct LAN connection to LAN 1206 and has access to reporting mechanisms pertinent to each domain of each agent or system operating on LAN 1206.

A novel server 1205 is provided within center 1200 and adapted to provide workforce management and planning (WFMP) services for center 1200. Server 1205 will hereinafter be referred to in this specification as WFMP server 1205. WFMP 1205 is IMPP-enabled and connected directly to queue 1201, which is also IMPP-enabled, by a separate network 1208. During operation, WFMP server 1205 interrogates queue 1201 using an instant message protocol about events represented therein. Each event represented has a presence and property-state information associated with it. For example, a voice over IP call will have a media type, and origination ID, a destination request ID, and state information regarding the purpose of the event. Other types of events will have differing presence and state information associated with them. Server 1205 has the capability of aggregating all of the information for a portion of or all of queue 1201 in a single or in a series of interactions.

For example, one IMPP interaction between server 1205 and queue 1201 may be used to obtain all of the pertinent COST event data represented in queue 1201, while e-mail data may be communicated in a second interaction and so on. It will be appreciated that the contents of queue 1201 are constantly changing with respect to the amount of unprocessed events, their types and parameters. Therefore the frequency of access of queue 1201 from server 1205 is set at a relatively high level for each media type represented.

WFMP software running on server 1205 also has data access to state server 1204. State server 1204, as previously described, serves current state data on the presence state and resolute activity states of all of the LAN connected agents and, in some cases automated systems. In this example, all of the agents in groups 1 and 2 have their presence and state activity data published to server 1204 by push or pull method. WFMP server 1205 also has a direct LAN connection and can also, if desired, access agent presence and activity data via LAN.

WFPM server 1205 has additional data and communication access capability to T-server 1203 and to RTR 1202 via LAN 1206. WFMP 1205 is adapted to access and analyze needs and requirements associated with events in queue 1201 and compare those findings with state data served by server 1204 and formulate recommendations regarding near term resource allocation to best handle the current events stacked in queue. Presence information plays a large roll in enabling WFMP software to formulate accurate real-time assessments of a current communication-center queuing and routing environment. Instant messaging is used as a medium of communication between all involved components.

An example of a resource assessment and allocation recommendation against current queue requirements would be a case wherein WFMP server accesses queue 1201 via link 1208 and interrogates the queue for all waiting events that require account management services provided by agent group 1. Assume that a current snapshot result of queue activity shows that events A-K are waiting for account services while events L, M, and N are waiting for technical service provided by group 2. For the instant snapshot, it is noted that resources are not optimally configured for working the queue.

WFMP 1205 accesses state of groups 1 and 2 after interrogating queue 1201 from state server 1204. A comparative process begins within server 1205 wherein near term needs (current queued event requirements) are compared against resource availability and allocation parameters. WFMP determines during this process that more resources need to be diverted from group 2 in this case to group 1 to best handle the current load of queue 1201. A message is formulated within server 1205 containing the resource re-allocation recommendations and the message is sent, in this case to supervising agent 1207 over LAN 1206. The message is in a preferred embodiment an instant notification that informs the supervisor of a proposed action of diverting resources temporarily to help with the events in queue that require account management services.

The supervising agent at station 1207 receives the message and can make the appropriate resource allocation modifications through instant messaging to individual agents of group 2 to break off and join with group 1. At a next interrogation interval, WEMP 1205 will perform a new assessment and recommendation sending the recommendation to the supervising agent.

In one embodiment, certain simple resource allocation orders may be issued to target resources by WFMP software through server 1205 without supervisor involvement. These may be automated resources such as routing systems, interaction systems, or response systems, as well as live agent reassignment orders. It is noted herein that the allocation parameters of this example, group 1 (account management) and group 2 (technical service) is a simple example of allocating resources based on purpose of incoming event. In other embodiments, resources may be allocated based on other criteria such as media type required of incoming events, callback parameters for outbound dialing campaigns, and other mixes of criteria that may be represented by queue 1201.

In still another embodiment, presence information regarding live agents may be predicted by WFMP software by virtue of data access to individual agent schedules. For example, WFMP may drop agents from re-allocation recommendations if those particular agents will be unavailable due to shift changes, vacation schedules, and so on. Moreover, some of those same resources may be reserved intelligently through a recommendation by WFMP that lunch schedules be delayed because of current workload.

In still another embodiment, WFMP may have limited access through LAN connection to agents that are not at their workstations such as remote agents similar to agent 1018 described with reference to FIG. 10 above. In this case, the agent in question may be allocated to take calls for group 2 instead of group 1 because of access to technical knowledge and limited access to account management service resources. Supervising agent 1207 may configure T-server 1203 to route certain events to like agents using their personal cell phones. T-server 1203 forwards the control routine to Router 1202 to route the events.

In still another embodiment, threshold rules or constraints may apply to WFMP recommendations in order to lessen the frequency of resource re-allocation recommendations received by supervising agent 1207. Thresholds may be constructed from possible queue states in terms of content requirements and time waiting for events with no response. For example, in the first case using the simple example of groups 1 and 2, a resource re-allocation recommendation may not be issued until a snapshot of queue activity reflects an event-purpose shift from technical service requirements to account management requirements above a certain percentage of events waiting. In the second case, the threshold for issuing a re-allocation of resource recommendation may occur only if the resource-starved events begin to breach a time threshold for waiting for a response. Once the time threshold is reported to be breached a recommendation to re-allocate resources is issued to add resources for those particular events.

In yet another embodiment, statistical information resulting from actual tracking of queue and routing interaction over a particular time period of a campaign may be used by WFMP to fine tune recommendations by using probability figures to anticipate incoming events predicting the quantity and nature of those events up to a specified window of time ahead of queue registration. Such probability statistics can be generated from information accessed from a historical database and used to help determine resource re-allocation recommendations. In this case events O, P, and Q would be anticipated by WFMP software and statistically defined by probability factors.

One with skill in the art of intelligent routing and queue management will recognize that the method and apparatus of the invention provides a much needed assistance in resource planning by pre-analyzing queue requirements well ahead of required event processing and by sending recommendations to resource-responsible entities minutes before those resources are actually required. As a result, service optimization and event-handling efficiency can be continually improved for clients of the center.

FIG. 13 is a process flow diagram illustrating basic steps of queue processing and resource allocation according to a preferred embodiment of the invention. At step 1300, WFMP software accesses a communication-center master virtual queue (VQ) and reviews data about events registered therein. Data about events includes but is not limited to media type of event, event origination ID, event destination ID, and purpose of event data. At step 1301, event requirements are determined per event and sorted for priority. In this step processing is dependent in part of existing parameters and constraints set up by the hosting enterprise. In a media specific example where internal routing is determined only by media type, requirements may simply be media type and destination ID per event wherein the data is quantified and sorted by number of events waiting of each type.

At step 1302, WFMP accesses and reviews presence and state activity information of the current allocated resources for handling the events. It is noted herein that both environments, the events in queue and the state of resources allocated are evolving and changing as queue processing and routing ensues. Therefore, each transaction between WFMP and the queue and between WFMP and the resource presence and state information provides only the most recent snapshot of each environment. In one embodiment, steps 1300 and 1302 occur simultaneously in a multitask scenario to optimize accuracy.

At step 1303, current presence and state information of allocated resources is compared against near term event requirements of events in queue to determine if a recommendation is necessary. In some cases, it may be determined in step 1303 that no further action is required in which case the process resolves back to step 1300. It is noted herein that through various connections illustrated in FIG. 12, WFMP software has informational access to all un-allocated resources. Therefore, this knowledge is incorporated in step 1304 wherein WFMP software, if required, generates a resource re-allocation recommendation based on the most recent information. In a preferred embodiment of the invention, the recommendation is in the form of an instant message notification containing the data as an attachment or in the form body.

At step 1305, the resource recommendation is sent to a responsible entity like a supervising agent responsible for configuring center resources to respond to queued events. The recommendation may be received as an alert wherein the resources recommended for addition, subtraction, diversion, etc. are identified and known to be available according to the recommendation. In one embodiment, the target is an automated system instead of a live agent. For example, a communication center may employ 2 automated e-mail response servers wherein only one is currently allocated to process e-mails. A recommendation in this case may simply be targeted to the off-line server with an order to power up and begin processing from the pool.

At step 1306 the resources are re-allocated according to the latest recommendation. Depending on the time frame within the virtual queue, and perhaps any overriding priority considerations, resource re-allocation may occur several minutes before the resources are actually required. The exact amount of lead-time will, of course, vary according to conditions. For an empty or starved queue, the system may not be required at all. However, when the queue is near full and estimated waiting times are relatively high, then resource re-allocation can be performed well ahead of time to help process the waiting events more expediently.

It will be apparent to one with skill in the art that the process steps described in this example may be varied somewhat by subroutine and order without departing from the spirit and scope of the invention. For example, at step 1306 the target entity responsible for resources may override a recommendation and may elect not re-configure resources unless a more urgent recommendation arrives. Moreover recommendations may also be configured to provide dropped event probabilities and other consequence data if a recommendation is not initiated into an order. Further, it should be understood that the invention in some embodiments is not limited to IMPP protocol, but other protocols may even be more suitable than IMPP.

In one embodiment at step 1302, the presence and state information may be reported directly to the WFMP server from individually monitored resources so that it may have local data access to the most recent information. In another embodiment the server access a data store for the most recent information as it is synchronized thereto periodically. In still another embodiment, an additional subroutine may be provided for gauging one or more threshold levels applied to queue parameters before going ahead with preparation of a recommendation at step 1304.

Event Response Optimization

In another aspect of the present invention a software routine is provided for optimizing response time for events waiting in queue that typically have lower priority but could be processed in less time than other higher-priority events. The routine can be inserted into the process for workforce management as a sub-routine. The methods and apparatus of the present invention are described in enabling detail below.

FIG. 14 is a block diagram illustrating a multimedia communication center queuing and routing system 1400 according to embodiments of the present invention. System 1400 is similar in many respects to system 1200 described with reference to FIG. 12 above. Some elements belonging to system 1400 were also illustrated in the example of FIG. 12. Those common elements that are unchanged from their previous function and description retain the same element numbers and are not re-introduced.

System 1400 includes components that support dual capability in communication center operation meaning that system 1400 queues and routes COST telephony and DNT telephony in a preferred embodiment. System 1400 may be implemented within a communication center as is the case in this example. Therefore system 1400 may be referred to as communication center 1400.

Center 1400 utilizes a LAN network 1206, which is enabled for IP/TCP/IP, IMPP, and other suitable protocols as was described with reference to FIG. 12 above. LAN 1206 supports other components and serves as a routing network as well as a node network for sharing information and for entity to entity communication and interaction.

LAN 1206 supports group 1 and group 2, which represent agent and/or system-automated resources. Groups 1 and 2 may in one embodiment represent live agents having at minimum a computer station with VDU. The example described with reference to FIG. 12 above may also apply in this example including communication equipment options that agents from group 1 and 2 (if live) may have at their disposal.

In this example, both virtual queuing technology and real queuing technology is represented. For example, a multimedia virtual queue 1401 is provided to system 1400, in one embodiment, and adapted to receive tokenized events that represent real events that have arrived in other system queues. Queue 1401 is analogous in this embodiment to queue 1201 described further above in that there may be any priority scheme implemented ranging from simple FIFO to skill-based, predictive based, or other known routines that have already been described. As is the case regarding queue 1201 of FIG. 12, queue 1401 is illustrated as having multimedia mixed events processed therein. Each single event is assigned a letter in this example. Therefore, events A-N are resident in virtual queue 1401 and events O, P, and Q are just in the process of entering queue 1401. Multimedia events A-O may be of any of the types previously described above.

In another embodiment of the present invention, queue 1401 may be a Real Master Queue as optionally labeled. For example, queue 1401 may be a master telephony queue for queuing COST events. Queue 1401 may alternately be a master queue for queuing e-mail events or other DNT events including IMPP events. In still another embodiment, queue 1401 may be a master queue that holds a mix of differing types of DNT events. The term master as applied to a queue in this specification implies that there are other queues that are accessible to queue 1401 whether queue 1401 is a virtual or a real queue. It suffices to say that the methods and apparatus of the invention are not limited to queue type or content whether virtual or real.

In this example, a central telephony switch 1405 is illustrated within center 1401 and is adapted to receive all COST telephony events that arrive at center 1401 over an illustrated telephony trunk 1411. Switch 1405 may be a PBX, ACD, or other type of known telephony switch. In this embodiment, switch 1405 has a COST queue 1406 provided therein and adapted to queue incoming COST calls that are destined for one or more resources represented by group 1 or group 2.

Telephony switch 1405 is, in this embodiment, CTI-enhanced by a CTI processor 1410 connected thereto by a CTI link. Processor 1410 provides routing intelligence to switch 1405 by way of a Transaction Server (TS) application known to the inventor and described with reference to T-server 1203 of FIG. 12 above. However, in this case TS is provided with an IVR application on one machine, namely processor 1410. Processor 1410 may also be connected by a separate network illustrated herein as network 1409 to a similar processor connected to a network level switch for the purpose of providing intelligent agent-level routing at network level. Network 1409, in that case, is adapted to deliver information about a COST call and caller digitally to processor 1410, which can pass the information on to a final destination (Group 1, Group 2) over LAN 1206 by way of a LAN connection as illustrated herein between the just mentioned entities.

Switch 1405 is connected to individual agent telephones assumed present in this example by way of internal telephony wiring 1412 leading to both resource groups 1 and 2. Processor 1410 has a token generator engine provide therein and adapted to tokenize each arriving COST call so that the call can be represented within queue 1401 and handled in a virtual sense. Processor 1410 tokenizes each incoming event and sends the event token or information over a digital connection labeled COST Events herein to queue 1401 to mix with other tokens representing DNT events.

An IP router 1408 is provided within center 1400 and adapted to receive events by way of a network access pipeline 1412, and to route all arriving DNT events to their final destinations. DNT events may include IP telephone, E-mail, IM, IMPP, IP Fax, IP Chat, and other IP events that use shared bandwidth. IP router 1408 has real queues in a queuing system 1407 associated therewith and adapted as real queues for each type of DNT media represented. In this exemplary embodiment there is a real queue for e-mail, IP-voice, IP chat, IP-Fax, and IM. When a DNT event arrives at router 1408, it is deposited in the appropriate real queue of queuing system 1407 according to media type. In other embodiments, DNT event routing and queuing systems may be still further segregated as to be individual to a single or few media types. The inventor illustrated one router and one connected queue system for ease of description of the present invention only.

Queuing system 1403 has a token generator provided thereto for the purpose of tokenizing events deposited in queuing system 1407. When a DNT event arrives and is queued in one of the queues of system 1407, then a token is generated that represents the event and the token is sent to queue 1401 and deposited therein as illustrated. In this way all of the events being handled within center 1401 can be pre-processed and queue-managed in one container by one management system. It is noted herein that if queue 1401 is a real master queue or simply a media specific real queue, then token generators are not required. The general method of the present invention applies to both virtual and real queuing embodiments in different applications.

In this dually-capable embodiment, virtual queue 1401 represents all of the events that are waiting for processing and internal routing within center 1401. Center 1401 has a WFMP server 1402 provided therein, which is essentially identical in basic function as was described above with reference to the example of FIG. 12 and accompanying description. Server 1402 includes a machine-readable medium that is enhanced in this embodiment with an estimated disposal time (ETD) scanning application 1403, which is adapted to access queue 1401 and determine if there are any low priority events that could be resolved very quickly within the system.

Application 1403 works in conjunction with WFMP software to further optimize management of content within queue 1401. WFMP, for example, accesses queue content to determine if a resource re-allocation is appropriate to better and more expeditiously handle events in queue while EDT scanning expedites processing of lower priority events that can be handled swiftly without significantly taxing existing resources from responding to higher priority events.

Application 1403 has a direct connection to a rules base 1404 that is also connected to LAN 1206. Rules base 1404 is adapted, in this embodiment, to serve rules created for tokenizing different types of media events according to what event-content and state matter that may need to be considered when trying to determine whether or not the event can be handled swiftly within the system. Rules to this regard will vary according to media type of event and will govern what specific information blocks from the actual event will be available in token form, in addition to the state information normally included in a token that represents an actual event. For example, each token event has minimally presence and property-state information associated with it including a media type, an origination ID and destination request ID, and state information regarding the purpose of the event. Token events will have differing presence and state information associated with them according to media type, priority assigned, and so on.

EDT application 1403 may rely on some of the normal data that is already present in token events like media type and purpose of event information. Additionally, application 1403 is adapted to parse certain data that may be added to the normal token information when the actual event is first tokenized. It is logical to assume then that the process of token generation as practiced in this example by processor 1410, and by queuing system 1407 using generator 1403, is augmented by rules stored in rules base 1404, which is accessible to both processor 1410 and to system 1407 over LAN 1206. In another embodiment, direct network connections may be provided between the participating components to alleviate some LAN traffic.

To illustrate better the types of content that may be embedded into a token and utilized by application 1403, assume that a media type e-mail, for example, has normal tokenized blocks, sender, recipient, time stamp, and subject line. Assume that the subject line reads, “request for information about computer product A”. Typically, the e-mail may receive a relatively lower priority than, for example, a purchase order ready for processing. If that e-mail resides in queue 1401 along with a substantial number of e-mails that are for purchase orders, then those of a higher priority may continually bump that particular e-mail. Application 1403 accesses queue 1401 and parses the token information of the e-mail and consults with rules base 1404. In the process, application 1403 determines that the e-mail requesting information can be automatically handled in seconds by sending a quick response with an electronic brochure attached. Application 1403 can reassign the priority to high and can re-write any handling protocol for that e-mail effectively screening it for alternate automated processing and taking it out of the main queuing system.

Application 1403, in a preferred embodiment, accesses queue 1401 periodically and processes a plurality of new incoming events simultaneously in batch operations. Parsing the token information for each event enables the application to sort according to which events are lower priority events of what media types and or original destination queue assignments. From these events, further parsing determines which of those events can be alternately processed or otherwise handled efficiently without causing latency to higher priority events. If, citing our previous e-mail example, there is no subject line, or a subject line that reads “request for information”, which is not product specific, then application 1403 will require further information to be included in the token version of the event in order to consider it for evaluation. Therefore, when the e-mail is tokenized, generator 1403 determines that some of the body of the e-mail message should be included in the token version to compensate for the lack of a subject line or of a specific subject line that reveals a purpose for the event. In this way, application 1403 parses the included message content to determine the purpose for the event.

In a preferred embodiment, EDT application 1403 uses INP protocol to communicate with queue 1401, which is also INPP enabled. If normal priority assignments are made during tokenizing, queue 1401 is, in one embodiment, configured according to a priority threshold to report using instant messaging to application 1403 when there are a significant number of lower priority events in queue that should be accessed for processing according to EDT rules. In this case much sorting through events is eliminated.

Rules base 1404 is flexible in a preferred embodiment so as to provide different sets of rules for tokenizing different media types. Rules base 1404 also contains rules that govern EDT thresholds that can very dynamically according to currently allocated resources. For example, if a number of telephone calls having a low priority can be processed by playing an automated statement containing a specific information requested, and the collective estimated time and resource to handle those calls falls below a time and resource threshold value imposed on an IVR system then all of those calls can be promoted out of the main queue and can be immediately processed without conflicting with IVR interactions of a higher priority.

The end result is that more interactions get processed in a shorter amount of time. Potential clients that originally expect to have a longer wait in queue are treated with a higher priority if their EDT values are acceptable to the system resulting in more satisfaction with service and potential sales increases in new business. In the event of diverting some of the events to automated systems, agents have more time to focus on the events that require their attention and do not have to manually redirect so many events.

In an alternate embodiment, queue 1401 is not a virtual queue, but a real master queue as previously described. A real master queue, if a DNT queue, can include most if not all DNT events supported by the system. In this case, queuing system 1407 may comprise specific agent queues, queues shared by agent groups, and specific system queues. No tokenizing or virtual queuing is required in order to practice the present invention. In the event that queue 1401 is a real queue, application 1403 accesses queue 1401 as before and sorts events by media type and priority and parses only those of a lower priority to determine if those events can be handled swiftly according to EDT rules. Those events that meet the criteria are promoted to the agent/system specific queues ahead of some of the higher priority messages in a load-balanced fashion to minimize delay in handling of the higher priority events.

Parsing of events in a real master queue 1401 is still governed by rules served by rules base 1404. Those rules and methods of parsing depend largely on media type represented in queue 1401. For example, if queue 1401 is a COST queue, then it holds telephone calls, fax requests, voice mail messages, and other COST-dependant events. In this case, application 1403 can parse DNIS, ANIS, caller ID, destination ID, call priority assignment, and call purpose data if previously solicited from the caller by IVR interaction. In a COST queuing embodiment certain data like solicited information can be attached to the call as parse able digital data. Also in this case COST queue 1406 may not be required and queue 1401 would be, instead part of a telephony switching and routing system like switch 1405 and processor 1410. Application 1403 does not determine priority but can reassign priority if EDT values warrant such a reassignment.

Types of criterion that might be developed and considered when estimating a disposal time for an event include relatively simple state representations such as, for e-mails or text messages, a shorter text body contributes to a probability of faster processing than a long text body (message size). Also whether or not the e-mail or text message includes an attached document can be considered. Message subject lines, IVR selections made, and interactive options selected can also be used to estimate disposal time if those subject lines and selected options equate to known business processes conducted within center 1401.

Predictive analysis based on historical account can be used in some cases to predict EDT. For example, for an IP chat request, a historical EDT average value of that request originator's past chat sessions can be used to predict a probable disposal time. If a particular client exhibits a lower EDT average for chat sessions then he or she can be routed with a higher priority.

It is noted herein that some event types will have no specific priority assignments. In this case, it is possible that application 1403 assigns an original priority state based on EDT. However, in a preferred embodiment, the goal is to alleviate the queue of persistent low-priority messages that typically wait longer than other more-important messages. Accumulation of such lower priority messages can clog the queue and may begin to slow processing of the higher priority events. The method of the present invention may be practiced, as well, on individual real queues in parallel without the presence of a master queue. There are many possibilities.

FIG. 15 is a process flow diagram illustrating steps for practice of the present invention utilizing a virtual queue. At step 1500 incoming events are received in queue. Step 1500 is an ongoing step and applies to all supported media events received within the communications center. At step 1501 received events are tokenized and virtually queued in a master virtual queuing system analogous to queue 1401 described with reference to FIG. 14 above. At step 1501 a rules base (illustrated in association with step 1501) analogous to rules base 1404 described further above is consulted for the rules of tokenizing each type of event. Rules for each media type represented may very widely. IMPP protocols may be used when creating a token event such that the reportable particulars used for EDT processing are contained in an IM that can be accessed or sent to the EDT application for processing. Likewise, other standard machine languages can be used and attached to or integrated with event tokens. Furthermore, automated queue reporting can be set up so that when a number of tokens fitting EDT criteria for processing accumulate in queue, the queue can report the status to the EDT application to initiate batch processing.

In this case, it is assumed that the EDT application will periodically access the queue to determine if there are any tokens meeting processing criteria. Therefore at step 1502 a pre-scanner application accesses the virtual queue for processing. At step 1503 the pre-scanner sorts the tokenized events having a suitable low priority and then scan them for content related to EDT possibilities.

At step 1504 for each token event the EDT application attempts to determine if the event content meets queue priority promotion criteria for quick resolution without taxing current resources. At this step the rules base illustrated herein in association with steps 1501 and 1504 is consulted. Each media type may have a separate set of rules for handling according to stated purpose, which may have been added to the event token during the token phase at step 1501. Step 1504 can be initiated upon isolating a batch of event tokens with some tokens failing to meet criterion and some tokens meeting the criterion.

For those tokens meeting the EDT criterion, the EDT application extracts them from the virtual queue at step 1505 and re-assigns their priority to a higher priority at step 1506 at which point the events may be re-deposited in the virtual queue and processed according to their new priority states. In some embodiments, the EDT application also overrides the handling instructions for those events according to preferred methods known in the system. By extraction, it is meant that the EDT application accesses and takes write control over each event and not necessarily removing the event from queue positioning. The token events that fail to meet criterion at step 1504 are passed over and retain their original disposition instructions and priority states.

In a preferred embodiment of the present invention, the EDT application tags those events that have already been sorted and processed so that upon a next access, the same events are not re-processed. Step 1502, 1503, and 1504 is an ongoing loop wherein only those events that succeed in meeting EDT criterion are modified for quick resolution.

In one embodiment, the EDT application causes instant routing of any events that succeed in meeting EDT criterion for quick resolution. For example, a plurality of e-mail messages that can be easily handled automatically and otherwise would sit in queue at a low priority can be diverted from human response procedure and instead be automatically processed. In this case, the EDT application sends an overriding request to the routing system in charge of those e-mails, the request containing new instructions for routing them to the appropriate automated e-mail response system. At the same time, the tokens representing those e-mails are deleted from the virtual queue. The messaging from the EDT application-host server to the routing system can be of the form of an instant message requesting the alternate processing for the identified events waiting.

WFMP software described with reference to FIG. 12 above uses EDT results as well in planning resource availability. For example, if the EDT application determines that a number of events of a particular media type can be handled very quickly by a specific automated system for example, WFMP software can be notified to cause allocation of the desired system resource to handle those particular events effectively diverting them out of the live-agent system.

One with skill in the art will recognize that the process steps illustrated herein may vary somewhat in order and description depending on particular application with out departing from the spirit and scope of the present invention. For example, instead of batch processing as described with reference to steps 1502 through 1504, the process may be practiced per event. In this case EDT software would have constant access to the virtual queue and evaluate events as they arrive and are pre-assigned to destinations.

FIG. 16 is a process flow diagram illustrating steps for practice of the present invention utilizing a real master queue. At step 1600 incoming events arrive within the communication center and are queued in a master queue. It is assumed in this embodiment that the master queue is a real queue and that events will be promoted out of the master queue into final destination queues according to priority and availability. At step 1601 the events in the master queue are sorted according to media type and prioritized for normal handling according to routing rules that apply.

At step 1602 the pre-scanner application accesses the master queue. As was described above with reference to step 1502, this step is periodic in a preferred embodiment. At step 1603 the pre-scanner evaluates events for media type and content including priority assignment In one embodiment only low priority events below a certain pre-set priority threshold are evaluated eliminating the need for the pre-scanner to access every event in queue. In this embodiment, the master queue can report to the EDT application when there are a number of events for evaluation.

From those events under evaluation, at step 1604 it is determined which of those events meet or fail the EDT criterion for quick resolution probability. It is noted herein that some events will lend to a certainty result for quick resolution while others will lend only to a probability result for quick resolution. At step 1604 a rules base (drawn in association with the step) is consulted for each event evaluated. For those events that only a probability factor is produced it is possible that they will, in fact not be able to be quickly resolved. The system makes an intelligent guess based on information contained in or associated with the event. For example, if the event is an IP telephone call from a certain repeat customer and in the past such calls were handled relatively quickly, then a probability value for a quick resolution would be generated.

At step 1605, those items that do not meet the EDT criteria for quick resolution are simply removed from consideration and preferably tagged as having been processed so that they are not re-evaluated. Those events that do meet the criterion for quick resolution, in one embodiment are physically extracted from the master or general queue at step 1606 and then deposited at step 1607 into the destination-appropriate final queues for event handling. In this case, EDT actually distributes the events to the final destination queues based on results of evaluation and immediate availability information regarding the final destination queues.

In another embodiment events are not physically extracted from the master queue, but are re-assigned to the priority status that effects their promotion and subsequent distribution into the appropriate final destination queues for handling. As previously described, based on evaluation results per event, the EDT application can re-write the handling protocol for an event and change the original destination queue assignment to a new assignment. An example would be to divert an instant message session request from one live-agent group operating a shared queue to an automated system queue where the instant message will be answered by an automated response message effectively diverting or re-directing the event from one destination to another (internal re-routing).

In the event that a general master queue embodiment is practiced it is likely that there will be separate master queues, one for COST events and one for DNT events. In this case, the EDT application server would access both queues and process events there from simultaneously in a multitaskable fashion. It is important to note herein that EDT software may, instead of periodic access ability, have constant access connection to the master queue and may process events as they arrive instead of in batch without departing from the spirit and scope of the present invention. Moreover, if priority assignment is practiced, the queue may be configured to report which events queued were assigned a priority level under a pre-set threshold for evaluation to EDT software. Such reporting may be configured to occur when the queue has enough events therein to surpass a certain pre-set threshold of a number of events having low priority. There are many possibilities.

FIG. 17 is a block diagram illustrating the pre-scan software application of FIG. 14 according to embodiments of the present invention. Application 1403 is described herein as an EDT application and in some instances as a pre-scanner application because of its main function of pre-scanning real or token events for indication of quick resolution possibilities. Application 1403 has a plurality of modules that enable various scanning operations on token or real event data as well as a number of system interfaces.

A virtual/master queue interface 1700 is provided to application 1403 and adapted to enable application 1403 to access a main virtual or real data queue for the purpose of processing events there from. Interface 1700 can be a software interface or a hard-wired server port or other network connection interface as required according to specific hardware architecture used.

An agent/system queue interface 1702 is provided to application 1403 and is adapted to enable access to real queues, final destination queues, system queues, and any other queues held separately from master or main queues. Port 1702 is optional in that in one application events selected for promotion according to EDT criterion are re-assigned higher priority levels to induce quicker response, but are physically left in main or general queues, virtual or real until such priority reassignments cause event promotion (real) to final destination queues or final routing and handling according to token progression (virtual) using normal system paths.

An interface to a rules base 1701 is provided to application 1403 and is adapted to enable consultation with system and enterprise directed rules which govern decisions made during evaluation of events or event tokens and, which may also be consulted during the token generation process in a virtual queue embodiment. Rules contained in such a rules base as described above include those that might relate to probability of quick resolution: according to certain discernable states. For example, a short text message with no attachment will receive a higher score than a long text message including one or more attachments. An IP voice call placed from a later time zone may receive a higher score than one originating locally. Detection of the presence and availability of special resources like foreign language resources just coming on-line as identified through IMPP by WFMP software might precede an evaluation of like foreign language-seeking events. In this case, the evaluated events receive a higher score than English language requests because of the available resource for quick resolution.

There are many possibilities for rules creation, modification, management, and implementation. Some basic rules may cover simple content states such as included subject line (e-mails), stated purpose (IVR solicitation telephone), and so on. Implementation of these rules may be as simple a s “immediately divert all ‘found’ e-mails waiting of priority lower than “6” containing subject line “request for information” from live agent handling to automated system response. More complex rules are probability-based and may include accesses to other database information such as historical performance records. One example implementation might be “re-assign priority from ‘5’ or lower to ‘9’ for all chat requests with a “historical EDT average” of lower than 6 minutes. In this particular case, there may be some re-assigned chat requests that will actually take more than 6 minutes to resolve. However the new time of resolution will be figured in to their historical EDT average figure to be considered the next time they log-in to a chat room.

A module for event-type identification and sorting 1703 is provided to application 1403 for the purpose of identifying various different media types of events and sorting them accordingly using a parsing engine 1704. Engine 1704 is adapted to read from header information in a token or real event. Module 1703 interfaces with a master or virtual main queue through interface 1700. A module for event-type state evaluation 1705 is provided to application 1403 and adapted to determine type of event or token event and current priority state assigned using a parsing engine 1706. Engine 1706 is adapted to read system-assigned state data including routing information, origination information, and final destination information. Module 1705 interfaces with the main virtual or master queue through interface 1700.

An event content evaluation module 1707 is provided to application 1403 and is adapted to read message, using a parsing engine 1708 content including subject lines, selected body text, interaction result data, and any other parse able content data included in a token event or embedded in a real event. Module 1707 interfaces with a main or master queue in concert with the earlier described modules through interface 1700 and also interfaces to a rules base through interface 1701 to access rules regarding priority state and found content. It is noted herein that modules 1703, 1705, and 1707 may be provided as a single integrated module using a same parsing engine without departing from the spirit and scope of the present invention. The inventor seeks to logically separate function only for illustrative purpose.

A priority configuration and event promotion module 1709 is provided to application 1403 and is adapted by way of a calculator 1710 to compute EDT probability factors or scores for token events or real events and to effect priority reassignments and to initiate queue promotions (where required). Module 1709 has interface to a rules base through interface 1701 and an optional interface to real agent and/or system queues through interface 1702 in the event of direct queue promotion activity that bypasses normal queue progression paths. Module 1709 considers information results provided by modules 1705, and 1707 to perform per-event calculations to receive implementation results leading to any direct actions that might be taken. Depending on rules, token or real events may fail evaluation during evaluation by any one of the described modules. Likewise, an event or token event may succeed evaluation before reaching the point of evaluation by module 1707 effectively bypassing event content evaluation. In one embodiment, module 1707 is always invoked if prior evaluation fails to retrieve enough information to reach a decision. In this case content is parsed to gain the additional information that may reveal a likely probability for short resolution.

It will be apparent to one with skill in the art that the method and apparatus of the present invention can be distributed to more than one machine having connection to the routing network without departing from the spirit and scope of the present invention. For example, modules 1703 and 1705 may be provided as client reporting modules and integrated with queue software and hardware. In this case, modules 1707 and 1709 might form a parent application residing on a separate server connected to the routing network. Likewise, there may be more interfaces to external information sources than those illustrated herein. For example, an interface to a customer information system (CIS) server and/or to a historical database might be incorporated herein to enable application 1403 to consider other information used to make decisions. This can be especially important when one factor is a historical EDT average accessed and retrieved for priority reassignment considerations.

The computing method of the present invention is in a preferred embodiment performed by algorithm including score calculation. There is more than one computation method that might be used. For some situations, a simple comparison of state information to applicable rule for match will be sufficient for priority-reassignment. In more complex considerations, a series of scores for different blocks of parsed information can be calculated for each event and weighted against a rules set to produce a final result that will determine if the event or token event will be priority-modified and, perhaps to what specific level of priority or promotion from a plurality of existing levels the event or event token will receive.

In still another embodiment of the present invention, there is no original priority assignment to queued messages. In this case EDT evaluations are performed on all queued messages no matter what the queue status is and those that can be handled quickly are promoted first to alleviate overall queue latency by processing those events that can be handled easily and quickly without taxing normal agent response resources.

The method and apparatus of the present invention has been demonstrated herein to have patentable weight in a variety of different embodiments and therefore should be afforded the broadest possible scope under examination. Only the claim language provided below limits the spirit and scope of the present invention.

Claims

1. A system for increasing transaction queue efficiency comprising:

a computerized server having software stored on and executing from a machine-readable medium, the software comprising:
a first portion of instructions for implementing a queue for governing order of processing transactions;
a second portion of instructions for reordering and/or removing one or more of the transactions from the queue;
an electronic router coupled to the computerized server for routing at least one of the transactions to a final destination;
wherein the second portion of instructions is for periodically accesses accessing stored information concerning individual ones of the transactions, using rules separately stored determines from the information, determining an estimated disposal time (EDT) for the transactions considered, and for particular ones of the transactions having a determined the estimated disposal time lower than a pre-stored time, either moves those moving the particular ones of the transactions ahead of other ones of the transactions in the queue or removes those removing particular ones of the transactions from the queue,
wherein the estimated disposal time is an estimate based on historical averaging of previous measurements for an originator of a transaction of a same type.

2. The system of claim 1 wherein the computerized server is a work force management and planning server enhanced with the addition of the software application.

3. The system of claim 1 wherein the queue is a virtual message queue for a communication center.

4. The system of claim 1 wherein the queue is a telephony queue.

5. The system of claim 1 wherein the software application includes at least one parsing engine instructions for parsing transaction information.

6. The system of claim 1 wherein the software application includes an interface to a historical data repository.

7. The system of claim 5 wherein the information parsed includes one or more of event type, event status in queue, event routing information, and event origination information.

8. The system of claim 1 wherein the disposal time determined is an estimate based on known procedure for handling the event transactions.

9. The system of claim 1 wherein the disposal time determined is an estimate based on historical averaging of previous measurements for the same originator of an event of a same type.

10. The system of claim 1 wherein some events of the transactions are immediately promoted from the queue to an appropriate final destination queue.

11. The system of claim 1 wherein events certain ones of the transactions that are modified to reflect a higher priority state are immediately routed to their final destinations.

12. A method for increasing transaction queue efficiency comprising the steps of:

(a) implementing, by a processor, a queue for governing order of processing transactions on a computerized server having software stored on and executing from a machine-readable medium;
(b) periodically accessing, by the processor, stored information concerning individual ones of the transactions;
(c) using rules separately stored from the information, determining, by the processor, an estimated disposal time (EDT) for the individual ones of the transactions considered and, wherein the estimated disposal time is an estimate based on historical averaging of previous measurements for an originator of a transaction of a same type;
(d) for one or more transactions of the individual ones of the transactions having a determined the estimated disposal time lower than a pre-stored time, either moving those, by the processor, the one or more transactions ahead of other ones of the transactions in the queue or removing those the one or more transactions from the queue; and
(e) routing, by an electronic router coupled to the processor, at least one of the transactions to a final destination.

13. The method of claim 12 wherein the computerized server is a work force management and planning server enhanced with the addition of the software application.

14. The method of claim 12 wherein the queue is a virtual message queue for a communication center.

15. The method of claim 12 wherein the queue is a telephony queue.

16. The method of claim 12 wherein the software application includes at least one parsing engine for parsing transaction information.

17. The method of claim 12 wherein the software application includes an interface to a historical data repository.

18. The method of claim 12 wherein the information parsed includes one or more of event type, event status in queue, event routing information, and event origination information.

19. The method of claim 12 wherein the disposal time determined is an estimate based on known procedure for handling the event transactions.

20. The method of claim 12 wherein the disposal time determined is an estimate based on historical averaging of previous measurements for the same originator of an event of a same type.

21. The method of claim 12 wherein some events of the transactions are immediately promoted from the queue to an appropriate final destination queue.

22. The system method of claim 12 wherein events certain ones of the transactions that are modified to reflect a higher priority state are immediately routed to their final destinations.

Referenced Cited
U.S. Patent Documents
4718005 January 5, 1988 Feigenbaum et al.
4800583 January 24, 1989 Theis
4958368 September 18, 1990 Parker
5006983 April 9, 1991 Wayne et al.
5036535 July 30, 1991 Gechter et al.
5040208 August 13, 1991 Jolissaint
5062103 October 29, 1991 Davidson et al.
5155761 October 13, 1992 Hammond
5163083 November 10, 1992 Dowden et al.
5181236 January 19, 1993 LaVallee et al.
5206903 April 27, 1993 Kohler et al.
5271058 December 14, 1993 Andrews et al.
5274700 December 28, 1993 Gechter et al.
5311574 May 10, 1994 Livanos
5311583 May 10, 1994 Friedes et al.
5436967 July 25, 1995 Hanson
5452350 September 19, 1995 Reynolds et al.
5535335 July 9, 1996 Cox et al.
5542088 July 30, 1996 Jennings, Jr. et al.
5557736 September 17, 1996 Hirosawa et al.
5583922 December 10, 1996 Davis et al.
5586174 December 17, 1996 Bogner et al.
5611050 March 11, 1997 Theimer et al.
5633924 May 27, 1997 Kaish et al.
5678002 October 14, 1997 Fawcett et al.
5689548 November 18, 1997 Maupin et al.
5696486 December 9, 1997 Poliquin et al.
5742905 April 21, 1998 Pepe et al.
5757904 May 26, 1998 Anderson
5764913 June 9, 1998 Jancke et al.
5774668 June 30, 1998 Choquier et al.
5777614 July 7, 1998 Ando et al.
5778060 July 7, 1998 Otto
5825869 October 20, 1998 Brooks et al.
5848143 December 8, 1998 Andrews et al.
5867562 February 2, 1999 Scherer
5870464 February 9, 1999 Brewster et al.
5884032 March 16, 1999 Bateman et al.
5892764 April 6, 1999 Riemann et al.
5895459 April 20, 1999 Enomoto
5898770 April 27, 1999 Valentine
5907547 May 25, 1999 Foladare et al.
5911134 June 8, 1999 Castonguay et al.
5913040 June 15, 1999 Rakavy et al.
5918222 June 29, 1999 Fukui et al.
5926539 July 20, 1999 Shtivelman
5943478 August 24, 1999 Aggarwal et al.
5946388 August 31, 1999 Walker et al.
5956509 September 21, 1999 Kevner
5960442 September 28, 1999 Pickering
5964837 October 12, 1999 Chao et al.
5966653 October 12, 1999 Joensuu et al.
5966699 October 12, 1999 Zandi
5999965 December 7, 1999 Kelly
6011845 January 4, 2000 Nabkel et al.
6064730 May 16, 2000 Ginsberg
6064874 May 16, 2000 Cox et al.
6085097 July 4, 2000 Savery et al.
6108700 August 22, 2000 Maccabee et al.
6111940 August 29, 2000 Kugell
6112243 August 29, 2000 Downs et al.
6115743 September 5, 2000 Cowan et al.
6137869 October 24, 2000 Voit et al.
6157655 December 5, 2000 Shtivelman
6161099 December 12, 2000 Harrington et al.
6163607 December 19, 2000 Bogart et al.
6178443 January 23, 2001 Lin
6199099 March 6, 2001 Gershman et al.
6229888 May 8, 2001 Miloslavsky
6230197 May 8, 2001 Beck et al.
6259774 July 10, 2001 Miloslavsky
6278936 August 21, 2001 Jones
6301609 October 9, 2001 Aravamudan et al.
6308216 October 23, 2001 Goldszmidt et al.
6317786 November 13, 2001 Yamane et al.
6324683 November 27, 2001 Fuh et al.
6327364 December 4, 2001 Shaffer et al.
6332154 December 18, 2001 Beck et al.
6345305 February 5, 2002 Beck et al.
6363411 March 26, 2002 Dugan et al.
6363421 March 26, 2002 Barker et al.
6367013 April 2, 2002 Bisbee et al.
6373836 April 16, 2002 Deryugin et al.
6389007 May 14, 2002 Shenkman et al.
6389028 May 14, 2002 Bondarenko et al.
6389127 May 14, 2002 Vardi et al.
6389132 May 14, 2002 Price
6392666 May 21, 2002 Hong et al.
6405035 June 11, 2002 Singh
6408062 June 18, 2002 Cave
6415318 July 2, 2002 Aggarwal et al.
6424709 July 23, 2002 Doyle et al.
6430602 August 6, 2002 Kay et al.
6434121 August 13, 2002 Davidson et al.
6434230 August 13, 2002 Gabriel
6442432 August 27, 2002 Lee
6449646 September 10, 2002 Sikora et al.
6449648 September 10, 2002 Waldo et al.
6477374 November 5, 2002 Shaffer et al.
6484196 November 19, 2002 Maurille
6487590 November 26, 2002 Foley et al.
6493446 December 10, 2002 Cherry
6493447 December 10, 2002 Goss et al.
6546419 April 8, 2003 Humpleman et al.
6553336 April 22, 2003 Johnson et al.
6564261 May 13, 2003 Gudjonsson et al.
6571282 May 27, 2003 Bowman-Amuah
6574605 June 3, 2003 Sanders et al.
6578005 June 10, 2003 Lesaint et al.
6578054 June 10, 2003 Hopmann et al.
6584186 June 24, 2003 Aravamudan et al.
6584499 June 24, 2003 Jantz et al.
6587831 July 1, 2003 O'Brien
6603396 August 5, 2003 Lewis et al.
6603837 August 5, 2003 Kesanupalli et al.
6606668 August 12, 2003 MeLampy et al.
6611498 August 26, 2003 Baker et al.
6611590 August 26, 2003 Lu et al.
6618369 September 9, 2003 Huh et al.
6631407 October 7, 2003 Mukaiyama et al.
6650748 November 18, 2003 Edwards et al.
6651085 November 18, 2003 Woods
6654816 November 25, 2003 Zaudtke et al.
6658106 December 2, 2003 Atkinson et al.
6661889 December 9, 2003 Flockhart et al.
6665375 December 16, 2003 Forlenza et al.
6697858 February 24, 2004 Ezerzer et al.
6701366 March 2, 2004 Kallas et al.
6707906 March 16, 2004 Ben-Chanoch
6724884 April 20, 2004 Jensen et al.
6728262 April 27, 2004 Woram
6728365 April 27, 2004 Li et al.
6747970 June 8, 2004 Lamb et al.
6748471 June 8, 2004 Keeney et al.
6760767 July 6, 2004 Miesbauer et al.
6763384 July 13, 2004 Gupta et al.
6775371 August 10, 2004 Elsey et al.
6782413 August 24, 2004 Loveland
6795830 September 21, 2004 Banerjee et al.
6810026 October 26, 2004 Huttunen
6822945 November 23, 2004 Petrovykh
6842877 January 11, 2005 Robarts et al.
6857012 February 15, 2005 Sim et al.
6868525 March 15, 2005 Szabo
6874090 March 29, 2005 See et al.
6985576 January 10, 2006 Huck
6996603 February 7, 2006 Srinivasan
7187662 March 6, 2007 Klingman
7224774 May 29, 2007 Brown et al.
7254641 August 7, 2007 Broughton et al.
7257552 August 14, 2007 Franco
7269160 September 11, 2007 Friedman et al.
7299259 November 20, 2007 Petrovykh
7324637 January 29, 2008 Brown et al.
7586859 September 8, 2009 Petrovykh
7730135 June 1, 2010 Petrovykh
7929464 April 19, 2011 Petrovykh
7929562 April 19, 2011 Petrovykh
7953219 May 31, 2011 Freedman et al.
9031087 May 12, 2015 Petrovykh
RE46174 October 4, 2016 Petrovykh
20010000458 April 26, 2001 Shtivelman et al.
20010025310 September 27, 2001 Krishnamurthy et al.
20010031997 October 18, 2001 Lee
20010042123 November 15, 2001 Moody et al.
20010044840 November 22, 2001 Carleton
20010054064 December 20, 2001 Kannan
20020018554 February 14, 2002 Jensen et al.
20020049608 April 25, 2002 Hartsell et al.
20020055853 May 9, 2002 Macleod Beck et al.
20020055967 May 9, 2002 Coussement
20020055975 May 9, 2002 Petrovykh
20020056000 May 9, 2002 Albert Coussement
20020116531 August 22, 2002 Chu
20020120697 August 29, 2002 Generous et al.
20020143987 October 3, 2002 Sadler et al.
20020154171 October 24, 2002 Lee et al.
20020178227 November 28, 2002 Matsa et al.
20030009530 January 9, 2003 Philonenko et al.
20030046396 March 6, 2003 Richter et al.
20030212583 November 13, 2003 Perras, Jr. et al.
20050033846 February 10, 2005 Sankaranarayan et al.
20050289068 December 29, 2005 Stefik et al.
20070294410 December 20, 2007 Pandya et al.
20080071917 March 20, 2008 Petrovykh
20110286444 November 24, 2011 Petrovykh
20130145019 June 6, 2013 Petrovykh
20160134754 May 12, 2016 Petrovykh
Foreign Patent Documents
1120951 August 2001 EP
1225752 July 2002 EP
1227635 July 2002 EP
1109387 December 2003 EP
1119170 December 2003 EP
1107615 June 2004 EP
1423795 October 2004 EP
1206106 June 2005 EP
1478167 October 2005 EP
1535173 October 2005 EP
1540900 October 2005 EP
2338870 December 1999 GB
2001-0016151 March 2001 KR
9914930 March 1999 WO
0022802 April 2000 WO
0044159 July 2000 WO
0069140 November 2000 WO
0140959 June 2001 WO
0223877 March 2002 WO
WO 02/23877 March 2002 WO
03025776 March 2003 WO
2004021127 March 2004 WO
2004023324 March 2004 WO
Other references
  • Atkins, David et al., Mawl: Integrated Web and Telephone Service Creation, Bell Laboratories, Lucent Proprietary, Mar. 4, 1997, 21 pages.
  • Brause, Rudiger, Prozess-Scheduling with Google English Translation, URL:http://home.fhtw-berlin.de/{s0505342/scheduling.pdf>, Dec. 16, 2002, XP002342968, 13 pages.
  • Brazier, Frances et al., Formal Specification of Multi-Agent Systems: a Real World Case, 1995, 8 pages.
  • Brown, Scott M. et al., Intelligent Interface Agents for Intelligent Environments, U.S., 1998, 3 pages.
  • Day, M. et al., Request for Comments (RFC) 2778: A Model for Presence and Instant Messaging, Internet Engineering Task Force—IETF RFC 2778, Feb. 2000, 12 pages.
  • Day, M. et al., RFC 2779—Instant Messaging/ Presence Protocol Requirements, Internet Society, Feb. 2000, 21 pages.
  • Decision on Appeal for European Patent Application No. 02761182.1, dated Aug. 6, 2011, 21 pages.
  • European Office action for Patent Application No. 02001005.4, dated Mar. 10, 2005, 7 pages.
  • European Office action for Patent Application No. 01125447.1, dated May 8, 2006, 4 pages.
  • European Office action for Patent Application No. 02000168.1, dated Jun. 3, 2004, 6 pages.
  • European Office action for Patent Application No. 02000168.1, Jul. 19, 2005, 5 pages.
  • European Office action for Patent Application No. 02761182.1, dated Jun. 25, 2008, 8 pages.
  • European Office action for Patent Application No. 02761182.1, dated Jun. 29, 2005, 6 pages.
  • European Office action for Patent Application No. 03791883.6, dated Jul. 11, 2008, 3 pages.
  • European Office action for Patent Application No. 03791883.6, dated Oct. 18, 2006, 5 pages.
  • European Office action for Patent Application No. 04009486.4, dated Jun. 10, 2014, 3 pages.
  • European Office action for Patent Application No. 04009486.4, dated Mar. 10, 2008, 6 pages.
  • European Office action for Patent Application No. 04009486.4, dated May 25, 2011, 5 pages.
  • European Search Report for Patent Application No. 01125447, issued on Apr. 15, 2005, 2 pages.
  • European Search Report for Patent Application No. 02000168, issued on Feb. 19, 2004, 2 pages.
  • European Search Report for Patent Application No. 02001005, issued on Aug. 25, 2004, 1 page.
  • European Search Report for Patent Application No. 02761182.1, issued on Aug. 2, 2004, 1 page.
  • European Search Report for Patent Application No. 03749323.6, issued on Aug. 29, 2005, 1 page.
  • European Search Report for Patent Application No. 03791883, issued on Aug. 29, 2005, 1 page.
  • European Search Report for Patent Application No. 04009486.4, dated Sep. 12, 2005, 4 pages.
  • FIE 2000: 30th Annual Frontiers in Education Conference: Building on a century of progress in engineering education: Conference proceedings: Hyatt Regency Crown Center Hotel, Kansas City, Missouri, U.S., Oct. 18-21, 2000, IEEE Tab Products, Piscataway, NJ, IEEE Catalog No. 00CH37135, ISBN:07803-6424-4, 3 pages.
  • Guttman, Robert H. et al., Agent-mediated Integrative Negotiation for Retail Electronic Commerce, MIT Media Laboratory, Cambridge, Massachusetts, U.S., 1998, 13 pages.
  • International Search Report for PCT/US2002/23851, mailed on Sep. 17, 2002, p. 1.
  • International Search Report for PCT/US2003/26935, mailed on Jun. 7, 2004, p. 1.
  • International Search Report for PCT/US2003/27418, mailed on Jan. 28, 2004, 2 pages.
  • Koplowitz, H.B., Instant Mess (Lost in Cyberspace), Online, 1999, Retrieved from the Internet at http://hbkoplowitz.com/LIC/instant/im.html, Jul. 22, 2004, 2 pages.
  • Lowekamp, Bruce et al., A resource Query Interface for Network-Aware Applications, School of Computer Science, Carnegie Mellon University, Pittsburgh, Pennsylvania, U.S., 1999, 8 pages.
  • Michael, Bill, Hey Buddy . . . , Commweb, Online, May 11, 2000, XP002270636, Retrieved from the Internet, Nov. 5, 2000, 4 pages.
  • Moon Y.S. et al., A CRM model based on Voice over IP, IEEE, 2000, 5 pages.
  • Nardi, Bonnie A. et al., Interaction and Outeraction: Instant Messaging in Action, AT&T Labs-Research, Information and Computer Science, University of California, Irvine, Irvine, CA, U.S., 2000, 10 pages.
  • Panagos, Euthimios et al., Reducing Escalation-Related Costs in WFMSs, AT&T Labs-Research, 1997, 21 pages.
  • Rosenberg, J. et al., Draft-Roseberg-sip-pip-00.txt: SIP for Presence, Nov. 18, 1998, 22 pages.
  • Silver, A. et al., Unified Network Presence Management, Nortel Network Wireline Solutions, May 21, 2000, XP002195089 Retrieved from the Internet Mar. 28, 2002, 6 pages.
  • Tanir, Oryal et al., Call Center Simulation in Bell Canada, Proceedings of the 1999 Winter Simulation Conference, Canada, 8 pages.
  • U.S. Appl. No. 09/710,042, filed Nov. 8, 2000, 34 pages.
  • Wellman, Michael P., A computational market model for distributed configuration design, Artificial Intelligence for Engineering, Design, Analysis and Manufacturing, vol. 9, Issue 2, 1995, doi:10.1017/S089006040000216X, 1 page.
  • Wurman, Peter R. et al., A Control Architecture for Flexible Internet Auction Servers, Artificial Intelligence Laboratory, University of Michigan, Michigan, U.S., Feb. 6, 1999, 12 pages.
  • Wurman, Peter R. et al., A Parametrization of the Auction Design Space, Games and Economic Behavior 35, 304-338, 2001, May 19, 1998, 35 pages, DOI:10.1006/game.2000.0828, available online at http://www/idealibrary.com.
  • Zwicky, Elizabeth D. et al., Building Internet Firewalls, O'Reilly, US , Sebastopol, Jun. 2000, XP002290595, 3 pages.
  • Voida, Amy et al., Interviewing Over Instant Messaging, College of Computing, GVU Center, Georgia Tech, Atlanta, Georgia; IBM T.J. Watson Research Center, Yorktown Heights, New York, U.S., Mar. 2004, 4 pages.
  • Boyer, David G. et al., Presence Awareness Tools for Virtual Enterprises, Bell Labs, Lucent Technologies, Holmdel, New Jersey, U.S., Oct. 20, 6 pages.
  • Day, M., et al., A Model for Presence and Instant Messaging, XP-002201444 Network Working Group, Feb. 2000, 17 pages.
  • U.S. Appl. No. 10/229,514, Yevgeniy Petrovyhk, Priority Claim.
  • U.S. Appl. No. 09/766,271, Stefaan Coussement, Priority Claim
  • U.S. Appl. No. 09/710,042, Stefaan Coussement, Priority Claim.
Patent History
Patent number: RE46776
Type: Grant
Filed: Dec 12, 2014
Date of Patent: Apr 3, 2018
Assignee: GENESYS TELECOMMUNICATIONS LABORATORIES, INC. (Daly City, CA)
Inventor: Yevgeniy Petrovykh (Walnut Creek, CA)
Primary Examiner: Minh Dieu Nguyen
Application Number: 14/569,598
Classifications
Current U.S. Class: Scheduling, Planning, Or Task Assignment For A Person Or Group (705/7.13)
International Classification: H04L 12/54 (20130101); H04M 3/523 (20060101); H04L 12/24 (20060101); H04M 3/51 (20060101); H04M 7/00 (20060101); H04Q 3/64 (20060101); H04L 12/715 (20130101); H04L 29/08 (20060101); H04L 29/06 (20060101); H04L 12/58 (20060101); H04M 3/22 (20060101); H04M 3/36 (20060101); H04M 3/42 (20060101); H04M 7/12 (20060101);