US20180295074A1

US20180295074A1 - Method and System for Exchanging Emails

Info

Publication number: US20180295074A1
Application number: US15/956,360
Authority: US
Inventors: Fabrice Dumans
Original assignee: TIMYO HOLDINGS Inc
Current assignee: TIMYO HOLDINGS Inc
Priority date: 2013-06-26
Filing date: 2018-04-18
Publication date: 2018-10-11
Also published as: IL248758A0; US9973452B2; US20150007051A1; US8930827B1; US20150007052A1; US9191345B2; CN107004178A; JP2017520046A; US20150007048A1; US20150319123A1

Abstract

A system for organization, preparation and viewing of an email. The system includes a graphical user interface operating on a display of a computing device. The graphical user interface has a writing interface including a “To: . . . ” field, a “Subject: . . . ” field, and a “When . . . ” field. The graphical user interface also includes a reading interface having a “Schedule” field and an organizing interface with a plurality of organizing functions.

Description

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a method and a system of exchanging emails. The invention can be used with any device that allows sending emails through a web browser, which includes personal computers, tablets or mobile phones. It can also be used through any email software that runs on any such device. The invention modifies the way a user writes and sends emails in a way that it is easier for the sender and the receiver of such emails to organize, sort and treat their emails.

2. Description of the Related Art

The volume of emails sent and received has many people feeling as though they are drowning under a flood of email. Endless messages come in waves faster than you can ever hope to deal with them, discussion threads in their n^thlap, file attachments that need your edits or comments (again), tasks your boss asked you to finish, favors your colleagues have asked of you, meetings you're supposed to be a part of, newsletters you signed up for, never-ending personal messages, semi solicited sales messages, or spam that crept in in-spite of all those spam filters. With all of this many of us feel like we are spending more time playing catch up with emails, rather than actually getting quality work done, and are forever hounded by the nagging feeling that we have missed something.
Common acceptance argues that we've got the problem all wrong. If email deluge is a problem, we are part of the problem. We are not using email for what it was meant for or for what it was designed for. It is from this the problem of email, chaos stems, as does the problem of constant distraction and productivity sapping due to email interruptions. Email is actually working against us.
Daily e-mail volume is now at 247 billion a day worldwide and increasing, as projected by The Radicati Group, a market research firm. To top that, there will be around 40 trillion spam e-mail messages delivered in 2009. A late 2007 Basex Research study estimated that businesses lose $650 billion annually in productivity due to unnecessary e-mail interruptions. Additionally, the average number of corporate e-mails sent and received per person per day is expected to reach over 228 by the year 2015.
Until the development of the present email exchange system, all solutions to the problem of email overload have assumed that the torrent on incoming mail is an uncontrollable variable. Most approaches revolve around “management” of email influx, and the approaches are helpless about actually controlling the torrent of emails. For example, the following strategies have been contemplated:

- Accommodate it All: With latest storage technologies allowing the storage of greater and greater amounts of data more easily, one approach is to simply expand storage space. The attitude simply is - bring on the email deluge, we can take it.
- Better Search: Another variant of the above approach is to improve search capabilities of the email system. The vast sea of emails remains, but we find better ways to dive in and retrieve the email we want.
- Better Spam Filters: Another approach is to develop more intelligent spam filters, which ensure that only legitimate emails end up in your inbox. The question to be asked here is, how much of the problem is actually caused by spam?
- The “Getting Things Done” Approach: Another approach is that of “managing your inbox better”. You can find endless articles online, each written by people who have devised individual strategies around better managing email deluge and maximizing productivity.
- Better managing your email time: Many email battered experts suggest the time you spend checking and responding to emails should be strictly managed. Turn notifications off and curb the obsessive compulsive urge to go check mail every ten minutes expecting a critical mail in your inbox.
- Effectively Organizing your Email: The second strategy revolves around better categorizing and filing the emails you receive. Emails could be filed in “go through”, or “urgent”, or “doesn't need attention right now” folders, which can be checked according to priority.
- Subject Lines: Another solution is to modify and optimize the subject lines of emails so that you can easily search and retrieve them when the need arises.

