Automated contact management

A contact communication system comprising:

• a computer executable application including:
• identifier generation logic configured to generate a first unique exchange identifier,
• event identification logic configured to receive information regarding an event, the event optionally including sending of an e-mail, text message or a social media connection,
• code generation logic configured to generate a first machine readable code encoding the first unique exchange identifier and the information regarding the event,
• placement logic configured to place the first code within a message, such as an e-mail, connection invitation or text message,
• logging logic configured to generate a log of when or where the first code was placed,
• contact storage logic configured to store contact information of a user of the mobile device,
• contact reception logic configured to receive a second machine readable code from a third party, the second code encoding a second exchange identifier and contact information of the third party, the contact reception logic may be configured to receive the second machine readable code via a camera or by parsing the message, and
• communication logic configured to communication the first exchange code and the information regarding the event to a remote destination;
• and
• a contact server including:
• log reception logic configured to receive the first exchange code and optionally the information regarding the event from the mobile device via a communication network,
• user tracking logic configured to track events and exchange of contact information by the user,
• user connection logic configured to suggest introduction to third parties to the user, and
• user authentication logic configured to authenticate that the first exchange identifier was generated by the user.

A contact communication system comprising:

• storage configured to store contact information and relationships for a plurality of device users, the plurality of device users including a first party and a second party;
• user connection logic configured to receive information regarding an identity of the first party from the second party and to establish a two-way exchange of contact information between the first party and the second party, the two-way exchange including sending contact information of the first party to the second party and sending contact information of the second party to the first party;
• user authentication logic configured to determine that the information regarding the identity of the first party is authentic and has been provided to the second party by the first party;
• and
• log reception logic configured to log interactions between the first party and the second party.

A method of communicating contact information, the method comprising:

• receiving a request to communicate contact information;
• selecting a set of contact information to communicate;
• receiving information regarding an event;
• generating a unique identifier;
• associating the unique identifier with the contact information and optionally the information about the event;
• generating an encoding the unique identifier and the contact information, the encoding optionally being a visible object;
• displaying the visible object or the like;
• logging transfer of the contact information, in a log of contact information transfer;
• and
• communicating the log of the transfer of the contact information to a remote device.

A method of performing a two-way exchange of contact information based on a one-way exchange of a machine readable code, the method comprising:

• generating the machine readable code, the machine readable code regarding (e.g., being associated with or including) an identity of a first party;
• displaying the machine readable code on a display of a first device of the first party, or adding the machine readable code to a message to be sent by the first party;
• reading the machine readable code using a second device of a second party;
• sending information encoded in the machine readable code from the second mobile device to a contact management server;
• optionally authenticating the information sent to the contact management server as being sent by the first party to the second party;
• identifying both the first party and the second party at the contact management server;
• establishing a relationship between the first party and the second party, in response to receiving the information sent to the contact management server from the second device;
• sending the second party contact information of the first party, based on the established relationship;
• and
• sending the first party contact information of the second party, based on the established relations, thus achieving the two-way exchange of contact information.