Action assignment tracking using natural language processing in electronic communication applications

Systems and methods are disclosed for meeting completion. In one implementation, a message generated in relation to a meeting is received. The message is processed to identify a first action item and a first user associated with the first action item. The first action item is assigned to the first user. Performance of the first action item by the first user is tracked. The performance of the first action item by the first user is presented within an action tracking interface.

TECHNICAL FIELD

Aspects and implementations of the present disclosure relate to data processing and, more specifically, but without limitation, to meeting completion.

BACKGROUND

Electronic calendar applications enable users to schedule events and manage schedules. Using a calendar application, one user can schedule an event and invite other user(s) to participate in the scheduled event. The invited user(s) can be provided with information reflecting the details of the event (e.g., time, date, location, etc.).

SUMMARY

The following presents a shortened summary of various aspects of this disclosure in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements nor delineate the scope of such aspects. Its purpose is to present some concepts of this disclosure in a compact form as a prelude to the more detailed description that is presented later.

In one aspect of the present disclosure, Systems and methods are disclosed for meeting completion. In one implementation, a message generated in relation to a meeting is received. The message is processed to identify a first action item and a first user associated with the first action item. The first action item is assigned to the first user. Performance of the first action item by the first user is tracked. The performance of the first action item by the first user is presented within an action tracking interface.

DETAILED DESCRIPTION

Aspects and implementations of the present disclosure are directed to meeting completion.

It can be appreciated that electronic calendar applications (and other collaboration tools, such as a suite of applications that includes a calendar application) can enable users to schedule a meeting and invite other user(s) to participate in the meeting. While such tools are effective with respect to scheduling, many shortcomings and inefficiencies remain with respect to the manner in which such user(s) follow-up on commitments, resolutions, agreements, etc., discussed during a meeting. For example, in certain scenarios one user can volunteer or be appointed as the user responsible for following up on the outcome(s) of a meeting. Such a responsible user may compose an email (or other such communication) to the meeting participants, outlining various action items discussed during the meeting. However, once such a follow-up email is sent, existing calendar applications/collaboration tools do not enable users to effectively follow up on the results of such action items (e.g., whether or not such items are actually completed). As a result, completion of many action items may be delayed (or such items can remain permanently incomplete).

Accordingly, described herein in various implementations are technologies, including methods, machine readable mediums, and systems, that enable meeting completion. The described technologies can process various follow-up message(s) (e.g., email(s) composed in response to a meeting) in order to identify action item(s) and user(s) referenced therein. Each identified action item(s) can be assigned to a user(s) that is responsible for its completion. Performance of an action item by a user can then be tracked and various notifications, reminders, etc., can be provided to facilitate completion of outstanding action item(s). An action tracking interface can also be provided, e.g., to a user that is responsible for following up on the meeting. Such an action tracking interface can provide the user with an overview of the status of action item(s) relating to various meetings, as well as detailed information relating to specific users and action items. In doing so, the described technologies can automate and enhance numerous aspects of the manner in which meetings are followed up on and action items (arising from such meetings) are completed.

It can therefore be appreciated that the described technologies are directed to and address specific technical challenges and longstanding deficiencies in multiple technical areas, including but not limited to collaboration tools, communication technologies, and tracking interfaces. As described in detail herein, the disclosed technologies provide specific, technical solutions to the referenced technical challenges and unmet needs in the referenced technical fields and provide numerous advantages and improvements upon conventional approaches. Additionally, in various implementations one or more of the hardware elements, components, etc., referenced herein operate to enable, improve, and/or enhance the described technologies, such as in a manner described herein.

FIG. 1illustrates an example system100, in accordance with some implementations. As shown, the system100includes various devices such as device110A and device110B (collectively device(s)110). Each device110which can be a laptop computer, a desktop computer, a terminal, a mobile phone, a tablet computer, a smart watch, a personal digital assistant (PDA), a digital music player, a server, and the like. User130A and User130B (collectively user(s)130) can each be a human user who interacts with a device110(e.g., device110A and device110B, respectively). For example, user130can provide various inputs (e.g., via an input device/interface such as a keyboard, mouse, touchscreen, etc.) to device110. Device110can also display, project, and/or otherwise provide content to user130(e.g., via output components such as a screen, speaker, etc.).

