# US 11,909,836 B2 · Systems and methods for updating confidence scores of labels based on subsequent electronic activities

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

- Number: US 11,909,836 B2
- Document ID: US11909836B2
- Status: Granted
- Kind: B2
- Application number: 17/683,240
- Filed: 2022-02-28
- Published: 2022-06-16
- Granted: 2024-02-20
- Earliest claimed: 2018-05-24
- Assignees: People.ai, Inc.
- Applicants: People.ai, Inc.
- Inventors: John Wulf; Sathya Hariesh Prakash; Vardhman Jain; Stefan Hermanek; Wei Hai; Oleg Rogynskyy
- Web page: https://patentgrep.com/patent/US11909836B2

## CPC

- G06Q 10/107: Computer-aided management of electronic mailing [e-mailing]
- G06F 7/14: Merging, i.e. combining at least two sets of record carriers each arranged in the same ordered sequence to produce a single set having the same ordered sequence
- G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications}
- G06F 11/3024: {where the computing system component is a central processing unit [CPU]}
- G06F 11/3452: {Performance evaluation by statistical analysis}
- G06F 11/3495: {for systems}
- G06F 16/122: {using management policies (point-in-time backing up or restoration of persistent data G06F11/1446; file migration policies for HSM systems G06F16/185)}
- G06F 16/1734: {Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs}
- G06F 16/178: Techniques for file synchronisation in file systems
- G06F 16/182: Distributed file systems
- G06F 16/212: {with details for data modelling support}
- G06F 16/215: Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
- G06F 16/219: {Managing data history or versioning (querying versioned data G06F16/2474; querying temporal data G06F16/2477)}
- G06F 16/22: Indexing; Data structures therefor; Storage structures
- G06F 16/221: {Column-oriented storage; Management thereof}
- G06F 16/2228: {Indexing structures}
- G06F 16/2264: {Multidimensional index structures}
- G06F 16/2272: {Management thereof}
- G06F 16/23: Updating
- G06F 16/235: {Update request formulation}
- G06F 16/2358: {Change logging, detection, and notification (replication G06F16/27)}
- G06F 16/2365: {Ensuring data consistency and integrity}
- G06F 16/2379: {Updates performed during online database operations; commit processing}
- G06F 16/2386: {Bulk updating operations (data conversion details G06F16/258)}
- G06F 16/245: Query processing
- G06F 16/24558: {Binary matching operations}
- G06F 16/24564: {Applying rules; Deductive queries}
- G06F 16/2457: with adaptation to user needs
- G06F 16/24575: {using context}
- G06F 16/24578: {using ranking}
- G06F 16/2477: {Temporal data queries}
- G06F 16/254: {Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses}
- G06F 16/256: {in federated or virtual databases}
- G06F 16/26: Visual data mining; Browsing structured data
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F 16/273: {Asynchronous replication or reconciliation}
- G06F 16/28: Databases characterised by their database models, e.g. relational or object models
- G06F 16/285: {Clustering or classification}
- G06F 16/288: {Entity relationship models}
- G06F 16/289: {Object oriented databases}
- G06F 16/29: Geographical information databases
- G06F 16/313: {Selection or weighting of terms for indexing}
- G06F 16/337: {Profile generation, learning or modification}
- G06F 16/355: Creation or modification of classes or clusters
- G06F 16/901: Indexing; Data structures therefor; Storage structures (for retrieval from the web G06F16/951)
- G06F 16/9024: {Graphs; Linked lists (G06F16/9027 takes precedence)}
- G06F 16/90344: {by using string matching techniques}
- G06F 16/9035: Filtering based on additional data, e.g. user or group profiles
- G06F 16/906: Clustering; Classification
- G06F 16/93: Document management systems
- G06F 16/9535: Search customisation based on user profiles and personalisation
- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- G06F 21/6245: {Protecting personal data, e.g. for financial or medical purposes}
- G06F 40/20: Natural language analysis (semantic analysis of natural language G06F40/30)
- G06F 40/237: Lexical tools
- G06F 40/295: Named entity recognition
- G06F 40/30: Semantic analysis
- G06N 3/08: Learning methods
- G06N 3/09: Supervised learning
- G06N 5/022: Knowledge engineering; Knowledge acquisition
- G06N 5/025: Extracting rules from data
- G06N 5/04: Inference or reasoning models
- G06N 7/02: using fuzzy logic (computing arrangements based on biological models G06N3/00; computing arrangements using knowledge-based models G06N5/00)
- G06Q 10/04: Forecasting or optimisation specially adapted for administrative or management purposes, e.g. linear programming or "cutting stock problem" (market predictions or forecasting for commercial activities G06Q30/0202)
- G06Q 10/063114: {Status monitoring or status determination for a person or group}
- G06Q 10/06312: {Adjustment or analysis of established resource schedule, e.g. resource or task levelling, or dynamic rescheduling}
- G06Q 10/06315: {Needs-based resource requirements planning or analysis}
- G06Q 10/06393: {Score-carding, benchmarking or key performance indicator [KPI] analysis}
- G06Q 10/06398: {Performance of employee with respect to a job function}
- G06Q 10/109: Time management, e.g. calendars, reminders, meetings or time accounting
- G06Q 10/1091: Recording time for administrative or management purposes
- G06Q 10/1093: Calendar-based scheduling for persons or groups
- G06Q 10/40: Business processes related to social networking or social networking services
- G06Q 30/0201: Market modelling; Market analysis; Collecting market data
- G06Q 50/22: Social work or social welfare, e.g. community support activities or counselling services
- G16H 50/20: for computer-aided diagnosis, e.g. based on medical expert systems
- H04L 12/14: Charging, metering or billing arrangements specially adapted for data communications, e.g. authentication, authorisation and accounting [AAA] framework
- H04L 12/1831: {Tracking arrangements for later retrieval, e.g. recording contents, participants activities or behavior, network status}
- H04L 41/082: the condition being updates or upgrades of network functionality
- H04L 41/14: Network analysis or design
- H04L 43/026: using flow identification
- H04L 43/045: for graphical visualisation of monitoring data
- H04L 43/062: related to network traffic
- H04L 43/065: related to network devices
- H04L 43/067: using time frame reporting
- H04L 43/0876: Network utilisation, e.g. volume of load or congestion level
- H04L 43/14: {using software, i.e. software packages (network security related monitoring H04L63/1408)}
- H04L 51/046: Interoperability with other network applications or services
- H04L 51/212: using filtering or selective blocking
- H04L 51/234: for tracking messages
- H04L 51/42: Mailbox-related aspects, e.g. synchronisation of mailboxes
- H04L 61/45: Network directories; Name-to-address mapping
- H04L 67/125: involving control of end-device applications over a network
- H04L 67/30: Profiles
- H04L 67/303: Terminal profiles
- H04L 67/306: User profiles
- H04L 67/535: {Tracking the activity of the user (network monitoring arrangements H04L43/00; recording of computer activity G06F11/34)}
- H04M 3/436: Arrangements for screening incoming calls {, i.e. evaluating the characteristics of a call before deciding whether to answer it (based on the calling party profile H04M3/42059; based on location H04M3/42348; based on presence H04M3/42365; diversion H04M3/54)}
- H04M 3/5175: {Call or contact centers supervision arrangements}
- H04M 15/00: Arrangements for metering, time-control or time indication {; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP}
- H04M 15/41: {Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]}
- H04M 15/58: {based on statistics of usage or network monitoring}
- H04M 15/60: {based on actual use of network resources}
- H04M 15/66: {Policy and charging system}
- H04M 15/755: {Account identification}
- H04W 4/24: Accounting or billing
- G06F 40/205: Parsing
- G06N 20/00: Machine learning
- G06Q 10/10: Office automation; Time management
- G16H 15/00: ICT specially adapted for medical reports, e.g. generation or transmission thereof
- G16H 50/30: for calculating health indices; for individual health risk assessment
- H04L 12/1407: {Policy-and-charging control [PCC] architecture}
- H04L 43/08: Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L 61/4594: Address books, i.e. directories containing contact information about correspondents (telephone directories in user terminals H04M1/27453)
- H04L 2101/00: Indexing scheme associated with group H04L61/00
- H04L 2101/35: containing special prefixes
- H04L 2101/37: E-mail addresses
- H04M 3/2218: {Call detail recording}
- H04M 3/56: Arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities (video conference systems H04N7/15)
- H04M 15/50: {for cross-charging network operators}
- H04M 2203/556: Statistical analysis and interpretation
- 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)
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

