# US 10,769,639 B2 · Client relationship management system for multiple independent parties > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,769,639 B2 - Document ID: US10769639B2 - Status: Granted - Kind: B2 - Application number: 16/058,454 - Filed: 2018-08-08 - Published: 2020-02-13 - Granted: 2020-09-08 - Earliest claimed: 2018-08-08 - Assignees: Client 4 Life Group, LLC. - Applicants: Client 4 Life Group, LLC. - Inventors: Korbin King; Amber Hawkins; Alex Reed - Web page: https://patentgrep.com/patent/US10769639B2 ## CPC - G06Q 30/01: Customer relationship services - G06F 16/903: Querying (for retrieval from the web G06F16/953) - G06Q 10/1093: Calendar-based scheduling for persons or groups - 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 A novel system and process for managing multiple parties in a client relationship process is described. The system manages three independent parties including a client, an account manager, and an advisor. Records are retrieved from a file for a group of all clients that are part of the client relationship process. The records are displayed as user interface widgets that indicate status of client relationship for the group. Based on time periods expiring combined with no other contacts to a client having been made, a client relationship campaign of advisor, client being in a pre-defined tier, and client not being part of an active sales campaign, a script is retrieved for use during a follow-up communication. Account manager uses script to contact client. Answers received are stored into record in database associated with client in a hierarchical tree structure. Alerts, follow-up actions, and updating of user interface widgets are triggered. ## Claims ### Claim 1 A computer-based method of managing multiple parties in a client relationship process, the computer-based method comprising: based on one or more time periods expiring combined with no other contacts to a third party having been made by either a first party or a second party, and the third party is not part of an active sales campaign governed by the first party, retrieving from a record from a database at least a script as part based on a combination of a client relationship campaign of a first party and at least one of three predefined tiers of a third party, for use during a follow-up communication carried out by a second party with a third party, and in which each of the first party, the second party and the third party are different parties, the record in the database including the client attribute indicating whether the third party is a contact with no previous relationship with the first party, a contact with a current relationship with the first party but has not yet purchased a good or a service from the first party, or a client; storing answers received from the third party by the second party during the follow-up communications, using a hierarchical tree structure that summarizes answers in a predefined format, into the record in the database associated with the third party, wherein the hierarchical tree structure includes a plurality of branch nodes, each branch node linked directly by paths to a parent node and at least one child node, and whereby an answer received at a branch node defines a path to a child node; and triggering, based on the script, at least one of follow-up alerts and follow-up actions; and presenting in real-time on a graphical user interface, the answers about the third party received by the second party using the predefined format in the database, along with the at least one of follow-up alert and follow-up actions, as part of a dashboard displayed to the first party, the dashboard further including a summary of contacts complete, where the color of the contacts complete are presented in one of three colors depending on a percentage complete. ### Claim 2 (depends on 1) The computer-based method of claim 1, wherein the calling of the third party by the second party is based on the third party being categorized into one of the three predefined tiers. ### Claim 3 (depends on 1) The computer-based method of claim 1, wherein the one or more time periods expiring is a checkup call interval. ### Claim 4 (depends on 1) The computer-based method of claim 1, wherein the calling of the third party by the second party is based on the third party being categorized into one of the three predefined tiers. ### Claim 5 (depends on 1) The computer-based method of claim 1, further comprising: calling the third party by the first party based on the third party being categorized into another one of the three predefined tiers. ### Claim 6 (depends on 1) The computer-based method of claim 1, further comprising: storing preferences provided by the first party for the client relationship campaign, the preferences include script variables, contact variables, and meeting variables. ### Claim 7 (depends on 6) The computer-based method of claim 6, further comprising: storing preferences provided by the first party for the client relationship campaign, the preferences include a number of days required to prepare for a meeting with the third party, preparation time required between each meeting, duration of the meeting, and preferred location of the meeting. ### Claim 8 (depends on 6) The computer-based method of claim 6, further comprising: storing preferences provided by the first party for the client relationship campaign, the preferences include a frequency of call attempts, a number of days in between contact attempts, and four telephone call attempts to be scheduled as a default as two separate telephone calls during different afternoon time periods, one call in a morning time period, and one call in an evening time period. ### Claim 9 (depends on 6) The computer-based method of claim 6, further comprising: storing preferences provided by the first party for the client relationship campaign, the preferences include the type of script associated with the corresponding client attribute indicating whether the third party is a contact with no previous relationship with the first party, a contact with a current relationship with the first party but has not yet purchased a good or a service from the first party, or a client, the offer of the client relationship campaign, the first party's contact information, and specific language to be used in the script, with the possibility of removing certain questions. ### Claim 10 (depends on 1) The computer-based method of claim 1, wherein the script is encoded using a markup language. ### Claim 11 (depends on 1) The computer-based method of claim 1, further comprising: retrieving from the database a series of records for a group of all third parties including the third party that are part of a client relationship process; presenting a plurality of graphical user interface widgets indicating at least one of follow-up alerts, follow-up actions, and status of the client relationship process for the group of all third parties. ### Claim 12 (depends on 1) The computer-based method of claim 1, wherein the script includes contents for recording a voice mail left at a telephone number of the third party, the contents are based on the preferences set by the first party. ### Claim 13 (depends on 12) The computer-based method of claim 12, wherein the voice mail is generated using text-to-speech. ### Claim 14 A system for multiple parties in a client relationship process, the system comprising: a computer memory capable of storing machine instructions; and a hardware processor in communication with the computer memory, the hardware processor configured to access the computer memory, the hardware processor performing based on one or more time periods expiring combined with no other contacts to a third party having been made by either a first party or a second party, and the third party is not part of an active sales campaign governed by the first party, retrieving from a record from a database at least a script as part based on a combination of a client relationship campaign of a first party and at least one of three predefined tiers of a third party, for use during a follow-up communication carried out by a second party with a third party, and in which each of the first party, the second party and the third party are different parties, the record in the database including the client attribute indicating whether the third party is a contact with no previous relationship with the first party, a contact with a current relationship with the first party but has not yet purchased a good or a service from the first party, or a client; storing answers received from the third party by the second party during the follow-up communications, using a hierarchical tree structure that summarizes answers in a predefined format, into the record in the database associated with the third party, wherein the hierarchical tree structure includes a plurality of branch nodes, each branch node linked directly by paths to a parent node and at least one child node, and whereby an answer received at a branch node defines a path to a child node; and triggering, based on the script, at least one of follow-up alerts, and follow-up actions; and presenting in real-time on a graphical user interface, the answers about the third party received by the second party using the predefined format in the database, along with the at least one of follow-up alert and follow-up actions, as part of a dashboard displayed to the first party, the dashboard further including a summary of contacts complete, where the color of the contacts complete are presented in one of three colors depending on a percentage complete. ### Claim 15 (depends on 14) The system of claim 14, wherein the calling of the third party by the second party is based on the third party being categorized into one of the three predefined tiers. ### Claim 16 (depends on 14) The system of claim 14, wherein the one or more time periods expiring is a checkup call interval. ### Claim 17 (depends on 14) The system of claim 14, wherein the calling of the third party by the second party is based on the third party being categorized into one of the three predefined tiers. ### Claim 18 (depends on 14) The system of claim 14, further comprising: calling the third party by the first party based on the third party being categorized into another one of the three predefined tiers. ### Claim 19 A non-transitory computer program product tangibly embodying computer readable instructions which, when implemented, cause a computer to carry out the steps of a method for managing multiple parties in a client relationship process on a storage media, comprising: based on one or more time periods expiring combined with no other contacts to a third party having been made by either a first party or a second party, and the third party is not part of an active sales campaign governed by the first party, retrieving from a record from a database at least a script as part based on a combination of a client relationship campaign of a first party and at least one of three predefined tiers of a third party, for use during a follow-up communication carried out by a second party with a third party, and in which each of the first party, the second party and the third party are different parties, the record in the database including the client attribute indicating whether the third party is a contact with no previous relationship with the first party, a contact with a current relationship with the first party but has not yet purchased a good or a service from the first party, or a client; storing answers received from the third party by the second party during the follow-up communications, using a hierarchical tree structure that summarizes answers in a predefined format, into the record in the database associated with the third party, wherein the hierarchical tree structure includes a plurality of branch nodes, each branch node linked directly by paths to a parent node and at least one child node, and whereby an answer received at a branch node defines a path to a child node; and triggering, based on the script, at least one of follow-up alerts, and follow-up actions; and presenting in real-time on a graphical user interface, the answers about the third party received by the second party using the predefined format in the database, along with the at least one of follow-up alert and follow-up actions, as part of a dashboard displayed to the first party, the dashboard further including a summary of contacts complete, where the color of the contacts complete are presented in one of three colors depending on a percentage complete. ### Claim 20 (depends on 19) The non-transitory computer program product of claim 19, wherein the calling of the third party by the second party is based on the third party being categorized into one of the three predefined tiers.