As shown inFIG. 1, device110A can include collaboration application116. Collaboration application116can be an application, module, suite of applications, etc., that configures/enables the device to generate, transmit, receive and/or present communications (e.g., email or other electronic messages). Additionally, in certain implementations collaboration application116can include a calendar or other such time/schedule management application, such as an application that enables a user to schedule and/or manage meetings between multiple parties. In certain implementations, collaboration application116can include yet additional functionality, such as an application to track and manage the performance of action items.

As shown inFIG. 1, device110A can also include additional applications, programs, modules, etc., such as meeting completion engine118. Meeting completion engine can be an application stored in memory of device110A (e.g. memory730as depicted inFIG. 7and described below). One or more processor(s) of device110A (e.g., processors710as depicted inFIG. 7and described below) can execute the application. In doing so, device110A can be configured to perform various operations, present content to user130A, etc., as described herein. In certain implementations, meeting completion engine118can be a plug-in and/or a standalone application that operates together/in conjunction with collaboration engine116. As described herein, meeting completion engine118can configure device110A to process various message(s) (e.g., email messages generated with respect to a meeting) and track the performance of various related action items.

It should also be noted that while various components (e.g., meeting completion engine118) are depicted and/or described as operating on a device110A, this is only for the sake of clarity. However, in other implementations the referenced components (e.g., meeting completion engine118) can also be implemented on other devices/machines. For example, in lieu of executing locally at device110A, meeting completion engine118can be implemented remotely (e.g., on a server device or within a cloud service or framework), as described herein. By way of illustration, meeting completion118can also execute on server140(as shown inFIG. 1), and the various operations described herein can be performed/implemented at the server.

As also shown inFIG. 1, devices110can connect to and/or otherwise communicate with server140via network120. Network120can include one or more networks such as the Internet, a wide area network (WAN), a local area network (LAN), a virtual private network (VPN), an intranet, and the like.

Server140can be, for example, a server computer, computing device, storage service (e.g., a ‘cloud’ service), etc., and can include meeting completion engine118, log144, and content repository160. As described in greater detail below, log144can be, for example, a database or repository that stores various information, including but not limited to records pertaining to the manner in which a user completes an action item. Content repository160can be, for example, a database or repository that stores various content items (documents, files, etc.) such as content item150A and content item150B (collectively, content items150). Such content item(s)150can be associated with various users, action items, meetings, etc. (as reflected, for example, in metadata stored with the content item), as described herein.

FIG. 2depicts an example user interface210of collaboration application116, such as may be presented to user130A at device110A. As shown inFIG. 2, interface210presents a calendar application within which information pertaining to various meetings such as meeting220A (‘Sales Meeting’) and meeting220A (‘Marketing Meeting’) (collectively, meeting(s)220) is presented. Such meetings220can be entrie(s) within the calendar application that reflect scheduling information, location information, participant information, and/or other information related to an event, meeting, etc. For example, meeting220A (‘Sales Meeting’) is scheduled for Wednesday, January 3rdand includes various users such as user230A (‘User1’), user230B (‘User2’), etc. that are invited to or otherwise associated with the meeting.

As also shown inFIG. 2, collaboration application116can enable user130A to initiate various operations with respect to a meeting220. For example, user130A can select (e.g., via touch screen interaction, mouse click such as a ‘right click’ operation, etc.) meeting220A. In response to such a selection, collaboration application116can present a menu such as context menu202to the user130A. Such a menu202can include an option204(‘Reply All’) that causes a message (e.g., an email) to be generated with respect/in relation to meeting220A. In certain implementations, upon selecting such an option204(e.g., by hovering pointer206over the region associated with option204and clicking or otherwise selecting such an option), an email (originating from user130A and directed to the various other users associated with meeting220A) can be generated. An example of such an email is depicted inFIG. 3A.