The present disclosure relates to methods, systems, and storage media for updating confidence scores of labels based on subsequent electronic activities. Exemplary embodiments may maintain a plurality of node profiles corresponding to a plurality of unique entities; access a plurality of electronic activities transmitted or received via electronic accounts associated with one or more data source providers; identify a first electronic activity to process; assign a tag to the first electronic activity based on the data included in the electronic activity; determine a confidence score of the tag based on the data included in the first electronic activity; identify a second electronic activity to process; and update the confidence score of the tag assigned to the first electronic activity responsive to parsing the second electronic activity.

## Claims

### Claim 1

A method comprising:
maintaining, by one or more processors, a plurality of node profiles corresponding to a plurality of unique entities, each node profile of the plurality of node profiles including one or more node field-value pairs, each node field-value pair of the node profile associated with a corresponding field and a node field value;
accessing, by the one or more processors, a plurality of electronic mails transmitted or received via electronic accounts associated with one or more data source providers, the one or more processors configured to update the plurality of node profiles using the plurality of electronic mails;
identifying, by the one or more processors, a first electronic mail to process, the first electronic mail determined to be linked to a first node profile and a second node profile of the plurality of node profiles;
assigning, by the one or more processors, a tag to the first electronic mail based on the data included in the first electronic mail;
determining, by the one or more processors, a confidence score of the tag based on the data included in the first electronic mail, the confidence score of the tag indicating a likelihood that the tag is correct;
identifying, by the one or more processors, a second electronic mail to process, the second electronic mail determined to be linked to at least one of the first node profile or the second node profile, the second electronic mail transmitted subsequent to the first electronic mail; and
updating, by the one or more processors, the confidence score of the tag assigned to the first electronic mail responsive to parsing the second electronic mail.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
determining, by the one or more processors, a relationship between a sender of the first electronic mail and at least one recipient of the one or more recipients of the first electronic mail using the node profiles of the sender and the at least one recipient included in the plurality of node profiles; and
wherein assigning the tag to the first electronic mail based on the data included in the first electronic mail comprises assigning, by the one or more processors, the tag to the first electronic mail based on the relationship between the sender and the one or more recipients.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
determining, by the one or more processors, that the first electronic mail identifies an event scheduled in a calendar of at least one of the sender or the one or more recipients; and
wherein assigning the tag to the first electronic mail based on the data included in the first electronic mail comprises assigning, by the one or more processors, the tag to the first electronic mail based on the type of event scheduled in the calendar.

