Analytics driven engagement

Information

  • Patent Grant
  • 8943002
  • Patent Number
    8,943,002
  • Date Filed
    Tuesday, March 6, 2012
    12 years ago
  • Date Issued
    Tuesday, January 27, 2015
    10 years ago
Abstract
Various embodiments relate to an engagement server and a related method of initiating an engagement between an agent device and a user device based on formed and modified engagement rules. In one embodiment, the engagement server can receive one or more third-party analytic reports and use them to form engagement rules that determine when the engagement server initiates an engagement between the agent device and user device. In some embodiments, the engagement server can also receive user interaction data from the user device to modify engagement rules to fit a particular user. In some embodiments, the engagement server can use the third-party analytic reports and/or user interaction data from a plurality of users to form a statistical model. The engagement server may then use the statistical model to form and/or modify the engagement rules.
Description
TECHNICAL FIELD

Various exemplary embodiments disclosed herein relate generally to methods executed on a computer and computer-based apparatus, including computer program products, for an analytic driven engagement.


BACKGROUND

A company can use its website in a variety of ways to communicate information to its customers. For example, a company can configure its website to provide information to a customer before the customer makes a purchasing decision. In other instances, the company can directly provide its products and/or services to its customers through its website, provide customer service through a support network, and/or gather specific information about its potential customers.


In order to implement such a wide array of services (which customers in this day and age have come to expect from Internet companies), many companies must employ large, robust websites and maintain large web presences. One consequence of creating such large and complex websites is that customers many not readily find the information or service they desire. For example, a customer may navigate to a desired location (e.g., web page) on a company's website, yet many not know the appropriate next steps to take once he or she reaches the desired location (e.g., how to complete a purchase transaction, how to compare a displayed product with other products, etc.). It is often difficult to determine when to engage a user of a website (e.g., to provide online chat help, to send coupons, to send advertisements, etc.).


SUMMARY

The methods and apparatus disclosed herein allow a website to engage website users (or to offer engagement to users) when the users may want or need help (e.g., to offer online chat with customer service agents, to provide coupons, etc.). Actions or other properties associated with the user's interaction with the website can be used to decide when the website should engage with a customer (e.g., offered help).


A brief summary of various exemplary embodiments is presented. Some simplifications and omissions may be made in the following summary, which is intended to highlight and introduce some aspects of the various exemplary embodiments, but not limit the scope of the invention. Detailed descriptions of a preferred exemplary embodiment adequate to allow those of ordinary skill in the art to make and use the inventive concepts will follow in the later sections.


In one embodiment, a computerized method for automatically adjusting engagement rules based on user interaction with a website is featured. The method includes a server computer storing a set of engagement rules for a website, wherein each engagement rule defines criteria that, if met, causes the website to engage a user of the website. The method includes the server computer receiving data indicative of a set of users' interactions with the website, wherein the data is generated by a third-party data provider. The method also includes automatically the server computer adjusting one or more generated rules from the set of engagement rules based on the received data.


In another embodiment, a computer program product, tangibly embodied in a non-transitory computer readable medium is featured. The computer program product includes instructions being configured to cause a data processing apparatus to store a set of engagement rules for a website, wherein each engagement rule defines criteria that, if met, causes the website to engage a user of the website. The computer program product includes instructions being configured to cause a data processing apparatus to receive data indicative of a set of users' interactions with the website, wherein the data is generated by a third-party data provider. The computer program product includes instructions being configured to cause a data processing apparatus to automatically adjust one or more generated rules from the set of engagement rules based on the received data.


In another embodiment, an apparatus for automatically adjusting engagement rules based on user interactions with a website is featured. The apparatus comprises a processor and memory. The apparatus is configured to store a set of engagement rules for a website, wherein each engagement rule defines criteria that, if met, causes the website to engage a user of the website. The apparatus is configured receive data indicative of a set of users' interactions with the website, wherein the data is generated by a third-party data provider. The apparatus is configured to automatically adjust one or more generated rules from the set of engagement rules based on the received data.


In other examples, any of the aspects above include one or more of the following features. In some examples, the server computer receives second data indicative of a second set of users' interactions with the website, wherein the second data is generated by a second third-party data provider that is different than the third-party data provider. In some examples, the server computer generates a statistical model based on the received data and the second received data. The received data and the second received data can each comprise one or more parameters. Generating the statistical model can comprise correlating a first parameter from the received data and a second parameter from the second received data using a principal component analysis (PCA).


In some examples, the statistical model can be indicative of user interaction with the website. The received data can comprise a website analytic report. Engaging a user can comprise transmitting a pop-up window to the user. Automatically adjusting can comprise creating a new engagement rule in the set of engagement rules. Automatically adjusting can comprise changing an existing engagement rule in the set of engagement rules.


It should be apparent that, in this manner, various exemplary embodiments enable dynamic engagement between an agent and a user on a website (or other user engagements, such as providing targeted advertisements, providing coupons, etc.). Particularly, by using analytical reports and modeling an agent can engage a user under predefined conditions, which can result in a more meaningful engagement between the agent and user.


The techniques, which include both methods and apparatuses, described herein can provide one or more of the following advantages. The incorporation of one or more third-party analytic tools and analytic reports allows the system to determine when to engage a user (e.g., based on robust statistics) that will more likely result in a successful engagement (e.g., a helpful engagement to the user, an engagement that promotes the sale of products or services, etc.) between agent and user. Automatically integrating such analytic tools with the rest of the engagement system eliminates the need for manual creation and maintenance of engagement rules that define the criterion(s) for when the system engages a user. Other aspects and advantages of the embodiments will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, illustrating the principles of the invention by way of example only.





BRIEF DESCRIPTION OF THE DRAWINGS

In order to better understand various exemplary embodiments, reference is made to the accompanying drawings wherein:



FIG. 1 illustrates an exemplary analytic-driven engagement system;



FIG. 2 illustrates a flowchart of an exemplary method of initiating engagement; and



FIG. 3 illustrates a flowchart of another exemplary method of initiating engagement.





DETAILED DESCRIPTION

Referring now to the drawings, in which like numerals refer to like components or steps, there are disclosed broad aspects of various exemplary embodiments.


In general overview, computerized systems and methods are provided for an analytic-driven engagement system that initiates engagement with a user (e.g., engagement between a customer service agent and the user) based on, at least, analytic reports and/or analytic tools. The analytic reports and tools can be produced both internally and can be received from a third party. An engagement can include, for example, direct communications between an agent and a user (e.g., online text chat, voice chat, video chat, etc.). An engagement can also include other forms of action based on a user's interaction with the website. For example, a user can be presented with instructional text or video (e.g., that is automatically-generated based on the user's actions taken at the website), coupons (e.g., for products offered on the website and/or for products related to the website content), articles, community-created content, social media content (e.g., Facebook, Twitter), etc. An engagement server can monitor a user's activities when connected to a website or webpage. The engagement server, using engagement rules dynamically formed from at least the analytic tools, waits until the engagement rules are satisfied before engaging the user. In some embodiments, the engagement server can form the engagement rules from other users' activity data. In some embodiments, the engagement server can initiate the engagement between an agent and the user through the creation of a chat session on both the user device and agent device that enable direct communication between the user and agent. In some embodiments, the engagement server can initiate another form of initiation, such as providing specific content like an advertisement.



FIG. 1 illustrates an exemplary analytic-driven engagement system 100, which includes a user device 101, a web server 103, a network 107, an engagement server 111, an engagement database (DB) 113, an agent device 115, third-party servers 121A-121B, and third-party databases 123A-123B. The user device 101 includes a web browser 102 that connects to the web server 103. The web browser 102 can also include a tag 104. In the illustrative embodiment, the user device 101 is in communication with the web server 103, while the engagement server 111 is in communication with the engagement DB 113 and the agent device 115. In some embodiments, the engagement server 111 can enable communication between the user device 101 and the agent device 115 through the tag 104 in the web browser 102 (e.g., the tag 104 determines an engagement rule is satisfied, and sets up a chat session between the user of the user device 101 and the agent device 115 through the engagement server 111). In some embodiments, the engagement server 111 can receive information from the tag 104 via the web server 103 and the network 107, where the web server 103 and the network 107 relay the information between the engagement server 111 and the tag 104 (e.g., as illustrated by connection 117).


Network 107 can be, for example, a packet-switching network that is able to forward packets to other devices based on information included in the packet. The network 107 can provide, for example, phone and/or Internet service to various devices like the user device 101 and the agent device 115 in communication with the network 107.


The engagement server 111 can be, for example, a single web server with a processor and memory. In some embodiments, the engagement server 111 can include multiple web servers connected directly or through the network 107. For example, the agent or agent company can improve brand management and/or customer service by connecting its agents with its customers (or users) at what it deems opportune times (e.g., as defined by the engagement rules). Advantageously, the engagement server 111 can receive user interaction data from a particular user device 101 (e.g., from tag 104) and use various engagement rules to determine when to engage with user device 101 (e.g., to initiate an engagement between an agent and a user via the agent device 115 and the user device 101). In some embodiments, the engagement server 111 can retrieve other data, such as user analytics stored in engagement database (DB) 113 to form and/or modify its engagement rules. The engagement server 111 can also store the engagement rules in the engagement database 113. In some embodiments, the engagement server 111 can retrieve one or more third-party analytics, such as third-party analytic reports, from third party databases 123A-123B via third-party servers 121A-121B when forming and/or modifying the stored engagement rules. The engagement server 111 can also provide other software to both the user device 101 and the agent device 115. For example, the engagement server 111 can provide chat software to the user device 101 and the agent device 115 to facilitate a chat session between the user device 101 and the agent device 115.


Engagement database (DB) 113 can be a database in communication with the engagement server 111 that can provide user analytics to the engagement server 111. In some embodiments, the engagement DB 113 can be in communication with the engagement server 111 through a direct connection. In other embodiments, the engagement DB 113 can be in communication with the engagement server 111 through the network 107. In some embodiments, the engagement database 113 stores the engagement rules. In some embodiments, the engagement DB 113 can store web analytics received by the engagement server 111. In some embodiments, the engagement DB 113 can accumulate and store user interaction data the engagement server 111 received from a plurality of user devices 101 over time. In some embodiments, the engagement DB 113 can store statistical models form by the engagement server 111. The engagement server 111 can access the engagement DB 113 when forming and updating engagement rules, statistical models, and accumulated user interaction data. The engagement server 111 can use information stored in the engagement DB 113 with other information, such as third-party web analytics retrieved from other sources when forming or modifying engagement rules and/or statistical models.


Third-Party databases (DBs) 123A-123B can be one or more databases in communication with the engagement server 111 through the network 107 and third-party servers 121A-121B. Each of the third-party servers 121A-121B can be, for example, a single web server with a processor and memory that are controlled by a party other than the user or agent. Third-party DBs 123A-123B can accumulate and store web analytics, which the engagement server 111 can access when forming and modifying its engagement rules and/or statistical models. In some embodiments, the web analytics stored in the third-party DBs 123A-123B can be static web analytic reports. In other embodiments, the third-party DBs can include web analytic reports that are consistently updated by the third-party. In some embodiments, the engagement server 111 can access the static and/or updated web analytic reports stored in one or more of the third-party DBs when forming and modifying its engagement rules, or when forming and modifying its statistical models. For example, the engagement server 111 can connect to the first third-party DB 123A to retrieve a static third-party report, connect to the second third-party DB 123B to retrieve an updated third-party report, and/or connect to the engagement DB 113 to retrieve accumulated user interaction data to form a statistical model for the user.