FIG. 3Adepicts an example user interface310A of collaboration application116, such as may be presented to user130A at device110A. For example, in response to a selection of option204(‘Reply All’) as shown inFIG. 2, collaboration application116can launch or present interface310A. Doing so can enable the user to compose a message associated with the selected meeting (here, meeting220A). By way of illustration, after participating in a meeting one of the participants can initiate subsequent communication(s) with other participant(s) (and/or other related parties), e.g., to ensure that action items and other tasks discussed during the meeting are completed.

For example, in the scenario depicted inFIG. 3A, ‘User2’ has selected option204(‘Reply All,’ as shown inFIG. 2) with respect to meeting220A (‘Sales Meeting’). As shown inFIG. 3A, interface310A can then be presented to User2 (e.g., by collaboration application116). Such an interface310A can be a ‘compose email’ interface which can be populated with information from the corresponding meeting220A. As shown inFIG. 3A, the email (being composed by User2) can be directed (in the ‘To:’ field) to the other participants in the meeting220A (here, User1 and User3) and can be associated (e.g., in the ‘Subject:’ field) with the title, name, etc., of the meeting. Within such an interface310A, User2 can, for example, compose a message directed to the meeting participants. Such a message can, for example, summarize the outcome of the meeting, next steps to be taken, follow up items, etc., such as message320A as shown inFIG. 3A.

Having composed message320A (as shown inFIG. 3A), a user (e.g., User2 in the above example) can initiate or activate meeting completion engine118. For example, in certain implementations meeting completion engine118can be initiated in response to a user selection of a selectable control (e.g., a button, etc.) that can be integrated within an interface of collaboration application116(e.g., button308as shown inFIG. 3B). Meeting completion engine118can then process various aspects of message320A and initiate various additional operations, as described herein.

In certain implementations, meeting completion engine118can utilize natural language processing (NLP) and/or other such content processing techniques to process messages, content, etc., as described herein. Additionally, as shown inFIG. 3B, upon selection of button308, an identifier380corresponding to meeting completion engine118(e.g., an email address, such as ‘MeetingAssistant,’ as shown) can be inserted into interface310B (e.g., into the ‘CC:’ field). Such an identifier can enable subsequent communications (e.g., replies from various users that contain status updates) to be directed to and/or received (and processed) by meeting completion engine118.

