TECHNICAL FIELD

[0001] Aspects of the disclosure are related to computing hardware and software technology, and in particular to a reminder service for email.

BACKGROUND

[0002] Email triage is an exercise engaged in by email users in order to organize messages in their inbox or other folders. When triaging their email, users make quick decisions about how to handle a given email, such as by electing to delete an email, move an email to another folder, or mark an email for later follow up.

[0003J Some email applications provide specific features to assist with triage, such as the follow-up feature in Microsoft® Outlook® that allows a user to mark an email for follow up later that day, the next day, or even in a matter of weeks or more. A task is then scheduled in the task module, a reminder can be set for the task, and so on.

[0004] Users frequently user their mobile devices to triage email. Mobile situations tend to lend themselves to brief interactions with one's inbox, such as when traveling or at other moments when there is enough time to make some decisions with respect to an email, but not enough time to prepare a detailed response or otherwise respond at length.

[0005] Many mobile email applications lack some of the features and functionality as their desktop counterparts, and thus may not offer triaging capabilities. In such situations, users sometimes resort to ad-hoc solutions to triage their email, such as by marking read messages as "un-read" so as to capture their attention later. At the very least, some limited triage is possible by deleting messages, but this is largely a sub-optimal experience.

[0006] However, one solution supports email triage in a mobile environment by providing a triage view of a user's mail in terms of those messages that have been triaged and those that remain un-triaged. The user can navigate to the triaged emails or possibly to the un-triaged emails. When dealing with the un-triaged emails, the user can elect an email to be handled next or deferred for later reference. A specific task can also be created in association with an email, such as to place a call or schedule a meeting related to the email.

[0007] As a user progresses through their email, various tasks will be created which can then be viewed later by way of a desktop email client. In addition to viewing their inbox, a user may view their tasks in the desktop email client, organized in various ways, such as by the task type or by when the tasks are due.

SUMMARY

[0008] Provided herein are systems, methods, and software for implementing a reminder service that allows users to organize email in an email application such that they may be reminded about a follow-up action in another application.

[0009] In at least one implementation, a reminder service receives action information indicative of an email selected for follow-up action in an email application. The reminder service identifies an additional application through which to surface a reminder about the follow-up action and communicates reminder information to the additional application with which to render the reminder.

[0010] In some implementations, a user interface to an email service may be rendered that includes a triage menu through which to select a follow-up action for an email. Another user interface to an additional service may also be rendered that includes a reminder about the follow-up action for the email.

[0011 ] This Overview is provided to introduce a selection of concepts in a simplified form that are further described below in the Technical Disclosure. It may be understood that this Overview is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Many aspects of the disclosure can be better understood with reference to the following drawings. While several implementations are described in connection with these drawings, the disclosure is not limited to the implementations disclosed herein. On the contrary, the intent is to cover all alternatives, modifications, and equivalents.

[0013] Figure 1 illustrates an operational scenario in an implementation.

[0014] Figure 2 illustrates a triage process in an implementation.

[0015] Figure 3 illustrates a triage process in an implementation.

[0016] Figure 4 illustrates a triage process in an implementation.

[0017] Figure 5 A illustrates an operational scenario in an implementation.

[0018] Figure 5B illustrates an operational scenario in an implementation.

[0019] Figure 6 illustrates a user interface to an email application and an associated operational scenario in an implementation.

[0020] Figure 7 illustrates an operational scenario in an implementation. [00211 Figure 8 illustrates an operational scenario in an implementation.

[0022] Figure 9 illustrates a computing system in an implementation.

TECHNICAL DISCLOSURE

[0023] Implementations disclosed herein refer to a reminder service for enhancing email triage. When engaged with an email application, a user may select an email for a follow-up action. When engaged later with another application, such as another email client, a productivity application, a contacts application, or a game, for example, the user may be reminded of the email and the follow-up action. In this manner, awareness of email that is triaged using one application is not lost or dissipated when engaged with other applications.

[0024] In at least one implementation, a reminder service receives action information indicative of an email selected for follow-up action in an email application and responsively identifies an additional application through which to surface a reminder about the follow-up action. The reminder service communicates reminder information to the additional application with which to render the reminder.

[0025[ In some scenarios, the additional application may be selected from various other applications based at least in part on with which of the applications the follow-up action is associated. Examples of the other applications include, but are not limited to, a real-time communication application, a contacts application, a calendar application, a productivity application, and an additional email application. Examples of follow-up actions include reading the email later, replying to the email later, placing a call related to the email later, and scheduling a meeting related to the email later.

[0026] The follow-up action may be selectable in some implementations from a triage menu in the email application. The applications may be associated with the various follow-up actions such that, in at least one scenario, the follow-up action is associated with an additional email application and at least one other application. The additional application may be, for instance, a contacts application, in which case a reminder may be rendered in a user interface to the contacts application. The reminder may even be rendered in visual association with one of various contacts included in the user interface. In other instances, the additional application may be a productivity application, in which case the reminder may be rendered in a user interface to the productivity application. For example, the reminder may be included in a most recently used (M.R.U.) menu in visual association with a document represented in the most recently used menu. [0027] Referring now the drawings, Figure 1 illustrates an operational scenario in an implementation in which an email application and additional applications interact with a reminder service. Figures 2-4 illustrates triage processes employed by the email application, the reminder service, and the additional applications. Figure 5A and Figure 5B illustrate two more operational scenarios. Figure 6 illustrates a user interface to an email application in an operational scenario, as does Figure 7. Figure 8 illustrates a user interface to a contacts application and a user interface to a productivity application. Figure 9 illustrates a computing system representative of any apparatus, device, or collections thereof suitable for implementing a reminder service, an email application, or an additional application, and for implementing the various operational scenarios disclosed herein.

(0028] In operational scenario 100 illustrated in Figure 1, an email application 110 is in communication with a reminder service 115 to facilitate enhanced email triage.

Reminder service 115 may also be in communication with an additional application 120 and another additional application 130.

[0029] Email application 110 is representative of any software application, module, component, or collections thereof for conducting email, with which a user may engage in order to obtain access to and interact with an email service (not shown). Email application 110 is capable of employing triage process 200, described in more detail below with respect to Figure 2. Various types of physical or virtual computing systems may be used to implement email application 1 10, such as server computers, desktop computers, laptop computers, tablet computers, smart phones, gaming appliances, or any other suitable computing appliance, of which computing system 900, discussed below with respect to Figure 9, is representative. Email application 110 may be locally installed and executed, executed from within the context of a browser, streamed, or otherwise delivered in some other suitable manner, including combinations or variations thereof.

[0030] Reminder service 115 is representative of any software application, module, component, or collections thereof capable employing triage process 300 in support of triage decisions made with respect to email application 110. Reminder service 115 may be implemented in a stand-alone fashion or may be implemented within other environments in an integrated or cooperative fashion.

[0031] Various types of physical or virtual computing systems may be used to implement triage process 300 within the context of reminder service 115, such as server computers, desktop computers, laptop computers, tablet computers, smart phones, or any other suitable computing appliance, of which computing system 900, discussed below with respect to Figure 9, is representative. When implemented using a server computer, any of a variety of servers may be used including, but not limited to, application servers, database servers, mail servers, rack servers, blade servers, tower servers, or any other type of server, variation or combination thereof.

[0032] Additional application 120 is representative of any software application, module, component, or collection thereof, capable of rendering a reminder about an email selected for triage. Examples of additional application 120 include, but are not limited to, productivity applications, contact applications, calendar applications, games, and email applications, as well as any other type of application. Additional application 130 is also representative of such applications. Both additional application 120 and additional application 130 are capable of employing triage process 400 to facilitate enhanced triage. Various types of physical or virtual computing systems may be used to implement additional application 120 and additional application 130, such as server computers, desktop computers, laptop computers, tablet computers, smart phones, gaming appliances, or any other suitable computing appliance, of which computing system 900, discussed below with respect to Figure 9, is representative. Additional application 120 and additional application 130 may be locally installed and executed, executed within the context of a browser, streamed, or otherwise delivered in some other suitable manner.

[0033J In operational scenario 100, a user interacts with email application 110 through user interface 111, which is a user interface to an email service. For example, a user may interact with their email, compose or read messages, move and sort messages, or otherwise perform any number of actions using user interface 111.

[0034] User interface 111 includes a list of emails representative of those a user may encounter in an inbox, or some other folder, including email 112, email 113, and email 114. It may be appreciated that other elements are possible, in place of or in addition to those included in user interface 111, and may be considered within the scope of the present disclosure. It is assumed for exemplary purposes that email 113 has been selected for triaging, as indicated by its shaded representation.

[0035] In addition, a triage menu 118 has been selected or otherwise surfaced, which includes follow-up actions 1 16 selectable from the triage menu 118. A user input 117 or selection is made from the triage menu 118 of one of the follow-up actions 116, in response to which action information is communicated by email application 110 to reminder service 115. The action information identifies the email (or emails) and the follow-up action.

(0036] Reminder service 115 receives the action information and responsively identifies which additional application corresponds to the follow-up action identified in the action information. In this scenario, it is assumed for exemplary purposes that additional application 120 corresponds to the follow-up action. Accordingly, reminder service 115 communicates reminder information to additional application 120 indicative of the follow- up action and the email. Optionally, reminder service 115 may also communicate reminder information to additional application 130.

[00371 Additional application 120 receives the reminder information and presents it in user interface 121. User interface 121 includes interface element 122 and interface element 123, which are representative of any graphical elements, or any other type of element, that may be encountered in a user interface. A reminder 124 is rendered in user interface 121 such that a user may be reminded of the email and the follow-up action when interacting with interface elements in user interface 121. Reminder 124 is positioned in visual association with interface element 122 for exemplary purposes, although it may be appreciated that it may be arranged visually in user interface 121 in any other way.

[0038] Figure 2 illustrates triage process 200 which may be employed by email application 110 within the context of operational scenario 100, although it may be appreciated that triage process 300 could be employed in other scenarios. In operation, email application 110 renders a visual representation of follow-up actions (step 201). While triage menu is an example of a drop-down menu, a variety of other menus or other ways in which to present the follow-up actions from which a user may make a selection are possible and may be considered within the scope of the present disclosure.

[0039[ Next, email application 110 receive a selection input by a user via user interface 111 selecting a particular email or emails for triage and identifying one of the follow-up actions from the presentation of follow-up actions (step 203). The selection may be made by, for example, a gesture, a touch, a mouse click, or some other suitable user input.

[0040] Upon receiving the selection(s) via user interface 111 , email application 110 communicates action information to reminder service 115 indicative of the email or emails selected for triage and the associated follow-up action (step 205). Reminder service 115 may then handle the action information in accordance with triage process 300. [00411 Figure 3 illustrates triage process 300 which may be employed by reminder service 115 in the context of operational scenario 100, although it may be appreciated that triage process 300 could be employed in other scenarios. In operation, reminder service 115 receives action information from an email application, such as email application 110 (step 301). The action information identifies an email or emails selected for triage and an associated follow-up action. Reminder service 115 proceeds to identify which additional application or applications is associated with the follow-up action and through which a reminder may be surface (step 303).

[0042] In an example, the follow-up action may be to call a person associated with the triaged email, in which case the additional application associated with the follow-up action may be a dialer application, a contacts application, a voice calling application, or some other application generally associated with placing calls. In another example, the triaged email may include an attachment and the follow-up action may be to read the triaged email. The associated application may be a reader application or some other productivity application with which the attachment can be read. In yet another example, the follow-up action may be to schedule an event, in which case the associated application may be a calendar application.

[0043] Such associations between additional applications and follow-up actions may be configured at any time. The associations may be configured manually,

automatically, programmatically, or in some other manner. The follow-up actions may be associated with just one application but may also be associated with more than one application. The follow-up actions are generally associated with applications based on a functional relationship between the actions and the applications. For instance, a follow-up action to place a call may be associated with one or more applications suitable for placing a call. However, other associations can be made. Thus, an additional email application may be associated with any follow-up action so that reminders can be surfaced through the additional email application, regardless of whether or not the additional email application is suitable for performing the follow-up action.

[0044] Having identified the appropriate additional application or applications, reminder service 115 communicates reminder information to the application or

applications (step 305). Such communication may occur in a variety of ways, such in a push manner in which reminder service 115 initiates communication with the additional application(s) in order to transfer the reminder information. However, reminder service 115 may also be polled by the various applications on a periodic basis or some other basis. Other communication mechanisms are possible for conveying reminder information and may be considered within the scope of the present disclosure.

(0045] Figure 4 illustrates triage process 400 which may be employed by other applications, such as additional application 120 or additional application 130, in the context of operational scenario 100, although it may be appreciated that triage process 300 could be employed in other scenarios. In operation, user interface 121 is invoked and presented by additional application 120 (step 401). Before, during, or after when user interface 121 is invoked, additional application 120 receives reminder information from reminder service 115 indicative of a triaged email and an associated follow-up action (step 403).

[0046J The email and follow-up action may be identified directly in the reminder information. For instance, the reminder information may specifically identify the email by a name, a link, or some other identifier. The follow-up action may also be specifically identified by a name, a link, or some other identifier. However, the email and the follow- up action may be identified indirectly by the reminder information. For instance, the reminder information may merely indicate in general that an email exists that has been triaged and that has an associated follow-up action. Other ways of representing the email and the follow-up action in reminder information are possible, in addition to or in place of those disclosed herein, and may be considered within the scope of the present disclosure.

[0047J Having received the reminder information, additional application 120 renders a reminder in user interface 121 (step 405). The reminder may be represented in text, as a graphical element, or in some other manner that serves to visually remind a user about a triaged email. In some scenarios, the reminder may be rendered as an email icon or image, although other types of images are possible, such as a star, color coding, font modifications, and the like.

[0048] Figure 5 A illustrates another operational scenario 501 in an implementation in which multiple additional applications are capable of surfacing reminders, including an email application 520, a contacts application 530, and a calendar application 540. In addition, operational scenario 501 involves a personal information service 512 in the context of which a reminder service 515 may be implemented.

[0049] Examples of personal information service 512 include, but are not limited to, Microsoft® Exchange®, Gmail®, and Yahoo! ® Mail, as well as any other suitable personal information service, variation, or combination thereof. Reminder service 515 is representative of any software service, application, module, component, or variations and combinations thereof that may run within the context of personal information service 512. Personal information service 512 and reminder service 515 may be implemented using any suitable computing system or collection of computing systems, of which computing system 900 illustrated in Figure 9 is representative.

[0050] Email application 510 is representative of any email application, module, or component capable of communicating triage information. Email application 520 is representative of any email application, module, or component capable of receiving reminder information and surfacing a reminder. Contacts application 530 is representative of any contacts application, module, or component capable of receiving reminder information and surfacing a reminder. Calendar application 540 is representative of any calendar application, module, or component capable of receiving reminder information and surfacing a reminder.

[0051] Email application 510, email application 520, contacts application 530, and calendar application 540 may be implemented as separate applications or in an integrated fashion within the context of another application. In addition, email application 510, email application 520, contacts application 530, and calendar application 540 may be implemented on a single device or on multiple, different devices. Any combination of applications and devices is also possible and may be considered within the scope of the present disclosure.

[0052] In operational scenario 501, an email is selected for follow-up action and email application 510 communicates triage information indicative of the same to reminder service 515. The triage information may be communicated directly to reminder service 515 or indirectly through personal information service 512.

[0053] Reminder service 515 identifies which other applications are associated with the follow-up action indicated by the triage information and communicates reminder information to those applications about the triaged email. In operational scenario 501, it is illustrated that reminder service 515 communicates reminder information to all three of email application 520, contacts application 530, and calendar application 540. However, it may be appreciated that fewer than all three may be supplied with the reminder information.

[0054] In some implementations, an application that receives the reminder information may also be capable of replying to the reminder information. For example, an application may provide a user with the ability to dismiss or change the status of a triaged email through the user interface to that application. A follow-up action could be changed from one action to another, for example, or deleted entirely. In another example, a follow- up action could be marked as complete and a reply provided by an associated application to reminder service 515. The completed status of the follow-up action may then be provided to a user's mailbox or other email repository in personal information service 512.

[0055] Figure 5B illustrates yet another operational scenario 503 in an

implementation in which additional applications are capable of receiving reminder information from reminder service 515, but in some instances by way of an application service. In particular, operational scenario 503 involves email application 510, email application 520, contacts application 530, productivity application 545, personal information service 512, reminder service 515, application service 550, and reminder service 560.

(0056) In operational scenario 503, an email is selected for follow-up action and email application 510 communicates triage information indicative of the same to reminder service 515. The triage information may be communicated directly to reminder service 515 or indirectly through personal information service 512.

[0057] Reminder service 515 identifies which other applications are associated with the follow-up action indicated by the triage information and communicates reminder information to those applications about the triaged email. In operational scenario 501, it is illustrated that reminder service 515 communicates reminder information to email application 520 and to contacts application 530. However, reminder service 515 also communicates reminder information to reminder service 560, which resides in application service 550.

[0058] Reminder service 560 may be any software application, module, or component capable of receiving reminder information from reminder service 515.

Application service 550 may be any software application, service, module, component, or collections thereof, capable of providing a productivity application service to productivity application 545 and in which reminder service 560 may be hosted. Application service 550 and reminder service 560 may be implemented using any suitable computing system or collections of computing systems, of which computing system 900 is representative.

[0059] Reminder service 560, by way of application service 550, communicates reminder information to productivity application 545. Productivity application 545 may then surface a reminder to a user through a user interface to application service 550. It may be appreciated that, although reminder information is supplied to all three additional applications in operational scenario 503, in some scenarios fewer than all three may be involved.

(0060] In some implementations, an application that receives the reminder information may also be capable of replying to the reminder information. For example, an application may provide a user with the ability to dismiss or change the status of a triaged email through the user interface to that application. A follow-up action could be changed from one action to another, for example, or deleted entirely. In another example, a follow- up action could be marked as complete and a reply provided by an associated application to reminder service 515. The completed status of the follow-up action may then be provided to a user's mailbox or other email repository in personal information service 512.

[0061J Figure 6 illustrates an operational scenario 600 involving a user interface

601 to an email service. User interface 601 may be rendered by an email application executed by a suitable computing system, of which computing system 900 is

representative.

[0062] In operation, an initial view in user interface 601 is rendered that includes an inbox 610, a filter menu 620, a function menu 630, and a message preview pane 635. A user may interact with the various features and functions of user interface 601 to, for example, read and compose emails and other types of messages and notifications. In addition, a user may triage their email using some of the features and functions of user interface 601.

(0063) Inbox 610 includes various messages and other items, including email 611, email 612, text message 613, email 614, and a notification 615 of a missed phone call. Which items are displayed in inbox 610 may depend on how it is set to be filtered. In particular, filter menu 620 allows a user to filter items based on how they have been triaged. For example, filter menu 620 includes a control 621 for viewing all emails, a control 622 for viewing those selected be read later, a control 623 for viewing those selected to be replied to later, and a control 624 for performing triage and picking follow- up actions for any of the items in inbox 610.

[0064] Triage may also be performed on an email via function menu 630. In function menu 630, various options are available for whichever item is selected for viewing in message preview pane 635. In this scenario, email 614 has been selected and its content is displayed in message preview pane 635. Email 614 may be subject to the various controls in function menu 630, including a control 631 for forwarding an email, a control 632 for replying to an email, a control 634 for deleting an email, and a control 633 for surfacing a triage menu with which email 614 may be triaged.

(0065] Upon selection of control 633, represented by user input 641, a triage menu

650 is rendered which various follow-up actions included therein. The follow-up actions include one follow-up action 651 for reading the email later, a follow-up action 652 for replying to the email later, a follow-up action 653 for scheduling a meeting later, a follow- up action 654 for placing a call later, and a follow-up action 655 for texting later. It may be appreciated that other follow-up actions in addition to or in place of those disclosed herein may be included in triage menu 650. In addition, it may be appreciate that triage menu 650 may also be rendered in response to a selection of control 624.

[0066J Figure 7 illustrates an operational scenario 700 involving another user interface 701 to an email service. User interface 701 may be rendered by an email application executed by a suitable computing system, of which computing system 900 is representative.

[0067] In operation, an initial view in user interface 701 is rendered that includes an inbox 710 and a filter menu 720. A user may interact with the various features and functions of user interface 701 to, for example, read and compose emails and other types of messages and notifications. In addition, a user may triage their email using some of the features and functions of user interface 701.

[0068J Inbox 610 includes email 711, email 712, text message 713, email 714, email 715, email 716, and email 717. Which items are displayed in inbox 710 may depend on how it is set to be filtered. In particular, filter menu 720 allows a user to filter items based on how they have been triaged. For example, filter menu 720 includes a control 721 for viewing all emails, a control 722 for viewing those selected be read later, a control 723 for viewing those selected for a later phone call, and a control 724 for performing triage and picking follow-up actions for any of the items in inbox 710.

[0069] In this scenario, a user input 741 is initiated to select control 723, which triggers inbox 710 to be filtered to only those items for which a phone call is to be placed. Accordingly, user interface 701 is modified such that only email 712 and email 715 are displayed in inbox 710 as those two emails were triaged earlier for phone calls.

[0070] In some implementations, which filter options are rendered in filter menu

720 may be dynamically determined. For example, the ability to filter by emails subject to phone calls may be surfaced in an email application running on a smart phone, but not on some other device that lacks phone calling capability, or for which phone calls are not a main function. In another example, the ability to filter by emails triaged for text messaging may not be surfaced on a device that lacks text messaging capability. Other contextual influences on what options may be surfaced may be considered within the scope of this disclosure.

[0071] It may be appreciated that user interface 701 could be considered a subsequent user interface in that a user may triage email using a different user interface to the same email service. For example, a user may triage their email using an email application on one device and then interact with the triaged email using another email application on another device. Thus, user interface 701 may be considered a subsequent user interface because a user may have used a different user interface previously.

[0072J Figure 8 illustrates two exemplary user interfaces, including user interface

801 to a contacts service and user interface 803 to a productivity service. User interface 801 may be rendered when a contacts application is executed by a suitable computing system, of which computing system 900 is representative. User interface 803 may also be rendered when a productivity application is executed by a suitable computing system. User interface 801 and user interface 803 both illustrate various ways in which a reminder may be surface to remind a user about an email or other item that has been triaged for follow- up action.

[00731 User interface 801 includes a contacts list 810 in which various contacts 811-818 are displayed. User interface 801 also includes reminder 822 and reminder 824 that are surfaced to remind a user about a triaged item. Reminder 822 may be a graphical element that reminds a user an email and is displayed in visual association with contact 812. In some implementations, the visual association may be driven by a logical association between the triaged email and a contact, such as when a participant in the email is the contact. For example, an email from a sender may be triaged for later follow- up action. A reminder that is then rendered for the email can be displayed in visual association with the contact for the sender so that, when a user is browsing contacts list 810, he or she is reminded of the email. Reminder 824 may also be visually associated with contact 814 so as to remind a user about an email involving a person associated with contact 814. Other types of reminders and other ways in which to visually present the reminders are possible and may be considered within the scope of the present disclosure.

[0074] User interface 803 includes a productivity application menu 830 in which various features and functions of a productivity application or service may be made available. User interface 803 also includes a most recently used menu 840 and a template canvas 850. The view presented by user interface 803 may be one that is encountered by a user when initially launching a productivity application, for instance.

(0075] Most recently used menu 840 includes representations 841-845 of various documents that were used recently. Template canvas 850 includes various template documents 851-856 from which a user may select a template when creating a document. User interface 803 also includes a reminder 861 surfaced in visual proximity to a representation 842 of a document and reminder 863 surfaced in visual proximity to another representation 845 of a document.

[0076] Reminder 861 and reminder 863 may each be a graphical element that reminds a user about an email that may be associated with a document represented in most recently used menu 840. For example, an email may be triaged for later reading that includes an attachment. The attachment can be surfaced as a document in the most recently used menu 840. In another example, an email triaged for later reading may have been sent by a person that created, modified, or is somehow else related to one of the documents represented in most recently used menu 840. As such a reminder about the email can be surfaced nearby a representation of that document. Other types of reminders and other ways in which to visually present the reminders in a most recently used menu are possible and may be considered within the scope of the present disclosure. It may also be appreciated that reminders could be surfaced in a user interface to a productivity application service in other ways, such as in other menus, on template canvas 850, or elsewhere.

[0077] Figure 9 illustrates computing system 900, which is representative of any suitable computing system or collection of systems that may be employed to implement all or portions of a reminder service 910. Examples of reminder service 910 include reminder service 115 and reminder service 515.

[0078] Examples of computing system 900 include server computers, rack servers, web servers, cloud computing platforms, and data center equipment, as well as any other type of physical or virtual server machine, and any variation or combination thereof. In some implementations, a collection of multiple computing systems may be employed to implement all or portions of a collaboration service which may be hosted in one or more data centers, virtual data centers, or any other suitable computing facilities.

[0079] Computing system 900 is also representative of any suitable computing system or collection of systems that may be employed to implement all or portions of an email application 911, or any other application. Examples of email application 911 include but are not limited to email application 110, email application 510, and email application 520, as well as any other email application. Computing system 900 is also representative of any computing system suitable for implementing any of the user interfaces 111, 601, 701, 801, and 803, as well as any other user interface. Examples of computing system 900 also include, but are not limited to, desktop computers, laptop computers, tablet computers, notebook computers, mobile computing devices, smart phones, cell phones, media devices, and gaming devices, as well as any other type of physical or virtual computing machine.

[0080] Computing system 900 may be implemented as a single apparatus, system, or device or may be implemented in a distributed manner as multiple apparatuses, systems, or devices. Computing system 900 includes, but is not limited to, processing system 901, storage system 903, software 905, communication interface system 907, and user interface system 909. Processing system 901 is operatively coupled with storage system 903, communication interface system 907, and user interface system 909. User interface system 909 is optional in some implementations. Processing system 901 loads and executes software 905 from storage system 903. When executed by processing system 901, software 905 directs processing system 901 to operate as described herein for any one or more of

reminder services 1 15 and 515, as well as email applications 110, 510, and 520, and optionally as described for any of the user interfaces and operational scenarios and sequences disclosed herein. Computing system 900 may optionally include additional devices, features, or functionality not discussed for purposes of brevity.

[0081] Referring still to Figure 9, processing system 901 may comprise a microprocessor and other circuitry that retrieves and executes software 905 from storage system 903. Processing system 901 may be implemented within a single processing device but may also be distributed across multiple processing devices or sub-systems that cooperate in executing program instructions. Examples of processing system 901 include general purpose central processing units, application specific processors, and logic devices, as well as any other type of processing device, combinations, or variations thereof.

[0082] Storage system 903 may comprise any computer readable storage media readable by processing system 901 and capable of storing software 905. Storage system 903 may include volatile and nonvolatile, removable and non-removable media

implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. Examples of storage media include random access memory, read only memory, magnetic disks, optical disks, flash memory, virtual memory and non-virtual memory, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other suitable storage media. In no case is the computer readable storage media a propagated signal.

[0083] In addition to computer readable storage media, in some implementations storage system 903 may also include computer readable communication media over which software 905 may be communicated internally or externally. Storage system 903 may be implemented as a single storage device but may also be implemented across multiple storage devices or sub-systems co-located or distributed relative to each other. Storage system 903 may comprise additional elements, such as a controller, capable of

communicating with processing system 901 or possibly other systems.

[0084] Software 905 may be implemented in program instructions and among other functions may, when executed by processing system 901, direct processing system 901 to operate as described herein as described with respect to the various operational scenarios disclosed herein. In particular, the program instructions may include various components or modules that cooperate or otherwise interact to carry out the various processes and operational scenarios described herein. The various components or modules may be embodied in compiled or interpreted instructions or in some other variation or

combination of instructions. The various components or modules may be executed in a synchronous or asynchronous manner, serially or in parallel, in a single threaded environment or multi-threaded, or in accordance with any other suitable execution paradigm, variation, or combination thereof. Software 905 may include additional processes, programs, or components, such as operating system software or other application software. Software 905 may also comprise firmware or some other form of machine-readable processing instructions executable by processing system 901.

[0085] In general, software 905 may, when loaded into processing system 901 and executed, transform a suitable apparatus, system, or device (of which computing system 900 is representative) overall from a general-purpose computing system into a special- purpose computing system customized to facilitate enhanced email triage as described herein for each implementation. Indeed, encoding software 905 on storage system 903 may transform the physical structure of storage system 903. The specific transformation of the physical structure may depend on various factors in different implementations of this description. Examples of such factors may include, but are not limited, to the technology used to implement the storage media of storage system 903 and whether the computer- storage media are characterized as primary or secondary storage, as well as other factors. (0086] For example, if the computer readable storage media are implemented as semiconductor-based memory, software 905 may transform the physical state of the semiconductor memory when the program instructions are encoded therein, such as by transforming the state of transistors, capacitors, or other discrete circuit elements constituting the semiconductor memory. A similar transformation may occur with respect to magnetic or optical media. Other transformations of physical media are possible without departing from the scope of the present description, with the foregoing examples provided only to facilitate the present discussion.

[0087J Referring again to Figure 1 as an example, through the operation of a computing system or systems of which computing system 900 is representative, transformations may be performed with respect to a user interface to an email service, such as user interface 111 and user interface 121. As an example, a user may select an email for triage in user interface 111. Accordingly, a reminder is surfaced in user interface 121, thereby changing the state of user interface 121 from a first state (without the reminder) to a second, transformed state (with the reminder). Other examples of transformations are possible and may be considered within the scope of the present disclosure.

[0088J It should be understood that computing system 900 is generally intended to represent a computing system or systems on which software 905 may be deployed and executed in order to implement enhanced email triage. However, computing system 900 may also be suitable as any computing system on which software 905 may be staged and from where software 905 may be distributed, transported, downloaded, or otherwise provided to yet another computing system for deployment and execution, or yet additional distribution.

[0089] Communication interface system 907 may include communication connections and devices that allow for communication with other computing systems (not shown) over a communication network or collection of networks (not shown). Examples of connections and devices that together allow for inter-system communication may include network interface cards, antennas, power amplifiers, RF circuitry, transceivers, and other communication circuitry. The connections and devices may communicate over communication media to exchange communications with other computing systems or networks of systems, such as metal, glass, air, or any other suitable communication media. The aforementioned media, connections, and devices are well known and need not be discussed at length here.

(0090] Communication between computing system 900 and any other computing system (not shown) may occur over a communication network or networks and in accordance with various communication protocols, combinations of protocols, or variations thereof. Examples of communication networks over which computing system 900 may exchange information with other computing systems include intranets, the Internet, local area networks, wide area networks, wireless networks, wired networks, virtual networks, software defined networks, data center buses, computing backplanes, networks, or any combination or variation thereof. The aforementioned communication networks and protocols are well known and need not be discussed at length here.

However, some communication protocols that may be used include, but are not limited to, the Internet protocol (IP, IPv4, IPv6, etc.), the transfer control protocol (TCP), and the user datagram protocol (UDP), as well as any other suitable communication protocol, variation, or combination thereof. In any of the aforementioned examples in which information is exchanged, the exchange of information may occur in accordance with any of a variety of protocols, including FTP (file transfer protocol), HTTP (hypertext transfer protocol), REST (representational state transfer), WebSocket, DOM (Document Object Model), HTML (hypertext markup language), CSS (cascading style sheets), HTML5, XML (extensible markup language), JavaScript, JSON (JavaScript Object Notation), and AJAX (Asynchronous JavaScript and XML), as well as any other suitable protocol, variation, or combination thereof.

[0091] User interface system 909 may include a keyboard, a mouse, a voice input device, a touch input device for receiving a touch gesture from a user, a motion input device for detecting non-touch gestures and other motions by a user, and other comparable input devices and associated processing elements capable of receiving user input from a user. Output devices such as a display, speakers, haptic devices, and other types of output devices may also be included in user interface system 909. In some cases, the input and output devices may be combined in a single device, such as a display capable of displaying images and receiving touch gestures. The aforementioned user input and output devices are well known in the art and need not be discussed at length here.

[0092] User interface system 909 may also include associated user interface software executable by processing system 901 in support of the various user input and output devices discussed above. Separately or in conjunction with each other and other hardware and software elements, the user interface software and user interface devices may support a graphical user interface, a natural user interface, or any other type of user interface. For example, user interface 111 or user interface 121 may be presented through user interface system 909. In addition, user input made with respect to user interface 111 or user interface 121 can be input via user interface system 909.

[0093] The functional block diagrams, operational scenarios and sequences, and flow diagrams provided in the Figures are representative of exemplary systems, environments, and methodologies for performing novel aspects of the disclosure. While, for purposes of simplicity of explanation, methods included herein may be in the form of a functional diagram, operational scenario or sequence, or flow diagram, and may be described as a series of acts, it is to be understood and appreciated that the methods are not limited by the order of acts, as some acts may, in accordance therewith, occur in a different order and/or concurrently with other acts from that shown and described herein. For example, those skilled in the art will understand and appreciate that a method could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all acts illustrated in a methodology may be required for a novel implementation.

[0094] The included descriptions and figures depict specific implementations to teach those skilled in the art how to make and use the best option. For the purpose of teaching inventive principles, some conventional aspects have been simplified or omitted. Those skilled in the art will appreciate variations from these implementations that fall within the scope of the invention. Those skilled in the art will also appreciate that the features described above can be combined in various ways to form multiple

implementations. As a result, the invention is not limited to the specific implementations described above, but only by the claims and their equivalents.