US20110211679A1 - Voice Response Processing - Google Patents
Voice Response Processing Download PDFInfo
- Publication number
- US20110211679A1 US20110211679A1 US12/713,806 US71380610A US2011211679A1 US 20110211679 A1 US20110211679 A1 US 20110211679A1 US 71380610 A US71380610 A US 71380610A US 2011211679 A1 US2011211679 A1 US 2011211679A1
- Authority
- US
- United States
- Prior art keywords
- caller
- voice
- text message
- options
- ivr
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/487—Arrangements for providing information services, e.g. recorded voice services or time announcements
- H04M3/493—Interactive information services, e.g. directory enquiries ; Arrangements therefor, e.g. interactive voice response [IVR] systems or voice portals
- H04M3/4936—Speech interaction details
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42382—Text-based messaging services in telephone networks such as PSTN/ISDN, e.g. User-to-User Signalling or Short Message Service for fixed networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/487—Arrangements for providing information services, e.g. recorded voice services or time announcements
- H04M3/493—Interactive information services, e.g. directory enquiries ; Arrangements therefor, e.g. interactive voice response [IVR] systems or voice portals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
- H04M3/5183—Call or contact centers with computer-telephony arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2201/00—Electronic components, circuits, software, systems or apparatus used in telephone systems
- H04M2201/38—Displays
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2203/00—Aspects of automatic or semi-automatic exchanges
- H04M2203/25—Aspects of automatic or semi-automatic exchanges related to user interface aspects of the telephonic communication service
- H04M2203/251—Aspects of automatic or semi-automatic exchanges related to user interface aspects of the telephonic communication service where a voice mode or a visual mode can be used interchangeably
- H04M2203/253—Aspects of automatic or semi-automatic exchanges related to user interface aspects of the telephonic communication service where a voice mode or a visual mode can be used interchangeably where a visual mode is used instead of a voice mode
- H04M2203/254—Aspects of automatic or semi-automatic exchanges related to user interface aspects of the telephonic communication service where a voice mode or a visual mode can be used interchangeably where a visual mode is used instead of a voice mode where the visual mode comprises menus
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2203/00—Aspects of automatic or semi-automatic exchanges
- H04M2203/65—Aspects of automatic or semi-automatic exchanges related to applications where calls are combined with other types of communication
- H04M2203/651—Text message transmission triggered by call
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
Definitions
- the present invention is in the field of telephony communications including data network telephony (DNT) and pertains particularly to methods and a system for dynamic addition of a visual channel during a voice interaction.
- DNT data network telephony
- the IVR unit is typically adapted for customer self service. However, IVR units may be used to screen callers for routing to live agents within the call center or working remotely from the center but connected to the center by a wireless or wired carrier network.
- Every IVR system is enabled by one or more voice applications, one by-product of which is an abundance of users interacting with the system with at least a portion thereof finding the interactive experience confusing requiring frequent repetition of IVR menus.
- Most such systems employ voice applications which execute at the time of interception of caller by the IVR system.
- Voice applications and application servers are typically a part of such apparatus.
- the present inventor realized in an inventive moment that if, at the point of caller intercept, IVR menu options could be simultaneously presented to callers over a text channel in addition to the voice channel, significant efficiency in the overall IVR call processing might result.
- the inventor therefore constructed a unique IVR system for interacting with potential customers in a telephony environment that allowed menu options to be vocalized to customers and presented visually to those same customers through a text messaging interface. A significant reduction of work results, with no impediment to the business process created.
- step (a) interaction by voice with the caller is by an interactive voice response (IVR) system utilizing a voice application.
- IVR interactive voice response
- individual portions of the IVR script providing choices by voice are tagged as associated with text messages providing the same choices, and when such a portion is encountered in the transaction, the associated text message is sent to the caller's device using the text message destination address. Determination may be made by a voice query to the caller, answered by the caller.
- step (a) interaction by voice with the caller is by a live agent at a station to which the call is routed.
- the live agent operates a computerized appliance executing a desktop application, and the desktop application provides standardized text messages of choices the live agent may wish to communicate to the caller, and when the live agent encounters a point in the voice interaction where the agent determines to send a choice to the caller, the agent is enabled to select the associated text message and enter the text message destination address of the caller to send the text message.
- a system for transmitting choices to a caller using a communication device comprising a switch receiving a voice call from the caller, an end point having voice interaction capability to which the call is routed from the switch, software operating at the end point having access to standardized text messages offering options.
- a determination is made as to whether the caller's communication device is enabled to receive text messages, and, upon encountering a point in the transaction with the caller that a choice between two or more options is to be provided to the caller, a compatible text message comprising the options is selected, a text message destination address to the caller's device is associated with the text message, and the text message is transmitted to the caller's device.
- the end point is an interactive voice response (IVR) system utilizing a voice application.
- IVR interactive voice response
- individual portions of the IVR script providing options by voice are tagged as associated with text messages providing the same options, and when such a portion is encountered in the transaction, the associated text message is sent to the caller's device using the text message destination address. Determination of whether the caller's device can accept text messages may be made by a voice query to the caller, answered by the caller.
- the end point is a station where the call is connected to a live agent for voice response.
- the live agent operates a computerized appliance executing a desktop application, and the desktop application provides standardized text messages of choices the live agent may wish to communicate to the caller, and when the live agent encounters a point in the voice interaction where the agent determines to send a choice to the caller, the agent is enabled to select the associated text message and enter the text message destination address of the caller to send the text message.
- FIG. 2 is a process flow chart illustrating steps for dynamically adding and operating a visual channel to a customer service voice application.
- FIG. 4 is an architectural overview of a communications network supporting dynamic multi-channel customer service according to another embodiment of the present invention.
- the inventors provide a unique interactive multi-modal customer service system for a call center that enables dynamic addition of a visual channel for interaction in addition to an established voice channel.
- the system and methods of the present invention are described in enabling detail below using the following examples, which may describe more than one embodiment of the present invention.
- FIG. 1 is an architectural overview of a communications network 100 supporting dynamic multi-channel customer service according to an embodiment of the present invention.
- Communications network 100 includes a public switched telephony network (PSTN) 101 , a connected wireless carrier network (WCN) 102 , and a connected call center (CC) 103 .
- PSTN 101 may be a private telephony network instead of the public switched network without departing from the spirit and scope of the present invention.
- Call center 103 represents any enterprise call center or contracted center that interfaces with customers and processes transactions involving those customers.
- CC 103 has a local area network (LAN) 117 provided therein and adapted for Internet communication using transfer control protocol over Internet protocol (TCP/IP) and like Internet transport and communications protocols.
- LAN local area network
- TCP/IP transfer control protocol over Internet protocol
- CC 103 may have connections to both the Internet and to the public telephone network without departing from the spirit and scope of the present invention.
- CC 103 may process both analog transactions and digital transactions that have arrived via the Internet, for example.
- the Internet and associated connection architecture is not illustrated, but may be presumed present.
- LAN 117 in CC 103 supports a computer telephony integrated (CTI) central telephone switch (CS) 109 .
- CTI computer telephony integrated
- CS 109 is computer integrated using a CTI processor 111 having a direct connection to LAN 117 .
- CS 109 has a direct connection to a local telephone switch (LS) 104 illustrated within PSTN 101 via telephone trunking.
- CTI processor 111 is connected to CS 109 by a CTI link.
- CS 109 may be an automated call distributor (ACD) or a private branch exchange (PBX) or some other type of telephone switching apparatus including a soft switch (switch implemented in software) without departing from the spirit and scope of the present invention.
- CS 109 may optionally be a leased switch off site maintained by a third-party service provider.
- CS 109 includes internal telephone wiring 119 that may connect the switch to internal telephones manned by live agents. Agent stations are not illustrated in this example, but may be presumed present.
- VAS 114 supports a voice application server (VAS) 114 .
- VAS 114 as with all other described computing appliances or machines includes a digital medium provided therein or coupled thereto which contains all of the software and data required to enable function, in this case, as a voice application server.
- VAS 114 is adapted to contain and serve at least one voice application such as a voice extensible markup language (VXML) application (APP) 115 .
- VXML APP 115 is executed and runs on VAS 114 when called by IVR unit 112 .
- a VXML application such as VXML APP 115 is designed to connect with a call waiting at switch 109 , and to determine what has to be done with the call.
- LAN 117 supports a proxy server (PX) 116 .
- PX 116 includes a digital medium provided therein or coupled thereto which contains all of the software and data required to enable function, in this case, as a proxy server.
- PX 116 is adapted to intercept hypertext transfer protocol (HTTP) messages from VAS 114 running VXML APP 115 or a similar instance. The intercepted messages are parsed to determine if there are menu options that may be read by IVR unit 112 during interaction with the customer.
- VAS 114 as with all other described computing appliances or machines includes a digital medium provided therein or coupled thereto which contains all of the software and data required to enable function, in this case, as a voice application server.
- a tagged application 118 is executing on IVR unit 112 and is being navigated by at least one customer.
- a messaging system (MSG) 110 is provided in this example and is directed and controlled by CTI processor 111 .
- MSG system 110 is adapted to generate short message service (SMS) or media message service (MMS) messages in cooperation with a third-party messaging service provider.
- SMS short message service
- MMS media message service
- MSG 110 may also generate other types of text messages such as those used by Tweeter and other popular third-party messaging services.
- Appliance 107 in this embodiment has a wireless connection to a wireless service provider (WSP) 106 within WCN 102 .
- WSP 106 is adapted to provide wireless telephone and Internet services.
- a call placed on appliance 107 may be registered at CS 109 within CC 103 as a new call waiting to be serviced.
- the connection past WSP 106 may include various cell towers and a gateway (GW) 105 adapted to bridge communication over WCN 102 and PSTN 101 . Once on PSTN 101 , the call is connected through LS 104 to CS 109 where the call is waiting to be serviced.
- GW gateway
- Appliance 107 is enabled for SMS/MMS services and may receive and send SMS and MMS messages while the caller is talking over the voice channel of the appliance.
- IVR unit 112 intercepts the call via synthesized voice channel as is fairly common in IVR implementation. Dual tone multi-frequency (DTMF) tone selection may also be utilized by IVR unit 112 in interaction with the call using communications appliance 107 .
- DTMF Dual tone multi-frequency
- IVR unit 112 receives APP 115 via proxy server 116 as tagged application 118 .
- Tagging SW 113 may use Java tags to tag portions of the VXML application that need to be visually displayed to the caller through appliance 107 in an embodiment of the invention.
- a SMS message for example, may be generated by SMS/MMS server 110 , capturing the IVR menu options included in the tag.
- the menu options are rendered as text and sent in the form of an SMS or MMS, or another message type to communications appliance 107 .
- a messaging port is added to the IVR unit 112 .
- messaging server 110 includes a digital medium coupled thereto that contains all of the software and data required to enable function as a messaging server.
- the message may be immediately displayed on appliance 107 so the caller may read the options while at the same time or perhaps just after receiving the message, the options are recited by the IVR unit.
- the system when IVR unit 112 reaches a point where a tag is encountered, the system sends the text message before rendering the options as synthesized speech so that the caller, for example, may see the options before they are enunciated by the system over the voice channel.
- the caller may respond verbally to the displayed list of options by speaking the desired option from the list of options sent in the message.
- IVR unit 112 may hear the spoken option and perform a required action without it being necessary for the system to render the option list in speech to the caller. In this way, call processing time is reduced for the caller.
- V-Tag SW 113 and PX 116 may not be utilized to enhance that caller's experience.
- menu options in VXML are dynamically tagged before service so that text messages may be generated and sent to the caller at the same time or just before the IVR unit renders the options as voice to the caller.
- the caller may still receive visual menu options through text messages sent to a separate communications device like a computer connected to the Internet, for example.
- the system would have to obtain the messaging address to use from the caller at the beginning of IVR interaction if the user desires that options be sent in a visual message.
- callers who do not have messaging capabilities on the device used to make the call into CC 103 are treated using voice only by default.
- IVR unit 112 may still ask callers if the communication appliance used to call in is able to receive text messages before ruling out visual prompting for that caller.
- FIG. 2 is a process flow chart 200 illustrating steps for dynamically adding and operating a visual channel to a customer service voice application.
- a call arrives at a call center from a caller.
- the IVR system determines if the caller has been prequalified for visual prompting over a text message channel. Prequalification may be performed during the caller identification process using automatic number identification service (ANIS). The number of the caller's communications appliance may be checked against a database of customer information including name, contact information, and any prequalification data obtained and stored by the system during a previous interaction with the caller relative to the same communications appliance.
- ANIS automatic number identification service
- the system determines if the caller has opted in. If the caller has not opted in at step 205 , the IVR treats the caller with voice only at step 206 . This may be the default treatment if the appliance used to call into the center has no text messaging capability. The caller may reject the option if the caller simply desires that voice only mode be used for IVR interaction.
- the IVR unit may collect information about the caller and the end device used by the caller to place the call to the call center at step 207 .
- the process moves to step 208 from step 203 or from step 207 depending on the results of the decision steps 202 and 205 .
- the IVR system calls a proxy server running a VXML tagging SW such as V-Tag SW 113 .
- the proxy server intercepts the VXML stream from the voice application server before it gets to the IVR unit for the purpose of dynamically tagging the appropriate menu options of the application.
- the proxy server begins receiving HTTP messages from the VXML server and determines at step 210 if a menu option is received that will be rendered as a sequence of voice options to the caller. If at step 210 the system determines that no menu options have been received, the messages are simply passed on to or forwarded to the voice platform for speech rendering at step 212 . The process then resolves back to step 209 and back to step 210 until the system detects a menu having two or more options at step 210 . A menu having only one option, for example, requiring a simple yes or no response, may be ignored for tagging because there would be no practical reason for visualizing the option.
- step 210 the system determines that an intercepted HTTP message infers a voice application menu containing two or more selectable options, then at step 211 the proxy server running V-tagging SW inserts a visualization tag in front of the menu and forwards it to the IVR unit or voice platform at step 212 .
- Steps 210 , 211 , and 212 may be repeated as long as the caller is still connected to the IVR system for as many menus as the caller must navigate. The process flow ends when the IVR session with the caller terminates due to routing, or call disposal.
- the VXML applications are dynamically tagged so as not to waste time and resource.
- the next menu with two or more options in the VXML application running is tagged only when the caller will navigate it.
- the visual tag embedded in the VXML instructs a messaging server to render the selectable options of the menu to text in a text message and to send the text message to the caller's end device.
- a VXML application has more than one menu with two or more options and the nature of the application is that a caller will, by default, navigate all of the menus, then the application may be pre-tagged and only the caller's text message address or number needs to be inserted when actual text messages are generated containing the selectable options. In most cases, a caller will only navigate menus and select options until some goal has been identified at which time the caller will either be transferred to a destination or will be disposed of by the IVR unit.
- FIG. 3 is a process flow chart 300 illustrating steps for servicing a customer using two or more IVR channels according to an embodiment of the present invention.
- Flow chart 300 presumes that a caller is interacting with the IVR system and the system has reached a point of an embedded V-Tag associated with a menu containing two or more selectable options at step 301 .
- the system may call or notify a session management module at step 302 for the purpose of managing session synchronization between the voice and text channels used to interact with the caller's end device or appliance.
- the session management module associates the two active IVR channels to a single end device and an active position in a running voice application.
- a message server may generate a text message containing all of the menu options.
- the text message may be a SMS or MMS message, or a Tweet, or other type of short message.
- the individual menu options may be associated with radio buttons enabling a caller to select an option generating a text message response to the message server connected to the IVR.
- a session management module may be provided in this case to ensure that the IVR unit is responsive to the caller's selection made in response to the text message in the form of a message reply.
- a text message may be pushed at step 304 to the caller's end device or communications appliance.
- the IVR unit may then render the menu options as voice played to the caller at step 305 . It is important to note herein that the text message may be generated and sent before the voice rendering of the menu options is performed. This may give the caller time to see the entire set of options so that a response may be made with more efficiency.
- the system waits for a response from the caller.
- a response may come back over voice or text channel from the caller.
- the caller may receive and display the text message containing the options, and may select an option in a text message reply without responding at all by voice to the voice rendered options.
- the session management module may ensure that the selection made in a text reply from the caller is implemented by the IVR system.
- the caller may vocalize the desired option while viewing the set of options received in a text message from the system, the vocalization picked up over the voice channel by the IVR before or during voice rendition of the options.
- the IVR recognizes the option vocalized by the caller without a requirement of waiting until any of or all of the menu options are rendered in voice.
- the system determines if the caller responded by a text reply or response at step 308 . If at step 308 the system detected that the caller responded by texting a response including the selection of the desired option, the process may resolve back to step 310 and then to step 311 . If the response means that the IVR session is over for that caller then the process resolves back to step 312 and ends for that caller.
- the process may resolve back to step 301 for another caller. In such a case the caller dropped out of the system before responding to the IVR menu options. If at step 309 the system determines that the session is still open, the process may resolve back to step 306 where the IVR unit waits some additional time for the caller to respond. In one aspect no response to a menu option presented within a specified period of wait time leads to IVR unit terminating the call. It is noted herein that many callers are interacting with the IVR system simultaneously and the voice application, tagging process, and session management process are spawned for each individual caller connected to the switch.
- a caller may select a presented option resulting in transfer of the caller from self service to live help thereby ending the IVR session for that caller.
- FIG. 4 is an architectural overview of a communications network 400 supporting dynamic multi-channel customer service according to another embodiment of the present invention.
- Communications network 400 includes PSTN 101 , WCN 102 and CC 103 described earlier in this specification.
- This example includes many of the elements of the example of FIG. 1 and those elements not significantly changed in this example retain their element numbers and are not reintroduced.
- a caller calls into CC 103 using communication appliance 107 .
- Appliance 107 connects to WSP 106 in WCN 102 , and the call is routed through GW 105 and LS 104 in PSTN 101 to CS 109 within center 103 .
- IVR unit 112 interacts with the caller as previously described.
- the caller will be routed to a live agent operating one of agent workstations 401 ( 1 -n).
- Agent workstations 401 ( 1 -n) each include a personal computer (PC) connected to LAN 117 and a telephone connected to CS 109 via internal telephony wiring 404 .
- PC personal computer
- the call from communication appliance 107 is intercepted at switch 109 by IVR unit 112 , and initially the interaction may be self service. However, at some point the caller opts to be transferred to a live agent, such as one operating agent workstation 401 ( 2 ), for example.
- LAN 117 supports a universal routing server (URS) 403 .
- URS 403 has a digital medium coupled thereto or otherwise made accessible thereto that contains all of the data and SW required to enable function as a routing server.
- the agent may, at some point during the transaction, recite a list of options or choices to the caller that the caller may select from to further process the transaction. An example of this might be the agent reciting the options for rendering payment for the transaction at hand.
- Agent workstation 401 ( 2 ) has an agent desktop application 405 installed thereon and executable therefrom.
- Agent desktop application 405 is a visual interface that enables the agent to work much more efficiently with the caller. For example, information about the caller and reason for the call may be forwarded to agent desktop interface 405 ahead of the actual transaction. While the agent is conversing with the caller (using phone 2 ), the agent may reach a point in the conversation where a standardized set of choices needs to be presented to the caller by the agent. In this case, the caller may be sent a text message 406 manually from the agent desktop application where the text message 406 contains the standard options that the agent intends to recite to the caller over the open voice channel.
- the text message in this case may be pre-configured based on the standardized choices that the customer is presented with in a specific circumstance.
- the agent may manually send text message 406 containing the selectable options from the agent desktop interface.
- the generated message may be sent to the caller by message server 402 or message server 110 connected to IVR unit 112 .
- the text message may be sent at the same time or just before the agent verbalizes the options or choices to the client.
- the client may respond to the received text message containing the selectable options by voice before the agent has time to verbalize all of the options or by selecting an option in a text response.
- the agent may finish the transaction based on the response from the caller.
- the typical live voice options read to a customer may be pre-configured as a text message template ( 406 ) including the boilerplate (options) where only the address of the communication device of the caller needs to be inserted into the message before send.
- Information forwarded to the agent desktop application before the transaction arrives may include the telephone number (SMS address/MMS address) and confirmation of the pending messaging action that only requires addressing for send.
- the system may automatically address the message using ANIS information from the IVR unit where the messaging address is the caller's phone number
- the text channel between the caller device and the agent computer can be used to help illustrate options that otherwise could only be spoken to the caller.
- FIG. 5 is a process flow chart 500 illustrating steps for live interaction with a customer using two or more channels according to an embodiment of the present invention.
- the system receives an incoming call.
- the system identifies the caller, the caller's communication device and the reason for the call. It is presumed in this example that the caller is prequalified to use the visual text channel. It is noted herein that in one embodiment destination number identification service (DNIS) is used to identify a user that has been called by an outbound dialing service connected to the IVR.
- DNIS destination number identification service
- the system determines if the caller requires live help. If the system determines that the caller will not require a live agent to assist, then the IVR system treats the call as a self service call at step 505 with the capability of utilizing a text channel during the call as previously described above. The process may resolve back to step 503 anytime the system detects that the caller needs live assistance. If the system determined at step 503 that the caller needs live help the call is routed to a live agent at step 504 . In this aspect, the call data including the SMS address is forwarded to the agent desktop application of the agent working with the caller before the actual transaction arrives as a ringing event.
- the agent may pick up the call and may greet the caller or customer.
- the agent begins live interaction with the caller in an attempt to service the caller satisfactorily.
- the agent determines if he or she must recite a list of choices or options to the caller. These choices or options should be more or less standardized such that at least all of the same options would be in a preconfigured text message template ready to launch in the agent's desktop application.
- the process may loop back on the same step until the agent has to recite two or more choices or options hat the customer may select from. If the agent has to recite two or more options or choices to the caller as determined at step 509 , the agent pushes a send button or other mechanism associated with the pre-configured text message to send the message including the options or choices for selection to the caller at step 510 .
Abstract
Description
- 1. Field of the Invention
- The present invention is in the field of telephony communications including data network telephony (DNT) and pertains particularly to methods and a system for dynamic addition of a visual channel during a voice interaction.
- 2. Discussion of the State of the Art
- In the art of telephony, there are call centers that specialize in processing telephone calls. A state-of-art call center has access to a central telephone switch and a local area network (LAN) supporting telephony equipment such as telephones, computing appliances, servers, and the like. In most such call centers, an interactive voice response (IVR) unit is accessible to the center for intercepting calls destined for the center.
- The IVR unit is typically adapted for customer self service. However, IVR units may be used to screen callers for routing to live agents within the call center or working remotely from the center but connected to the center by a wireless or wired carrier network.
- In IVR interaction, a voice application is played for the caller and the caller interacts with menu options that the caller hears the voice platform play. Interaction with such enunciated voice menus can be difficult. This is partly due to confusion because of the recitation of many options presented serially to the caller through the voice interface. Often a caller must replay the menu and listen to the available options again and again before selecting one. This creates delay in the system that could lead to delay in call processing and to reduction of call processing efficiency.
- Therefore, what is clearly needed is a system for enabling dynamic addition of a visual channel to a voice transaction in process so that menu options may be presented over the visual channel and may display at the caller's end , enabling quicker, more efficient and error free interaction with the system. Such a system would reduce call processing delays and increase overall call processing efficiency within the call center.
- The problem stated above is that efficiency is desirable for an interactive voice response (IVR) system operating in a telephony environment, but many of the conventional methods for voice interaction with called or calling parties, such as by traditional voice-based interactive voice response units, also create delays. The inventors therefore considered functional components of an IVR system, looking for elements that exhibit interoperability that could potentially be harnessed to provide a more efficient IVR experience, but in a manner that would not create confusion or add delays.
- Every IVR system is enabled by one or more voice applications, one by-product of which is an abundance of users interacting with the system with at least a portion thereof finding the interactive experience confusing requiring frequent repetition of IVR menus. Most such systems employ voice applications which execute at the time of interception of caller by the IVR system. Voice applications and application servers are typically a part of such apparatus.
- The present inventor realized in an inventive moment that if, at the point of caller intercept, IVR menu options could be simultaneously presented to callers over a text channel in addition to the voice channel, significant efficiency in the overall IVR call processing might result. The inventor therefore constructed a unique IVR system for interacting with potential customers in a telephony environment that allowed menu options to be vocalized to customers and presented visually to those same customers through a text messaging interface. A significant reduction of work results, with no impediment to the business process created.
- Accordingly, in one embodiment of the present invention, a method for transmitting choices to a caller is provided, comprising the steps of (a) interacting by voice with a caller using a communication device; (b) encountering a point in the interaction that a choice between two or more options is to be provided to the caller; (c) determining if the caller's communication device is capable of receiving a text message; (d) selecting a compatible text message comprising the options; (e) associating with the text message a text message destination address to the caller's device; and (f) transmitting the text message to the caller's device.
- In one embodiment of the method, in step (a), interaction by voice with the caller is by an interactive voice response (IVR) system utilizing a voice application. In this embodiment individual portions of the IVR script providing choices by voice are tagged as associated with text messages providing the same choices, and when such a portion is encountered in the transaction, the associated text message is sent to the caller's device using the text message destination address. Determination may be made by a voice query to the caller, answered by the caller.
- In another embodiment, in, in step (a), interaction by voice with the caller is by a live agent at a station to which the call is routed. In this embodiment the the live agent operates a computerized appliance executing a desktop application, and the desktop application provides standardized text messages of choices the live agent may wish to communicate to the caller, and when the live agent encounters a point in the voice interaction where the agent determines to send a choice to the caller, the agent is enabled to select the associated text message and enter the text message destination address of the caller to send the text message.
- In another aspect of the invention a system for transmitting choices to a caller using a communication device is provided, comprising a switch receiving a voice call from the caller, an end point having voice interaction capability to which the call is routed from the switch, software operating at the end point having access to standardized text messages offering options. A determination is made as to whether the caller's communication device is enabled to receive text messages, and, upon encountering a point in the transaction with the caller that a choice between two or more options is to be provided to the caller, a compatible text message comprising the options is selected, a text message destination address to the caller's device is associated with the text message, and the text message is transmitted to the caller's device.
- In one embodiment of the system the end point is an interactive voice response (IVR) system utilizing a voice application. IN this embodiment individual portions of the IVR script providing options by voice are tagged as associated with text messages providing the same options, and when such a portion is encountered in the transaction, the associated text message is sent to the caller's device using the text message destination address. Determination of whether the caller's device can accept text messages may be made by a voice query to the caller, answered by the caller.
- In another embodiment of the system the end point is a station where the call is connected to a live agent for voice response. In this embodiment the live agent operates a computerized appliance executing a desktop application, and the desktop application provides standardized text messages of choices the live agent may wish to communicate to the caller, and when the live agent encounters a point in the voice interaction where the agent determines to send a choice to the caller, the agent is enabled to select the associated text message and enter the text message destination address of the caller to send the text message.
-
FIG. 1 is an architectural overview of a communications network supporting dynamic multi-channel customer service according to an embodiment of the present invention. -
FIG. 2 is a process flow chart illustrating steps for dynamically adding and operating a visual channel to a customer service voice application. -
FIG. 3 is a process flow chart illustrating steps for servicing a customer using two or more IVR channels according to an embodiment of the present invention. -
FIG. 4 is an architectural overview of a communications network supporting dynamic multi-channel customer service according to another embodiment of the present invention. -
FIG. 5 is a process flow chart illustrating steps for live interaction with a customer using two or more channels according to an embodiment of the present invention. - The inventors provide a unique interactive multi-modal customer service system for a call center that enables dynamic addition of a visual channel for interaction in addition to an established voice channel. The system and methods of the present invention are described in enabling detail below using the following examples, which may describe more than one embodiment of the present invention.
-
FIG. 1 is an architectural overview of acommunications network 100 supporting dynamic multi-channel customer service according to an embodiment of the present invention.Communications network 100 includes a public switched telephony network (PSTN) 101, a connected wireless carrier network (WCN) 102, and a connected call center (CC) 103. PSTN 101 may be a private telephony network instead of the public switched network without departing from the spirit and scope of the present invention. -
Call center 103 represents any enterprise call center or contracted center that interfaces with customers and processes transactions involving those customers. CC 103 has a local area network (LAN) 117 provided therein and adapted for Internet communication using transfer control protocol over Internet protocol (TCP/IP) and like Internet transport and communications protocols. CC 103 may have connections to both the Internet and to the public telephone network without departing from the spirit and scope of the present invention. In this regard, CC 103 may process both analog transactions and digital transactions that have arrived via the Internet, for example. In this example the Internet and associated connection architecture is not illustrated, but may be presumed present. - LAN 117 in CC 103 supports a computer telephony integrated (CTI) central telephone switch (CS) 109. CS 109 is computer integrated using a
CTI processor 111 having a direct connection toLAN 117. CS 109 has a direct connection to a local telephone switch (LS) 104 illustrated within PSTN 101 via telephone trunking. CTIprocessor 111 is connected to CS 109 by a CTI link. CS 109 may be an automated call distributor (ACD) or a private branch exchange (PBX) or some other type of telephone switching apparatus including a soft switch (switch implemented in software) without departing from the spirit and scope of the present invention. CS 109 may optionally be a leased switch off site maintained by a third-party service provider. In this example, CS 109 includesinternal telephone wiring 119 that may connect the switch to internal telephones manned by live agents. Agent stations are not illustrated in this example, but may be presumed present. -
CS 109 has CTI access to an interactive voice response (IVR)unit 112.IVR unit 112 may be a separate piece of hardware connected to switch 109 or it may be installed on the switch in some cases or integrated with a soft switch in some cases. In thisexample IVR unit 112 is an intelligent peripheral connected to switch 109 via CTI link or by a separate link.IVR unit 112 may be directly connected toLAN 117 or it may be accessible fromLAN 117 throughCTI processor 111.IVR unit 112 intercepts transactions waiting atswitch 109 and qualifies which of those transactions require live services and which can be disposed of through IVR self service. -
LAN 117 supports a voice application server (VAS) 114.VAS 114, as with all other described computing appliances or machines includes a digital medium provided therein or coupled thereto which contains all of the software and data required to enable function, in this case, as a voice application server.VAS 114 is adapted to contain and serve at least one voice application such as a voice extensible markup language (VXML) application (APP) 115.VXML APP 115 is executed and runs onVAS 114 when called byIVR unit 112. There may be many more than one different voice application installed on and executable fromVAS 114 without departing from the spirit and scope of the present invention. A VXML application such asVXML APP 115 is designed to connect with a call waiting atswitch 109, and to determine what has to be done with the call. -
LAN 117 supports a proxy server (PX) 116.PX 116, as with all other described computing appliances or machines, includes a digital medium provided therein or coupled thereto which contains all of the software and data required to enable function, in this case, as a proxy server.PX 116 is adapted to intercept hypertext transfer protocol (HTTP) messages fromVAS 114 runningVXML APP 115 or a similar instance. The intercepted messages are parsed to determine if there are menu options that may be read byIVR unit 112 during interaction with the customer.VAS 114, as with all other described computing appliances or machines includes a digital medium provided therein or coupled thereto which contains all of the software and data required to enable function, in this case, as a voice application server. -
PX 116 with the aid of a visual tagging (V-Tag)SW application 113 provides visual tagging of any specific menu options in the VXML that may subsequently be speech rendered atIVR unit 112. A taggedapplication 118 is executing onIVR unit 112 and is being navigated by at least one customer. A messaging system (MSG) 110 is provided in this example and is directed and controlled byCTI processor 111.MSG system 110 is adapted to generate short message service (SMS) or media message service (MMS) messages in cooperation with a third-party messaging service provider.MSG 110 may also generate other types of text messages such as those used by Tweeter and other popular third-party messaging services. - A
communications appliance 107 is illustrated in this example and is operated by a user not shown. The user is any potential customer ofCC 103. The user may also be referred to herein as the caller.Appliance 107 in this embodiment is a third or fourth generation (3G, 4G) cellular telephone. In anotherembodiment appliance 107 may be a personal digital assistant (PDA), a computer running a telephony application or some other type of network appliance that supports both voice and text channels simultaneously. -
Appliance 107 in this embodiment has a wireless connection to a wireless service provider (WSP) 106 withinWCN 102.WSP 106 is adapted to provide wireless telephone and Internet services. A call placed onappliance 107 may be registered atCS 109 withinCC 103 as a new call waiting to be serviced. The connection pastWSP 106 may include various cell towers and a gateway (GW) 105 adapted to bridge communication overWCN 102 andPSTN 101. Once onPSTN 101, the call is connected throughLS 104 toCS 109 where the call is waiting to be serviced. -
Appliance 107 is enabled for SMS/MMS services and may receive and send SMS and MMS messages while the caller is talking over the voice channel of the appliance.IVR unit 112 intercepts the call via synthesized voice channel as is fairly common in IVR implementation. Dual tone multi-frequency (DTMF) tone selection may also be utilized byIVR unit 112 in interaction with the call usingcommunications appliance 107. -
IVR unit 112 receivesAPP 115 viaproxy server 116 as taggedapplication 118.Tagging SW 113 may use Java tags to tag portions of the VXML application that need to be visually displayed to the caller throughappliance 107 in an embodiment of the invention. WhenIVR unit 112 reaches a tag in taggedapplication 118, a SMS message, for example, may be generated by SMS/MMS server 110, capturing the IVR menu options included in the tag. The menu options are rendered as text and sent in the form of an SMS or MMS, or another message type tocommunications appliance 107. In one embodiment a messaging port is added to theIVR unit 112. In oneembodiment messaging server 110 is provided and includes a digital medium coupled thereto that contains all of the software and data required to enable function as a messaging server. The message may be immediately displayed onappliance 107 so the caller may read the options while at the same time or perhaps just after receiving the message, the options are recited by the IVR unit. - In one embodiment, when
IVR unit 112 reaches a point where a tag is encountered, the system sends the text message before rendering the options as synthesized speech so that the caller, for example, may see the options before they are enunciated by the system over the voice channel. In this case, the caller may respond verbally to the displayed list of options by speaking the desired option from the list of options sent in the message.IVR unit 112 may hear the spoken option and perform a required action without it being necessary for the system to render the option list in speech to the caller. In this way, call processing time is reduced for the caller. - It is noted herein that for any given period of processing, some callers may be known by the system while some callers may be new to the system. A short IVR interaction at the beginning of a call may ask the caller if they would like to use visual prompting over a text channel. If the caller decides not to use visual prompting at the beginning of interaction, then V-
Tag SW 113 andPX 116 may not be utilized to enhance that caller's experience. However, if the caller opts in to the visual prompting solution, menu options in VXML are dynamically tagged before service so that text messages may be generated and sent to the caller at the same time or just before the IVR unit renders the options as voice to the caller. Once callers have opted into visual prompting through text messaging, the system automatically treats the caller with visual prompting each time the caller calls in using the same communications appliance. - In most embodiments of the present invention voice rendering and text messaging are directed by the IVR system to the same communications device used by a caller to call into the center. A session management module (not illustrated) may be provided to ensure that only navigated menu options are tagged and visually displayed to callers over a text channel at the same time or before the voice rendering of the options would commence. In an embodiment where a voice application remains constant and is not subject to constant revision, the voice application may be tagged using V-Tag SW anywhere a menu with two or more options exists in the application ahead of first use of the application. Callers that have not opted in or that do not have a messaging channel will not be treated using visual prompts and the V-tags will be ignored for those callers.
- If the caller calls in with a communications device that does not support text message receipt, such as a fixed analog telephone, then the caller may still receive visual menu options through text messages sent to a separate communications device like a computer connected to the Internet, for example. In this case, the system would have to obtain the messaging address to use from the caller at the beginning of IVR interaction if the user desires that options be sent in a visual message. In some cases callers who do not have messaging capabilities on the device used to make the call into
CC 103 are treated using voice only by default. However,IVR unit 112 may still ask callers if the communication appliance used to call in is able to receive text messages before ruling out visual prompting for that caller. -
FIG. 2 is aprocess flow chart 200 illustrating steps for dynamically adding and operating a visual channel to a customer service voice application. At step 201 a call arrives at a call center from a caller. Atstep 202 the IVR system determines if the caller has been prequalified for visual prompting over a text message channel. Prequalification may be performed during the caller identification process using automatic number identification service (ANIS). The number of the caller's communications appliance may be checked against a database of customer information including name, contact information, and any prequalification data obtained and stored by the system during a previous interaction with the caller relative to the same communications appliance. - If at
step 202 the system determines that the caller is prequalified for accepting visual prompting using a text messaging channel, then atstep 203 the system greets the caller and identifies the end device of the caller. Prequalification means that the system has already configured this user to receive text messages providing visualization of voice rendered menu options from a voice application. In one embodiment the messaging capabilities of the end device are identified by device serial number lookup, the serial number provided in advance by the calling or called party. - If at
step 202 the caller is not prequalified to receive text visualization of IVR menu options, the IVR may prompt the caller if the caller would like to have menu options sent as text messages in conjunction with IVR voice rendering of the same VXML options atstep 204. During this interaction with the IVR, the IVR might also confirm that the end device or appliance used to call into the center has text message capability sufficient to practice the invention using the same appliance for both voice and text interaction. An end device may be one of a cellular telephone, a personal digital assistant, a smart phone, or a computing appliance running a telephony application. - At
step 205, the system determines if the caller has opted in. If the caller has not opted in atstep 205, the IVR treats the caller with voice only atstep 206. This may be the default treatment if the appliance used to call into the center has no text messaging capability. The caller may reject the option if the caller simply desires that voice only mode be used for IVR interaction. - If the caller has opted in at
step 205, then the IVR unit may collect information about the caller and the end device used by the caller to place the call to the call center atstep 207. The process moves to step 208 fromstep 203 or fromstep 207 depending on the results of the decision steps 202 and 205. Atstep 208, the IVR system calls a proxy server running a VXML tagging SW such as V-Tag SW 113. Atstep 209, the proxy server intercepts the VXML stream from the voice application server before it gets to the IVR unit for the purpose of dynamically tagging the appropriate menu options of the application. - The proxy server begins receiving HTTP messages from the VXML server and determines at
step 210 if a menu option is received that will be rendered as a sequence of voice options to the caller. If atstep 210 the system determines that no menu options have been received, the messages are simply passed on to or forwarded to the voice platform for speech rendering atstep 212. The process then resolves back to step 209 and back to step 210 until the system detects a menu having two or more options atstep 210. A menu having only one option, for example, requiring a simple yes or no response, may be ignored for tagging because there would be no practical reason for visualizing the option. - If at
step 210 the system determines that an intercepted HTTP message infers a voice application menu containing two or more selectable options, then atstep 211 the proxy server running V-tagging SW inserts a visualization tag in front of the menu and forwards it to the IVR unit or voice platform atstep 212.Steps - In a preferred embodiment, the VXML applications are dynamically tagged so as not to waste time and resource. The next menu with two or more options in the VXML application running is tagged only when the caller will navigate it. The visual tag embedded in the VXML instructs a messaging server to render the selectable options of the menu to text in a text message and to send the text message to the caller's end device. In one embodiment where a VXML application has more than one menu with two or more options and the nature of the application is that a caller will, by default, navigate all of the menus, then the application may be pre-tagged and only the caller's text message address or number needs to be inserted when actual text messages are generated containing the selectable options. In most cases, a caller will only navigate menus and select options until some goal has been identified at which time the caller will either be transferred to a destination or will be disposed of by the IVR unit.
-
FIG. 3 is aprocess flow chart 300 illustrating steps for servicing a customer using two or more IVR channels according to an embodiment of the present invention.Flow chart 300 presumes that a caller is interacting with the IVR system and the system has reached a point of an embedded V-Tag associated with a menu containing two or more selectable options atstep 301. The system may call or notify a session management module atstep 302 for the purpose of managing session synchronization between the voice and text channels used to interact with the caller's end device or appliance. The session management module associates the two active IVR channels to a single end device and an active position in a running voice application. - At
step 303, a message server may generate a text message containing all of the menu options. The text message may be a SMS or MMS message, or a Tweet, or other type of short message. The individual menu options may be associated with radio buttons enabling a caller to select an option generating a text message response to the message server connected to the IVR. A session management module may be provided in this case to ensure that the IVR unit is responsive to the caller's selection made in response to the text message in the form of a message reply. - Once a text message is generated at
step 303, it may be pushed atstep 304 to the caller's end device or communications appliance. The IVR unit may then render the menu options as voice played to the caller atstep 305. It is important to note herein that the text message may be generated and sent before the voice rendering of the menu options is performed. This may give the caller time to see the entire set of options so that a response may be made with more efficiency. - At
step 306 the system waits for a response from the caller. A response may come back over voice or text channel from the caller. For example, the caller may receive and display the text message containing the options, and may select an option in a text message reply without responding at all by voice to the voice rendered options. In this case, the session management module may ensure that the selection made in a text reply from the caller is implemented by the IVR system. In one aspect, the caller may vocalize the desired option while viewing the set of options received in a text message from the system, the vocalization picked up over the voice channel by the IVR before or during voice rendition of the options. In this case, the IVR recognizes the option vocalized by the caller without a requirement of waiting until any of or all of the menu options are rendered in voice. - At
step 307 the system determines if there was a voice response back from the caller selecting an option from the menu. If atstep 307 the system received and recognized a voice response from the caller, then atstep 310 the system performs an action relative to the selected response. The system may determine if the IVR session is over as a result of the previous response detected atstep 307. If the session is determined to be over atstep 311 then the process ends for that caller atstep 312. - If the system does not receive a voice response to the menu options texted and rendered as synthesized voice to the caller in
steps step 307 ten the system determines if the caller responded by a text reply or response atstep 308. If atstep 308 the system detected that the caller responded by texting a response including the selection of the desired option, the process may resolve back to step 310 and then to step 311. If the response means that the IVR session is over for that caller then the process resolves back to step 312 and ends for that caller. Whether the caller has responded by voice or by text, if the system determines atstep 311 that the session is not over, then the process may resolve back to step 301 when a next tagged menu option is reached by the IVR in interaction with the caller. In one aspect the session management module stays open to monitor the IVR dual channel session as long as the caller is still connected to the IVR unit. - If the system does not receive a voice response at
step 307 or a text response atstep 308, the system may determine if the session with the caller is still open atstep 309. In one aspect a time period may be defined within which the system should receive a response from the caller. If the time period expires before a response is received for the previous prompt, the IVR may repeat the menu for the caller. The caller may also elect to hear the menu over again if repeating the menu is a selectable option. - If the system determines that the session with the caller is terminated the process may resolve back to step 301 for another caller. In such a case the caller dropped out of the system before responding to the IVR menu options. If at
step 309 the system determines that the session is still open, the process may resolve back to step 306 where the IVR unit waits some additional time for the caller to respond. In one aspect no response to a menu option presented within a specified period of wait time leads to IVR unit terminating the call. It is noted herein that many callers are interacting with the IVR system simultaneously and the voice application, tagging process, and session management process are spawned for each individual caller connected to the switch. - In one embodiment of the present invention, a caller may select a presented option resulting in transfer of the caller from self service to live help thereby ending the IVR session for that caller. In such a case, it is still possible to use messaging to present choices to the caller from the perspective of the live agent assigned to help the caller by telephone.
-
FIG. 4 is an architectural overview of acommunications network 400 supporting dynamic multi-channel customer service according to another embodiment of the present invention.Communications network 400 includesPSTN 101,WCN 102 andCC 103 described earlier in this specification. This example includes many of the elements of the example ofFIG. 1 and those elements not significantly changed in this example retain their element numbers and are not reintroduced. - In this example, as in the example of
FIG. 1 , a caller calls intoCC 103 usingcommunication appliance 107.Appliance 107 connects toWSP 106 inWCN 102, and the call is routed throughGW 105 andLS 104 inPSTN 101 toCS 109 withincenter 103.IVR unit 112 interacts with the caller as previously described. In this embodiment the caller will be routed to a live agent operating one of agent workstations 401 (1-n). Agent workstations 401 (1-n) each include a personal computer (PC) connected toLAN 117 and a telephone connected toCS 109 viainternal telephony wiring 404. - In this embodiment the call from
communication appliance 107 is intercepted atswitch 109 byIVR unit 112, and initially the interaction may be self service. However, at some point the caller opts to be transferred to a live agent, such as one operating agent workstation 401 (2), for example.LAN 117 supports a universal routing server (URS) 403.URS 403 has a digital medium coupled thereto or otherwise made accessible thereto that contains all of the data and SW required to enable function as a routing server. In this case the agent may, at some point during the transaction, recite a list of options or choices to the caller that the caller may select from to further process the transaction. An example of this might be the agent reciting the options for rendering payment for the transaction at hand. - Agent workstation 401 (2) has an
agent desktop application 405 installed thereon and executable therefrom.Agent desktop application 405 is a visual interface that enables the agent to work much more efficiently with the caller. For example, information about the caller and reason for the call may be forwarded toagent desktop interface 405 ahead of the actual transaction. While the agent is conversing with the caller (using phone 2), the agent may reach a point in the conversation where a standardized set of choices needs to be presented to the caller by the agent. In this case, the caller may be sent atext message 406 manually from the agent desktop application where thetext message 406 contains the standard options that the agent intends to recite to the caller over the open voice channel. - The text message in this case may be pre-configured based on the standardized choices that the customer is presented with in a specific circumstance. The agent may manually send
text message 406 containing the selectable options from the agent desktop interface. The generated message may be sent to the caller bymessage server 402 ormessage server 110 connected toIVR unit 112. The text message may be sent at the same time or just before the agent verbalizes the options or choices to the client. Much like the IVR embodiment, the client may respond to the received text message containing the selectable options by voice before the agent has time to verbalize all of the options or by selecting an option in a text response. - The agent may finish the transaction based on the response from the caller. The typical live voice options read to a customer may be pre-configured as a text message template (406) including the boilerplate (options) where only the address of the communication device of the caller needs to be inserted into the message before send. Information forwarded to the agent desktop application before the transaction arrives may include the telephone number (SMS address/MMS address) and confirmation of the pending messaging action that only requires addressing for send. The system may automatically address the message using ANIS information from the IVR unit where the messaging address is the caller's phone number The text channel between the caller device and the agent computer can be used to help illustrate options that otherwise could only be spoken to the caller.
-
FIG. 5 is aprocess flow chart 500 illustrating steps for live interaction with a customer using two or more channels according to an embodiment of the present invention. Atstep 501 the system receives an incoming call. Atstep 502 the system identifies the caller, the caller's communication device and the reason for the call. It is presumed in this example that the caller is prequalified to use the visual text channel. It is noted herein that in one embodiment destination number identification service (DNIS) is used to identify a user that has been called by an outbound dialing service connected to the IVR. - At
step 503 the system determines if the caller requires live help. If the system determines that the caller will not require a live agent to assist, then the IVR system treats the call as a self service call atstep 505 with the capability of utilizing a text channel during the call as previously described above. The process may resolve back to step 503 anytime the system detects that the caller needs live assistance. If the system determined atstep 503 that the caller needs live help the call is routed to a live agent atstep 504. In this aspect, the call data including the SMS address is forwarded to the agent desktop application of the agent working with the caller before the actual transaction arrives as a ringing event. - At
step 507 the agent may pick up the call and may greet the caller or customer. Atstep 508 the agent begins live interaction with the caller in an attempt to service the caller satisfactorily. Atstep 509 the agent determines if he or she must recite a list of choices or options to the caller. These choices or options should be more or less standardized such that at least all of the same options would be in a preconfigured text message template ready to launch in the agent's desktop application. - At
step 509 if the agent has not yet recited a list of selectable choices or options, the process may loop back on the same step until the agent has to recite two or more choices or options hat the customer may select from. If the agent has to recite two or more options or choices to the caller as determined atstep 509, the agent pushes a send button or other mechanism associated with the pre-configured text message to send the message including the options or choices for selection to the caller atstep 510. - It will be apparent to one with skill in the art that the multi-modal customer interaction system of the invention may be provided using some or all of the mentioned features and components without departing from the spirit and scope of the present invention. It will also be apparent to the skilled artisan that the embodiments described above are specific examples of a single broader invention which may have greater scope than any of the singular descriptions taught. There may be many alterations made in the descriptions without departing from the spirit and scope of the present invention.
Claims (12)
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/713,806 US20110211679A1 (en) | 2010-02-26 | 2010-02-26 | Voice Response Processing |
PCT/US2011/023705 WO2011106139A1 (en) | 2010-02-26 | 2011-02-04 | Voice response processing |
US14/341,572 US9560199B2 (en) | 2010-02-26 | 2014-07-25 | Voice response processing |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/713,806 US20110211679A1 (en) | 2010-02-26 | 2010-02-26 | Voice Response Processing |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/341,572 Continuation US9560199B2 (en) | 2010-02-26 | 2014-07-25 | Voice response processing |
Publications (1)
Publication Number | Publication Date |
---|---|
US20110211679A1 true US20110211679A1 (en) | 2011-09-01 |
Family
ID=43806921
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/713,806 Abandoned US20110211679A1 (en) | 2010-02-26 | 2010-02-26 | Voice Response Processing |
US14/341,572 Active US9560199B2 (en) | 2010-02-26 | 2014-07-25 | Voice response processing |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/341,572 Active US9560199B2 (en) | 2010-02-26 | 2014-07-25 | Voice response processing |
Country Status (2)
Country | Link |
---|---|
US (2) | US20110211679A1 (en) |
WO (1) | WO2011106139A1 (en) |
Cited By (77)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110313903A1 (en) * | 2010-06-18 | 2011-12-22 | Infosys Technologies Limited | Method and system facilitating an end-to-end solution for one or more service offerings |
US20120201238A1 (en) * | 2011-02-04 | 2012-08-09 | Jeffrey Lawson | Method for processing telephony sessions of a network |
US20130080519A1 (en) * | 2011-09-28 | 2013-03-28 | Royce A. Levien | Multi-modality communication participation |
US20130086193A1 (en) * | 2010-06-14 | 2013-04-04 | Nec Corporation | Information processing system, linkage server, and information processing method |
US20130129073A1 (en) * | 2011-11-22 | 2013-05-23 | Incontact, Inc. | Systems and methods of parallel media communication in contact handling systems |
US8477915B1 (en) * | 2012-10-01 | 2013-07-02 | Google Inc. | System and method for enforcing a recording preference |
US8570873B2 (en) | 2009-03-02 | 2013-10-29 | Twilio, Inc. | Method and system for a multitenancy telephone network |
US8601136B1 (en) | 2012-05-09 | 2013-12-03 | Twilio, Inc. | System and method for managing latency in a distributed telephony network |
US8638781B2 (en) | 2010-01-19 | 2014-01-28 | Twilio, Inc. | Method and system for preserving telephony session state |
US8644457B1 (en) | 2012-10-01 | 2014-02-04 | Google Inc. | System and method for enforcing a recording preference |
US8738051B2 (en) | 2012-07-26 | 2014-05-27 | Twilio, Inc. | Method and system for controlling message routing |
US8737962B2 (en) | 2012-07-24 | 2014-05-27 | Twilio, Inc. | Method and system for preventing illicit use of a telephony platform |
US8755376B2 (en) | 2008-04-02 | 2014-06-17 | Twilio, Inc. | System and method for processing telephony sessions |
US8781103B2 (en) | 2012-12-12 | 2014-07-15 | Genesys Telecommunications Laboratories, Inc. | System and method for call and data matching in a contact center |
US8838707B2 (en) | 2010-06-25 | 2014-09-16 | Twilio, Inc. | System and method for enabling real-time eventing |
US8837465B2 (en) | 2008-04-02 | 2014-09-16 | Twilio, Inc. | System and method for processing telephony sessions |
US20140324424A1 (en) * | 2011-11-23 | 2014-10-30 | Yongjin Kim | Method for providing a supplementary voice recognition service and apparatus applied to same |
US20140348311A1 (en) * | 2013-05-22 | 2014-11-27 | Hon Hai Precision Industry Co., Ltd. | Information broadcasting system and method |
US8938053B2 (en) | 2012-10-15 | 2015-01-20 | Twilio, Inc. | System and method for triggering on platform usage |
US8948356B2 (en) | 2012-10-15 | 2015-02-03 | Twilio, Inc. | System and method for routing communications |
US8964726B2 (en) | 2008-10-01 | 2015-02-24 | Twilio, Inc. | Telephony web event system and method |
CN104428419A (en) * | 2012-07-04 | 2015-03-18 | 艾维贝合作公司 | Methods using patatin |
US9002937B2 (en) | 2011-09-28 | 2015-04-07 | Elwha Llc | Multi-party multi-modality communication |
US9001666B2 (en) | 2013-03-15 | 2015-04-07 | Twilio, Inc. | System and method for improving routing in a distributed communication platform |
US9064259B2 (en) | 2012-12-19 | 2015-06-23 | Genesys Telecomminucations Laboratories, Inc. | Customer care mobile application |
US9137127B2 (en) | 2013-09-17 | 2015-09-15 | Twilio, Inc. | System and method for providing communication platform metadata |
US9160696B2 (en) | 2013-06-19 | 2015-10-13 | Twilio, Inc. | System for transforming media resource into destination device compatible messaging format |
US9210275B2 (en) | 2009-10-07 | 2015-12-08 | Twilio, Inc. | System and method for running a multi-module telephony application |
US9225840B2 (en) | 2013-06-19 | 2015-12-29 | Twilio, Inc. | System and method for providing a communication endpoint information service |
US9226217B2 (en) | 2014-04-17 | 2015-12-29 | Twilio, Inc. | System and method for enabling multi-modal communication |
US9240941B2 (en) | 2012-05-09 | 2016-01-19 | Twilio, Inc. | System and method for managing media in a distributed communication network |
US9246694B1 (en) | 2014-07-07 | 2016-01-26 | Twilio, Inc. | System and method for managing conferencing in a distributed communication network |
US9247062B2 (en) | 2012-06-19 | 2016-01-26 | Twilio, Inc. | System and method for queuing a communication session |
US9253254B2 (en) | 2013-01-14 | 2016-02-02 | Twilio, Inc. | System and method for offering a multi-partner delegated platform |
US9251371B2 (en) | 2014-07-07 | 2016-02-02 | Twilio, Inc. | Method and system for applying data retention policies in a computing platform |
US9282124B2 (en) | 2013-03-14 | 2016-03-08 | Twilio, Inc. | System and method for integrating session initiation protocol communication in a telecommunications platform |
US9325624B2 (en) | 2013-11-12 | 2016-04-26 | Twilio, Inc. | System and method for enabling dynamic multi-modal communication |
US9336500B2 (en) | 2011-09-21 | 2016-05-10 | Twilio, Inc. | System and method for authorizing and connecting application developers and users |
US9338280B2 (en) | 2013-06-19 | 2016-05-10 | Twilio, Inc. | System and method for managing telephony endpoint inventory |
US9338018B2 (en) | 2013-09-17 | 2016-05-10 | Twilio, Inc. | System and method for pricing communication of a telecommunication platform |
US9338064B2 (en) | 2010-06-23 | 2016-05-10 | Twilio, Inc. | System and method for managing a computing cluster |
US9344573B2 (en) | 2014-03-14 | 2016-05-17 | Twilio, Inc. | System and method for a work distribution service |
US9363301B2 (en) | 2014-10-21 | 2016-06-07 | Twilio, Inc. | System and method for providing a micro-services communication platform |
US9398622B2 (en) | 2011-05-23 | 2016-07-19 | Twilio, Inc. | System and method for connecting a communication to a client |
US9413888B2 (en) * | 2011-06-15 | 2016-08-09 | Nickelback OU | Terminal based interactive voice response system with information prioritization |
US9459926B2 (en) | 2010-06-23 | 2016-10-04 | Twilio, Inc. | System and method for managing a computing cluster |
US9459925B2 (en) | 2010-06-23 | 2016-10-04 | Twilio, Inc. | System and method for managing a computing cluster |
US9467563B1 (en) | 2015-04-10 | 2016-10-11 | Angel.Com Incorporated | Visual interactive voice response system |
US9477975B2 (en) | 2015-02-03 | 2016-10-25 | Twilio, Inc. | System and method for a media intelligence platform |
US9477943B2 (en) | 2011-09-28 | 2016-10-25 | Elwha Llc | Multi-modality communication |
US9483328B2 (en) | 2013-07-19 | 2016-11-01 | Twilio, Inc. | System and method for delivering application content |
US9495227B2 (en) | 2012-02-10 | 2016-11-15 | Twilio, Inc. | System and method for managing concurrent events |
US9503550B2 (en) | 2011-09-28 | 2016-11-22 | Elwha Llc | Multi-modality communication modification |
US9516101B2 (en) | 2014-07-07 | 2016-12-06 | Twilio, Inc. | System and method for collecting feedback in a multi-tenant communication platform |
US9516167B2 (en) | 2014-07-24 | 2016-12-06 | Genesys Telecommunications Laboratories, Inc. | Media channel management apparatus for network communications sessions |
US9553799B2 (en) | 2013-11-12 | 2017-01-24 | Twilio, Inc. | System and method for client communication in a distributed telephony network |
US9590849B2 (en) | 2010-06-23 | 2017-03-07 | Twilio, Inc. | System and method for managing a computing cluster |
US9602586B2 (en) | 2012-05-09 | 2017-03-21 | Twilio, Inc. | System and method for managing media in a distributed communication network |
US9641677B2 (en) | 2011-09-21 | 2017-05-02 | Twilio, Inc. | System and method for determining and communicating presence information |
US9648006B2 (en) | 2011-05-23 | 2017-05-09 | Twilio, Inc. | System and method for communicating with a client application |
US9699632B2 (en) | 2011-09-28 | 2017-07-04 | Elwha Llc | Multi-modality communication with interceptive conversion |
US9774687B2 (en) | 2014-07-07 | 2017-09-26 | Twilio, Inc. | System and method for managing media and signaling in a communication platform |
US9788349B2 (en) | 2011-09-28 | 2017-10-10 | Elwha Llc | Multi-modality communication auto-activation |
US9811398B2 (en) | 2013-09-17 | 2017-11-07 | Twilio, Inc. | System and method for tagging and tracking events of an application platform |
US9906927B2 (en) | 2011-09-28 | 2018-02-27 | Elwha Llc | Multi-modality communication initiation |
US9948703B2 (en) | 2015-05-14 | 2018-04-17 | Twilio, Inc. | System and method for signaling through data storage |
US9984374B2 (en) | 2013-02-25 | 2018-05-29 | Genesys Telecommunications Laboratories Inc. | Mobile expert desktop |
US10063713B2 (en) | 2016-05-23 | 2018-08-28 | Twilio Inc. | System and method for programmatic device connectivity |
US10165015B2 (en) | 2011-05-23 | 2018-12-25 | Twilio Inc. | System and method for real-time communication by using a client application communication protocol |
US10320979B2 (en) * | 2017-09-08 | 2019-06-11 | Verizon Patent And Licensing Inc. | Data structure driven interactive voice response (IVR) framework |
US10419891B2 (en) | 2015-05-14 | 2019-09-17 | Twilio, Inc. | System and method for communicating through multiple endpoints |
US10659349B2 (en) | 2016-02-04 | 2020-05-19 | Twilio Inc. | Systems and methods for providing secure network exchanged for a multitenant virtual private cloud |
US10686902B2 (en) | 2016-05-23 | 2020-06-16 | Twilio Inc. | System and method for a multi-channel notification service |
US11039013B1 (en) * | 2020-04-10 | 2021-06-15 | Medallia, Inc. | Real-time contact center speech analytics, with critical call alerts, deployed across multiple security zones |
WO2021178114A1 (en) * | 2020-03-06 | 2021-09-10 | PAG Financial International LLC | Systems and methods for operating an interactive voice response system |
GB2600553A (en) * | 2020-09-30 | 2022-05-04 | Avaya Man Lp | Enhanced digital messaging |
US11637934B2 (en) | 2010-06-23 | 2023-04-25 | Twilio Inc. | System and method for monitoring account usage on a platform |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103475953B (en) * | 2013-09-13 | 2017-11-17 | 华为技术有限公司 | A kind of media control method and equipment based on desktop cloud |
US11310362B2 (en) * | 2014-04-27 | 2022-04-19 | Webtext Holdings Limited | Voice call diversion to alternate communication method |
US11489962B2 (en) * | 2015-01-06 | 2022-11-01 | Cyara Solutions Pty Ltd | System and methods for automated customer response system mapping and duplication |
US10038783B2 (en) | 2016-08-31 | 2018-07-31 | Genesys Telecommunications Laboratories, Inc. | System and method for handling interactions with individuals with physical impairments |
US9900438B1 (en) | 2016-09-29 | 2018-02-20 | Genesys Telecommunications Laboratories, Inc. | Pinning in an interactive media/voice response system |
US10725750B2 (en) * | 2016-12-01 | 2020-07-28 | Red Hat, Inc. | Compiler integrated intelligent deserialization framework |
US11902467B1 (en) * | 2018-11-09 | 2024-02-13 | Intrado Corporation | System and method of directed flow interactive chat |
US10984791B2 (en) | 2018-11-29 | 2021-04-20 | Hughes Network Systems, Llc | Spoken language interface for network management |
US11178099B2 (en) | 2019-04-09 | 2021-11-16 | Avaya Inc. | Interactive system for rerouting a two-way email communication pathway |
US11240377B2 (en) | 2019-04-09 | 2022-02-01 | Avaya Inc. | Interactive system for rerouting a two-way text communication pathway |
Citations (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5802526A (en) * | 1995-11-15 | 1998-09-01 | Microsoft Corporation | System and method for graphically displaying and navigating through an interactive voice response menu |
US20040137956A1 (en) * | 2002-12-02 | 2004-07-15 | Mann Roy Bernard | Rapid outgoing message readout system |
US7136478B1 (en) * | 2004-01-13 | 2006-11-14 | Avaya Technology Corp. | Interactive voice response unit response display |
US20070135101A1 (en) * | 2005-12-08 | 2007-06-14 | Comverse, Ltd. | Enhanced visual IVR capabilities |
US20090154666A1 (en) * | 2007-12-17 | 2009-06-18 | Motorola, Inc. | Devices and methods for automating interactive voice response system interaction |
US7813485B2 (en) * | 2005-05-26 | 2010-10-12 | International Business Machines Corporation | System and method for seamlessly integrating an interactive visual menu with an voice menu provided in an interactive voice response system |
US7912186B2 (en) * | 2004-10-20 | 2011-03-22 | Microsoft Corporation | Selectable state machine user interface system |
US7924985B2 (en) * | 2005-04-21 | 2011-04-12 | The Invention Science Fund I, Llc | Interaction history applied to structured voice interaction system |
US8010092B2 (en) * | 2004-06-23 | 2011-08-30 | Genesys Telecommunications Laboratories, Inc. | System for facilitating parallel data transfer from a wireless caller into a communications center |
US8090083B2 (en) * | 2004-10-20 | 2012-01-03 | Microsoft Corporation | Unified messaging architecture |
US8139725B2 (en) * | 2005-04-22 | 2012-03-20 | The Invention Science Fund I, Llc | Associated information in structured voice interaction systems |
US8265234B2 (en) * | 2007-03-16 | 2012-09-11 | Intellicomm Inc. | Systems and methods for enabling a user to more easily navigate an interactive voice response (IVR) menu |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8582729B2 (en) * | 2006-02-24 | 2013-11-12 | Qualcomm Incorporated | System and method of controlling a graphical user interface at a wireless device |
US9270817B2 (en) * | 2007-11-23 | 2016-02-23 | Foncloud, Inc. | Method for determining the on-hold status in a call |
US8908847B2 (en) * | 2007-11-23 | 2014-12-09 | Foncloud, Inc. | System and method for deep dialing phone systems |
US8340969B2 (en) * | 2009-04-24 | 2012-12-25 | Research In Motion Limited | Method and mobile communication device for generating dual-tone multi-frequency (DTMF) commands on a mobile communication device having a touchscreen |
US8340255B2 (en) * | 2009-07-07 | 2012-12-25 | CallVU, Ltd. | Interactive display response system |
CA2776973A1 (en) * | 2009-10-05 | 2011-04-14 | Callspace, Inc. | Contextualized telephony message management |
EP2548385B1 (en) * | 2010-03-17 | 2017-08-23 | Alcatel Lucent | Voice notification to the destination of a text message that is engaged in a voice call |
US20170006161A9 (en) * | 2013-03-15 | 2017-01-05 | Genesys Telecommunications Laboratories, Inc. | Intelligent automated agent for a contact center |
-
2010
- 2010-02-26 US US12/713,806 patent/US20110211679A1/en not_active Abandoned
-
2011
- 2011-02-04 WO PCT/US2011/023705 patent/WO2011106139A1/en active Application Filing
-
2014
- 2014-07-25 US US14/341,572 patent/US9560199B2/en active Active
Patent Citations (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5802526A (en) * | 1995-11-15 | 1998-09-01 | Microsoft Corporation | System and method for graphically displaying and navigating through an interactive voice response menu |
US20040137956A1 (en) * | 2002-12-02 | 2004-07-15 | Mann Roy Bernard | Rapid outgoing message readout system |
US7136478B1 (en) * | 2004-01-13 | 2006-11-14 | Avaya Technology Corp. | Interactive voice response unit response display |
US8010092B2 (en) * | 2004-06-23 | 2011-08-30 | Genesys Telecommunications Laboratories, Inc. | System for facilitating parallel data transfer from a wireless caller into a communications center |
US7912186B2 (en) * | 2004-10-20 | 2011-03-22 | Microsoft Corporation | Selectable state machine user interface system |
US8090083B2 (en) * | 2004-10-20 | 2012-01-03 | Microsoft Corporation | Unified messaging architecture |
US7924985B2 (en) * | 2005-04-21 | 2011-04-12 | The Invention Science Fund I, Llc | Interaction history applied to structured voice interaction system |
US8139725B2 (en) * | 2005-04-22 | 2012-03-20 | The Invention Science Fund I, Llc | Associated information in structured voice interaction systems |
US7813485B2 (en) * | 2005-05-26 | 2010-10-12 | International Business Machines Corporation | System and method for seamlessly integrating an interactive visual menu with an voice menu provided in an interactive voice response system |
US20070135101A1 (en) * | 2005-12-08 | 2007-06-14 | Comverse, Ltd. | Enhanced visual IVR capabilities |
US8265234B2 (en) * | 2007-03-16 | 2012-09-11 | Intellicomm Inc. | Systems and methods for enabling a user to more easily navigate an interactive voice response (IVR) menu |
US20090154666A1 (en) * | 2007-12-17 | 2009-06-18 | Motorola, Inc. | Devices and methods for automating interactive voice response system interaction |
Cited By (236)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11706349B2 (en) | 2008-04-02 | 2023-07-18 | Twilio Inc. | System and method for processing telephony sessions |
US9306982B2 (en) | 2008-04-02 | 2016-04-05 | Twilio, Inc. | System and method for processing media requests during telephony sessions |
US11611663B2 (en) | 2008-04-02 | 2023-03-21 | Twilio Inc. | System and method for processing telephony sessions |
US11575795B2 (en) | 2008-04-02 | 2023-02-07 | Twilio Inc. | System and method for processing telephony sessions |
US10560495B2 (en) | 2008-04-02 | 2020-02-11 | Twilio Inc. | System and method for processing telephony sessions |
US11444985B2 (en) | 2008-04-02 | 2022-09-13 | Twilio Inc. | System and method for processing telephony sessions |
US11856150B2 (en) | 2008-04-02 | 2023-12-26 | Twilio Inc. | System and method for processing telephony sessions |
US10694042B2 (en) | 2008-04-02 | 2020-06-23 | Twilio Inc. | System and method for processing media requests during telephony sessions |
US9456008B2 (en) | 2008-04-02 | 2016-09-27 | Twilio, Inc. | System and method for processing telephony sessions |
US9591033B2 (en) | 2008-04-02 | 2017-03-07 | Twilio, Inc. | System and method for processing media requests during telephony sessions |
US11722602B2 (en) | 2008-04-02 | 2023-08-08 | Twilio Inc. | System and method for processing media requests during telephony sessions |
US10893079B2 (en) | 2008-04-02 | 2021-01-12 | Twilio Inc. | System and method for processing telephony sessions |
US11283843B2 (en) | 2008-04-02 | 2022-03-22 | Twilio Inc. | System and method for processing telephony sessions |
US11765275B2 (en) | 2008-04-02 | 2023-09-19 | Twilio Inc. | System and method for processing telephony sessions |
US8755376B2 (en) | 2008-04-02 | 2014-06-17 | Twilio, Inc. | System and method for processing telephony sessions |
US10893078B2 (en) | 2008-04-02 | 2021-01-12 | Twilio Inc. | System and method for processing telephony sessions |
US9596274B2 (en) | 2008-04-02 | 2017-03-14 | Twilio, Inc. | System and method for processing telephony sessions |
US8837465B2 (en) | 2008-04-02 | 2014-09-16 | Twilio, Inc. | System and method for processing telephony sessions |
US10986142B2 (en) | 2008-04-02 | 2021-04-20 | Twilio Inc. | System and method for processing telephony sessions |
US11831810B2 (en) | 2008-04-02 | 2023-11-28 | Twilio Inc. | System and method for processing telephony sessions |
US9906571B2 (en) | 2008-04-02 | 2018-02-27 | Twilio, Inc. | System and method for processing telephony sessions |
US9906651B2 (en) | 2008-04-02 | 2018-02-27 | Twilio, Inc. | System and method for processing media requests during telephony sessions |
US11843722B2 (en) | 2008-04-02 | 2023-12-12 | Twilio Inc. | System and method for processing telephony sessions |
US11005998B2 (en) | 2008-10-01 | 2021-05-11 | Twilio Inc. | Telephony web event system and method |
US10187530B2 (en) | 2008-10-01 | 2019-01-22 | Twilio, Inc. | Telephony web event system and method |
US9407597B2 (en) | 2008-10-01 | 2016-08-02 | Twilio, Inc. | Telephony web event system and method |
US9807244B2 (en) | 2008-10-01 | 2017-10-31 | Twilio, Inc. | Telephony web event system and method |
US11632471B2 (en) | 2008-10-01 | 2023-04-18 | Twilio Inc. | Telephony web event system and method |
US11665285B2 (en) | 2008-10-01 | 2023-05-30 | Twilio Inc. | Telephony web event system and method |
US11641427B2 (en) | 2008-10-01 | 2023-05-02 | Twilio Inc. | Telephony web event system and method |
US10455094B2 (en) | 2008-10-01 | 2019-10-22 | Twilio Inc. | Telephony web event system and method |
US8964726B2 (en) | 2008-10-01 | 2015-02-24 | Twilio, Inc. | Telephony web event system and method |
US10708437B2 (en) | 2009-03-02 | 2020-07-07 | Twilio Inc. | Method and system for a multitenancy telephone network |
US9621733B2 (en) | 2009-03-02 | 2017-04-11 | Twilio, Inc. | Method and system for a multitenancy telephone network |
US9357047B2 (en) | 2009-03-02 | 2016-05-31 | Twilio, Inc. | Method and system for a multitenancy telephone network |
US8570873B2 (en) | 2009-03-02 | 2013-10-29 | Twilio, Inc. | Method and system for a multitenancy telephone network |
US11785145B2 (en) | 2009-03-02 | 2023-10-10 | Twilio Inc. | Method and system for a multitenancy telephone network |
US9894212B2 (en) | 2009-03-02 | 2018-02-13 | Twilio, Inc. | Method and system for a multitenancy telephone network |
US10348908B2 (en) | 2009-03-02 | 2019-07-09 | Twilio, Inc. | Method and system for a multitenancy telephone network |
US8737593B2 (en) | 2009-03-02 | 2014-05-27 | Twilio, Inc. | Method and system for a multitenancy telephone network |
US11240381B2 (en) | 2009-03-02 | 2022-02-01 | Twilio Inc. | Method and system for a multitenancy telephone network |
US8995641B2 (en) | 2009-03-02 | 2015-03-31 | Twilio, Inc. | Method and system for a multitenancy telephone network |
US9210275B2 (en) | 2009-10-07 | 2015-12-08 | Twilio, Inc. | System and method for running a multi-module telephony application |
US9491309B2 (en) | 2009-10-07 | 2016-11-08 | Twilio, Inc. | System and method for running a multi-module telephony application |
US10554825B2 (en) | 2009-10-07 | 2020-02-04 | Twilio Inc. | System and method for running a multi-module telephony application |
US11637933B2 (en) | 2009-10-07 | 2023-04-25 | Twilio Inc. | System and method for running a multi-module telephony application |
US8638781B2 (en) | 2010-01-19 | 2014-01-28 | Twilio, Inc. | Method and system for preserving telephony session state |
US20130086193A1 (en) * | 2010-06-14 | 2013-04-04 | Nec Corporation | Information processing system, linkage server, and information processing method |
US9350691B2 (en) * | 2010-06-14 | 2016-05-24 | Nec Corporation | Information processing system, linkage server, and information processing method |
US20110313903A1 (en) * | 2010-06-18 | 2011-12-22 | Infosys Technologies Limited | Method and system facilitating an end-to-end solution for one or more service offerings |
US9338064B2 (en) | 2010-06-23 | 2016-05-10 | Twilio, Inc. | System and method for managing a computing cluster |
US9590849B2 (en) | 2010-06-23 | 2017-03-07 | Twilio, Inc. | System and method for managing a computing cluster |
US9459925B2 (en) | 2010-06-23 | 2016-10-04 | Twilio, Inc. | System and method for managing a computing cluster |
US11637934B2 (en) | 2010-06-23 | 2023-04-25 | Twilio Inc. | System and method for monitoring account usage on a platform |
US9459926B2 (en) | 2010-06-23 | 2016-10-04 | Twilio, Inc. | System and method for managing a computing cluster |
US8838707B2 (en) | 2010-06-25 | 2014-09-16 | Twilio, Inc. | System and method for enabling real-time eventing |
US9967224B2 (en) | 2010-06-25 | 2018-05-08 | Twilio, Inc. | System and method for enabling real-time eventing |
US11936609B2 (en) | 2010-06-25 | 2024-03-19 | Twilio Inc. | System and method for enabling real-time eventing |
US11088984B2 (en) | 2010-06-25 | 2021-08-10 | Twilio Ine. | System and method for enabling real-time eventing |
US11032330B2 (en) | 2011-02-04 | 2021-06-08 | Twilio Inc. | Method for processing telephony sessions of a network |
US20120201238A1 (en) * | 2011-02-04 | 2012-08-09 | Jeffrey Lawson | Method for processing telephony sessions of a network |
US11848967B2 (en) | 2011-02-04 | 2023-12-19 | Twilio Inc. | Method for processing telephony sessions of a network |
US10230772B2 (en) | 2011-02-04 | 2019-03-12 | Twilio, Inc. | Method for processing telephony sessions of a network |
US8649268B2 (en) * | 2011-02-04 | 2014-02-11 | Twilio, Inc. | Method for processing telephony sessions of a network |
US9455949B2 (en) | 2011-02-04 | 2016-09-27 | Twilio, Inc. | Method for processing telephony sessions of a network |
US10708317B2 (en) | 2011-02-04 | 2020-07-07 | Twilio Inc. | Method for processing telephony sessions of a network |
US9882942B2 (en) | 2011-02-04 | 2018-01-30 | Twilio, Inc. | Method for processing telephony sessions of a network |
US10819757B2 (en) | 2011-05-23 | 2020-10-27 | Twilio Inc. | System and method for real-time communication by using a client application communication protocol |
US10122763B2 (en) | 2011-05-23 | 2018-11-06 | Twilio, Inc. | System and method for connecting a communication to a client |
US10165015B2 (en) | 2011-05-23 | 2018-12-25 | Twilio Inc. | System and method for real-time communication by using a client application communication protocol |
US9648006B2 (en) | 2011-05-23 | 2017-05-09 | Twilio, Inc. | System and method for communicating with a client application |
US10560485B2 (en) | 2011-05-23 | 2020-02-11 | Twilio Inc. | System and method for connecting a communication to a client |
US9398622B2 (en) | 2011-05-23 | 2016-07-19 | Twilio, Inc. | System and method for connecting a communication to a client |
US11399044B2 (en) | 2011-05-23 | 2022-07-26 | Twilio Inc. | System and method for connecting a communication to a client |
US9413888B2 (en) * | 2011-06-15 | 2016-08-09 | Nickelback OU | Terminal based interactive voice response system with information prioritization |
US10212275B2 (en) | 2011-09-21 | 2019-02-19 | Twilio, Inc. | System and method for determining and communicating presence information |
US9336500B2 (en) | 2011-09-21 | 2016-05-10 | Twilio, Inc. | System and method for authorizing and connecting application developers and users |
US10182147B2 (en) | 2011-09-21 | 2019-01-15 | Twilio Inc. | System and method for determining and communicating presence information |
US9942394B2 (en) | 2011-09-21 | 2018-04-10 | Twilio, Inc. | System and method for determining and communicating presence information |
US10841421B2 (en) | 2011-09-21 | 2020-11-17 | Twilio Inc. | System and method for determining and communicating presence information |
US10686936B2 (en) | 2011-09-21 | 2020-06-16 | Twilio Inc. | System and method for determining and communicating presence information |
US9641677B2 (en) | 2011-09-21 | 2017-05-02 | Twilio, Inc. | System and method for determining and communicating presence information |
US11489961B2 (en) | 2011-09-21 | 2022-11-01 | Twilio Inc. | System and method for determining and communicating presence information |
US9699632B2 (en) | 2011-09-28 | 2017-07-04 | Elwha Llc | Multi-modality communication with interceptive conversion |
US9762524B2 (en) * | 2011-09-28 | 2017-09-12 | Elwha Llc | Multi-modality communication participation |
US20130080519A1 (en) * | 2011-09-28 | 2013-03-28 | Royce A. Levien | Multi-modality communication participation |
US9794209B2 (en) | 2011-09-28 | 2017-10-17 | Elwha Llc | User interface for multi-modality communication |
US9906927B2 (en) | 2011-09-28 | 2018-02-27 | Elwha Llc | Multi-modality communication initiation |
US9477943B2 (en) | 2011-09-28 | 2016-10-25 | Elwha Llc | Multi-modality communication |
US9503550B2 (en) | 2011-09-28 | 2016-11-22 | Elwha Llc | Multi-modality communication modification |
US9002937B2 (en) | 2011-09-28 | 2015-04-07 | Elwha Llc | Multi-party multi-modality communication |
US9788349B2 (en) | 2011-09-28 | 2017-10-10 | Elwha Llc | Multi-modality communication auto-activation |
US9307083B2 (en) * | 2011-11-22 | 2016-04-05 | Incontact, Inc. | Systems and methods of parallel media communication in contact handling systems |
US20130129073A1 (en) * | 2011-11-22 | 2013-05-23 | Incontact, Inc. | Systems and methods of parallel media communication in contact handling systems |
US20140324424A1 (en) * | 2011-11-23 | 2014-10-30 | Yongjin Kim | Method for providing a supplementary voice recognition service and apparatus applied to same |
US11093305B2 (en) | 2012-02-10 | 2021-08-17 | Twilio Inc. | System and method for managing concurrent events |
US10467064B2 (en) | 2012-02-10 | 2019-11-05 | Twilio Inc. | System and method for managing concurrent events |
US9495227B2 (en) | 2012-02-10 | 2016-11-15 | Twilio, Inc. | System and method for managing concurrent events |
US9602586B2 (en) | 2012-05-09 | 2017-03-21 | Twilio, Inc. | System and method for managing media in a distributed communication network |
US11165853B2 (en) | 2012-05-09 | 2021-11-02 | Twilio Inc. | System and method for managing media in a distributed communication network |
US10200458B2 (en) | 2012-05-09 | 2019-02-05 | Twilio, Inc. | System and method for managing media in a distributed communication network |
US9240941B2 (en) | 2012-05-09 | 2016-01-19 | Twilio, Inc. | System and method for managing media in a distributed communication network |
US9350642B2 (en) | 2012-05-09 | 2016-05-24 | Twilio, Inc. | System and method for managing latency in a distributed telephony network |
US8601136B1 (en) | 2012-05-09 | 2013-12-03 | Twilio, Inc. | System and method for managing latency in a distributed telephony network |
US10637912B2 (en) | 2012-05-09 | 2020-04-28 | Twilio Inc. | System and method for managing media in a distributed communication network |
US11546471B2 (en) | 2012-06-19 | 2023-01-03 | Twilio Inc. | System and method for queuing a communication session |
US10320983B2 (en) | 2012-06-19 | 2019-06-11 | Twilio Inc. | System and method for queuing a communication session |
US9247062B2 (en) | 2012-06-19 | 2016-01-26 | Twilio, Inc. | System and method for queuing a communication session |
CN104428419A (en) * | 2012-07-04 | 2015-03-18 | 艾维贝合作公司 | Methods using patatin |
US11882139B2 (en) | 2012-07-24 | 2024-01-23 | Twilio Inc. | Method and system for preventing illicit use of a telephony platform |
US10469670B2 (en) | 2012-07-24 | 2019-11-05 | Twilio Inc. | Method and system for preventing illicit use of a telephony platform |
US11063972B2 (en) | 2012-07-24 | 2021-07-13 | Twilio Inc. | Method and system for preventing illicit use of a telephony platform |
US9948788B2 (en) | 2012-07-24 | 2018-04-17 | Twilio, Inc. | Method and system for preventing illicit use of a telephony platform |
US9614972B2 (en) | 2012-07-24 | 2017-04-04 | Twilio, Inc. | Method and system for preventing illicit use of a telephony platform |
US8737962B2 (en) | 2012-07-24 | 2014-05-27 | Twilio, Inc. | Method and system for preventing illicit use of a telephony platform |
US9270833B2 (en) | 2012-07-24 | 2016-02-23 | Twilio, Inc. | Method and system for preventing illicit use of a telephony platform |
US8738051B2 (en) | 2012-07-26 | 2014-05-27 | Twilio, Inc. | Method and system for controlling message routing |
US8644457B1 (en) | 2012-10-01 | 2014-02-04 | Google Inc. | System and method for enforcing a recording preference |
US8477915B1 (en) * | 2012-10-01 | 2013-07-02 | Google Inc. | System and method for enforcing a recording preference |
US10033617B2 (en) | 2012-10-15 | 2018-07-24 | Twilio, Inc. | System and method for triggering on platform usage |
US11689899B2 (en) | 2012-10-15 | 2023-06-27 | Twilio Inc. | System and method for triggering on platform usage |
US10757546B2 (en) | 2012-10-15 | 2020-08-25 | Twilio Inc. | System and method for triggering on platform usage |
US11595792B2 (en) | 2012-10-15 | 2023-02-28 | Twilio Inc. | System and method for triggering on platform usage |
US8938053B2 (en) | 2012-10-15 | 2015-01-20 | Twilio, Inc. | System and method for triggering on platform usage |
US8948356B2 (en) | 2012-10-15 | 2015-02-03 | Twilio, Inc. | System and method for routing communications |
US9319857B2 (en) | 2012-10-15 | 2016-04-19 | Twilio, Inc. | System and method for triggering on platform usage |
US9307094B2 (en) | 2012-10-15 | 2016-04-05 | Twilio, Inc. | System and method for routing communications |
US10257674B2 (en) | 2012-10-15 | 2019-04-09 | Twilio, Inc. | System and method for triggering on platform usage |
US11246013B2 (en) | 2012-10-15 | 2022-02-08 | Twilio Inc. | System and method for triggering on platform usage |
US9654647B2 (en) | 2012-10-15 | 2017-05-16 | Twilio, Inc. | System and method for routing communications |
US9160855B2 (en) | 2012-12-12 | 2015-10-13 | Genesys Telecommunications Laboratories, Inc. | System and method for call and data matching in a contact center |
US9088656B2 (en) | 2012-12-12 | 2015-07-21 | Genesys Telecommunications Laboratories, Inc. | System and method for access number distribution in a contact center |
US9621727B2 (en) | 2012-12-12 | 2017-04-11 | Genesys Telecommunications Laboratories, Inc. | System and method for call and data matching in a contact center |
US9578172B2 (en) | 2012-12-12 | 2017-02-21 | Genesys Telecommunications Laboratories, Inc. | System and method for providing interaction history via a customer application |
US9531878B2 (en) | 2012-12-12 | 2016-12-27 | Genesys Telecommunications Laboratories, Inc. | System and method for access number distribution in a contact center |
US10122858B2 (en) | 2012-12-12 | 2018-11-06 | Genesys Telecommunications Laboratories, Inc. | System and method for interacting with customer contact center over a mobile device |
US8781103B2 (en) | 2012-12-12 | 2014-07-15 | Genesys Telecommunications Laboratories, Inc. | System and method for call and data matching in a contact center |
US10171664B2 (en) | 2012-12-19 | 2019-01-01 | Genesys Telecommunications Laboratories, Inc. | Customer care mobile application |
US9064259B2 (en) | 2012-12-19 | 2015-06-23 | Genesys Telecomminucations Laboratories, Inc. | Customer care mobile application |
US9883038B2 (en) | 2012-12-19 | 2018-01-30 | Genesys Telecommunications Laboratories, Inc. | Customer care mobile application |
US9532209B2 (en) | 2012-12-19 | 2016-12-27 | Genesys Telecommunications Laboratories, Inc. | Customer care mobile application |
US9253254B2 (en) | 2013-01-14 | 2016-02-02 | Twilio, Inc. | System and method for offering a multi-partner delegated platform |
US9984374B2 (en) | 2013-02-25 | 2018-05-29 | Genesys Telecommunications Laboratories Inc. | Mobile expert desktop |
US10051011B2 (en) | 2013-03-14 | 2018-08-14 | Twilio, Inc. | System and method for integrating session initiation protocol communication in a telecommunications platform |
US11032325B2 (en) | 2013-03-14 | 2021-06-08 | Twilio Inc. | System and method for integrating session initiation protocol communication in a telecommunications platform |
US9282124B2 (en) | 2013-03-14 | 2016-03-08 | Twilio, Inc. | System and method for integrating session initiation protocol communication in a telecommunications platform |
US11637876B2 (en) | 2013-03-14 | 2023-04-25 | Twilio Inc. | System and method for integrating session initiation protocol communication in a telecommunications platform |
US10560490B2 (en) | 2013-03-14 | 2020-02-11 | Twilio Inc. | System and method for integrating session initiation protocol communication in a telecommunications platform |
US9001666B2 (en) | 2013-03-15 | 2015-04-07 | Twilio, Inc. | System and method for improving routing in a distributed communication platform |
US20140348311A1 (en) * | 2013-05-22 | 2014-11-27 | Hon Hai Precision Industry Co., Ltd. | Information broadcasting system and method |
US9992608B2 (en) | 2013-06-19 | 2018-06-05 | Twilio, Inc. | System and method for providing a communication endpoint information service |
US9225840B2 (en) | 2013-06-19 | 2015-12-29 | Twilio, Inc. | System and method for providing a communication endpoint information service |
US9338280B2 (en) | 2013-06-19 | 2016-05-10 | Twilio, Inc. | System and method for managing telephony endpoint inventory |
US10057734B2 (en) | 2013-06-19 | 2018-08-21 | Twilio Inc. | System and method for transmitting and receiving media messages |
US9160696B2 (en) | 2013-06-19 | 2015-10-13 | Twilio, Inc. | System for transforming media resource into destination device compatible messaging format |
US9240966B2 (en) | 2013-06-19 | 2016-01-19 | Twilio, Inc. | System and method for transmitting and receiving media messages |
US9483328B2 (en) | 2013-07-19 | 2016-11-01 | Twilio, Inc. | System and method for delivering application content |
US10439907B2 (en) | 2013-09-17 | 2019-10-08 | Twilio Inc. | System and method for providing communication platform metadata |
US10671452B2 (en) | 2013-09-17 | 2020-06-02 | Twilio Inc. | System and method for tagging and tracking events of an application |
US9137127B2 (en) | 2013-09-17 | 2015-09-15 | Twilio, Inc. | System and method for providing communication platform metadata |
US9338018B2 (en) | 2013-09-17 | 2016-05-10 | Twilio, Inc. | System and method for pricing communication of a telecommunication platform |
US9853872B2 (en) | 2013-09-17 | 2017-12-26 | Twilio, Inc. | System and method for providing communication platform metadata |
US11539601B2 (en) | 2013-09-17 | 2022-12-27 | Twilio Inc. | System and method for providing communication platform metadata |
US9959151B2 (en) | 2013-09-17 | 2018-05-01 | Twilio, Inc. | System and method for tagging and tracking events of an application platform |
US9811398B2 (en) | 2013-09-17 | 2017-11-07 | Twilio, Inc. | System and method for tagging and tracking events of an application platform |
US11379275B2 (en) | 2013-09-17 | 2022-07-05 | Twilio Inc. | System and method for tagging and tracking events of an application |
US10063461B2 (en) | 2013-11-12 | 2018-08-28 | Twilio, Inc. | System and method for client communication in a distributed telephony network |
US10069773B2 (en) | 2013-11-12 | 2018-09-04 | Twilio, Inc. | System and method for enabling dynamic multi-modal communication |
US11394673B2 (en) | 2013-11-12 | 2022-07-19 | Twilio Inc. | System and method for enabling dynamic multi-modal communication |
US11621911B2 (en) | 2013-11-12 | 2023-04-04 | Twillo Inc. | System and method for client communication in a distributed telephony network |
US9553799B2 (en) | 2013-11-12 | 2017-01-24 | Twilio, Inc. | System and method for client communication in a distributed telephony network |
US11831415B2 (en) | 2013-11-12 | 2023-11-28 | Twilio Inc. | System and method for enabling dynamic multi-modal communication |
US10686694B2 (en) | 2013-11-12 | 2020-06-16 | Twilio Inc. | System and method for client communication in a distributed telephony network |
US9325624B2 (en) | 2013-11-12 | 2016-04-26 | Twilio, Inc. | System and method for enabling dynamic multi-modal communication |
US10904389B2 (en) | 2014-03-14 | 2021-01-26 | Twilio Inc. | System and method for a work distribution service |
US9344573B2 (en) | 2014-03-14 | 2016-05-17 | Twilio, Inc. | System and method for a work distribution service |
US11882242B2 (en) | 2014-03-14 | 2024-01-23 | Twilio Inc. | System and method for a work distribution service |
US10291782B2 (en) | 2014-03-14 | 2019-05-14 | Twilio, Inc. | System and method for a work distribution service |
US9628624B2 (en) | 2014-03-14 | 2017-04-18 | Twilio, Inc. | System and method for a work distribution service |
US11330108B2 (en) | 2014-03-14 | 2022-05-10 | Twilio Inc. | System and method for a work distribution service |
US10003693B2 (en) | 2014-03-14 | 2018-06-19 | Twilio, Inc. | System and method for a work distribution service |
US10873892B2 (en) | 2014-04-17 | 2020-12-22 | Twilio Inc. | System and method for enabling multi-modal communication |
US11653282B2 (en) | 2014-04-17 | 2023-05-16 | Twilio Inc. | System and method for enabling multi-modal communication |
US9907010B2 (en) | 2014-04-17 | 2018-02-27 | Twilio, Inc. | System and method for enabling multi-modal communication |
US9226217B2 (en) | 2014-04-17 | 2015-12-29 | Twilio, Inc. | System and method for enabling multi-modal communication |
US10440627B2 (en) | 2014-04-17 | 2019-10-08 | Twilio Inc. | System and method for enabling multi-modal communication |
US10212237B2 (en) | 2014-07-07 | 2019-02-19 | Twilio, Inc. | System and method for managing media and signaling in a communication platform |
US10757200B2 (en) | 2014-07-07 | 2020-08-25 | Twilio Inc. | System and method for managing conferencing in a distributed communication network |
US9774687B2 (en) | 2014-07-07 | 2017-09-26 | Twilio, Inc. | System and method for managing media and signaling in a communication platform |
US10229126B2 (en) | 2014-07-07 | 2019-03-12 | Twilio, Inc. | Method and system for applying data retention policies in a computing platform |
US9251371B2 (en) | 2014-07-07 | 2016-02-02 | Twilio, Inc. | Method and system for applying data retention policies in a computing platform |
US9246694B1 (en) | 2014-07-07 | 2016-01-26 | Twilio, Inc. | System and method for managing conferencing in a distributed communication network |
US11768802B2 (en) | 2014-07-07 | 2023-09-26 | Twilio Inc. | Method and system for applying data retention policies in a computing platform |
US9588974B2 (en) | 2014-07-07 | 2017-03-07 | Twilio, Inc. | Method and system for applying data retention policies in a computing platform |
US9858279B2 (en) | 2014-07-07 | 2018-01-02 | Twilio, Inc. | Method and system for applying data retention policies in a computing platform |
US9516101B2 (en) | 2014-07-07 | 2016-12-06 | Twilio, Inc. | System and method for collecting feedback in a multi-tenant communication platform |
US11341092B2 (en) | 2014-07-07 | 2022-05-24 | Twilio Inc. | Method and system for applying data retention policies in a computing platform |
US10116733B2 (en) | 2014-07-07 | 2018-10-30 | Twilio, Inc. | System and method for collecting feedback in a multi-tenant communication platform |
US10747717B2 (en) | 2014-07-07 | 2020-08-18 | Twilio Inc. | Method and system for applying data retention policies in a computing platform |
US11755530B2 (en) | 2014-07-07 | 2023-09-12 | Twilio Inc. | Method and system for applying data retention policies in a computing platform |
US9553900B2 (en) | 2014-07-07 | 2017-01-24 | Twilio, Inc. | System and method for managing conferencing in a distributed communication network |
US9516167B2 (en) | 2014-07-24 | 2016-12-06 | Genesys Telecommunications Laboratories, Inc. | Media channel management apparatus for network communications sessions |
US10476917B2 (en) | 2014-07-24 | 2019-11-12 | Genesys Telecommunications Laboratories, Inc. | Media channel management apparatus for network communications sessions |
US11019159B2 (en) | 2014-10-21 | 2021-05-25 | Twilio Inc. | System and method for providing a micro-services communication platform |
US9906607B2 (en) | 2014-10-21 | 2018-02-27 | Twilio, Inc. | System and method for providing a micro-services communication platform |
US9363301B2 (en) | 2014-10-21 | 2016-06-07 | Twilio, Inc. | System and method for providing a micro-services communication platform |
US9509782B2 (en) | 2014-10-21 | 2016-11-29 | Twilio, Inc. | System and method for providing a micro-services communication platform |
US10637938B2 (en) | 2014-10-21 | 2020-04-28 | Twilio Inc. | System and method for providing a micro-services communication platform |
US10853854B2 (en) | 2015-02-03 | 2020-12-01 | Twilio Inc. | System and method for a media intelligence platform |
US11544752B2 (en) | 2015-02-03 | 2023-01-03 | Twilio Inc. | System and method for a media intelligence platform |
US9477975B2 (en) | 2015-02-03 | 2016-10-25 | Twilio, Inc. | System and method for a media intelligence platform |
US9805399B2 (en) | 2015-02-03 | 2017-10-31 | Twilio, Inc. | System and method for a media intelligence platform |
US10467665B2 (en) | 2015-02-03 | 2019-11-05 | Twilio Inc. | System and method for a media intelligence platform |
US9467563B1 (en) | 2015-04-10 | 2016-10-11 | Angel.Com Incorporated | Visual interactive voice response system |
US10270908B2 (en) | 2015-04-10 | 2019-04-23 | Genesys Telecommunications Laboratories, Inc. | Visual interactive voice response system |
US11265367B2 (en) | 2015-05-14 | 2022-03-01 | Twilio Inc. | System and method for signaling through data storage |
US11272325B2 (en) | 2015-05-14 | 2022-03-08 | Twilio Inc. | System and method for communicating through multiple endpoints |
US10419891B2 (en) | 2015-05-14 | 2019-09-17 | Twilio, Inc. | System and method for communicating through multiple endpoints |
US9948703B2 (en) | 2015-05-14 | 2018-04-17 | Twilio, Inc. | System and method for signaling through data storage |
US10560516B2 (en) | 2015-05-14 | 2020-02-11 | Twilio Inc. | System and method for signaling through data storage |
US11171865B2 (en) | 2016-02-04 | 2021-11-09 | Twilio Inc. | Systems and methods for providing secure network exchanged for a multitenant virtual private cloud |
US10659349B2 (en) | 2016-02-04 | 2020-05-19 | Twilio Inc. | Systems and methods for providing secure network exchanged for a multitenant virtual private cloud |
US11622022B2 (en) | 2016-05-23 | 2023-04-04 | Twilio Inc. | System and method for a multi-channel notification service |
US11265392B2 (en) | 2016-05-23 | 2022-03-01 | Twilio Inc. | System and method for a multi-channel notification service |
US10440192B2 (en) | 2016-05-23 | 2019-10-08 | Twilio Inc. | System and method for programmatic device connectivity |
US11076054B2 (en) | 2016-05-23 | 2021-07-27 | Twilio Inc. | System and method for programmatic device connectivity |
US11627225B2 (en) | 2016-05-23 | 2023-04-11 | Twilio Inc. | System and method for programmatic device connectivity |
US10063713B2 (en) | 2016-05-23 | 2018-08-28 | Twilio Inc. | System and method for programmatic device connectivity |
US10686902B2 (en) | 2016-05-23 | 2020-06-16 | Twilio Inc. | System and method for a multi-channel notification service |
US10320979B2 (en) * | 2017-09-08 | 2019-06-11 | Verizon Patent And Licensing Inc. | Data structure driven interactive voice response (IVR) framework |
WO2021178114A1 (en) * | 2020-03-06 | 2021-09-10 | PAG Financial International LLC | Systems and methods for operating an interactive voice response system |
US11363140B2 (en) | 2020-03-06 | 2022-06-14 | Celligence International Llc | Systems and methods for operating an interactive voice response system |
GB2609130A (en) * | 2020-03-06 | 2023-01-25 | Celligence Int Llc | Systems and methods for operating an interactive voice response system |
US11039013B1 (en) * | 2020-04-10 | 2021-06-15 | Medallia, Inc. | Real-time contact center speech analytics, with critical call alerts, deployed across multiple security zones |
US11843717B2 (en) | 2020-09-30 | 2023-12-12 | Avaya Management L.P. | Highly scalable contact center with automated transition from voice interaction |
GB2600553A (en) * | 2020-09-30 | 2022-05-04 | Avaya Man Lp | Enhanced digital messaging |
Also Published As
Publication number | Publication date |
---|---|
WO2011106139A1 (en) | 2011-09-01 |
US20140334614A1 (en) | 2014-11-13 |
US9560199B2 (en) | 2017-01-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9560199B2 (en) | Voice response processing | |
JP3101768B2 (en) | Voice Call Notification and Message Control by Data Path | |
US7961865B1 (en) | Method for handling incoming calls directed to a virtual communication service subscriber via a guest PBX | |
US7180991B2 (en) | Dynamic, interactive call notification | |
AU2004260484B2 (en) | Multi-user call waiting | |
US20070064915A1 (en) | Language interpretation call transferring in a telecommunications network | |
US20050232169A1 (en) | System and method for providing telecommunication relay services | |
KR100513217B1 (en) | System for coordinating calls between an adjunct device and a switching system | |
EP2572523A1 (en) | Dynamic call routing for real-time handling of inbound voice calls on mobile phones | |
JP5302248B2 (en) | Computer and phone integration | |
EP1836867A2 (en) | Method and device for communications while using a single telephone device | |
US20090028300A1 (en) | Network communication systems including video phones | |
US7555521B1 (en) | System and method for accepting text calls on voice telephones at call centers or other locations | |
JP2009182836A (en) | Call center apparatus | |
US10819853B2 (en) | System and method for replacing hold-time with a call back in a contact center environment | |
WO2012159036A1 (en) | Method and apparatus for providing called party data to a subscriber of a call forwarding system via at least one mobile network | |
US20050025127A1 (en) | Method and apparatus for communication web services | |
US20130093830A1 (en) | Systems and methods for accepting video calls on voice telephones at call centers or other locations | |
JP3703072B2 (en) | Method and system for reducing call costs at a recipient | |
EP1610570B1 (en) | System for transferring data between a wireless caller and a communication center | |
US6603848B1 (en) | Techniques for providing caller name announcement | |
US20140269440A1 (en) | Systems and methods for handling incoming communications directed to a telephony device | |
JP7150243B2 (en) | Automated message system and method | |
US7184536B2 (en) | Intelligent forwarded telephone call handling with a call answering system | |
US20140269439A1 (en) | Systems and methods for handling incoming communications directed to a telephony device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: GENESYS TELECOMMUNICATIONS LABORATORIES, INC., CAL Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MEZHIBOVSKY, VLADIMIR;SAINT-MARC, JEROME;REEL/FRAME:023999/0606 Effective date: 20100208 |
|
AS | Assignment |
Owner name: GOLDMAN SACHS LENDING PARTNERS LLC, NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNOR:GENESYS TELECOMMUNICATIONS LABORATORIES, INC.;REEL/FRAME:027623/0096 Effective date: 20120131 |
|
AS | Assignment |
Owner name: ALCATEL LUCENT, FRANCE Free format text: ASSIGNMENT OF 50% INTEREST;ASSIGNOR:GENESYS TELECOMMUNICATIONS LABORATORIES, INC.;REEL/FRAME:027714/0838 Effective date: 20120130 |
|
AS | Assignment |
Owner name: CREDIT SUISSE AG, NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNOR:LUCENT, ALCATEL;REEL/FRAME:029821/0001 Effective date: 20130130 Owner name: CREDIT SUISSE AG, NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNOR:ALCATEL LUCENT;REEL/FRAME:029821/0001 Effective date: 20130130 |
|
AS | Assignment |
Owner name: GENESYS TELECOMMUNICATIONS LABORATORIES, INC., CAL Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:GOLDMAN SACHS LENDING PARTNERS LLC;REEL/FRAME:029778/0060 Effective date: 20130208 Owner name: GOLDMAN SACHS BANK USA, NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNOR:GENESYS TELECOMMUNICATIONS LABORATORIES, INC.;REEL/FRAME:029778/0939 Effective date: 20130208 |
|
AS | Assignment |
Owner name: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT, DE Free format text: SECURITY AGREEMENT;ASSIGNORS:GENESYS TELECOMMUNICATIONS LABORATORIES, INC.;ANGEL.COM INCORPORATED;UTOPY, INC.;AND OTHERS;REEL/FRAME:031644/0814 Effective date: 20131113 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: ALCATEL LUCENT, FRANCE Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG;REEL/FRAME:033868/0555 Effective date: 20140819 |
|
AS | Assignment |
Owner name: ANGEL.COM INCORPORATED, CALIFORNIA Free format text: PATENT RELEASE (REEL:031644/FRAME:0814);ASSIGNOR:JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT;REEL/FRAME:040798/0428 Effective date: 20161201 Owner name: UTOPY, INC., CALIFORNIA Free format text: PATENT RELEASE (REEL:031644/FRAME:0814);ASSIGNOR:JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT;REEL/FRAME:040798/0428 Effective date: 20161201 Owner name: SOUNDBITE COMMUNICATIONS, INC., CALIFORNIA Free format text: PATENT RELEASE (REEL:031644/FRAME:0814);ASSIGNOR:JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT;REEL/FRAME:040798/0428 Effective date: 20161201 Owner name: GENESYS TELECOMMUNICATIONS LABORATORIES, INC., AS Free format text: PATENT RELEASE (REEL:031644/FRAME:0814);ASSIGNOR:JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT;REEL/FRAME:040798/0428 Effective date: 20161201 |
|
AS | Assignment |
Owner name: ANGEL.COM INCORPORATED, CALIFORNIA Free format text: CORRECTIVE RELEASE FOR SECURITY INTEREST IN PATENTS ORIGINALLY RECORDED AT REEL/FRAME (029778/0939);ASSIGNOR:JPMORGAN CHASE BANK, N.A., AS SUCCESSOR TO THE ORIGINAL COLLATERAL AGENT GOLDMAN SACHS BANK USA;REEL/FRAME:041821/0209 Effective date: 20170223 Owner name: GENESYS TELECOMMUNICATIONS LABORATORIES, INC., CAL Free format text: CORRECTIVE RELEASE FOR SECURITY INTEREST IN PATENTS ORIGINALLY RECORDED AT REEL/FRAME (029778/0939);ASSIGNOR:JPMORGAN CHASE BANK, N.A., AS SUCCESSOR TO THE ORIGINAL COLLATERAL AGENT GOLDMAN SACHS BANK USA;REEL/FRAME:041821/0209 Effective date: 20170223 Owner name: UTOPY, INC., CALIFORNIA Free format text: CORRECTIVE RELEASE FOR SECURITY INTEREST IN PATENTS ORIGINALLY RECORDED AT REEL/FRAME (029778/0939);ASSIGNOR:JPMORGAN CHASE BANK, N.A., AS SUCCESSOR TO THE ORIGINAL COLLATERAL AGENT GOLDMAN SACHS BANK USA;REEL/FRAME:041821/0209 Effective date: 20170223 Owner name: SOUNDBITE COMMUNICATIONS, INC., CALIFORNIA Free format text: CORRECTIVE RELEASE FOR SECURITY INTEREST IN PATENTS ORIGINALLY RECORDED AT REEL/FRAME (029778/0939);ASSIGNOR:JPMORGAN CHASE BANK, N.A., AS SUCCESSOR TO THE ORIGINAL COLLATERAL AGENT GOLDMAN SACHS BANK USA;REEL/FRAME:041821/0209 Effective date: 20170223 |