As shown inFIG. 3A, meeting completion engine118can process message320A (“As discussed during today's sales meeting . . . ”) to identify various user(s) that are mentioned and/or referenced within the message. By way of illustration, message320A can be processed to identify user330A (‘User1’), user330B (‘User2’), etc., mentioned within the message. Additionally, in certain implementations message320A can be processed to identify various action item(s) that are mentioned and/or referenced within the message. Such action items can be, for example, tasks or other such items that are to be performed or completed. By way of illustration, message320A can be processed to identify action item340A (‘update the sales report’), action item340B (‘prepare a new spreadsheet’), etc., mentioned within the message.

The various elements referenced herein (e.g., users and action items) should be understood to be provided merely by way of example. Accordingly, meeting completion engine118can also identify various additional elements within a message. For example, meeting completion engine118can further identify due dates mentioned within a message (e.g., with respect to a particular action item).

Additionally, in certain implementations meeting completion engine118can identify various associations between identified elements. For example, in addition to identifying various user(s) and action item(s) within a message, meeting completion engine118can further identify an association between a user and an action item. By way of illustration, as shown inFIG. 3B, meeting completion engine118can identify (e.g., using NLP) an association between user330A (‘User1’) and action item340A (‘update the sales report’). In doing so, the referenced action item can be assigned to the user to which it is associated, and meeting completion engine118can further track performance of the action item by the associated user, as described herein.

As also shown inFIG. 3B, meeting completion engine118can generate and/or insert various supplemental content (e.g., into the email being composed). For example, meeting completion engine118can generate supplemental content322(‘ACTION ITEMS . . . ’) which can reflect or include a summary or list of the various identified users and the respective action item(s) assigned to each one. Such supplemental content322can be inserted into the referenced email being composed (e.g., after/below message320A). Various subsequent follow-up notifications, etc., can update this summary/list to reflect the status of various action items, as described herein.

Moreover, in certain implementations meeting completion engine118can identify various content items (e.g., documents, links, etc.) that are related to/associated with an action item. For example, meeting completion engine118can identify (e.g., using NLP) various documents that are referenced within message320A in relation to an action item. Such content items (and/or links to the content item(s)) can then be incorporated (e.g., attached or inserted) into the email being composed. By way of illustration, meeting completion engine118can identify that action item340A (‘update . . . ’) references content item350A (‘SalesReport.doc’) and action item340B (‘prepare . . . ’) references content item350B (‘Spreadsheet (template).xls’). Such identified content items can be incorporated (e.g., attached/linked) into the email being composed, as shown inFIG. 3B.

In certain implementations, the referenced content item(s) can be identified within and/or retrieved/received from content repository160(as shown inFIG. 1). Content repository160can be, for example, a database or repository (e.g., on server140) that stores various content items such as content item150A and content item150B (collectively, content items150). Such content items150can include documents, files, etc. Content repository can also store additional information such as metadata associated with a content item (or such metadata can be included or incorporated within the content item itself). Such metadata can reflect, for example, various associations or relationships between a content item and various other elements (e.g., users, action items, meetings, etc.). By way of illustration, metadata associated with a particular document can reflect a user that composed/created the document, a user that recently accessed the document, etc. Accordingly, meeting completion engine118can utilize such metadata/information in identifying content item(s) related to/associated with an action item. For example, in the scenario depicted inFIG. 3B, a content item entitled ‘SalesReport.doc’ that is associated (as determined based on corresponding metadata) with ‘User1’ (and/or another participant in the meeting, e.g., ‘User2’) can be determined to be likely to be relevant to the identified action item. In contrast, another document within content repository160(e.g., ‘MonthlySalesReport.doc’) that is not otherwise associated with any meeting participants, etc., can be determined to be relatively less likely to be relevant to the action item/meeting.

In various implementations, meeting completion engine118can also identify, retrieve, and/or receive the referenced content item(s) from various services such as service128A and service128B (collectively services128), as shown inFIG. 1. Such services can be, for example, third-party services that enable the retrieval of content (e.g., business names, addresses, phone numbers, documents, files, etc.) that may enhance or otherwise be relevant to certain operations described herein. In certain implementations meeting completion engine118can transmit and/or receive content, instructions, etc. to/from such services via an application programming interface (API).

After the message/email (e.g., as depicted inFIG. 3B) is sent (e.g., to the participants in a meeting), meeting completion engine118can track the performance of the various action items by the respective users. As noted above, in certain implementations users can compose and send reply emails (e.g., containing the word ‘completed’) to an email address associated with meeting completion engine118. Meeting completion engine118can then process/parse such email(s) and maintain an updated status of the performance of each action item. Additionally, in certain implementations meeting completion engine118can generate, transmit, and/or otherwise provide various notification(s). Such notifications can update the user(s) with respect to the status of various action item(s) and/or facilitate the completion of such action item(s).

By way of illustration,FIG. 4Adepicts an example email notification410A that can be generated and/or provided by meeting completion engine118to track the performance of various action items. As shown inFIG. 4A, email410A can include message420A which reflects the status of the various action items (e.g., as updated with respect to summary/list in supplemental content322as shown inFIG. 3B).

By way of further illustration,FIG. 4Bdepicts an example email notification410B that can be generated and/or provided by meeting completion engine118to track the performance of various action items. As shown inFIG. 4B, email410B can include message420B which includes content that can enable the user to complete an assigned action item (e.g., ‘Click below . . . , ’ together with a content item450A associated with the action item).

In certain implementations, various aspect of the manner in which a user completes an assigned action item (and/or otherwise responds to various notification(s)) can be stored in a log (e.g., log144as depicted inFIG. 1). Log144can be, for example, a database or repository that stores various information, including but not limited to records pertaining to the manner in which a user completes an action item (e.g., the amount of time that elapses until such action item is completed) and/or responds to various notification(s). In doing so, meeting completion engine118can identify (e.g., using various machine-learning techniques) various operations, preferences, etc. of a particular user, and subsequently utilize such determinations with respect to subsequent action item(s).

For example, in one scenario meeting completion engine118can initially transmit/provide a notification to user as depicted inFIG. 4A(e.g., including a request to complete an assigned action item and a status update showing that other users have completed their action items). Upon determining that the user has still not completed the assigned action item (e.g., after 48 hours), another notification as depicted inFIG. 4B(e.g., including an attachment/link enabling the user to directly complete the action item) can be provided to the user. Upon determining that the user completed the action item after the second notification (as reflected in the records of log144), subsequent notification(s) generated/provided by meeting completion engine118to the referenced user can reflect the format of the notification as depicted inFIG. 4B. In doing so, meeting completion engine118can utilize the tendencies, etc., of a particular user to provide notification(s) in a manner that are most effective in enabling the user to complete assigned action item(s).

The email notifications shown inFIGS. 4A and 4Bare provided herein only by way of example. Accordingly, various other types of notifications can also be employed. For example, the described notifications can be implemented as push notifications, pop-up notifications, other types of reminders, etc.

FIG. 5depicts an action tracking interface510within which meeting completion engine118can present/display the status associated with various action items and other related information. In certain implementations, action tracking interface510can be accessed by a user (e.g., ‘User2,’ who is the user that initiated the meeting follow up email in the example above) via a selectable control (e.g., button270as shown inFIG. 2).

As shown inFIG. 5, action tracking interface510can include various sections or regions such as region512A and region512B. Region512A can include information pertaining to various meetings a user is responsible for (e.g., meeting520A and meeting520B, as shown). For example, an entry for a particular meeting (e.g., meeting520A) can reflect the status514of the completion of the various action items associated with such a meeting. By way of illustration, as shown inFIG. 5, the status of meeting520A (‘Sales Meeting’) reflects that two out of three action items have been completed. Various other status information can also be provided.

Upon selecting a particular meeting from within region512A (e.g., by clicking on meeting520A using pointer506), meeting completion engine118can present additional details and information within region512B of action tracking interface510. As shown inFIG. 5, region512B can depict a detailed breakdown for each user that is a participant in the selected meeting (e.g., ‘User1,’ ‘User2,’ etc.).

For example, with respect to ‘User1,’ region512B of action tracking interface510can depict various action items assigned to the user, as well as their respective completion status. As shown with respect to ‘User1,’ action item540A (‘Update . . . ’) associated with the selected meeting (meeting520A—‘Sales Meeting’) is displayed, as well as action item540B (‘Draft . . . ’) associated with another meeting (meeting520B—‘Marketing Meeting’). By presenting action items that originate from multiple meetings, the viewer (here, ‘User2,’ who initiated the follow up for ‘Sales Meeting’) can account for additional action items assigned to User1 (e.g., with respect to other meetings), e.g., in assessing the capabilities, etc., of the user to complete a particular action item. Corresponding content items (e.g., content item550A) can also be incorporated within action tracking interface510, as shown. Additionally, various icons and/or selectable controls can depict the status of each action item. For example, icon/control524A (which reflects a ‘selected’ state) can depict that a particular action item has been completed, while icon/control524B can depict that a particular action item has not been completed. Such icons/controls can be selected (e.g., clicked on, etc.) within action tracking interface510to change the status of the corresponding action item.

While various examples described herein are illustrated with respect to a single device (e.g., device110A) and/or server (e.g., server140), this is simply for the sake of clarity and brevity. However, it should be understood that the described technologies can also be implemented (in any number of configurations) across multiple devices, servers, services, etc.

Further aspects and features of device110and server140are described herein in conjunction withFIGS. 2-7.

As used herein, the term “configured” encompasses its plain and ordinary meaning. In one example, a machine is configured to carry out a method by having software code for that method stored in a memory that is accessible to the processor(s) of the machine. The processor(s) access the memory to implement the method. In another example, the instructions for carrying out the method are hard-wired into the processor(s). In yet another example, a portion of the instructions are hard-wired, and a portion of the instructions are stored as software code in the memory.

FIG. 6is a flow chart illustrating a method600, according to an example embodiment, for meeting completion. The method is performed by processing logic that can comprise hardware (circuitry, dedicated logic, etc.), software (such as is run on a computing device such as those described herein), or a combination of both. In one implementation, the method600is performed by one or more elements depicted and/or described in relation toFIG. 1(including but not limited to meeting completion engine118, e.g., as executing on device11A and/or server140), while in some other implementations, the one or more blocks ofFIG. 6can be performed by another machine or machines.

At operation610, a message is received. In certain implementations, such a message (e.g., an email) can be composed or generated in relation to a meeting. Such a meeting can include or otherwise reflect or correspond to a scheduling entry within a calendar application. For example,FIG. 2depicts an example meeting220A (‘Sales Meeting’). In response to the selection of the ‘Reply All’ option204with respect to meeting220A, a user can begin to compose/generate message320A as shown inFIG. 3A. Upon selecting button308(‘Meeting Assistant’), such a message320A can be provided to/received by meeting completion engine118.

In certain implementations, various aspects of operation610(as well as the other operations described with respect toFIG. 6and/or described herein) are performed by device110A (e.g., in conjunction with meeting completion engine118). In other implementations, various aspects of operation610(as well as the other operations described with respect toFIG. 6and/or described herein) are performed by server140(e.g., in conjunction with meeting completion engine118). In yet other implementations, such aspects can be performed by one or more other elements/components, such as those described herein.

At operation620, the message (e.g., as received at operation610) is processed. In doing so, an action item and/or a user (e.g., a user associated with the action item) can be identified. In certain implementations, the message can be processed using NLP and/or other such techniques to identify the action item(s), user(s), etc. mentioned/referenced within the message. For example, as shown inFIG. 3B, meeting completion engine118can process message320A (“As discussed during today's sales meeting . . . ”) to identify various user(s) and/or action item(s) that are mentioned and/or referenced within the message.

At operation630, an action item (e.g., as identified at operation620) is assigned to a user. For example, associations can be identified between user(s) and action item(s) that are identified within the message. For example, as shown inFIG. 3B, user330A (‘User1’) can be identified as being associated with action item340A (‘update the sales report’).

Additionally, in certain implementations supplemental content is inserted (e.g., by meeting completion engine118as executing on device110A) into a message. In other implementations, such supplemental content can be provided (e.g., by meeting completion engine118as executing on server140). The referenced supplemental content can correspond to or reflect to the assigning of certain action item(s) to certain user(s). For example,FIG. 3Bdepicts supplemental content322(‘ACTION ITEMS . . . ’) which can reflect or include a summary or list of various identified users and respective action item(s) assigned to each one. Such supplemental content322can be inserted an email being composed with respect to the corresponding meeting, as shown.

At operation640, a content item is identified. In certain implementations, such a content item can be identified as being related to one or more action item(s) (such as those identified at operation620). Such content item can be, for example, a file, document, link, etc. In certain implementations the content item can be identified as being related to a particular action item based on an association between the content item and a particular user (e.g., the user assigned to the corresponding action item). In other implementations the content item can be identified as being related to a particular action item based on an association between the content item and another user (e.g., another participant in the meeting from which the referenced action item originated). For example, as illustrated above, a content item associated with one participant in a meeting can be determined to be likely to be relevant to an action item assigned to another participant in the same meeting.

At operation650, the content item (e.g., as identified at640) is incorporated. In certain implementations, such a content item can be incorporated (e.g., attached, linked to, etc.) within the message (e.g., the message received at operation610). For example, as shown inFIG. 3B, various content items350A,350B, etc., can be incorporated/attached within the message. It should be noted that whileFIG. 3Bdepicts multiple content items350A,350B, etc. attached, in certain implementations only those content items that are relevant to a particular user can be incorporated/provided in an email directed to such user.

At operation660, performance of an action item (e.g., as identified at operation620) is tracked. In certain implementations, various updates regarding the performance of the action item can be received. Such updates can be received via messages, replies, etc., received from various users via an identifier/email address associated with meeting completion engine118(e.g., identifier380—‘MeetingAssitant’—as shown inFIG. 3B). In other implementations such updates can be received via inputs provided by such user(s) via an action tracking interface, such as interface510as depicted inFIG. 5. For example, a user can select a button (e.g., button524A) that corresponds to an action item in order to update the status of such an action item (e.g., to ‘completed’).

The referenced updates, status of action items, etc., can be provided as notification(s) to various user(s) (e.g., the user responsible for a particular action item, the user that initiated the email in response to the meeting, etc.).FIGS. 4A and 4Bdepict various types of notifications that can be generated, provided, presented, etc. to such user(s), as described in detail above.

At operation670, performance of various action item(s) (e.g., as tracked at operation660) can be providing and/or presented. In certain implementations, such performance can be provided to and/or presented within an action tracking interface. Such an action tracking interface (e.g., interface510as shown inFIG. 5) can be, for example, an interface that depicts various meetings and information pertaining to the status of action item(s) associated with such meetings.

At operation680, another action item is identified. Such an action item can be another action item (e.g., associated with a second meeting) assigned to a particular user (e.g., a user that was also a participant in a first meeting). For example, as shown inFIG. 5, User1 who is associated with action item540A (‘Update . . . ’) which originated from ‘Sales Meeting’ can also be associated with another action item540B (‘Draft . . . ’) that originated from ‘Marketing Meeting.’

At operation690, performance of the second action item (e.g., the action item identified at operation680) is tracked. As noted above, in certain implementations the manner in which performance of such a second action item is tracked can be dictated or adjusted based on feedback, results, etc., identified with respect to the performance of a first action item by the user. For example, upon determining that a particular user previously completed an action item in response to a particular type of notification, subsequent notification(s) generated/provided by meeting completion engine118to such user can reflect the format of the notification to which the user was responsive to. In doing so, meeting completion engine118can utilize the tendencies, etc., of a particular user to provide notification(s) in a manner that are most effective in enabling the user to complete assigned action item(s).

It should also be noted that while the technologies described herein are illustrated primarily with respect to meeting completion, the described technologies can also be implemented in any number of additional or alternative settings or contexts and towards any number of additional objectives. It should be understood that further technical advantages, solutions, and/or improvements (beyond those described and/or referenced herein) can be enabled as a result of such implementations.

Similarly, the methods described herein can be at least partially processor-implemented, with a particular processor or processors being an example of hardware. For example, at least some of the operations of a method can be performed by one or more processors or processor-implemented modules. Moreover, the one or more processors can also operate to support performance of the relevant operations in a “cloud computing” environment or as a “software as a service” (SaaS). For example, at least some of the operations can be performed by a group of computers (as examples of machines including processors), with these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., an API).

The performance of certain of the operations can be distributed among the processors, not only residing within a single machine, but deployed across a number of machines. In some example implementations, the processors or processor-implemented modules can be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other example implementations, the processors or processor-implemented modules can be distributed across a number of geographic locations.

The modules, methods, applications, and so forth described in conjunction withFIGS. 1-6are implemented in some implementations in the context of a machine and an associated software architecture. The sections below describe representative software architecture(s) and machine (e.g., hardware) architecture(s) that are suitable for use with the disclosed implementations.

FIG. 7is a block diagram illustrating components of a machine700, according to some example implementations, able to read instructions from a machine-readable medium (e.g., a machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically,FIG. 7shows a diagrammatic representation of the machine700in the example form of a computer system, within which instructions716(e.g., software, a program, an application, an applet, an app, or other executable code) for causing the machine700to perform any one or more of the methodologies discussed herein can be executed. The instructions716transform the general, non-programmed machine into a particular machine programmed to carry out the described and illustrated functions in the manner described. In alternative implementations, the machine700operates as a standalone device or can be coupled (e.g., networked) to other machines. In a networked deployment, the machine700can operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine700can comprise, but not be limited to, a server computer, a client computer, PC, a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular telephone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of executing the instructions716, sequentially or otherwise, that specify actions to be taken by the machine700. Further, while only a single machine700is illustrated, the term “machine” shall also be taken to include a collection of machines700that individually or jointly execute the instructions716to perform any one or more of the methodologies discussed herein.

The machine700can include processors710, memory/storage730, and I/O components750, which can be configured to communicate with each other such as via a bus702. In an example implementation, the processors710(e.g., a Central Processing Unit (CPU), a Reduced Instruction Set Computing (RISC) processor, a Complex Instruction Set Computing (CISC) processor, a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP), an ASIC, a Radio-Frequency Integrated Circuit (RFIC), another processor, or any suitable combination thereof) can include, for example, a processor712and a processor714that can execute the instructions716. The term “processor” is intended to include multi-core processors that can comprise two or more independent processors (sometimes referred to as “cores”) that can execute instructions contemporaneously. AlthoughFIG. 7shows multiple processors710, the machine700can include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiples cores, or any combination thereof.

The memory/storage730can include a memory732, such as a main memory, or other memory storage, and a storage unit736, both accessible to the processors710such as via the bus702. The storage unit736and memory732store the instructions716embodying any one or more of the methodologies or functions described herein. The instructions716can also reside, completely or partially, within the memory732, within the storage unit736, within at least one of the processors710(e.g., within the processor's cache memory), or any suitable combination thereof, during execution thereof by the machine700. Accordingly, the memory732, the storage unit736, and the memory of the processors710are examples of machine-readable media.

In further example implementations, the I/O components750can include biometric components756, motion components758, environmental components760, or position components762, among a wide array of other components. For example, the biometric components756can include components to detect expressions (e.g., hand expressions, facial expressions, vocal expressions, body gestures, or eye tracking), measure biosignals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identify a person (e.g., voice identification, retinal identification, facial identification, fingerprint identification, or electroencephalogram based identification), and the like. The motion components758can include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope), and so forth. The environmental components760can include, for example, illumination sensor components (e.g., photometer), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., infrared sensors that detect nearby objects), gas sensors (e.g., gas detection sensors to detect concentrations of hazardous gases for safety or to measure pollutants in the atmosphere), or other components that can provide indications, measurements, or signals corresponding to a surrounding physical environment. The position components762can include location sensor components (e.g., a Global Position System (GPS) receiver component), altitude sensor components (e.g., altimeters or barometers that detect air pressure from which altitude can be derived), orientation sensor components (e.g., magnetometers), and the like.

