# US 2023/0274292 A1 · Churn prevention using graphs

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2023/0274292 A1
- Document ID: US20230274292A1
- Status: Published application
- Kind: A1
- Application number: 17/683,112
- Filed: 2022-02-28
- Published: 2023-08-31
- Earliest claimed: 2022-02-28
- Assignees: Intuit Inc.
- Applicants: Intuit Inc.
- Inventors: Rohith Ramakrishnan; Rohit Jain
- Web page: https://patentgrep.com/patent/US20230274292A1

## CPC

- G06F 16/9024: {Graphs; Linked lists (G06F16/9027 takes precedence)}
- G06Q 30/0201: Market modelling; Market analysis; Collecting market data
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

A method implements churn prevention using graphs. The method includes receiving clickstream data, which includes an event, of a user session with an application. The method further includes identifying the event as corresponding to a churn user account and mapping the event to a pair of nodes of a graph. The method further includes updating a churn user count of the pair of nodes in response to identifying the event as corresponding to the churn user account. The method further includes identifying an edge of the graph, corresponding to the pair of nodes. The method further includes updating a value of the edge using an active user count and the churn user count presenting an update responsive to the value.

## Claims

### Claim 1

A method comprising:
receiving clickstream data, comprising an event of a plurality of events, of a user session with an application;
identifying the event as corresponding to a churn user account;
mapping the event to a pair of nodes of a graph;
updating a churn user count of the pair of nodes in response to identifying the event as corresponding to the churn user account;
identifying an edge, of a plurality of edges of the graph, corresponding to the pair of nodes;
updating a value of the edge using an active user count and the churn user count; and
presenting an update responsive to the value.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
calculating the value by:
dividing the active user count of a destination node, of the pair of nodes, by an active user count of a source node, of the pair of nodes, to generate an active percentage;
dividing the churn user count of the destination node, of the pair of nodes, by a churn user count of the source node, of the pair of nodes, to generate a churn percentage; and
calculating a difference between the churn percentage and the active percentage to form the value.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
updating the churn user count by incrementing the churn user count.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
receiving the event in response to interaction with a user device;
identifying a node, of the graph, corresponding to the event;
identifying the edge, corresponding to the node; and
determining the value, of the edge, satisfies a threshold in response to receiving the event.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
presenting the update by transmitting the update to a user device in response to determining the value satisfies a threshold.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
presenting the update by transmitting a table comprising the value to a user device.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
updating the graph periodically.

### Claim 8 (depends on 1)

The method of claim 1, wherein the churn user account has not been accessed for a threshold length of time.

### Claim 9 (depends on 1)

The method of claim 1, wherein the edge is an outgoing edge of a source node of the pair of nodes.

### Claim 10 (depends on 1)

The method of claim 1, wherein the edge is an incoming edge of a destination node of the pair of nodes.

### Claim 11

A system comprising:
a graph controller configured to receive clickstream data;
a node controller configured to map an event to a pair of nodes;
an edge controller configured to update a value of an edge;
a modeling application executing on one or more servers and configured for:
receiving, by the graph controller, the clickstream data, comprising the event of a plurality of events, of a user session with an application;
identifying the event as corresponding to a churn user account;
mapping, by the node controller, the event to the pair of nodes of a graph;
updating a churn user count of the pair of nodes in response to identifying the event as corresponding to the churn user account;
identifying the edge, of a plurality of edges of the graph, corresponding to the pair of nodes;
updating, by the edge controller, the value of the edge using an active user count and the churn user count; and
presenting an update responsive to the value.

### Claim 12 (depends on 11)

The system of claim 11, wherein the modeling application is further configured for:
calculating, by the edge controller, the value by:
dividing the active user count of a destination node, of the pair of nodes, by an active user count of a source node, of the pair of nodes, to generate an active percentage;
dividing the churn user count of the destination node, of the pair of nodes, by a churn user count of the source node, of the pair of nodes, to generate a churn percentage; and
calculating a difference between the churn percentage and the active percentage to form the value.

### Claim 13 (depends on 11)

The system of claim 11, wherein the modeling application is further configured for: updating the churn user count by incrementing the churn user count.

### Claim 14 (depends on 11)

The system of claim 11, further comprising:
a server application executing on the one or more servers and configured for:
receiving the event in response to interaction with a user device;
identifying a node, of the graph, corresponding to the event;
identifying the edge, corresponding to the node; and
determining the value, of the edge, satisfies a threshold in response to receiving the event.

### Claim 15 (depends on 11)

The system of claim 11, further comprising:
a server application executing on the one or more servers and configured for:
presenting the update by transmitting the update to a user device in response to determining the value satisfies a threshold.

### Claim 16 (depends on 11)

The system of claim 11, further comprising:
a server application executing on the one or more servers and configured for:
presenting the update by transmitting a table comprising the value to a user device.

### Claim 17 (depends on 11)

The system of claim 11, wherein the modeling application is further configured for: updating the graph periodically.

### Claim 18 (depends on 11)

The system of claim 11, wherein the churn user account has not been accessed for a threshold length of time.

### Claim 19 (depends on 11)

The system of claim 11, wherein the edge is an outgoing edge of a source node of the pair of nodes.

### Claim 20

A method comprising:
receiving an event in response to interaction with a user device;
identifying a node, of a graph, corresponding to the event;
identifying an edge, corresponding to the node; and
determining a value, of the edge, satisfies a threshold in response to receiving the event, wherein the value is calculated using an active user count and a churn user count.
presenting an update responsive to determining the value satisfies the threshold.
