Recherche Images Maps Play YouTube Actualités Gmail Drive Plus »
Connexion
Les utilisateurs de lecteurs d'écran peuvent cliquer sur ce lien pour activer le mode d'accessibilité. Celui-ci propose les mêmes fonctionnalités principales, mais il est optimisé pour votre lecteur d'écran.

Brevets

  1. Recherche avancée dans les brevets
Numéro de publicationUS8005204 B2
Type de publicationOctroi
Numéro de demandeUS 11/145,513
Date de publication23 août 2011
Date de dépôt3 juin 2005
Date de priorité3 juin 2005
État de paiement des fraisPayé
Autre référence de publicationUS20070019800
Numéro de publication11145513, 145513, US 8005204 B2, US 8005204B2, US-B2-8005204, US8005204 B2, US8005204B2
InventeursRobert R. Bushey, Sarah Korth
Cessionnaire d'origineAt&T Intellectual Property I, L.P.
Exporter la citationBiBTeX, EndNote, RefMan
Liens externes: USPTO, Cession USPTO, Espacenet
Call routing system and method of using the same
US 8005204 B2
Résumé
A call service center can include a call routing system that can use one or more action object identifiers. In one embodiment, a future action object identifier is associated with a task that is desired or otherwise intended to be performed at the call service center. The call routing system may route the call to a module that is not associated with the future action object identifier or perform a portion of a task within the same module, wherein the portion of the task is not associated with the future action object identifier. In another embodiment, at least two action object identifiers can be passed with a call from one module to another module. In a particular embodiment, a past, current, or future action object identifier, other information related to the call, or any combination thereof may be passed from one module to another module with the call.
Images(5)
Previous page
Next page
Revendications(31)
1. A method comprising:
generating a first identifier at a first module of a data processing system, wherein the first identifier is generated in response to a call received at the data processing system and wherein the first identifier identifies a first action;
after generating the first identifier, automatically routing the received call and the first identifier to a second module of the data processing system, wherein the second module is associated with one or more actions and wherein the first action identified by the first identifier differs from each of the one or more actions associated with the second module;
after routing the received call and the first identifier to the second module, performing one of the one or more actions at the second module; and
after performing the one of the one or more actions at the second module, routing the received call from the second module to a third module of the data processing system, wherein the third module is associated with the first action.
2. The method of claim 1, wherein the first action comprises a purchase of at least one of a product and a service by a caller associated with the call.
3. The method of claim 2, wherein the action performed at the second module comprises determining account status information of an account of the caller associated with the call.
4. The method of claim 1, further comprising:
receiving an interrupt signal at the second module while the one of the one or more actions is being performed at the second module;
in response to receipt of the interrupt signal at the second module, routing the call from the second module to an attendant interaction module;
receiving an attendant input signal from an attendant at the attendant interaction module; and
in response to receiving the attendant input signal at the attendant interaction module, routing the call from the attendant interaction module to the third module.
5. A data processing system comprising:
a first module, the first module configured to:
generate a first identifier that identifies a first action, wherein the first identifier is generated in response at least in part to receipt of a call; and
pass the call and the first identifier to a second module, wherein the second module is associated with one or more actions and wherein the first action identified by the first identifier differs from each of the one or more actions associated with the second module; and
the second module, wherein the second module is configured to:
perform one of the one or more actions; and
pass the call, or have the call passed, to a third module, wherein the third module is configured to perform the first action.
6. The data processing system of claim 5, wherein each of the first, second, and third modules is configured to pass a second identifier associated with the call to a corresponding subsequent module.
7. The data processing system of claim 5, wherein the second module is an attendant interaction module that is configured to:
transmit the first identifier to a first output port;
receive an attendant input signal from an attendant at a first input port of the attendant interaction module; and
transmit the attendant input signal to a disposition module.
8. The data processing system of claim 5, further comprising a disposition module and a routing module, wherein:
the second module is an attendant interaction module and is further configured to transmit the first identifier to a first output port in response to an attendant input signal received at a first input port of the attendant interaction module;
the disposition module is configured to:
receive the call, the first identifier, and the attendant input signal from the attendant interaction module; and
generate a disposition signal in response at least in part to the attendant input signal; and
the routing module is configured to:
receive the call, the first identifier, and the disposition signal from the disposition module; and
route the call and the first identifier to the third module in response at least in part to the disposition signal.
9. A computer-readable medium storing processor-executable instructions that, when executed by a processor, cause the processor to:
generate a first identifier at a first module in response to information gathered from a call that has been received, wherein the first identifier identifies a first action;
route the call and the first identifier to a second module, wherein the second module is associated with one or more actions and wherein the first action differs from each of the one or more actions associated with the second module; and
route the call to a third module that is associated with the first action after routing the call to the second module.
10. The computer-readable medium of claim 9, wherein the first identifier is associated with a future task pertaining to the call.
11. The computer-readable medium of claim 9, wherein the instruction to route the call to the third module comprises an instruction to pass the firstidentifier from the second module to the third module.
12. The computer-readable medium of claim 9, wherein:
one of the one or more actions includes determining an account status; and
the first action includes purchasing at least one of a product and a service.
13. The computer-readable medium of claim 9, wherein a first instruction to route the call to the third module is executed by the processor in response at least in part to the first identifier routed to the second module.
14. The computer-readable medium of claim 9, wherein the processor-executable instructions comprise an instruction to route the call from the second module to an attendant interaction module in response at least in part to receiving an interrupt signal when the call is being processed by the second module, wherein the instruction to route the call to the third module is executed in response at least in part to receiving an attendant input signal at the attendant interaction module.
15. A computer-readable medium having data to be used with a call routing system, wherein the data is embodied within the computer readable medium, the data storing a processor-executable instruction that, when executed by a processor, causes the processor to:
pass a call, a first identifier that is associated with a first action, and a second identifier from a first module to a second module, wherein the first and second modules are within the call routing system, wherein the first identifier and the second identifier are associated with the call and are generated in response to information received via the call, wherein the second module is associated with one or more actions, and wherein the first action differs from each of the one or more actions.
16. The computer-readable medium of claim 15, wherein each of the first identifier and second identifier comprises one of a past identifier, a current identifier, and a future identifier.
17. The computer-readable medium of claim 15, wherein the processor-executable instruction further causes the processor to pass a third identifier from the first module to the second module, wherein:
the first identifier comprises a future identifier that is associated with a first task to be completed at a future time;
the second identifier comprises a current identifier that is associated with a second task to be completed at a present time; and
the third identifier comprises a past identifier that is associated with a third task that was completed at a prior time.
18. The computer-readable medium of claim 17, wherein the second task comprises one of authenticate caller and check account.
19. The computer-readable medium of claim 9, wherein a plurality of distinct identifiers are generated that are simultaneously associated with the call and include:
a past identifier associated with a past task that has been performed;
a current identifier associated with a current task that is currently being performed; and
a future identifier associated with a future task that is to be performed at a future time.
20. The computer-readable medium of claim 17, wherein the future identifier indicates that a caller originating the call desires to purchase a service, a product, or a combination thereof.
21. The computer-readable medium of claim 17, wherein the second task comprises authenticate caller and the third task comprises receive the call.
22. The computer-readable medium of claim 17, wherein the second task comprises check account and the third task comprises authenticate caller.
23. The computer-readable medium of claim 22, wherein the processor-executable instruction further causes the processor to pass a result identifier indicating that an account associated with a caller that initiated the call has a zero or positive balance.
24. The computer-readable medium of claim 22, wherein the processor-executable instruction further causes the processor to pass information including a reason associated with one of success and failure of the second task.
25. The method of claim 1, wherein the first identifier is generated at the first module in response to information gathered via the call that is received.
26. The method of claim 1, wherein a caller associated with the call does not speak during the call.
27. The method of claim 1, further comprising generating:
a second identifier associated with a second action that is being performed at the second module; and
a third identifier associated with a past action that has been performed at the data processing system.
28. The method of claim 27, further comprising storing the first identifier, the second identifier, and the third identifier at a memory that is coupled to the data processing system.
29. The data processing system of claim 5, wherein the first identifier is generated in response to information gathered via the call that is received.
30. The method of claim 1, wherein the data processing system includes a controller, the controller configured to route the received call from the first module to the second module.
31. The data processing system of claim 5, further comprising an input/output port operative to receive the call.
Description
BACKGROUND

1. Field of the Disclosure

The present disclosure relates to call routing systems, and more particularly to methods, data processing systems, and data processing system readable media for use in call routing systems.

2. Description of the Related Art

Many businesses use call service centers as a way to conduct business with their customers. Operating a call services center can be expensive, particularly if an attendant needs to interact with every or nearly every caller. Automating call service centers typically includes using a call routing system. Insufficient information may be provided to a call routing system. If insufficient information is provided, the call may be routed to an improper destination, or the call may need to be manually dispositioned by an attendant. The former can be problematic because it can increase the caller's frustration with the call service center and may result in potential lost revenue. The latter can be problematic because the purpose of automating is to reduce having calls, that could otherwise be properly routed, manually dispositioned by an attendant.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 includes a general diagram of a caller at a phone using a call service center including a call routing system.

FIG. 2 includes a flow diagram of a method of using a call routing system.

FIG. 3 includes a flow diagram of a method of authenticating a caller using the call service center of FIG. 1.

FIG. 4 includes a flow diagram of a method of inquiring an account balance associated with the caller using the call service center of FIG. 1.

Skilled artisans will appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale.

DETAILED DESCRIPTION

A call service center can include a call routing system that can use one or more action object identifiers. In one embodiment, an action object identifier can be associated with a task that is desired or otherwise intended to be performed at the call service center. The call routing system may route the call to a module that is not associated with the action object identifier or perform a portion of a task within the same module, wherein the portion of the task is not associated with the action object identifier. The use of the one or more action object identifiers can help a data processing system or a human attendant in more accurately handling the routing of the call. In another embodiment, at least two action object identifiers can be passed with a call from one module to another module. In a particular embodiment, a past action object identifier, a current action object identifier, a future action object identifier, other information related to the call, or any combination thereof may be passed from one module to another module along with the call. By using more than one action object identifier, more complex logic can be used by a data processing system or a human attendant can review the action object identifiers to more accurately route the call, as more variables are available to determine how to route of the call. A log file or other data from a database, storage network, or other memory does not need to be accessed, and thus, the call can be routed quicker and more accurately.