### Claim 4 (depends on 3)

The method of claim 3, wherein updating the confidence score of the tag includes updating the confidence score of the tag responsive to determining that the second electronic mail includes one or more predetermined strings that map to different types of events.

### Claim 5 (depends on 1)

The method of claim 1, wherein the second electronic mail is a response to the first electronic mail.

### Claim 6 (depends on 1)

The method of claim 1, wherein the tag is based on the first node profile and the second node profile and is used to determine to match the first electronic mail to a record object of a system of record associated with the data source provider corresponding to the first electronic mail.

### Claim 7 (depends on 1)

The method of claim 1, wherein the tag is a first tag based on the first node profile and the second node profile, and wherein the method further comprises assigning a second tag to the first electronic mail responsive to parsing the second electronic mail and using the first tag and second tag to match the first electronic mail to a record object of a system of record associated with the data source provider corresponding to the first electronic mail.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
identifying, by the one or more processors, a third electronic mail to process, the third electronic mail determined to be linked to a third node profile and at least one of the first node profile or the second node profile;
updating, by the one or more processors, the tag of the first electronic mail based on the third node profile.

### Claim 9 (depends on 8)

The method of claim 8, further comprising:
determining, by the one or more processors responsive to parsing content of the third electronic mail, a context of the third electronic mail; and
wherein updating the tag of the first electronic mail based on the third node profile includes updating the tag based on the context of the third electronic mail.

### Claim 10 (depends on 9)

The method of claim 9, wherein the context of the third electronic mail is a third context, and wherein the method further comprises;
determining, by the one or more processors responsive to parsing content of the first electronic mail and second electronic mail, a first context of the first electronic mail and a second context of the second electronic mail;
determining, by the one or more processors, that the first electronic mail, the second electronic mail and third electronic mail are related based on the first context, the second context, and the third context; and
adding, by the one or processors, a second tag to the first electronic mail based on at least one of the first context, the second context, or the third context.

### Claim 11

A system comprising:
one or more hardware processors configured by machine-readable instructions to:
maintain a plurality of node profiles corresponding to a plurality of unique entities, each node profile of the plurality of node profiles including one or more node field-value pairs, each node field-value pair of the node profile associated with a corresponding field and a node field value;
access a plurality of electronic mails transmitted or received via electronic accounts associated with one or more data source providers, the one or more processors configured to update the plurality of node profiles using the plurality of electronic mails;
identify a first electronic mail to process, the first electronic mail determined to be linked to a first node profile and a second node profile of the plurality of node profiles;
assign a tag to the first electronic mail based on the data included in the first electronic mail;
determine a confidence score of the tag based on the data included in the first electronic mail, the confidence score of the tag indicating a likelihood that the tag is correct;
identify a second electronic mail to process, the second electronic mail determined to be linked to at least one of the first node profile or the second node profile, the second electronic mail transmitted subsequent to the first electronic mail; and
update the confidence score of the tag assigned to the first electronic mail responsive to parsing the second electronic mail.