Exemplary of such systems is US Patent Application Publication No. 2009/0106370 which describes a computer-implemented method of sorting electronic messages, the system sorts the email by identifying at least one recipient of an electronic message and retrieving a classification scheme of the recipient. An identifier can be included within the electronic message. The identifier can specify a tag selected from the classification scheme of the recipient. The electronic message, including the identifier specifying the selected tag, can be sent.
The common thread in all the above approaches is that they're fatalistic. There is no attempt to define the problem, or an attempt to seek out “how did we get here in the first place”. The problem has been accepted as a given—that we can't get away from a sea of emails.
As it is well appreciated the objective of technology, including email, is to enhance employee productivity and information management, the present system and methodology attempts to overcome the problems associated with the overburdened email systems by helping users reduce the email deluge, streamline information management and increase overall productivity.

SUMMARY OF THE INVENTION

It is, therefore, an object of the present invention to provide a system for organization, preparation and viewing of an email, including a graphical user interface operating on a display of a computing device. The graphical user interface has a writing interface including a “To: . . . ” field, a “Subject: . . . ” field, and a “When” field. The graphical user interface also includes a reading interface having a “Schedule” field and an organizing interface with a plurality of organizing functions.
A writer on the home screen of the graphical user interface simply clicks upon the write icon (that is, the new email icon) for instant access to various functions associated with the writing interface and the writing interface for the preparation of a new email is presented. The writing interface includes a traditional “To: . . . ” field and a traditional “Subject: . . . ” field. Accordingly, the writing interface is designed to function in manner people have become accustom to when they write an email. The writer first defines the “To . . . ” field and the “Subject . . . ” field. Thereafter, the writer defines the “When . . . ” field. The “When . . . ” field allows the user to designate “What should this person do with this email?”—selecting “REPLY,” “READ-ONLY” or “TO-DO”; When would you like this to be done?”—selecting “ASAP,” “TODAY,” “TOMORROW,” or “PICK DATE”; and finally select the “Notification Style”—designating when it should be read, for example, “Please Read-Only by Tomorrow”. This information is then saved and incorporated into the “When” field.
It is appreciated writers will be preparing emails using various computing devices and operating systems, for example, laptops, desktops, smartphones, mobile communication devices, etc. As such, the underlying concepts of the present invention may be achieved using various interface set-ups.
However, and in contrast to traditional email preparation interfaces, the present writing interface, upon the initiation of the preparation of an email, prompts the writer with a series of screens allowing the writer to append specific instructions to the email for processing by the computing device of the recipient; that is, the writing interface allows the writer the option of appending various instructions indicating that which is expected of the recipient with regard to the sent email.
Other objects and advantages of the present invention will become apparent from the following detailed description when viewed in conjunction with the accompanying drawings, which set forth certain embodiments of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a front view of a computing device showing the home screen of the present system.

FIG. 2 is a schematic overview of the present system.

FIGS. 3A-E, 4, and 5 disclose functionalities associated with the writing interface of the present system.

FIG. 6 is a view of the home screen showing the ToDo icon after the creation of a task with the number of tasks noted adjacent thereto.

FIG. 7 is a view of an email after the establishment of a task.

FIGS. 8 and 9 show the conversation functionality associated with the writing interface.

FIGS. 10 and 11 show the conversation functionality associated with the reading interface.

FIGS. 12, 13 and 14 show the ability of a writer to designate emails for classification in various folders.

FIGS. 15A-15C show reader interfaces in accordance with the present invention.

FIGS. 16-22 show various functionalities associated with the reading interface.

FIGS. 23-35 show various functionalities associated with the organizing interface.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

