WO2000011573A1 - A method and apparatus for network based customer service - Google Patents

A method and apparatus for network based customer service Download PDF

Info

Publication number
WO2000011573A1
WO2000011573A1 PCT/US1999/018684 US9918684W WO0011573A1 WO 2000011573 A1 WO2000011573 A1 WO 2000011573A1 US 9918684 W US9918684 W US 9918684W WO 0011573 A1 WO0011573 A1 WO 0011573A1
Authority
WO
WIPO (PCT)
Prior art keywords
help
client
advisor
customer
answer
Prior art date
Application number
PCT/US1999/018684
Other languages
French (fr)
Inventor
Frank A. Galdes
Mark A. Ericson
Original Assignee
Kana Communications, Inc.
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=22479941&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=WO2000011573(A1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by Kana Communications, Inc. filed Critical Kana Communications, Inc.
Priority to AU54896/99A priority Critical patent/AU5489699A/en
Publication of WO2000011573A1 publication Critical patent/WO2000011573A1/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/954Navigation, e.g. using categorised browsing
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2216/00Indexing scheme relating to additional aspects of information retrieval not explicitly covered by G06F16/00 and subgroups
    • G06F2216/15Synchronised browsing

Definitions

  • the present invention relates to customer service, and more specifically, to network based customer service.
  • a recent business trend is to reduce help desk traffic by promoting the Internet as a way for customers, and individuals within the corporation, to access information.
  • the Internet is particularly suited for this because of its global reach and relatively easy accessibility.
  • Q&A Question and Answer
  • FAQ frequently asked questions
  • help-desk One prior art method of providing more interactive customer service on the Internet is a web based help-desk.
  • the customer logs on to a "help page," that is separate from the area in which the customer had trouble.
  • the customer then fills out a help request, including answering a series of questions regarding the problem.
  • the customer's computer system sends configuration information to service technicians.
  • the service technicians evaluate the data from the computer and the help request.
  • the service technicians then call the customer to discuss the problem.
  • help desk traffic As a direct 800 number help desk. Additionally, filling out the help request is a chore that takes considerable time. Furthermore, some customers do not like having the contents of their personal computers surveyed, especially if at least some sections of that computer are not relevant to the problem, and contain private information. In addition, the customer must leave the web page on which he or she encountered the problem to log on to the help page to start this help process. This interrupts normal work, and is a hassle.
  • a method and apparatus for network based customer service is described.
  • a menu including three levels of interaction is displayed.
  • One level of interaction is self-help searching in a database of information.
  • a second level of interaction is asynchronous help, requesting help and receiving a reply.
  • the third level of interaction is synchronous help, interaction with an advisor. If the client selects synchronous help, the method includes the steps of alerting the advisor and displaying a list of previously visited sites by the client to the advisor.
  • the synchronous help method further includes providing a synchronized display between the client and the advisor, such that the advisor sees an identical display to the client.
  • Figure 1 illustrates one embodiment of a network including a client and server system.
  • Figure 2 illustrates one embodiment of a server system in which the present invention may be implemented.
  • Figure 3 illustrates one embodiment of a help system block diagram.
  • Figures 4 illustrates one embodiment of an overview flow chart of the collaborative process.
  • Figure 5 illustrates one embodiment of a flowchart illustrating a self- help search.
  • Figure 6 illustrates one embodiment of a flowchart of asynchronous help.
  • Figure 7 illustrates one embodiment of a flow chart of synchronous help.
  • Figure 8 illustrates one embodiment of slider bars.
  • a method and apparatus for a network based customer service is described. As more and more information becomes available through a network such as the Internet, LAN, WAN or similar network, customer service should improve commensurably.
  • a network based customer service that allows a company to provide services in a faster and more organized matter, is advantageous.
  • Figure 1 illustrates a network including a client and server system.
  • a customer 110 is coupled to a network 120.
  • the network 120 may be the Internet, a LAN, a WAN, or a similar network 120.
  • the customer 110 has access to a database 140 and corporate web site 150 through the network 120.
  • the corporate web site 150 may implement a help system as described below. Alternatively the customer's system 110 may implement the help system.
  • An advisor 130 may be coupled to the network 120.
  • the advisor 130 may be a customer service representative, another customer, an automated system, or any other mechanism that provides help to the customer 110.
  • the advisor 130 is not always coupled to the network 120.
  • a voice connection 160 may be established between the customer 110 and the advisor 130, when the customer 110 requests help, as will be described below.
  • the voice connection 160 is established through a conventional telephone system.
  • the voice connection 160 may be established through the network 120, or through some other means, such as satellite.
  • the customer 110 can browse a number of sites through the network 120. If the customer 110 requests help a connection is established between the customer 110 and the advisor 130.
  • Figure 2 illustrates one embodiment of a server system in which the present invention may be implemented.
  • the help system is implemented in a client-server system.
  • Figure 3 illustrates a block diagram of one embodiment of a help system.
  • the collaboration unit 300 is located on a server, and permits the advisor to respond to customer help requests.
  • the collaboration unit 300 is located on the advisor's system.
  • the database unit 360 is located on a server.
  • the database unit is located on the same server as the collaboration unit 300.
  • the database unit 360 is coupled to the collaboration unit 300 through a network connection 355.
  • the collaboration unit 300 includes a network connection unit 310, permitting the collaboration unit 300 to interact with a customer.
  • the collaboration unit 300 also interfaces with the database unit 360 through the network connection unit 310.
  • the collaboration unit 300 further includes a communication channel 315.
  • the communication channel 315 includes a digital connection for text, images, video, etc. and a voice channel.
  • the communication channel 315 is established through the network connection unit 310.
  • the collaboration unit 300 further includes a workflow controller 325.
  • the workflow controller 325 controls what cases are routed to each advisor.
  • the workflow controller 325 also tracks the actions of the advisor and opens and closes cases.
  • the workflow controller 325 is a single system that controls workflow to all of the advisors.
  • the context grabbing unit 340 collects context information from the customer's system, to aid the advisor in helping the customer.
  • Context information includes the web tracks of the customer, the locations he or she visited prior to asking for help.
  • the web tracks also include the actions of the customer at the prior locations.
  • the context may further include customer history. Customer history, for one embodiment, includes previous questions asked by the customer as well as personal information about the customer. All of this information may be used by the advisor to help the customer.
  • the collaboration unit 300 further may include a synchronization unit 320.
  • the advisor After a case is opened to respond to a help request, the advisor establishes a connection with the customer through the communication channel 315.
  • the advisor may also walk the customer through a web page to answer the customer's questions.
  • the synchronization unit 320 allows the customer's and advisor's browser display the same text and images at the same time.
  • the collaboration unit 300 further includes a search system 350, that permits the advisor to search a database to answer the customer's question.
  • the data may be in the data unit 370 of the database unit 360.
  • the search system 350 is automatically engaged to find an answer.
  • the elevation unit 330 elevates the customer's help request.
  • the elevation unit 330 collects the context information gathered by the context grabbing unit 340, and the information about the collaborative session collected by the workflow controller 325, and passes them to a second advisor.
  • the second advisor may be a manager or a technical specialist.
  • the posting generator 345 may be used if an answer is found to the customer's help request.
  • the posting generator 345 allows the advisor to "stick" a posting to a web page discussed with the customer.
  • the posting may include text, audio information, video, etc. This posting is associated with the specific web page for the customer.
  • the posting is persistent and appears on the web page every time the customer opens that web page, or until the customer closes the posting.
  • the postings generated by the posting generator 345 are stored in the database unit 360, not on the customer's computer system.
  • a report generation unit 335 may be used to generate a report on a specific case, or on some or all of the cases handled by the collaboration unit 300.
  • the report generation unit 335 automatically generates reports.
  • Some reports for example are: the number of questions answered by an advisor, the number of questions asked about any one location, the percentage of customers who asked questions, etc.
  • the database unit 360 includes data 370 that is searched by the search system 350.
  • the database 370 includes past postings and contexts.
  • the database 370 may further include a help file, a frequently asked questions (FAQ), or other data.
  • the database unit 360 may further include a purge unit 380.
  • the purge unit 380 may purge data in the data unit 370 if the data was not used for a long time. For one embodiment, if a data in the database 370 is not accessed for a period of time, it is purged. For example, the data may include an expiration date that is refreshed every time an access to the data is made. In this way, unused data is purged. For another embodiment, the purge unit 380 purges data relating to pages that are no longer available.
  • Figures 4-7 illustrates one embodiment of a flow chart of the operation of the present invention.
  • Figure 4 illustrates an overview of the collaboration process.
  • the customer indicates that he or she needs help.
  • the help form is accessible from a web page on which the customer has questions.
  • a help request form is displayed, which the customer then completes.
  • the customer's system dynamically overlay a help button over the web page.
  • the customer submits his or her help request via e-mail, telephone, or another method. If the help request is not submitted in an electronic form, it may be converted into an electronic query automatically or manually.
  • a case is opened in a workflow system.
  • the workflow system is on a server that receives the help request.
  • a case is opened.
  • the case includes the identity of the customer, the customer's specific question, and other information.
  • the other information may include a history of previous questions from the same customer, information about the skill level of the customer, and any further available information that improves a interaction between the customer and the customer service system.
  • the process tests whether the customer is using a thin client or a thick client.
  • a thick client is a system that automatically collects all relevant information from the customer.
  • a thin client may only collect the customer's identity. For one embodiment, if the help request was received through an e-mail request, telephonic request, or by another means, the client is designated as a thin client.
  • the process queries to determine the priority of response.
  • the customer may indicate a number of possible priorities.
  • the priorities are high, medium, and low.
  • data is saved in a database 450.
  • the database 450 is available to the advisor, and may be available to the customer, for searching.
  • the data saved in the database 450 enables a second advisor to determine what the question and the answer were.
  • the database 450 is used to provide consistent answers, and enhance searching for an answer.
  • the workflow case database is updated. This update indicates how the customer's question was disposed of, and that the case was completed.
  • the information is entered by the advisor.
  • the process may automatically determine the disposal of the case, and update the database.
  • the customer's personal solution determined during the session at block 435, 440, or 445, is posted. This solution is now available to the customer persistently. The answer is also available to other customers through the database.
  • Figure 5 illustrates one embodiment of the process of self-service lookup.
  • the self-service lookup is initiated.
  • the self-service lookup is initiated in response to a customer posting a low priority help request.
  • the process tests whether the customer has selected a search basis.
  • the type of search used depends on the search basis.
  • the search basis may include:
  • search bases • structured search, i.e. searching through a tree.
  • One of these search bases may be selected.
  • a combination of one or more of these search bases may be selected, for example a context based search further refined using keywords.
  • this step may be skipped and the process may automatically select the search type.
  • a combination of one or more of the search basis may be used for the search.
  • a search data entry block is displayed, allowing the customer to type in a search.
  • the search is a Boolean search, allowing a complex query.
  • the text search is an English search that allows the customer to type in a query in normal English, and the search engine parses the query to obtain search terms. Alternative ways of searching are known in the art and may be used.
  • the process continues to block 525.
  • postings relating to the current page from which the customer requested help are displayed.
  • the postings are displayed with headers indicating the topic of the posting, allowing the customer to select postings that may be relevant to the customer's question.
  • the process then continues to block 545. Alternatively, if there are too many postings associated with the page, the process may continue to block 535.
  • the process obtains the customer's web tracks.
  • the web tracks include past locations, i.e. what web pages the customer visited prior to asking for help.
  • the web tracks may further include the actions of the customer at each of the previous sites.
  • the web tracks include only those sites and actions that are relevant. Thus, for example, if prior to starting the process leading to the current question, the customer visited other sites, such as a search engine, web store, bank, etc., that information is not collected.
  • the process then continues to block 535.
  • the customer is allowed to select keys /specificity.
  • the customer may, at this point, select how closely the context, text, or page location of the customer has to match the data associated with the postings to be displayed. For one embodiment, this block may be left out of the process. For another embodiment, this block is selectively included in the process if the number of postings found otherwise is excessive.
  • a set of hierarchical folders is displayed with headers indicating the type of postings included in each of the folders.
  • an alternative means of display may be used.
  • the customer is allowed to narrow or broaden the search.
  • the customer changes the scope of the search using slide selection bars.
  • One embodiment of bars are illustrated in Figure 8.
  • the process determines whether the customer has found an answer.
  • the customer may indicate that he or she has found an answer by pushing an "answer found” button, or the process may determine in some other way that the customer has found the answer.
  • the process continues to block 565.
  • the customer is permitted to execute a new search or change the search basis.
  • the customer is also allowed to change the priority of the help request, thereby requesting another type of help.
  • the customer may decide that he or she can not obtain an answer using self-help, and may request asynchronous or synchronous help.
  • the process continues to block 555.
  • the customer may create a posting associated with the web page. This posting may clarify the answer the customer has found. This posting is useful for the customer, since it is persistent and remains associated with the web page for this customer.
  • an electronic agent may push relevant information onto the customer's computer system. For one embodiment, push technology is used.
  • relevant information tagged by the customer is saved to the customer's system using another method.
  • the customer's click stream, or web tracks, are added to the context for the answer.
  • the context gathered during this interaction is added to the context of the answer in the database.
  • the search text may also be added to the context for the answer. Adding this information to the context simplifies the search procedure for the next customer who has a similar query.
  • the self-help process may be simplified.
  • the context-based search is automatically selected.
  • the process determines an answer, and an electronic agent pushes the answer to the customer's system.
  • This methodology does not require customer interaction with the help system.
  • the process described with respect to Figure 5 is used, but all decisions indicated to be made by the customer are automated.
  • the customer can select this type of self-help.
  • the system may automatically select this agent based self-help method.
  • Figure 6 illustrates the process of asynchronous collaboration.
  • Asynchronous collaboration permits the customer to post a help query.
  • the help query is answered by an advisor at a later time, and the response is posted to the customer. The customer can then access the answer.
  • This process takes place asynchronously.
  • asynchronous help generally posts responses to a help query within 24 hours.
  • the asynchronous collaboration is initiated.
  • the asynchronous collaboration is initiated in response to a customer posting a medium priority help request.
  • the help request is transmitted to an advisor.
  • the advisor may be a customer service representative.
  • the advisor may be an artificial intelligence.
  • the advisor may be another customer.
  • the web tracks of the customer requesting help are transmitted to the advisor. As described above, the web tracks may include past locations and past actions of the customer.
  • the customer's history is retrieved.
  • the customer's history may include previous help requests.
  • the customer's history may include the customer's previous actions with respect to this help request. Thus, for example, if the customer initially did a self-help search, this information is transmitted to the advisor.
  • the process tests whether the advisor has an answer for the customer's request.
  • the advisor may have more experience than the customer, and may be able to obtain an answer without searching. If the advisor has an answer, the process continues to block 670, otherwise, the process continues to block 655.
  • the advisor is prompted to look up the help request in an answer database.
  • the answer database search for the advisor is similar to the search for the self-help, as discussed with respect to Figure 5.
  • the advisor is also able to use a more command-oriented interface for more in-depth searching.
  • the process tests whether the answer was found in the database.
  • the advisor indicates whether the answer was found by selecting the answer or selecting a "no answer found" button.
  • the process continues to block 670. If no answer was found, the process continues to block 665.
  • the advisor elevates the help request. As described above, elevating the help request passes the request and associated information to someone else. The process then returns to block 650, where the process determines whether the new advisor, to whom the help request was elevated, has an answer.
  • the process continues to block 670.
  • the answer is posted to the customer.
  • the answer may be posted as a separate document, a posting directly associated with the web site, or in some other way.
  • the answer may include text, video, audio or other display technology indicating an answer to the customer's help query.
  • the process determines whether the answer exists in the database. For one embodiment, if the advisor knew the answer, and did not find it in the database, the answer may be new to the system. If the answer is found in the database, the process continues to block 685.
  • the information from the customer is added to the existing answer.
  • the information may include the customer's web tracks, meta-tags, information associated with the help query, as well as the help query itself. This allows the next advisor or customer looking for the answer to find it more easily.
  • the process continues to block 690.
  • the answer and some associated information is added to the database.
  • the answer is added into a folder.
  • the associated information may include the customer's web tracks, meta-tags associated with the help query, as well as the help query itself.
  • the customer has an answer accessible to the customer and available to advisors and/or customers through the database.
  • Figure 7 illustrates the process of synchronous collaboration.
  • the synchronous collaboration is initiated. Synchronous collaboration provides almost instantaneous personal help to the customer.
  • the synchronous collaboration is initiated in response to a customer posting a high priority help request.
  • the synchronous collaboration is initiated. For one embodiment, if the customer posted the help request through e-mail or telephone, the synchronous collaboration is initiated when an Internet connection is established between the customer and the agent.
  • help requests are allocated to advisors on a time basis, i.e. the advisor that is not busy will receive the next help request.
  • help requests may be allocated based on the advisor's level of knowledge in the area of the help request.
  • the customer's history may influence what advisor receives the help request.
  • the advisor is permitted to prepare by reviewing the customer's data. This informs the advisor of the question the customer has, as well as prior interactions between the help system and the customer.
  • a collaboration connection is established between the advisor and the customer.
  • the advisor presses a button indicating that the advisor is ready to collaborate with the customer.
  • this establishes a network link between the customer and the advisor.
  • the advisor may also establish a voice link with the customer.
  • the advisor may decide to open a synchronized collaboration window, so that the display for the advisor and the customer is identical. This may be helpful to clarify the problem and /or answer. For one embodiment, this step may be left out.
  • the advisor may decide to establish the window or not establish the window based on the type of question asked by the customer.
  • the customer may refuse the establishment of the synchronized collaboration window. If the customer refuses to establish the window, the process continues directly to block 770. If the customer does not refuse the establishment of a synchronized window, the process continues to block 760.
  • a synchronized collaboration window is opened on both system.
  • This window allows an identical display, permitting closer interaction between the customer and the advisor.
  • the synchronous collaboration window allows the advisor to see the same display as the customer even if the customer's question comes from a personalized web page.
  • the process determines whether the advisor has an answer to the customer's query. If the advisor has an answer, the process continues to block 790. If the advisor does not have an answer, the process continues to block 775.
  • a database window is opened.
  • the database window is a separate window from the collaboration window, and the synchronous collaboration window.
  • the database window is invisible to the customer.
  • the database window is visible to the customer. The advisor then searches the database.
  • the process determines whether the advisor has found an answer in the database. If the advisor has found an answer, the process returns to block 790. If the advisor did not find an answer, the process continues to block 785.
  • the help request is elevated. For one embodiment, the customer is informed of this elevation, and the customer further interacts with the new advisor who receives the elevated request. For another embodiment, the customer remains with the original advisor, and is not informed of the elevation of the request. Once the request is elevated, the process returns to block 770, determining whether the advisor to whom the request was elevated has an answer.
  • the process continued to block 790.
  • the answer is posted to the collaboration window of the customer.
  • the collaboration window is a synchronous collaboration window displaying web pages synchronously to the customer and the advisor.
  • the collaboration window may be a separate window that allows interaction between the customer and the advisor without a synchronous display.
  • the posting may include text, audio, video, and /or any other type of data to answer the customer's question.
  • the database is updated.
  • the answer may be added to the database, if it was not found in the database.
  • the information associated with the specific customer's question and web tracks may be added to the answer if the answer was found in the database.
  • This synchronous collaboration provides immediate answers to the customers' high priority questions.
  • the postings are persistent, and remain associated with the specific page and help query to which they correspond.
  • the each of these types of collaboration also builds a more elaborate database with each request.
  • Figure 8 illustrates one embodiment of the slider bars that may be used to change answers displayed to the customer. These slider bars may be used to select a number of things. For example, the slider bars may determine the similarity between the web tracks of a previous answer in the database and the current query. The less specificity is requested, the more answers may correspond to the help query. The slider bars may also determine such things as the length of the answer requested, the complexity of the answer requested, the format of the answer requested, etc.
  • the importance of each of those terms or previous locations may be individually adjusted.
  • the customer has visited six previous locations before asking the question, more importance may be attached to one particular previous page during the search.
  • these slider bars are adjusted during initial searching.
  • these slider bars may be moved to refine a search during the search process, based on the types of answers retrieved from the initial search.

Abstract

A method and apparatus for a network (120) based customer (110) service is provided. In response to a client requesting help, a menu including three levels of interaction is displayed. One level of interaction is self-help searching in a database (140) of information. A second level of interaction is synchronous help, requesting help and receiving a reply. The third level of interaction is synchronous help, interaction with an advisor (130). If the client selects synchronous help, the method includes the steps of alerting the advisor and displaying a list of previously visited sites (150) by the client to the advisor. The synchronous help method further includes providing a synchronized display between the client and the advisor, such that the advisor sees an identical display to the client.

Description

A METHOD AND APPARATUS FOR NETWORK BASED CUSTOMER
SERVICE FIELD OF THE INVENTION
The present invention relates to customer service, and more specifically, to network based customer service.
BACKGROUND
A recent business trend is to reduce help desk traffic by promoting the Internet as a way for customers, and individuals within the corporation, to access information. The Internet is particularly suited for this because of its global reach and relatively easy accessibility.
One prior art method of providing customer service is by posting a question in a Question and Answer (Q&A) list, and waiting until either service personnel or other customers provide an answer by posting it to the same Q&A list. The answer may or may not be correct.
Another prior art Internet based customer service solution is posting a large "frequently asked questions" (FAQ) list that answers most typical questions.
While using the Internet reduces costs, for most prior art systems it reduces customer satisfaction. The customer does not feel that he or she is receiving individual attention. Furthermore, there is no assurance that the answer is correct for the specific situation in which the customer finds himself or herself.
One prior art method of providing more interactive customer service on the Internet is a web based help-desk. The customer logs on to a "help page," that is separate from the area in which the customer had trouble. The customer then fills out a help request, including answering a series of questions regarding the problem. While the customer is connected to this help page on the Internet, the customer's computer system sends configuration information to service technicians. The service technicians evaluate the data from the computer and the help request. The service technicians then call the customer to discuss the problem.
However, this requires the same amount of help desk traffic as a direct 800 number help desk. Additionally, filling out the help request is a chore that takes considerable time. Furthermore, some customers do not like having the contents of their personal computers surveyed, especially if at least some sections of that computer are not relevant to the problem, and contain private information. In addition, the customer must leave the web page on which he or she encountered the problem to log on to the help page to start this help process. This interrupts normal work, and is a hassle.
SUMMARY OF THE INVENTION
A method and apparatus for network based customer service is described. In response to a client requesting help, a menu including three levels of interaction is displayed. One level of interaction is self-help searching in a database of information. A second level of interaction is asynchronous help, requesting help and receiving a reply. The third level of interaction is synchronous help, interaction with an advisor. If the client selects synchronous help, the method includes the steps of alerting the advisor and displaying a list of previously visited sites by the client to the advisor. The synchronous help method further includes providing a synchronized display between the client and the advisor, such that the advisor sees an identical display to the client.
BRIEF DESCRIPTION OF THE DRAWINGS
The present invention is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which:
Figure 1 illustrates one embodiment of a network including a client and server system.
Figure 2 illustrates one embodiment of a server system in which the present invention may be implemented. Figure 3 illustrates one embodiment of a help system block diagram.
Figures 4 illustrates one embodiment of an overview flow chart of the collaborative process.
Figure 5 illustrates one embodiment of a flowchart illustrating a self- help search.
Figure 6 illustrates one embodiment of a flowchart of asynchronous help.
Figure 7 illustrates one embodiment of a flow chart of synchronous help.
Figure 8 illustrates one embodiment of slider bars.
DETAILED DESCRIPTION
A method and apparatus for a network based customer service is described. As more and more information becomes available through a network such as the Internet, LAN, WAN or similar network, customer service should improve commensurably. A network based customer service, that allows a company to provide services in a faster and more organized matter, is advantageous.
Figure 1 illustrates a network including a client and server system. A customer 110 is coupled to a network 120. The network 120 may be the Internet, a LAN, a WAN, or a similar network 120. The customer 110 has access to a database 140 and corporate web site 150 through the network 120. The corporate web site 150 may implement a help system as described below. Alternatively the customer's system 110 may implement the help system.
An advisor 130 may be coupled to the network 120. The advisor 130 may be a customer service representative, another customer, an automated system, or any other mechanism that provides help to the customer 110. For one embodiment, the advisor 130 is not always coupled to the network 120. Furthermore, a voice connection 160 may be established between the customer 110 and the advisor 130, when the customer 110 requests help, as will be described below. For one embodiment, the voice connection 160 is established through a conventional telephone system. Alternatively, the voice connection 160 may be established through the network 120, or through some other means, such as satellite.
The customer 110 can browse a number of sites through the network 120. If the customer 110 requests help a connection is established between the customer 110 and the advisor 130.
Figure 2 illustrates one embodiment of a server system in which the present invention may be implemented. For one embodiment, the help system is implemented in a client-server system.
Figure 3 illustrates a block diagram of one embodiment of a help system. The collaboration unit 300 is located on a server, and permits the advisor to respond to customer help requests. For one embodiment, the collaboration unit 300 is located on the advisor's system. The database unit 360 is located on a server. For one embodiment, the database unit is located on the same server as the collaboration unit 300. For another embodiment, the database unit 360 is coupled to the collaboration unit 300 through a network connection 355.
The collaboration unit 300 includes a network connection unit 310, permitting the collaboration unit 300 to interact with a customer. For another embodiment, the collaboration unit 300 also interfaces with the database unit 360 through the network connection unit 310.
The collaboration unit 300 further includes a communication channel 315. For one embodiment, the communication channel 315 includes a digital connection for text, images, video, etc. and a voice channel. For one embodiment, the communication channel 315 is established through the network connection unit 310.
The collaboration unit 300 further includes a workflow controller 325. The workflow controller 325 controls what cases are routed to each advisor. The workflow controller 325 also tracks the actions of the advisor and opens and closes cases. For one embodiment, the workflow controller 325 is a single system that controls workflow to all of the advisors.
When a new case is opened by the workflow controller 325, the context grabbing unit 340 collects context information from the customer's system, to aid the advisor in helping the customer. Context information includes the web tracks of the customer, the locations he or she visited prior to asking for help. For one embodiment, the web tracks also include the actions of the customer at the prior locations. For one embodiment, the context may further include customer history. Customer history, for one embodiment, includes previous questions asked by the customer as well as personal information about the customer. All of this information may be used by the advisor to help the customer.
The collaboration unit 300 further may include a synchronization unit 320. For one embodiment, after a case is opened to respond to a help request, the advisor establishes a connection with the customer through the communication channel 315. For one embodiment, the advisor may also walk the customer through a web page to answer the customer's questions. The synchronization unit 320 allows the customer's and advisor's browser display the same text and images at the same time.
The collaboration unit 300 further includes a search system 350, that permits the advisor to search a database to answer the customer's question. The data may be in the data unit 370 of the database unit 360. For one embodiment, if the advisor does not know the answer to the customer's help request, the search system 350 is automatically engaged to find an answer. For one embodiment, if the advisor can not answer with the help of the search system 350, the elevation unit 330 elevates the customer's help request. The elevation unit 330 collects the context information gathered by the context grabbing unit 340, and the information about the collaborative session collected by the workflow controller 325, and passes them to a second advisor. For one embodiment, the second advisor may be a manager or a technical specialist.
The posting generator 345 may be used if an answer is found to the customer's help request. The posting generator 345 allows the advisor to "stick" a posting to a web page discussed with the customer. The posting may include text, audio information, video, etc. This posting is associated with the specific web page for the customer. For one embodiment, the posting is persistent and appears on the web page every time the customer opens that web page, or until the customer closes the posting. For one embodiment, the postings generated by the posting generator 345 are stored in the database unit 360, not on the customer's computer system.
A report generation unit 335 may be used to generate a report on a specific case, or on some or all of the cases handled by the collaboration unit 300. For one embodiment, the report generation unit 335 automatically generates reports. Some reports, for example are: the number of questions answered by an advisor, the number of questions asked about any one location, the percentage of customers who asked questions, etc.
The database unit 360 includes data 370 that is searched by the search system 350. The database 370 includes past postings and contexts. The database 370 may further include a help file, a frequently asked questions (FAQ), or other data. The database unit 360 may further include a purge unit 380. The purge unit 380 may purge data in the data unit 370 if the data was not used for a long time. For one embodiment, if a data in the database 370 is not accessed for a period of time, it is purged. For example, the data may include an expiration date that is refreshed every time an access to the data is made. In this way, unused data is purged. For another embodiment, the purge unit 380 purges data relating to pages that are no longer available.
Figures 4-7 illustrates one embodiment of a flow chart of the operation of the present invention. Figure 4 illustrates an overview of the collaboration process.
At block 410, the customer indicates that he or she needs help. For one embodiment, the help form is accessible from a web page on which the customer has questions. For one embodiment, there is an icon on a web page indicating that the customer needs help. When the customer clicks on that icon, a help request form is displayed, which the customer then completes. For another embodiment, the customer's system dynamically overlay a help button over the web page. For yet another embodiment, the customer submits his or her help request via e-mail, telephone, or another method. If the help request is not submitted in an electronic form, it may be converted into an electronic query automatically or manually.
At block 415, a case is opened in a workflow system. The workflow system is on a server that receives the help request. In response to receiving a help request, a case is opened. For one embodiment, the case includes the identity of the customer, the customer's specific question, and other information. For one embodiment, the other information may include a history of previous questions from the same customer, information about the skill level of the customer, and any further available information that improves a interaction between the customer and the customer service system.
At block 420, the process tests whether the customer is using a thin client or a thick client. A thick client is a system that automatically collects all relevant information from the customer. A thin client may only collect the customer's identity. For one embodiment, if the help request was received through an e-mail request, telephonic request, or by another means, the client is designated as a thin client.
If the customer is using a thick client, relevant information is automatically collected by the system. If the customer is using a thin client, the process continues to block 425. At block 425, context is collected. The process then continues to block 430. If a thick client was used, the process continues directly to block 430 direction.
At block 430, the process queries to determine the priority of response. The customer may indicate a number of possible priorities. For one embodiment, the priorities are high, medium, and low.
If low priority was selected, the process continues to block 445, and a self-service lookup is initiated. The self-service lookup is described in more detail with respect to Figure 5.
If medium priority was selected, the process continues to block 440, and an asynchronous collaboration is initiated. Asynchronous collaboration is described in more detail with respect to Figure 6. If high priority was selected, the process continues to block 435, and a synchronous collaboration is initiated. Synchronous collaboration is described in more detail with respect to Figure 7.
Each of the types of responses, synchronous collaboration at block 435, asynchronous collaboration at block 440, and self-help lookup at block 445, continue to block 450.
At block 450, data is saved in a database 450. The database 450 is available to the advisor, and may be available to the customer, for searching. The data saved in the database 450 enables a second advisor to determine what the question and the answer were. The database 450 is used to provide consistent answers, and enhance searching for an answer.
At block 455, the workflow case database is updated. This update indicates how the customer's question was disposed of, and that the case was completed. For one embodiment, the information is entered by the advisor. Alternatively, the process may automatically determine the disposal of the case, and update the database.
At block 460, the customer's personal solution, determined during the session at block 435, 440, or 445, is posted. This solution is now available to the customer persistently. The answer is also available to other customers through the database.
Figure 5 illustrates one embodiment of the process of self-service lookup. At block 510, the self-service lookup is initiated. For one embodiment, the self-service lookup is initiated in response to a customer posting a low priority help request.
At block 515, the process tests whether the customer has selected a search basis. For one embodiment, the type of search used depends on the search basis. For one embodiment, the search basis may include:
• keywords, i.e. a text search,
• context, a current location from which the help was requested,
• structured search, i.e. searching through a tree. One of these search bases may be selected. Alternatively, a combination of one or more of these search bases may be selected, for example a context based search further refined using keywords.
For another embodiment, this step may be skipped and the process may automatically select the search type. For another embodiment, a combination of one or more of the search basis may be used for the search.
If the customer selects a text search, the process continues to block 520. At block 520, a search data entry block is displayed, allowing the customer to type in a search. For one embodiment, the search is a Boolean search, allowing a complex query. For another embodiment, the text search is an English search that allows the customer to type in a query in normal English, and the search engine parses the query to obtain search terms. Alternative ways of searching are known in the art and may be used. When the customer enters the query, the process continues to block 535.
If the customer selects a "current page" based search, the process continues to block 525. At block 525, postings relating to the current page from which the customer requested help are displayed. For one embodiment, the postings are displayed with headers indicating the topic of the posting, allowing the customer to select postings that may be relevant to the customer's question. For one embodiment, the process then continues to block 545. Alternatively, if there are too many postings associated with the page, the process may continue to block 535.
If the customer selects a "context based" search, the process continues to block 530. At block 530, the process obtains the customer's web tracks. The web tracks, for one embodiment, include past locations, i.e. what web pages the customer visited prior to asking for help. The web tracks may further include the actions of the customer at each of the previous sites. For one embodiment, the web tracks include only those sites and actions that are relevant. Thus, for example, if prior to starting the process leading to the current question, the customer visited other sites, such as a search engine, web store, bank, etc., that information is not collected. The process then continues to block 535. At block 535, the customer is allowed to select keys /specificity. The customer may, at this point, select how closely the context, text, or page location of the customer has to match the data associated with the postings to be displayed. For one embodiment, this block may be left out of the process. For another embodiment, this block is selectively included in the process if the number of postings found otherwise is excessive.
At block 540, a set of hierarchical folders is displayed with headers indicating the type of postings included in each of the folders. For another embodiment, an alternative means of display may be used.
At block 545, the customer is allowed to narrow or broaden the search. For one embodiment, the customer changes the scope of the search using slide selection bars. One embodiment of bars are illustrated in Figure 8.
At block 550, the process determines whether the customer has found an answer. For one embodiment, the customer may indicate that he or she has found an answer by pushing an "answer found" button, or the process may determine in some other way that the customer has found the answer.
If the answer was not found, the process continues to block 565. At block 565, the customer is permitted to execute a new search or change the search basis. For one embodiment, the customer is also allowed to change the priority of the help request, thereby requesting another type of help. Thus, the customer may decide that he or she can not obtain an answer using self-help, and may request asynchronous or synchronous help.
If the answer was found at block 550, the process continues to block 555. At block 555, the customer may create a posting associated with the web page. This posting may clarify the answer the customer has found. This posting is useful for the customer, since it is persistent and remains associated with the web page for this customer. For another embodiment, an electronic agent may push relevant information onto the customer's computer system. For one embodiment, push technology is used. For another embodiment, relevant information tagged by the customer is saved to the customer's system using another method. At block 560, the customer's click stream, or web tracks, are added to the context for the answer. Thus, the context gathered during this interaction is added to the context of the answer in the database. For one embodiment, the search text may also be added to the context for the answer. Adding this information to the context simplifies the search procedure for the next customer who has a similar query.
For another embodiment, the self-help process may be simplified. In that instance, the context-based search is automatically selected. The process then determines an answer, and an electronic agent pushes the answer to the customer's system. This methodology does not require customer interaction with the help system. The process described with respect to Figure 5 is used, but all decisions indicated to be made by the customer are automated. For one embodiment, the customer can select this type of self-help. For another embodiment, based on customer information, i.e. if the customer is inexperienced with computers, the system may automatically select this agent based self-help method.
Figure 6 illustrates the process of asynchronous collaboration. Asynchronous collaboration permits the customer to post a help query. The help query is answered by an advisor at a later time, and the response is posted to the customer. The customer can then access the answer. This process takes place asynchronously. For one embodiment, asynchronous help generally posts responses to a help query within 24 hours.
At block 610, the asynchronous collaboration is initiated. For one embodiment, the asynchronous collaboration is initiated in response to a customer posting a medium priority help request.
At block 620, the help request is transmitted to an advisor. For one embodiment, the advisor may be a customer service representative. For another embodiment, the advisor may be an artificial intelligence. For yet another embodiment, the advisor may be another customer. At block 630, the web tracks of the customer requesting help are transmitted to the advisor. As described above, the web tracks may include past locations and past actions of the customer.
At block 640, the customer's history is retrieved. For one embodiment, the customer's history may include previous help requests. For another embodiment, the customer's history may include the customer's previous actions with respect to this help request. Thus, for example, if the customer initially did a self-help search, this information is transmitted to the advisor.
At block 650, the process tests whether the advisor has an answer for the customer's request. The advisor may have more experience than the customer, and may be able to obtain an answer without searching. If the advisor has an answer, the process continues to block 670, otherwise, the process continues to block 655.
At block 655, the advisor is prompted to look up the help request in an answer database. The answer database search for the advisor is similar to the search for the self-help, as discussed with respect to Figure 5. For one embodiment, the advisor is also able to use a more command-oriented interface for more in-depth searching.
At block 660, the process tests whether the answer was found in the database. For one embodiment, the advisor indicates whether the answer was found by selecting the answer or selecting a "no answer found" button.
If an answer was found, the process continues to block 670. If no answer was found, the process continues to block 665. At block 665, the advisor elevates the help request. As described above, elevating the help request passes the request and associated information to someone else. The process then returns to block 650, where the process determines whether the new advisor, to whom the help request was elevated, has an answer.
If an answer was found at block 650 or 660, the process continues to block 670. At block 670, the answer is posted to the customer. For one embodiment, the answer may be posted as a separate document, a posting directly associated with the web site, or in some other way. The answer may include text, video, audio or other display technology indicating an answer to the customer's help query.
At block 680, the process determines whether the answer exists in the database. For one embodiment, if the advisor knew the answer, and did not find it in the database, the answer may be new to the system. If the answer is found in the database, the process continues to block 685.
At block 685, the information from the customer is added to the existing answer. For one embodiment, the information may include the customer's web tracks, meta-tags, information associated with the help query, as well as the help query itself. This allows the next advisor or customer looking for the answer to find it more easily.
If the answer was not found in the database, the process continues to block 690. At block 690, the answer and some associated information is added to the database. For one embodiment, the answer is added into a folder. For one embodiment, the associated information may include the customer's web tracks, meta-tags associated with the help query, as well as the help query itself. The customer has an answer accessible to the customer and available to advisors and/or customers through the database.
Figure 7 illustrates the process of synchronous collaboration. At block 710, the synchronous collaboration is initiated. Synchronous collaboration provides almost instantaneous personal help to the customer. For one embodiment, the synchronous collaboration is initiated in response to a customer posting a high priority help request.
At block 710, the synchronous collaboration is initiated. For one embodiment, if the customer posted the help request through e-mail or telephone, the synchronous collaboration is initiated when an Internet connection is established between the customer and the agent.
At block 720, the help request, web tracks, and customer history is transmitted to the advisor that will handle this help request. For one embodiment, help requests are allocated to advisors on a time basis, i.e. the advisor that is not busy will receive the next help request. For another embodiment, help requests may be allocated based on the advisor's level of knowledge in the area of the help request. For another embodiment, the customer's history may influence what advisor receives the help request.
At block 730, the advisor is permitted to prepare by reviewing the customer's data. This informs the advisor of the question the customer has, as well as prior interactions between the help system and the customer.
At block 740, a collaboration connection is established between the advisor and the customer. For one embodiment, the advisor presses a button indicating that the advisor is ready to collaborate with the customer. For one embodiment, this establishes a network link between the customer and the advisor. For anther embodiment, the advisor may also establish a voice link with the customer.
At block 750, the advisor may decide to open a synchronized collaboration window, so that the display for the advisor and the customer is identical. This may be helpful to clarify the problem and /or answer. For one embodiment, this step may be left out. For another embodiment, the advisor may decide to establish the window or not establish the window based on the type of question asked by the customer. For another embodiment, the customer may refuse the establishment of the synchronized collaboration window. If the customer refuses to establish the window, the process continues directly to block 770. If the customer does not refuse the establishment of a synchronized window, the process continues to block 760.
At block 760, a synchronized collaboration window is opened on both system. This window allows an identical display, permitting closer interaction between the customer and the advisor. Furthermore, for one embodiment, the synchronous collaboration window allows the advisor to see the same display as the customer even if the customer's question comes from a personalized web page.
At block 770, the process determines whether the advisor has an answer to the customer's query. If the advisor has an answer, the process continues to block 790. If the advisor does not have an answer, the process continues to block 775.
At block 775, a database window is opened. For one embodiment, the database window is a separate window from the collaboration window, and the synchronous collaboration window. For one embodiment, the database window is invisible to the customer. For another embodiment, the database window is visible to the customer. The advisor then searches the database.
At block 780, the process determines whether the advisor has found an answer in the database. If the advisor has found an answer, the process returns to block 790. If the advisor did not find an answer, the process continues to block 785. At block 785, the help request is elevated. For one embodiment, the customer is informed of this elevation, and the customer further interacts with the new advisor who receives the elevated request. For another embodiment, the customer remains with the original advisor, and is not informed of the elevation of the request. Once the request is elevated, the process returns to block 770, determining whether the advisor to whom the request was elevated has an answer.
If an answer was found at block 770 or block 780, the process continued to block 790. At block 790, the answer is posted to the collaboration window of the customer. For one embodiment, the collaboration window is a synchronous collaboration window displaying web pages synchronously to the customer and the advisor. For another embodiment, the collaboration window may be a separate window that allows interaction between the customer and the advisor without a synchronous display. The posting may include text, audio, video, and /or any other type of data to answer the customer's question.
At block 795, the database is updated. The answer may be added to the database, if it was not found in the database. Alternatively, the information associated with the specific customer's question and web tracks may be added to the answer if the answer was found in the database.
This synchronous collaboration provides immediate answers to the customers' high priority questions. In addition, the postings are persistent, and remain associated with the specific page and help query to which they correspond. The each of these types of collaboration also builds a more elaborate database with each request.
Figure 8 illustrates one embodiment of the slider bars that may be used to change answers displayed to the customer. These slider bars may be used to select a number of things. For example, the slider bars may determine the similarity between the web tracks of a previous answer in the database and the current query. The less specificity is requested, the more answers may correspond to the help query. The slider bars may also determine such things as the length of the answer requested, the complexity of the answer requested, the format of the answer requested, etc.
For another embodiment, in a search including multiple terms or previous locations, the importance of each of those terms or previous locations may be individually adjusted. Thus, for example, if the customer has visited six previous locations before asking the question, more importance may be attached to one particular previous page during the search.
For one embodiment, these slider bars are adjusted during initial searching. For another embodiment, these slider bars may be moved to refine a search during the search process, based on the types of answers retrieved from the initial search.
In the foregoing specification, the invention has been described with reference to specific exemplary embodiments thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the invention as set forth in the appended claims. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.

Claims

CLAIMSWhat is claimed is:
1. A method comprising: in response to a client requesting help, displaying a menu including three levels of interaction: self-help searching in a database of information; asynchronous help, requesting help and receiving a reply; and synchronous help, interaction with an advisor; if the client selects synchronous help, alerting the advisor; displaying a list of previously visited sites by the client to the advisor; and synchronizing display between the client and the advisor, such that the advisor sees an identical display to the client.
2. The method according to claim 1, wherein the identical display is displayed at a same rate for the advisor as for the client.
3. The method according to claim 1, wherein the advisor further has an additional display permitting search of a database of information to help the client.
4. The method according to claim 1, wherein the advisor posts sticky notes on a web site discussed with the client.
5. The method according to claim 4, wherein the sticky notes may include text, hyper-linked references, video, audio, or other information.
6. The method according to claim 4, wherein the sticky notes remain associated with the web site discussed with the client, and the client may go back to the web site and review the sticky notes.
7. The method according to claim 1, further comprising the step of creating a reviewable discussion trail based on the client's discussion with the advisor.
8. The method according to claim 7, wherein the discussion trail is stored on a server, and may be reviewed by the client at any time.
9. The method according to claim 1, further comprising the step of adding a help information generated by the advisor to the database of information accessible to clients.
10. The method according to claim 1, wherein if the client selects asynchronous help, the method further comprising the steps of: prompting the client to enter a help question; forwarding the help question to the advisor; waiting for the advisor to generate an answer the help question; and returning the answer to the client.
11. The method according to claim 10, wherein the answer returned to the client comprises a web page hyperlink.
12. The method according to claim 11, wherein the answer further includes a sticky note with hints.
13. The method according to claim 12, wherein the hints may include one or more of the following: a video of the advisor explaining the answer, a text message, an audio recording of the hints, or visual images.
14. A method of providing help through a client-server system comprising the steps of: a server receiving a help request from a client on a client system that is linked to the server; classifying the help request as a synchronous request or an asynchronous request; alerting a advisor if the help request is the synchronous request, the advisor conversing with the client over the link to deduce a problem and a solution; generating an answer to the problem including a hyper-linked web page and a sticky note for the client; and associating the answer with the client, such that the client can retrieve the answer multiple times, including the hyper-linked web page and the sticky note.
15. A method of providing help through a client-server system comprising the steps of: dynamically injecting a help button into web pages displayed to a client system; permitting the client system to request help from a first web page by pushing the help button; and providing a persistent answer to the client system that becomes associated with the first web page, and is displayed whenever the client system accesses the first web page.
16. The method of claim 15, wherein the persistent answer is stored on the server system.
17. The method of claim 15, further comprising: establishing a synchronous collaboration between a customer on the client system and an advisor, the synchronous collaboration providing a synchronous display and permitting the advisor to pilot a browser of the customer
18. The method of claim 15, further comprising: searching a predictive answer system for a response to the help request, wherein the predictive answer system uses pattern matching with a database to determine whether the response is applicable.
19. The method of claim 18, wherein the pattern includes customer profile and context information.
20. The method of claim 19, wherein the context information comprises previous web page locations visited by the customer and actions on the previous web page locations.
PCT/US1999/018684 1998-08-21 1999-08-16 A method and apparatus for network based customer service WO2000011573A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU54896/99A AU5489699A (en) 1998-08-21 1999-08-16 A method and apparatus for network based customer service

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US09/137,989 US6177932B1 (en) 1998-08-21 1998-08-21 Method and apparatus for network based customer service
US09/137,989 1998-08-21

Publications (1)

Publication Number Publication Date
WO2000011573A1 true WO2000011573A1 (en) 2000-03-02

Family

ID=22479941

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1999/018684 WO2000011573A1 (en) 1998-08-21 1999-08-16 A method and apparatus for network based customer service

Country Status (3)

Country Link
US (1) US6177932B1 (en)
AU (1) AU5489699A (en)
WO (1) WO2000011573A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1323100A1 (en) * 2000-09-27 2003-07-02 Cyber'Act Interactive method for communication data to communication network users
US8935772B2 (en) 1997-09-26 2015-01-13 Verizon Patent And Licensing Inc. Secure server architecture for web based data management

Families Citing this family (237)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010054064A1 (en) * 1997-07-02 2001-12-20 Pallipuram V. Kannan Method system and computer program product for providing customer service over the world-wide web
US6693661B1 (en) * 1998-10-14 2004-02-17 Polycom, Inc. Conferencing system having an embedded web server, and method of use thereof
US7127499B1 (en) * 1998-11-25 2006-10-24 General Electric Company Medical diagnostic system service method and apparatus
US6477531B1 (en) * 1998-12-18 2002-11-05 Motive Communications, Inc. Technical support chain automation with guided self-help capability using active content
US6615240B1 (en) 1998-12-18 2003-09-02 Motive Communications, Inc. Technical support chain automation with guided self-help capability and option to escalate to live help
US6694314B1 (en) * 1998-12-18 2004-02-17 Motive Communications, Inc. Technical support chain automation with guided self-help capability via a system-supplied search string
US6353446B1 (en) * 1999-01-25 2002-03-05 Network Associates, Inc. Method and system for integrated network management applications
US6360227B1 (en) * 1999-01-29 2002-03-19 International Business Machines Corporation System and method for generating taxonomies with applications to content-based recommendations
US6542898B1 (en) * 1999-05-12 2003-04-01 Motive Communications, Inc. Technical support chain automation with guided self-help capability using active content developed for specific audiences
US6711585B1 (en) 1999-06-15 2004-03-23 Kanisa Inc. System and method for implementing a knowledge management system
US6418448B1 (en) * 1999-12-06 2002-07-09 Shyam Sundar Sarkar Method and apparatus for processing markup language specifications for data and metadata used inside multiple related internet documents to navigate, query and manipulate information from a plurality of object relational databases over the web
SG134961A1 (en) * 2000-02-09 2007-09-28 Hitachi Ltd Answer system for technical support, and technical support method
US6658598B1 (en) 2000-02-17 2003-12-02 Motive Communications, Inc. Technical support chain automation with guided self-help capability using active content assertions
US6691159B1 (en) * 2000-02-24 2004-02-10 General Electric Company Web-based method and system for providing assistance to computer users
US8335994B2 (en) * 2000-02-25 2012-12-18 Salmon Alagnak Llc Method and apparatus for providing content to a computing device
EP1275042A2 (en) * 2000-03-06 2003-01-15 Kanisa Inc. A system and method for providing an intelligent multi-step dialog with a user
US7343295B2 (en) 2000-04-05 2008-03-11 Brenda Pomerance Automated complaint resolution system
US7529679B1 (en) 2000-04-05 2009-05-05 Brenda Pomerance Automated alternative dispute resolution
EP1156430A2 (en) * 2000-05-17 2001-11-21 Matsushita Electric Industrial Co., Ltd. Information retrieval system
US6701322B1 (en) * 2000-06-07 2004-03-02 Ge Financial Assurance Holdings, Inc. Interactive customer-business interview system and process for managing interview flow
US6829585B1 (en) * 2000-07-06 2004-12-07 General Electric Company Web-based method and system for indicating expert availability
US6618722B1 (en) * 2000-07-24 2003-09-09 International Business Machines Corporation Session-history-based recency-biased natural language document search
US7308646B1 (en) * 2000-08-30 2007-12-11 International Business Machines Corporation Integrating diverse data sources using a mark-up language
US7472166B1 (en) * 2000-08-31 2008-12-30 Intel Corporation Assisting users with web pages
US7302397B1 (en) * 2000-09-07 2007-11-27 The Boeing Company System for issue identification, prioritization, and resolution and associated method
US8565937B2 (en) * 2000-09-07 2013-10-22 The Boeing Company System, process and computer program product for issue communication and facilitating issue resolution
US6581067B1 (en) * 2000-09-12 2003-06-17 Uniprise, Inc. Method and system for providing administrative support
US6850988B1 (en) * 2000-09-15 2005-02-01 Oracle International Corporation System and method for dynamically evaluating an electronic commerce business model through click stream analysis
US6871213B1 (en) * 2000-10-11 2005-03-22 Kana Software, Inc. System and method for web co-navigation with dynamic content including incorporation of business rule into web document
US20020123983A1 (en) * 2000-10-20 2002-09-05 Riley Karen E. Method for implementing service desk capability
US20040260790A1 (en) * 2000-12-21 2004-12-23 Ge Medical System Global Technology Company, Llc Method and apparatus for remote or collaborative control of an imaging system
US6950981B2 (en) * 2000-12-29 2005-09-27 International Business Machines Corporation Method and system for providing task information in a place
US20020133392A1 (en) * 2001-02-22 2002-09-19 Angel Mark A. Distributed customer relationship management systems and methods
US7493366B1 (en) * 2001-03-01 2009-02-17 Verizon Laboratories, Inc. System and method for processing customer requests relating to unsolicited commercial email and other service disruptions
US20020143898A1 (en) * 2001-03-27 2002-10-03 Mansfield Michael A. System and method for providing personalized customer support
JP2002340664A (en) * 2001-05-14 2002-11-27 Shimadzu Corp Electronic balance
US7302440B2 (en) * 2001-07-27 2007-11-27 Metatomix, Inc. Methods and apparatus for statistical data analysis and reduction for an enterprise application
US7058637B2 (en) * 2001-05-15 2006-06-06 Metatomix, Inc. Methods and apparatus for enterprise application integration
US6856992B2 (en) 2001-05-15 2005-02-15 Metatomix, Inc. Methods and apparatus for real-time business visibility using persistent schema-less data storage
US6925457B2 (en) * 2001-07-27 2005-08-02 Metatomix, Inc. Methods and apparatus for querying a relational data store using schema-less queries
US7890517B2 (en) * 2001-05-15 2011-02-15 Metatomix, Inc. Appliance for enterprise information integration and enterprise resource interoperability platform and methods
US20030208499A1 (en) * 2002-05-03 2003-11-06 David Bigwood Methods and apparatus for visualizing relationships among triples of resource description framework (RDF) data sets
US20020174170A1 (en) * 2001-05-21 2002-11-21 Serge Ioffe Method and system for distributing messages to agents
WO2002099586A2 (en) * 2001-06-04 2002-12-12 Rhodia, Inc. Virtual advisor
US7110525B1 (en) 2001-06-25 2006-09-19 Toby Heller Agent training sensitive call routing system
US7895350B1 (en) 2001-07-05 2011-02-22 Motive, Inc. N-way data stream splitter
WO2003007148A1 (en) * 2001-07-13 2003-01-23 Cadessa, L.L.C. System and method for managing networks using local intelligent agents
CN1338695A (en) * 2001-07-17 2002-03-06 天津南开戈德集团有限公司 Self-service network system and its operation method
US20030041108A1 (en) * 2001-08-22 2003-02-27 Henrick Robert F. Enhancement of communications by peer-to-peer collaborative web browsing
US20030065727A1 (en) * 2001-09-28 2003-04-03 Capital One Financial Corporation Systems and methods for providing secured electronic messaging
JP2003114875A (en) * 2001-10-05 2003-04-18 Fujitsu Ltd Server machine, client machine, server program, client program, server program storage medium, and client program storage medium
US7120647B2 (en) * 2001-10-30 2006-10-10 General Electric Company Web-based method and system for providing expert information on selected matters
US20030101082A1 (en) * 2001-11-29 2003-05-29 Ge Mortgage Holdings, Llc Systems and methods for managing customer-related communications
US7698162B2 (en) * 2002-02-25 2010-04-13 Xerox Corporation Customer satisfaction system and method
US7372952B1 (en) 2002-03-07 2008-05-13 Wai Wu Telephony control system with intelligent call routing
US7003530B2 (en) * 2002-03-22 2006-02-21 General Motors Corporation Algorithm for selecting audio content
US8280873B1 (en) * 2002-04-17 2012-10-02 Teradata Us, Inc. System for capturing a business context of a user's interaction with a website and method for the same
US20030208497A1 (en) * 2002-05-01 2003-11-06 National Notification Center, Llc Customer relationship management system
US20030237022A1 (en) * 2002-06-21 2003-12-25 Thayer Jennifer J. System and mehod for providing a service log for processor-based devices
US7881964B2 (en) 2002-09-05 2011-02-01 Accenture Global Services Gmbh Computer self-support management
CA2501847A1 (en) * 2002-10-07 2004-04-22 Metatomix, Inc Methods and apparatus for identifying related nodes in a directed graph having named arcs
US7249123B2 (en) * 2002-10-31 2007-07-24 International Business Machines Corporation System and method for building social networks based on activity around shared virtual objects
US7853594B2 (en) 2002-10-31 2010-12-14 International Business Machines Corporation System and method for determining founders of an information aggregate
US7257569B2 (en) * 2002-10-31 2007-08-14 International Business Machines Corporation System and method for determining community overlap
US20040088322A1 (en) * 2002-10-31 2004-05-06 International Business Machines Corporation System and method for determining connections between information aggregates
US7065532B2 (en) * 2002-10-31 2006-06-20 International Business Machines Corporation System and method for evaluating information aggregates by visualizing associated categories
US7103609B2 (en) * 2002-10-31 2006-09-05 International Business Machines Corporation System and method for analyzing usage patterns in information aggregates
US7130844B2 (en) * 2002-10-31 2006-10-31 International Business Machines Corporation System and method for examining, calculating the age of an document collection as a measure of time since creation, visualizing, identifying selectively reference those document collections representing current activity
US7080082B2 (en) * 2002-10-31 2006-07-18 International Business Machines Corporation System and method for finding the acceleration of an information aggregate
US9818136B1 (en) 2003-02-05 2017-11-14 Steven M. Hoffberg System and method for determining contingent relevance
US7676034B1 (en) 2003-03-07 2010-03-09 Wai Wu Method and system for matching entities in an auction
US7519173B2 (en) * 2003-06-24 2009-04-14 International Business Machines Corporation Method for managing resources in a multi-channeled customer service environment
US8211338B2 (en) 2003-07-01 2012-07-03 Transitions Optical, Inc Photochromic compounds
EP1690210A2 (en) * 2003-07-07 2006-08-16 Metatomix, Inc. Surveillance, monitoring and real-time events platform
US20050144252A1 (en) * 2003-12-29 2005-06-30 Microsoft Corporation System and method for managing a dynamic, structured query and integrating it into a desired application
US20050193055A1 (en) * 2004-02-26 2005-09-01 Mark Angel Context sensitive dynamic user interface for customer service agent
US7665063B1 (en) * 2004-05-26 2010-02-16 Pegasystems, Inc. Integration of declarative rule-based processing with procedural programming
US20060136474A1 (en) * 2004-12-21 2006-06-22 Inventec Corporation Customer service automatic answering system and method
US8335704B2 (en) 2005-01-28 2012-12-18 Pegasystems Inc. Methods and apparatus for work management and routing
US20060195352A1 (en) * 2005-02-10 2006-08-31 David Goldberg Method and system for demand pricing of leads
US8874477B2 (en) 2005-10-04 2014-10-28 Steven Mark Hoffberg Multifactorial optimization system and method
US20070156500A1 (en) * 2005-12-30 2007-07-05 Wilfried Merkel Architectural design for sell from stock application software
US8688495B2 (en) * 2005-12-30 2014-04-01 Sap Ag Architectural design for time recording application software
US20070156550A1 (en) * 2005-12-30 2007-07-05 Der Emde Martin V Architectural design for cash and liquidity management application software
US8407664B2 (en) 2005-12-30 2013-03-26 Sap Ag Software model business objects
US8396731B2 (en) * 2005-12-30 2013-03-12 Sap Ag Architectural design for service procurement application software
US20070162494A1 (en) * 2005-12-30 2007-07-12 Thomas Schneider Embedded business process monitoring
US8522194B2 (en) 2005-12-30 2013-08-27 Sap Ag Software modeling
US8321831B2 (en) 2005-12-30 2012-11-27 Sap Ag Architectural design for internal projects application software
US7930681B2 (en) * 2005-12-30 2011-04-19 Sap Ag Service and application management in information technology systems
US8448137B2 (en) * 2005-12-30 2013-05-21 Sap Ag Software model integration scenarios
US8370794B2 (en) * 2005-12-30 2013-02-05 Sap Ag Software model process component
US8402426B2 (en) 2005-12-30 2013-03-19 Sap Ag Architectural design for make to stock application software
US20070164849A1 (en) * 2005-12-30 2007-07-19 Tilmann Haeberle Enterprise software with contextual support
US8676617B2 (en) * 2005-12-30 2014-03-18 Sap Ag Architectural design for self-service procurement application software
US8176483B2 (en) * 2005-12-30 2012-05-08 Sap Ag Software maintenance management
US8380553B2 (en) * 2005-12-30 2013-02-19 Sap Ag Architectural design for plan-driven procurement application software
US20080275713A9 (en) * 2005-12-30 2008-11-06 Shai Alfandary Architectural design for physical inventory application software
US8046755B2 (en) * 2005-12-30 2011-10-25 Sap Ag Deploying software based on a calculated deployment risk level
US20070156835A1 (en) * 2005-12-30 2007-07-05 Sebastian Pulkowski Exchanging data between enterprise computing systems and service provider systems
US8527542B2 (en) * 2005-12-30 2013-09-03 Sap Ag Generating contextual support requests
US7979733B2 (en) * 2005-12-30 2011-07-12 Sap Ag Health check monitoring process
US8316344B2 (en) * 2005-12-30 2012-11-20 Sap Ag Software model deployment units
US20070174731A1 (en) * 2005-12-30 2007-07-26 Tilmann Haeberle Contextual enterprise software support tools
US8326703B2 (en) * 2005-12-30 2012-12-04 Sap Ag Architectural design for product catalog management application software
US8660904B2 (en) * 2005-12-30 2014-02-25 Sap Ag Architectural design for service request and order management application software
US8327319B2 (en) * 2005-12-30 2012-12-04 Sap Ag Software model process interaction
US7599861B2 (en) 2006-03-02 2009-10-06 Convergys Customer Management Group, Inc. System and method for closed loop decisionmaking in an automated care system
US8438119B2 (en) * 2006-03-30 2013-05-07 Sap Ag Foundation layer for services based enterprise software architecture
US20070233575A1 (en) * 2006-03-30 2007-10-04 Arthur Berger Architectural design for strategic sourcing application software
US20070233539A1 (en) * 2006-03-30 2007-10-04 Philipp Suenderhauf Providing human capital management software application as enterprise services
US8396749B2 (en) * 2006-03-30 2013-03-12 Sap Ag Providing customer relationship management application as enterprise services
US8326702B2 (en) * 2006-03-30 2012-12-04 Sap Ag Providing supplier relationship management software application as enterprise services
US20090132232A1 (en) * 2006-03-30 2009-05-21 Pegasystems Inc. Methods and apparatus for implementing multilingual software applications
US8396761B2 (en) * 2006-03-30 2013-03-12 Sap Ag Providing product catalog software application as enterprise services
US8538864B2 (en) * 2006-03-30 2013-09-17 Sap Ag Providing payment software application as enterprise services
US8924335B1 (en) 2006-03-30 2014-12-30 Pegasystems Inc. Rule-based user interface conformance methods
US8442850B2 (en) * 2006-03-30 2013-05-14 Sap Ag Providing accounting software application as enterprise services
US8321832B2 (en) * 2006-03-31 2012-11-27 Sap Ag Composite application modeling
US8300798B1 (en) 2006-04-03 2012-10-30 Wai Wu Intelligent communication routing system and method
US8312416B2 (en) * 2006-04-13 2012-11-13 Sap Ag Software model business process variant types
US7809663B1 (en) * 2006-05-22 2010-10-05 Convergys Cmg Utah, Inc. System and method for supporting the utilization of machine language
US8379830B1 (en) 2006-05-22 2013-02-19 Convergys Customer Management Delaware Llc System and method for automated customer service with contingent live interaction
US8112747B2 (en) * 2006-11-27 2012-02-07 Sap Ag Integrated software support for a distributed business application with seamless backend communications
US8250525B2 (en) 2007-03-02 2012-08-21 Pegasystems Inc. Proactive performance management for multi-user enterprise software systems
US7757126B2 (en) 2007-04-20 2010-07-13 Sap Ag System and method for supporting software
US8209669B2 (en) 2007-04-20 2012-06-26 Sap Ag System and method for supporting software
US8621008B2 (en) 2007-04-26 2013-12-31 Mcafee, Inc. System, method and computer program product for performing an action based on an aspect of an electronic mail message thread
US20090043882A1 (en) * 2007-08-08 2009-02-12 Hibbets Jason S Systems and methods for consolidated service level agreements
US20090043669A1 (en) * 2007-08-08 2009-02-12 Hibbets Jason S Systems and methods for collaborative federation of support
US8199965B1 (en) 2007-08-17 2012-06-12 Mcafee, Inc. System, method, and computer program product for preventing image-related data loss
US20130276061A1 (en) 2007-09-05 2013-10-17 Gopi Krishna Chebiyyam System, method, and computer program product for preventing access to data with respect to a data access attempt associated with a remote data sharing session
US20090112657A1 (en) * 2007-10-26 2009-04-30 Sony Corporation Repository infrastructure to store transaction information for providing customer service
US8560369B2 (en) * 2007-11-01 2013-10-15 Red Hat, Inc. Systems and methods for technical support based on a flock structure
US10282701B2 (en) * 2007-11-20 2019-05-07 Red Hat, Inc. Web-based technical issue assignments based on technical support groups having handled a highest number of technical requests
US8127235B2 (en) 2007-11-30 2012-02-28 International Business Machines Corporation Automatic increasing of capacity of a virtual space in a virtual world
US20090164919A1 (en) 2007-12-24 2009-06-25 Cary Lee Bates Generating data for managing encounters in a virtual world environment
US8671034B2 (en) * 2007-12-31 2014-03-11 Sap Ag Providing human capital management software application as enterprise services
US8447657B2 (en) * 2007-12-31 2013-05-21 Sap Ag Architectural design for service procurement application software
US8401936B2 (en) * 2007-12-31 2013-03-19 Sap Ag Architectural design for expense reimbursement application software
US20090171811A1 (en) * 2007-12-31 2009-07-02 Peter Markus A Architectural Design For Product Catalog Management Application Software
US8671032B2 (en) 2007-12-31 2014-03-11 Sap Ag Providing payment software application as enterprise services
US8315900B2 (en) * 2007-12-31 2012-11-20 Sap Ag Architectural design for self-service procurement application software
US8671033B2 (en) * 2007-12-31 2014-03-11 Sap Ag Architectural design for personnel events application software
US8510143B2 (en) * 2007-12-31 2013-08-13 Sap Ag Architectural design for ad-hoc goods movement software
US20090171758A1 (en) * 2007-12-31 2009-07-02 Shai Alfandary Architectural design for physical inventory application software
US8234633B2 (en) 2008-01-09 2012-07-31 Sap Ag Incident simulation support environment and business objects associated with the incident
US8893285B2 (en) 2008-03-14 2014-11-18 Mcafee, Inc. Securing data using integrated host-based data loss agent with encryption detection
US8819560B2 (en) * 2008-08-04 2014-08-26 International Business Machines Corporation Dispatching events to multiple browser windows/tabs using a single connection
US9077684B1 (en) 2008-08-06 2015-07-07 Mcafee, Inc. System, method, and computer program product for determining whether an electronic mail message is compliant with an etiquette policy
US8065315B2 (en) * 2008-08-27 2011-11-22 Sap Ag Solution search for software support
US7917815B2 (en) * 2008-08-27 2011-03-29 Sap Ag Multi-layer context parsing and incident model construction for software support
US8352338B2 (en) * 2008-09-18 2013-01-08 Sap Ag Architectural design for time recording application software
US20100070395A1 (en) * 2008-09-18 2010-03-18 Andreas Elkeles Architectural design for payroll processing application software
US20100082497A1 (en) * 2008-09-18 2010-04-01 Sap Ag Providing Foundation Application as Enterprise Services
US8326706B2 (en) * 2008-09-18 2012-12-04 Sap Ag Providing logistics execution application as enterprise services
US8818884B2 (en) * 2008-09-18 2014-08-26 Sap Ag Architectural design for customer returns handling application software
US8401928B2 (en) * 2008-09-18 2013-03-19 Sap Ag Providing supplier relationship management software application as enterprise services
US8380549B2 (en) * 2008-09-18 2013-02-19 Sap Ag Architectural design for embedded support application software
US8359218B2 (en) * 2008-09-18 2013-01-22 Sap Ag Computer readable medium for implementing supply chain control using service-oriented methodology
US8595077B2 (en) * 2008-09-18 2013-11-26 Sap Ag Architectural design for service request and order management application software
US8386325B2 (en) * 2008-09-18 2013-02-26 Sap Ag Architectural design for plan-driven procurement application software
US8321250B2 (en) * 2008-09-18 2012-11-27 Sap Ag Architectural design for sell from stock application software
US8315926B2 (en) 2008-09-18 2012-11-20 Sap Ag Architectural design for tax declaration application software
US20100070556A1 (en) * 2008-09-18 2010-03-18 Sap Ag Architectural Design for Data Migration Application Software
US20100070336A1 (en) * 2008-09-18 2010-03-18 Sap Ag Providing Customer Relationship Management Application as Enterprise Services
US8374896B2 (en) * 2008-09-18 2013-02-12 Sap Ag Architectural design for opportunity management application software
US8578265B2 (en) * 2008-10-07 2013-11-05 Bigmachines, Inc. Methods and apparatus for generating a dynamic document
US9524506B2 (en) 2011-10-21 2016-12-20 Bigmachines, Inc. Methods and apparatus for maintaining business rules in a configuration system
US10481878B2 (en) * 2008-10-09 2019-11-19 Objectstore, Inc. User interface apparatus and methods
US20100106552A1 (en) * 2008-10-27 2010-04-29 International Business Machines Corporation On-demand access to technical skills
US8726170B2 (en) * 2008-10-30 2014-05-13 Sap Ag Delivery of contextual information
US8311904B2 (en) * 2008-12-03 2012-11-13 Sap Ag Architectural design for intra-company stock transfer application software
US8321308B2 (en) * 2008-12-03 2012-11-27 Sap Ag Architectural design for manual invoicing application software
US8401908B2 (en) * 2008-12-03 2013-03-19 Sap Ag Architectural design for make-to-specification application software
US8321306B2 (en) * 2008-12-03 2012-11-27 Sap Ag Architectural design for selling project-based services application software
US8738476B2 (en) * 2008-12-03 2014-05-27 Sap Ag Architectural design for selling standardized services application software
US20100153158A1 (en) * 2008-12-11 2010-06-17 Sap Ag Providing project management software application as enterprise services
US20100153239A1 (en) * 2008-12-11 2010-06-17 Sap Ag Providing accounting software application as enterprise services
US8671035B2 (en) * 2008-12-11 2014-03-11 Sap Ag Providing payroll software application as enterprise services
US8843435B1 (en) 2009-03-12 2014-09-23 Pegasystems Inc. Techniques for dynamic data processing
US8468492B1 (en) 2009-03-30 2013-06-18 Pegasystems, Inc. System and method for creation and modification of software applications
US20100281429A1 (en) * 2009-04-30 2010-11-04 Bigmachines, Inc. Methods and apparatus for configuring a product using an array of configuration sets
US9205328B2 (en) 2010-02-18 2015-12-08 Activision Publishing, Inc. Videogame system and method that enables characters to earn virtual fans by completing secondary objectives
US9811799B2 (en) 2010-06-10 2017-11-07 Sony Eletronics, Inc. Distributed customer support credits
US10904178B1 (en) 2010-07-09 2021-01-26 Gummarus, Llc Methods, systems, and computer program products for processing a request for a resource in a communication
US8880487B1 (en) 2011-02-18 2014-11-04 Pegasystems Inc. Systems and methods for distributed rules processing
US9195936B1 (en) 2011-12-30 2015-11-24 Pegasystems Inc. System and method for updating or modifying an application without manual coding
US9973457B2 (en) * 2012-06-26 2018-05-15 Nuance Communications, Inc. Method and apparatus for live chat integration
US10216791B2 (en) * 2012-09-14 2019-02-26 Salesforce.Com System, method and computer program product for adjusting a data query
US10019135B1 (en) 2012-10-18 2018-07-10 Sitting Man, Llc Methods, and computer program products for constraining a communication exchange
US10033672B1 (en) 2012-10-18 2018-07-24 Sitting Man, Llc Methods and computer program products for browsing using a communicant identifier
USD732560S1 (en) * 2013-06-09 2015-06-23 Apple Inc. Display screen or portion thereof with animated graphical user interface
US20150221052A1 (en) * 2014-02-04 2015-08-06 John Howard Messing Automated legal issue spotting and reasoning method
USD780777S1 (en) 2014-04-22 2017-03-07 Google Inc. Display screen with graphical user interface or portion thereof
US9934222B2 (en) 2014-04-22 2018-04-03 Google Llc Providing a thumbnail image that follows a main image
USD781318S1 (en) 2014-04-22 2017-03-14 Google Inc. Display screen with graphical user interface or portion thereof
USD781317S1 (en) 2014-04-22 2017-03-14 Google Inc. Display screen with graphical user interface or portion thereof
US10322351B2 (en) 2014-07-03 2019-06-18 Activision Publishing, Inc. Matchmaking system and method for multiplayer video games
US8903933B1 (en) 2014-07-21 2014-12-02 ConnectWise Inc. Systems and methods for prioritizing and servicing support tickets using a chat session
US10079736B2 (en) 2014-07-31 2018-09-18 Connectwise.Com, Inc. Systems and methods for managing service level agreements of support tickets using a chat session
US10469396B2 (en) 2014-10-10 2019-11-05 Pegasystems, Inc. Event processing with enhanced throughput
US9940409B2 (en) 2014-10-31 2018-04-10 Bank Of America Corporation Contextual search tool
US9922117B2 (en) * 2014-10-31 2018-03-20 Bank Of America Corporation Contextual search input from advisors
US9785304B2 (en) 2014-10-31 2017-10-10 Bank Of America Corporation Linking customer profiles with household profiles
US10118099B2 (en) 2014-12-16 2018-11-06 Activision Publishing, Inc. System and method for transparently styling non-player characters in a multiplayer video game
USD769297S1 (en) * 2015-04-02 2016-10-18 Xerox Corporation Production inkjet printer screen with animated graphical user interface with slider
US10315113B2 (en) 2015-05-14 2019-06-11 Activision Publishing, Inc. System and method for simulating gameplay of nonplayer characters distributed across networked end user devices
US10471348B2 (en) 2015-07-24 2019-11-12 Activision Publishing, Inc. System and method for creating and sharing customized video game weapon configurations in multiplayer video games via one or more social networks
US10698599B2 (en) 2016-06-03 2020-06-30 Pegasystems, Inc. Connecting graphical shapes using gestures
USD837239S1 (en) * 2016-07-06 2019-01-01 Fujifilm Corporation Digital camera display panel with transitional graphical user interface
US10083451B2 (en) 2016-07-08 2018-09-25 Asapp, Inc. Using semantic processing for customer support
EP3482393A4 (en) 2016-07-08 2019-12-18 Asapp, Inc. Automatically responding to a request of a user
US10698647B2 (en) 2016-07-11 2020-06-30 Pegasystems Inc. Selective sharing for collaborative application usage
US10500498B2 (en) 2016-11-29 2019-12-10 Activision Publishing, Inc. System and method for optimizing virtual games
US10109275B2 (en) 2016-12-19 2018-10-23 Asapp, Inc. Word hash language model
US10561945B2 (en) 2017-09-27 2020-02-18 Activision Publishing, Inc. Methods and systems for incentivizing team cooperation in multiplayer gaming environments
US11040286B2 (en) 2017-09-27 2021-06-22 Activision Publishing, Inc. Methods and systems for improved content generation in multiplayer gaming environments
US10974150B2 (en) 2017-09-27 2021-04-13 Activision Publishing, Inc. Methods and systems for improved content customization in multiplayer gaming environments
US10497004B2 (en) 2017-12-08 2019-12-03 Asapp, Inc. Automating communications using an intent classifier
US20190182383A1 (en) * 2017-12-08 2019-06-13 Asapp, Inc. Transfer of customer support to automated processing
US10765948B2 (en) 2017-12-22 2020-09-08 Activision Publishing, Inc. Video game content aggregation, normalization, and publication systems and methods
US10489792B2 (en) 2018-01-05 2019-11-26 Asapp, Inc. Maintaining quality of customer support messages
US11488263B1 (en) 2018-01-31 2022-11-01 Block, Inc. Social network for merchants
US10169315B1 (en) 2018-04-27 2019-01-01 Asapp, Inc. Removing personal information from text using a neural network
US11216510B2 (en) 2018-08-03 2022-01-04 Asapp, Inc. Processing an incomplete message with a neural network to generate suggested messages
US11048488B2 (en) 2018-08-14 2021-06-29 Pegasystems, Inc. Software code optimizer and method
US10747957B2 (en) 2018-11-13 2020-08-18 Asapp, Inc. Processing communications using a prototype classifier
US11551004B2 (en) 2018-11-13 2023-01-10 Asapp, Inc. Intent discovery with a prototype classifier
US11679330B2 (en) 2018-12-18 2023-06-20 Activision Publishing, Inc. Systems and methods for generating improved non-player characters
US11097193B2 (en) 2019-09-11 2021-08-24 Activision Publishing, Inc. Methods and systems for increasing player engagement in multiplayer gaming environments
US11425064B2 (en) 2019-10-25 2022-08-23 Asapp, Inc. Customized message suggestion with user embedding vectors
US11712627B2 (en) 2019-11-08 2023-08-01 Activision Publishing, Inc. System and method for providing conditional access to virtual gaming items
US11524234B2 (en) 2020-08-18 2022-12-13 Activision Publishing, Inc. Multiplayer video games with virtual characters having dynamically modified fields of view
US11351459B2 (en) 2020-08-18 2022-06-07 Activision Publishing, Inc. Multiplayer video games with virtual characters having dynamically generated attribute profiles unconstrained by predefined discrete values
US11567945B1 (en) 2020-08-27 2023-01-31 Pegasystems Inc. Customized digital content generation systems and methods
JP1693301S (en) * 2020-12-24 2021-08-23

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5796393A (en) * 1996-11-08 1998-08-18 Compuserve Incorporated System for intergrating an on-line service community with a foreign service

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5623679A (en) * 1993-11-19 1997-04-22 Waverley Holdings, Inc. System and method for creating and manipulating notes each containing multiple sub-notes, and linking the sub-notes to portions of data objects

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5796393A (en) * 1996-11-08 1998-08-18 Compuserve Incorporated System for intergrating an on-line service community with a foreign service

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8935772B2 (en) 1997-09-26 2015-01-13 Verizon Patent And Licensing Inc. Secure server architecture for web based data management
US9197599B1 (en) 1997-09-26 2015-11-24 Verizon Patent And Licensing Inc. Integrated business system for web based telecommunications management
EP1323100A1 (en) * 2000-09-27 2003-07-02 Cyber'Act Interactive method for communication data to communication network users

Also Published As

Publication number Publication date
AU5489699A (en) 2000-03-14
US6177932B1 (en) 2001-01-23

Similar Documents

Publication Publication Date Title
US6177932B1 (en) Method and apparatus for network based customer service
US6829585B1 (en) Web-based method and system for indicating expert availability
US7194505B2 (en) Shared information processing system and recording medium
US7120647B2 (en) Web-based method and system for providing expert information on selected matters
CA2248409C (en) Geo-enabled personal information manager
US5870744A (en) Virtual people networking
US5819267A (en) Know-how management apparatus, and method
US9292609B2 (en) Predictive information retrieval
JP5063218B2 (en) Internet protocol telephony architecture including information storage and retrieval system to track familiarity
KR100653506B1 (en) System for providing information converted in response to search request
US7353247B2 (en) Querying applications using online messenger service
US6944651B2 (en) Single click synchronization of data from a public information store to a private information store
US6304653B1 (en) Method and apparatus for intelligent data network call setup
US20020169631A1 (en) System and method for providing employers with virtual interviews of potential job candidates
US20080071743A1 (en) Efficient navigation of search results
US20020052913A1 (en) User support apparatus and system using agents
US20080195487A1 (en) Internet shopping assistance technology and e-mail place
MX2011006234A (en) Providing recent history with search results.
USRE45730E1 (en) Process for generating personalized digital directory pages
JP2007220117A (en) Method for relaying one-to-one question and answer through communication network, and system for executing the method
KR20010028733A (en) System for Receiving Queries and Providing Answers thereto
WO2002099697A1 (en) Method and system for displaying the searching result with specified image
JP4961537B2 (en) Q & A system
CA2339217A1 (en) Information access
KR20010000686A (en) Wanted and seeking jobs system using internets and the method thereof

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW SD SL SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase