either minimal or extensive, depending on the context. For example, minimal customization may
involve determining relevant details of the person to contact for the inquiry based on the context,
and including this information in the standard automatic response. Alternatively, pertinent
details may be incorporated into the static user provided response where appropriate, for
example, based on topics or keywords in incoming emails. In some cases, extensive
customization involves generating a new free-form text response to the email.
Prediction model(s) (106) may be trained and optimized for different criteria. For
example, machine learning techniques for extracting relevant metadata or content could be
optimized to identify private and sensitive information and exclude such content from the
automatic response to preserve user privacy. Similarly, matching can be optimized based on
semantic analysis and clustering (e.g., of different topics) so that the incoming emails are
appropriately matched with relevant email communication previously received by the user.
To avoid sharing potentially sensitive data, users are enabled to configure privacy
settings in advance. For example, a default privacy level is tailored such that content included in
the automatic reply does not include sensitive data. A user interface (108) is provided to easily
customize and turn on and off privacy options. For example, the present techniques can be either
disabled completely or selectively disabled, e.g., for internal versus external emails and
customized, turned off for particular groups, etc. Also, the user interface allows automatic
replies to be turned off.
For emails corresponding to sensitive matters, only contact information of the relevant
people who can respond to the email sender is included in the automatic reply while in more
permissive contexts, additional details could be incorporated. These additional details in the
context of a project may include relevant events related to the project (conference/meeting),