Patent Publication Number: US-6212178-B1

Title: Method and apparatus for selectively presenting media-options to clients of a multimedia call center

Description:
CROSS-REFERENCE TO RELATED DOCUMENTS 
     The present application is a continuation-in-part (CIP) of application P3313, application number: 09/151,564, filed Nov. 11, 1998, now U.S. Pat. No. 6,108,711, which is incorporated herein in its entirety by reference. 
    
    
     FIELD OF THE INVENTION 
     The present invention is in the field of telecommunication encompassing all existing sorts of interaction multimedia technology, and pertains more particularly to methods and apparatus for providing media options to incoming callers to a multimedia communication center using existing enterprise rules. 
     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 (SCPs), 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 is 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 unit&#39;s (PC/VDU&#39;s) 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/VDUs 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. 
     When a call arrives at a call center, whether or not the call has been pre-processed at an SCP, typically at least the telephone number of the calling line is made available to the receiving switch at the call center by the network provider. This service is available by most networks as caller-ID information in one of several formats such as Automatic Number Identification (ANI). Typically the number called is also available through a service such as Dialed Number Identification Service (DNIS). If the call center is computer-enhanced (CTI), the phone number of the calling party may be used as a key to access additional information from a customer information system (CIS) database at a server on the network that connects the agent workstations. In this manner information pertinent to a call may be provided to an agent, often as a screen pop on the agent&#39;s PC/VDU. 
     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). 
     For purposes of nomenclature and definition, the inventors wish to distinguish clearly between what might be called conventional telephony, which is the telephone service enjoyed by nearly all citizens through local telephone companies and several long-distance telephone network providers, and what has been described herein as computer-simulated telephony or data-network telephony. The conventional systems are referred to herein as Connection-Oriented Switched-Telephony (COST) systems, CTI enhanced or not. 
     The computer-simulated, or DNT systems are familiar to those who use and understand computers and data-network systems. Perhaps the best example of DNT is telephone service provided over the Internet, which will be referred to herein as Internet Protocol Network Telephony (IPNT), by far the most extensive, but still a subset of DNT. 
     Both systems use signals transmitted over network links. In fact, connection to data networks for DNT such as IPNT is typically accomplished over local telephone lines, used to reach points in the network such as an Internet Service Provider (ISP). The definitive difference is that COST telephony may be considered to be connection-oriented telephony. In the COST system, calls are placed and connected by a specific dedicated path, and the connection path is maintained over the time of the call. Bandwidth is basically assured. Other calls and data do not share a connected channel path in a COST system. A DNT system, on the other hand, is not dedicated or connection-oriented. That is, data, including audio data, is prepared, sent, and received as data packets over a data-network. The data packets share network links, and may travel by varied and variable paths. 
     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 multimedia capabilities. 
     In typical communication centers, DNT is accomplished by Internet connection and IPNT calls. For this reason, IPNT and the Internet will be used in examples to follow. IT should be understood, however, that this usage is exemplary, and not limiting. 
     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&#39;s PC while conventional telephony calls are routed to the agent&#39;s conventional telephone or headset. Typically separate lines and equipment must be implemented for each type of call weather COST or IPNT. 
     Due in part to added costs associated with additional equipment, lines, and data ports that are needed to add IPNT capability to a CTI-enhanced call-center, companies are currently experimenting with various forms of integration between the older COST system and the newer IPNT system. For example, by enhancing data servers, interactive voice response units (IVR&#39;s), agent-connecting networks, and so on, with the capability of conforming to Internet protocol, call data arriving from either network may be integrated requiring less equipment and lines to facilitate processing, storage, and transfer of data. 
     With many new communication products supporting various media types available to businesses and customers, a communication center must add significant application software to accommodate the diversity. For example, e-mail programs have differing parameters than do IP applications. IP applications are different regarding protocol than COST calls, and so on. Separate routing systems and/or software components are needed for routing e-mails, IP calls, COST calls, file sharing, etc. Agents must then be trained in the use of a variety of applications supporting the different types of media. 
     Keeping contact histories, reporting statistics, creating routing rules and the like becomes more complex as newer types of media are added to communication center capability. Additional hardware implementations such as servers, processors, etc. are generally required to aid full multimedia communication and reporting. Therefore, it is desirable that interactions of all multimedia sorts be analyzed, recorded, and routed according to enterprise (business) rules in a manner that provides seamless integration between media types and application types, thereby allowing agents to respond intelligently and efficiently to customer queries and problems. 
     An obstacle with the implementation of the desired seamless integration of customer/agent interactions described above is that there are many types of media applications available both to agent&#39;s working in communication centers and customers patronizing those centers, that may differ widely from one another in terms of functional application type or protocol. For example, one IP application may not naturally interface with another IP application due to proprietary constraints. This may be true with certain other applications as well such as e-mail, fax programs, modem programs, file share applications, and so on. Therefore, a customer accessing a DNT network must generally obtain the necessary communication software and in some cases, operating system components, in order to communicate over the network to agent&#39;s operating compatible applications. 
     What is clearly needed for achieving seamless integration between a customer interacting with an agent operating in a modem multimedia communication-center enhanced with a customer/enterprise interaction-network operating-system (CINOS} is a method and apparatus for providing various pre-selected media options, in some instances, supported by application-independent media viewers, to clients of the system that are qualified by the hosting enterprise. Media type on initial contacts may be limited in an embodiment of the invention herein described, by requiring all incoming contacts to traverse a client-facing interface having a capability for identifying the client/customer, and even eliciting information, which may then be used for assigning media type for a continuing transaction. 
     SUMMARY OF THE INVENTION 
     In a preferred embodiment of the present invention an enterprise-hosted multimedia telecommunication center is provided, comprising a client-facing media processing layer for receiving client-initiated transaction requests and for linking clients and enterprise resources by a plurality of media types; a processing layer for processing client transaction requests to establish client communication according to enterprise rules; and a cold-contact principal media interactive interface. The center restricts all cold-contacts to the principal media interactive interface, the principal media interface is capable of identifying clients, and clients are offered communication choices after client identification, according to the identification. 
     In various embodiments the principal media interactive interface is a WEB page, a live agent, or an IVR, and the interactive interface elicits identifying data from the client, the identifying data is used in a categorization process to categorize the client by enterprise rules and procedures, including accessing client data from one or more connected data repositories, and multimedia communication choices are offered to the client through the WEB page after the categorization process. 
     In various embodiments the communication choices offered to the client after identification include types of media, and the types of media are restricted according to client identification. Choices to be offered to a client are predicated, at least in part, on client transaction history recorded in an enterprise data repository. In some cases client transaction history is stored, including transaction strings related to current projects, and live telephone calls are reserved for those clients engaged in a current project. 
     In other aspects of the invention single-media interactive interfaces and methods for practicing the invention are taught. In several embodiments of the invention described below in enabling detail, a facility for controlling access to enterprise center resources is provided that enhances efficiency, saves time, and increases customer satisfaction. 
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS FIGURES 
     FIG. 1 is a diagram of a multimedia communications center enhanced with a network operating system according to an embodiment of the present invention. 
     FIG. 2 is a block diagram illustrating basic layers of a customer interaction operating system according to an embodiment of the present invention. 
     FIG. 3 is a flow chart illustrating basic steps performed by the network operating system of FIG. 2 related to completing interactive transactions between business partners. 
     FIG. 4 is a block diagram illustrating agent-desktop function according to an embodiment of the present invention. 
     FIG. 5 is a block diagram of an exemplary WEB-form customer interface according to an embodiment of the present invention. 
     FIG. 6 is a flow chart illustrating media-presentation and customer-interface logic steps according to an embodiment of the present invention. 
    
    
     DESCRIPTION OF THE PREFERRED EMBODIMENTS 
     FIG. 1 is a multimedia communications center enhanced with a network operating system according to an embodiment of the present invention. A telephony-network architecture  11  comprises an enterprise-hosted communication center  17  that is linked to, in this example, both a publicly-switched telephone network (PSTN)  13 , and a wide area network (WAN)  15 , which may be the public Internet or other digital network, such as a company Intranet. 
     In this particular embodiment communication center  17  handles both conventional telephone calls, which may be categorized as connection oriented switched telephony (COST) calls, and data network telephony (DNT) calls, which may be DNT calls over a private digital network or calls according to a protocol such as the well-known Internet protocol. DNT calls are characterized in that data is transmitted as addressed data packets as opposed to dedicated connections in COST calls. As indicated, PSTN  13  may be a private rather than a public network. WAN  15  may be a company Intranet, the Internet, or another type of WAN known in the art. The particular method of call delivery and call center integration is not particularly relevant for the purposes of this invention. There are many ways known both to the inventor as well as known in the art. Particular issues discussed in the disclosure between the telephones and the computers might be implemented differently depending on the actual system, but shall be deemed equivalent for all purposes of this invention. 
     Incoming COST calls arrive at a network-level telephony switching apparatus  19  in network cloud  13  and are connected over trunk  23  to a central telephony switching apparatus  27  within communication center  17 . From switching apparatus  27 , calls are routed according to existing routing rules over internal wiring  56  to agents&#39; telephones  47 ,  49 ,  51 , and  53  residing at agents&#39; workstations  31 ,  33 ,  35 , and  37  respectively. 
     Incoming DNT calls, and other communication events such as e-mail, file transfers and the like, arrive at a routing node  21  in WAN  15  and are passed on over digital connection  25  to a routing server  29  within communication center  17 . Once calls arrive at server  29 , they may, in some embodiments, be routed directly over LAN  55  according to existing routing rules to personal computer/video display units (PC/VDU) such as PC/VDU  39 ,  41 ,  43 , or  45  located at agent&#39;s workstations  31 ,  33 ,  35 , and  37  respectively. 
     In this embodiment, switch-connected telephones  47 - 53  are also connected to PC/VDU&#39;s  39 - 45  via a headset to computer sound-card according to technique known to the inventor and accomplished via an I/O cable. Thus connected, agents may respond to incoming COST and DNT calls with the same headset. 
     In the exemplary system and communication center shown, the equipment and applications are adapted to provide for multimedia operation at each of the agent stations, so the agents can interact with clients in many different ways, as are known in the multimedia arts. 
     Computer telephony integration (CTI) enhancement is, in this embodiment, provided both at communication center  17  and in PSTN  13 . For example, in PSTN  13 , a processor  61  running instances of a CTI application known as a T-server (TS) to the inventors, and a statistics server (Stat) is connected to telephony switch  19  via CT link  65 . An intelligent peripheral  69  of the form of an interactive voice response unit (IVR) is connected to processor  61  via data connection  63 . Similar CTI equipment is illustrated within communication center  17 . Namely, a processor  67  running instances of TS and Stat and connected to telephony switch  27  via CTI link  71 , and an IVR  69  connected to processor  67  via a data connection  73 , with processor  67  further connected to a local area network (LAN)  55  within communication center  17 . 
     In alternative embodiments there may also be a CTI processor  22  in WAN  15  connected to server  21  by a CTI link  24 . Also in some embodiments a separate data network  66  connects these CTI processors. In this way, intelligent routing may be performed at the network level with negotiation and direction from within communication center  17 . 
     It will be appreciated by those with skill in the art that the CTI enhancements, as immediately described above, may be hosted on one processor at PSTN  13  and on one processor at communication center  17  without departing from the spirit and scope of the present invention. The inventor has chosen to show separate processors having separate functions for exemplary purposes only. It will also be appreciated by the skilled artisan that there may be many more or fewer than the four agent stations shown in communications center  17 , and hardware and software arrangements may be made is a variety of ways. Also, home agents might be connected in a variety of ways to the call center. 
     In a preferred embodiment of the present invention, a customer-interaction network operating system, hereinafter termed (CINOS), is provided for the purpose of managing communications center  17 , and optimizing and recording all agent/customer interactions received at communication center  17  from networks  13  and  15 . CINOS is unique in the fact that it is a multi-tiered object-and process-orientated system wherein logic regarding the various aspects of it&#39;s functionality is achieved via knowledge-based architecture and object modeling. Various functions of CINOS, more fully described below, include capturing (recording), analyzing, routing, and, in many instances, responding via automated process to customers engaged in interactions with the enterprise (company hosting the communication center). CINOS is adapted to support all planned communication mediums such as multimedia DNT applications including e-mail, video mail, file transfers, chat sessions, IP calls, and CTI COST transactions such as voice calls, voice mails, faxes, and so on. 
     Referring back to FIG. 1, CINOS utilizes various LAN-connected machines in order to perform various operations. Among these various hardware implementations are a multimedia server (MIS)  79  adapted to physically store and serve all multimedia transactions, and a customer-information-system server (CIS)  57  adapted to physically store and serve information relevant to customers such as purchase history, financial status, product preferences, contact information, etc. A central server (COS)  77  acts as a host location for a CINOS manager application (noted in text balloon) which is, in effect, the parent application that controls all of the operation and functionality of the system. 
     In addition to the above-mentioned machines hosting CINOS routines, each PC/VDU such as PC/VDU  39 , for example, has a CINOS-agent desktop interface or client application (not shown) adapted to interact with the parent application. Also, each machine that provides particular dedicated function to communication center  17  such as switch-connected CTI processors, IVR&#39;s, and other related equipment host instances of CINOS application-program interfaces (API&#39;s) to enable seamless integration of differing parameters and/or protocols that are used with various planned application and media types utilized within communication center  17 . Such programs may also co-reside or be in any combination or hosted by themselves. Additionally, for performance purposes, additional dedicated network links may exist between those servers, but essentially they are only performance boosters, and hence for clarity purposes, only a simple network is shown. 
     As previously described, CINOS comprises a multi-tiered architecture. This unique architecture comprises an external media layer for interfacing with the customer or business contact, a workflow layer for making routing decisions, organizing automated responses, recording transactions, and so on, and an internal media layer for interfacing and presenting interactions to an agent or knowledge worker. An innovative concept associated with CINOS involves the use of tooled process models, knowledge bases, and other object models as base instruction for it&#39;s various functions. These modular conventions may be inter-bound with each other, and are easily editable providing a customizable framework that may conform to virtually any existing business logic. 
     In simple operation, and after any network level routing, COST calls and DNT calls including other media events arrive at communication center  17  to telephony switch  27 , and routing server  29  respectively. Network level routing, as defined herein, includes any intelligent implementation that may be in place and aided via processors  59 ,  61 , and  22 . Load balancing to multiple communication centers, and transferring customer data obtained at network-level over data-network connection  66  would be examples of such network-level routing. 
     Once a call or other communication event registers at either switch  27  or routing server  29 , CINOS immediately identifies the media type associated with the call and begins it&#39;s processes depending on enterprise rules. For example, a live COST call may first be routed to IVR  69  whereby the customer can be presented with varying choices such as leaving a voice message, waiting in queue, receiving a call back, or perhaps an e-mail, and so on. Interaction by IVR  69 , in this instance, will preferably be via voice recognition technique such as is known in the art, but may also be via touch tone response or other known method. As previously described, the caller may elect from a number of options, such as to hold for a next available agent, select an automated response such as a fax back, or perhaps a later agent-initiated response such as an e-mail or call back. In all cases, CINOS seamlessly processes and executes the logic required to accomplish the goal of the caller in a media and application-independent fashion. 
     DNT events are handled much the same way as described above for live callers. For example, an IP call may be routed to a digital equivalent of an IVR for interaction or queued for a next available agent, and so on. In one embodiment, IVR  69  may be adapted to handle both COST and DNT interaction. 
     All interactions with live external media, including actual text-based events whether live or not, are recorded and stored in MIS  79  with an associated text version of the media stored as well, and becoming part of an overall threaded contact history. This is accomplished in varying ways according to existing parameters such as media type, whether the event is a live call, and so on. For example, CINOS may execute a command directing IVR  69  to digitally record an incoming COST call during customer interaction and then store the voice recording of the transaction in MIS  79 . A text version of the recording either created simultaneously from the voice recording via voice-to-text techniques (known in the art), or created by a live attendant via manual annotation may be sent to and stored in DB  79 . An IPNT call arriving at routing server  29  may be similarly recorded and stored in MIS  79  with an associated text version of the interaction stored in DB  79 . E-mails, video calls, voice mails and so on are similarly handled. For example, an incoming e-mail is stored in MIS server  79  while text from the e-mail may be extracted and stored associated with the e-mail. 
     The purpose of the text version of the event is twofold. Firstly, a complete text-based transaction history of communication center  17  may be compiled and reserved for later access and audit. Secondly, an agent or knowledge worker may, in some instances, see the text version of the event at the same time that he receives routed notification of the event. In this way, an agent may begin mental preparation before taking a call. The text version of an event must be machine-readable and human readable at times displayed. Interactive media-independent viewers, part of the agent&#39;s client application, may be used to disseminate information which may initially not be human readable. 
     It is important to note here that the text-based version of an event may or may not be a complete and verbatim rendition of an actual media event. For example, an e-mail may contain many documents each having many pages of text. Therefore, the text-based version of a particular e-mail event may simply contain the name and particulars regarding the author, a purchase order, and a list of the enclosed documents by title, and basic content or memo as well as a possible manual annotation. The attachments to the e-mail may be stored separately, and be also cross-indexed and retrievable. Seeing the purchase order when the event is routed to an agent desktop tells the agent that this e-mail is important. 
     A fax, stored originally as a bit-mapped document, may be converted to text in the system via optical recognition (OCR) technique wherein sometimes only certain content such as the authors contact information, basic intent of the fax, and perhaps special numbers or codes contained in the original fax are recorded in a text version  79 , sometimes the whole text is OCR&#39;d, while the original fax is stored in it&#39;s entirety in DB  79 . Such codes or numbers that are specifically parsed from actual media may be part of a unique coding system set up by the enterprise whereby customers are directed to include such codes or numbers with their orders, service requests, and so on. 
     Parsing text messages is accomplished via a text-analyzer known to the inventor. In other non-text media types, such as video or graphics, descriptive notes may be taken via live attendant and stored in DB  79  as previously mentioned. Voice recognition technology may also be used in a case of recorded sound or video with sound. All transactions regardless of media type are thus recorded and stored according to enterprise rules with at least a meaningful part of the content if not all of the content of such transactions converted to text and stored in DB  79  associated with the recording of the event. Again, the importance of the text version is that the extracted knowledge of the transaction therein is in machine-operable code, allowing search and cross-referencing functions that may otherwise not be possible. 
     After incoming events are analyzed and processed with regards to queuing, recording, storing, etc. CINOS decides the disposition paths of each event. For example, live calls in queue are routed to live agents if available, if this is the priority action in the enterprise rules. E-mails are either routed to next available agents using a push technology, or simply stored in MIS server  79  where they may be retrieved by agents after receiving notification. Recorded events such as IVR voice requests are stored in MIS server  79  where they may be retrieved by agents, and so on. 
     By the use of routing and routing notification events, any media may be routed to an appropriate agent based on skill, or any other rule-based routing method over LAN  55 . Actual multimedia events may be accessed from MIS server  79  at the agent&#39;s discretion, or by rule, and text-based versions of those events stored in DB  79  may be mirrored and routed to the agent along with notification of the incoming event. 
     Other services may be performed by CINOS such as responding to media requests without agent participation via initiating automated fax responses, out-bound dialing campaigns wherein recorded information is given to a customer perhaps concerning an order placed by the customer, and so on. Networking via business or chat applications between several business partners, customers, agents, and so on, is possible wherein each entry may be stored in DB  79  as part of a discussion thread including responses of another media type, perhaps initiated by a communication-center agent to one of the participants during the discussion. 
     As a general rule, fill multimedia storage is done in a mass storage server, and linked by cross-indexing to the database. Depending on the business model, full text or only partial annotation is stored in the database, or a mix therof, e.g by media type. 
     In addition to supporting a wide variety of applications and protocol, CINOS is provided with the tools for building media-independent self-help wizards that are adapted for problem solving and reduction. Similarly, external and internal interaction media viewers are provided and adapted to support any media of choice. 
     CINOS uses object modeling and linking techniques that are known in the art to effect much of it&#39;s goal of presenting a seamless customer interaction with an enterprise agent or knowledge worker operating in a communication center such as center  17 . For example, an interaction object model (IOM) represents a transcript of all interaction history stored in DB  79  and provides an audit trail of the state of transactions of all interactions. An interaction process model (IPM) controls how events are handled within the operating system. 
     An additional set of models handle how agents receive their routed media such as via traditional push model, blended push model, publish and subscribe model, or interrupt model. Prioritizing interaction events may also be accomplished through varying the push theme or scheme. For example, traditional push technology for e-mail means that only e-mail (media type) is being worked on by an agent By blending the push model with a publish and subscribe model, the interrupt model is created wherein the agent may subscribe to various routed media such as answering phones, and responding to faxes, but may be interrupted for an important interaction of another media type such as e-mail and so on. In this way an agent&#39;s time may be utilized according to enterprise rules within an automated environment. 
     Outbound campaigns may be configured according to enterprise rules and media preference using a single rule-set knowledge-base. This single set of outbound tools can be used to initiate customer dialog via predictive dialing, e-mail push, automated recorded messages, and so on. 
     It will be apparent to those with skill in the art that common object modeling (COM) can be used to create virtually any type of model for any type of enterprise situation. It is the intention of the inventor to provide the applicable control codes known in the art for building process and object models and enabling the linking and interaction between the models. As previously described, it is partly the fact that CINOS uses these various models and knowledge bases to achieve desired interaction that sets it above current-art systems. The inventor knows of no such network interfacing operating system that is based on the above described technology. 
     CINOS may be implemented in a number of different topologies. For example, CINOS may be implemented as a centralized topology with one communication center as shown here in FIG. 1, a distributed topology wherein a single communication center may span multiple physical locations, a segmented communication center wherein a single pool of agents services more than one company or customer base, or a wide communication network wherein a plurality of communication centers such as center  17  cooperatively service a common pool of customers or a customer base. Enterprises involved in commerce such as large financial institutions hosting many geographically separate communication centers may build their entire networking system using CINOS architecture in standardized and distributed fashion. There is no limitation to the type of enterprise that may use CINOS as it may be tooled to accommodate virtually any network architecture linked to a communication center having DNT capability. 
     It will also be apparent to one with skill in the art that CINOS routines according to various embodiments of the present invention may be included and implemented at the network level without departing from the spirit and scope of the present invention such as in processor  61 , and IVR  59  in PSTN  13 , or in routing node  21  in WAN  11 . 
     FIG. 2 is a block diagram illustrating basic layers of the network operating system according to an embodiment of the present invention. As previously described with reference to FIG. 1, CINOS comprises three basic operating layers. They are an external media layer  83 , a workflow layer  85 , and an internal media layer  87 . External media layer  83  interfaces directly with the customers or business contacts or partners as illustrated via customers a and b, and business contact c. The bi-directional arrows beneath each of the above mentioned participants illustrate interactive participation with CINOS on the customer side. 
     External media layer  83  may, in one embodiment, be a multifaceted, web-based self-help interface providing news information and a host of other services that may be personalized by the customer. In many respects, external media layer  83  in this embodiment is similar to a web browser. 
     Workflow layer  85  comprises 3 basic function categories beginning with a content analysis category  89  wherein textual analysis, voice analysis, IVR interaction, recording and storing takes place. The next category is context resolution  91 . Context resolution involves customer identification, business process binding, preparation for routing, and so on. A third category termed interaction routing  93  comprises various processes associated with the presentation of the interaction to agents, service persons, knowledge workers, business partners, customers and the like, that is, all transaction partners. Category  93  covers queuing, skill-based routing, automated treatment, workflow models, and so on. 
     Internal media layer  87  comprises an agent desktop interface not shown in FIG. 1, but described in more detail below. Both external layer  83  and internal layer  87  contain the required tools for enabling media and application-independent interfacing such as previously mentioned self-help wizards, media viewers, and other controls as prescribed via enterprise rules. 
     Internal media layer  87  provides an agent with, among other options, information about the customer or contact, information about current or historical business processes, information about current interactions and their relationship to business processes, and a knowledge-base to guide the agent or knowledge worker with interaction response and workflow. An agent a, and agent b, and a knowledge worker c are shown herein interacting with the system as illustrated via bi-directional arrows. The skilled artisan will recognize these are merely examples, and there may be many more such persons, and interactions in some instances may be routed to machines for response. 
     It will be apparent to one with skill in the art that the multi-tiered architecture of CINOS such as is illustrated herein may comprise many more or differing steps or processes without departing from the spirit and scope of the present invention. 
     FIG. 3 is a flow chart illustrating basic steps performed by the interaction operating system of FIG. 2 related to completing a transaction between a customer and an agent, wherein the transaction is initiated by the customer. Similar steps may be accomplished in the opposite direction for communications initiated by an agent, as the system is bi-directional, but the present example will serve to teach the inventive aspects of the system. In step  95 , an incoming transaction, such as a live call, an e-mail, etc., is received at the appropriate CTI switch (COST) or routing server (DNT) in a CINOS communication center such as center  17 . In step  97 , customer and media type are identified and interaction proceeds. 
     All transactions, whether live calls, such as video calls, DNT calls and COST calls, or text-based documents, such as e-mails, are recorded and stored in one or more mass storage devices handled by one or more database applications. This may be taken as server  79  of FIG. 1, although the diagram of FIG. 1 is exemplary. 
     A principle object of the invention is to extract maximum information from every transaction for building a knowledge base that can be used for dynamic management and future analysis and development. This is done primarily by data mining, which is applicable to machine-operable code, that is text. Because of the nature of the extraction, there is a difference in the way live calls and text-based media is handled. 
     Discrimination as to the text nature of the media is made at step  99 . If the media chosen by the customer is already text-based, then the transaction is recorded as received ( 101 ), and a data mining application extracts important information in step  103  and stores it in the knowledge base. The distinct portions and versions of the transaction, such as the originally recorded version and any extracted data are related to one another and to other knowledge previously stored, and become part of a threaded interaction history associated with an ongoing interaction and ultimately of an overall contact history. 
     If the media chosen by the customer is determined in step  99  to be a live interaction such as a COST or IPNT call, then the existing knowledge base is accessed at step  107 , and the call is routed to the best fit agent. This may, of course, be done in a number of ways, such as an ADC, skill-based routing as known to the inventors, transfer to an IVR for automatic processing, and so on, as may be dictated by enterprise rules. If routing is to an agent, customer information may be retrieved from CIS server  57  (FIG. 1) and sent to the agent&#39;s PC, and appropriate scripts may be provided to guide an agent in interacting with the caller. 
     In step  109  the actual transaction is recorded as it takes place, which, in the case of live calls, may be a video or an audio recording or a combination of both. Preferably the recording is digitized. 
     In step  111 , a maximal text version is prepared from the actual transaction. The ability to do so depends to a degree on the sophistication of the system. This process may be as simple as a person adding notes for annotation or as sophisticated as a voice-to-text application preparing a full text version as the transaction transpires. 
     In step  113  the text version is mined for data and resulting knowledge is stored in the appropriate knowledge base for future use, and added to overall record with appropriate cross-referencing. 
     It will be apparent to one with skill in the art that there will be many routines comprising various steps for performing different processes as may be determined by enterprise rules which may likewise vary depending on, among other considerations, company type, product and or service type, communication center architecture, whether or not the system architecture is centralized or distributed, and so on. The embodiment taught herein is meant only as a basic example of process functionality related to CINOS processing of an incoming event. 
     FIG. 4 is a block diagram illustrating agent-desktop function according to an embodiment of the present invention. An agent-desktop client  115 , part of the CINOS overall architecture, enables an agent or knowledge worker to configure and control his or her interface to the rest of the system and to external media. Client  115  may be personalized according to a particular agents parameters. A desktop interface  117  may appear and function much like a personalized web-browser containing many similar attributes related to network capabilities including full multimedia function, software tool kits, linking and embedding capability, and so on. 
     An HTML client application  119  oversees all of the network capability previously mentioned. In this embodiment for example, HTML client  119  communicates with an Internet information server  121  using HTTP protocol which is standard. Client  119 , if provided minimally, may be used in conjunction with an Internet browser for full multimedia function. In some embodiments, it may be maximally provided to be a fully featured client with full web browser function. For example, an agent may create and edit web forms, web pages, embed controls into such web-based forms or pages to provide certain customer interaction mechanisms in addition to having a fully functional navigation tool at his disposal. 
     In another embodiment, Server  121  may be a server on a private network or corporate WAN instead of an Internet server. In a preferred embodiment, however, any number of servers on the Internet and/or linked to a WAN other than the Internet may communicate with client  119  as it intended to support all existing and known communication protocols. 
     A windows client  123  is provided to seamlessly integrate existing applications on the agent&#39;s PC to network applications and processes. This may be implemented via a desktop tool-kit  125  that contains all of the required controls for building, integrating and customizing the interface. 
     A business-logic layer comprises business object models  129 , hereinafter termed business objects  129 , representing contacts, interactions, knowledge-bases, events, routing processes, and other system routines. Integration and interaction of the various described desktop components with these logics is accomplished via common object modeling (COM) which is known in the art and available to the inventor. Desktop to CTI integration is accomplished via controls provided or created with a CTI set of tools or tool kit (not shown). For example, if the enterprise desires to blend voice and e-mail, the CTI tool kit would be used to build and integrate the interface. 
     Existing network applications such as CIS, enterprise resource planning (ERP), Commerce, and the like interact with various business objects using COM and may also interact with a physical database using ODBC and SQL. 
     Customer Interface Media Window 
     According to a preferred embodiment of the present invention, CINOS access by customers of an enhanced multimedia communication center, such as center  17  of FIG. 1, is controlled by means of a customer-facing media interface, by which customers may be identified and even categorized according to numerous criteria. In some cases access may be controlled through subscription, or according to other qualifying criteria such as may be deemed appropriate by the enterprise. For example, if the enterprise is an exclusive investment club, membership may be required. Categorizing criteria may include demographic information such as income level, credit history, or any other attribute that may be quantified and used to categorize a customer. 
     An enterprise-controlled access point may be defined as an interfacing window or portal created and maintained at a typical customer entry point in a network as may be known in the art. Such interfaces may take the form of a WEB-based customer interface (a WEB page), an interactive voice response (WR) unit, a service control point (SCP), or some other customer-facing system or apparatus as may be known in the art. 
     For the purposes of this specification, an example of an enterprise-controlled WEB-form access and interface window is illustrated as an example for a preferred embodiment. The inventor deems such an interface to be most adept in offering best-fit media options while remaining accessible to a large customer or client base. 
     FIG. 5 is a block diagram of a WEB-form customer interface according to an embodiment of the present invention. WEB form  133 , hereinafter termed access window  133 , is provided to be a part of an enterprise&#39;s WEB page which may be accessed through Internet connection and navigation, as is known in the art. Widow  133  is part of the CINOS software architecture described above, and represents the initiation of any customer interaction with the hosting enterprise. A WEB counter  143  is provided and records the number of visits to window  133 . 
     Window  133  is built and edited using COM codes available to the inventor and typically found in tool kits adapted for the purpose of creating interactive displays on a WEB page. Such a tool kit may be located on an agent&#39;s desktop, perhaps part of an agent&#39;s HTML client such as client  119  of FIG.  4 . In one embodiment, it may be part of a system administrator&#39;s tool kit. 
     Window  133  contains interactive options directed at various categories and functions. For example, a new client section  135  contains interactive options related to adding a new client to the active customer base of the enterprise. A customer service section  137  contains interactive options presented to existing clients needing service. A new order section  139  contains interactive options presented to existing clients wishing to do new business. 
     Each offered interactive option is an embedded executable function having the appropriate links to other system areas of CINOS such as may be relevant to the immediate interaction such as to services offered, routing routines, database searching, interaction recording, and so on. 
     An innovative function of window  133  is to provide front-end control of access to the enterprise by existing and potential clients/customers. For example, as a client, contact, or potential client interacts with the various media and functional options presented by the enterprise in window  133 , he or she is being directed according to enterprise rules in such a way that he or she may first be qualified or not to patronize the enterprise. Secondly, the contacting person may be categorized and sorted as to type of qualified customer. Thirdly, the contacting person may be directed to pre-selected media options by the enterprise for various services offered including but not limited to routing live interactions, and so on. 
     In a preferred embodiment of the present invention, access window  133  is fully customizable, based on customer data and enterprise rules with the focus of such customization directed toward benefiting the enterprise and ultimately the client. That is, the client&#39;s options within window  133  are pre-selected and preferred by the hosting enterprise based in part on data about the client, details about the client&#39;s communication equipment and software, and enterprise rules and constraints. In some embodiments, the client may aid in customizing window  133 . However, as it is desired by the enterprise to provide service in a cost-effective manner, the client will be presented with options as preferred by the enterprise in most cases. 
     To further illustrate, refer now to new client section  135 . If window  133  is part of the enterprise WEB page, as is the case with this example, there will be a variety of visitors which may or may not be pre-qualified by the enterprise. Therefore, an interested party would begin (and be restricted to) taking a new client survey, illustrated as one of the options in section  135 . If the enterprise rules require this as a first step, then the other options may be enabled only upon completion of the survey. By choosing new client survey, a second window may contain various survey options such as via e-mail, interactive voice recording, type and send method, or the like. 
     Information taken in the client survey is recorded and entered into a CINOS database such as DB  75  of FIG.  1 . Such information may also be compared against enterprise rules or constraints, and other known information as may be available to the enterprise. Assuming the client is now recognized by the enterprise, the client&#39;s media hardware and telephony information may be recorded for future interaction purposes. Such information may include the client&#39;s personal computer parameters including modem type, Internet connection type, computer platform type, type of Internet phone application installed, etc. Similarly, COST telephone parameters may be recorded, such as personal phone number, business phone number, cellular phone number, forwarding numbers, and so on. Such data will influence latter customization of his personal window  133  for the particular client including the types of media that will be offered. 
     Finally, the client may be asked to create a password for the purpose of accessing CINOS. A section  141  is provided containing a network log-in option along with download sections for obtaining permanent and or temporary software as may be desired or needed, or, in some cases, required for the client to access certain services, view certain content, and so on. 
     Section  137  presents media options for clients seeking customer service from the enterprise. These options are, in a preferred embodiment, presented in a customized or personalized fashion within the client&#39;s window  133  as was described above. Therefore, each client patronizing the enterprise may access a version of window  133  that differs in look and functionality than that of another client. In this example, service section  137  contains options for e-mail, chat program, fax program, a self-help wizard, and a voice wizard. Other media types may be added or subtracted from the client&#39;s window  133  depending on any of several criteria. Personalization of widow  133  takes into account client information as stored in CINOS database  75 , service-agent media availability and preferences, and perhaps any overriding enterprise rules. Unless and until a client is identified there are typically no options presented to the client for continuing a transaction with the enterprise. 
     For an identified client, by selecting the e-mail option, the client&#39;s preferred e-mail program may be activated for the purpose of sending a message to or soliciting a reply from a service agent. By selecting chat program, the client may be launched into a scheduled service seminar featuring many clients interacting with a service expert regarding a certain subject. One enterprise rule regarding section  137  may be that there is no telephone or I-phone media option for customer service for a client in the absence of an ongoing project with the particular customer. In this sense an ongoing project includes any unfinished business that the client is involved in with the enterprise. 
     Self-help wizards and voice wizards as illustrated in section  137  may be offered to help a client resolve an issue without taxing further resource. Such wizards may be customized based on a client&#39;s recorded data, perhaps confirming past interactions, providing account or order status, and so on. In some embodiments, selecting an option might avail several additional options. For example, selecting chat program may avail three possible chat programs to choose from with different schedules, content, and functionality attributed to each individual program. 
     New order section  139  in this example contains various options adapted to facilitate placing orders. The options as illustrated herein include, but are not limited to, I-phone, call back, promotional models, video presentations, an on-line viewer, and an order wizard. Interaction is the same as was stated with regards to section  137 . For example, selecting promotional models, accesses a database containing the current promotional information and features of products which may be viewed interactively by the client using an on-line viewer offered as one of the functional options (tool). The options presented in the New Orders section may also be customized according to client identity, demographics, transaction history, and enterprise rules. 
     On-line viewers may enable the client to view documents that are not supported on his computer platform. Selecting video presentation may avail several types of videos for viewing ,such that the client may choose one. If the client does not have a viewer installed on his computer which will support the offered video, perhaps the on-line viewer may play the video, or the client could download a temporary viewer from section  141 , etc. Selecting call back may bring up a second array of media choices made available by the enterprise for receiving a reply interaction from an agent. 
     By providing a controlled interface window such as window  133  the enterprise may control routing and interaction right from the beginning of customer contact. Through the innovative method of linking and reporting to other CINOS functions, and repositories, much real-time personaliation of window  133  according to enterprise rules and customer parameters may be made automatically. For example, if a client&#39;s history indicates a propensity toward frequent buying, an I-phone option may be presented in customer service section  137  in his window  133  immediately after such a determination so that he may get direct customer service at all times. 
     Certain media options, as described above, may be afforded a certain priority over one another regarding interaction with the enterprise. For example, a VIP client may have live interactive media choices offered in window  133  such as I-phone, call back to COST phone, video phone, etc. A client known for infrequent contact or troublesome interactive history may be limited to text-based interaction such as e-mail and so on. 
     As an integral part of CINOS functionality, window  133  acts as a portal through which existing and potential clients may be screened, categorized and routed according to enterprise rules. Customer interfaces such as window  133  may be provided at various locations on a WAN such as the Internet without departing from the spirit and scope of the present invention. Such portals may exist in different geographic regions, and may be created for differing customer bases such as one for Latin America, and one for the pacific rim, and so on. Instances of CINOS routine may be distributed widely over a network. 
     Although the example provided herein is of a WEB form, it will be apparent to one with skill in the art that a CTI counterpart may be created for the COST telephony network. Such a case may be a CINOS enhanced IVR at an SCP or customer access point in the COST network. 
     CINOS, as previously described, optimizes customer/agent interaction in a manner which is economical and cost efficient to both the enterprise and the patronizing client. The customer interfacing window as taught herein with regards to FIG. 5 is innovative in that it is a fully customizable portal that facilities seamless integration between clients and enterprise agents according to enterprise rules. Further innovation is evident in that client data is fully and seamlessly integrated with CINOS intelligence and enterprise rules regarding routing of interactions and other constraints or limitations that are programmed into the system. In effect, logic from the front end, or customer side, to the back end or agent side is linked and accessible to all appropriate CINOS routines which include applicable CTI CINOS routines. The various customer interfacing logic is explained more fully below in a series of process logic steps in a flow chart. 
     FIG. 6 is a flow chart illustrating media-presentation and customer-interface logic steps according to an embodiment of the present invention. In step  145 , a visitor registers at an enterprise&#39;s WEB page. The visitor is identified according to enterprise rules in step  147 . In step  148  CINOS determines the current status of the visitor after searching known client and contact data records. For example, the visitor may be a potential new client, an existing client, or an existing business contact. Although not specifically illustrated, a potential or new-business-client is not typically logically separated from a potential new-client until further process ensues in step  149  with regards to qualification via survey. 
     If the visitor wishes to be a client, he may log-in to the network system in step  159 . Log-in may be automatic in the event that CINOS remembers the client&#39;s assigned password, or perhaps typing the password or other code may still be required for security reasons. At the time of log-in, window  133  is presented in personalized fashion according to client data and enterprise rules in step  161 . In step  163 , interaction between an enterprise entity and the client begins with a media type that is offered by the enterprise and selected by the client. An enterprise entity, as immediately described above, is herein defined as an agent, knowledge worker, service person, or any other live attendant, as well as any entity constituting an automated response action such as an automated fax, an IVR, automated file downloads, etc. 
     At step  148 , if it is determined that the visitor is new, then a new client survey is conducted in step  149 . Step  149  will determine if the new visitor is a client or business contact via the survey process. As described with reference to FIG. 6, the client survey may be conducted using a variety of known techniques and media Presuming that a new visitor qualifies as a client or business contact in step  149 , he or she may be asked to create a password in order to provide access to CINOS. In step  153 , the clients appropriate communication and system parameters are recorded for future reference and for use in customizing window  133 . 
     At step  155 , a client instance of CINOS, or perhaps another enabling application, may be presented for download by the client. In some embodiments, there may be no required software for download. Therefore, step  155  may be considered optional in this regard. In step  157 , the new client may log-in to the network system and begin interaction. Because the client, in this case, is accessing the system for the first time, the steps wherein he would obtain a customized window and begin interaction with an enterprise entity are not shown as intermediate configuration of media choices, product preferences, and the like, may still be required before a customized interface may be presented. In one embodiment, the client may not see a customized window until the next time he or she attempts to access the network. 
     Steps  165 ,  167 , and  169  for an existing business contact as determined in step  148  are similar to steps  159 ,  161 , and  163  for an existing client although the rules for interaction such as media used, personnel involved and so forth will be different. For example, in step  167  an existing business contact may be offered the option of using a network-collaboration program wherein I-phone, file sharing, video conferencing and the like are inherent to that one application. 
     It will be appreciated that there are many possible logic sequences or steps that may be followed in interfacing and enabling interaction between a client and an enterprise entity without departing from the spirit and scope of the present invention. FIG. 6 presents just one possible example of many. 
     It will be apparent to one with skill in the art that the rules governing the types of media offered to clients may be based on a combination of variables such as may be decided upon by the enterprise without departing from the spirit and scope of the present invention. Likewise, offered media types may be added or withheld from a client over a period of time based on such variables. Moreover, such additions or subtractions of media availability with regards to customer interface window  133  may be automated and based on calculated variables. 
     In one embodiment, a client may add or subtract media choices if desired, however, the enterprise may reserve the right not to engage such media if added by a client. 
     In one embodiment, special application-independent media viewers such as the viewer offered in section  139  of window  133  of FIG. 5, are offered to clients and possessed by agents so that initial illegible information may be made human readable regardless of the authoring application used by the agent or the client in the process of interaction. 
     It will be apparent to one with skill in the art that CINOS may be implemented in a single communication center, or in a plurality of communication centers linked via WAN without departing from the spirit and scope of the present invention. 
     It will also be apparent to one with skill in the art that rules may be created which govern access to CINOS without departing from the spirit and scope of the present invention. For example, customers may be required to subscribe to CINOS, and may also be provided with a customer application enabling such access. In another embodiment, access may be given to the general public according to established security rules governing commerce, financial transactions, and other processes. 
     There are many existing and future implementation opportunities for an interaction operating system such as CINOS many of which have already been stated. The spirit and scope of the present invention is limited only by the claim that follow.