Back to results
US 8,898,229 B2Granted
Contact management system and method
AssigneeBarclays Capital Inc.
InventorsJohn Andrew Harvey, George Richard Black, Michael Joseph Catchpole, Richard H. Mai, Gerald John McCormack, Aiko Muro, Dante R. Sarigumba, George Tierney
Life of this patent
Estimating the term…
Abstract
A contact management system is described having a first database containing proprietary information and a second database containing public information. Where appropriate, the publicly available information is displayed with the proprietary information to give the user more information about a contact. The multiple relationships provided by the public database allow the user to use both the proprietary and public data to find a relationship with a potential client.
Claims31
A contact management system comprising:
- one or more memory units each operable to store at least one program;
- and
- at least one processor communicatively coupled to the one or more memory units, the at least one processor configured to execute the at least one program;
- a first database containing proprietary contact information;
- a second database containing public contact information;
- a contact component for receiving proprietary contact information from a user for storage in the first database and presenting contact information to the user, wherein the presented contact information includes information retrieved from the first database and the second database, said contact component providing one or more links between contact information in the first and second databases;
- a referral component that receives referral data from the user, the referral data identifying a person as a potential referral in the proprietary database and identifying the user as a sponsor, the referral data being stored in the proprietary database, wherein the referral component receives a query from another user, the referral component accesses the proprietary database, the referral component compares a contact list of the other user to the referral data in the proprietary database to identify the potential referral and the sponsor;
- and
- an appointment component for receiving meeting data from a user and presenting one or more meeting alerts to the user, wherein when the meeting data includes a link to a meeting pattern of a recurring meeting, the appointment component generates a future meeting entry from the meeting pattern when a future meeting pattern is selected and the future meeting entry falls within a predetermined future time period and automatically generates one or more next future meeting entries from the meeting pattern upon expiration of at least a portion of the predetermined future time period.
6 more elements
A method comprising the steps of:
- retrieving proprietary contact information from a first database;
- retrieving public contact information from a second database;
- presenting to a user contact information comprising the proprietary contact information and the public contact information;
- providing one or more links between contact information in the first and second databases;
- receiving referral data from the user, the referral data identifying a person as a potential referral in the first database and identifying the user as a sponsor;
- receiving a query from another user;
- accessing the first database;
- comparing a contact list of the other user to the referral data in the first database to identify the potential referral and the sponsor;
- receiving meeting data from a user;
- and
- when the meeting data includes a link to a meeting pattern of a recurring meeting, generating a future meeting entry from the meeting pattern when the future meeting entry falls within a predetermined future time period and automatically generating one or more next future meeting entries from the meeting pattern upon expiration of at least a portion of the predetermined future time period.
8 more elements
A method comprising the steps of:
- requesting contact information of a contact;
- viewing the requested information, wherein the requested information includes proprietary information retrieved from a proprietary database and public information retrieved from a public database;
- providing one or more links between contact information in the proprietary and public databases;
- receiving referral data from the user, the referral data identifying a person as a potential referral in the first database and identifying the user as a sponsor;
- receiving a query from another user;
- accessing the first database;
- comparing a contact list of the other user to the referral data in the first database to identify the potential referral and the sponsor;
- sending meeting data to an appointment module;
- and
- when the meeting data includes a link to a meeting pattern of a recurring meeting, receiving, for insertion into a calendar of an attendee, a future meeting entry from the appointment module that is generated from the meeting pattern when the future meeting entry falls within a predetermined future time period, and the appointment component automatically generates one or more next future meeting entries from the meeting pattern upon expiration of at least a portion of the predetermined future time period.
7 more elements
Dependencies are inferred from the claim text.