Method and apparatus to ensure correct recipient lists on e-mail through context, learning and company profiles
Publication Date: 2012-Sep-14
The IP.com Prior Art Database
This article provides details of a method by which an Email is analysed to ascertain the correctness of the recipient list in the context of the message content and the recipient list itself. Additionally, utilising historic data of incorrect recipients, modifications made with regards to particular recipients and recipient lists, pattern recognition and recipient coupling as input to the system to determine the correctness of said Email recipient list.
Page 01 of 2
Method and apparatus to ensure correct recipient lists on e -mail through context, learning and company profiles
Sending an e-mail within a company utilising predictive completion of e-mail address can commonly lend itself to e-mails being sent to the incorrect participants. For instance, within a company there may be:
email@example.com - Performance Team Lead firstname.lastname@example.org - IT Solutions Architect email@example.com - Legal Counsel
If a user is not paying enough attention to the predictive search and completion then he/she can very easily incorrectly address an Email.
Current implementations allow for personal contact lists that are queried prior to the company directories but this still results in a number of incorrectly addressed e-mails.
Herein there is proposed a system whereby the e-mail body is inspected for keywords and matched against profiles for those included on the recipient list. Recipients can include keywords not associated (or these can be learnt by the system on common mistakes) to provide a secondary layer of assurance.
Common recipient coupling is also compared and history of addresses changed after inspection used to improve the system accuracy.
If the system identifies a recipient it does not think matches the context of the message or is typically incorrect in relation to co-recipients based on historical information and profile biography, the user is provided with this information on send, with the o...