In a first aspect, a method of using a call routing system can include generating an action object identifier at a first module in response at least in part to a call, and routing the call to a second module that does not correspond to the action object identifier. The method can also include routing the call to a third module that is associated with the action object identifier after routing the call to the second module.

In a second aspect, a data processing system can include a first module configured to generate an action object identifier and pass or have passed a call to a second module that does not correspond to the action object identifier. The data processing system can also include a second module configured to perform a first task regarding the call, wherein the first task does not correspond to the action object identifier, and pass or have passed the call to a third module that is associated with the action object identifier. The data processing system can further include a third module configured to perform a second task regarding the call, wherein the second task is associated with the action object identifier.

In a third aspect, a data processing system readable medium can have data to be used with a call routing system, wherein the data is embodied within the data processing system readable medium. The data can include an instruction to generate an action object identifier at a first module in response at least in part to a call, an instruction to route the call to a second module that does not correspond to the action object identifier, and an instruction to route the call to a third module that is associated with the action object identifier after routing the call to the second module.

In a fourth aspect, a data processing system readable medium can have data to be used with a call routing system, wherein the data is embodied within the data processing system readable medium. The data can include an instruction to pass a call, a first action object identifier, and a second action object identifier from a first module to a second module, wherein the first and second modules are within the call routing system.

As used herein, the terms “comprises,” “comprising,” “includes,” “including,” “has,” “having” or any other variation thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, article, or apparatus that comprises a list of elements is not necessarily limited to only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Further, unless expressly stated to the contrary, “or” refers to an inclusive or and not to an exclusive or. For example, a condition A or B is satisfied by any one of the following: A is true (or present) and B is false (or not present), A is false (or not present) and B is true (or present), and both A and B are true (or present).

Additionally, for clarity purposes and to give a general sense of the scope of the embodiments described herein, the use of “a” or “an” are employed to describe one or more articles to which “a” or “an” refers. Therefore, the description should be read to include at least one whenever “a” or “an” is used, and the singular also includes the plural unless it is clear that the contrary is meant otherwise.

Unless stated otherwise, any combination of parts of a system may be bi-directionally or uni-directionally coupled to each other, even though a figure may illustrate only a single-headed arrow or a double-headed arrow. Arrows within the drawing are illustrated, as a matter of convenience, to show a principal information, data, or signal flow within the system or between the system and one or more components outside the system, one or more modules outside the system, another system, or any combination thereof in accordance with an embodiment. Coupling should be construed to include a direct electrical connection in one embodiment and alternatively, may include any one or more of an intervening switch, resistor, capacitor, inductor, router, firewall, network fabric or the like between any combination of one or more components, one or more devices, or one or more modules.

Unless otherwise defined, technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art. In addition, the methods and examples disclosed are illustrative only and not intended to be limiting.

FIG. 1 includes a general diagram of a caller 164 using a call service center 100. The call service center 100 can receive a call from a caller 164 that allows the caller to obtain information, products, or services, potentially without using an attendant. Thus, the call service center 100 can be used by a wide variety of businesses including manufactures, retailers, distributors, telephone service providers, airlines, etc. The call service center 100 can be designed as described herein to help automate routing of calls within the call service center 100 while still allowing an attendant or other human to interact with the caller to reduce caller frustration, reduce the likelihood that the caller, who may intend on purchasing a product or service, leaves without successfully making the purchase, etc. After reading this specification, skilled artisans will appreciate that the architectures and methods described herein can be adapted to the need or desires of the entity using a call service center.

The call service center 100 can include a data processing system 120 that is bi-directionally coupled to an antenna 110 and an attendant terminal 142. In another embodiment, the antenna 110 is not used, particularly if the phone 162 is a wireline phone, rather than a wireless phone as illustrated in FIG. 1. A human attendant 144 can be present at the attendant terminal 142. A caller 164 can use a phone 162 to call the call service center 100 and transact business with the entity operating the call service center 100. The call may include speech of the caller 164 that may be received by the call service center 100. The caller 164 may or may not speak at all during the call. In one embodiment, the phone 162 is communicatively coupled to the data processing system 120, via the antenna 110. The phone 162 can include a wireline phone or a wireless phone. The phone 162 can include a conventional telephone, a cell phone, a voice over Internet protocol phone, or the like. Wires, switches, routers, or potentially other equipment (not illustrated) may be used to communicatively couple the phone 162 to the data processing system 120.

The data processing system 120 can be part of or include a call routing system, as described herein. Each of the antenna 110 and attendant terminal 142 can be coupled to the data processing system 120 through one or more input/output (“I/O”) ports 1202. In another embodiment, separate input ports and output ports could be used. For simplicity, I/O ports 1202 will be used to refer to any or all of input ports, output ports or input/output ports. The data processing system 120 further comprises a controller 1220 that is bi-directionally coupled to modules that are designed to perform actions as requested by a caller using the call service center 100. In the embodiment as illustrated in FIG. 1, the controller 1220 is bi-directionally coupled to module 1231, module 1232, module 1233, and module 1234. Although not illustrated, one or more other modules may be present. Each of the modules 1231 through 1234 can perform one or more actions at the call service center 100. Such actions can include authenticating caller 164, determining account status or other account information of the caller 164, providing information regarding products or services of the entity operation the call service center 100, allowing the caller 164 to purchase products or services at the call service center 100, perform other suitable action, or any combination thereof. Each of the modules 1231 through 1234 may or may not be configured to route the call to the other of the modules 1231 through 1234. In another embodiment, more or fewer modules may be used.

The controller 1220 is also bi-directionally coupled to an attendant interaction module 1240, a disposition module 1260, and a routing module 1280. The attendant interaction module 1240 can allow an attendant input signal from the attendant terminal 142 to be received at the data processing system 120 when the attendant 144 is servicing a call. The attendant interaction module 1240 is bi-directionally coupled to the disposition module 1260 and the routing module 1280. The disposition module 1260 can receive an attendant interaction signal from the attendant interaction module 1240 or a signal from the controller 1220 in order to generate a disposition signal at the disposition module 1260 in order to disposition a call. The disposition module is bi-directionally coupled to the routing module 1280. The routing module 1280 may receive signals from the controller 1220, the attendant interaction module 1240, the disposition module 1260, any one or more of the modules 1231 through 1234, or any combination thereof in order to route the call to an appropriate module when servicing the call.

Although not illustrated, other connections and memories may reside in or be coupled to the data processing system 120. Such memories can include a hard disk, content addressable memory, static random access memory, cache, first-in-first-out (“FIFO”), a database, a storage network, other memories, or any combination thereof. The memories can include media that can be read by the data processing system 120. Therefore, each of the types of memory includes a data processing system readable medium.

Portions of the methods described herein may be implemented in suitable software code or other data for carrying out the methods described. In one embodiment, computer-executable instructions may be lines of assembly code or compiled C++, Java, or other language code. In another embodiment, the code may be contained on a data storage device, such as a hard disk, magnetic tape, floppy diskette, optical storage device, networked storage device(s), or other appropriate data processing system readable medium or storage device.

Functions preformed by any one or more of the modules may be combined with one or more other modules or the controller 1220. For example, the disposition module 1260 and the routing module 1280 may be combined into a single module. In still another embodiment, one or more of the modules may be located outside of the data processing system 120. For example, the attendant interaction module 1240 could reside in the attendant terminal 142. Further, more than one type of module may reside in one or more devices. For example, a disposition module may reside within the phone 162, the attendant terminal 142, or both in addition to or in place of the disposition module 1280 within the data processing system 120. Such disposition modules may be substantially the same or different when compared to each other. Also, any single module may be embedded within a plurality of integrated circuits, chip sets, circuit boards, or the like. Additionally, a software program or its software components with such code may be embodied in more than one data processing system readable medium in more than one computer or other item having a controller or a processor.

Attention is now directed toward a method of using a call routing system for the call service center 100 in accordance with an embodiment, as illustrated in FIG. 2. The method can include receiving a call from the caller 164, at block 222. The method can also include generating an action object identifier at a first module in response at least in part to the call, at block 242. The method can further include routing the call to a second module that does not correspond to the action object identifier, at block 262. The method can still further include the call to a third module that is associated with the action object identifier after routing the call to the second module, at block 282. Some details regarding the operations performed as described in blocks 242, 262, and 282 are described with respect to exemplary, non-limiting embodiments, as illustrated in FIGS. 3 and 4. Occasional references will be made to the call service center 100 or one or more portions thereof, as illustrated in FIG. 1, when describing methods as illustrated in FIGS. 3 and 4.

FIGS. 3 and 4 include process flow diagrams that illustrate potential actions that may occur within an authentication module and an account status module. Referring to FIG. 3, signals can be received from an incoming call coming from the caller 164 at phone 162, at item 302. In one embodiment, the call includes a communication in which a caller's voice can be transmitted from the phone 162 to the data processing system 120. The caller 164 may or may not speak during the call. The call from the phone 162 can be received at I/O port 1202 of the data processing system 120 via the antenna 110. The signal can be transmitted from the I/O port 1202 to the controller 1220. The controller 1220 may transmit the signals to an authentication module that may be module 1231 in FIG. 1. The authentication module can be used authenticate the caller 164. The transmission from the controller 1220 may be directly from the controller 1220 to the module 1231 or may occur via the routing module 1280.

The method can include authenticating the caller, at block 322 in FIG. 3. In one embodiment, one or more conventional techniques may be used for authenticating the caller. Referring to FIG. 1, module 1231 may be used to perform the task of authentication. After authentication, the data processing system 120 may transmit one or more options to the caller 164 at phone 162 regarding one or more other actions from which the caller 164 can select. The actions can include obtaining information, such as account information, order status information, product or service information, ordering a product or service, paying a bill, transferring funds, other suitable information or transaction, or any combination thereof.

The method can also include receiving a user input signal associated with purchasing a service, at block 342. In another embodiment, the user input signal could be associated with purchasing a product or any combination of one or more products or one or more services. Referring to FIG. 1, the caller 164 at phone 162 can activate one or more keys, buttons, or other controls, or any combination thereof of the phone 162 to generate the user input signal that is received by the data processing system 120. In this particular embodiment, the caller 164 has selected to purchase a service.

