Systems and methods for visual presentation and selection of IVR menu
Embodiments of the invention provide a system for enhancing user interaction with Interactive Voice Response (IVR) destinations, the system comprising: a processor; and a memory coupled to the processor, the memory comprising: data encoding a database, the database comprising a list of telephone numbers associated with one or more destinations implementing an IVR; instructions executable by the processor for automatically communicating with at least one user; and instructions executable by the processor to pull at least one menu from the database and display the menu to the at least one user, wherein the menu is associated with a telephone number dialed by the at least one user, and wherein the menu comprises at least one icon.
The invention relates to Interactive Voice Response (IVR) system and more specifically the invention relates to visual selection of IVR option from a caller device.BACKGROUND OF THE INVENTION
Interactive Voice Response (IVR) technology is generally used to detect voice and key inputs from a caller. Various organizations such as banks, insurance companies, and other service providers use IVR technology to manage calls from their customers. Typically, IVR systems are used by organizations that have high call volumes. An objective for implementing the IVR systems is to provide the customers with a quick and good experience. Moreover, the cost of providing the services is reduced.
Generally, when the caller calls a destination, such as a bank, an automated audio menu is played. The audio IVR menu can contain instructions to provide instant services such as account balance inquiry when the destination is a bank. Further, audio menu can provide options for the caller to connect to a desired end inside the destination. For example, the menu may direct the caller to press various keys on a telephone to connect to a particular department or agent. The audio IVR menu is designed specific to a destination. Therefore, each destination or organization may have different IVR menus. Further, the IVR menu in an organization can be based on the type of departments, type of services, customer care executives or agents and so forth. For example, an IVR menu of a bank may include options related to the account details of the caller, while an IVR menu of a pizzeria may contain options to order or select a pizza.
Typically, the caller calling the destination may have to listen and follow instructions on the menu to get a desired response or a function performed. Therefore, the process can be time consuming. Moreover, in case the caller provides an incorrect input, the complete process may have to be repeated. Furthermore, the IVR menu for an organization may be updated or changed regularly. For example, extension numbers inside an organization may be changed and correspondingly, the extension numbers associated with the IVR menu may be updated. As a result, a frequent caller may not be able to reach a desired end by remembering a combination of numbers. Therefore, the caller may become frustrated with the IVR systems.
Some prior art try to address this problem by providing visual form of IVR. These prior arts display the IVR menu graphically on a caller device. U.S. Pat. No. 7,215,743 assigned to International Business Machines Corporation and a published U.S. patent application Ser. No. 11/957,605, filed Dec. 17, 2007 and assigned to Motorola Inc., provides the IVR menu of the destination in a visual form to the caller. The caller can select the options from the IVR menu without listening to the complete audio IVR menu. However, the IVR menu displayed on the caller device is stored on an IVR server at the destination end. As a result, the visual IVR menu is specific to the destination and only the IVR of the destination dialed is displayed. Further, the IVR menu may be required to be configured on the server of the destination to display it to the caller, as disclosed in U.S. Pat. No. 7,092,738 assigned to International Business Machines Corporation. A U.S. patent application Ser. No. 11/467,548, filed Aug. 26, 2006 discloses sending digital signals from the destination to the caller device. Thereafter, the digital signals are processed by the caller device for presenting a visual display of the IVR menu. These techniques therefore, require each destination to set-up hardware, software and other facilities to be deployed for providing visual IVR servers.
Another existing technique as disclosed in U.S. Pat. No. 6,560,320 assigned to International Business Machines Corporation enables an operator of the IVR to send customized signals to the caller for generating and displaying graphical elements on the device of the caller. Thereafter, the caller can respond by selecting options through touch-screen interface of the device. Dual Tone Multi frequency (DTMF) signals of the IVR. However, this technique requires a specifically configured device to interpret the codes sent as Dual Tone Multi frequency (DTMF) signals for generating the graphics. Moreover, an operator is required to present the graphics to the caller. Furthermore, specialized software and hardware are required at the operator to design and generate DTMF codes. Therefore, the technique faces various practical limitations. Further, a U.S. Pat. No. 7,027,990 assigned to Lester Sussman, discloses visual menus for a touch-tone telephone with an embedded computer. In this case the text menus may be pre-loaded into the telephone of the caller as text menus. Therefore, when the caller dials the destination, an associated text menu is displayed on a screen. However, this technique is limited to touch-tone telephones with embedded computer. Another existing technique as disclosed in U.S. patent application Ser. No. 11/957,605, filed on Dec. 17, 2007 and assigned to Motorola Inc., provides a directory of an IVR system in the form of, for example, a menu tree, on screen of the caller device. However, the menu tree is provided to the caller device by a remote server. Another existing technique discloses sending messages such as Short Messaging Service (SMS) to the caller device corresponding to the audible IVR menu. Such technique is disclosed in U.S. patent application Ser. No. 11/877,952, filed Oct. 24, 2007. However, the message functions only as a visual aid and the caller is still required to listen and respond to the audio IVR menu. A published PCT Application WO 2008/086320, filed Jan. 7, 2008 and assigned to Snapin Software Inc., displays IVR menu to the caller's device after connecting a call with the destination.
Generally, the IVR menus of the organizations are in form of audible menu. Moreover, there are a large number of organizations that use IVR menus. Therefore, converting the audible menus to visual menus can be time consuming. An existing technique, as disclosed in U.S. Pat. No. 6,920,425 assigned to Nortel Networks Limited, discloses an automated script to convert the audible menus scripts to visual menu scripts. However, the audible menus scripts must be available in a particular format to enable the conversion. Furthermore, the audio menu scripts must be available or downloadable for the program to function. As a result, only the audio menus scripts that are available can be converted to visual menu scripts. Furthermore, the device of the caller must be designed or programmed to understand the visual menu scripts. A U.S. Pat. No. 6,885,737 assigned to BellSouth Intellectual Property Corp., discloses a web interface for displaying the IVR menu. However, a server is required to transmit the IVR menu to the caller's device.
Various organizations encourage the customers to call them for information on their products or services, or for helping existing customers. Generally, a contact number is provided by the organizations on their website as a button. Therefore, when the customer presses the button a form is displayed. The customer then enters his contact number where an executive from the organization may call. However, this may be time consuming for the customer. Moreover, the customer may be not being able to talk to another executive during the call in case the on-line executive is not able to satisfy the customer. U.S. patent application Ser. No. 12/049,021, filed Mar. 14, 2008 and assigned to Harprit Singh, provides methods and systems for displaying an IVR menu, when the caller clicks a link on a webpage provided by the organization. However, the customer is still required to request the webpage with embedded information from a server of the organization. Moreover, the methods and systems are limited to the organizations that provide the required webpage to the customers. Other technologies include U.S. patent application Ser. No. 11/877,952 filed Oct. 24, 2007 and assigned to International Business Machine Corporation.
The effectiveness of providing the IVR in visual form is discussed in a technical paper titled, ‘The Benefits of Augmenting Telephone Voice Menu Navigation with Visual Browsing and Search’ by Min Yin et al. The paper discusses a setup where visual content of the IVR is sent from a service provider to a computer connected to a mobile phone. However, the technique discussed in the paper is limited to the visual content provided by the service provider's end, after the connection is established. Moreover, the providers are required to individually set up the hardware and services for providing visual content.
As discussed above the existing technologies have various limitations.SUMMARY
An aspect of the invention is to provide to a caller using a device a visual menu corresponding to an audible IVR menu of a destination.
Another aspect of the invention is to enable the caller to directly interact with the visual menu without listening to the audible IVR menu of the destination.
Yet another aspect of the invention is to provide the visual menu to the caller before establishing a connection of the device with the destination.
Another aspect of the invention is to enable the caller to interact with the visual menu by using a touch sensitive screen of the device.
Another aspect of the invention is to provide advertisements related to the destination or function of the destination dialed by the caller.
A caller may dial or select a phone number from a device of a destination. The phone number is detected by Visuphone implemented on the device to display a visual menu corresponding to the audible IVR menu of the destination. Visuphone may be hardware, an application stored as a software or firmware on the device, or a combination thereof. Visuphone may include a database of visual menus corresponding to audible IVR menus for various destinations. Thereafter, the caller may interact with the visual menu displayed on the device to establish a connection with the destination. Furthermore, Visuphone may detect and launch a VOIP application for establishing the connection. Moreover, Visuphone may provide pre-recorded or computer synthesized audio responses on behalf of the caller to the destination.
An enhanced telephone system is provided. The telephone system comprises a database that comprises one or more phone numbers and one or more menus corresponding to the phone numbers, wherein the menus comprise one or more options for selection. The telephone system comprises means for comparing a dialed number to the phone numbers in the database; means for displaying a menu based on a result of the comparison; means for enabling selection of the one or more options from the displayed menu; and means for establishing a connection with a destination of the dialed number based on the selection of the one or more options.
An enhanced telephone system is provided. The telephone system comprises a database comprising one or more phone numbers and one or more menus corresponding to the phone numbers, wherein the menus comprises one or more options for selection; means for comparing the a received number of a received call to the phone numbers in the database; means for displaying a menu based on a result of the comparison; and means for enabling selection of the one or more options from the displayed menu.
A method for providing enhanced telephony is also provided. The method comprising identifying a number dialed from a telephone system; comparing the dialed number to one or more phone numbers stored in a database, wherein the database comprises one or more menus corresponding to the phone numbers, and wherein the menus comprises one or more options for selection; and displaying on the telephone system a menu from the database based on a result of the comparison.
Another aspect of the invention is to generate a database of visual menus. The database generation could be done by successive calling the IVR and combined with voice recognition. Calling the IVR systems can be done manually by operators that will listen to options of the IVR and enter these options into the database. In this manual mode, the operator will dial IVR numbers from a list and for each of them will follow all the options in several levels and in each level, enter the menu entries into the database. This can be done to many different IVR phone numbers, by one or multiple operators. The voice menu can be recorded to for analyzing in a different process or a different time.
Another aspect of the invention is to generate a database of visual menus by a computer system. Combination of hardware and software that is connected to phone system and automatically dials the IVR phone numbers, record the different options of the voice menu, analyze the voice menu and generate and enter the different entries into the database. The system will generate the voice tone that simulates the relevant touchtone of a phone number pressed. This process will be done in several levels until covering all the entries in all the levels of the specific IVR system. This process is done for all the IVR phone number in the list.
Additional alternative is to access the IVR internal database and download the menu. This approach requires the collaboration with the IVR maker and at least permission from the IVR owner. Having both a system could be build to access IVR using their maintenance port, which is often connected to the Internet. Accordingly, the system would access the IVR and once authorized by the IVR owner it will download the internal file representing the IVR menu, which could be called the IVR customization record. The downloaded file would then be converted to visual menu by utility that could be design according to the format, which could be provided by the IVR maker.
Another aspect of the invention is to provide updates to the visual menus stored in the device.
Another aspect of the invention is to provide the visual menu when the call is forwarded from one destination to another.
Another aspect of the invention is to provide visual menus on electronic devices with screens that are connected to Visuphone.
Additional aspect of the invention is an automatic learning of user choice and uses that for assisting the user in his future calls.
Having thus described the invention in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:
Illustrative embodiments of the invention now will be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the invention are shown. Indeed, the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like numbers refer to like elements throughout.
With reference to
For example, selection of option 204a presents an option 208a that plays an audible instruction, “press 1 for veg” and an option 210a that plays an audible instruction, “press 2 for non-veg” is played. Similarly, selecting option 208a or 210a presents or option 214a that plays an audible instruction, “press 1 for home delivery”, an option 216a that plays an audible instruction, “press 2 for take away”. Similarly, selection of option 206a presents an option 212a that plays an audible instruction, “press 1 to talk to an executive”.
Options 204a, 206a, 208a, 210a, 212a, 214a, and 216a are part of a main menu 218a. Main menu 218a can be repeated by selecting option 220a by caller 106. Caller 106 may repeat main menu 218a for example, in case of a mistake in selection. Therefore, caller 106 directly interacting with audible IVR menu 222a may be required to listen to all or various audible options before executing a desired action. However, the interaction is simplified by Visuphone 104, that presents a visual menu 222b to caller 106 corresponding to audible IVR menu 222a, as explained with reference to
As shown in
In an embodiment of the invention, visual menu 222b is displayed to caller 106 when a call is received at device 102. For example, a service provider may call to provide information about new services or account of caller 106. Further, caller 106 may be required to select various options based on his preferences. Visuphone 104b may detect the received number and correspondingly display a visual menu to the caller.
The graphics may be displayed for each node or a few nodes based on the usability of visual menu 222c. For example, for the node 208 can icon of a vegetable may be displayed to designate a vegetarian pizza, and for the node 214c of home delivery, an icon of house may be displayed. In an embodiment of the invention, visual menu 222c can be customized to display only the text, only the icons or both. Furthermore, caller 106 can suggest or use various icons based on his preferences.
In an embodiment of the invention, Visuphone 104b may provide a standard menu per group of similar audible IVR or destinations. With reference to
Device 102a includes a display 302 to output graphical information to caller 106. In an embodiment of the invention, display 302 may includes a touch sensitive screen. Therefore, caller 106 can provide inputs to device 102a by touching display 302 or by point and click using the ‘mouse’. Memory 306 of device 102a stores various programs, data and/or instructions that can be executed by Central Processing Unit (CPU) 304. Examples of memory include, but are not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a hard disk, and so forth. A person skilled in the art will appreciate that other types of computer-readable media which can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, digital video disks, and the like, may also be used by device 102a. Memory 306 may include Operating System (OS) (not shown) for device 102a to function. Further, memory 306 may include other applications 310 that enable the caller to communication with destinations. Examples of other applications 310 include, but are not limited to, Skype, Google Talk, Magic Jack, and so forth. Other applications 310 may be stored as software or firmware on device 102a. Further, memory 306 includes Visuphone 104 for presenting a visual menu corresponding to the audible IVR menu of destination as discussed with reference to
With reference to
In an exemplary instance, if caller dials a phone number of an IVR destination, then a visual menu corresponding to audible IVR menu of the destination is displayed on display 412. Similarly, if the caller receives a call from a phone number of destination, then a visual menu corresponding to audible IVR menu of destination is displayed on display 412. Thereafter, caller can interact with the visual menu to select options from the audible IVR menu. Visual menu 406 may be displayed before actual connection of device 102c to destinations. Therefore, caller can select a desired action from visual menu 406 before connecting to destinations. In an embodiment of the invention, visual menu 406 may be provided in real-time to caller. In an embodiment of the invention, visual menu 406 is provided a messaging service such as a Short Messaging Service (SMS). Therefore, destinations may provide customized visual menu 406 to caller 106. Visual menu 406 may be customized based on the profile of caller. In an embodiment of the invention, the profile may be generated based on access pattern of caller or the data capture by a hub connected to device 102c.
Caller can interact with visual menu 406 by pressing a desired button from keypad 320. For example, caller can press a ‘5’ key from keypad 320 to select a node 5 in visual menu 406. Further, caller can directly select the node 5 of visual menu 406 from display 412, in case of a touch sensitive screen. Depending on the complexity or size of destinations, visual menu 406 may have various nodes. Moreover, display area of display 412 may be limited or small. As a result, all the nodes of visual menu 406 may not be displayed together on display 412. In such a case, Visuphone is configured to allow caller to navigate by scrolling horizontally and/or vertically to view nodes on visual menu 406. Further, Visuphone may detect the capability of device 102a before displaying the visual menu. For example, in case device 102a is a basic mobile phone with limited functionality of the display screen. Therefore, Visuphone may display the visual menu in form of a simple list. Similarly, a list may be displayed in case of fixed line telephones. Moreover, in case device 102c includes a high capability screen, such as but not limited to an iPhone, then the visual menu is displayed in form of graphics.
Subsequently, after caller selects a desired action from visual menu 406, a connection is established between device 102c and destinations based on the selected option. In one embodiment, Visuphone is configured to detect and present an application or computer program available on device 102c.
Visuphone can be further configured to display an advertisement 408. Advertisement 408 may correspond to the type of services provided by the dialed destinations. For example, if destination dialed is a pizzeria, then advertisement 408 may include promotions or offers about a new pizza. Moreover, advertisement 408 may include promotions or offers from a third party or a competitor of the destination. Further, Visuphone may be coupled to an advertising database. The advertising database may include advertisements related to the phone numbers of the destinations. The advertising database may be stored at device 102c, the destinations, service providers or other third party servers. Further, the advertisements may be provided based on a profile of caller. For example, assuming that the caller calls a bank holding his saving account. Therefore, the advertisement displayed to the caller may be based on the location, address, account balance, type and volume of transactions, loans, purchases and so forth.
Visuphone may be configured to connect to an intended destination, when caller selects advertisement 408. Further, Visuphone displays visual menu 406 of the intended destination. In an embodiment, Visuphone stores the interactions of caller with visual menus. For example, Visuphone may automatically learn the numbers dialed or options selected from the menu. Moreover, the learned numbers or choices are associated with the dialed phone number of the destination. Therefore, the caller is assisted in his future calls. For example, when caller calls the destination again, then the actions that were performed in the last interaction are presented prominently to caller; or a previous sequence may be automatically performed. Further, the actions that are frequently performed are presented prominently to caller. For example, if caller dials a bank frequently to enquire about his account balance, then the options for selecting his account balance may be highlighted.
Device 102b includes a display interface 502 to connect to a display 512. Display interface 502 can be for example, a video adapter. Display 512 outputs graphical information to caller. In an embodiment of the invention, display 512 includes a touch sensitive screen. Therefore, caller 106 can provide inputs to device 102b by touching display 512 or by pointing with the mouse and click. Memory 506 of device 102b stores various programs, data and/or instructions that can be executed by Central Processing Unit (CPU) 504. Examples of memory include, but are not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a hard disk, and so forth. A person skilled in the art will appreciate that other types of computer-readable media which can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, digital video disks, and the like, may also be used by device 102b. Memory 506 may include Operating System (OS) (not shown) for device 102b to function. Further, memory 506 may include other applications 510 that enable caller 106 to communication with destinations 108a-n. Examples of other applications 510 include, but are not limited to, Skype, Google Talk, Magic Jack, and so forth. Other applications 510 may be stored as software or firmware on device 102b. Further, memory 506 includes Visuphone 104 for searching and presenting a visual menu corresponding to the audible IVR menu of a destination as discussed with reference to
With reference to
In an exemplary instance, if caller 106 dials a phone number of destination, then a visual menu corresponding to audible IVR menu of destination is displayed. Thereafter, caller can interact with the visual menu to select options and to transmit inputs for the audible IVR menu of the corresponding destination. Visual menu 604 could be displayed before actual connection of device 102b to destinations. Therefore, caller 106 can select a desired option from visual menu 604 before establishing a connection to the destination. Depending on the complexity or size of the destinations, visual menu 604 may have various nodes. For example, an organization with 50 departments may have more menu options or nodes than that of an organization with 10 departments. Further, the display area of display 512 may be limited. As a result, all the nodes of visual menu 604 may not be displayed together on display 512. In such a case, Visuphone 104 is configured to allow caller 106 to navigate by scrolling horizontally and/or vertically to view nodes on visual menu 604. Moreover, caller 106 can search for a desired option from the visual menu.
Subsequently, after caller 106 selects a desired option from visual menu 604, a connection is established between device 102b and a destination based on the selected action. In one embodiment, Visuphone is configured to detect and present applications suitable to caller for initiating the connection. For example, Visuphone may detect more than one VOIP applications present in device 102b and present them to caller 106 on display 512. Thereafter, caller can select an application to be used or initiate the connection in a default configuration. The default configuration can be for example, VOIP application 608 on which phone number 610 was dialed. In another embodiment, caller 610 may select a phone number displayed in applications such as a browser, messenger, or a mail client. Subsequently, Visuphone detects and presents applications suitable to caller for initiating the connection. Furthermore, Visuphone is configured to display visual menu 604 for the phone number selected from the applications.
Visuphone is further configured to display an advertisement 606. Advertisement 606 may correspond to the type of services provided by destinations. For example, if the destination is a bank, then advertisement 606 may include promotions or offers about new loans or schemes. Moreover, advertisement 606 may include promotions or offers from a third party or a competitor of destination. Visuphone may be configured to connect to intended destination, when caller selects advertisement 606. Further, Visuphone displays visual menu 606 of the intended destination. In an embodiment, Visuphone stores the interactions of caller with visual menus after a call to an IVR was made. Therefore, when caller calls the same destination again, then the options that were selected in the last interaction are presented prominently. Further, the options that are frequently selected can be presented prominently. For example, if caller dials a bank frequently to check his account balance, then the options for selecting his account balance may be highlighted. Additionally the information such his account number can be brought up to save effort for the user who can than just OK for that ‘auto fill’ to be dialed out to the IVR at the proper time.
With reference to
Visuphone detects and launches a VOIP application on device 102b. In an embodiment, in case more than one application is available on device 102, Visuphone selects a VOIP application preferred by caller. Moreover, Visuphone 104 may be configured to automatically login into the VOIP application. In an embodiment, caller 106 stores the login details for the VOIP application in Visuphone. Further, Visuphone displays a visual menu corresponding to audible IVR menu of the destination connected once click on the connect 706 tab. Therefore, caller can connect to the destination from web browser 702 automatically and may not be required to dial the phone number or provide a call-back information.
In an embodiment of the invention, Visuphone 104 may include a VOIP plug-in that monitors the outgoing calls made from the VOIP application. Therefore, the VOIP plug-in may search each dialed number in visual menu database 308. In case, the dialed number is found in visual menu database 308 and is associated with an IVR, then the VOIP plug-in may display the visual menu corresponding to the audible IVR menu of the dialed number.
Another embodiment of the invention allows the user to select the visual menu using car display like GPS display. Hands-free cell phone system is used in many cars as a separated device or as an integrated system in the car. These devices allow the user to talk with the cell phone without holding the cell phone in his hands. Some devices are using the car speakers for the phone call. In many cases, the hands-free system can use a display screen in the car like GPS screen or other display. Following voice menu while driving might not be the optimal way to use hands-free cell phone system. In some cases, selecting an option from a visual menu is preferred. While driving or stopping in red light, it might be easier to use larger display like the GPS display in the car. The display can present the visual menu and the user can select the option from the menu. The computing engine to support the visual menu could be embedded in the car GPS system or in another controller that have access to the car display. Once the system recognize a destination of a call to be an IVR it will access the database pull out the menu and display. Accordingly all the other Visuphone features could be incorporated.
Operating System 806 provides memory and environment required by Visuphone 104 and other applications 808 for functioning on device. Examples of Operating System 806 include, but are not limited to, Windows, Macintosh, Linux, Symbian, Andriod and so forth. Visuphone 104 may be implemented as a plug-in to other applications 808, such as Skype, Google Talk, web browser, mail client, and so forth. In an embodiment, Visuphone 104 may be implemented as a standalone application on device. Further, Visuphone 104 may be configured to execute as a background application. Therefore, caller may not be required to specifically launch Visuphone 104. Furthermore, Visuphone 104 may be implemented as a multi-threaded application. Therefore, visual menus of more than one destination may be displayed simultaneously on device.
When caller dials, selects or receives a phone number on the device, a detection module 902 of Visuphone 104 detects that a phone number has been dialed, selected or received. For example, detection module 902 may detect key presses or caller ID on device. Caller may use a VOIP application on device for dialing the phone number. Moreover, caller may use a mouse to a joystick to select or press icons of numbers displayed on the VOIP application. Further, detection module 902 is configured to identify the VOIP applications available on device and used by caller. Moreover, detection module 902 may detect the position co-ordinates of the VOIP application on a display of device. For example, in case device includes the Microsoft Windows OS, then the position co-ordinates of the VOIP application can be detected from the registry of the OS. Detection module 902 may be configured to store the position of number icons relative to position co-ordinates of various VOIP applications. Therefore, based on the co-ordinates of the position of the VOIP application, detection module 902 can detect the exact position of each number icon on the display of device. For example, if the co-ordinates of a top-left edge of the VOIP application is (X,Y) on the display, and the co-ordinates of an icon for number ‘1’ on VOIP application is (X1,Y1) relative to its top-left edge, then the exact co-ordinates of the icon for number ‘1’ may be calculated as (X+X1, Y+Y1) on the display. A person skilled in the art will appreciate that other types of mathematical operations can be applied to calculate the co-ordinates of the icons on the display of the device.
Detection module 902 may be configured to detect the co-ordinates of the cursor on the display of device. Further, detection module may be configured to detect the action events generated by the mouse or joystick, such as a click, a double-click, drag, select, scroll and so forth. Therefore, when caller selects or press a number on the VOIP application, detection module 902 may detect the number from the position of the cursor, the VOIP application and the number icon. In an embodiment, detection module 902 may be configured to store the last used co-ordinates of the VOIP application and number icons. Therefore, detection and/or calculation of the co-ordinates may not be required. Furthermore, detection module 902 may be configured to detect a connect button displayed on a web page of a browser on device as explained with reference to
The phone number detected by detection module 902 is used by a search module 904 of Visuphone. In an embodiment, detection module 902 may be configured to transfer each digit to search module 904 in real-time as clicked by caller. Search module 904 searches visual menu database for visual menu corresponding to the phone number. An exemplary visual menu is as explained above in conjunction with
The visual menu identified by a search module 904 is displayed on the display of device by display module 906 of Visuphone 104. Display module 906 identifies the position on the display where the visual menu is to be displayed. In an embodiment, the visual menu is displayed such that there is minimum overlap with the VOIP application from which the phone number was dialed or selected. Moreover, display module 906 identifies the size of the visual menu for display based on the characteristics of the display screen of device. Examples of characteristics of the display screen include, but are not limited to, a screen size, resolution, and so forth. Furthermore, in case the visual menu is not completely displayed on the display, then display module 906 may allow caller to navigate the visual menu by scrolling. Moreover, display module 906 may be configured to display other information received from search module 904.
Caller may interact with the visual menu or other information displayed on device. For example, caller may scroll through the visual menu, or select a node from the visual menu. Therefore, when caller selects a node from the visual menu, detection module 902 detects the selected node and communicates the selection to a connection module 908. Thereafter, connection module 908 may establish a connection between device and a destination based on the nodes selected by caller. Connection module 908 may be configured to detect communication systems available in device. For example, in a case, device is a phone not connected to the Internet, connection module 908 may detect that only a radio connection can be made. Otherwise, a most suitable or a connection preferred by caller can be made. In an embodiment, connection module 908 may allow caller 106 to select a VOIP application to establish the connection. In another embodiment, communication module 908 may launch a default VOIP application on the device 102. In yet another embodiment of the invention, connection module 908 can use a VOIP protocol stack defined by Visuphone to establish the connection.
Sometimes, a call of caller may be transferred from one point in the organization to another point within the same organization or to a completely different organization. For example, the call of caller with destination 108a may be transferred to destination 108b. However, destinations 108a and 108b may have different audible IVR menus. Connection module 908 is configured identify the transfer of call and to switch the visual menu of destination 108a with destination 108b. The switching of visual menus is explained in detail in conjunction with
Some organizations such as banks may require caller to present a voice input for the purpose of authentication. For example, caller may be required to voice out his name or an answer to a security question specified by caller to the bank. Furthermore, voice input may be required to accept or decline a transaction. Caller may record and store the voice responses for such authentications or questions alternatively the system can use synthesis voice. Therefore, when connection module 908 detects that a voice authentication is required, and then voice module 910 is used. Voice module 910 provides voice inputs on behalf of caller by using the responses recorded by caller. Subsequently, the connection or the transaction can be processed.
As discussed in conjunction with
In some cases, the audible IVR menu of destination may change. For example, the extension numbers of agents in banks may be changed due to addition of new agents. A person skilled in the art will appreciate that there can be other reasons for the audible IVR menu of a destination to be edited, amended or updated. Further, new organizations may be available that use audible IVR menus. The visual menus for these new organizations may not be available in visual menu database stored on device. Therefore, visual menu database may be required to be updated. In an embodiment, Visuphone may be updated to provide additional functionalities to caller. Update module 914 may be configured to update the visual menus stored in visual menu database of device. Moreover, update module 914 may be configured to update Visuphone. Update module 914 may receive the updated visual menus from the remote server on the network. The remote server is explained in detail in conjunction with
Visuphone may record the caller's selections or keystrokes for audible IVR menus by using customization module 916. The keystrokes may be some personal data of the caller such as his account number, customer number, and so forth. Visuphone can provide better support to caller by presenting the recorded keystrokes so that the caller can approve and sending them without entering them every time. Customization module 916 personalizes the generic visual menu by associating the keystrokes with it and storing in visual menu database 308. Alternatively, an additional set of standard may be defined for representing caller data. In this case, only the code indicating the type of required data is added to visual menu database 308. Visuphonecan than build a relatively small table in visual menu database 308, with the various personal data codes and the actual caller data as analyzed from the caller's keystrokes during his connection with destinations of the audible IVR menus.
Further, device 102 includes visual menu database 308. As discussed above, visual menu database 308 includes visual menus corresponding to audible IVR menus of destinations 108a-n. Moreover, visual menu database 308 may store other information such as profile of caller, voice response of caller, login details for a VOIP application, preferences of caller, ratings for visual menus, identity of visual menus and so forth. As discussed in conjunction with
In case, the audible IVR menu of a destination is changed, caller may not be able to connect to the destination by using Visuphone. Visuphone is configured to detect the error generated while establishing the connection. For example, caller may select a node in the visual menu that may not have a corresponding option available in audible IVR menu, or a connection not be established between device 102 and the destination. The error is detected by update module 914 of Visuphone. Subsequently, update module 914 sends an error report to remote server 1002. Remote server 1002 may check remote repository 1004 for updates related to the visual menu. Thereafter, in case any updates are available, remote server 1002 may send the updates to device 102 for performing the update. In an embodiment, visual menu database 308 may be checked and updated based on a pre-defined time interval by the device 102. In an embodiment, the error report may include the error generated and an Identity (ID) or version of the visual menu on which the error was generated. In case, the updates are not available in remote repository 1004, then an update of remote repository 1004 may be required. In an embodiment of the invention, remote repository 1004 is updated based on a pre-defined time interval. In another embodiment of the invention, the caller can rate the relevance or correctness of the visual menu from device 102. Therefore, remote repository 1004 can be updated based on a cumulative ratings received from callers and other users of the visual menu. The remote server 1002 can comprise a process of continuously scanning the IVRs 108a to 108n updating the remote repository 1004 with changes of various IVR menus and adding addition menu records for new IVRs. Also the remote server 1002 might get a ‘problem report’ from device 102 if caller identify problem between the menu as it is in the database 308 and the audible menu of a specific IVR. In such case a recheck process will be initiated to update the remote repository 1004 and the new information can be than offered to device 102 for download an update.
In an embodiment of the invention, visual menu database 308 may include other information and parameters related to the visual menus. The parameters related to the visual menus enable accessing, modifying or updating of the visual menus. Examples of parameters of visual menus include, but are not limited to, ID or version of the visual menus, destination phone numbers, and a last update timestamp. Furthermore, visual menu database 308 may include other information such as a profile, the calling history, or preferences of the caller. The calling history of a caller may include the numbers dialed or received, most frequent numbers dialed or received, most frequent nodes selected from visual menus. The profile of a caller may include, but is not limited to, the name, age, sex, address, phone number, profession, office address, recorded voice responses for visual menus, or other personal and professional details of the caller.
With reference to
As shown in
In an embodiment, destination 108b sends an identity (ID) or version of the audible IVR menu to a caller as shown by arrow 1106. The audible IVR menu ID is specific to the audible IVR menu of destination 108b. Subsequently, display module 906 of Visuphone 104 uses the audible IVR menu ID to display the corresponding visual menu. Further, a caller may select a node from the visual menu corresponding to destination 108b. Therefore, when a caller selects a node, a connection may be established with destination 108b. In an embodiment of the invention, connection between device 102 and destination 108a is disconnected after establishing a connection between device 102 and destination 108b. In another embodiment of the invention, connection between device 102 and destination 108a is maintained for complete communication session till the caller disconnects the call.
Another embodiment of the invention allow visual menu for calls made from a conventional home telephone.
Further, the connection to network 1220 is associated with a wide band Internet ‘smart’ modem 1206. Phone 1204 may be a regular phone, such as a landline phone or a cordless landline phone. Modem 1206 may be a Digital Subscriber Link (DSL) modem or a cable modem that connects the home device to the Internet and/or computer network. Modem 1206 is connected to a service provider, and can provide the home devices with telephone, Internet and television services. Modem 1206 may provide both wired and wireless connections. As shown with reference to
Once the connection with the destination has been established, ‘smart’ modem 1206 will continue to monitor the numbers dialed or received by phone 1204 to browse or advance the visual menu accordingly. Furthermore, the numbers dialed or received may be stored for future processing such as highlighting previous selections in the visual menu, providing customized visual menu and so forth. The Visual menu system comprising computer 1202 and Modem 1206 may incorporate additional enhancements as presented before such as automatic dialing of customer information. The automatic dialing may be achieved by using computer 1202 to initiate and execute such automatic dialing.
In another embodiment of the invention, a house television 1212 may be used to present the visual menu. In various houses modem 1206 decodes television signals and transfer it to a set-top box 1216 that provide signals to television 1212. The visual menu may be presented on a channel dedicated for IVR. Therefore, when phone 1204 is used to initiate a call, modem 1206 can detect it and present the visual menu corresponding to the dialed number on the designated channel of the television 1212. Further, all the options described before can be provided now using the screen of television 1212 for the visual menu. The caller selection can be done by using the simple home phone or alternatively using the TV 1212 set top box 1216 remote control. Further, television 1212 screen may be used to present the visual menu in a few alternatives ways. For example, a device provided by a company named RokuInc., allows streaming of content from the Internet to television. Most set-top boxes now have an Internet connection or telephone connections. Furthermore, various devices such as some Digital Versatile Disc (DVD) players, and video game players or controllers such as Xbox or Playstation, can be connected to the Internet. Each of those devices may allow ‘smart’ modem 1206 to provide a visual menu on the screens of television 1212.
In another embodiment of the invention a telephone connection may be established through an external telephone service by using a computer, as discussed with reference to
Another enhancement for such external service provider 1310 is to provide a ‘smart’ connect. In case of the ‘smart’ connect, the user can designate not just destination 1312, but a specific node of visual menu, such as node 212b as discussed with reference to
Additional alternatives to the invention are illustrated with reference to
At step 1502, Visuphone such as of device 102 detects a phone number dialed, selected or received by caller for destination. In an embodiment of the invention, the number is clicked according to the display of device 102. The number is detected by detection module 902 of Visuphone 104. Thereafter, search module 904 searches visual menu database 308 of device 102 for the phone number, at step 1504. Search module 904 searches for visual menu and other information corresponding to the phone number. Other information may include, for example, the caller profile, call history of the caller, advertisement associated with the phone number and so forth. In an embodiment of the invention, search module 904 searches visual menu database 308 in real-time. Therefore, the visual menu and other information may be searched with only a few digits of the phone number.
At step 1506, it is determined by search module 904 whether the visual menu and other information are available for the phone number in visual menu database 308. In case, the visual menu is available, then the process continues to step 1508. In case, the visual menu is not available, then device 102 may be connected to remote repository 1004 by update module 914, at step 1518 as shown with reference to
Further, at step 1506, once it been determined by the search module 904 that the visual menu for the destination is available in the visual menu database 308, an asynchrony request is sent to remote repository 1004, at step 1558. The request is sent to check whether a newer version of the menu with different content is available, at step 1560. Subsequently, if such version exists in remote repository 1004, then visual menu database 308 is updated accordingly, at step 1522. The process is then continues to step 1524.
In case, the visual menu is not available in remote repository 1004, then the process continues to step 1528. At step 1528, audible IVR menu selection in detected on device 102. The audible IVR menu selection may be determined based on Dual Tone Multi Frequency (DTMF) tones or keys pressed by the user of device 102. Thereafter, in case a selection is detected, then the dialed number may be detected as a possible destination number. The dialed number may be provided to remote repository 1004 at step 1530. Thereafter, the process continues to step 1526, where remote repository 1004 is updated for information.
At step 1524, it is determined by search module 904 if visual menu is available for the dialed number in updated visual menu database 308. In an embodiment, Visuphone detects the correctness of information based on the error received on connection to the IVR destination or behavior of the caller. In case, visual menu is available, then the process continues to step 1508. Otherwise, in case the visual menu is not available, then the process continues to step 1526, where remote repository 1004 is updated for information. In an embodiment, Visuphone 104 sends an error report to remote repository 1004 to initiate the update. The error report may include the error details of connection, behavior of the caller and other information required to update remote repository 1004. In another embodiment, the caller may provide ratings for the correctness of the visual menu and other information. Subsequently, the ratings are sent to remote repository 1004. In an embodiment of the invention, ratings from multiple devices are received at remote repository 1004. Thereafter, remote repository 1004 may be updated based on the ratings. In an embodiment of the invention, remote repository 1004 may be updated based on a pre-defined time interval. In another embodiment of the invention, remote repository 1004 is updated by an administrator of remote server 1102.
At step 1508, if the visual menu is available in the visual menu database, then the visual menu corresponding to the audible IVR menu of destination is displayed on device 102. In an embodiment of the invention, advertisements related to the type of destination are also displayed on device 102. At step 1510, inputs from the caller are detected on the visual menu. In an embodiment, the inputs include the nodes of the visual menu selected by the caller. In another embodiment, the inputs include the advertisement selected by the caller. Subsequently, device 102 is connected to destination based on the inputs provided by the caller, at step 1512. At step 1514, it is determined if the visual menu displayed on device 102 is correct. In case, the visual menu is not correct, then the process continues to step 1518. Thereafter, the process steps as discussed above are followed. However, in case the visual menu is correct, then the connection between device 102 and destination is maintained, at step 1516. Moreover, further inputs from the caller are received, to continue the communication till the caller or destination disconnects the connection.
The information stored in remote repository 1004 may be gathered from various destinations. For example, various destinations may be called to detect audio IVR menus and accordingly generate the information for remote repository 1004. With reference to
Device 1602 may include a memory 1604 that stores various programs, data and/or instructions that can be executed by a processor 1610. Examples of memory include, but are not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a hard disk, a computer-readable medium and so forth. A person skilled in the art will appreciate that other types of computer-readable media which can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, digital video disks, and the like, may also be used by device 1602. Memory 1604 may include Database Construction System (DCS) 1606 for gathering audible IVR menu information, which could be called the IVR customization record, from the destinations and store it in a records database 1608. In an embodiment of the invention DCS 1606 may be an application stored as software or firmware on device 1602.
DCS 1606 may include various modules or instructions that may be executed by processor 1610 for generating information in records database 1608, as explained in detail with reference to
Records database 1608, may include multiple records. Further each record may include an IVR identity code, multiple internal destinations and an activation code for each said internal destination. The IVR identity code may be for example, the phone number of the destinations. The activation code may be for example, a telephone key that should be dialed such as a dial tone associated with the phone number. The internal destination is usually an extension to which the call will be forward once the caller makes a choice, according to the provided menu, and apply the activation code that is usually a dial tone transmitted to the IVR from the Visuphone once the caller dials or selects a proper number or option. Each internal destination may further include another internal destination or extension that may be referred to as a sub-internal destination. Moreover, each sub-internal destination may be associated with a sub-record. Furthermore, the internal destinations may be associated with an icon code. As discussed above, the icons provide a convenient display for the user of a visual menu. In some audible IVR menus the activation code may be a voice command that could be activated by the caller by voicing his selection, or the Visuphone may transmit a pre-recorded voice command or a synthesized voice command when the caller makes a selection from the option menu of the visual menu provided by the Visuphone. Further, records database 1608 may include a record of the metadata or keywords associated with the various options in the menus. The metadata and/or keywords may be used by the Visuphone to enable the caller to search for a desired menu by providing keywords. In an embodiment of the invention records database 1608 is remote repository 1004.
DCA 1720 may include a Target List Module (TLM) 1722 that assigns the IVR destination or a target list to each instance of DCA 1720 for connecting and gathering information. The target list may include the IVR identity code, which can be as phone number or any type of information on how to connect to the IVR directly or indirectly. Further, the target list may include additional details such as internal destination. In an embodiment of the invention, the additional information of the internal destination may be implemented as one or more activation codes associate with the IVR identity code.
DCA 1720 may include an IVR Tracking Module (ITM) 1724 that tracks IVR content from a root location associated with the Target information assigned by TLM 1722. ITM 1724 constructs the full IVR content from a given IVR root.
ITM 1724 may include IVR Logic Module (ILM) 1726. ILM 1726 may detect the type of IVR of the destination. Typically, various types of audible IVR menus are implemented by destinations. The audible IVR menus may be categorized into various types, such as a simple IVR, IVR with audio response, IVR with additional data authentication and so forth. ILM 1726 detects the type of audible IVR menu, and accordingly the information is generated for records database 1608. Various categories of the audible IVR menu are explained in detail in conjunction with
ILM 1726 as part of its internal algorithm will drive the interaction sessions with the IVR. ILM 1726 may include data structure optimized with the tracked IVR menus to decide a right path or a next choice at any existing stage of the IVR tracking. The decisions made by ILM 1726 may be optimized as a mathematically directed graph tracking process. The tracking process may use an option from the audible IVR menu that corresponds to a “return to a previous menu” option of the audible IVR menu. As a result, the number of sessions required for tracking the audible IVR menu is reduced.
The process of IVR tracking may require multiple communications with the audible IVR menu to completely determine the content. Further, during the tracking process the content of the audible IVR menu may be discovered partially. Therefore, ITM 1724 may include a Tree Storage Module (TSM) 1728 to manage a temporary database record. Thereafter, when the process or a phase is complete, TSM 1728 may use Repository Connection Module (RCM) 1738 to submit the content as a batch of records to records database 1608. In case, a connection to records database 1608 is not available, then TSM 1728 may accumulate the information until a connection can be established.
Dialog Module 1730 of ITM 1724 interacts with the audible IVR menu. Further, dialog module 1730 manages the IVR requests and sends responses according to the decisions of ILM 1726. Further, dialog module 1730 may use a Speech Recognition Module (SRM) 1732 to interpret the audio of the IVR request to generate multiple records for records database 1608. In an embodiment of the invention, the audio is interpreted to generate text information. Moreover, SRM 1732 can provide a score to the text generated for each audio, according to the amount of guessing that is required for translating the IVR audio request. SRM 1732 may use a single grammar or a combination of dedicated grammars, for example, but limited to, a specific IVR service topic, IVR service sub topic, IVR stage, IVR location, the specific IVR, the hour of the day, and so forth. Furthermore, SRM 1732 may use multiple preset terms stored in the memory. Examples, of preset terms include, but not limited to, “yes”, “no”, name of the caller, and so forth. The text generated by SRM 1732 from speech recognition may be parsed by dialog module 1730 to enable ILM 1726 to select a next path or option.
Dialog module 1730 may be required to respond to the IVR requests during a tracking session. Dialog module 1730 may use a response module 1734 to generate the required response. Various audible IVR menus require a voice response from the caller. For example, the voice response may be required for the authentication of the caller. Response module 1734 may provide a recorded voice response to the audible IVR menu. For example, the voice response may be recorded voice phrase or preset of terms such as, but not limited to, “yes”, “no”, name of the caller, and so forth. Further, the voice response may be a synthesized voice response, generated by response module 1734. Therefore, response module 1734 may include a voice synthesizer. In this case, the activation code may be the recorded voice phrase and/or the synthesized voice phrase. Moreover, response module 1734 may include a voice decoder to recognize the voice. For example, the voice prompts generated by an audible IVR menu. In some other cases, the IVR menus may require a simple key tone (DTMF). The response module 1734 may include recorded tones or an internal module to generate the require tones.
Various destinations may provide a different audible IVR menu in the working hours and a different menu after working hours or during the holidays. DCA 1720 may detect the various times or time periods for which the audible IVR menus are presented in different mode. SRM 1732 may decode the voice from the audible IVR menu to recognize the IVR message. Further, ILM 1726 may analyze the response message for the periods and different operating mode. Therefore, ILM 1726 may call the destinations based on the recognized periods to generate records database 1608. Further, records database 1608 may include the time information for which a particular audible IVR menu is active. Accordingly, ITM 1724 may call the destinations multiple times based on the time information.
Various audible IVR menus include multi-level menus, as discussed with reference to
ITM 1724 may include components to connect to the audible IVR menu. As shown with reference to
Further, as shown with reference to
In an embodiment of the invention, the voice recognition for constructing records database 1608 is based on context-enhanced voice recognition. As the process of calling the destination is initiated by selecting a number from a list such as yellow pages, the voice recognition system would be provided file of potential menu terms, which could be farther narrowed base on knowledge of the business domain and the potential options such destinations may offer. Therefore, the process of voice recognition is greatly enhanced, when the recognition is done with respect to a relatively small number of choices. SRM 1732 in DCA 1720 may be pre-loaded with a small set of terms most likely used by the destination and, therefore, may be required to make the recognition out of the relatively small set of terms.
Further, the voice may be converted to a text format. In an embodiment of the invention, a voice-to-text application may be used to convert the audible instructions to text format. Subsequently, the information generated from the analysis of the first level is stored in records database 1608, at step 1806. The information may include the details about the sub-menu and the numbers to be dialed to access the sub-menu. For example, with reference to
In an embodiment of the invention, records database 1608 may be updated automatically based on a pre-defined update time interval. The update may be required to validate the correctness of information in the database. Moreover, records database 1608 may be updated based on ratings from users of Visuphone. For example, the caller may identify that a visual menu incorrect or incomplete, and may subsequently provide a rating to the visual menu. Further, an administrator or user of records database 1608 may update it manually.
Various audible IVR menus require audio commands from the caller instead of selecting options. DCS 1606 analyzes such IVRs to generate records database 1608. In an embodiment of the invention, a two-phase process may be applied to generate records database 1608. In the first phase a standard menu is generated for the IVR that may relate to a particular class of the destinations. A class can be a business class, for example, banks, airlines, hospitals and so forth. The first phase could be extended to cover as many domains as possible so that standard menus exist for most business classes of destinations. In the second phase, the IVR that requires a natural language voice command may be interrogated by repetitively applying the standard menus according to the class. Therefore, the relevance of the standard menu for the specific IVR is confirmed. In the process, a stored voice or synthesized voice could be use for each menu option. Thereafter, the menu may be stored in records database 1608 based on the confirmation. Some IVR menus may be require any or both of natural language commands and dial tones. In such a case, both options could be made available in the records database 1608, and eventually in the visual menu database for the caller at the time of use. As discussed with reference to
Additional variations of the categories include an IVR menu that provides a legal notice. For example, the audible IVR menu of a mortgage bank usually include an header stating that this is debt collector and anything stated during the call could be used for future collections. Other statements can be such as those that relate to the option to record the call and so forth. The statement may be registered and added to records database 1608, so that the legal statement can be presented with the visual menu. Further, additional statements may be added at the end of the statements regarding the last time when the IVR was verified.
Corresponding to these requests a display may be generated on the user's device, an exemplary illustration is as shown with reference to
In another embodiment of the invention, electronic yellow pages directory allows the dialing the number directly from the directory and further provides the visual menu of the destination. The caller can select the exact destination before dialing or follow the visual menu after dialing. For example, an airline company might have various option, menus and layers in the large organization. Selecting the exact department in the organization before dialing can save the user the time and overhead of listening to the menu and making decisions based on the voice menu. The yellow pages company can have a copy of the visual menu database or can be connected to a visual menu service in order to provide the menu to the user.
Alternatively an enhanced web base yellow page could be provided, wherein the caller can first choose the provider he requires to contact. Thereafter, if that destination provides an IVR, then the enhanced yellow page will use the visual menu database to present a visual menu on the web page. Moreover, the caller can click to choose the internal destination of that provider and the enhanced yellow page may accordingly initiate the call. The call could be made using the conventional telephone network or PSTN. In this case, the enhanced yellow page may need the caller's telephone number to perform the connection. Alternatively, the enhanced yellow page could use VOIP to connect the caller over the web to the IVR of the destination.
In some IVR systems, the caller may have to wait or hold on a queue of previous dialers until the specific department or agent is available. In another embodiment of the invention, the enhanced yellow page system will connect the caller only after the specific agent is available, without waiting in a long waiting line queue. The system can recognize that the waiting queue message of the specific department, and to connect the user only after the agent is answering. Therefore, the waiting time of the caller on the phone queue that sometimes may be very long, may be reduced. The system can park on the line for the waiting line on the specific entry in the menu, as soon as the agent is available, the caller gets a signal to start the conversation with the agent.
Additional advantage of the invention relates to callers who are more proficient in foreign language. Visuphone may provide the visual menu in multiple languages. A caller can than choose a language of his choice and download to his device database the menu in that language.
Yet another advantage of the invention relates to IVR that ask for voice commands. This IVR interface is for some user harder to use due to accent or other problems. The database could be provided with the option as been described before for the system to output voice command according to caller selection of the menu options.
Embodiments of the invention are described above with reference to block diagrams and schematic illustrations of methods and systems according to embodiments of the invention. It will be understood that each block of the diagrams and combinations of blocks in the diagrams can be implemented by computer program instructions. These computer program instructions may be loaded onto one or more general purpose computers, special purpose computers, or other programmable data processing translator to produce machines, such that the instructions which execute on the computers or other programmable data processing translator create means for implementing the functions specified in the block or blocks. Such computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means that implement the function specified in the block or blocks.
While the invention has been described in connection with what is presently considered to be the most practical and various embodiments, it is to be understood that the invention is not to be limited to the disclosed embodiments, but on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims. The invention has been described in the general context of computing devices, phone and computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, characters, components, data structures, etc., that perform particular tasks or implement particular abstract data types. A person skilled in the art will appreciate that the invention may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. Further, the invention may also be practiced in distributed computing worlds where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing world, program modules may be located in both local and remote memory storage devices.
This written description uses examples to disclose the invention, including the best mode, and also to enable any person skilled in the art to practice the invention, including making and using any devices or systems and performing any incorporated methods. The patentable scope the invention is defined in the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements with insubstantial differences from the literal languages of the claims.
1. A method for generating an Interactive Voice Response (IVR) database, the method comprising:
- a list of telephone numbers associated with plurality of destinations implementing IVR menus;
- communicating with said plurality of destinations for receiving their voice menu;
- wherein said communicating comprise calling at least one destination plurality of times, and
- recognizing said at least one destination voice menu and storing the IVR menu record in an IVR database set for storing said plurality of destinations IVR menus.
2. The method of claim 1, comprises associating at least one icon code with at least one of said IVR menu record.
3. The method of claim 1, comprises downloading one or more activation codes associated with said at least one of said IVR menus, and wherein said activation codes are associated with one or more internal destinations of said at least one of said IVR menus.
4. The method of claim 1, comprises performing said recognizing said at least one destination voice menu, at least two times for the same IVR destination and comparing the two voice menu record.
5. The method of claim 1, wherein said recognizing said at least one destination voice menu comprise the use of a speech recognition algorithm.
6. The method of claim 1, wherein a code related to a business domain of at least one of said destinations, is associated with a at least one of said IVR menu.
7. A method for construction of an Interactive Voice Response (IVR) database comprising:
- having a list of telephone numbers associated with a plurality of destinations implementing IVR menus, wherein the destinations are grouped based on one or more business domains;
- calling a telephone number from the list; and
- recognizing the voiced IVR menus to generate one or more records of the IVR database, wherein
- said calling a telephone number from the list comprise calling plurality of times the same telephone number.
8. The method of claim 7, comprises multiple preset terms recognizable by said speech recognition.
9. The method of claim 7, comprises generating a voice command.
10. The method of claim 7, comprises generating a plurality of calls at different times to a destination.
11. The method of claim 7, comprises:
- detecting a legal notice associated with the IVR menus;
- storing the legal notice in the memory; and
- associating the legal notice with an identification code of said IVR.
12. The method of claim 7, comprises characterizing said IVR as one or more preset IVR types.
13. The method of claim 7, comprises associating at least one icon code with an internal destination.
14. A method for managing an Interactive Voice Response database, the method comprising:
- dialing a telephone number corresponding to an IVR destination, the telephone number being dialed to receive an audio information corresponding to one or more options of an IVR menu associated with the IVR destination;
- generating one or more records based on the received audio information, the records being generated by using speech recognition; and
- storing the generated records in the Interactive Voice Response Database, wherein the telephone number being selected from a list of telephone numbers corresponding to a plurality of IVR destinations, and wherein each of the telephone numbers being dialed successively for storing records corresponding to each of the IVR menus related to the IVR destinations, thereby managing the Interactive Voice Response database.
15. The method of claim 14 further comprising analyzing the one or more options using speech recognition to determine one or more hierarchies corresponding to the IVR menu.
16. The method of claim 14 further comprising updating the Interactive Voice Response database by adding one or more properties corresponding to each IVR destination based on an informational database.
17. The method of claim 14, wherein the records comprise a business code associated with the IVR menu.
18. The method of claim 14, comprises said associating personal data of at least one caller with at least one of said telephone numbers.
19. The method of claim 14, further comprising:
- detecting a legal notice associated with the IVR menu; and
- storing the legal notice in the Interactive Voice Response database.
20. The method of claim 14, further comprising updating the Interactive Voice Response database by storing time information associated with each IVR menu.
|4653045||March 24, 1987||Stanley et al.|
|4736405||April 5, 1988||Akiyama|
|4897866||January 30, 1990||Majmudar et al.|
|5006987||April 9, 1991||Harles|
|5007429||April 16, 1991||Treatch et al.|
|5027400||June 25, 1991||Baji et al.|
|5086385||February 4, 1992||Launey et al.|
|5144548||September 1, 1992||Salandro|
|5265014||November 23, 1993||Haddock et al.|
|5294229||March 15, 1994||Hartzell et al.|
|5335276||August 2, 1994||Thompson et al.|
|5416831||May 16, 1995||Chewning, III et al.|
|5417575||May 23, 1995||McTaggart|
|5422809||June 6, 1995||Griffin et al.|
|5465213||November 7, 1995||Ross|
|5465401||November 7, 1995||Thompson|
|5475399||December 12, 1995||Borsuk|
|5499330||March 12, 1996||Lucas et al.|
|5519809||May 21, 1996||Husseiny et al.|
|5533102||July 2, 1996||Robinson et al.|
|5550746||August 27, 1996||Jacobs|
|5572581||November 5, 1996||Sattar et al.|
|5585858||December 17, 1996||Harper et al.|
|5586235||December 17, 1996||Kauffman|
|5588044||December 24, 1996||Lofgren et al.|
|5592538||January 7, 1997||Kosowsky et al.|
|5606361||February 25, 1997||Davidsohn et al.|
|5633909||May 27, 1997||Fitch|
|5633916||May 27, 1997||Goldhagen et al.|
|5657221||August 12, 1997||Warman et al.|
|5689648||November 18, 1997||Diaz et al.|
|5724412||March 3, 1998||Srinivasan|
|5739814||April 14, 1998||Ohara et al.|
|5740549||April 1998||Reilly et al.|
|5768142||June 16, 1998||Jacobs|
|5790652||August 4, 1998||Gulley et al.|
|5794205||August 11, 1998||Walters et al.|
|5796806||August 18, 1998||Birckbichler|
|5802283||September 1, 1998||Grady et al.|
|5802526||September 1, 1998||Fawcett et al.|
|5807336||September 15, 1998||Russo et al.|
|5819225||October 6, 1998||Eastwood et al.|
|5822404||October 13, 1998||Cave|
|5822405||October 13, 1998||Astarabadi|
|5838682||November 17, 1998||Dekelbaum et al.|
|5838775||November 17, 1998||Montalbano|
|5867816||February 2, 1999||Nussbaum|
|5873068||February 16, 1999||Beaumont et al.|
|5885083||March 23, 1999||Ferrell|
|5885245||March 23, 1999||Lynch et al.|
|5890123||March 30, 1999||Brown et al.|
|5892813||April 6, 1999||Morin et al.|
|5907793||May 25, 1999||Reams|
|5912952||June 15, 1999||Brendzel|
|5913195||June 15, 1999||Weeren et al.|
|5920477||July 6, 1999||Hoffberg et al.|
|5937040||August 10, 1999||Wrede et al.|
|5940488||August 17, 1999||DeGrazia et al.|
|5948040||September 7, 1999||DeLorme et al.|
|5956034||September 21, 1999||Sachs et al.|
|5982875||November 9, 1999||Lieben et al.|
|5987103||November 16, 1999||Martino|
|6009398||December 28, 1999||Mueller et al.|
|6014428||January 11, 2000||Wolf|
|6020915||February 1, 2000||Bruno et al.|
|6049779||April 11, 2000||Berkson|
|6055513||April 25, 2000||Katz et al.|
|6062863||May 16, 2000||Kirksey et al.|
|6088429||July 11, 2000||Garcia|
|6088712||July 11, 2000||Huang et al.|
|6091805||July 18, 2000||Watson|
|6091956||July 18, 2000||Hollenberg|
|6104790||August 15, 2000||Narayanaswami|
|6144848||November 7, 2000||Walsh et al.|
|6148065||November 14, 2000||Katz|
|6169734||January 2, 2001||Wilson|
|6212547||April 3, 2001||Ludwig et al.|
|6228921||May 8, 2001||Kasemann et al.|
|6229694||May 8, 2001||Kono|
|6230197||May 8, 2001||Beck et al.|
|6259444||July 10, 2001||Palmer et al.|
|6263064||July 17, 2001||O'Neal et al.|
|6273726||August 14, 2001||Kirksey et al.|
|6321198||November 20, 2001||Hank et al.|
|6335678||January 1, 2002||Heutschi|
|6366650||April 2, 2002||Rhie et al.|
|6373817||April 16, 2002||Kung et al.|
|6400807||June 4, 2002||Hewitt et al.|
|6405033||June 11, 2002||Kennedy, III et al.|
|6408301||June 18, 2002||Patton et al.|
|6427063||July 30, 2002||Cook et al.|
|6445694||September 3, 2002||Swartz|
|6449595||September 10, 2002||Arslan et al.|
|6456706||September 24, 2002||Blood et al.|
|6460057||October 1, 2002||Butler et al.|
|6463145||October 8, 2002||O'Neal et al.|
|6482156||November 19, 2002||Iliff|
|6505146||January 7, 2003||Blackmer|
|6510411||January 21, 2003||Norton et al.|
|6529500||March 4, 2003||Pandharipande|
|6560320||May 6, 2003||Paleiov et al.|
|6603840||August 5, 2003||Fellingham et al.|
|6606611||August 12, 2003||Khan|
|6606741||August 12, 2003||Kojima et al.|
|6636835||October 21, 2003||Ragsdale et al.|
|6653930||November 25, 2003||Bonomo et al.|
|6658389||December 2, 2003||Alpdemir|
|6700972||March 2, 2004||McHugh et al.|
|6705869||March 16, 2004||Schwartz|
|6714519||March 30, 2004||Luzzatti et al.|
|6731625||May 4, 2004||Eastep et al.|
|6754181||June 22, 2004||Elliott et al.|
|6754332||June 22, 2004||Kneipp et al.|
|6788770||September 7, 2004||Cook et al.|
|6791583||September 14, 2004||Tang et al.|
|6816580||November 9, 2004||Timmins|
|6820037||November 16, 2004||Simon|
|6820062||November 16, 2004||Gupta et al.|
|6826194||November 30, 2004||Vered et al.|
|6829368||December 7, 2004||Meyer et al.|
|6856673||February 15, 2005||Banks et al.|
|6862713||March 1, 2005||Kraft et al.|
|6865268||March 8, 2005||Matthews et al.|
|6885737||April 26, 2005||Gao et al.|
|6889195||May 3, 2005||Strandberg|
|6920205||July 19, 2005||Hahn et al.|
|6920425||July 19, 2005||Will et al.|
|6920431||July 19, 2005||Showghi et al.|
|6922466||July 26, 2005||Peterson et al.|
|6937705||August 30, 2005||Godfrey et al.|
|6968506||November 22, 2005||Yacovone et al.|
|6990455||January 24, 2006||Vozick|
|7020609||March 28, 2006||Thrift et al.|
|7027990||April 11, 2006||Sussman|
|7036128||April 25, 2006||Julia et al.|
|7039589||May 2, 2006||Whitham|
|7047196||May 16, 2006||Calderone et al.|
|7065188||June 20, 2006||Mei et al.|
|7068643||June 27, 2006||Hammond|
|7092738||August 15, 2006||Creamer et al.|
|7092888||August 15, 2006||McCarthy et al.|
|7100118||August 29, 2006||Klask|
|7130391||October 31, 2006||Janakiraman et al.|
|7133515||November 7, 2006||Cook|
|7136480||November 14, 2006||Mason|
|7139591||November 21, 2006||Callaghan et al.|
|7145902||December 5, 2006||Schindler et al.|
|7146321||December 5, 2006||Cyr et al.|
|7149549||December 12, 2006||Ortiz et al.|
|7159008||January 2, 2007||Wies et al.|
|7177814||February 13, 2007||Gong et al.|
|7180889||February 20, 2007||Kung et al.|
|7180985||February 20, 2007||Colson et al.|
|7181401||February 20, 2007||Johnson et al.|
|7181502||February 20, 2007||Incertis|
|7188352||March 6, 2007||Nathan et al.|
|7203517||April 10, 2007||Shimoda et al.|
|7206745||April 17, 2007||Sarukkai et al.|
|7206809||April 17, 2007||Ludwig et al.|
|7209124||April 24, 2007||Hunt et al.|
|7213061||May 1, 2007||Hite et al|
|7215743||May 8, 2007||Creamer et al.|
|7216348||May 8, 2007||deCarmo|
|7225409||May 29, 2007||Schnarel et al.|
|7225455||May 29, 2007||Bennington et al.|
|7228492||June 5, 2007||Graham|
|7231636||June 12, 2007||Evans|
|7231656||June 12, 2007||Nathan|
|7240006||July 3, 2007||Brocious et al.|
|7240289||July 3, 2007||Naughton et al.|
|7246063||July 17, 2007||James et al.|
|7248885||July 24, 2007||Benco et al.|
|7250939||July 31, 2007||Lira|
|7254227||August 7, 2007||Mumick et al.|
|7260537||August 21, 2007||Creamer et al.|
|7265861||September 4, 2007||Ranalli et al.|
|7266185||September 4, 2007||Trandal et al.|
|7266186||September 4, 2007||Henderson|
|7266499||September 4, 2007||Surace et al.|
|7272222||September 18, 2007||Joseph et al.|
|7272497||September 18, 2007||Koshiji et al.|
|7277854||October 2, 2007||Bennett et al.|
|7280097||October 9, 2007||Chen et al.|
|7280646||October 9, 2007||Urban et al.|
|7280651||October 9, 2007||Anderson|
|7286990||October 23, 2007||Edmonds et al.|
|7289608||October 30, 2007||Kumhyr|
|7289904||October 30, 2007||Uyeki|
|7299405||November 20, 2007||Lee et al.|
|7303121||December 4, 2007||Martinez|
|7319477||January 15, 2008||Katz|
|7324947||January 29, 2008||Jordan et al.|
|7328239||February 5, 2008||Berberian et al.|
|7330890||February 12, 2008||Partovi et al.|
|7353016||April 1, 2008||Roundtree et al.|
|7392193||June 24, 2008||Mault|
|7398215||July 8, 2008||Mesbah et al.|
|7406413||July 29, 2008||Geppert et al.|
|7412533||August 12, 2008||Johnson et al.|
|7433452||October 7, 2008||Taylor et al.|
|7440898||October 21, 2008||Eberle et al.|
|7450112||November 11, 2008||Shneidman|
|7460652||December 2, 2008||Chang|
|7466803||December 16, 2008||Burg et al.|
|7492883||February 17, 2009||Kumhyr|
|7515695||April 7, 2009||Chan et al.|
|7539480||May 26, 2009||Fieldhouse et al.|
|7539484||May 26, 2009||Roundtree|
|7546143||June 9, 2009||Nelson et al.|
|7577664||August 18, 2009||Malik|
|7584249||September 1, 2009||Mummick et al.|
|7606741||October 20, 2009||King et al.|
|7646858||January 12, 2010||Salafia et al.|
|7693720||April 6, 2010||Kennewick et al.|
|7720091||May 18, 2010||Faber et al.|
|7729490||June 1, 2010||Hemm et al.|
|7757173||July 13, 2010||Beaman|
|7809376||October 5, 2010||Letourneau et al.|
|7813485||October 12, 2010||Yin et al.|
|7843899||November 30, 2010||Burritt|
|7864944||January 4, 2011||Khouri et al.|
|7904516||March 8, 2011||Chern|
|7908381||March 15, 2011||Koch et al.|
|7966188||June 21, 2011||Ativanichayaphong et al.|
|7991125||August 2, 2011||Ryals et al.|
|8000454||August 16, 2011||Or-Bach et al.|
|8023624||September 20, 2011||Kargman et al.|
|8036347||October 11, 2011||Kanade|
|8054952||November 8, 2011||Or-Bach et al.|
|8155280||April 10, 2012||Or-Bach et al.|
|8160215||April 17, 2012||Or-Bach et al.|
|8223931||July 17, 2012||Lavian et al.|
|8345835||January 1, 2013||Or-Bach et al.|
|8406388||March 26, 2013||Or-Bach et al.|
|8537989||September 17, 2013||Lavian et al.|
|8548131||October 1, 2013||Lavian et al.|
|8548135||October 1, 2013||Lavian et al.|
|8553859||October 8, 2013||Lavian et al.|
|8566419||October 22, 2013||Purdy et al.|
|8572303||October 29, 2013||Lavian et al.|
|8594280||November 26, 2013||Or-Bach et al.|
|8625756||January 7, 2014||Lavian et al.|
|20020055844||May 9, 2002||L'Esperance et al.|
|20020147986||October 10, 2002||Michael et al.|
|20030005126||January 2, 2003||Schwartz et al.|
|20030007625||January 9, 2003||Pines et al.|
|20030033382||February 13, 2003||Bogolea et al.|
|20030074198||April 17, 2003||Sussman|
|20030112931||June 19, 2003||Brown et al.|
|20030225682||December 4, 2003||Montemer|
|20040034561||February 19, 2004||Smith|
|20040121814||June 24, 2004||Creamer et al.|
|20040122941||June 24, 2004||Creamer et al.|
|20040198316||October 7, 2004||Johnson|
|20040204116||October 14, 2004||Ben Efraim et al.|
|20050004977||January 6, 2005||Roberts et al.|
|20050055310||March 10, 2005||Drewett et al.|
|20060203977||September 14, 2006||Erhart et al.|
|20060239422||October 26, 2006||Rinaldo et al.|
|20060259424||November 16, 2006||Turcotte et al.|
|20060262921||November 23, 2006||Eppel et al.|
|20060285662||December 21, 2006||Yin et al.|
|20070026852||February 1, 2007||Logan et al.|
|20070032247||February 8, 2007||Shaffer et al.|
|20070038513||February 15, 2007||Flax et al.|
|20070094109||April 26, 2007||Perry|
|20070123223||May 31, 2007||Letourneau et al.|
|20070239537||October 11, 2007||Protheroe et al.|
|20070243887||October 18, 2007||Bandhole et al.|
|20070298776||December 27, 2007||Arlene|
|20080066015||March 13, 2008||Blankenhorn|
|20080095330||April 24, 2008||Jin et al.|
|20080165948||July 10, 2008||Ryals et al.|
|20080226042||September 18, 2008||Singh|
|20080240374||October 2, 2008||Conway et al.|
|20080250334||October 9, 2008||Price|
|20090041215||February 12, 2009||Schmitt et al.|
|20090116414||May 7, 2009||Or et al.|
|20090136014||May 28, 2009||Bigue et al.|
|20090154666||June 18, 2009||Rios et al.|
|20090154686||June 18, 2009||Purdy et al.|
|20090202050||August 13, 2009||Berger et al.|
|20090207980||August 20, 2009||Berger et al.|
|20090207996||August 20, 2009||Berger et al.|
|20090225788||September 10, 2009||Kephart et al.|
|20090228908||September 10, 2009||Margis et al.|
|20090276441||November 5, 2009||Malik|
|20090276708||November 5, 2009||Smith et al.|
|20090280863||November 12, 2009||Shin et al.|
|20090285380||November 19, 2009||Chen et al.|
|20100007028||January 14, 2010||Fachmann et al.|
|20100021030||January 28, 2010||Collins et al.|
|20100049654||February 25, 2010||Pilo et al.|
|20100087175||April 8, 2010||Roundtree|
|20100100377||April 22, 2010||Madhavapeddi et al.|
|20100166158||July 1, 2010||Costello et al.|
|20100172481||July 8, 2010||Canu et al.|
|20100189250||July 29, 2010||Williams et al.|
|20110009096||January 13, 2011||Rotsztein et al.|
|20110014952||January 20, 2011||Minton|
|20110060683||March 10, 2011||Salmon Rock et al.|
|20110091021||April 21, 2011||Adkar et al.|
|20110099116||April 28, 2011||Gabel|
|20110225330||September 15, 2011||Lavian et al.|
|20110276408||November 10, 2011||Toole|
|20120063574||March 15, 2012||Or-Bach et al.|
|20130022181||January 24, 2013||Or-Bach et al.|
|20130022183||January 24, 2013||Or-Bach et al.|
|20130022191||January 24, 2013||Or-Bach et al.|
- Yin, M. and Zhai, S., “The Benefits of Augmenting Telephone Voice Menu Navigation with Visual Browsing and Search,” CHI'06 Proceedings of the SIGCHI conference on Human Factors in computing systems: pp. 319-328, ACM, Montreal, Canada (Apr. 2006).
- Damhuis, M., et al., “A Multimodal Consumer Information Server with IVR Menu,” 2nd IEEE Workshop on Interactive Voice Technology for Telecommunications Applications (IVTTA94): pp. 73-76, Kyoto, Japan (Sep. 1994).
- Shah, S.AA., et al., “Interactive Voice Response with Pattern Recognition Based on Artificial Neural Network Approach,” International Conference on Emerging Technologies: pp. 249-252, (Nov. 2007).
- Trihandoyo, A., et al., “A real-time speech recognition architecture for a multi-channel interactive voice response system,” International Conference on Acoustics, Speech, and Signal Processing vol. 4: pp. 2687-2690,(1995).
- Hattori, S., et al., “A multimedia intelligent message communication system for distributed coordination environments,” Electronics & Communications in Japan, Part I—Communications, vol. 76, No. 1, pp. 11-23 (1993).
- Patent abstracts of Japan, vol. 097, No. 001, Jan. 31, 1997 & JP 08 242307 A (Canon Inc), Sep. 17, 1996.
- Kalva, H., et al., “Delivering Object-Based Audio-Visual Services,” IEEE Transactions on Consumer Electronics, vol. 45, No. 4, pp. 1108-1111, (1999).
- Schmandt, “Phoneshell: the telephone as computer terminal,” Proceedings of first ACM International Conference on Multimedia, Anaheim, CA, US, pp. 373-381, (1993).
- Himberg, J., et al., “Time Series Segmentation for Context Recognition in Mobile Devices”, IEEE, 203-210, (2001).
- Chris Schmandt and Stephen Casner, “Phonetool: Integrating Telephones and Workstations,” IEEE Communication Society, Nov. 27-30, pp. 0970-0974, (1989).
- Basinger, R. G., et al., “Calling Card Service—Overall Description and Operational Characteristics”, The Bell System Technical Journal, (1982).
- Cadiz et al. “Designing and Deploying an Information Awareness interface” CSCW'02, Nov. 2002, ACM, pp. 314-323.
- Corcoran et al. disclose “User interface technologies for home appliances and networks”, IEEE Trans. Consumer Elect.; pp. 679-685, (1998).
- Nancy Friedrich, “Graphical-User-Interface Module Eases Integration,” Wireless Systems Design, Oct. 2004, 1 page.
- Balachandran, R., et al., “Dialog System for Mixed Initiative One-Turn Address entry and Error Recovery,” Proceedings of SIGDIAL 2009, the 10th Annual Meeting of the Special Interest Group in Discourse and Dialogue, pp. 152-155, Queen Mary University of London, Association of Computational Logistics, (2009).
International Classification: H04M 11/06 (20060101); G06F 15/16 (20060101); G06Q 30/00 (20120101); G10L 15/06 (20130101);