Communication can be implemented using a wide variety of technologies. The I/O components750can include communication components764operable to couple the machine700to a network780or devices770via a coupling782and a coupling772, respectively. For example, the communication components764can include a network interface component or other suitable device to interface with the network780. In further examples, the communication components764can include wired communication components, wireless communication components, cellular communication components, Near Field Communication (NFC) components. Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components to provide communication via other modalities. The devices770can be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a USB).

The instructions716can be transmitted or received over the network780using a transmission medium via a network interface device (e.g., a network interface component included in the communication components764) and utilizing any one of a number of well-known transfer protocols (e.g., HTTP). Similarly, the instructions716can be transmitted or received using a transmission medium via the coupling772(e.g., a peer-to-peer coupling) to the devices770. The term “transmission medium” shall be taken to include any intangible medium that is capable of storing, encoding, or carrying the instructions716for execution by the machine700, and includes digital or analog communications signals or other intangible media to facilitate communication of such software.

Although an overview of the inventive subject matter has been described with reference to specific example implementations, various modifications and changes can be made to these implementations without departing from the broader scope of implementations of the present disclosure. Such implementations of the inventive subject matter can be referred to herein, individually or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single disclosure or inventive concept if more than one is, in fact, disclosed.

As used herein, the term “or” can be construed in either an inclusive or exclusive sense. Moreover, plural instances can be provided for resources, operations, or structures described herein as a single instance. Additionally, boundaries between various resources, operations, modules, engines, and data stores are somewhat arbitrary, and particular operations are illustrated in a context of specific illustrative configurations. Other allocations of functionality are envisioned and can fall within a scope of various implementations of the present disclosure. In general, structures and functionality presented as separate resources in the example configurations can be implemented as a combined structure or resource. Similarly, structures and functionality presented as a single resource can be implemented as separate resources. These and other variations, modifications, additions, and improvements fall within a scope of implementations of the present disclosure as represented by the appended claims. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.