Module 1231 may generate one or more action object identifiers associated with the call. In one embodiment, past, current, and future action object identifiers are generated. An action object identifier can be associated with a task that has been, is being, or is desired or otherwise intended to be performed. In a particular embodiment, a past action object identifier can be associated with a task that has been performed, a current action object identifier can be associated with a task that is being performed, and a future action object identifier can be associated with a task that is desired or otherwise intended to be performed. The past, current, and future action object identifiers may be identified with respect to a particular module. For example, the same action object identifier may have been a past action object identifier at the particular module and may be a current action object identifier at another module that immediately preceded the particular module. The level of detail regarding the action object identifiers can be varied. For example, each of the past, current, and future action object identifiers may include a reference to a module (e.g., module 1231 to 1234) or to a more particular aspect or a portion of a task that was, is, or is desired or otherwise intended to be performed at the module.

In FIG. 3, exemplary action object identifiers include “Past AO: Receive_Call,” “Current AO: Authenticate_Caller,” “Future AO: Buy_Service,” at block 344. The information within block 344 indicates that, at module 1231, an incoming call was received before reaching module 1231, authentication is the task performed by module 1231, and the caller 164 desires to purchase a service. Other information (not illustrated) may be generated, such as whether the current action object was successfully completed, a reason why the current action object was or was not successful, other suitable information regarding the processing of the call, or any combination thereof. The method can include saving the past action object identifier, current action object identifier, future action object identifier, and potentially other information. Such information may be stored within memory (not illustrated) within the data processing system 120, or a database or other storage (not illustrated) coupled to the data processing system 120.

The method can further include determining whether the caller 164 intends to purchase a product, a service, or any combination thereof, at decision act 362. The data processing system 120 can analyze the future action object identifier to determine that the caller 164 desires to purchase a service (“yes” branch from decision act 362). The call and any one or more of the past action object identifier, current action object identifier, future action object identifier, other information, or any combination thereof may be passed to an account status module. In one embodiment, the account status module is module 1322 in FIG. 1. In a particular embodiment, the module 1321 may route the call and associated information to module 1322 or may have the routing module 1280 route the call and associated information to module 1322. Thus, the module 1321 can pass or can have passed the call and the associated information. If the caller 164 at phone 162 does not desire to purchase any products or services (“no” branch from decision act 362), the caller 164 at phone 162 may be routed to another module or allow other action to be taken by the data processing system 120 with or without further input from the phone 162. The determination whether the caller 164 intends to purchase a product, a service, or any combination thereof, at decision act 362, may be performed by the module 1321 or the routing module 1280.

The process at the account status module is illustrated in the process flow diagram in FIG. 4. The call and associated information can be passed to the account status module. In one embodiment, the account status module can be used by the entity that controls and operates the caller service center 100 to reduce the likelihood that the its customers will be allowed to make any purchases if they already are overdue in paying an outstanding balance, are at or have exceeded a credit limit of the caller's account, other one or more indicia that collecting money from the caller for an additional purchase would be difficult, or any combination thereof.

The call and associated information can be passed to the account status module from the authentication module, at item 402 in FIG. 4. The method can include retrieving account information of the caller's account, at block 422. The information may be obtained from memory (not illustrated) within the data processing system 100, or from a database, a storage network, or other external storage network (not illustrated). The method can further determine if the balance of the caller's account is less than zero, at decision act 424.

If the balance is not less than zero (“no” branch from decision act 424), the account status module can generate the past action object identifier, current action object identifier, future action object identifier, other information, or any combination thereof, at block 442. In one embodiment, one or more of the action object identifiers can be changed or otherwise generated by the account status module.

In a particular embodiment, the current action object identifier from the authentication module becomes the past action object identifier within the account status module. Thus, the past action object identifier can include “Past AO: Authenticate_Caller.” The current action object identifier can be associated with the account status module, which is where the call is currently being processed. The current action object identifier can include “Current AO: Check_Account.” Although not illustrated, a result identifier, a reason identifier, or both can be used to indicate that the action was successfully performed and that the account has a zero or positive balance. Note that a positive balance indicator may be used even if the balance is zero. Such information may be passed with the call. Referring to FIG. 4, the positive balance indicates that the determination in decision act 424 has been performed and the call is along the “no” branch from decision act 424.

An optional determination can be made regarding the future action object identifier from the authentication module. If the current module is not associated with the future action object identifier, the future action object identifier from the authentication module may also be the future action object identifier for the account status module. If the current module is associated with the future action object identifier but the call has not yet reached a particular portion of a task associated with the future action object identifier, the future action object identifier from the authentication module may also be the future action object identifier at this point in the process. In one particular embodiment, the caller desires to purchase a service, and therefore, the future action object identifier can be “Future AO: Buy_Service.”

Other information (not illustrated) may be generated, such as whether the current action object was successfully completed, a reason why the current action object was or was not successful, other suitable information regarding the processing of the call, or any combination thereof. The method can include saving the past action object identifier, current action object identifier, future action object identifier, and potentially other information. Such information may be stored within memory (not illustrated) within the data processing system 120, a database, or other storage (not illustrated) coupled to the data processing system 120.

The method can further include routing the call to the “Buy_Service” module, at block 444 in FIG. 4. The call and any one or more of the past action object identifier, current action object identifier, future action object identifier, other information, or any combination thereof may be passed to the “Buy_Service” module. In one embodiment, the “Buy_Service” module is module 1323 in FIG. 1. In a particular embodiment, the module 1322 may route the call and associated information to module 1323 or may have the routing module 1280 route the call and associated information to module 1323. Thus, the module 1322 can pass or can have passed the call and the associated information. The caller 164 at the phone 162 may be able to acquire or otherwise purchase one or more services that the caller 164 desires. At the “Buy_Service” module, the current action object identifier at the account status module becomes the past action object identifier at the “Buy_Service” module.

The future action object identifier at the account status module becomes the current action object identifier at the “Buy_Service” module, or the current action object identifier at the “Buy_Service” module may be different and potentially more specific to the portion of the task being performed at the “Buy Service” module. The future action object identifier can be assigned a zero or null value or may be assigned a different value after a further dialog with the caller 164 at the phone 162. For the example, the caller may desire to acquire a digital subscriber line (“DSL”) service for Internet access, and the future action object identifier can be “Future AO: Buy_DSL.”

The call can continue with the caller 164 at phone 162, the data processing system 120, or a combination thereof providing sufficient information to the caller 164 for him or her to decide whether to acquire the DSL service, provide sufficient information to the service provider to provide the service and properly bill the caller 164 for the service, perform other associated actions, or any combination thereof.

In one embodiment, the future action object identifier can be used to keep track of where the caller 164 at phone 162, the data processing system 120, or any combination thereof desires or otherwise intends to do, even though the call may need to be processed by one or more unassociated, intervening modules, or one or more unassociated, intervening portions of one or more tasks within the same module. By using the future action object identifiers, calls can be more accurately routed while still allowing optional or intervening processing of the call to occur.

Returning to decision act 424 in FIG. 4, a determination may be made that the balance of the caller's account is less than zero (“yes” branch). In one embodiment, the method can include announcing the amount due, and optionally, the due date, at block 462. In a particular embodiment, audio signals can be generated at the data processing system 120 and be transmitted to the phone 162. The phone 162 can receive the audio signals and convert them to audible signals that the caller 164 can hear. The audible signals can also prompt the caller 164 to decide whether he or she wants to make a payment. The caller 164 can activate one or more keys, buttons, or other controls, or any combination thereof of the phone 162 to generate a user input signal that is received by the data processing system 120.

After receiving the user input signal, the method can include determining whether a payment is to be made (decision act 464 in FIG. 4). In one embodiment, the user input signal may be associated with the “yes” branch from decision act 464. The method can further include receiving payment information, at block 482. The method can vary depending on how the payment will be made. A credit, bank, or smart card may be used, a bank checking or savings account may be used, money may be wire transferred, another suitable payment selection may be used, or any combination thereof. The caller 164 at phone 162 may need to take the balance to zero, become positive, reduce the current balance by a predetermining amount (e.g., $50, $100, etc.) or a predetermined fraction (e.g., reduce negative balance by 50%, 80%, etc.). The account status module can generate the past action object identifier, current action object identifier, future action object identifier, other information, or any combination thereof, at block 484. In one embodiment, one or more of the action object identifiers can be changed or otherwise generated by the account status module.

In a particular embodiment, the past action object identifier can include “Past AO: Authenticate.” The “Current AO: Check_Account.” If a payment was made to reduce the balance to zero or become positive, an optional result identifier, reason identifier, or both can indicated that the account status check was successfully performed and that the account has a zero or positive account balance. An optional determination can be made regarding the future action object identifier from the authentication module. If the current module is not associated with the future action object identifier, the future action object identifier from the authentication module may also be the future action object identifier for the account status module. If the current module is associated with the future action object identifier but the call has not yet reached a particular portion of a task associated with the future action object identifier, the future action object identifier from the authentication module may also be the future action object identifier at this point in the process. In one particular embodiment, the caller desires to purchase a service, and therefore, the future action object identifier can be “Future AO: Buy_Service.”

Other information (not illustrated) may be generated, such as whether the current action object was successfully completed, a reason why the current action object was or was not successful, other suitable information regarding the processing of the call, or any combination thereof. The method can include saving the past action object identifier, current action object identifier, future action object identifier, and potentially other information. Such information may be stored within memory (not illustrated) within the data processing system 120, a database or other storage (not illustrated) coupled to the data processing system 120.

The method can further include routing the call to the “Buy_Service” module, at block 486 in FIG. 4. The call and any one or more of the past action object identifier, current action object identifier, future action object identifier, other information, or any combination thereof may be passed to the “Buy_Service” module. The call can be further processed as described herein.

Returning to decision act 464, if the user input signals from phone 162 are associated with not making a payment or not making a sufficient payment, the caller 164 at phone 162 may be having a problem with the call service center 100. The account status module can generate the past action object identifier, current action object identifier, future action object identifier, other information, or any combination thereof, at block 492. In one embodiment, one or more of the action object identifiers can be changed or otherwise generated by the account status module.

