WO2014063304A1 - Call center direct access - Google Patents
Call center direct access Download PDFInfo
- Publication number
- WO2014063304A1 WO2014063304A1 PCT/CN2012/083371 CN2012083371W WO2014063304A1 WO 2014063304 A1 WO2014063304 A1 WO 2014063304A1 CN 2012083371 W CN2012083371 W CN 2012083371W WO 2014063304 A1 WO2014063304 A1 WO 2014063304A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- call center
- map
- mobile device
- hierarchy map
- hierarchy
- 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.)
- Ceased
Links
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/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/5175—Call or contact centers supervision arrangements
-
- 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/5166—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing in combination with interactive voice response systems or voice portals, e.g. as front-ends
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72484—User interfaces specially adapted for cordless or mobile telephones wherein functions are triggered by incoming communication events
-
- 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
- H04W76/00—Connection management
- H04W76/10—Connection setup
-
- 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/252—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 voice mode is enhanced with visual information
Definitions
- a headend of a call center system sends a user a visual hierarchy map upon their first request.
- a client application residing on a user's device loads the hierarchy map with corresponding instructions on a screen and monitors a user's input.
- a user browses the hierarchy map and locates a final number sequence they would like to dial, and selects the specific leaf node of the hierarchy tree for that number sequence.
- the dialing instructions are sent to a backend of the call center system, and a communication circuit is constructed accordingly. Meanwhile, the number is stated on the headend for optimizing the rendering of the hierarchy map.
- the hierarchy map is arranged according to the dialing count, i.e., the more the number is dialed, the higher it will be located in each level of the hierarchy map.
- FIG. 1 is an example of a call center system and its subsystems.
- FIG. 2 is an example of a user interface with graphics on a client side application residing on a user's device.
- FIG. 3 is an example data structure that resides on a statistics server.
- FIG. 4 is an example call center system residing on a mobile device.
- a call center call centers can be from a service provider and/or directly from a business, etc.
- the user's device automatically interacts with the call center at the appropriate point.
- This technique has many advantages over the traditional call center voice hierarchy.
- a user In the traditional call center, a user must listen to menu functions of all the keys one by one in a single step before they can determine which key they should press. This is very time consuming and requires the user to start the menu listing program over if they do not hear the appropriate function the first time. Voice prompting is different from text or picture prompting.
- the voice prompting can cause errors in dialing, especially in noisy environment.
- the conventional methods are very tedious and time consuming, costing the user a lot of time and money, especially when they travelling abroad where phone rates are typically at a premium.
- the instruction or menu hierarchy always prompts the user in the same sequence. It cannot modify the sequence unless the sequence is adjusted manually on the headend side - which is very cumbersome.
- a call center system 100 there are five main subsystems including a mobile device 102, a call center exchange 104, a hierarchy map server 106, a statistics server 108 and a call center direct line 110.
- a user launches a call request 112 to the call center exchange 104, it will request hierarchy map 114 from the hierarchy map server 106.
- the hierarchy map server 106 gets statistical information 116 from the statistics server 108.
- the hierarchy map server 106 On the hierarchy map server 106, it generates a hierarchy map 118 according to the statistical information 120, and then returns the hierarchy map 122 to the call center exchange 104, and finally 124 to the mobile device 102.
- the user can then select a specific leaf node in the hierarchy map 126, and send a call request 128 to the call center direct line 110. Then connection between mobile device 102 and the call center direct line 110 is then constructed 130, and the user can directly communicate with the call center direct line 110 until they end the call 132 and close the connection 134.
- the call center direct line 110 then updates the statistics information 136 to statistical serverl08.
- FIG. 2 illustrates an example of a user interface 200 with graphics on a client side application residing on a user's device.
- an end user can zoom in 202 and out 204 by selecting a menu item, and/or directly using their fingers on a screen to zoom in and out on a whole hierarchy map 206.
- a user Once a user is familiar with the hierarchy map 206, they can also directly move their finger to a specific leaf node, e.g., the lowest layer node 208 in the hierarchy map 206.
- Hint information 210 pops up prompting a specific usage message relating to a direct line number. The user can then directly select this menu item 208 to get a connection with a call center direct line.
- the numbers are arranged according to the Arabic number sequence. In other instances, the numbers on each layer can be placed according to statistics information, which is discussed infra.
- FIG. 3 An example data structure 300 of one instance that resides on a statistics server is shown in FIG. 3.
- a hierarchy map is generated according to the following data structure.
- the top layer is the call center exchange number from the table “CallCenterExchange” 302, and then the numbers are retrieved from the table “Number” 306 according to their layer_id, e.g., one layer by one layer.
- the numbers are lined up according to a descent sequence calculated by a field "count" in table "Number” 306.
- a mobile device 402 comprises a mobile device interface 404 and a display 406.
- the interface 404 and the display 406 are the same mechanical structure (e.g., a touch screen, etc.).
- the display 406 is separate from a user input interface 404 such as a keyboard, mouse and the like.
- a map processor 408 resides on the mobile device 402 and interacts with the mobile device interface 404 and the display 406.
- a user enters a call center number 410 into the mobile device interface 404. This can be done by directly entering keystrokes on a keypad, via a touch screen and/or by selecting a number from a contact list to command the mobile device to dial the call center number 410.
- the map processor 408 can receive the dialed call center number 410 at the time of dialing to prepare it for receiving a call center hierarchy map 412. In other instances, the map processor 408 does not receive the call center number 410 at the time of dialing but monitors communication means of the mobile device for incoming hierarchy maps. In either case, when the map processor 408 receives the call center hierarchy map 412, it processes the map information, if necessary, and sends it to the display 406 of the mobile device 402. The user is then presented with the call center hierarchy map 412 and can select which node of the hierarchy they desire to contact. This user interaction with the hierarchy map 414, whether via the mobile device interface 404 and/or via the display 406, is then forwarded to the map processor 408. The map processor 408 then determines a desired call center connection 416 and transmits this information via a communication means of the mobile device 402 to establish a direct connection for the user.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Business, Economics & Management (AREA)
- Marketing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Human Computer Interaction (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Abstract
A map processor residing on a mobile device displays a call center hierarchy map based, in part, on a dialed call center number. User interactions with the map are then processed by the map processor to determine a desired call center connection. This information is used by the map processor to establish a direct connection with the desired node of the call center hierarchy map. In other instances, the mobile device interacts with a call center exchange, hierarchy map server, statistical server and a call center direct line to facilitate in providing a call center hierarchy map and a direct connection.
Description
CALL CENTER DIRECT ACCESS
BACKGROUND
[0001] Conventional auto-answer call centers including e-commerce, credit card, etc. have hierarchical instructions requiring a user to input a response to each prompt of the call center. The navigation process to the final target dialing number is time consuming and boring. For those people who travel abroad and their mobile phones use roaming service, this kind of navigation incurs extra expenses and wastes time.
SUMMARY
[0002] A headend of a call center system sends a user a visual hierarchy map upon their first request. A client application residing on a user's device loads the hierarchy map with corresponding instructions on a screen and monitors a user's input. A user browses the hierarchy map and locates a final number sequence they would like to dial, and selects the specific leaf node of the hierarchy tree for that number sequence. The dialing instructions are sent to a backend of the call center system, and a communication circuit is constructed accordingly. Meanwhile, the number is stated on the headend for optimizing the rendering of the hierarchy map. For subsequent operations, the hierarchy map is arranged according to the dialing count, i.e., the more the number is dialed, the higher it will be located in each level of the hierarchy map.
[0003] The above presents a simplified summary of the subject matter in order to provide a basic understanding of some aspects of subject matter embodiments. This summary is not an extensive overview of the subject matter. It is not intended to identify key/critical elements of the embodiments or to delineate the scope of the subject matter. Its sole purpose is to present some concepts of the subject matter in a simplified form as a prelude to the more detailed description that is presented later.
[0004] To the accomplishment of the foregoing and related ends, certain illustrative aspects of embodiments are described herein in connection with the following description and the annexed drawings. These aspects are indicative, however, of but a few of the various ways in which the principles of the subject
matter can be employed, and the subject matter is intended to include all such aspects and their equivalents. Other advantages and novel features of the subject matter can become apparent from the following detailed description when considered in conjunction with the drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
[0005] FIG. 1 is an example of a call center system and its subsystems.
[0006] FIG. 2 is an example of a user interface with graphics on a client side application residing on a user's device.
[0007] FIG. 3 is an example data structure that resides on a statistics server.
[0008] FIG. 4 is an example call center system residing on a mobile device.
DETAILED DESCRIPTION
[0009] The subject matter is now described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the subject matter. It can be evident, however, that subject matter embodiments can be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to facilitate describing the embodiments.
[0010] A message, including an instruction hierarchy, is sent to a user's device (landline, mobile device, television, monitor, etc.) after the user calls a call center (call centers can be from a service provider and/or directly from a business, etc.). Once the user selects a menu item in a call menu hierarchy, the user's device automatically interacts with the call center at the appropriate point. This technique has many advantages over the traditional call center voice hierarchy. In the traditional call center, a user must listen to menu functions of all the keys one by one in a single step before they can determine which key they should press. This is very time consuming and requires the user to start the menu listing program over if they do not hear the appropriate function the first time. Voice prompting is different from text or picture prompting. The voice prompting can cause errors in dialing, especially in noisy environment. The conventional methods are very tedious and time consuming, costing the user a lot of time and money, especially when they travelling abroad
where phone rates are typically at a premium. With these types of conventional methods, the instruction or menu hierarchy always prompts the user in the same sequence. It cannot modify the sequence unless the sequence is adjusted manually on the headend side - which is very cumbersome.
[0011] In one instance of a call center system 100 as illustrated in FIG. 1, there are five main subsystems including a mobile device 102, a call center exchange 104, a hierarchy map server 106, a statistics server 108 and a call center direct line 110. Once a user launches a call request 112 to the call center exchange 104, it will request hierarchy map 114 from the hierarchy map server 106. Then the hierarchy map server 106 gets statistical information 116 from the statistics server 108. On the hierarchy map server 106, it generates a hierarchy map 118 according to the statistical information 120, and then returns the hierarchy map 122 to the call center exchange 104, and finally 124 to the mobile device 102. Once the user gets to view the hierarchy map on their mobile device, they can then select a specific leaf node in the hierarchy map 126, and send a call request 128 to the call center direct line 110. Then connection between mobile device 102 and the call center direct line 110 is then constructed 130, and the user can directly communicate with the call center direct line 110 until they end the call 132 and close the connection 134. The call center direct line 110 then updates the statistics information 136 to statistical serverl08.
[0012] FIG. 2 illustrates an example of a user interface 200 with graphics on a client side application residing on a user's device. In one instance, an end user can zoom in 202 and out 204 by selecting a menu item, and/or directly using their fingers on a screen to zoom in and out on a whole hierarchy map 206. Once a user is familiar with the hierarchy map 206, they can also directly move their finger to a specific leaf node, e.g., the lowest layer node 208 in the hierarchy map 206. Hint information 210 pops up prompting a specific usage message relating to a direct line number. The user can then directly select this menu item 208 to get a connection with a call center direct line. In one instance, on each layer, the numbers are arranged according to the Arabic number sequence. In other instances, the numbers on each layer can be placed according to statistics information, which is discussed infra.
[0013] An example data structure 300 of one instance that resides on a statistics server is shown in FIG. 3. There are three tables 302-306, which are respectively table "CallCenterExchange" 302, table "Layer" 304, and table
"Number"306. In this example, a hierarchy map is generated according to the following data structure. The top layer is the call center exchange number from the table "CallCenterExchange" 302, and then the numbers are retrieved from the table "Number" 306 according to their layer_id, e.g., one layer by one layer. On a specific layer, the numbers are lined up according to a descent sequence calculated by a field "count" in table "Number" 306.
[0014] In one example, system 400 illustrated in FIG. 4, a mobile device 402 comprises a mobile device interface 404 and a display 406. In some mobile devices, the interface 404 and the display 406 are the same mechanical structure (e.g., a touch screen, etc.). On other mobile devices, the display 406 is separate from a user input interface 404 such as a keyboard, mouse and the like. A map processor 408 resides on the mobile device 402 and interacts with the mobile device interface 404 and the display 406. In this example, a user enters a call center number 410 into the mobile device interface 404. This can be done by directly entering keystrokes on a keypad, via a touch screen and/or by selecting a number from a contact list to command the mobile device to dial the call center number 410.
[0015] The map processor 408 can receive the dialed call center number 410 at the time of dialing to prepare it for receiving a call center hierarchy map 412. In other instances, the map processor 408 does not receive the call center number 410 at the time of dialing but monitors communication means of the mobile device for incoming hierarchy maps. In either case, when the map processor 408 receives the call center hierarchy map 412, it processes the map information, if necessary, and sends it to the display 406 of the mobile device 402. The user is then presented with the call center hierarchy map 412 and can select which node of the hierarchy they desire to contact. This user interaction with the hierarchy map 414, whether via the mobile device interface 404 and/or via the display 406, is then forwarded to the map processor 408. The map processor 408 then determines a desired call center connection 416 and transmits this information via a communication means of the mobile device 402 to establish a direct connection for the user.
[0016] What has been described above includes examples of the embodiments.
It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the embodiments, but one of ordinary skill in the art can recognize that many further combinations and permutations of the
embodiments are possible. Accordingly, the subject matter is intended to embrace all such alterations, modifications and variations that fall within scope of the appended claims. Furthermore, to the extent that the term "includes" is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term "comprising" as "comprising" is interpreted when employed as a transitional word in a claim.
Claims
1. A system that provides call center information, comprising:
a map processor residing in a mobile device that receives a call center hierarchy map, displays the call center hierarchy map on the mobile device and accepts user input to establish a direct communications link with a call center.
2. The system of claim 1, wherein the map processor receives a dialed call center number at the time of dialing and subsequently monitors a communication means of the mobile device for a call center hierarchy map.
3. The system of claim 1, wherein the map processor receives a call center hierarchy map with frequently contacted numbers shown at higher levels as the dialing frequency of the contacted numbers increases.
4. The system of claim 1, wherein the map processor displays a usage message in proximity of a leaf node of the call center hierarchy map.
5. The system of claim 1, wherein the map processor monitors a communication means of the mobile device for a call center hierarchy map.
6. The system of claim 1, wherein the map processor interacts with at least one of an interface of the mobile device and a display of the mobile device to accept user input regarding a selected call center connection.
7. The system of claim 6, wherein the map processor receives the call center hierarchy map from at least one of a call center exchange and a hierarchy map server.
8. The system of claim 1, wherein the map processor receives a call center hierarchy map from at least one of a Wide Area Network communication connection of the mobile device and a cellular communication connection of the mobile device.
9. A method for providing call center information, comprising:
receiving, on a mobile device, a call center hierarchy map associated with a dialed call center number;
displaying the call center hierarchy map interactively on the mobile device; receiving a user selection from the interactive call center hierarchy map; and transmitting a request for a call center connection associated with the user selection.
10. The method of claim 9 further comprising:
receiving the call center hierarchy map over a communication means of the mobile device.
11. The method of claim 10 wherein the communication means comprising at least one of a Wide Area Network communication connection and a cellular communication connection.
12. The method of claim 9 further comprising:
displaying a usage message in proximity of a leaf node of the call center hierarchy map.
13. The method of claim 9 further comprising:
generating a call center hierarchy map with frequently contacted numbers shown at higher levels as the dialing frequency of the contacted numbers increases.
14. The method of claim 9 further comprising:
displaying the call center hierarchy map with nodes representing direct connections that are selectable by a user.
15. The method of claim 9 further comprising:
transforming the received call center hierarchy map to fit a display associated with the mobile device.
16. The method of claim 9further comprising:
communicating between the mobile device and at least one of a call center exchange, a hierarchy map server, a statistical server and a call center direct line to generate the call center hierarchy map and establish the call center connection associated with the user selection.
17. A system that establishes call center direct connections, comprising: means for receiving, on a mobile device, a call center hierarchy map associated with a dialed call center number;
means for displaying the call center hierarchy map interactively on the mobile device;
means for receiving a user selection from the interactive call center hierarchy map; and
means for transmitting a request for a call center connection associated with the user selection.
18. The system of claim 17 further comprising:
a means for receiving the call center hierarchy map over at least one type of communication means of the mobile device.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US14/435,612 US20150358466A1 (en) | 2012-10-23 | 2012-10-23 | Call Center Direct Access |
| PCT/CN2012/083371 WO2014063304A1 (en) | 2012-10-23 | 2012-10-23 | Call center direct access |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2012/083371 WO2014063304A1 (en) | 2012-10-23 | 2012-10-23 | Call center direct access |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2014063304A1 true WO2014063304A1 (en) | 2014-05-01 |
Family
ID=50543863
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2012/083371 Ceased WO2014063304A1 (en) | 2012-10-23 | 2012-10-23 | Call center direct access |
Country Status (2)
| Country | Link |
|---|---|
| US (1) | US20150358466A1 (en) |
| WO (1) | WO2014063304A1 (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040120483A1 (en) * | 2002-12-20 | 2004-06-24 | J. M. Buzbee Family Limited Partnership | Telephonic interface for a visual presentation of a hierarchy of menus |
| CN102185982A (en) * | 2011-05-13 | 2011-09-14 | 廖公仆 | Method for shortening waiting time of telephone voice prompt system |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6456699B1 (en) * | 1998-11-30 | 2002-09-24 | At&T Corp. | Web-based generation of telephony-based interactive voice response applications |
| US6829348B1 (en) * | 1999-07-30 | 2004-12-07 | Convergys Cmg Utah, Inc. | System for customer contact information management and methods for using same |
| US7027571B1 (en) * | 2002-10-21 | 2006-04-11 | Sprint Communications Company L.P. | Accelerator for intelligent voice response system |
| US7092738B2 (en) * | 2002-12-20 | 2006-08-15 | International Business Machines Corporation | Navigation of interactive voice response application using a wireless communications device graphical user interface |
| US20040235520A1 (en) * | 2003-05-20 | 2004-11-25 | Cadiz Jonathan Jay | Enhanced telephony computer user interface allowing user interaction and control of a telephone using a personal computer |
| US8364125B2 (en) * | 2004-11-09 | 2013-01-29 | Avaya, Inc. | Content delivery to a telecommunications terminal that is associated with a call in progress |
| 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 |
| US8903073B2 (en) * | 2011-07-20 | 2014-12-02 | Zvi Or-Bach | Systems and methods for visual presentation and selection of IVR menu |
-
2012
- 2012-10-23 WO PCT/CN2012/083371 patent/WO2014063304A1/en not_active Ceased
- 2012-10-23 US US14/435,612 patent/US20150358466A1/en not_active Abandoned
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040120483A1 (en) * | 2002-12-20 | 2004-06-24 | J. M. Buzbee Family Limited Partnership | Telephonic interface for a visual presentation of a hierarchy of menus |
| CN102185982A (en) * | 2011-05-13 | 2011-09-14 | 廖公仆 | Method for shortening waiting time of telephone voice prompt system |
Also Published As
| Publication number | Publication date |
|---|---|
| US20150358466A1 (en) | 2015-12-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9071950B2 (en) | Systems and methods of call-based data communication | |
| US8340255B2 (en) | Interactive display response system | |
| US8798585B2 (en) | System and method for enhanced communications via small data rate communication systems | |
| US7092738B2 (en) | Navigation of interactive voice response application using a wireless communications device graphical user interface | |
| US20070135101A1 (en) | Enhanced visual IVR capabilities | |
| CN103428377A (en) | Visible IVR (Interactive Voice Response) implementation method and system | |
| US8548131B1 (en) | Systems and methods for communicating with an interactive voice response system | |
| CN105721470A (en) | Method for realizing visual access of calling center | |
| US20150358476A1 (en) | System for conducting packet service telecommunications on non-packet enabled devices | |
| CN101330674A (en) | Method for dynamically updating mobile phone software menu | |
| CN101943991A (en) | Input method and equipment based on cloud computing | |
| US20160150080A1 (en) | A url transmission system and means thereof | |
| CN104216982A (en) | Information processing method and electronic equipment | |
| CN103635878B (en) | Information distribution system and method thereof | |
| KR20100050603A (en) | System providing widget service and method for updating widget information thereof | |
| US20150358466A1 (en) | Call Center Direct Access | |
| US9154633B2 (en) | Data communication | |
| US20100202600A1 (en) | Communication system, communication control device, communication method, communication control method and recording medium | |
| KR101318471B1 (en) | Interactive response system for giving a user access to information | |
| CN102082764A (en) | Method and system for providing uniform service platform by using calling to push videos | |
| CN102739616A (en) | Interactive voice service system and realization method thereof | |
| CN106559589B (en) | Information in conversation display methods and device | |
| CN110688490A (en) | Method and device for configuring knowledge graph | |
| CN104348942B (en) | The method and user terminal of dialing auxiliary information is presented | |
| US8400966B2 (en) | Computer assisted VOIP communication method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 12887294 Country of ref document: EP Kind code of ref document: A1 |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 14435612 Country of ref document: US |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 12887294 Country of ref document: EP Kind code of ref document: A1 |