### Claim 12 (depends on 11)

The system of claim 11, wherein the one or more hardware processors are further configured by machine-readable instructions to:
determine a relationship between a sender of the first electronic mail and at least one recipient of the one or more recipients of the first electronic mail using the node profiles of the sender and the at least one recipient included in the plurality of node profiles;
wherein to assign the tag to the first electronic activity, the one or more hardware processors are further configured by machine-readable instructions to assign the tag to the first electronic mail based on the relationship between the sender and the one or more recipients.

### Claim 13 (depends on 11)

The system of claim 11, wherein the one or more hardware processors are further configured by machine-readable instructions to:
determine that the first electronic mail identifies an event scheduled in a calendar of at least one of the sender or the one or more recipients;
wherein to assign the tag to the first electronic mail, the one or more hardware processors are further configured by machine-readable instructions to assign the tag to the electronic mail based on the type of event scheduled in the calendar.

### Claim 14 (depends on 13)

The system of claim 13, wherein to update the confidence score of the tag, the one or more hardware processors are configured to update the confidence score of the tag responsive to determining that the second electronic mail includes one or more predetermined strings that map to different types of events.

### Claim 15 (depends on 11)

The system of claim 11, wherein the tag is based on the first node profile and the second node profile and is used to determine to match the first electronic mail to a record object of a system of record associated with the data source provider corresponding to the first electronic mail.

### Claim 16 (depends on 11)

The system of claim 11, wherein the tag is a first tag based on the first node profile and the second node profile, and wherein the one or more hardware processors are further configured to assign a second tag to the first electronic mail responsive to parsing the second electronic mail and use the first tag and second tag to match the first electronic activity to a record object of a system of record associated with the data source provider corresponding to the first electronic mail.

### Claim 17 (depends on 11)

The system of claim 11, wherein the one or more hardware processors are further configured by machine-readable instructions to:
identify a third electronic mail to process, the third electronic mail determined to be linked to a third node profile and at least one of the first node profile or the second node profile;
update the tag of the first electronic mail based on the third node profile.

### Claim 18 (depends on 17)

The system of claim 17, wherein the one or more hardware processors are further configured by machine-readable instructions to:
determine, responsive to parsing content of the third electronic mail, a context of the third electronic mail;
wherein to update the tag of the first electronic activity based on the third node profile, the one or more hardware processors are configured to update the tag based on the context of the third electronic mail.

### Claim 19 (depends on 18)

The system of claim 18, wherein the context of the third electronic activity is a third context;
wherein the one or more hardware processors are further configured by machine-readable instructions to determine, responsive to parsing content of the first electronic activity and second electronic activity, a first context of the first electronic mail and a second context of the second electronic mail;
wherein the one or more hardware processors are further configured by machine-readable instructions to determine that the first electronic mail, the second electronic mail and third electronic mail are related based on the first context, the second context, and the third context; and
wherein the one or more hardware processors are further configured by machine-readable instructions to add a second tag to the first electronic mail based on at least one of the first context, the second context, or the third context.

### Claim 20

A non-transitory computer-readable storage medium having instructions embodied thereon, the instructions being executable by one or more processors to cause the one or more processors to:
maintain a plurality of node profiles corresponding to a plurality of unique entities, each node profile of the plurality of node profiles including one or more node field-value pairs, each node field-value pair of the node profile associated with a corresponding field and a node field value;
access a plurality of electronic mails transmitted or received via electronic accounts associated with one or more data source providers, the one or more processors configured to update the plurality of node profiles using the plurality of electronic mails;
identify a first electronic mail to process, the first electronic mail determined to be linked to a first node profile and a second node profile of the plurality of node profiles;
assign a tag to the first electronic mail based on the data included in the first electronic mail;
determine a confidence score of the tag based on the data included in the first electronic mail, the confidence score of the tag indicating a likelihood that the tag is correct;
identify a second electronic mail to process, the second electronic mail determined to be linked to at least one of the first node profile or the second node profile, the second electronic mail transmitted subsequent to the first electronic mail; and
update the confidence score of the tag assigned to the first electronic mail responsive to parsing the second electronic mail.