In a particular embodiment, the past action object identifier can include “Past AO: Authenticate.” The current action object identifier may include “Current AO: Check_Account” in one particular embodiment. An optional result identifier, reason identifier, or both can indicate that the account status check was or was not successfully performed and that the account has a negative account balance. An optional determination can be made regarding the future action object identifier from the authentication module. If the current module is not associated with the future action object identifier, the future action object identifier from the authentication module may also be the future action object identifier for the account status module. If the current module is associated with the future action object identifier but the call has not yet reached a particular portion of a task associated with the future action object identifier, the future action object identifier from the authentication module may also be the future action object identifier at this point in the process. In one particular embodiment, the future action object identifier can be “Future AO: Buy_Service.”

Other information (not illustrated) may be generated, such as whether the current action object was successfully completed, a reason why the current action object was or was not successful, other suitable information regarding the processing of the call, or any combination thereof. The method can include saving the past action object identifier, current action object identifier, future action object identifier, and potentially other information. Such information may be stored within memory (not illustrated) within the data processing system 120, a database or other storage (not illustrated) coupled to the data processing system 120.

The method can further include routing the call to the attendant interaction module 1240, at block 494 in FIG. 4. The call and any one or more of the past action object identifier, current action object identifier, future action object identifier, future action object identifier, other information, or any combination thereof may be passed to the attendant interaction module 1240. In a particular embodiment, the module 1322 may route the call and associated information to the attendant interaction module 1240 or may have the routing module 1280 route the call and associated information to the attendant interaction module 1240. Thus, the module 1322 can pass or can have passed the call and the associated information.

In still another embodiment, the method may be interrupted at potentially nearly any time because the caller 164 made a wrong selection, the attendant 144 may determine that the caller 164 appears to be lost, the controller 1220 may determine that the call has been in a module too long or is causing an infinite loop to be performed by a module, or for another reason. Therefore, an interrupt signal may be generated by the phone 162, the attendant terminal 142, or the data processing system 120. The interrupt signal can be used to at least temporarily stop processing in order for another action to be taken.

For example, the caller 164 may determine that he or she desires to have an attendant 144 service the call. The phone 162 can generate an interrupt signal that is received by the controller 1220 of the data processing system 120. The controller 1220 can then transmit one or more signals to any one or more modules within the data processing system 120. For example, the controller 1220 can instruct the routing module to route the call, and optionally one or more action object identifiers, a result identifier for a current or other action object, and a reason identifier for the current or other action object to the attendant interaction module 1240. The attendant interaction module 1240 can transmit a notice to the attendant terminal 142 for the attendant 144 to service the call. The attendant terminal 142 can then transmit one or more attendant input signals to the attendant interaction module 1240 that can generate an attendant interaction signal. The attendant interaction signal can be transmitted to the disposition module 1260, which in turn, can generate a disposition signal that can be transmitted to the routing module 1280.

During the process, the call and associated information can be passed from one module to another module. When the past, current, and future action object identifiers, and other associated information are passed with the call, the modules within the data processing system 120, or the attendant 144 at the attendant terminal 142 may quickly analyze status information regarding the call without having to access a log file or otherwise retrieve data from storage. By not having to analyze data within a log file or retrieving information from storage, handling of the call at the call service center 100 may be done more quickly and efficiently.

Whenever a past object identifier, a current object identifier, a future object identifier, any other associated information, or any combination thereof is generated or used to route a call, such information can be stored within a log file. The log file can be used by the attendant, analyzing call data to improve or otherwise change a configuration of the call service center, or for another reason.

In an alternative embodiment, the balance determination 424 may be replaced by or performed in conjunction with a credit limit determination. For example, the determination could include determining whether the caller's account has a zero or negative credit limit (e.g., user was previously allowed to exceed his or her credit limit). If caller's account has a positive credit limit (“no” branch from decision act 424), the method can proceed as described with respect to block 442 and block 444. If the caller's account has a zero or negative credit limit (“yes” branch from decision act 424), the method can proceed as described with respect to decision act 464 and subsequent blocks.

In still another embodiment, the credit limit of the caller's account may be determined after retrieving account information of the caller 164 at block 442. An available amount remaining regarding the credit limit may be determined and the caller 164 may be able to purchase one or more products, one or more services, or any combination thereof to the extent the credit limit is not exceeded. If the caller 164 exceeds the available amount, the data processing system 120 can allow the caller 164 to delete one or more products, one or more services, or a combination thereof until the credit limit for the caller's account is no longer exceeded, require the caller 164 to pay the difference between the value of the purchased items and the available amount, allow the caller 164 to pay for the current items being purchased, or any combination thereof.

The use of one or more action object identifiers, other information, or any combination thereof by a call routing system can allow for more accurate routing of a call within a call service center. The likelihood of inaccurate routing or unnecessary human intervention by an attendant can be significantly reduced. Retrieving a log file or information from a database is not needed in order to use the call routing system as described. Therefore, more accurate automated routing with less human intervention can be achieved with a call routing system.

The call routing system may be used in a variety of call service centers. In one non-limiting embodiment, the call service center 100 can include a speech-enabled, self-service call routing system or call service center for performing one or more transactions or obtaining information from the entity that controls the call service center 100. The methods described herein are highly flexible and can be tailored to the particular needs to desires of the entity.

Note that not all of the activities described above in the general description or the examples are required, that a portion of a specific activity may not be required, and that one or more further activities may be performed in addition to those described. Still further, the order in which activities are listed are not necessarily the order in which they are performed.

Any one or more benefits, one or more other advantages, one or more solutions to one or more problems, or any combination thereof have been described above with regard to one or more particular embodiments. However, the benefit(s), advantage(s), solution(s) to problem(s), or any element(s) that may cause any benefit, advantage, or solution to occur or become more pronounced is not to be construed as a critical, required, or essential feature or element of any or all of the claims.

The above-disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments, which fall within the scope of the present invention. Thus, to the maximum extent allowed by law, the scope of the present invention is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited by the foregoing detailed description.

