Automatically managing email communications using indirect reply identity resolution
Methods and systems are enclosed herein for automatically managing email communication between a group of users and a group of target prospects. A sequence of outbound emails is automatically sent on behalf of a user to a prospect. Based upon the prospect's inbound replies (or lack thereof) the system will perform preconfigured actions, such as stopping automated communications and deferring to the user for manual action.
1. A non-transitory computer-readable medium comprising memory with instructions encoded thereon for automatically managing email communication between a user and a known prospect, the instructions comprising:
first instructions to detect an email received at an email inbox of a first user;
second instructions to extract a first portion of metadata and a second portion of metadata from a header of the email;
third instructions to determine whether the first portion of metadata matches first information in a first entry of a first database, the first entry corresponding to the known prospect;
fourth instructions to, responsive to determining that the first portion of metadata matches the first information in the first entry of the first database, determine that the email is associated with the known prospect;
fifth instructions to determine whether the second portion of metadata matches second information in a second entry of a second database, the second entry indicating whether a copy of the email, received at an email inbox of a second user, is already stored to the second database;
sixth instructions to, responsive to determining that the second portion of metadata matches the second information in the second entry of the second database, discard the email; and
seventh instructions to, responsive to determining that the second portion of metadata does not match the second information in the second entry of the second database, store the email to the second database in association with the known prospect.
2. The non-transitory computer-readable medium of claim 1 , wherein the first portion of metadata comprises a user identifier.
3. The non-transitory computer-readable medium of claim 2 , wherein the third instructions to determine whether the first portion of metadata matches the first information in the first entry of the first database comprise further instructions to determine whether the user identifier is an exact match to a known user identifier of the known prospect in the first database.
4. The non-transitory computer-readable medium of claim 2 , wherein the third instructions to determine whether the first portion of metadata matches the first information in the first entry of the first database comprise eighth instructions to:
determine that the user identifier is not an exact match to a known user identifier of the known prospect in the first database;
determine whether the user identifier has a character match with one or more of a first name and a last name of the known prospect; and
responsive to determining that the user identifier has the character match with the one or more of the first name and the last name of the known prospect, determine that the first portion of metadata matches the first information in the first entry of the first database.
5. The non-transitory computer-readable medium of claim 4 , wherein the eighth instructions further comprise ninth instructions to, further responsive to determining that the user identifier has the character match with the one or more of the first name and the last name of the known prospect, associate the user identifier with the known prospect.
6. The non-transitory computer-readable medium of claim 1 , wherein the second portion of metadata comprises a message identifier.
7. The non-transitory computer-readable medium of claim 6 , wherein the fifth instructions to determine that the second portion of metadata matches the second information in the second entry of the second database comprise eighth instructions to determine that the message identifier matches a separate message identifier stored in association with the email inbox of the second user.
8. The non-transitory computer-readable medium of claim 1 , wherein the instructions further comprise eighth instructions to, further responsive to determining that the second portion of metadata matches the second information in the second entry of the second database, associate the copy of the email with the known prospect.
9. The non-transitory computer-readable medium of claim 1 , wherein the first database and the second database are a same database.
10. A method for automatically managing email communication between a user and a known prospect, the method comprising:
detecting an email received at an email inbox of a first user;
extracting a first portion of metadata and a second portion of metadata from a header of the email;
determining whether the first portion of metadata matches first information in a first entry of a first database, the first entry corresponding to the known prospect;
responsive to determining that the first portion of metadata matches the first information in the first entry of the first database, determining that the email is associated with the known prospect;
determining whether the second portion of metadata matches second information in a second entry of a second database, the second entry indicating whether a copy of the email, received at an email inbox of a second user, is already stored to the second database;
responsive to determining that the second portion of metadata matches the second information in the second entry of the second database, discarding the email; and
responsive to determining that the second portion of metadata does not match the second information in the second entry of the second database, storing the email to the second database in association with the known prospect.
11. The method of claim 10 , wherein the first portion of metadata comprises a user identifier.
12. The method of claim 11 , wherein determining whether the first portion of metadata matches the first information in the first entry of the first database comprises determining whether the user identifier is an exact match to a known user identifier of the known prospect in the first database.
13. The method of claim 11 , wherein determining whether the first portion of metadata matches the first information in the first entry of the first database comprises:
determining that the user identifier is not an exact match to a known user identifier of the known prospect in the first database;
determining whether the user identifier has a character match with one or more of a first name and a last name of the known prospect; and
responsive to determining that the user identifier has the character match with the one or more of the first name and the last name of the known prospect, determining that the first portion of metadata matches the first information in the first entry of the first database.
14. The method of claim 13 , wherein the method further comprises, further responsive to determining that the user identifier has the character match with the one or more of the first name and the last name of the known prospect, associating the user identifier with the known prospect.
15. The method of claim 10 , wherein the second portion of metadata comprises a message identifier.
16. The method of claim 15 , wherein determining that the second portion of metadata matches the second information in the second entry of the second database comprises determining that the message identifier matches a separate message identifier stored in association with the email inbox of the second user.
17. The method of claim 10 , wherein the method further comprises, further responsive to determining that the second portion of metadata matches the second information in the second entry of the second database, associating the copy of the email with the known prospect.
18. The method of claim 10 , wherein the first database and the second database are a same database.
19. A system comprising:
memory with instructions encoded thereon; and
one or more processors that, when executing the instructions, are caused to perform operations comprising:
detecting an email received at an email inbox of a first user;
extracting a first portion of metadata and a second portion of metadata from a header of the email;
determining whether the first portion of metadata matches first information in a first entry of a first database, the first entry corresponding to a known prospect;
responsive to determining that the first portion of metadata matches the first information in the first entry of the first database, determining that the email is associated with the known prospect;
determining whether the second portion of metadata matches second information in a second entry of a second database, the second entry indicating whether a copy of the email, received at an email inbox of a second user, is already stored to the second database;
responsive to determining that the second portion of metadata matches the second information in the second entry of the second database, discarding the email without storing the email to the second database in association with the known prospect; and
responsive to determining that the second portion of metadata does not match the second information in the second entry of the second database,
storing the email to the second database in association with the known prospect.
20. The system of claim 19 , wherein the first portion of metadata comprises a user identifier.
21. The system of claim 20 , wherein determining whether the first portion of metadata matches the first information in the first entry of the first database comprises determining whether the user identifier is an exact match to a known user identifier of the known prospect in the first database.
22. The system of claim 20 , wherein determining whether the first portion of metadata matches the first information in the first entry of the first database comprises:
determining that the user identifier is not an exact match to a known user identifier of the known prospect in the first database;
determining whether the user identifier has a character match with one or more of a first name and a last name of the known prospect; and
responsive to determining that the user identifier has the character match with the one or more of the first name and the last name of the known prospect, determining that the first portion of metadata matches the first information in the first entry of the first database.
23. The system of claim 22 , wherein the operations further comprise, further responsive to determining that the user identifier has the character match with the one or more of the first name and the last name of the known prospect, associating the user identifier with the known prospect.
24. The system of claim 19 , wherein the first database and the second database are a same database.