# US 2019/0377758 A1 · Systems and Methods for Identifying Groups Relevant to Stored Objectives and Recommending Actions

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

- Number: US 2019/0377758 A1
- Document ID: US20190377758A1
- Status: Published application
- Kind: A1
- Application number: 16/448,812
- Filed: 2019-06-21
- Published: 2019-12-12
- Earliest claimed: 2010-12-03
- Assignees: Relationship Capital Technologies Inc.
- Applicants: Relationship Capital Technologies Inc.
- Inventors: Andrew R. Wilson; John Slade; Daniel Bouganim; Sean L. Cramer
- Web page: https://patentgrep.com/patent/US20190377758A1

## CPC

- G06Q 10/42: Determination of affinities or common interests between users
- G06F 16/23: Updating
- G06F 16/25: Integrating or interfacing systems involving database management systems
- G06F 16/284: {Relational databases}
- G06F 16/3322: {using system suggestions (G06F16/3325 takes precedence)}
- G06F 16/9024: {Graphs; Linked lists (G06F16/9027 takes precedence)}
- G06F 16/9535: Search customisation based on user profiles and personalisation
- G06Q 10/48: using social graphs
- 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
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Relationship management systems in accordance with embodiments of the invention are configured to provide systematic ways for a user to measure, and manage relationships in the user's social network. One embodiment of the invention includes a relationship management server system, and a database. In addition, the relationship management server system is configured to store a user account associated with a user in the database, store information concerning contacts associated with the user in the database, store event information associated with the user and at least one of the stored contacts in the database, store at least one objective in the database, score at least one relationship between the user and a contact based upon stored event information associated with the user and the contact to create a scored relationship graph, and generate a recommendation concerning an action based upon the stored objective and the scored relationship graph.

## Claims

### Claim 1

A relationship management system, comprising:
a relationship management server system; and
a database;
wherein the relationship management server system is configured to:
store a user account associated with a user in the database;
store information concerning contacts associated with the user in the database;
store event information associated with the user and at least one of the stored contacts in the database;
store at least one objective in the database;
score at least one relationship between the user and a contact based upon stored event information associated with the user and the contact to create a scored relationship graph; and
generate a recommendation concerning an action based upon at least one stored objective and the scored relationship graph.

### Claim 2 (depends on 1)

The relationship management system of claim 1, wherein the relationship management server system is configured to obtain contact information from at least one source of contact information.

### Claim 3 (depends on 2)

The relationship management system of claim 2, wherein at least one source of contact information is selected from the group consisting of a web mail service, an enterprise mail system, and an online social network.

### Claim 4 (depends on 1)

The relationship management system of claim 1, wherein the relationship management server system is configured to obtain event information from at least one source of event information.

### Claim 5 (depends on 4)

The relationship management system of claim 4, wherein at least one source of event information is selected from the group consisting of a web mail service, an enterprise mail system, a web calendaring service, an enterprise calendaring system, call data records, and an online social network.

### Claim 6 (depends on 1)

The relationship management system of claim 1, wherein the objective relates to a specific project.

### Claim 7 (depends on 1)

The relationship management system of claim 1, wherein the objective relates to an objective with respect to the user's relationship graph.

### Claim 8 (depends on 7)

The relationship management system of claim 7, wherein the objective relates to a specific relationship.

### Claim 9 (depends on 1)

The relationship management system of claim 1, wherein the relationship management server system is further configured to store information characterizing at least one relationship between the user and a contact.

### Claim 10 (depends on 9)

The relationship management system of claim 9, wherein the information characterizing a relationship between the user and a contact is expressed in terms of a first value indicative of the importance of the relationship to the user, and a second value indicative of the strength of the relationship.

### Claim 11 (depends on 10)

The relationship management system of claim 10, wherein the objective is expressed as a target value for the strength of a relationship.

### Claim 12 (depends on 9)

The relationship management system of claim 9, wherein:
the relationship management server system is further configured to prompt the user for information characterizing at least one relationship; and
the at least one relationship is selected based upon the importance of the relationship to the generation of a recommendation concerning an action based upon the stored objective and the scored relationship graph.

### Claim 13 (depends on 1)

The relationship management system of claim 1, wherein the relationship management server system is further configured to store information identifying a group of contacts associated with the objective.

### Claim 14 (depends on 13)

The relationship management system of claim 13, wherein the relationship management server system is further configured to recommend at least one contact for inclusion in the group of contacts associated with the objective.

### Claim 15 (depends on 1)

The relationship management system of claim 1, wherein the relationship management server system is further configured to decrease the score assigned to a relationship between a user and a contact due to the passage of time.

### Claim 16 (depends on 1)

The relationship management system of claim 1, wherein the relationship management server system is further configured to increase the score assigned to a relationship between a user and a contact in response to the occurrence of an event involving at least the user and the contact.

### Claim 17 (depends on 1)

The relationship management system of claim 1, wherein the relationship management server system is further configured to increase the score assigned to a relationship between a user and a contact in response to the occurrence of a telephone conversation between the user and the contact.

### Claim 18 (depends on 1)

The relationship management system of claim 1, wherein the relationship management server system is further configured to increase the score assigned to a relationship between a user and a contact in response to the occurrence of a meeting between the user and the contact.

### Claim 19 (depends on 1)

The relationship management system of claim 1, wherein the relationship management server system is further configured to modify the score assigned to a relationship between a user and a contact in response to the user requesting a predetermined action from the contact.

### Claim 20 (depends on 1)

The relationship management system of claim 1, wherein the relationship management server system is further configured to score event information associated with the user and at least one of the contacts.