In some embodiments, the statistical model can be generated using partial-least-squares projections to latent structures, (PLS), principal component analysis (PCA), or a combination of PLS and PCA. Further details of PCA and PLS analysis can be found in “Multi- and Megavariate Data Analysis, Part I, Basic Principles and Applications”, Eriksson et al, Umetrics Academy, January 2006, and “Multi- and Megavariate Data Analysis, Part II, Advanced Applications and Method Extensions”, Eriksson et al., Umetrics Academy, March 2006, the entirety of which are herein incorporated by reference.


PLS is a multivariate analytical tool commonly used to analyze data. PLS is a method for relating two data matrices, X and Y, to each other by a linear multivariate model. In its simplest form, a linear model specifies the relationship between a dependent or response variable y, or a set of response variables Y, and a set of predictor variables X's. For example, the response variable y is a user-specified quality for irregular objects, and the predictor variables X are the measured data for the irregular objects.


A PLS component includes a vector of X-scores t, Y-scores u, weights w and c, and loadings p. PLS components of a PLS model are traditionally calculated using the nonlinear iterative partial least squares (NIPALS) algorithm. There are many variations on the NIPALS algorithm, which consist of a matrix-vector multiplication (e.g., X′y) to generate the weight vector w. The matrix-vector multiplication is computed through a set of vector-vector multiplications xk′×y, to result in scalar results wk.


PLS can be represented graphically. For example, consider a regression application with N observations, 3 X-variables (factors/predictors), and 1 y-variable (response). Here, the dimensions of the X matrix are 3 columns by N observations, and the dimensions of the Y matrix is 1 column by N observations. Because there are two matrices, each row (or each observation of the N observations) corresponds to two points; one point on the X-space for the X matrix and one in the Y-space for the Y matrix. When the data table is graphed for all N observations, there is a cluster of N points in the X-space and a cluster of N points in the Y-space. The first PLS component is a line, or vector, in the X-space which approximates the cluster of points and provides a good correlation with the y-vector. Upon computing the first PLS component, the co-ordinate of an observation i along the first component vector can be obtained by projecting the sample onto the line to achieve the score ti1 of observation i. The scores of all the observations form the first X-score vector t1. A model estimate of y can be determined by multiplying t1 by the weight of the y-vector c1:

ŷ(1)=c1t1  Equation 1

where:

  • ŷ(1) is an estimate of y after one PLS model component;
  • c1 is the weight of the y-vector; and
  • t1 is the first X-score vector.


Usually, one PLS component is insufficient to adequately model the variation in the y-data. A second PLS component is used to expand on the PLS model. The second PLS component is also a line in the X-space, which passes through the origin and is orthogonal to the first PLS component. After computing the second PLS component, a second score vector t2 is achieved, as well as weights c2 and w2:

ŷ(2)=c1t1+c2t2  Equation 2

where:

  • ŷ(2) is an estimate of y after two PLS model components;
  • c1 is the weight of the first y-vector;
  • t1 is the first X-score vector;
  • c2 is the weight of the second y-vector; and
  • t2 is the second X-score vector.


This PLS component generation process is repeated until reaching the desired number of components for the PLS model. Additionally, this can be performed with a single response y or multiple responses Y.


The vector-vector multiplications of the NIPALS algorithm produce similar results to a least squares estimation of a slope of a line through the origin b=(x′y)/(x′x), where x′x is a constant. Further, partial averages of the sorted data set divided into three portions gives a good estimate of b=(yy3−yy1)/(xx3−xx1), where the average of the highest third of y is yy3, the average of the lowest third of y is yy1, the average of the highest third of x is xx3, and the average of the lowest third of x is xx1. While partial averages can be a good estimate of b, partial averages can be affected by outside tails of the distribution. Further, computation of PLS components is limited based on the amount of memory available in the processing system. With large amounts of data storage becoming available at lower prices, the size of data sets are becoming increasingly larger than the computer memory available in the processing system. Consequently PLS processing of large data sets becomes time consuming. Further, standard PLS deflates both the X and Y matrices to speed up the computation with constant vector subtractions.


PCA is a multivariate projection method designed to extract and display the systematic variation in a data matrix X, revealing groups of observations, trends, and outliers. Data matrix X is a matrix of data with N rows (observations) and K columns (variables). The observations can be, for example, analytical samples, chemical compounds or reactions, process time points of a continuous process, batches from a batch process, biological individuals, trials of a DOE-protocol, and other measurements. To characterize the properties of the observations, variables are measured. The variables can be, for example, of spectral origin, of chromatographic origin, or measurements from sensors in a process (e.g., temperatures, flows, pressures, curves, etc.).


In some embodiments, the data are pre-processed (e.g., through scaling and mean-centering, described in further detail below). Once pre-processed (if at all), the first principal component (PC1) is computed, which is the line in the K-dimensional space that best approximates the data in the least squares sense. The line goes through the average point, and each observation can be projected onto the line to calculate the observation's score. The model can be extended with additional principal components. Usually, one principal component is insufficient to model the systematic variation of a data set. The second principal component, for example, is also represented by a line in the K-dimensional space which is orthogonal to the first PC. The line also passes through the average point, and improves the approximation of the X-data as much as possible.


To determine which variables are responsible for the patterns seen among the observations, the principal component loadings are analyzed, which are vectors called p1 and p2. Geometrically, the principal component loadings express the orientation of the model plane in the K-dimensional variable space. The direction of PC1 in relation to the original variables is given by the cosine of the angles for each variable. For example, for three variables, the direction is given by a1, a2, and a3. These values indicate how the original variables (e.g., x1, x2, and x3 for a three variable matrix) load, or contribute to, PC1. A second set of loading coefficients expresses the direction of PC2 in relation to the original variables.


By using PCA a data table X is modeled as:

X=1* x′+T*P′+E  Equation 3

where:

  • 1* x′ represents the variable averages after pre-processing the data, if any;
  • T*P′ models the structure; and
  • E contains noise.


The principal component scores are the columns of the score matrix T (e.g., t1, t2, and t3 for first, second, and third components). These scores are the coordinates of the observations in the model. The scores can be sorted in descending importance (e.g., t1 explains more variation than t2). As discussed above, the meaning of the scores is given by the loadings, which build up the loading matrix P (e.g., loadings of the first, second, and third components are p1, p2, and p3. The loadings demonstrate the magnitude (e.g., large or small correlation) and the manner (e.g., positive or negative correlation) in which the measured variables contribute to the scores.


In some embodiments, the data matrices are preprocessed before performing PCA and/or PLS. For example, when using PLS, one or more of the matrices (e.g., matrix X and/or matrix Y) are transformed, centered, and/or scaled by a preprocessing method. Similarly, prior to PCA, the data can be pre-treated into a form suitable for analysis (e.g., to reshape the data such that important assumptions are better fulfilled). PLS modeling works best when the data are generally symmetrically distributed and have a generally constant error variance. Variables that vary more than ten-fold can be logarithmically transformed before the analysis to remove undesired behavior. Transforming variables can improve the predictive power and interpretability of a multivariate model. For example, a dataset which includes measurements that are outliers may unduly influence model building. Manipulating such measurements in some way prior to data analysis prevents the measurements from exerting a large influence on the model, causing the measurements to dominate over the other measurements. For example, outliers can be removed to minimize the effect that the measurements would have on the model.


To give variables (i.e., columns) of a matrix relatively or approximately equal weight in the subsequent analysis, the data can be column-wise transformed, scaled, and/or centered. Transformations of variables are often used to give them a more symmetrical distribution. For example, logarithmic transformations, negative logarithm scaling, logit scaling, square root scaling, fourth root scaling, inverse scaling, or power transformation scaling can be used.


For many types of data, centering and scaling are intertwined. Centering corresponds to a subtraction of a reference vector, where scaling the variables involves multiplying the variables by a scaling vector. The choice of scaling vector is crucial. In situations where variables of different origin and numerical range are encountered the scaling vector is usually chosen as the inverse spread of the variables. In other situations, such as with process data, the scaling vector may be defined relative to a tolerable spread in the variables.


A scaling vector is a representation of a number of observations on a line such that the positioning of the points is related in some mathematical sense to one or more criteria relevant to the observations. The scaling process involves regulating the length of a coordinate axis in variable space according to a predetermined criteria (e.g., that the length of each coordinate axis be set to the same variance). A common technique for scaling data is referred to as “unit variance,” “UV” scaling, or “auto-scaling.” Unit variance scaling involves calculating a standard deviation for a particular variable from a data set. A scaling weight is calculated as the inverse of the standard deviation. Each value of the variable is multiplied by the scaling weight to determine the scaled variable. After all of the variables in the data matrices have been scaled, each of the variables (i.e., coordinate axes) have unit variance.


In FIG. 1, The web server 103 can be, for example, a single web server with a processor and memory. In other embodiments, the web server 103 can be a plurality of web servers configured to provide web services to a user device 101. The website can provide tag 104 along with website code (e.g., HTML code), comprising code (e.g., JavaScript code) that, when executed by the web browser 102 on the user device 101, monitors user activity of an associated website displayed in the web browser 102. In some embodiments, instead of or in addition to the tag 104, the website provided by the web server 103 can provide an application programming interface (API) that facilitates monitoring user activity, such as the monitoring of keywords in messages, or other data used within the website (e.g., which can be viewed by the user device 101). The API can be an interface implemented by the website that enables other software programs to interact with the website. In some embodiments, the web server 103 can provide a same website viewed on both the user device 101 via the web browser 102 and the agent device 115 (e.g., via a web browser on the agent device 115, not shown). In such instances, the website viewed on the agent device 115 and user device 101 may not be identical.


The user device 101 can be computing devices with a processor and memory that can interact with the website through its web browser 102. For example, the user device 101 can include desktop computers, laptop computer, tablet computers, and/or mobile phones connected to the network 107. A user of the user device 101 can use the user device 101 to connect to the website provided by the web server 103 and can be engaged with an agent device (e.g., agent device 115) through the engagement server 111.


The web browser 102 can be software used by the user device to connect to other devices through the network 107. In some embodiments, the user device can be connected to the web server 103 before connecting to the network 107. In other embodiments, the web server 103 can be connected to the user device 101 through the network 107.


Tag 104 can be a coded tag, such as an HTML tag, that can be included in a web page the web server 103 provides to the user device 101 through the web browser 102. In some embodiments, the tag 104 can be a tag module stored in the memory of the user device 101 that communicates with the web server 103 and/or the engagement server 111 via the connection 117. For example, when the user causes the web browser 102 to load the web page, the web browser 102 processes the tag 104, which causes the web browser 102 to download default tag code (e.g., a JavaScript code file) from the web server 103. In some embodiments, the engagement server 111 can provide the default tag code to the web browser 102. The web browser 102 can receive, process, and execute the default tag code to generate the tag. The default tag code can contain code/instructions that monitor and transmit information indicative of the user's interaction with the web page (e.g., user interaction data) to the web server 103, the engagement server 111, or both. For example, the user interaction data can include mouse clicks, form entries, and Uniform Resource Locator (URL) history. Combinations of one or more user interactions can trigger actions by the engagement server 111, which is described below with reference to FIGS. 2 and 3.


Agent device 115 can be computing devices with a processor and memory that can connect to the engagement server 111 and can be in communication with the user device 101. For example, the agent device 115 can include desktop computers, laptop computers, tablet computers, and/or mobile phones connected to the network 107. The agent using the agent device 115 can use the agent device 115 to connect to the user device through an engagement (e.g., chat, video chat, phone chat, etc.) initiated by the engagement server 111. Once engagement is initiated, the agent device 115 and user device 101 can be in communication with each other through the network 107. This can allow, for example, engagement between the agent and user through interactions such as a live chat session.



FIG. 2 illustrates a flowchart of an exemplary method 200 for initiating engagement with a user (e.g., a user browsing a website). For example, the engagement server 111 can run method 200 to determine whether to connect the agent device 115 to the user device 101. Method 200 starts at step 201 and proceed to step 203, where the engagement server 111 receives and stores engagement rules (e.g., receives and stores them in engagement DB 113). These engagement rules can be rules for determining when (e.g., based on certain user interactions with a website, based on the passage of a preconfigured amount of time, etc.) to connect the agent device 115 to the user device 101 for direct engagement (or mediated engagement), or for the web server 103 or the engagement server 111 to provide specific content to the user device 101 (e.g., a coupon, a targeted advertisement, etc.). For example, an engagement rule can be configured such that the engagement server 111 initiates a chat session between the agent device 115 and the user device 101 when the user device 101 has been idle on the same web page within a website for a specified period. In some embodiments, the engagement rule can be generated based on previous third-party analytics. For example, the engagement server 111 can retrieve one or more third-party analytic reports from third-party databases 123A-123B, which can indicate that users have a higher bounce rate once they reach a specific web page (e.g., a “FAQ” or “Help” web page). The engagement server 111 can then create and store an engagement rule that includes a shortened timer when a user device 101 is visiting one of these specific, “high-bounce” web pages.


The engagement server 111 can then proceed to step 205, where it receives user interaction data from the user device 101. For example, the tag 104 included in the user device 101 (e.g., downloaded from web server 103) can track and record user interaction data within the web browser 102. In some embodiments, the tag 104 sends the user interaction data to the web server 103, which can then send the user interaction data through the network 107 to the engagement server 111. In some embodiments, the tag 104 sends the user interaction data directly to the engagement server via connection 117. In some embodiments, the tag 104 can send the user interaction data to the engagement server 111 in packets at standard intervals, where the engagement server 111 can accrue the packets of data. In other embodiments, the tag 104 can wait for triggers to send user interaction data to the engagement server 111. This can, for example, help reduce the volume of user interaction data sent to the engagement server 111.


After receiving the user interaction data, the engagement server 111 can then proceed to step 207, where it can adjust the engagement rules. In some embodiments, the engagement server 111 can adjust the previously-stored engagement rules to, for example, trigger based on different conditions. For example, the engagement server 111 in step 205 may receive user interaction data that indicates that the user is spending longer-than-average times on each webpage before traversing to another page within the website. The engagement server 111 can then adjust engagement rule to have a longer trigger time so that the engagement server 111 initiates an engagement between the agent device 115 and the user device 101 after a longer period (e.g., to prevent initiating an engagement before a user may need help).


In step 209, the engagement server 111 determines whether it has received data indicative of an engagement rule being satisfied. In some embodiments, the engagement server 111 can monitor the user interaction data received in step 205 and compare the user interaction data against a plurality of engagement rules, initiating an engagement between the agent device 115 and the user device 101 when the conditions of any of the plurality of engagement rules is satisfied. For example, the engagement server 111 can be using an engagement rule that waits until a user has been on a specific web page (e.g., an FAQ page) for at least a specified duration. When the engagement server 111 reviews the received user interaction data to determine that the user has been on the specific web page for longer than the specified duration, the engagement server may then proceed to step 211 and initiate an engagement between with user device 101 (e.g., present the user device 101 with a popup, set up a service session between the user device 101 and the agent device 115 (e.g., a chat session, a video session, etc.), etc.). Otherwise, the engagement server 111 can loop back to step 209 (e.g., to analyze newly received user interaction data) to determine whether any of its engagement rules have been satisfied.


In step 211, the engagement server 111 can initiate an engagement with the user. For example, the engagement server 111 can initiate a chat session between the agent and the user via the agent device 115 and the user device 101. In some embodiments, the engagement server 111 can initiate an engagement with the user through other means, such as providing additional text or video instructions based on the engagement rule satisfied. For example, the engagement server 111 can monitor an engagement rule regarding a user comparing two or more similar products. Once the engagement server 111 determines that the comparison engagement rule has been satisfied, the engagement server 111 can provide a stored video comparison of the two or more products. In some embodiments, the engagement server can use other means through JavaScript and HTML to engage with the user device 101. This can include, for example, providing to the web browser 102 a banner, a tool-tip, hover-over text, and similar methods to provide more information to the user. Once the engagement has been initiated, the engagement server 111 can stop method 200 at step 213.



FIG. 3 illustrates a flowchart of another exemplary method of initiating engagement. Similar to the method 200 (e.g., implemented by the engagement server 111), the engagement server 111 can implement method 300 to incorporate web analytics from various sources along with received user interaction data to determine whether to initiate an engagement with the user device 101. Method 300 begins at step 301 and proceeds to step 303, where the engagement server 111 receives and stores one or more engagement rules. Similar to step 203, the engagement server 111 can receive one or more engagement rules that may indicate when to initiate an engagement with the user device 101 and the agent device 115. In some embodiments, the engagement server 111 can incorporate one or more third-party analytics, such as multiple third-party analytic reports, from one or more third-party databases 123A-123B via third-party servers 121A-121B.


In step 305, the engagement server 111 can receive user interaction data from a plurality of user devices similar to the user device 101 in FIG. 1. Similar to step 205 in method 200, the engagement server 111 can receive data that indicates how a particular user is interacting with the site. In step 305, the engagement server 111 can receive user interaction data from a plurality of user devices 101, such as simultaneously receiving data from multiple user devices 101 in parallel. In some embodiments, the engagement server 111 can accumulate the user interaction data from the plurality of users and store this data for later use. The engagement server 111 can track different data for different individual users; this data may still be used together by the engagement server 111 in later use.


The engagement server 111 can then proceed from step 305 and proceed to step 306, where the engagement server 111 generates a statistical model based on the accumulated user interaction data. In some embodiments, the engagement server can use various third-party analytics received from the plurality of third-party databases 123A-123B, in addition to stored user interaction data and the user interaction data received in step 305. The engagement server 111 can form the statistical model to create a “model” user profile, for example, that can represent the expected actions of a typical, default user. In such instances, the engagement server 111 bases its engagement decisions on the default statistical profile that can be constantly updated as the engagement server 111 receives new user interaction data. In some embodiments, the engagement server 111 can use the statistical model to form a plurality of user profiles that it may use to model each of the plurality of user devices for which it is receiving user interaction data.


After creating the statistical model, the engagement server 111 can then proceed to step 307, where it can adjust the engagement rules based on the received user interaction data. In some embodiments, the engagement server 111 can use the user interaction data to adjust the engagement rules. In other embodiments, the engagement server 111 can first use the statistical model to adjust the engagement rules and subsequently use the user interaction data to further adjust the engagement rules. The engagement server 111 may act in a similar manner to that of step 207, as the engagement server 111 can use the user interaction data along with the statistical model to modify the previously received and stored engagement rules so that the engagement server 111 initiates an engagement between the agent device 115 and the user device 101 at more opportune times.


In order to determine whether it is an opportune time to initiate an engagement between the user device 101 and the agent device 115, the engagement server 111 may proceed to step 309, where the engagement server 111 determines whether it has received user interaction data from a user device 101 indicative of any of the engagement rules being satisfied. In some embodiments, the engagement server 111 can constantly monitor multiple user devices 101 and can determine whether one of the plurality of user devices 101 satisfied its conditions for engagement. If not, the engagement server 111 can loop back to step 309 and wait until a condition is satisfied.


When a condition is satisfied, the engagement server 111 can proceed to step 311, where the engagement server 111 initiates an engagement with the user device 101. Similar to step 211, the engagement server 111 can initiate direct communication, such as, for example, a text or video chat session, between an agent and user via the agent device 115 and the user device 101. Once the engagement server 111 successfully initiates an engagement with the user device 101, it may proceed to step 313 and end method 300.


The above-described computerized methods and apparatuses can be implemented in digital and/or analog electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. The implementation can be as a computer program product, i.e., a computer program tangibly embodied in a machine-readable storage device, for execution by, or to control the operation of, a data processing apparatus, e.g., a programmable processor, a computer, and/or multiple computers. A computer program can be written in any form of computer or programming language, including source code, compiled code, interpreted code and/or machine code, and the computer program can be deployed in any form, including as a stand-alone program or as a subroutine, element, or other unit suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one or more sites.


The computerized method steps can be performed by one or more processors executing a computer program to perform functions of the invention by operating on input data and/or generating output data. Method steps can also be performed by, and an apparatus can be implemented as, special purpose logic circuitry, e.g., a FPGA (field programmable gate array), a FPAA (field-programmable analog array), a CPLD (complex programmable logic device), a PSoC (Programmable System-on-Chip), ASIP (application-specific instruction-set processor), or an ASIC (application-specific integrated circuit). Subroutines can refer to portions of the computer program and/or the processor/special circuitry that implement one or more functions.


Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital or analog computer. Generally, a processor receives instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and/or data. Memory devices, such as a cache, can be used to temporarily store data. Memory devices can also be used for long-term data storage. Generally, a computer also includes, or is operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. A computer can also be operatively coupled to a communications network in order to receive instructions and/or data from the network and/or to transfer instructions and/or data to the network. Computer-readable storage devices suitable for embodying computer program instructions and data include all forms of volatile and non-volatile memory, including by way of example semiconductor memory devices, e.g., DRAM, SRAM, EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and optical disks, e.g., CD, DVD, HD-DVD, and Blu-ray disks. The processor and the memory can be supplemented by and/or incorporated in special purpose logic circuitry.


To provide for interaction with a user, the above described techniques can be implemented on a computer in communication with a display device, e.g., a CRT (cathode ray tube), plasma, or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse, a trackball, a touchpad, or a motion sensor, by which the user can provide input to the computer (e.g., interact with a user interface element). Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, and/or tactile input.


The above described techniques can be implemented in a distributed computing system that includes a back-end component. The back-end component can, for example, be a data server, a middleware component, and/or an application server. The above described techniques can be implemented in a distributed computing system that includes a front-end component. The front-end component can, for example, be a client computer having a graphical user interface, a Web browser through which a user can interact with an example implementation, and/or other graphical user interfaces for a transmitting device. The above described techniques can be implemented in a distributed computing system that includes any combination of such back-end, middleware, or front-end components.


The computing system can include clients and servers. A client and a server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.


The components of the computing system can be interconnected by any form or medium of digital or analog data communication (e.g., a communication network). Examples of communication networks include circuit-based and packet-based networks. Packet-based networks can include, for example, the Internet, a carrier internet protocol (IP) network (e.g., local area network (LAN), wide area network (WAN), campus area network (CAN), metropolitan area network (MAN), home area network (HAN)), a private IP network, an IP private branch exchange (IPBX), a wireless network (e.g., radio access network (RAN), 802.11 network, 802.16 network, general packet radio service (GPRS) network, HiperLAN), and/or other packet-based networks. Circuit-based networks can include, for example, the public switched telephone network (PSTN), a private branch exchange (PBX), a wireless network (e.g., RAN, bluetooth, code-division multiple access (CDMA) network, time division multiple access (TDMA) network, global system for mobile communications (GSM) network), and/or other circuit-based networks.


Devices of the computing system and/or computing devices can include, for example, a computer, a computer with a browser device, a telephone, an IP phone, a mobile device (e.g., cellular phone, personal digital assistant (PDA) device, laptop computer, electronic mail device), a server, a rack with one or more processing cards, special purpose circuitry, and/or other communication devices. The browser device includes, for example, a computer (e.g., desktop computer, laptop computer) with a world wide web browser (e.g., Microsoft® Internet Explorer® available from Microsoft Corporation, Mozilla® Firefox available from Mozilla Corporation). A mobile computing device includes, for example, a Blackberry®. IP phones include, for example, a Cisco® Unified IP Phone 7985G available from Cisco System, Inc, and/or a Cisco® Unified Wireless Phone 7920 available from Cisco System, Inc.


One skilled in the art will realize the invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. The foregoing embodiments are therefore to be considered in all respects illustrative rather than limiting of the invention described herein. Scope of the invention is thus indicated by the appended claims, rather than by the foregoing description, and all changes that come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein.

Claims
  • 1. A computer-implemented method comprising: accessing a set of engagement rules defined based on data representing interactions with a website, wherein each of the engagement rules defines conditions for providing web-based content;accessing historical interaction data representing previous interactions with the website, the previous interactions made at a communications device;accessing an analytic report representing trends in internet usage amongst a group of website visitors;generating a statistical model based on the historical interaction data and the analytic report, wherein, when the statistical model is generated using principal component analysis, the historical interaction data is modeled as: X=1*x′+T*P′+E,
  • 2. The method of claim 1, wherein the historical interaction data is generated by a tag module operating on the first communications device.
  • 3. The method of claim 1, wherein the engagement includes a chat conversation involving the computing device.
  • 4. The method of claim 1, wherein the method is performed by an engagement server.
  • 5. The method of claim 1, wherein accessing the analytic report includes obtaining the analytic report from a third-party database.
  • 6. The method of claim 1, wherein at least one of the conditions is defined with respect to time spent interacting with a website.
  • 7. A system comprising: a processor configured to: access a set of engagement rules defined based on data representing interactions with a website, wherein each of the engagement rules defines conditions for providing web-based content;access historical interaction data representing previous interactions with the website, the previous interactions made at a communications device;access an analytic report representing trends in internet usage amongst a group of website visitors;generate a statistical model based on the historical interaction data and the analytic report, wherein, when the statistical model is generated using principal component analysis, the historical interaction data is modeled as: X=1*x′+T*P′+E, wherein: 1* x′ represents variable averages or percentile values after pre-processing the historical interaction data;T*P′ models a structure; andE contains noise;access data representing an ongoing visit to the website, the ongoing visit occurring at the communications device, wherein accessing data representing an ongoing website visit includes: making a classification decision by classifying the ongoing website visit using the statistical model; andupdating an engagement rule of the set based on the classification decision;access additional data representing the website visit, wherein accessing the additional data includes determining that the additional data satisfies a condition defined by the updated engagement rule; andinitiate an engagement on the website, in response to determining that the additional data satisfies the condition defined by the updated engagement rule.
  • 8. The system of claim 7, wherein the historical interaction data is generated by a tag module operating on the first communications device.
  • 9. The system of claim 7, wherein the engagement includes a chat conversation involving the computing device.
  • 10. The system of claim 7, wherein the method is performed by an engagement server.
  • 11. The system of claim 7, wherein accessing the analytic report includes obtaining the analytic report from a third-party database.
  • 12. The system of claim 7, wherein at least one of the conditions is defined with respect to time spent interacting with a website.
  • 13. A computer-program product tangibly embodied in a non-transitory machine-readable storage medium having instructions stored thereon, the instructions operable to cause a data processing apparatus to perform operations including: accessing a set of engagement rules defined based on data representing interactions with a website, wherein each of the engagement rules defines conditions for providing web-based content;accessing historical interaction data representing previous interactions with the website, the previous interactions made at a communications device;accessing an analytic report representing trends in internet usage amongst a group of website visitors;generating a statistical model based on the historical interaction data and the analytic report, wherein, when the statistical model is generated using principal component analysis, the historical interaction data is modeled as: X=1*x′+T*P′+E, wherein: 1* x′ represents variable averages or percentile values after pre-processing the historical interaction data;T*P′ models a structure; andE contains noise;accessing data representing an ongoing visit to the website, the ongoing visit occurring at the communications device, wherein accessing data representing an ongoing website visit includes: making a classification decision by classifying the ongoing website visit using the statistical model; andupdating an engagement rule of the set based on the classification decision;accessing additional data representing the website visit, wherein accessing the additional data includes determining that the additional data satisfies a condition defined by the updated engagement rule; andinitiating an engagement on the website, in response to determining that the additional data satisfies the condition defined by the updated engagement rule.
  • 14. The method of claim 13, wherein the historical interaction data is generated by a tag module operating on the first communications device.
  • 15. The method of claim 13, wherein the engagement includes a chat conversation involving the computing device.
  • 16. The method of claim 13, wherein the method is performed by an engagement server.
  • 17. The method of claim 13, wherein accessing the analytic report includes obtaining the analytic report from a third-party database.
  • 18. The method of claim 13, wherein at least one of the conditions is defined with respect to time spent interacting with a website.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of and priority under 35 U.S.C. §119(e) to U.S. Provisional Application No. 61/632,815, filed on Feb. 10, 2012, entitled “Analytic Driven Engagement,” the entire disclosure of which is incorporated herein by reference in its entirety.

US Referenced Citations (488)
Number Name Date Kind
4881261 Oliphant et al. Nov 1989 A
5187735 Herrero Garcia et al. Feb 1993 A
5206903 Kohler et al. Apr 1993 A
5208748 Flores et al. May 1993 A
5235519 Miura Aug 1993 A
5239462 Jones et al. Aug 1993 A
5262941 Saladin et al. Nov 1993 A
5289371 Abel et al. Feb 1994 A
5319542 King et al. Jun 1994 A
5351186 Bullock et al. Sep 1994 A
5372507 Goleh Dec 1994 A
5375055 Togher et al. Dec 1994 A
5387783 Mihm et al. Feb 1995 A
5450537 Hirai et al. Sep 1995 A
5517405 McAndrew et al. May 1996 A
5563805 Arbuckle et al. Oct 1996 A
5572643 Judson Nov 1996 A
5581702 McArdle et al. Dec 1996 A
5583763 Atcheson et al. Dec 1996 A
5590038 Pitroda Dec 1996 A
5592378 Cameron et al. Jan 1997 A
5611052 Dykstra et al. Mar 1997 A
5636346 Saxe Jun 1997 A
5664115 Fraser Sep 1997 A
5668953 Sloo Sep 1997 A
5678002 Fawcett et al. Oct 1997 A
5694163 Harrison Dec 1997 A
5696907 Tom Dec 1997 A
5699526 Siefert Dec 1997 A
5704029 Wright Dec 1997 A
5710887 Chelliah et al. Jan 1998 A
5715402 Popolo Feb 1998 A
5724155 Saito Mar 1998 A
5724522 Kagami et al. Mar 1998 A
5727048 Hiroshima et al. Mar 1998 A
5727163 Bezos Mar 1998 A
5732400 Mandler et al. Mar 1998 A
5745654 Titan Apr 1998 A
5748755 Johnson et al. May 1998 A
5758328 Giovannoli May 1998 A
5760771 Blonder et al. Jun 1998 A
5761640 Kalyanswamy et al. Jun 1998 A
5761649 Hill Jun 1998 A
5764916 Busey et al. Jun 1998 A
5765142 Allred et al. Jun 1998 A
5774869 Toader Jun 1998 A
5774870 Storey Jun 1998 A
5774882 Keen et al. Jun 1998 A
5774883 Andersen et al. Jun 1998 A
5778164 Watkins et al. Jul 1998 A
5784568 Needham Jul 1998 A
5793365 Tang et al. Aug 1998 A
5794207 Walker et al. Aug 1998 A
5796393 MacNaughton et al. Aug 1998 A
5797133 Jones et al. Aug 1998 A
5799151 Hoffer Aug 1998 A
5805159 Bertram et al. Sep 1998 A
5806043 Toader Sep 1998 A
5812769 Graber et al. Sep 1998 A
5815663 Uomini Sep 1998 A
5818907 Mahoney et al. Oct 1998 A
5819029 Edwards et al. Oct 1998 A
5819235 Tamai et al. Oct 1998 A
5819236 Josephson Oct 1998 A
5819291 Haimowitz et al. Oct 1998 A
5825869 Brooks et al. Oct 1998 A
5826241 Stein et al. Oct 1998 A
5826244 Huberman Oct 1998 A
5828839 Moncreiff Oct 1998 A
5832465 Tom Nov 1998 A
5835087 Herz et al. Nov 1998 A
5838682 Dekelbaum et al. Nov 1998 A
5838910 Domenikos et al. Nov 1998 A
5839117 Cameron et al. Nov 1998 A
5850517 Verkler et al. Dec 1998 A
5852809 Abel et al. Dec 1998 A
5857079 Claus et al. Jan 1999 A
5859974 McArdle et al. Jan 1999 A
5862330 Anupam et al. Jan 1999 A
5866889 Weiss et al. Feb 1999 A
5870721 Norris Feb 1999 A
5878403 DeFrancesco et al. Mar 1999 A
5895454 Harrington Apr 1999 A
5903641 Tonisson May 1999 A
5907677 Glenn et al. May 1999 A
5911135 Atkins Jun 1999 A
5916302 Dunn et al. Jun 1999 A
5918014 Robinson Jun 1999 A
5924082 Silverman et al. Jul 1999 A
5930776 Dykstra et al. Jul 1999 A
5940811 Norris Aug 1999 A
5940812 Tengel et al. Aug 1999 A
5943416 Gisby et al. Aug 1999 A
5943478 Aggarwal et al. Aug 1999 A
5945989 Freishtat et al. Aug 1999 A
5948061 Merriman et al. Sep 1999 A
5950179 Buchanan et al. Sep 1999 A
5956693 Geerlings Sep 1999 A
5958014 Cave Sep 1999 A
5960411 Hartman et al. Sep 1999 A
5963625 Kawecki et al. Oct 1999 A
5963635 Szlam Oct 1999 A
5966699 Zandi Oct 1999 A
5970475 Barnes et al. Oct 1999 A
5970478 Walker et al. Oct 1999 A
5974396 Anderson Oct 1999 A
5974446 Sonnenrich et al. Oct 1999 A
5987434 Libman Nov 1999 A
5991740 Messer Nov 1999 A
5995947 Fraser et al. Nov 1999 A
6000832 Franklin et al. Dec 1999 A
6003013 Boushy Dec 1999 A
6009410 LeMole et al. Dec 1999 A
6014644 Erickson Jan 2000 A
6014645 Cunningham Jan 2000 A
6014647 Nizzari Jan 2000 A
6016504 Arnold et al. Jan 2000 A
6026370 Jermyn Feb 2000 A
6028601 Machiraju et al. Feb 2000 A
6029141 Bezos et al. Feb 2000 A
6029149 Dykstra et al. Feb 2000 A
6029890 Austin et al. Feb 2000 A
6044146 Gisby et al. Mar 2000 A
6044360 Picciallo Mar 2000 A
6049784 Weatherly et al. Apr 2000 A
6052447 Golden Apr 2000 A
6052730 Felciano Apr 2000 A
6055573 Gardenswartz et al. Apr 2000 A
6058428 Wang et al. May 2000 A
6061658 Chou et al. May 2000 A
6064987 Walker et al. May 2000 A
6070149 Tavor et al. May 2000 A
6073112 Geerlings Jun 2000 A
6076100 Cottrille et al. Jun 2000 A
6078892 Anderson et al. Jun 2000 A
6084585 Kraft et al. Jul 2000 A
6085126 Mellgren, III et al. Jul 2000 A
6085195 Hoyt et al. Jul 2000 A
6088686 Walker et al. Jul 2000 A
6105007 Norris Aug 2000 A
6112190 Fletcher et al. Aug 2000 A
6119101 Peckover Sep 2000 A
6119103 Basch et al. Sep 2000 A
6131087 Luke et al. Oct 2000 A
6131095 Low et al. Oct 2000 A
6134318 O'Neil Oct 2000 A
6134530 Bunting et al. Oct 2000 A
6134532 Lazarus et al. Oct 2000 A
6134533 Shell Oct 2000 A
6134548 Gottsman et al. Oct 2000 A
6138139 Beck et al. Oct 2000 A
6141653 Conklin et al. Oct 2000 A
6144991 England Nov 2000 A
6163607 Bogart et al. Dec 2000 A
6167395 Beck et al. Dec 2000 A
6170011 Macleod Beck et al. Jan 2001 B1
6173053 Bogart et al. Jan 2001 B1
6182050 Ballard Jan 2001 B1
6182124 Lau et al. Jan 2001 B1
6185543 Galperin et al. Feb 2001 B1
6189003 Leal Feb 2001 B1
6192319 Simonson Feb 2001 B1
6192380 Light et al. Feb 2001 B1
6199079 Gupta et al. Mar 2001 B1
6202053 Christiansen et al. Mar 2001 B1
6202155 Tushie et al. Mar 2001 B1
6208979 Sinclair Mar 2001 B1
6222919 Hollatz et al. Apr 2001 B1
6236975 Boe et al. May 2001 B1
6240396 Walker et al. May 2001 B1
6249795 Douglis Jun 2001 B1
6262730 Horvitz Jul 2001 B1
6267292 Walker et al. Jul 2001 B1
6272506 Bell Aug 2001 B1
6282284 Dezonno et al. Aug 2001 B1
6285983 Jenkins Sep 2001 B1
6289319 Lockwood Sep 2001 B1
6292786 Deaton Sep 2001 B1
6295061 Park et al. Sep 2001 B1
6298348 Eldering Oct 2001 B1
6311169 Duhon Oct 2001 B2
6311178 Bi et al. Oct 2001 B1
6324524 Lent et al. Nov 2001 B1
6327574 Kramer et al. Dec 2001 B1
6330546 Gopinathan et al. Dec 2001 B1
6334110 Walter Dec 2001 B1
6338066 Martin et al. Jan 2002 B1
6346952 Shtivelman Feb 2002 B1
6349290 Horowitz et al. Feb 2002 B1
6356909 Spencer Mar 2002 B1
6374230 Walker et al. Apr 2002 B1
6377936 Henrick et al. Apr 2002 B1
6381640 Beck Apr 2002 B1
6385594 Lebda et al. May 2002 B1
6393479 Glommen et al. May 2002 B1
6405181 Lent et al. Jun 2002 B2
6438526 Dykes et al. Aug 2002 B1
6449358 Anisimov Sep 2002 B1
6449646 Sikora et al. Sep 2002 B1
6463149 Jolissaint et al. Oct 2002 B1
6477533 Schiff et al. Nov 2002 B2
6507851 Fujiwara et al. Jan 2003 B1
6510418 Case et al. Jan 2003 B1
6510427 Bossemeyer, Jr. et al. Jan 2003 B1
6516421 Peters Feb 2003 B1
6519628 Locascio Feb 2003 B1
6535492 Shtivelman Mar 2003 B2
6542936 Mayle et al. Apr 2003 B1
6546372 Lauffer Apr 2003 B2
6549919 Lambert et al. Apr 2003 B2
6567791 Lent et al. May 2003 B2
6571236 Ruppelt May 2003 B1
6597377 MacPhai Jul 2003 B1
6606744 Mikurak Aug 2003 B1
6618746 Desai et al. Sep 2003 B2
6622131 Brown et al. Sep 2003 B1
6622138 Bellamkonda Sep 2003 B1
6662215 Moskowitz et al. Dec 2003 B1
6665395 Busey et al. Dec 2003 B1
6671818 Mikurak Dec 2003 B1
6691151 Cheyer et al. Feb 2004 B1
6691159 Grewal et al. Feb 2004 B1
6701441 Balasubramaniam et al. Mar 2004 B1
6718313 Lent et al. Apr 2004 B1
6725210 Key Apr 2004 B1
6741995 Chen May 2004 B1
6760429 Hung et al. Jul 2004 B1
6766302 Bach Jul 2004 B2
6771766 Shafiee et al. Aug 2004 B1
6795812 Lent et al. Sep 2004 B1
6804659 Graham et al. Oct 2004 B1
6826594 Pettersen Nov 2004 B1
6829585 Grewal et al. Dec 2004 B1
6836768 Hirsh Dec 2004 B1
6839680 Liu Jan 2005 B1
6850896 Kelman et al. Feb 2005 B1
6865267 Dezono Mar 2005 B2
6892347 Williams May 2005 B1
6904408 McCarthy et al. Jun 2005 B1
6920434 Cossette Jul 2005 B1
6922705 Northrup Jul 2005 B1
6925441 Jones Aug 2005 B1
6925442 Shapira et al. Aug 2005 B1
6950983 Snavely Sep 2005 B1
6965868 Bednarek Nov 2005 B1
6981028 Rawat et al. Dec 2005 B1
6993557 Yen Jan 2006 B1
7003476 Samra et al. Feb 2006 B1
7039599 Merriman et al. May 2006 B2
7051273 Holt et al. May 2006 B1
7076443 Emens et al. Jul 2006 B1
7085682 Heller et al. Aug 2006 B1
7092959 Chen Aug 2006 B2
7106850 Campbell et al. Sep 2006 B2
7143063 Lent et al. Nov 2006 B2
7181492 Wen et al. Feb 2007 B2
7200614 Reid et al. Apr 2007 B2
7242760 Shires Jul 2007 B2
7243109 Omega et al. Jul 2007 B2
7251648 Chaudhuri et al. Jul 2007 B2
7287000 Boyd et al. Oct 2007 B2
7313575 Carr et al. Dec 2007 B2
7337127 Smith et al. Feb 2008 B1
7346576 Lent et al. Mar 2008 B2
7346604 Bharat et al. Mar 2008 B1
7346606 Bharat Mar 2008 B2
7370002 Heckerman et al. May 2008 B2
7376603 Mayr et al. May 2008 B1
7403973 Wilsher et al. Jul 2008 B2
7424363 Cheng Sep 2008 B2
7523191 Thomas et al. Apr 2009 B1
7526439 Freishtat et al. Apr 2009 B2
7536320 McQueen et al. May 2009 B2
7552080 Willard et al. Jun 2009 B1
7590550 Schoenberg Sep 2009 B2
7630986 Herz et al. Dec 2009 B1
7650381 Peters Jan 2010 B2
7657465 Freishtat et al. Feb 2010 B2
7689924 Schneider et al. Mar 2010 B1
7702635 Horvitz et al. Apr 2010 B2
7716322 Benedikt et al. May 2010 B2
7734503 Agarwal et al. Jun 2010 B2
7734632 Wang Jun 2010 B2
7739149 Freishtat et al. Jun 2010 B2
7818340 Warren Oct 2010 B1
7827128 Karlsson et al. Nov 2010 B1
7865457 Ravin et al. Jan 2011 B2
7877679 Ozana Jan 2011 B2
7958066 Pinckney et al. Jun 2011 B2
7966564 Catlin et al. Jun 2011 B2
7975020 Green et al. Jul 2011 B1
8010422 Lascelles et al. Aug 2011 B1
8185544 Oztekin et al. May 2012 B2
8260846 Lahav Sep 2012 B2
8266127 Mattox et al. Sep 2012 B2
8386340 Feinstein Feb 2013 B1
8392580 Allen et al. Mar 2013 B2
20010011245 Duhon Aug 2001 A1
20010011246 Tammaro Aug 2001 A1
20010011262 Hoyt et al. Aug 2001 A1
20010011282 Katsumata et al. Aug 2001 A1
20010013009 Greening Aug 2001 A1
20010014877 Defrancesco et al. Aug 2001 A1
20010025249 Tokunaga Sep 2001 A1
20010027436 Tenembaum Oct 2001 A1
20010032140 Hoffman Oct 2001 A1
20010032244 Neustel Oct 2001 A1
20010034689 Heilman Oct 2001 A1
20010054041 Chang Dec 2001 A1
20010054064 Kannan Dec 2001 A1
20010056405 Muyres Dec 2001 A1
20020002491 Whitfield Jan 2002 A1
20020004735 Gross Jan 2002 A1
20020010625 Smith et al. Jan 2002 A1
20020016731 Kupersmit Feb 2002 A1
20020023051 Kunzle et al. Feb 2002 A1
20020026351 Coleman Feb 2002 A1
20020029188 Schmid Mar 2002 A1
20020029267 Sankuratripati et al. Mar 2002 A1
20020035486 Huyn et al. Mar 2002 A1
20020038230 Chen Mar 2002 A1
20020045154 Wood Apr 2002 A1
20020046086 Pletz Apr 2002 A1
20020046096 Srinivasan Apr 2002 A1
20020047859 Szlam et al. Apr 2002 A1
20020055878 Burton et al. May 2002 A1
20020059095 Cook May 2002 A1
20020067500 Yokomizo et al. Jun 2002 A1
20020073162 McElfresh et al. Jun 2002 A1
20020082923 Merriman et al. Jun 2002 A1
20020083095 Wu et al. Jun 2002 A1
20020083167 Costigan et al. Jun 2002 A1
20020091832 Low et al. Jul 2002 A1
20020107728 Bailey et al. Aug 2002 A1
20020111850 Smrcka et al. Aug 2002 A1
20020123926 Bushold Sep 2002 A1
20020161620 Hatanaka Oct 2002 A1
20020161664 Shaya et al. Oct 2002 A1
20020167539 Brown et al. Nov 2002 A1
20030014304 Calvert et al. Jan 2003 A1
20030023754 Eichstadt et al. Jan 2003 A1
20030028415 Herschap et al. Feb 2003 A1
20030036949 Kaddeche et al. Feb 2003 A1
20030041056 Bossemeyer et al. Feb 2003 A1
20030055778 Erlanger Mar 2003 A1
20030105826 Mayraz Jun 2003 A1
20030110130 Pelletier Jun 2003 A1
20030140037 Deh-Lee Jul 2003 A1
20030149581 Chaudhri et al. Aug 2003 A1
20030149937 McElfresh et al. Aug 2003 A1
20030154196 Goodwin et al. Aug 2003 A1
20030167195 Fernandes et al. Sep 2003 A1
20030177096 Trent et al. Sep 2003 A1
20030195848 Felger Oct 2003 A1
20030217332 Smith et al. Nov 2003 A1
20030221163 Glover et al. Nov 2003 A1
20040034567 Gravett Feb 2004 A1
20040064412 Phillips et al. Apr 2004 A1
20040088323 Elder et al. May 2004 A1
20040128390 Blakley et al. Jul 2004 A1
20040153368 Freishtat et al. Aug 2004 A1
20040163101 Swix et al. Aug 2004 A1
20040167928 Anderson et al. Aug 2004 A1
20040193377 Brown Sep 2004 A1
20040210820 Tarr et al. Oct 2004 A1
20040243539 Skurtovich et al. Dec 2004 A1
20040260574 Gross Dec 2004 A1
20050004864 Lent et al. Jan 2005 A1
20050014117 Stillman Jan 2005 A1
20050033641 Jha et al. Feb 2005 A1
20050033728 James Feb 2005 A1
20050096997 Jain et al. May 2005 A1
20050114195 Bernasconi May 2005 A1
20050132205 Palliyil et al. Jun 2005 A1
20050138115 Llamas et al. Jun 2005 A1
20050171861 Bezos et al. Aug 2005 A1
20050183003 Peri Aug 2005 A1
20050198120 Reshef et al. Sep 2005 A1
20050198212 Zilberfayn et al. Sep 2005 A1
20050216342 Ashbaugh Sep 2005 A1
20050256955 Bodwell et al. Nov 2005 A1
20050262065 Barth et al. Nov 2005 A1
20050288943 Wei et al. Dec 2005 A1
20060015390 Rijsinghani et al. Jan 2006 A1
20060021009 Lunt Jan 2006 A1
20060026237 Wang et al. Feb 2006 A1
20060041476 Zheng Feb 2006 A1
20060047615 Ravin et al. Mar 2006 A1
20060059124 Krishna Mar 2006 A1
20060106788 Forrest May 2006 A1
20060122850 Ward et al. Jun 2006 A1
20060168509 Boss et al. Jul 2006 A1
20060253319 Chayes et al. Nov 2006 A1
20060265495 Butler et al. Nov 2006 A1
20060271545 Youn et al. Nov 2006 A1
20060282327 Neal et al. Dec 2006 A1
20060282328 Gerace et al. Dec 2006 A1
20060284378 Snow et al. Dec 2006 A1
20060288087 Sun Dec 2006 A1
20060293950 Meek et al. Dec 2006 A1
20070027771 Collins et al. Feb 2007 A1
20070027785 Lent et al. Feb 2007 A1
20070053513 Hoffberg Mar 2007 A1
20070061412 Karidi et al. Mar 2007 A1
20070061421 Karidi Mar 2007 A1
20070073585 Apple et al. Mar 2007 A1
20070094228 Nevin et al. Apr 2007 A1
20070100653 Ramer et al. May 2007 A1
20070100688 Book May 2007 A1
20070116238 Jacobi May 2007 A1
20070116239 Jacobi May 2007 A1
20070162501 Agassi et al. Jul 2007 A1
20070239527 Nazer et al. Oct 2007 A1
20070250585 Ly et al. Oct 2007 A1
20070260596 Koran et al. Nov 2007 A1
20070265873 Sheth et al. Nov 2007 A1
20080021816 Lent et al. Jan 2008 A1
20080033794 Ou et al. Feb 2008 A1
20080033941 Parrish Feb 2008 A1
20080040225 Roker Feb 2008 A1
20080072170 Simons Mar 2008 A1
20080147480 Sarma et al. Jun 2008 A1
20080147741 Gonen et al. Jun 2008 A1
20080201436 Gartner Aug 2008 A1
20080215541 Li et al. Sep 2008 A1
20080222656 Lyman Sep 2008 A1
20080244024 Aaltonen et al. Oct 2008 A1
20080262897 Howarter et al. Oct 2008 A1
20080270294 Lent et al. Oct 2008 A1
20080270295 Lent et al. Oct 2008 A1
20080319778 Abhyanker Dec 2008 A1
20090006174 Lauffer Jan 2009 A1
20090006179 Billingsley et al. Jan 2009 A1
20090006622 Doerr Jan 2009 A1
20090030859 Buchs et al. Jan 2009 A1
20090055267 Roker Feb 2009 A1
20090076887 Spivack et al. Mar 2009 A1
20090099904 Affeld et al. Apr 2009 A1
20090119173 Parsons et al. May 2009 A1
20090138606 Moran et al. May 2009 A1
20090164171 Wold et al. Jun 2009 A1
20090177771 Britton et al. Jul 2009 A1
20090210405 Ortega et al. Aug 2009 A1
20090222572 Fujihara Sep 2009 A1
20090287534 Guo et al. Nov 2009 A1
20090287633 Nevin et al. Nov 2009 A1
20090293001 Lu et al. Nov 2009 A1
20090307003 Benyamin et al. Dec 2009 A1
20090319296 Schoenberg Dec 2009 A1
20100023475 Lahav Jan 2010 A1
20100023581 Lahav Jan 2010 A1
20100049602 Softky Feb 2010 A1
20100106552 Barillaud Apr 2010 A1
20100110933 Wilcock May 2010 A1
20100205024 Shachar et al. Aug 2010 A1
20100255812 Nanjundaiah et al. Oct 2010 A1
20100281008 Braunwarth Nov 2010 A1
20110041168 Murray et al. Feb 2011 A1
20110055207 Schorzman et al. Mar 2011 A1
20110055331 Adelman et al. Mar 2011 A1
20110055338 Loeb et al. Mar 2011 A1
20110112893 Karlsson et al. May 2011 A1
20110113101 Ye et al. May 2011 A1
20110119264 Hu et al. May 2011 A1
20110138298 Alfred et al. Jun 2011 A1
20110161792 Florence et al. Jun 2011 A1
20110208822 Rathod Aug 2011 A1
20110246406 Lahav et al. Oct 2011 A1
20110270926 Boyd Nov 2011 A1
20110271175 Lavi et al. Nov 2011 A1
20110307331 Richard et al. Dec 2011 A1
20110320715 Ickman et al. Dec 2011 A1
20120042389 Bradley et al. Feb 2012 A1
20120059722 Rao Mar 2012 A1
20120136939 Stern et al. May 2012 A1
20120150973 Barak Jun 2012 A1
20120323346 Ashby et al. Dec 2012 A1
20130013362 Walker et al. Jan 2013 A1
20130036202 Lahav Feb 2013 A1
20130132194 Rajaram May 2013 A1
20130182834 Lauffer Jul 2013 A1
20130238714 Barak et al. Sep 2013 A1
20130268468 Vijayaraghavan et al. Oct 2013 A1
20130275862 Adra Oct 2013 A1
20130290533 Barak Oct 2013 A1
20130311874 Schachar et al. Nov 2013 A1
20130326375 Barak et al. Dec 2013 A1
20130336471 Agarwal et al. Dec 2013 A1
Foreign Referenced Citations (37)
Number Date Country
840244 May 1998 EP
1233361 Aug 2002 EP
1276 064 Jan 2003 EP
1549025 Jun 2005 EP
1 840 803 Oct 2007 EP
1845436 Oct 2007 EP
1850284 Oct 2007 EP
2 950 214 Mar 2011 FR
9288453 Nov 1997 JP
2004-054533 Feb 2004 JP
20040110399 Dec 2004 KR
20050010487 Jan 2005 KR
20080046310 May 2008 KR
20080097751 Nov 2008 KR
0127825 Apr 2001 WF
9722073 Jun 1997 WO
9845797 Oct 1998 WO
9909470 Feb 1999 WO
9922328 May 1999 WO
9944152 Sep 1999 WO
0057294 Sep 2000 WO
0135272 May 2001 WO
02065367 Aug 2002 WO
03032146 Apr 2003 WO
2004057473 Jul 2004 WO
2005059777 Jun 2005 WO
2007044757 Apr 2007 WO
2007129625 Nov 2007 WO
2008057181 May 2008 WO
2008143382 Nov 2008 WO
2009029940 Mar 2009 WO
2010099632 Sep 2010 WO
2010119379 Oct 2010 WO
2010144207 Dec 2010 WO
2011127049 Oct 2011 WO
2013158830 Oct 2013 WO
2013163426 Oct 2013 WO
Non-Patent Literature Citations (180)
Entry
Chartrand Sabra, “A new system seeks to ease the bottleneck in the customer-service information highway,” The New York Times (Apr. 30, 2001), 2 pages.
Just Answer (2004 Faq) Archive.org cache of www.justanswer.com circa (Dec. 2004), 8 pages.
Pack Thomas, “Human Search Engines the next Killer app,” (Dec. 1, 2000) Econtent DBS vol. 23; Issue 6, 7 pages.
Match.Com “Match.com Launches Match.com Advisors,” PR Newswire (Oct. 14, 2003), 2 pages.
Sitel, “Sitel to Provide Live Agent Support Online for Expertcity.com,” PR Newswire (Feb. 28, 2000), 2 pages.
Webmaster World, “Link to my website is in a frame with banner ad at the top,” www.webmasterworld.com (Nov. 11, 2003), 2 pages.
Bry et al., “Realilzing Business Processes with ECA Rules: Benefits, Challenges, Limits,” Principles and Practice of Sematic Web Reasoning Lecture Notes in Computer Science, pp. 48-62, LNCS, Springer, Berlin, DE (Jan. 2006).
Fairisaac, “How SmartForms for Blaze Advisor Works,” www.fairisaac.com 12 pages (Jan. 2005).
Mesbah A et al., “A Component-and Push-Based Architectural Style for Ajax Applications,” The Journal of Systems & Software, 81 (12): pp. 2194-2209, Elsevier North Holland, New York, NY US (Dec. 2008).
Oracle Fusion Middleware Administrator's Guide for Oracle SOA (Oracle Guide) Suite 11g Release 1 (11.1.1) Part No. E10226-02 www.docs.oracle.com (Oct. 2009), 548 pages.
“OAuth core 1.0 Revision A [XP002570263],” OAuth Core Workgroups, pp. 1-27 www.ouath.net/core/1.0a/ (retrieved Jan. 31, 2013), 24 pages.
Anon., “AnswerSoft Announces Concerto; First to Combine Call Center Automation with Power of Web,” Business Wire, (Feb. 3, 1997) 3 pages.
Emigh, J., “AnswerSoft Unveils Concerto for Web-Based Call Centers Feb. 5, 1996,” Newsbytes, (Feb. 5, 1997) 2 pages.
Grigonis, R., “Webphony—It's not Just Callback Buttons Anymore,” Computer Telephony, (Dec. 1997) 4 pages.
Wagner, M., “Caring for Customers,” Internet World, (Sep. 1, 1999) 3 pages.
Sweat, J., “Human Touch—A New Wave of E-Service Offerings Blends the Web, E-Mail, and Voice Bringing People back into the Picture,” Information week, (Oct. 4, 1999) 2 pages.
Kirkpatrick, K., “Electronic Exchange 2000, the,” Computer Shopper, (Nov. 1999) 5 pages.
Anon., “InstantService.com Teams with Island Data to provide Integrated Solution for Online Customer Response,” Business Wire, (May 22, 2000) 3 pages.
Kersnar, S., “Countrywide Offers Proprietary Technology for Online Wholesale Lending,” National Mortgage News, vol. 24, No. 38, (Jun. 5, 2000) 2 pages.
Douglas Armstrong, Firstar Web site helps add up future, Milwaukee Journal Sentinel, (Mar. 28, 1996) 3 pages.
redhat—.com downloaded on Jul. 23, 2006.
apache.org downloaded on Jul. 23, 2006.
mysql.com downloaded on Jul. 23, 2006.
developer.com downloaded on Jul. 23, 2006.
Canter, Ronald S., “Lender Beware-Federal Regulation of Consumer Credit”, Credit World, vol. 81, No. 5, pp. 16-20, (May 1993).
Staff, “On-Line System Approves Loans While Customer Waits,” Communication News, vol. 31, Issue 9, (Sep. 1994) 3 pages.
“Low-Rent Loan Officer in a Kiosk”, Bank Technology News vol. 8 No. 2, p (Feb. 1995) 2 pages.
Duclaux, Denise, “A Check for $5,000 in Ten Minutes”, ABA Banking Journal, vol. 87, No. 8, p. 45, AUQ. (1995) 2 pages.
“World Wide Web Enhances Customer's Choice”, Cards International, No. 143, p. 9, (Nov. 1995) 2 pages.
Wells Fargo Launches First Real-Time, Online Home Equity Credit Decision-Making Service, Business Wire, (Jun. 3, 1998), Dialog— File 621: New Product Announcement, 3 pages.
Handley, John, “Credit Review Lets the Numbers Do the Talking in Home Mortgage Game”, Chicago Tribune (Jul. 1998) 3 pages.
Sherman, Lee, “Wells Fargo Writes a New Online Script”, Interactive Week, vol. 5, No. 31, p. 29, (Aug. 1998) 2 pages.
Calvey, Mark, “Internet Gives Bankers a Snappy Comeback”, San Francisco Business Times, vol. 13, No. 5, p. 3 (Sep. 1998) 2 pages.
McCormick, Linda, “Users of Credit Scoring Face Tough Rules on Notification”, American Banker, Dialog File 625: American Banker Publications, (Mar. 21, 1982) 2 pages.
What the Credit Bureau is Saying About You: If a Mistake Sneaks Into Your Record, You May Not Know About it Until You Get Turned Down for Credit, Changing Times, vol. 37, p. 56, (Jul. 1983) 2 pages.
McShane. Peter K., “Got Financing?”, Business Journal Serving Southern Tier, CNY, Mohawk Valley, Finger Lakes. North, vol. 11, Issue 19, p. 9, (Sep. 15, 1997) 3 pages.
Borowsky, Mark, “The Neural Net: Predictor of Fraud or Victim of Hype?”, Bank Technology News DialoQ File 16:PROMT, p. 7 (Sep. 1993) 2 pages.
FICO http://houseloans.idis.com/fico (2009) 1 page.
Altavista: search, FICO http://www.altavista.com (2001) 3 pages.
What Do FICO Scores Mean to Me?, http://www.sancap.com. (1999) 3 pages.
What is a FICO Score?, http://www.aspeenloan.com (2009) 1 page.
“Credit”, The New Encyclopedia Britannica vol. 3 p. 722. (1994) 3 pages.
“Creditnet.com—An Online Guide to Credit Cards”, http://www.creditnet/com. (1999) 1 page.
“Phillips 66 Introduces Mastercard with Rebate Feature”, PR Newswire, p914NY067, (Sep. 14, 1995) 1 page.
Anon, “VAR Agreement Expands Credit Bureau Access.”, (CCS America, Magnum Communications Ltd expand CardPac access, Computers in Banking, v6, n10, (1) (Oct. 1989) 2 pages.
Wortmann, Harry S., “Reengineering Update—Outsourcing: An Option Full of Benefits and Responsibilities”, American Banker, (Oct. 24, 1994), p. 7A vol. 159, No. 205 3 pages.
Anon. “To Boost Balances, AT&T Renews No-Fee Universal Credit Card Offer”, Gale Group Newsletter, V 10, N. 13, (Mar. 30, 1992) 2 pages.
Anon. “Citgo Puts a New Spin on the Cobranded Oil Card”, Credit Card News, p. 4, (Nov. 1, 1995) 2 pages.
Anon. “Microsoft Targets More than PIM Market with Outlook 2000,” Computer Reseller News, N. 805 pp. 99, (Aug. 31, 1998) 2 pages.
Chesanow, Neil, “Pick the Right Credit Cards-and use them wisely”, Medical Economics, v. 75, n. 16, p. 94, (Aug. 24, 1998) 4 pages.
Friedland, Marc, “Credit Scoring Digs Deeper into Data”, Credit World, v. 84, n. 5 p. 19-23, (May 1996) 5 pages.
Hollander, Geoffrey, “Sibling Tool Personator 3 untangles File Formats”, InfoWorld, v20, n5, pp. 102 (Feb. 2, 1998) 2 pages.
Kantrow, Yvette D., “Banks Press Cardholders to Take Cash Advances”, American Banker, v. 157, n. 18 pp. 1-2. (Jan. 28, 1992) 2 pages.
Lotus News Release: “Lotus Delivers Pre-Release of Lotus Notes 4.6 Client Provides Compelling New Integration with Internet Explorer”, (May 20, 1997) 2 pages.
Stetenfeld, Beth, “Credit Scoring: Finding the Right Recipe”, Credit Union Management, v. 17, n. 11, pp. 24-26 (Nov. 1994).
Block, Valerie, “Network Assembles Card Issuers at an Internet Site”, Am. Banker, V160, (1998) 1 page.
CreditNet Financial Network http://consumers.creditnet.com (1999) 1 page.
Anon., “Lending Tree: Lending Tree Provides Borrowers Fast and Easy Online Access to Multiple Loan Offers,” Business Wire, Jun. 23, 1998, 2 pages.
Anon, Regulation Z Commentary Amendments, Retail Banking Digest, vol. 15, No. 2, p. 17-18, (Mar.-Apr. 1995).
Anon, San Diego Savings Association Offers Customers No-Fee Visa Product, Card News, (Feb. 29, 1988) 1 page.
Bloom, J.K., “For This New Visa, Only Web Surfers Need Apply,” American Banker, vol. 1163, No. 34 12 (Feb. 20, 1998) 2 pages.
Harney, K.R., “Realty Brokers, Lenders Face Restrictions,” Arizona Republic, Final Chaser edition, Sun Living section, (Feb. 10, 1991) 2 pages.
Higgins, K.T., “Mr. Plastic Joins the Marketing Team,” Credit Card Management, vol. 6, No. 3, pp. 26-30, Jun. 1993.
Microsoft Press Computer Dictionary, Third Edition, Microsoft Press, Redmond, 1997, 4 pages.
Whiteside, D.E., “One Million and Counting,” Collections and Credit Risk, vol. 1, No. 11 (Nov. 1996) 5 pages.
Fickenscher, L., “Providian Undercuts rivals with 7.9% Rate Offer,” American banker, vol. 163, Oct. 8, 1998, 2 pages.
Fargo, J., “The Internet Specialists,” Credit Card Management, vol. 11, No. 10, pp. 38-45, Jan. 1999.
Lemay, T., “Browsing for a Mortgage a Click away,” Financial Post, (Jan. 15, 2000) 1 page.
Wijnen, R., “Banks Fortify Online Services,” Bank Technology News, vol. 13, No. 3, Mar. 2000, 3 pages.
Anon. “IAFC Launches NextCard, the First True Internet VISA,” Business Wire, New York: (Feb. 6, 1998), 3 pages.
Lazarony, Lucy, “Only Online Applicants Need Apply,” Bank Advertising News, North Palm Beach, Mar. 23, 1998, vol. 21, Issue 15, 3 pages.
FIData, Inc., News & Press Releases, “Instant Credit Union Loans via the Internet,” http://web.archive.org/web/19990221115203/www.fidata-inc.com/news-pr01.htm (1999) 2 pages.
FIData, Inc., Press Releases, “Instant Loan Approvals via the Internet,” http://www.fidata-—inc.com/news/pr—040198.htm, (Apr. 1, 1998) 2 pages.
Staff, “On-Line System Approves Loans While Customer Waits”—Abstract, Communication News, vol. 31, Issue 9, (Sep. 1994) 3 pages.
Anon. “Affordable Lending Systems Now Available for Smaller Financial Institutions,” Business Wire, (May 18, 1998), 2 pages.
Nexis—All News Sources—Examiner's NPL Search Results in U.S. Appl. No. 11/932,498, included with Office Action issued Oct. 8, 2008, 14 pages.
“Sample Experian Credit Report” by Consumer Information consumerinfo.com (Jul. 9, 1998) 4 pages.
Plaintiffs Original Complaint, Nextcard, LLC v. Liveperson, Inc.; Civil Action No. 2:08-cv-00184-TJW, in the U.S. District Court for the Eastern District of Texas, Marshall Division, filed Apr. 30, 2008 (7 pages).
Amended Complaint and Jury Demand; Liveperson, Inc. v. Nextcard, LLC, et al.; Civil Action No. 08-062 (GMS), in the U.S. District Court for the District of Delaware, filed Mar. 18, 2008 (5 pages).
Plaintiffs Second Amended Complaint; Nextcard, LLC v. American Express Company, et al; Civil Action No. 2:07-cv-354 (TJW); in the U.S. District Court for the Eastern District of Texas, Marshall Division, filed Apr. 9, 2008 (12 pages).
Defendants HSBC North America Holdings Inc.'s and HSBC USA Inc's Answer, Affirmative Defenses and Counterclaims to Plaintiffs Second Amended Complaint; Nextcard, LLC v. American Express Company, et al; Civil Action No. 2:07-cv-354 (TJW); in the U.S. District Court for the Eastern District of Texas, Marshall Division filed (Apr. 28, 2008), 13 pages.
Answer and Counterclaims of Defendant DFS Services LLC; Nextcard, LLC v. American Express Company, et al; Civil Action No. 2:07-cv-354 (TJW); in the U.S. District Court for the Eastern District of Texas, Marshall Division, filed Apr. 28, 2008 (13 pages).
Defendant The PNC Financial Services Group, Inc.'s Answer and Affirmative Defenses to Second Amended Complaint; Nextcard, LLC v. American Express Company, et al; Civil Action No. 2:07-cv-354 (TJW); in the U.S. District Court for the Eastern District of Texas, Marshall Division, filed Apr. 28 2008, 10 pages.
Plaintiffs Second Amended Reply to Counterclaims of Defendants HSBC North America Holdings Inc. and HSBC USA Inc.; Nextcard, LLC v. American Express Company, et al; Civil Action No. 2:07-cv-354 (TJW); in the U.S. District Court for the Eastern District of Texas, Marshall Division, filed May 14, 2008, 5 pages.
Plaintiffs Second Amended Reply to Counterclaims of Defendant DFS Services LLC; Nextcard, LLC v. American Express Company, et al; Civil Action No. 2:07-cv-354 (TJW); in the U.S. District Court for the Eastern District of Texas, Marshall Division, filed May 14, 2008 (71 pages).
Plaintiffs Second Amended Reply to Counterclaims of Defendant American Express Company; Nextcard, LLC v. American Express Company, et al; Civil Action No. 2:07-cv-354 (TJW); in the U.S. District Court for the Eastern District of Texas, Marshall Division, filed (May 8, 2008), 8 pages.
Justin Hibbard, Gregory Dalton, Mary E Thyfault. (Jun. 1998). “Web-based customer care.” Information Week, (684) 18-20, 3 pages.
Kim S. Nash “Call all Customers.” Computerworld, 32 (1), 25-28 (Dec. 1997), 2 pages.
PRN: “First American Financial Acquires Tele-Track Inc.,” PR Newswire, (May 11, 1999), Proquest #41275773, 2 pages.
Young, Deborah, “The Information Store,” (Sep. 15, 2000), Wireless Review, pp. 42, 44, 46, 48, 50.
Whiting et al., “Profitable Customers,” (Mar. 29, 1999), Information Week, Issue 727, pp. 44, 45, 48, 52, 56.
Bayer, Judy, “A Framework for Developing and Using Retail Promotion Response Models,” Cares Integrated Solutions, retrieved from www.ceresion.com (2007) 5 pages.
Bayer, Judy, “Automated Response Modeling System for Targeted Marketing,” (Mar. 1998), Ceres Integrated Solutions, 5 pages.
Sweet et al., “Instant Marketing,” (Aug. 12, 1999), Information Week, pp. 18-20.
SmartKids.com “Chooses Quadstone—The Smartest Customer Data Mining Solution,” (Jul. 31, 2000), Business Wire, 2 pages.
“NCR's Next Generation Software Makes True Customer Relationship Management a Reality,” (Jul. 26, 1999) PR Newswire, 3 pages.
“Quadstone System 3.0 Meets New Market Demand for Fast, Easy-to-Use Predictive Analysis for CRM,” (May 22, 2000) Business Wire, 3 pages.
“Net Perceptions Alters Dynamics of Marketing Industry with Introduction of Net Perceptions for Call Centers,” (Oct. 12, 1998) PR Newswire, 3 pages.
“Ceres Targeted Marketing Application,” Ceres Integrated Solutions: retrieved from www.ceresios.com/Product/index.htm (2007) 3 pages.
Prince, C. J., E:business: A Look at the Future, Chief Executive, vol. 154, (Apr. 2000), pp. 10-11.
Oikarinen et al. “Internet Relay Chat Protocol” RFC-1459, pp. 1-65, (May 1993).
eDiet.com: Personalized Diets, Fitness, and Counseling, (May 3, 1998), pp. 1-15.
Fiszer, Max; “Customizing an inbound call-center with skills-based routing,” Telemarketing & Call Center Solutions, (Jan. 1997), v15i7 p. 24; Proquest #11267840, 5 pages.
“ESL Federal Credit Union Inaugurates Internet Target Marketing.” PR Newswire p. 4210 (Oct. 6, 1998), 3 pages.
“Welcome to eStara—The Industry Leader in Click to Call and Call Tracking Solutions,” e-Stara, Inc., retrieved from www.estara.com on Mar. 21, 2013, 1 page.
“Push to Talk Live Now! From your website” iTalkSystem, Inc., retrieved from www.italksystems.com on Mar. 21, 2013, 1 page.
Richardson et al., “Predicting Clicks: Estimating the Click-Through Rate for New Ads,” (May 2007) 9 pages.
“Welcome to Keen” retrieved from www.archive.org/web/20010302014355/http://www.keen.com/ on Jan. 25, 2013, 1 page.
Christophe Destruel, Herve Luga, Yves Duthen, Rene Caubet. “Classifiers based system for interface evolution.” Expersys Conference, 265-270 (1997), 6 pages.
Ulla de Stricker, Annie Joan Olesen. “Is Management Consulting for You?” SEARCHER, 48-53 (Mar. 2005), 6 pages.
Humberto T. Marques Neto, Leonardo C.D. Rocha, Pedro H.C. Guerra, Jussara M. Almeida, Wagner Meira Jr., Virgilio A. F. Almeida. “A Characterization of Broadband User Behavior and Their E-Business Activities.” ACM SIGMETRICS Performance Evaluation Review, 3-13 (2004), 11 pages.
Greg Bowman, Michael M. Danchak, Mary LaCombe, Don Porter. “Implementing the Rensselaer 80/20 Model in Professional Education.” 30th ASEE/IEEE Frontiers in Education Conference, Session T3G (Oct. 18-21, 2000), 1 page.
Elizabeth Sklar Rozier, Richard Alterman. “Participatory Adaptation.” CHI, 97, 261-262 (Mar. 22-27, 1997), 2 pages.
Frank White. “The User Interface of Expert Systems: What Recent Research Tells Us.” Library Software Review, vol. 13, No. 2, p. 91-98 (Summer 1994) 8 pages.
Frederick W. Rook, Michael L. Donnell. “Human Cognition and the Expert System Interface: Mental Models and Inference Explanations.” IEEE Transactions on Systems, Man, and Cybernetics, vol. 23, No. 6, p. 1649-1661 (Nov./Dec. 1993), 13 pages.
International Search Report and Written Opinion for PCT Application No. PCT/US2013/041147, mailed Jul. 30, 2013, 9 pages.
International Search Report and Written Opinion for PCT Application No. PCT/US2013/037086, mailed Jul. 12, 2013, 9 pages.
International Search Report and Written Opinion for PCT Application No. PCT/US2013/29389, mailed Jul. 24, 2013, 8 pages.
International Search Report and Written Opinion for PCT Application No. PCT/US2013/038212, mailed Jul. 17, 2013, 11 pages.
International Search Report for PCT Application No. PCT/US03/41090, mailed on Sep. 1, 2004, 3 pages.
International Search Report for PCT Application No. PCT/US05/40012, mailed on Oct. 5, 2007, 2 pages.
International Preliminary Report on Patentability for PCT Application No. PCT/US2006/039630, dated Apr. 16, 2008, 4 pages.
International Search Report for PCT Application No. PCT/US2011/031239, mailed on Jul. 7, 2011, 3 pages.
International Search Report for PCT Application No. PCT/US2011/064946, mailed on Jun. 22, 2012, 3 pages.
International Preliminary Report on Patentability for PCT Application No. PCT/US2011/031239, dated Oct. 9, 2012, 8 pages.
Non-Final Office Action of Dec. 11, 2008 for U.S. Appl. No. 11/394,078, 15 pages.
Final Office Action of Jul. 9, 2009 for U.S. Appl. No. 11/394,078, 15 pages.
Non-Final Office Action of Jan. 28, 2010 for U.S. Appl. No. 11/394,078, 14 pages.
Final Office Action of Jul. 9, 2010 for U.S. Appl. No. 11/394,078, 16 pages.
Non-Final Office Action of Feb. 1, 2011 for U.S. Appl. No. 11/394,078, 20 pages.
Final Office Action of Aug. 2, 2011 for U.S. Appl. No. 11/394,078, 23 pages.
Non-Final Office Action of May 16, 2012 for U.S. Appl. No. 11/394,078, 23 pages.
Final Office Action of Jan. 25, 2013 for U.S. Appl. No. 11/394,078, 22 pages.
Non-Final Office Action of Jun. 22, 2012 for U.S. Appl. No. 13/080,324, 9 pages.
Non-Final Office Action of Aug. 15, 2012 for U.S. Appl. No. 12/967,782, 31 pages.
Non-Final Office Action of Jul. 29, 2011 for U.S. Appl. No. 12/608,117, 20 pages.
Final Office Action of Apr. 4, 2012 for U.S. Appl. No. 12/608,117, 25 pages.
Non-Final Office Action of Apr. 24, 2004 for U.S. Appl. No. 09/922,753, 16 pages.
Final Office Action of Oct. 14, 2004 for U.S. Appl. No. 09/922,753, 13 pages.
Non-Final Office Action of May 17, 2005 for U.S. Appl. No. 09/922,753, 13 pages.
Non-Final Office Action of Mar. 14, 2006 for U.S. Appl. No. 09/922,753, 13 pages.
Final Office Action of Jul. 26, 2006 for U.S. Appl. No. 09/922,753, 13 pages.
Non-Final Office Action of Aug. 13, 2008 for U.S. Appl. No. 09/922,753, 10 pages.
Final Office Action of Apr. 23, 2009 for U.S. Appl. No. 09/922,753, 11 pages.
Non-Final Office Action of Jul. 21, 2009 for U.S. Appl. No. 09/922,753, 10 pages.
Final Office Action of Feb. 18, 2010 for U.S. Appl. No. 09/922,753, 9 pages.
Non-Final Office Action of Apr. 25, 2011 for U.S. Appl. No. 09/922,753, 9 pages.
Final Office Action of Nov. 25, 2011 for U.S. Appl. No. 09/922,753, 10 pages.
Non-Final Office Action of Aug. 7, 2007 for U.S. Appl. No. 10/980,613, 16 pages.
Non-Final Office Action of May 15, 2008 for U.S. Appl. No. 10/980,613, 23 pages.
Non-Final Office Action of Apr. 30, 2012 for U.S. Appl. No. 12/504,265, 16 pages.
Final Office Action of Aug. 28, 2012 for U.S. Appl. No. 12/504,265, 28 pages.
Final Office Action of Feb. 14, 2013 for U.S. Appl. No. 13/080,324, 11 pages.
Non-Final Office Action of Mar. 30, 2013 for U.S. Appl. No. 11/360,530, 23 pages.
Final Office Action of Apr. 11, 2013 for U.S. Appl. No. 12/967,782, 18 pages.
Non-Final Office Action of May 10, 2013 for U.S. Appl. No. 13/563,708, 20 pages.
Non-Final Office Action of Jun. 12, 2013 for U.S. Appl. No. 12/608,117, 56 pages.
Non-Final Office Action of Jun. 20, 2013 for U.S. Appl. No. 13/157,936, 19 pages.
Non-Final Office Action of Jun. 27, 2013 for U.S. Appl. No. 12/504,265, 11 pages.
Non-Final Office Action of Jul. 8, 2013 for U.S. Appl. No. 13/413,197, 10 pages.
Final Office Action of Oct. 21, 2013 for U.S. Appl. No. 12/504,265 14 pages.
Non-Final Office Action of Oct. 30, 2013 for U.S. Appl. No. 13/961,072, 10 pages.
Non-Final Office Action of Dec. 5, 2013 for U.S. Appl. No. 12/967,782, 14 pages.
Notice of Allowance of Jan. 3, 2014 for U.S. Appl. No. 11/360,530, 29 pages.
Final Office Action of Jan. 22, 2014 for U.S. Appl. No. 12/608,117, 45 pages.
Final Office Action of Jan. 27, 2014 for U.S. Appl. No. 13/563,708, 35 pages.
Notice of Allowance of Feb. 12, 2014 for U.S. Appl. No. 13/157,936, 33 pages.
Final Office Action of Feb. 19, 2014 for U.S. Appl. No. 13/961,072, 35 pages.
Non-Final Office Action of Feb. 20, 2014 for U.S. Appl. No. 10/980,613, 43 pages.
Notice of Allowance of Feb. 28, 2014 for U.S. Appl. No. 09/922,753, 13 pages.
Notice of Allowance of Mar. 25, 2014 for U.S. Appl. No. 12/504,265, 31 pages.
Notice of Allowance of Mar. 31, 2014 for U.S. Appl. No. 12/725,999, 41 pages.
Notice of Allowance of Apr. 1, 2014 for U.S. Appl. No. 13/413,197, 32 pages.
International Preliminary Report on Patentability for PCT Application No. PCT/US2013/29389, mailed Sep. 18, 2014, 6 pages.
International Preliminary Report on Patentability for PCT Application No. PCT/US2013/025142, mailed Aug. 21, 2014, 5 pages.
Non-Final Office Action of Jul. 17, 2014 for U.S. Appl. No. 11/394,078, 16 pages.
Non-Final Office Action of Jul. 31, 2014 for U.S. Appl. No. 13/080,324, 17 pages.
Notice of Allowance of Aug. 18, 2014 for U.S. Appl. No. 12/967,782, 17 pages.
Non-Final Office Action of Aug. 21, 2014 for U.S. Appl. No. 10/980,613, 17 pages.
Notice of Allowance of Sep. 26, 2014 for U.S. Appl. No. 13/563,708, 8 pages.
Related Publications (1)
Number Date Country
20130212497 A1 Aug 2013 US
Provisional Applications (1)
Number Date Country
61632815 Feb 2012 US