Citations de brevets
Brevet cité Date de dépôt Date de publication Déposant Titre
US493592720 nov. 198719 juin 1990International Mobile Machines CorporationBase station emulator
US495320417 oct. 198928 août 1990At&T Bell LaboratoriesMultilocation queuing for telephone calls
US49674059 déc. 198830 oct. 1990Transwitch CorporationSystem for cross-connecting high speed digital SONET signals
US498923023 sept. 198829 janv. 1991Motorola, Inc.Cellular cordless telephone
US512704225 févr. 199130 juin 1992Motorola, Inc.Cellular cordless telephone
US514269521 mars 199125 août 1992Novatel Communications, Ltd.Cellular radio-telephone receiver employing improved technique for generating an indication of received signal strength
US515575917 mai 199113 oct. 1992Nec CorporationControl method for cordless telephone which displays identities of responding called parties
US52187165 nov. 19908 juin 1993Motorola, Inc.Method for locating a communication unit within a multi mode communication system
US522970122 mars 199120 juil. 1993Nokia Mobile Phones Ltd.Battery charger for battery-operated equipment
US524756729 avr. 199221 sept. 1993Pioneer Electronic CorporationPortable-to-portable talk system for cordless telephone
US52609886 févr. 19929 nov. 1993Motorola, Inc.Apparatus and method for alternative radiotelephone system selection
US533526912 mars 19922 août 1994Rockwell International CorporationTwo dimensional routing apparatus in an automatic call director-type system
US53533315 mars 19924 oct. 1994Bell Atlantic Network Services, Inc.Personal communications service using wireline/wireless integration
US536755828 févr. 199422 nov. 1994Motorola, Inc.Cellular cordless telephone
US537316126 janv. 199413 déc. 1994Sopha MedicalGamma camera with gain compensation
US544268025 août 199415 août 1995Motorola, Inc.Dual system cellular cordless radiotelephone apparatus with sub-data channel timing monitor
US545590331 mai 19913 oct. 1995Edify Corp.Object oriented customer information exchange system and method
US546949619 avr. 199421 nov. 1995Bell Atlantic Network Services, Inc.Personal communications service using wireline/wireless integration
US549737322 mars 19945 mars 1996Ericsson Messaging Systems Inc.Multi-media interface
US551536617 nov. 19947 mai 1996International Business Machines CorporationMethod and apparatus for direct communication in a TDMA radio communication system
US55220463 juin 199428 mai 1996Ncr CorporationCommunication system uses diagnostic processors and master processor module to identify faults and generate mapping tables to reconfigure communication paths in a multistage interconnect network
US553074420 sept. 199425 juin 1996At&T Corp.Method and system for dynamic customized call routing
US55508952 déc. 199327 août 1996Lucent Technologies Inc.Bimodal portable telephone
US55531173 janv. 19943 sept. 1996Danny R. PetersonVehicular communications system
US555529914 juil. 199510 sept. 1996Teknekron Infoswitch CorporationMethod and system for transferring calls and call-related data between a plurality of call centers
US559018622 déc. 199331 déc. 1996At & TSystem and method for redirecting a telephone call with call merging
US563624323 juin 19953 juin 1997Nec CorporationInterterminal direct communication in digital mobile communication system
US564462026 mai 19951 juil. 1997Nec CorporationMethod of indicating a portable unit of a cordless telephone instrument out of operational area and its device
US565278930 sept. 199429 juil. 1997Wildfire Communications, Inc.Network based knowledgeable assistant
US567330812 oct. 199430 sept. 1997Bell Atlantic Network Services, Inc.Personal phone number system
US574585024 oct. 199428 avr. 1998Lucent Technologies, Inc.Apparatus and method for mobile (e.g. cellular or wireless) telephone call handover and impersonation
US574814731 août 19945 mai 1998Motorola IncPosition locating rescue transceiver
US57546393 nov. 199519 mai 1998Lucent TechnologiesMethod and apparatus for queuing a call to the best split
US575497827 oct. 199519 mai 1998Speech Systems Of Colorado, Inc.Speech recognition system
US58421122 juin 199524 nov. 1998Aspect Telecommunications CorporationPersonal communicator system for identifying a telephone which is disposed proximate a locator transmitter
US592374528 févr. 199713 juil. 1999Teknekron Infoswitch CorporationRouting calls to call centers
US594047628 juin 199617 août 1999Distributed Software Development, Inc.System and method for identifying an unidentified caller
US59463886 févr. 199731 août 1999Walker Asset Management Limited PartnershipMethod and apparatus for priority queuing of telephone calls
US59501335 nov. 19967 sept. 1999Lockheed Martin CorporationAdaptive communication network
US595370415 janv. 199714 sept. 1999Health Risk Management, Inc.Health care management system for comparing user-proposed and recommended resources required for treatment
US599583920 août 199630 nov. 1999Southwestern Bell Technology Resources, Inc.Private radiotelephone system with enhanced telephone system interface
US599996519 août 19977 déc. 1999Netspeak CorporationAutomatic call distribution server for computer telephony communications
US600268922 nov. 199614 déc. 1999Sprint Communications Co. L.P.System and method for interfacing a local communication device
US600276017 févr. 199814 déc. 1999Genesys Telecommunications Laboratories, Inc.Intelligent virtual queue
US60030117 janv. 199814 déc. 1999Xerox CorporationWorkflow management system wherein ad-hoc process instances can be generalized
US60412296 févr. 199721 mars 2000Nokia Mobile Phones, Ltd.Transferring information
US604959424 juil. 199711 avr. 2000At&T CorpAutomatic vocabulary generation for telecommunications network-based voice-dialing
US606958811 févr. 199930 mai 2000Ericsson Inc.Systems and methods for coaxially coupling an antenna to a radiotelephone through a window and amplifying signals adjacent and inside the window
US607303124 déc. 19976 juin 2000Nortel Networks CorporationDesktop docking station for use with a wireless telephone handset
US609194925 juin 199818 juil. 2000Telefonaktiebolaget Lm Ericsson (Publ)Location triggered barring of call forwarding
US61188663 août 199812 sept. 2000Geneys Telecommunications Laboratories, Inc.Emergency call load management for call centers
US611910117 janv. 199712 sept. 2000Personal Agents, Inc.Intelligent agents for electronic commerce
US613093830 juin 199710 oct. 2000Mitel CorporationAutomatic call forwarding
US61732666 mai 19989 janv. 2001Speechworks International, Inc.System and method for developing interactive speech applications
US617328914 mars 19979 janv. 2001Novell, Inc.Apparatus and method for performing actions on object-oriented software objects in a directory services system
US617339912 juin 19979 janv. 2001Vpnet Technologies, Inc.Apparatus for implementing virtual private networks
US61756214 nov. 199716 janv. 2001At&T Corp.Priority call on busy
US618542728 avr. 19986 févr. 2001Snaptrack, Inc.Distributed satellite position system processing and application network
US618888830 mars 199813 févr. 2001Oki Telecom, Inc.Charging unit and wireless telephone having multi-number call forwarding capability
US620195022 sept. 199413 mars 2001Aspect Telecommunications CorporationComputer-controlled paging and telephone communication system and method
US620885414 mai 199827 mars 2001Ameritech CorporationSystem and method for routing a call to a called party's landline or wireless communication unit
US62402972 déc. 199829 mai 2001AlcatelDocking station for mobile telecommunication handset
US625978618 nov. 199910 juil. 2001Genesys Telecommunications Laboratories, Inc.Intelligent virtual queue
US626915329 juil. 199831 juil. 2001Lucent Technologies Inc.Methods and apparatus for automatic call routing including disambiguating routing decisions
US630135030 juin 19959 oct. 2001Qwest Communications International, Inc.System and method for call handling
US63174393 juin 199913 nov. 2001Fujitsu Network Communications, Inc.Architecture for a SONET line unit including optical transceiver, cross-connect and synchronization subsystem
US632053424 août 199920 nov. 2001Lucent Technologies Inc.Location based personal telephone routing system
US6327363 *24 nov. 19984 déc. 2001Mci Worldcom, Inc.Method and system for automated customer services
US63320828 oct. 199918 déc. 2001Aspect Telecommunications CorporationPersonal communicator telephone system
US633398028 sept. 199425 déc. 2001Rockwell International CorporationAutomatic call distributor and method for routing incoming telephone calls based on proficiency ratings of agents
US635360816 juin 19985 mars 2002Mci Communications CorporationHost connect gateway for communications between interactive voice response platforms and customer host computing applications
US63627789 mars 200126 mars 2002Timothy J NeherPersonal location detection system
US63666587 mai 19982 avr. 2002Mci Communications CorporationTelecommunications architecture for call center services using advanced interactive voice responsive service node
US636666811 mars 19992 avr. 2002Avaya Technology Corp.Method of routing calls in an automatic call distribution network
US637381730 déc. 199916 avr. 2002At&T Corp.Chase me system
US63813293 nov. 199930 avr. 2002TeleraPoint-of-presence call center management system
US638558430 avr. 19997 mai 2002Verizon Services Corp.Providing automated voice responses with variable user prompting
US63894003 mai 199914 mai 2002Sbc Technology Resources, Inc.System and methods for intelligent routing of customer requests using customer and agent models
US640080410 déc. 19984 juin 2002At&T Corp.On-hold activity selection apparatus and method
US64009961 févr. 19994 juin 2002Steven M. HoffbergAdaptive pattern recognition based control system and method
US64051593 juin 199811 juin 2002Sbc Technology Resources, Inc.Method for categorizing, describing and modeling types of system users
US641496615 juin 20002 juil. 2002Oss CorporationBridging device for mapping/demapping ethernet packet data directly onto and from a sonet network
US64184244 mai 19999 juil. 2002Steven M. HoffbergErgonomic man-machine interface incorporating adaptive pattern recognition based control system
US64248405 nov. 199923 juil. 2002Signalsoft Corp.Method and system for dynamic location-based zone assignment for a wireless communication network
US644224729 mars 200027 août 2002Genesys Telecommunications Laboratories, Inc.Method and apparatus for recording and automated playback of personal agent greetings in a communication-center environment
US64805933 déc. 199712 nov. 2002British Telecommunications Public Limited CompanyCommunications system automatically diverting calls when user not present
US648402715 juin 199819 nov. 2002Sbc Technology Resources, Inc.Enhanced wireless handset, including direct handset-to-handset communication mode
US65050551 mai 19987 janv. 2003Starfish Software, Inc.Camel-back digital organizer and communication protocol for a cellular phone device
US65104145 oct. 199921 janv. 2003Cisco Technology, Inc.Speech recognition assisted data entry system and method
US651606012 juin 19984 févr. 2003At&T Corp.Advanced call sequencing service
US651956225 févr. 199911 févr. 2003Speechworks International, Inc.Dynamic semantic control of a speech recognition system
US652987125 oct. 20004 mars 2003International Business Machines CorporationApparatus and method for speaker verification/identification/classification employing non-acoustic and/or acoustic models and databases
US655311211 mars 199822 avr. 2003Fujitsu LimitedCall center system
US65709677 juin 199527 mai 2003Ronald A. Katz Technology Licensing, L.P.Voice-data telephonic interface control system
US657421314 déc. 19993 juin 2003Texas Instruments IncorporatedWireless base station systems for packet communications
US657447013 déc. 19993 juin 2003At&T Corp.Programmable ring-call forwarding in a wireless centrex services system
US658418016 janv. 200124 juin 2003International Business Machines Corp.Automatic voice response system using voice recognition means and method of the same
US65874754 sept. 19981 juil. 2003Lucent Technologies Inc.Method of assigning circuit ID's in an IS-IS compliant network
US658755625 févr. 20001 juil. 2003Teltronics, Inc.Skills based routing method and system for call center
US658768313 déc. 19991 juil. 2003At&T Corp.Unconditional call forwarding in a wireless centrex services system
US659813622 oct. 199722 juil. 2003National Semiconductor CorporationData transfer with highly granular cacheability control between memory and a scratchpad area
US660073417 déc. 199829 juil. 2003Symbol Technologies, Inc.Apparatus for interfacing a wireless local network and a wired voice telecommunications system
US660073631 mars 199929 juil. 2003Lucent Technologies Inc.Method of providing transfer capability on web-based interactive voice response services
US660385425 févr. 20005 août 2003Teltronics, Inc.System and method for evaluating agents in call center
US661168125 sept. 199826 août 2003Daniel A. HendersonMethod and apparatus for an improved call interrupt feature in a cordless telephone answering device
US661420623 mai 20022 sept. 2003Palm, Inc.Universal USB charging accessory
US661478120 nov. 19982 sept. 2003Level 3 Communications, Inc.Voice over data telecommunications network architecture
US661478410 déc. 19992 sept. 2003Telefonaktiebolaget L M Ericsson (Publ)System and method for providing supplementary services (SS) in an integrated telecommunications network
US662542329 sept. 200023 sept. 2003Steven WangControl device for forwarding incoming call from mobile phone to phone set coupled to public telecom network
US663118621 nov. 20007 oct. 2003Sbc Technology Resources, Inc.System and method for implementing and accessing call forwarding services
US665008823 avr. 200218 nov. 2003Palm, Inc.Apparatus and system for charging a portable electronic device
US667836025 août 200013 janv. 2004Ronald A. Katz Technology Licensing, L.P.Telephonic-interface statistical analysis system
US667871829 août 199713 janv. 2004Aspect Communications CorporationMethod and apparatus for establishing connections
US669078815 sept. 200010 févr. 2004Avaya Inc.Integrated work management engine for customer care in a communication system
US669401230 août 199917 févr. 2004Lucent Technologies Inc.System and method to provide control of music on hold to the hold party
US669746030 avr. 200224 févr. 2004Sbc Technology Resources, Inc.Adaptive voice recognition menu method and system
US670097225 août 19992 mars 2004Verizon Corporate Services Group Inc.System and method for processing and collecting data from a call directed to a call center
US670440411 juil. 20009 mars 2004Netcall PlcCallback telecommunication system and method
US670458014 mars 20009 mars 2004Intel CorporationCellular telephone docking system
US67077893 nov. 199916 mars 2004At&T Corp.Flexible SONET ring with integrated cross-connect system
US671463131 oct. 200230 mars 2004Sbc Properties, L.P.Method and system for an automated departure strategy
US672141613 juin 200013 avr. 2004International Business Machines CorporationCall centre agent automated assistance
US672188230 août 199913 avr. 2004Lucent Technologies Inc.Method and apparatus for warm starting a system where the system includes region(s) of software code incapable of warm starting
US673172213 juin 20024 mai 2004Callfx.ComAutomated transaction processing system
US67354324 nov. 199811 mai 2004At&T Wireless Services, Inc.Cordless cellular system and method
US673847319 oct. 200118 mai 2004At&T Corp.Call queuing
US674486130 juin 20001 juin 2004Verizon Services Corp.Voice dialing methods and apparatus implemented using AIN techniques
US67448778 mars 19991 juin 2004Avaya Technology Corp.Method and system for enterprise service balancing
US67513065 avr. 200115 juin 2004International Business Machines CorporationLocal on-hold information service with user-controlled personalized menu
US67573067 sept. 199929 juin 2004Nortel Networks LimitedMethod and system for intermediate system level 2 transparency using the SONET LDCC
US676617513 déc. 200020 juil. 2004Waxess Technologies, Inc.Cordless and wireless telephone docking station
US676632024 août 200020 juil. 2004Microsoft CorporationSearch engine with natural language-based robust parsing for user query and relevance feedback learning
US677535928 déc. 199910 août 2004Comverse Ltd.Voice reply to incoming e-mail messages, via e-mail
US677864321 mars 200017 août 2004Sbc Technology Resources, Inc.Interface and method of designing an interface
US679209611 avr. 200214 sept. 2004Sbc Technology Resources, Inc.Directory assistance dialog with configuration switches to switch from automated speech recognition to operator-assisted dialog
US68072745 juil. 200219 oct. 2004Sbc Technology Resources, Inc.Call routing from manual to automated dialog of interactive voice response system
US682330716 déc. 199923 nov. 2004Koninklijke Philips Electronics N.V.Language model based on the speech recognition history
US683193214 juil. 200014 déc. 2004Level 3 Communications, Inc.Transfer of SONET traffic over a packet-switched network
US68322241 avr. 200214 déc. 2004Tacit Software, Inc.Method and apparatus for assigning a confidence level to a term within a user knowledge profile
US684250413 août 200211 janv. 2005Sbc Properties, L.P.System and method for the automated analysis of performance data
US684771113 févr. 200325 janv. 2005Sbc Properties, L.P.Method for evaluating customer call center system designs
US685372229 avr. 20028 févr. 2005Sbc Technology Resources, Inc.System and method for automating customer slamming and cramming complaints
US685396630 avr. 20028 févr. 2005Sbc Technology Resources, Inc.Method for categorizing, describing and modeling types of system users
US685680620 déc. 200115 févr. 2005At&T Corp.Method for call forwarding a call from a mobile telephone
US685952925 févr. 200222 févr. 2005Austin Logistics IncorporatedMethod and system for self-service scheduling of inbound inquiries
US687121214 mai 200122 mars 2005Aspect Communication CorporationMethod and apparatus for processing a telephone call
US687968328 juin 200112 avr. 2005Bellsouth Intellectual Property Corp.System and method for providing a call back option for callers to a call center
US688573413 sept. 200026 avr. 2005Microstrategy, IncorporatedSystem and method for the creation and automatic deployment of personalized, dynamic and interactive inbound and outbound voice services, with real-time interactive voice database queries
US689193211 déc. 200110 mai 2005Cisco Technology, Inc.System and methodology for voice activated access to multiple data sources and voice repositories in a single session
US689208330 août 200210 mai 2005Vocera Communications Inc.Voice-controlled wireless communications system and method
US68950832 mai 200117 mai 2005Verizon Corporate Services Group Inc.System and method for maximum benefit routing
US690136626 août 199931 mai 2005Matsushita Electric Industrial Co., Ltd.System and method for assessing TV-related information over the internet
US69071198 mars 200114 juin 2005Qwest Communications International, Inc.Automated business directory assistance
US691524617 déc. 20015 juil. 2005International Business Machines CorporationEmploying speech recognition and capturing customer speech to improve customer service
US696398313 janv. 20048 nov. 2005Cylant, Inc.Method of and system for detecting an anomalous operation of a computer system
US69781545 oct. 200020 déc. 2005Telus Communications Inc.System for interfacing a conventional telephone installation to a wireless telephone network
US697816311 mars 200220 déc. 2005Jabra CorporationMulti-purpose dongle for wireless headset
US700660527 janv. 200328 févr. 2006Ochopee Big Cypress LlcAuthenticating a caller before providing the caller with access to one or more secured resources
US703144426 juin 200218 avr. 2006Voicegenie Technologies, Inc.Computer-implemented voice markup system and method
US703538810 oct. 200225 avr. 2006Fujitsu LimitedCaller identifying method, program, and apparatus and recording medium
US70620291 oct. 200313 juin 2006Sbc Properties, L.P.Method and apparatus for communicating information about a called party to a calling party
US710316522 janv. 20045 sept. 2006Sbc Technology Resources, Inc.Profile management system including user interface for accessing and maintaining profile data of user subscribed telephony services
US7110512 *18 juin 200319 sept. 2006Sbc Properties, L.P.Method and apparatus for providing prepaid local telephone services
US200100112113 juin 19982 août 2001Sbc Technology Resources, Inc.A method for categorizing, describing and modeling types of system users
US2001001459925 sept. 199816 août 2001Daniel A. HendersonMethod and apparatus for an improved call interrupt feature in a cordless telephone answering device
US2001001867229 mars 200130 août 2001Redtagoutlet.Com, Inc.Method and apparatus for facilitating the sale of goods over the internet
US200100199555 mars 20016 sept. 2001Henderson Daniel A.Method and apparatus for an improved call interrupt feature in a cordless telephone answering device
US2001002194814 mai 200113 sept. 2001Khouri Joseph F.Method and apparatus for processing a telephone call
US200100322297 déc. 200018 oct. 2001John HullsMethod and system for conducting commercial transactions by computer network
US2001003466216 févr. 200125 oct. 2001Morris Robert A.Method and system for facilitating a sale
US2002004603016 mai 200118 avr. 2002Haritsa Jayant RamaswamyMethod and apparatus for improved call handling and service based on caller's demographic information
US2002004987418 oct. 200125 avr. 2002Kazunobu KimuraData processing device used in serial communication system
US2002005767816 août 200116 mai 2002Jiang Yuen JunMethod and system for wireless voice channel/data channel integration
US200200591648 déc. 199916 mai 2002Yuri ShtivelmanMethod and apparatus for auto-assisting agents in agent-hosted communications sessions
US2002005916913 avr. 200116 mai 2002Quarterman John S.System for quickly collecting operational data for internet destinations
US2002006771428 sept. 20016 juin 2002Crain Louis M.System and method for wide area network and telco infrastructure integration
US2002008738528 déc. 20004 juil. 2002Vincent Perry G.System and method for suggesting interaction strategies to a customer service representative
US2002011119023 janv. 200215 août 2002Harrison Keith AlexanderBase station/data storage
US2002011443216 févr. 200122 août 2002Siemens Information And Communication Networks, Inc.Method and system for enabling queue camp-on for skills-based routing
US2002011548013 févr. 200122 août 2002Huang Chih ChenAdapter set
US200201163365 févr. 200222 août 2002Athanassios DiacakisMethod and device for displaying contact information in a presence and availability management system
US2002011980028 févr. 200129 août 2002Jaggers Christopher M.Docking station for wireless communication device
US2002013339430 avr. 200219 sept. 2002Sbc Technology Resources, Inc.Method for categorizing, describing and modeling types of system users
US200201334137 mars 200119 sept. 2002Chang Matthew S.System and method for purchasing an item displayed on a display device
US200201356185 févr. 200126 sept. 2002International Business Machines CorporationSystem and method for multi-modal focus detection, referential ambiguity resolution and mood classification using multi-modal input
US2002013747223 janv. 200126 sept. 2002Quinn Liam B.Wireless antenna switching system
US2002015669919 avr. 200224 oct. 2002Joseph GraySystem of upselling in a computer network environment
US2002016573221 mars 20027 nov. 2002Matchmd, LlcSystem and method for automated and interactive scheduling
US2002018144229 mai 20015 déc. 2002Purshotam RajaniMultimode personal communication system and method
US2002019627713 août 200226 déc. 2002Sbc Properties, L.P.Method and system for automating the creation of customer-centric interfaces
US2003000390029 juin 20012 janv. 2003Goss Stephen C.Proximity-based call forwarding
US2003001865913 mars 200223 janv. 2003Lingomotors, Inc.Category-based selections in an information access environment
US2003002640931 juil. 20016 févr. 2003Sbc Technology Resources, Inc.Telephone call processing in an interactive voice response call management system
US2003003538116 août 200120 févr. 2003Yihsiu ChenNetwork-based teleconferencing capabilities utilizing data network call set-up requests
US200300355169 août 200220 févr. 2003David GuedaliaBroadcastin and conferencing in a distributed environment
US200300392422 juil. 200227 févr. 2003General Instrument CorporationMethods, apparatus,and systems for accessing mobile and voice over IP telephone networks with a mobile handset
US2003004819531 août 200113 mars 2003Dirk TrossenApparatus and method to sense and subscribe to presence information
US2003006993712 nov. 200210 avr. 2003Khouri Joseph F.Method and apparatus for establishing connections
US2003009245115 nov. 200115 mai 2003Ibm CorporationMethod of mobile phone consolidation
US2003009565116 nov. 200122 mai 2003Sbc Technology Resources, Inc.System and method for routing terminating calls to voice mail
US2003009742826 oct. 200122 mai 2003Kambiz AfkhamiInternet server appliance platform with flexible integrated suite of server resources and content delivery capabilities supporting continuous data flow demands and bursty demands
US200301036193 déc. 20015 juin 2003Ibm CorporationEnabling caller controlled hold queue position adjustment
US20030108183 *4 nov. 200212 juin 2003First Usa Bank, NaSystem and methods for call decisioning in a virtual call center integrating telephony with computers
US2003011410518 déc. 200119 juin 2003Amit HallerMethod, system and computer readable medium for making a business decision in response to information from a short distance wireless network
US2003012507531 déc. 20013 juil. 2003Flemming KlovborgDesktop stand and mobile phone
US200301308649 janv. 200210 juil. 2003Ho Edwin Kong-SunFacilitation of mobile direct response by service callback
US2003013342117 janv. 200217 juil. 2003Rangamani SundarMethod, system and apparatus for providing WWAN services to a mobile station serviced by a WLAN
US2003014398130 janv. 200231 juil. 2003Sbc Technology Resources, Inc.Sequential presentation of long instructions in an interactive voice response system
US2003014484631 janv. 200231 juil. 2003Denenberg Lawrence A.Method and system for modifying the behavior of an application based upon the application's grammar
US2003014491913 févr. 200131 juil. 2003Christophe TrompetteProduct sale process management system
US2003015613329 août 200221 août 2003Sbc Properties, L.P.Interface and method of designing an interface
US2003016522314 févr. 20034 sept. 2003Timmins Timothy A.Technique for providing a telecommunication service including information assistance
US2003018120228 févr. 200325 sept. 2003Link Charles M.Automatic telephone service forwarding device
US2003018773229 mars 20022 oct. 2003Seta Joseph D.Method and system for presenting a sales incentive
US200301877732 avr. 20022 oct. 2003Santos Cipriano A.Virtual marketplace agent technology
US2003019406311 avr. 200216 oct. 2003Sbc Technology Resources, Inc.Directory assistance dialog with configuration switches to switch from automated speech recognition to operator-assisted dialog
US2003019575310 avr. 200216 oct. 2003Homuth Brandon GabrielSystems and methods for providing priority customer service
US2003020264030 avr. 200230 oct. 2003Sbc Technology Resources, Inc.Adaptive voice recognition menu method and system
US2003020264329 avr. 200230 oct. 2003Sbc Technology Resources, Inc.System and method for automating customer slamming and cramming complaints
US2003020264929 mai 200330 oct. 2003Castel, Inc.Call center management systems
US2003020443530 avr. 200230 oct. 2003Sbc Technology Resources, Inc.Direct collection of customer intentions for designing customer service center interface
US2003023528211 févr. 200325 déc. 2003Sichelman Ted M.Automated transportation call-taking system
US2003023528724 juin 200225 déc. 2003Michael MargolisVirtual interaction queuing using internet protocols
US200400050475 juil. 20028 janv. 2004Sbc Technology Resources, Inc.Call routing from manual to automated dialog of interactive voice response system
US200400064732 juil. 20028 janv. 2004Sbc Technology Resources, Inc.Method and system for automated categorization of statements
US2004001877424 juil. 200229 janv. 2004Long Michael D.Power adapter identification
US2004003248427 nov. 200119 févr. 2004Lasse HalttunenMethod of transferring data of screen and voice of mobile phone to a normal analog television receiver with an adapter
US2004003286231 juil. 200319 févr. 2004Nuasis CorporationHigh availability VoIP subsystem
US2004003293513 août 200219 févr. 2004Sbc Properties, L.P.System and method for the automated analysis of performance data
US2004004259229 août 20024 mars 2004Sbc Properties, L.P.Method, system and apparatus for providing an adaptive persona in speech-based interactive voice response systems
US200400449504 sept. 20024 mars 2004Sbc Properties, L.P.Method and system for automating the analysis of word frequencies
US20040047453 *28 sept. 200111 mars 2004Fraser Norman MacaskillVariable automated response system
US2004006640110 sept. 20038 avr. 2004Sbc Knowledge Ventures, L.P.System and method for selection of a voice user interface dialogue
US200400664163 oct. 20028 avr. 2004Sbc Properties, L.P.Dynamic and adaptable system and method for selecting a user interface dialogue model
US2004006677611 oct. 20028 avr. 2004Melco Inc.Connection device providing access point to wide area network
US200400725449 juil. 200315 avr. 2004Alexis Glenroy J.Communication systems and methods
US2004007356927 sept. 200215 avr. 2004Sbc Properties, L.P.System and method for integrating a personal adaptive agent
US2004008347930 déc. 200229 avr. 2004Oleg BondarenkoMethod for organizing multiple versions of XML for use in a contact center environment
US2004008828531 oct. 20026 mai 2004Sbc Properties, L.P.Method and system for an automated disambiguation
US2004010301722 nov. 200227 mai 2004Accenture Global Services, GmbhAdaptive marketing using insight driven customer interaction
US200401095556 déc. 200210 juin 2004Bellsouth Intellectual PropertyMethod and system for improved routing of repair calls to a call center
US200401160732 juil. 200317 juin 2004Sbc, Inc.Enhanced wireless handset, including direct handset-to-handset communication mode
US2004012047319 déc. 200224 juin 2004International Business Machines CorporationUsing a telephony application server for call control with a voice server
US2004012049229 sept. 200324 juin 2004Lew Gavin SueoMethod and system for generating a call processing control record
US2004012593731 déc. 20021 juil. 2004Turcan Diane BrownComputer telephony integration (CTI) complete customer contact center
US2004012593831 déc. 20021 juil. 2004Turcan Diane BrownComputer telephony integration (CTI) complete healthcare contact center
US2004012594031 déc. 20021 juil. 2004Turcan Diane BrownComputer telephony integration (CTI) complete hospitality contact center
US2004012724112 déc. 20031 juil. 2004Vocera Communications, Inc.Voice-controlled wireless communications system and method
US2004015649124 nov. 200312 août 2004Reding Craig L.Methods and systems for multiuser selective notification
US2004016107820 févr. 200419 août 2004Sbc Technology Resources, Inc.Adaptive voice recognition menu method and system
US2004016109412 févr. 200419 août 2004Sbc Properties, L.P.Method and system for an automated departure strategy
US2004016109613 févr. 200319 août 2004Sbc Properties, L.P.Method for evaluating customer call center system designs
US200401749806 mars 20039 sept. 2004Sbc Properties, L.P.System and method for providing customer activities while in queue
US2004020337428 oct. 200214 oct. 2004Nokia CorporationGraphical indication of a proximately located device
US200402040566 déc. 200214 oct. 2004William PhelpsCharger with rotating pocket and detachable pocket insert
US2004021321224 nov. 200328 oct. 2004Reding Craig L.Methods and systems for automatic communication line management based on device location
US2004023043813 mai 200318 nov. 2004Sbc Properties, L.P.System and method for automated customer feedback
US200402406352 juil. 20042 déc. 2004Sbc Technology Resources, Inc.Interface and method of designing an interface
US2004024356822 mars 20042 déc. 2004Hai-Feng WangSearch engine with natural language-based robust parsing of user query and relevance feedback learning
US2004026642524 juin 200330 déc. 2004Sbc, Inc.Wireless wide area network charger and cradle
US2005000814111 juil. 200313 janv. 2005Kortum Philip T.Telephone call center with method for providing customer with wait time updates
US2005001519725 avr. 200320 janv. 2005Shinya OhtsujiCommunication type navigation system and navigation method
US2005001574418 août 200420 janv. 2005Sbc Technology Resources Inc.Method for categorizing, describing and modeling types of system users
US2005001882525 juil. 200327 janv. 2005Jeremy HoApparatus and method to identify potential work-at-home callers
US200500202362 juil. 200327 janv. 2005Sbc, Inc.Enhanced wireless handset, including direct handset-to-handset communication mode
US2005002753527 août 20043 févr. 2005Sbc Technology Resources, Inc.Directory assistance dialog with configuration switches to switch from automated speech recognition to operator-assisted dialog
US200500324752 juil. 200310 févr. 2005Sbc, Inc.Enhanced wireless handset, including direct handset-to-handset communication mode
US2005004179623 sept. 200424 févr. 2005Sbc Technology Resources, Inc.Call routing from manual to automated dialog of interactive voice response system
US2005004757812 oct. 20043 mars 2005Sbc Properties, L.P.Method for evaluating customer call center system designs
US200500543354 sept. 200310 mars 2005Sbc Knowledge Ventures, L.P.Call forwarding control device and method of call management
US200500552164 sept. 200310 mars 2005Sbc Knowledge Ventures, L.P.System and method for the automated collection of data for grammar creation
US2005005826425 oct. 200417 mars 2005Sbc Technology Resources, Inc.System and method for processing complaints
US2005006336023 sept. 200324 mars 2005Sbc Knowledge Ventures, L.P.System and method for facilitating packetized calls between managed networks
US2005006352823 sept. 200324 mars 2005Sbc Knowledge Ventures, L.P.Location based call routing for call answering services
US2005006485323 sept. 200324 mars 2005Sbc Knowledge Ventures, L.P.Unified telephone handset for personal communications based on wireline and wireless network convergence
US2005006485523 sept. 200324 mars 2005Sbc Knowledge Ventures, L.P.Method and system for forwarding wireless communications
US200500758943 oct. 20037 avr. 2005Sbc Knowledge Ventures, L.P.System, method & software for a user responsive call center customer service delivery solution
US200500788057 déc. 200414 avr. 2005Sbc Properties, L.P.System and method for the automated analysis of performance data
US2005008063010 oct. 200314 avr. 2005Sbc Knowledge Ventures, L.P.System and method for analyzing automatic speech recognition performance data
US200500806678 oct. 200314 avr. 2005Sbc Knowledge Ventures, L.P.System and method for automated customized content delivery for web sites
US200500960245 nov. 20035 mai 2005Sbc Knowledge Ventures, L.P.System and method of transitioning between cellular and voice over internet protocol communication
US2005011307724 nov. 200326 mai 2005Bushnell William J.System for providing interoperability of call pickup service in a proprietary enterprise communication network and a cellular communication network
US2005013189210 déc. 200316 juin 2005Sbc Knowledge Ventures, L.P.Natural language web site interface
US2005013226215 déc. 200316 juin 2005Sbc Knowledge Ventures, L.P.System, method and software for a speech-enabled call routing application using an action-object matrix
US2005013559518 déc. 200323 juin 2005Sbc Knowledge Ventures, L.P.Intelligently routing customer communications
US2005014147912 oct. 200430 juin 2005Timucin OzugurPresence-based routing in a communications network environment
US2005014169230 sept. 200430 juin 2005Mark SchererComputer-telephony integration (CTI) system for controlling an automatic call distribution system using a bidirectional CTI model
US200501472185 janv. 20047 juil. 2005Sbc Knowledge Ventures, L.P.System and method for providing access to an interactive service offering
US2005016944130 janv. 20044 août 2005Sherif YacoubSystem and method for extracting demographic information
US2005016945329 janv. 20044 août 2005Sbc Knowledge Ventures, L.P.Method, software and system for developing interactive call center agent personas
US20050172148 *4 févr. 20044 août 2005I/O Controls CorporationWireless point-of-sale transaction system and method
US2005020154710 mars 200415 sept. 2005Burg Frederick M.Call queuing
US2005021010117 mai 200522 sept. 2005Universal Electronics Inc.System and method for providing content, management, and interactivity for client devices
US2005024041122 avr. 200427 oct. 2005Sherif YacoubSystem and method for quality of service management within a call handling system
US2005027378130 oct. 20038 déc. 2005Tomonori NakamuraService software acquiring method, system and electronic communication device used therefor
US2005027743114 juin 200415 déc. 2005Sbc Knowledge Ventures, LpSystem and method for managing wireless data communications
US2005028258226 août 200522 déc. 2005Benjamin SlotznickTelephone device with enhanced audio-visual features for interacting with nearby displays and display screens
US200600038062 juil. 20045 janv. 2006Sbc Knowledge Ventures, L.P.Phone synchronization device and method of handling personal information
US2006003158724 mai 20049 févr. 2006Toby PatersonMethod of synchronising between three or more devices
US200600508657 sept. 20049 mars 2006Sbc Knowledge Ventures, LpSystem and method for adapting the level of instructional detail provided through a user interface
US200600564066 déc. 200416 mars 2006Cavium NetworksPacket queuing, scheduling and ordering
US200600727375 oct. 20046 avr. 2006Jonathan PadenDynamic load balancing between multiple locations with different telephony system
US200601650666 avr. 200627 juil. 2006Aastra Intecom Inc.Customer communication service system
US200601770404 févr. 200510 août 2006Sbc Knowledge Ventures, L.P.Call center system for multiple transaction selections
US200601822521 févr. 200517 août 2006Sbc Knowledge Ventures LpMethod and apparatus for maintaining automated call transfers between service centers
US2006019531228 avr. 200631 août 2006University Of Southern CaliforniaInteger programming decoder for machine translation
US2006021583322 mars 200528 sept. 2006Sbc Knowledge Ventures, L.P.System and method for automating customer relations in a communications environment
US200602916423 juin 200528 déc. 2006Sbc Knowledge Ventures, LpCall routing system and method of using the same
US200700198003 juin 200525 janv. 2007Sbc Knowledge Ventures, LpCall routing system and method of using the same
US2007004155110 août 200522 févr. 2007Sbc Knowledge Ventures, LpSystem and method of managing calls to a customer service call center
US2007004772029 août 20051 mars 2007Sbc Knowledge Ventures, L.P.System and method of managing incoming telephone calls at a call center
US200701162304 nov. 200524 mai 2007Sbc Knowledge Ventures, LpSystem and method of managing calls at a call center
US20080273687 *21 juil. 20086 nov. 2008At&T Intellectual Property I, L.P.System and Method for Providing Customer Activities While in Queue
US20090171799 *4 mars 20092 juil. 2009I/O Controls CorporationWireless point-of-sale transaction system and method
EP0424015A210 oct. 199024 avr. 1991AT&T Corp.Multilocation queuing for telephone calls
EP0424015A310 oct. 199027 janv. 1993American Telephone And Telegraph CompanyMultilocation queuing for telephone calls
EP0424015B110 oct. 199020 mars 1996AT&T Corp.Multilocation queuing for telephone calls
EP0876652A417 janv. 19979 juin 1999Personal Agents IncIntelligent agents for electronic commerce
GB2305078B Titre non disponible
WO2001037539A216 nov. 200025 mai 2001Fairmarket, Inc.Network-based sales system
WO2001037539A316 nov. 200010 mai 2002Fairmarket IncNetwork-based sales system
WO2004049222A221 nov. 200310 juin 2004Accenture Global Services GmbhMulti-dimensional segmentation for use in a customer interaction
Citations hors brevets
Référence
1Bluetooth Consortium, "Specification of the Bluetooth System: Profiles"; Dec. 1, 1999.
2Charney, Ben; "VoIP Maker Plans Cell Hybrid"; http://zdnet.com, News Software; Oct. 3, 2003. pp. 1-3.
3Haartsen, J., "Bluetooth: A New Radio Interface Providing Ubiquitous Connectivity", IEEE, Dec. 2000, pp. 107-111.
4International Search Report and Written Opinion of the International Searching Authority for PCT/US04/16017; Aug. 16, 2005; 7 pages.
5International Search Report and Written Opinion of the International Searching Authority for PCT/US04/28260; Sep. 30, 2005; 10 pages.
6International Search Report and Written Opinion of the International Searching Authority for PCT/US04/34239; Feb. 17, 2005; 10 pages.
7International Search Report and Written Opinion of the International Searching Authority for PCT/US05/16449; Apr. 10, 2006; 11 pages.
8International Search Report and Written Opinion of the International Searching Authority for PCT/US2005/016449; Jun. 15, 2006; 3 pages.
9International Search Report for International Application No. PCT/US06/28349, mailed on Aug. 13, 2007.
10Ogino, Tsukasa, et al. "Technologies for Internet Infrastructure: Eliminating the World Wide Wait," iNet Japan, Jul. 18-21, 2000, www.isoc.org/inet2000/cdproceedings/1g/index.
11Schneiderman, R., "Bluetooth's Slow Down", IEEE, Dec. 1999, pp. 61-65.
12U.S. Appl. No. 10/898,722, filed Jul. 23, 2004.
13U.S. Appl. No. 10/901,925, filed Jul. 28, 2004.
14U.S. Appl. No. 10/901,926, filed Jul. 28, 2004.
15U.S. Appl. No. 10/917,233, filed Aug. 12, 2004.
16U.S. Appl. No. 10/920,719, filed Dec. 13, 2004.
17U.S. Appl. No. 10/920,720, filed Aug. 18, 2004.
18U.S. Appl. No. 10/935,726, filed Sep. 7, 2004.
19U.S. Appl. No. 10/948,089, filed Sep. 23, 2004.
20U.S. Appl. No. 10/975,023, filed Oct. 27, 2004.
21U.S. Appl. No. 10/979,784, filed Nov. 2, 2004.
22U.S. Appl. No. 10/996,127, filed Nov. 23, 2004.
23U.S. Appl. No. 10/999,199, filed Nov. 29, 2004.
24U.S. Appl. No. 11/005,494, filed Dec. 6, 2004.
25U.S. Appl. No. 11/005,498, filed Dec. 6, 2004.
26U.S. Appl. No. 11/010,633, filed Dec. 13, 2004.
27U.S. Appl. No. 11/032,495, filed Jan. 10, 2005.
28U.S. Appl. No. 11/036,201, filed Jan. 14, 2005.
29U.S. Appl. No. 11/036,204, filed Jan. 14, 2005.
30U.S. Appl. No. 11/062,100, filed Feb. 18, 2005.
31U.S. Appl. No. 11/071,068, filed Mar. 3, 2005.
32U.S. Appl. No. 11/086,794, filed Mar. 22, 2005.
33U.S. Appl. No. 11/086,796, filed Mar. 23, 2005.
34U.S. Appl. No. 11/129,051, filed May 13, 2005.
35U.S. Appl. No. 11/173,227, filed Jul. 1, 2005.
36U.S. Appl. No. 11/176,972, filed Jul. 7, 2005.
37U.S. Appl. No. 11/212,939, filed Aug. 25, 2005.
38Written Opinion of the International Searching Authority for PCT/US06/28349, mailed on Aug. 13, 2007.
39www.yahoo.com (as in Dec. 12, 1998) as archived in the Internet archive (www.archive.org).
Référencé par
Brevet citant Date de dépôt Date de publication Déposant Titre
US830621322 nov. 20116 nov. 2012Google Inc.Skill and level assignment via concentric inlaid circles
US840185115 juil. 200919 mars 2013At&T Intellectual Property I, L.P.System and method for targeted tuning of a speech recognition system
US873116515 avr. 201320 mai 2014At&T Intellectual Property I, L.P.System and method of automated order status retrieval
US87512326 févr. 201310 juin 2014At&T Intellectual Property I, L.P.System and method for targeted tuning of a speech recognition system
US88246593 juil. 20132 sept. 2014At&T Intellectual Property I, L.P.System and method for speech-enabled call routing
US887971414 sept. 20124 nov. 2014At&T Intellectual Property I, L.P.System and method of determining call treatment of repeat calls
US90886521 juil. 201421 juil. 2015At&T Intellectual Property I, L.P.System and method for speech-enabled call routing
US908865712 mars 201421 juil. 2015At&T Intellectual Property I, L.P.System and method of automated order status retrieval
US91129724 oct. 201218 août 2015Interactions LlcSystem and method for processing speech
US935086210 juil. 201524 mai 2016Interactions LlcSystem and method for processing speech
US936811125 avr. 201414 juin 2016Interactions LlcSystem and method for targeted tuning of a speech recognition system
US972971912 juin 20158 août 2017At&T Intellectual Property I, L.P.System and method of automated order status retrieval
Classifications
Classification aux États-Unis379/211.01, 379/266.01, 379/211.02, 379/212.01, 379/265.01
Classification internationaleH04M3/00, H04M3/42, H04M5/00
Classification coopérativeH04M3/523, H04M15/00, H04M2201/54, H04M15/62
Classification européenneH04M3/523, H04M15/00, H04M15/62
Événements juridiques
DateCodeÉvénementDescription
29 août 2005ASAssignment
Owner name: SBC KNOWLEDGE VENTURES, L.P., NEVADA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BUSHEY, ROBERT R.;KORTH, SARAH;REEL/FRAME:016673/0689;SIGNING DATES FROM 20050728 TO 20050801
Owner name: SBC KNOWLEDGE VENTURES, L.P., NEVADA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BUSHEY, ROBERT R.;KORTH, SARAH;SIGNING DATES FROM 20050728 TO 20050801;REEL/FRAME:016673/0689
31 déc. 2014FPAYFee payment
Year of fee payment: 4