MESSAGE TRACKING WITH THREAD-RECURRENT DATA

• US 20140136636A1
• Filed: 09/30/2013
• Published: 05/15/2014
• Est. Priority Date: 03/08/2004
• Status: Active Grant

• Current Assignee: NetSuite Inc. (Oracle Corporation)
• Original Assignee: NetSuite Inc. (Oracle Corporation)
• Inventors: Fabre, Patrice M., Kessman, Rosalina T., Forjindam, Yang
• Granted Patent: US 9,258,265 B2
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: G06Q 10/1095 Meeting or appointment
• CPC Class Codes: H04L 51/18 Commands or executable codes
• CPC Class Codes: H04L 51/234 for tracking messages

Abstract

A method, system, computer program product, and related business methods are described in the context of a web-based business information system having an internal email facility, wherein e-mail communications between a native e-mail system of an end user of the web-based business information system and an external contact are facilitated and automatically tracked by the web-based business information system, the native e-mail system lying outside the web-based business information system but often being preferred by the end user over the internal e-mail facility of the web-based business information system. The described preferred embodiments provide for easy-to-use, reasonably transparent, “no-click” integration of the web-based business information system with the end user'"'"'s native e-mail system in a manner that is independent of the particular type and choice of native e-mail system.

Claims

1-26. -26. (canceled)

27. A method of processing messages, comprising:

tracking a communication of a first message from a first user to a second user, the first message having a thread-recurrent field including a first field component identifying at least one of a plurality of communications categories and a second field component identifying a messaging thread involving the first user and the second user;

tracking a communication of a second message from the second user to the first user, the second message having a thread-recurrent field corresponding to the thread-recurrent field of the first message, the thread-recurrent field of the second message including a first field component identifying the at least one of the plurality of communications categories and a second field component identifying the messaging thread involving the first user and the second user; and

evaluating one or more rules related to message tracking functionality, the evaluation of the one or more rules based at least in part on the at least one of the plurality of communication categories identified by the first field component of the second message and the messaging thread identified by the second field component of the second message.

28. The method of claim 27, wherein the one or more rules related to message tracking functionality includes rules related to one or more of the routing, processing, or disposition of a message.

29. The method of claim 27, wherein the plurality of communications categories includes general correspondence, and the message tracking functionality comprises modifying the second message before the second message is received by the first user, the modified second message incorporating a modified version of a set of tracking information that includes the first field component identifying the at least one of the plurality of communications categories and the second field component identifying the messaging thread involving the first user and the second user.

30. The method of claim 27, wherein the plurality of communications categories includes trouble tickets, and the message tracking functionality comprises helpdesk functionality.

31. The method of claim 27, wherein the plurality of communications categories includes invitation replies, and the message tracking functionality comprises event organizing functionality.

32. The method of claim 31, wherein the event organizing functionality comprises one or more of setting a calendar appointment corresponding to a positive invitation reply or altering a resource allocation for an event based at least in part on an invitation reply.

33. The method of claim 27, wherein the evaluation of the one or more rules related to message tracking functionality is further based at least in part on a type or role of one or more of the first user and the second user.

34. The method of claim 33, wherein one or more of the set of rules evaluated or a way in which the rules are evaluated are based at least in part on the type or role of one or more of the first user and the second user.

35. The method of claim 27, wherein the first message comprises a first e-mail message and the second message comprises a second e-mail message sent in response to the first e-mail message.

36. The method of claim 27, wherein the thread-recurrent field of the first message further includes a cryptographic hash code based at least in part on one or more of the at least one of the plurality of communications categories and the thread of communications involving at least the first user and the second user.

37. The method of claim 36, wherein the cryptographic hash code inhibits tampering with one or more of the first field component and the second field component.

38. The method of claim 27, wherein one or more of tracking the communication of the first message from the first user to the second user and tracking the communication of the second message from the second user to the first user further comprises:

receiving one or more of the first message and the second message at a data processing element; and

processing the received message to identify one or more of the first field component and the second field component.

39. An Apparatus for processing messages, comprising:

a processor programmed to execute a set of instructions;

a data storage element in which the set of instructions are stored, wherein when executed by the processor the set of instructions cause the apparatus to

track a communication of a first message from a first user to a second user, the first message having a thread-recurrent field including a first field component identifying at least one of a plurality of communications categories and a second field component identifying a messaging thread involving the first user and the second user;

track a communication of a second message from the second user to the first user, the second message having a thread-recurrent field corresponding to the thread-recurrent field of the first message, the thread-recurrent field of the second message including a first field component identifying the at least one of the plurality of communications categories and a second field component identifying the messaging thread involving the first user and the second user; and

evaluate one or more rules related to message tracking functionality, the evaluation of the one or more rules based at least in part on the at least one of the plurality of communication categories identified by the first field component of the second message and the messaging thread identified by the second field component of the second message.

40. The apparatus of claim 39, wherein the one or more rules related to message tracking functionality includes rules related to one or more of the routing, processing, or disposition of a message.

41. The apparatus of claim 39, wherein the plurality of communications categories includes general correspondence, and the message tracking functionality comprises modifying the second message before the second message is received by the first user, the modified second message incorporating a modified version of a set of tracking information that includes the first field component identifying the at least one of the plurality of communications categories and the second field component identifying the messaging thread involving the first user and the second user.

42. The apparatus of claim 39, wherein the plurality of communications categories includes trouble tickets, and the message tracking functionality comprises helpdesk functionality.

43. The apparatus of claim 39, wherein the plurality of communications categories includes invitation replies, and the message tracking functionality comprises event organizing functionality.

44. The apparatus of claim 39, wherein the evaluation of the one or more rules related to message tracking functionality is further based at least in part on a type or role of one or more of the first user and the second user.

45. The apparatus of claim 39, wherein the first message comprises a first e-mail message and the second message comprises a second e-mail message sent in response to the first e-mail message.

46. The apparatus of claim 39, wherein the thread-recurrent field of the first message further includes a cryptographic hash code based at least in part on one or more of the at least one of the plurality of communications categories and the thread of communications involving at least the first user and the second user.

47. A method of processing a message, comprising:

receiving a message from a first user to a second user at a data processing element, the message having a thread-recurrent field including a first field component identifying at least one of a plurality of communications categories and a second field component identifying a messaging thread involving the first user and the second user; and

operating the data processing element to evaluate one or more rules related to message tracking functionality, the evaluation of the one or more rules based at least in part on the at least one of the plurality of communication categories identified by the first field component of the message and the messaging thread identified by the second field component of the message.

48. The method of claim 47, wherein the one or more rules related to message tracking functionality includes rules related to one or more of the routing, processing, or disposition of a message.

49. The method of claim 47, wherein the evaluation of the one or more rules related to message tracking functionality is further based at least in part on a type or role of one or more of the first user and the second user.