The detailed embodiments of the present invention are disclosed herein. It should be understood, however, that the disclosed embodiments are merely exemplary of the invention, which may be embodied in various forms. Therefore, the details disclosed herein are not to be interpreted as limiting, but merely as a basis for teaching one skilled in the art how to make and/or use the invention.
Referring to the various figures, a communication method and system 10 for the organization, preparation and viewing of emails is disclosed. The communication system 10 operates on any available computer system 16 and is employed through a graphical user interface 20 displayed upon a display 18 of the available computer system 16. It is appreciated the computer system 16 may take the form of a desktop computer, laptop computer, tablet computer, smartphone, or other available computer system. Similarly, it is appreciated the display 18 may take various forms including a conventional monitor with a keyboard/mouse interface, a touchscreen allowing for direct physical interface with the display as is commonly employed with tablet computers and smartphones, or other interface formats known to those skilled in the art.
In practice, and with reference to FIG. 2, the present communication method and system 10 allow for communication between and amongst various individuals 12 connected over a global communication network 14, for example, via the Internet. The present disclosure refers to various participants of the communication method and system 10 as writers and recipients. However, it is appreciated writers of such emails will most certainly also be recipients of such emails and recipients of such emails most certainly will be writers of such emails. Ultimately, both writers and recipients are simply users of the present system taking advantage of the efficiencies offered thereby.
The present communication method and system 10 is especially suited for enterprise level deployment and, as such, it is appreciated various features and functionalities may be modified, locked or initiated by an administrator of the present enterprise level system. The communication method and system 10 provides for the organization, preparation and viewing of emails based upon instructions provided by the writer of the email. As such, a recipient may rely upon such instructions so that the writer will be confident that such emails will be properly considered. The communication method and system 10 also enhances the efficiency of the recipient who may rely upon the instructions of the writer without necessitating any complicated actions on the part of the recipient to ensure the email is timely considered and acted upon.
The communication method and system 10 relies upon a graphical user interface 20 operating on a display 18 of the computing device 16. The graphical user interface 20 includes a writing interface 22 with a plurality of writing functions, a reading interface 24 with a plurality of reading functions; and an organizing interface 26 with a plurality of organizing functions. As will be appreciated based upon the following disclosure, the functions are accessed in a convenient and intuitive manner using icons allowing for ready access to the plurality of writing functions, the plurality of reading functions and the plurality of organizing functions. The use, function and positioning of these functions will become apparent with the following disclosure.
Referring to FIGS. 3A-3E, 4, 5, 8, and 9, the plurality of writing functions includes recipient action identifier(s) 44 indicating what is expected of the recipient with regard to the sent email. The recipient action identifier(s) 44 are appended to the email and deployed by a computing device 16 of a recipient upon receipt of the email by the recipient. As will be appreciated based upon the following disclosure, this information is used by software in the computing device 16 of the recipient in determining the folder in which the writer has designated the email should be stored.
For example, an email prepared at the writer's computing device is appended with action identifier(s) 44. When it is received at the recipient's computing device 16, it is placed in the appropriate folder(s) in accordance with the mechanism implemented in accordance with the present invention.
Briefly, and with reference to FIG. 1, the home screen 28 of the graphical user interface 20 provides a plurality of distinct icons allowing for instant access to various functions associated with the writing interface 22, reading interface 24 and the organizing interface 26 as well as indicators providing the user with instant knowledge regarding the status of various functionalities associated with the present system 10. For example, the user, i.e. the writer, may immediately begin writing an email by simply clicking upon the write icon 30. Similarly, the user, i.e. the recipient, may immediately: begin reading emails requiring an answer by simply clicking upon the read/answer icon 32; begin reading emails requiring an associated action by simply clicking upon the read/ToDo icon 34; or begin reading emails simply requiring that the emails be read by clicking upon the read/read icon 36. The number of emails in each category is specified by a designator, i.e. red (or another distinctly visible color) numbers 64a-c associated with the specific icon. Where organization is required, the recipient may click upon emails required to be read on a specific date by clicking on a late read icon 38, a timely read icon 40 or an early read icon 42. The recipient might also wish to access emails via the calendar icon 66 or simply check an inbox 67.
As mentioned above, and with particular reference to FIGS. 3A-3E, 4, 5, 8, and 9, the present system 10 offers a variety of writing functions associated with the writing interface 22. As will be fully appreciated based upon the following disclosure, these functionalities, once activated and identified by the writer, are appended to the email and applied by the computing device 16 of the recipient upon receipt of the email by the recipient.
With this in mind, and when a writer desires to send an email, an intuitive writing interface 22 provides a mechanism for preparing and sending emails in an efficient and effective manner. The intuitive writing interface 22 helps the writer to write emails such that with a few simple clicks, vital information, which assists both the writer and recipient, is provided to the recipient. The implementation of these functionalities enhances user experience in reading emails. In contrast to traditional email preparation interfaces, the present writing interface 22, upon the initiating of the preparation of an email, the system 10 prompts the writer with a series of screens allowing the writer to append specific instructions to the email for processing by the computing device 16 of the recipient; that is, the writing interface 22 allows the writer the option of appending various instructions indicating that which is expected of the recipient with regard to the sent email.
Referring to FIGS. 1 and 3A-C, with the writer on the system home screen 28, he or she simply clicks upon the write icon (that is, the new email icon) 30 and a writing interface 22 for the preparation of a new email is presented (see FIGS. 3A-C). The writing interface 22 includes a traditional “To: . . . ” field 48 and a traditional “Subject: . . . ” field 50. Accordingly, the writing interface 22 is designed to function in manner people have become accustom to when they write an email. The writer first defines the “To . . . ” field 48 and the “Subject . . . ” field 50 (see FIG. 3A). Thereafter, the writer defines action identifier(s) 44 using the “When . . . ” field 51. The “When . . . ” field 51 allows the user to designate “What should this person do with this email?”—selecting “REPLY,” 53 “READ-ONLY” 55 or “TO-DO” 57; When would you like this to be done?”—selecting “ASAP,” 59 “TODAY,” 61 “TOMORROW,” 63 or “PICK DATE” 65; and finally select the “Notification Style”—designating when it should be read, for example, “Please Read-Only by Tomorrow” 67 (see FIG. 3B). This information is then saved and incorporated into the “When” field 51 (see FIG. 3C).
It is appreciated writers will be preparing emails using various interfaces, for example, laptop/desktop interfaces, mobile communication device interfaces, etc. As such, the underlying concepts of the present invention may be achieved using various interface set-ups, for example, see the smartphone interface shown in FIGS. 3A-C or the laptop interface shown in FIGS. 3D and 3E.
As for the actual writing of the email, the writing interface 22 provides the writer with a traditional text box 58 in which he or she can write a desired message.
Referring now to FIGS. 4, 5, and 6, it is further appreciated the writing interface 22 may be used in creating an action to be accomplished. The writer creates an action to remind themselves that they are required to take a specific action by a specific date. In particular, the writer clicks upon the ToDo icon 60 of the writing interface 22 and then proceeds to create an “email” (that is, a notice for some action the writer, themself, must undertake) identifying that the writer is required to perform a specific action (as noted in the writing block 48) in accordance with the email. Such an email, when addressed to the writer will go into the Todo folder 94 of the writer. When the writer desires to view the created action, it is displayed as a received ToDo message, as shown in FIG. 7. The act folder 62 is used to store all kinds of acknowledgements, from the simple click on the acknowledgement icon 72 to any short message such as a thank you note, an agreement or disagreement note, or a specific action, such as, I'm talking care of it soon.
The writing interface 22 is further provided with a communication format function 80. For example, the communication format function allows the writer to switch from communicating in an email (long) form (see FIG. 8) to communicating in a short format protocol (see FIG. 9) by simply checking the conversation mode icon 81 which provides the writer with the writing interface. For example, the writer might wish to employ Short Message Service (SMS). It is appreciated that SMS is a text messaging service component of phone, web, or mobile communication systems, using standardized communications protocols that allow the exchange of short text messages between fixed line or mobile phone devices. The term “SMS” as used herein, and as understood by those skilled in the art is used as an acronym for all types of short text messaging and the user activity itself in many parts of the world.
Where the writer wishes to communicate in a short format protocol, he or she simply clicks upon the conversation mode icon 81 and the graphical user interface switches to an interface format suitable for short format protocol communication as shown in FIG. 9. As is appreciated, the recipient computer system will open the interface format suitable for short format protocol communications and thereby will open the connection between the two individuals.
Similarly, and as will be appreciated based upon the following disclosure, the reading interface 24 is provided with a conversation mode icon 82 allowing for immediate communication via short format protocol with the writer of a short format protocol communication received by the recipient (see FIGS. 10 and 11). As such, it is appreciated that the communication format function 80 provided in conjunction with the reading interface 24 employs features of the writing interface 22, and an overlap of functionalities does exist. As such, the conversation format 80 can be chosen while writing the message or while reading the message.
The writing interface 22, in conjunction with the organizing interface 26, allows the writer to designate the emails or short format protocol communications for classification in various folders, 90 a, 92 a, 94 a, 96 a, 98 a, 100 a, 102 a as shown in FIGS. 12 and 13. Accordingly, the writer may specify folders into which the email should go when received by the recipient; for example “Urgent” 90, “Answer” 92, “ToDo” 94, “Inform” 96, “Think” 98, “Classify” 100 and “Private” 102 (see FIG. 12). It is appreciated the present system has been developed for enterprise level usage and such the designators may be adapted and adjusted to suit the needs of the specific companies.
As such, an email prepared at the writer's computing device 16 is appended with a folder identifier, for example, “Urgent” 90. When it is received at the recipient's computing device 16, it is placed in the appropriate folder(s) 90 a (recipient's Urgent folder) in accordance with the mechanism implemented in accordance with the present invention. It is appreciated that such an email may also have action identifier(s) 44 or other identifiers discussed herein.
Referring now to FIGS. 15 to 22 when the recipient receives emails, they are processed and available for review via the reading interface 24. Using the reading interface 24, the present communication method and system 10 offers a variety of reading functions. These reading functions include icons 32, 34, 36 identifying emails based upon a recipient action identifier 44 applied by the writer of the mail, and a read calendar 66 indicating dates on which received emails are intended to be read and/or due to be read.
First, the reading interface 24 allows the reader to notify the sender while the reader is in the process of scheduling the email for a later reply. It has been found that people are not very comfortable to schedule a date to answer an email in the next 3 or 4 days because they are mainly under the pressure of the current status-quo of email, that is, they feel they must answer an email as soon as possible. As a result, the present invention allows readers the ability to schedule a date to answer an email (for yourself) and to inform the sender right away (and automatically) that the reader will come back with a reply a few days later.
In accordance with this embodiment, and with reference to FIGS. 20A, the reader defines the “Schedule” field 91. The “Schedule” field 91 allows the user to designate “When they would like to deal with this email?”—selecting “TODAY,” 93 “TOMORROW,” 95 “THIS MONDAY” 97 or “PICK DATE” 99 (for the smartphone interface as shown in FIG. 20A); and whether the reader wishes to “Send a Notification to the Sender” 101. This information is then saved and incorporated into the “Schedule” field 91.
It is appreciated that readers will be preparing emails using various interfaces, for example, laptop/desktop interfaces, mobile communication device interfaces, etc. As such, the underlying concepts of the present invention may be achieved using various interface set-ups.
With scheduling available, and in accordance with an alternate embodiment as shown with reference to FIGS. 20B and 20C, the reader interface 24 for a reader using the present system will be provided with tabs allowing a reader to designating those emails requiring a response “Today” 103 and those emails requiring a response “Later” 105. In particular, it has been appreciated that inboxes are mainly a messy space. In order to help people to be better organized and have less stress, the present invention focuses on what immediately matters to the reader. As a result, adding only a “Today” and a “Later” dimension is the ultimate simplicity but the way the reader can really be more efficient.
As with other interfaces employed in accordance with the present invention, it is appreciated readers will be preparing emails using various interfaces, for example, laptop/desktop interfaces, mobile communication device interfaces, etc. As such, the underlying concepts of the present invention may be achieved using various interface set-ups, for example, see the smartphone interface shown in FIG. 20B or the laptop interface shown in FIG. 20C.
With this in mind, and when a recipient desires to read an email, he or she may select amongst various ways in which the recipient accesses the received emails. For example, and with reference to FIG. 16, the recipient may read and review emails based upon the recipient action identifier 44 associated with the emails. In particular, and as discussed above, each email sent by a writer is labeled with a recipient action identifier 44 and is accordingly categorized as such, for example, by placement within predesignated folders as specified by instructions provided by the writer, when disclosed in the reading interface.
In accordance with a preferred embodiment, the reading interface 24, of the recipient, as shown in FIG. 1, is provided with an icon indicating emails requiring an answer 32, an icon indicating emails specifying an action to be undertaken 34 (i.e. ToDo), and an icon indicating emails that are solely intended for reading 36 (i.e. Read). As such, when a recipient wishes to read emails requiring an action, he or she simply clicks on the icon indicating emails requiring an answer 32 and a display is opened showing all of the emails requiring an answer. Such a procedure may similarly be used for emails simply requiring reading and emails requiring action on the part of the recipient.
In the alternative, the recipient may read emails based upon the read date indicated by the writer. With this in mind, the reading interface 24 includes a calendar icon 66 (FIG. 1) linking to a read calendar 68 (FIGS. 16 and 17) indicating dates on which received emails are intended to be read. Once the read calendar 68 is opened, the recipient is provided with colored numbers 70 in each of the days of the read calendar 68 indicating the number of emails necessary to be read on the specific date. The numbers are actually color coded to provide an indication as to the timeliness of the recipient's action in reading the emails. For example, emails that are to be read in the future are noted with, for example, the color green, emails that are to be read on or around the actual day are noted with, for example, the color yellow, and emails that were to be read in the past are noted, for example, with the color red. As such, and as with the emails requiring an action, the recipient clicks on the icon indicating emails requiring reading on a specific date, and a display is opened showing all of the emails requiring reading on the specified date.
As shown with reference to FIG. 16, the reading interface 24 allows user to combine the filtering based upon reading dates and the filtering based upon the recipient action identifiers 44. In particular, and once in the read calendar 68, the recipient may click on an action icon 32, 34, 36 to limit emails from a specific date to emails from that specific date as well as emails requiring the specific action identified.
It is also appreciated a recipient can also specify some contacts as special VIP contacts. Any email sent by one of these VIP contacts will be accessible or copied in a predetermined folder 104 a-c. Attention is directed to FIGS. 18 and 19, where the VIP contacts are exposed upon checking a VIP directional icon 105 on the home screen 28 and the reading interface 24 shows icons 104a-c that will immediately direct a reader to a graphical user interface showing specifically messages sent by such VIP contacts.
Referring now to FIGS. 20, 21 and 22, the recipient may take various actions with received emails. In addition to replying to emails 106 and acting upon emails, the recipient is provided with the option to forward or otherwise deal with emails. For example, and upon receipt of an email, the recipient is provided with the option of forwarding the email 108 or employing the required action or ToDo function 110.
The required action or ToDo function 110 is employed in a manner allowing the recipient of an email to transform any email into a task that will be treated as any email that was sent using the present system. Such an email will go into the Todo folder 94 of the recipient providing him, or her, an indication that some action must be achieved.
As for forwarding an email, the recipient clicks upon the forward icon 108 which results in the recipient being prompted with the option to simply forward the email 112, overlook the email 114 or take over the email 116 (see FIG. 21).
The forward function 112 is similar to a traditional forward function and allows a recipient to simply forward an email to a selected individual.
In addition to simply forwarding emails, the recipient may select the takeover function 118 for use in conjunction with an email being forwarded. In accordance with this functionality, the email and the added data as sent by the original writer is sent to another individual for action. The forwarded email can also be stored in a required action or ToDo folder 94a (as shown in FIG. 13). This email inherits all the data that has been sent by the initial sender. Both the initial sender and the forwarding sender, or only one of them, can be notified when the end receiver has treated or read the email. Further, the recipient may forward the email with an overlook function 120. This function, when the forwarding individual activates the overlook function, informs the subsequent recipient that when he or she is forwarding an email in order to warn the recipient of the email that he only needs to have a quick look at this email. As shown with reference to FIG. 22, when the emails are reviewed in the reading interface 24 they are provided with various icons indicative of their status and designation.
Referring to FIGS. 23-35, in addition to the writing functions and the reading functions, a plurality of organizing functions is provided. The plurality, of organizing functions, is primarily addressed via the organizing interface 26. As explained below in greater detail, the functionalities include an acknowledgement icon 72; a status identifier 74 allowing a recipient to provide a writer with the status of a previously requested recipient action; and writer status storage icon 62 providing a writer with a list 78 of previously requested actions and the status thereof.
With reference to FIG. 24, as to the acknowledgement icon 72, and in accordance with a preferred embodiment, the organizing interface 26 provides a single icon allowing a user to indicate to someone else that the recipient agrees with the email or that the recipient likes the email, or that the recipient thanks the writer.
As mentioned above, the organizing interface 26 provides a mechanism for identifying the status of a requested action (see FIG. 25). This mechanism allows the user to select status identifiers 74 from such status identifiers such as done 74 a, in progress 74 b, late 74 c and/or skip 74 d, for example, and shown in FIG. 26 such indicators as shown in conjunction with emails.
The status information provided by the recipient may be accessed by the writer using the writer status storage icon 62 which provides a writer with a list 78 of previously requested actions and the status thereof (see FIG. 26).
In addition to the functionalities discussed above, the organizing interface 26 can also provide an email rating 120 allowing a recipient to rate the received email (see FIG. 28), and tools for monitoring usage of the present communication method and system 10 by a user (see FIGS. 29, 30 and 31). With this in mind, the invention allows any user to score an email based on its pertinence, and a user or any person having access to the administration of the system can then analyze all the scores. Other statistics such as the number of received emails, the daily/weekly/monthly average number of sent/received emails, the most contacted people, the average response delay, the average difference between the response date and the read date, for each item or globally, can also be computed from the invention.
With reference to FIGS. 32, 33, 34 and 35 a response scheduling functionality for scheduling, preparation and delivery of responses to emails is provided. The delay between reception, the read date and/or the acknowledgement may be useful for a recipient and/or a manager. As shown in FIGS. 32 and 33, a swipe of an email 122 will bring up a display allowing the recipient to include an email for a reply later today 124, tomorrow 126, week's end 128, next week 130, a specific day of the month 132 or when other action is completed 134. Similarly, and with reference to FIGS. 34 and 35, the recipient may click upon the ongoing icon 136 for a list of emails which then may be scheduled by simply checking upon and using the same description discussed above with regard to FIG. 34.
The organizing interface also allows the recipient to check emails and archive the emails in the folders of choice. The recipient simply clicks upon the classify icon 100 a (see FIG. 23) on the email and indicates the folder in which various emails should be stored.
In addition to the features discussed above, it is appreciated the present system may implement all the other common features already known to emails, such as file attachments, automatic address book update with new email addresses present in sent or received emails, orthographic and grammar correction, style, etc.
The functionalities and interfaces described herein may be implemented by typical computer systems. As such, embodiments of the present invention may be implemented as programmable code for execution by such a computer system. Such a computer system includes one or more processors. The processor(s) may be any type of processor, including but not limited to a special purpose or a general-purpose digital signal processor. The processor is connected to a communication infrastructure (for example, a bus or network). Various software implementations are described in terms of this exemplary computer system. After reading this description, it will become apparent to a person skilled in the art how to implement the invention using other computer systems and/or computer architectures.
The computer system also includes a main memory, preferably random access memory (RAM), and may also include a secondary memory. The secondary memory may include, for example, a hard disk drive and/or a removable storage drive, for example, a floppy disk drive, a magnetic tape drive, an optical disk drive, etc. The removable storage drive reads from and/or writes to a removable storage unit in a well-known manner, wherein the removable storage unit may be a floppy disk, magnetic tape, optical disk, etc., which is read by and written to by removable storage drive. As will be appreciated, removable storage unit includes a computer usable storage medium having stored therein computer software and/or data.
The computer may also include a removable storage unit and an interface. Examples of such means may include a program cartridge and cartridge interface (such as that previously found in video game devices), a removable memory chip (such as an EPROM, or PROM, or flash memory) and associated socket, and other removable storage units and interfaces which allow software and data to be transferred from removable storage unit to computer system. The program may also be executed and/or the data accessed from the removable storage unit, using the processor of the computer system. It is also appreciated the computer system may also include a communication interface allowing software and data to be transferred between computer system and external devices.
The terms “computer program medium” and “computer usable medium” are used generally to refer to media such as removable storage drive, a hard disk installed in hard disk drive, and signals. These computer program products are means for providing software to computer system. However, these terms may also include signals (such as electrical, optical or electromagnetic signals) that embody the computer program disclosed herein.
Computer programs (also called computer control logic) are stored in main memory and/or secondary memory. Computer programs may also be received via communication interface. Such computer programs, when executed, enable computer system to implement embodiments of the present invention as discussed herein. Accordingly, such computer programs represent controllers of computer system. Where the embodiment is implemented using software, the software may be stored in a computer program product and loaded into computer system using removable storage drive, hard disk drive, or communication interface, to provide some examples.
Alternative embodiments may be implemented as control logic in hardware, firmware, or software or any combination thereof.
While the preferred embodiments have been shown and described, it will be understood that there is no intent to limit the invention by such disclosure, but rather, is intended to cover all modifications and alternate constructions falling within the spirit and scope of the invention.

Claims

1. A system for organization, preparation and viewing of an email, comprising:

a graphical user interface operating on a display of a computing device, the graphical user interface including:

a writing interface including a “To: . . . ” field, a “Subject: . . . ” field, and a “When . . . ” field;

a reading interface including a “Schedule” field; and

an organizing interface with a plurality of organizing functions.

2. The system according to claim 1, wherein the “When . . . ” field allows a user to designate what should be done with the email, when should action be taken with regard to the email, and when should the email be read.

3. The system according to claim 2, wherein the “Schedule” field allows a user to designate when the user would like to deal with the email and whether a notification should be sent to the sender.

4. The system according to claim 1, wherein the “When . . . ” field allows a user to designate what should be done with the email.

5. The system according to claim 1, wherein the “When . . . ” field allows a user to designate when action should be taken with regard to the email.

6. The system according to claim 1, wherein the “When . . . ” field allows a user to designate when the email should be read.

7. The system according to claim 1, wherein the “Schedule” field allows a user to designate when a user would like to deal with the email and whether a notification should be sent to the sender.

8. The system according to claim 1, wherein the “Schedule” field allows a user to designate when a user would like to deal with the email.

9. The system according to claim 1, wherein the “Schedule” field allows a user to designate whether a notification should be sent to the sender.