Patent Application
20160342665
Numerous and diverse communications platforms are currently available. Some communications platforms, e.g., messaging and/or email platforms, allow for a certain amount of interoperability. However, these platforms fail to adequately address the needs and requirements of contemporary team environments. Common communication services are fairly static and limited with respect to capabilities during authoring of a communication in a team environment. Further, third-party services typically register with a communication service but have limited interaction with the communication service thereafter. It is with respect to such general technical areas that the present application is directed.
Non-limiting examples of the present disclosure describe a collaborative communication system that may interface with one or more command resources. The collaborative communication system may comprise at least one memory and at least one processor operatively connected with the memory to execute operations. In response to command input being received during authoring in a user interface of the collaborative communication system, a query is processed and passed to a command resource. The query comprises parameters of the command input and a context associated with the authoring. A response is received from the command resource based on the parameters of the command input and the context. The response may comprise result data and parameters for interacting with the collaborative communication system. The result data is presented in the user interface of the collaborative communication system.
In additional non-limiting examples, the present disclosure describes a collaborative communication system that may interface with one or more external resources. In response to command input being received during authoring in a user interface of the collaborative communication system, a request is transmitted that comprises parameters of the command input and a context associated with the authoring. A response is received from an external resource based on the parameters of the command input and the context. The response may comprise result data and parameters for interacting with the collaborative communication system. The result data is presented in the user interface of the collaborative communication system.
In other non-limiting examples, registration data of a command handler is received from an external resource for a command that is executable in a collaborative communication service. The registration data comprises parameters defining a command associated with the command handler. The registration data is stored in a storage for the collaborative communication service. Upon receiving a declaration of input in the collaborative communication service, utilizing the parameters defining the command to determine whether the input triggers the command handler. Upon determining that the input triggers the command handler, presenting the stored command handler for display in a user interface of the collaborative communication service.
Other non-limiting examples of the present disclosure describe communication between a collaborative communication service and at least one external resource. Upon command input being received during authoring in a user interface of the collaborative communication service, a first query is transmitted to the external resource. The first query comprises parameters of the command input and a context associated with the authoring. A first response is received from the external resource based on the parameters of the command input and the context. The first response may comprise result data and parameters for interacting with the collaborative communication service. The result data is presented in the user interface. Upon update to the command input a second query is transmitted to the external resource. The second query comprises parameters of the updated command input. A second response is received from the external resource based on the parameters of the command input and the context provided by the first query. In examples, the second response received comprises updated result data. The updated result data is presented in the user interface.
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This summary 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.
Non-limiting and non-exhaustive examples are described with reference to the following Figures.
In the following detailed description, references are made to the accompanying drawings that form a part hereof, and in which are shown by way of illustrations specific embodiments or examples. These aspects may be combined, other aspects may be utilized, and structural changes may be made without departing from the present disclosure. Embodiments may be practiced as methods, systems, computer-readable storage devices or devices. Accordingly, embodiments may take the form of a hardware implementation, an entirely software implementation, or an implementation combining software and hardware aspects. The following detailed description is therefore not to be taken in a limiting sense, and the scope of the present disclosure is defined by the appended claims and their equivalents.
Communication services are becoming more advanced. However, communication services are fairly static with respect to capabilities during authoring of a communication. As an example, a user might be able to quickly say or enter input such as “service, please open my calendar.” However, previous communication systems/services are unable to interact with a user to process a command such as, “/meetingtime <Person 1, Person 2, Person 3>” and have an autocomplete entry show suggestions for when to suggest a meeting between the 3 specified persons. Accordingly, common communication services do not allow a user to deeply and efficiently interact with third-party services to craft a back-and-forth interaction between third-party services and the communication services.
Non-limiting examples of the present disclosure describe communication systems/services that afford for interaction with external services that is richer than mere register and forget interactions that currently exist between communication services and external services. Examples provided comprise systems and/or services that enable rich background communication with a plurality of external resources including third-party services to facilitate multi-step queries during authoring of content. In one example, a personal assistant service may register a set of handlers, that when triggered, may prompt for dynamic interactions during authoring of content such as a message/email. For instance, a user typing a new message could type “Hi John. I suggest we meet/mynextfreetimes.” Using examples described herein, a communication service may be able to interact with a third-party service for command processing to insert content that replaces the command “/mynextfreetimes” with the times that John is free. Exemplary communication systems/services described herein may foster further communication with external services to improve a user's experience with the exemplary communication system/services. Continuing the above example, a user may enter a command requesting additional available times to meet with John and the communication system/service may continue interaction with the external service to satisfy the request of the user. In another example, the user could enter an input of, “Sandy—I really like that /Assistant ‘What were docs from last meeting?’ Essentially, such an input may be asking a personal digital assistant service for a list of the documents presented in the last meeting. The personal assistant service may respond with a rich answer, perhaps in auto complete form, allowing the user to pick the documents they wanted to reference and then continue authoring a message. Accordingly, examples described herein enable for rich authoring integration.
A number of technical advantages are achieved based on the present disclosure including but not limited to: creation of a robust and scalable communication service, improved communication/interaction between an exemplary communication service and external services, processing efficiency with regard to input processing, improved user interaction between users and an exemplary communication service, improved efficiency and usability for UI control, reduction in error rate for input processing, and miniaturization or less space required for UI functionality, among other examples.
The unified communication platform 105 is a communication system/service that provides a collaborative environment for users to communicate and collaborate. The unified communication platform 105 is illustrated by a dashed line, illustrating that implementation of the unified communication platform 105 may involve the front end 106a, middle tier 106b and/or the back end 106c of server 106, among other examples. In aspects, server computing device 106 may include one or more server computing devices 106. In an example the unified communication platform 105 presents a configurable and extensible workspace for collaboration between users through a user interface (UI) that may comprise a plurality of different views. Users of the unified communication platform 105 may be include but are not limited to: one or more persons, companies, organizations, departments, virtual teams, ad-hoc groups, vendors, customers, third-parties, etc. Users of the unified communication platform 105 may have one or more user profiles that are customizable by the user. The unified communication platform 105 enables visibility and communication between users including users who are organized in teams or groups as well as users/groups outside of a team/group. Policies may be set for teams/groups by one or more administrators of a team/group and by administrators of the unified communication platform 105. Examples described throughout the present disclosure are designed to accommodate to protect user privacy. Protection of sensitive information, including legally protected data and personally identifiable information, is a paramount consideration for implementing examples described herein. For instance, users may set privacy settings for what data that can displayed/shared, and examples described herein comply with such settings as well as laws related to distribution of data and protection of privacy.
As illustrated in
In some aspects, the backend 106c may further comprise or be in communication with one or more application agents 106d to facilitate interoperability and communication with one or more external resources 114. More specifically, application agents 106d may interface with external resources 114 using webhooks 106e in order to facilitate integration between the unified communication platform 105 and external resources/services 114. External resources 114 are any resource (e.g., system, application/service, etc.) that exists and is manageable outside of the unified communication platform 105. External resources include but are not limited to systems, application/services that may be managed by a same organization as the unified communication platform 105 (e.g., other services provided by an organization such as web search services, e-mail applications, calendars, device management services, address book services, informational services, etc.) as well as services and/or websites that are hosted or controlled by third parties. For example, external resources 114 may include line-of-business (LOB) management services, customer relationship management (CRM) services, debugging services, accounting services, payroll services, etc. External resources 114 may further include other websites and/or applications hosted by third parties, such as social media websites; photo sharing websites; video and music streaming websites; search engine websites; sports, news or entertainment websites, and the like. That is, some external resources 114 may provide robust reporting, analytics, data compilation and/or storage service, etc., whereas other external resources 114 may provide search engines or other access to data and information, images, videos, and the like.
In aspects, data or information may be shared between server computing device 106 and the one or more external resources 114. For example, business contacts, sales, etc., may be input via a client computing device 104 in communication with server computing device 106, which is in communication with CRM software that is hosted by a third party. The CRM software may track sales activity, marketing, customer interactions, etc., to provide analytics or other information for promoting business relations. Alternatively, a manufacturing order may be input via a client computing device 104 in communication with server computing device 106, which is in communication with LOB management software that is hosted by a third party. The LOB management software may guide and track the order by creating work flows such as tasks or alerts for scheduling manufacturing equipment, ordering raw materials, scheduling shipping, relieving inventory, etc. In some cases, the LOB management software may create requests for user approval or review at different stages in the work flow. In still further aspect, a user may issue a query to one or more of the external resources 114, such as a request for business contacts, sales for the prior month, the status of an order, a request for an image, etc.
As illustrated by
According to further aspects, communication between the unified communication platform 105 and other components of the system may require authentication 112. Authentication 112 refers to a process by which a device, application, component, user, etc., provides proof that it is “authentic” or “authorized” to access or communicate with another device, application, component, user, etc. Authentication may involve the use of third-party digital certificates, authentication tokens, passwords, symmetric or asymmetric key encryption schemes, shared secrets, authentication protocols, or any other suitable authentication system or method either now known or developed in the future. In aspects, upon authentication, access or communication may be allowed and data or information may be exchanged between the unified communication platform 105 and various other components of the system. In some aspects, an environment or network linking various devices, applications, components, users, etc., may be referred to as a “trusted” environment. In a trusted environment, authentication between devices, applications, components, users, etc., may be unnecessary.
The unified communication platform 105 executing operations on the server computing device 106 may further be in communication with one or more enterprise applications (e.g., enterprise stack 110). Enterprise stack 110 may include, for example, an active directory 110a, an enterprise messaging application 110b, a file sharing application 110c, a telemetry application 110d, and the like. The enterprise stack 110 may be stored and/or executed locally, e.g., within an enterprise intranet, or in distributed locations over the Internet. In some cases, enterprise stack 110 may be included within server computing device 106. For example, active directory 110a may be included as part of back end 106c of server computing device 106. In at least some instances, enterprise stack 110 may reside or communicate with the unified communication platform 105 within a trusted environment. In aspects, information and/or messages received, sent or stored via the unified communication platform 105 may be communicated to the enterprise stack 110. Moreover, information and/or messages received, sent or stored via the enterprise stack 110 may be communicated to the unified communication platform 105.
Additionally, in some aspects, the unified communication platform 105 executing on the server computing device 106 may be in communication with one or more third party messaging applications 116. Third party messaging applications 116 are messaging applications that are hosted or controlled by third parties. In aspects, some users who are members of a team may be registered with the unified communication platform 105 (e.g., internal users), whereas other users who are members of the team may not be registered with the unified communication platform 105 (e.g., external users) but may be registered with one or more third party messaging applications 116. In some aspects, users who are registered with an enterprise messing application 110b, but not with the unified communication platform 105, are considered external users. In this case, the unified communication platform 105 may communicate with one or more third party messaging applications 116 and/or with one or more enterprise messaging applications 110b to exchange information and messages with the external users. In some aspects, communication between the unified communication platform 105 and the one or more third party messaging applications 116 and/or the one or more enterprise messaging applications 110b over network 108 may involve authentication 112. In other aspects, communication between the unified communication platform 105 and, for example, the one or more enterprise messaging applications 110b, may not involve authentication 112.
As should be appreciated, the various devices, components, etc., described with respect to
In aspects, a user may interact with a unified communication platform via a user interface 200, e.g., a graphical user interface. An exemplary unified communication platform 105 is described in the description of
As detailed above, each pane or window may display information in the form of text, graphics, etc., and/or one or more interactive controls or links. For example, a first pane, e.g., left rail 202, may display one or more teams 208, an email portal, etc. As used herein, a team refers to any group of two or more users formed for a purpose. A team may be formed for any purpose, e.g., a business purpose, a social purpose, a charitable purpose, and the like. Moreover, a team may comprise any type of user, e.g., co-workers, family members, classmates, business associates, and the like. In aspects, a team may be formed within the unified communication platform 105 by creating a team title, e.g., leadership team, design team, event team, project team, etc., and adding users (e.g., members) to the team. For example, in a settings or administration pane (not shown), members may be added to the team by selecting an identifier of a user, e.g., a user icon, a user email, a user phone number, etc. In at least some aspects, each member of a team is granted access to a team portal or channel. In further aspects, any number of teams may be created within the unified communication platform 105 and/or teams may be implicitly created based on communications between two or more users.
A team portal may provide access to all communications, files, links, lists, hashtags, development tools, etc., shared by any member of a team. According to examples, upon selection (e.g., by clicking) of a team title within a pane, e.g., the left rail 202, a team portal may be opened. A team portal refers to an access point through which team members can view and interact with shared information and other team members. In at least some cases, each member of a team is granted full access to the information and conversations shared within the team portal. In aspects, upon selection of a team 208, general information regarding the team, project specifications, etc., may be displayed in a second pane, e.g., center pane 204. For example, member names, member contact information (e.g., email addresses, phone numbers, etc.), member usage time, project specifications, project time lines, project mission, and the like, may be displayed in the center pane 204.
A team portal may be further organized based on categories 210 of information for a team 208. For example, any suitable category 210 for organizing team information may be created for a team portal, e.g., finance, engineering, launch readiness, debugging, catering, construction, general, random, and the like. In aspects, information related to a category 210 may be displayed in center pane 204 upon selecting a category 210 of a team 208 within left rail 202. In some instances, each member of a team is granted full access to information associated with each category 210 of a team 208 within the team portal.
As noted above, a team portal provides access to all communications, files, links, lists, hashtags, etc., shared by members of a team 208. In aspects, within each category 210, information may further be organized by tabs or pages. For example, each tab 212 may display a different type of information associated with a category 210 in the center pane 204. When selected, a tab 212 may be identified by highlighting, with a different font or font color, by outlining, and the like. As illustrated by
In some cases, described further below, one or more communications 218 may be grouped as a conversation thread 220. A communication 218 refers to a single message transmitted by a team member in any format (e.g., email, text, SMS, instant message, etc.) via any mode (e.g., via the unified communication platform, or via any enterprise or third-party messaging application). That is, messages may be generated within the unified communication platform 105 between internal users or messages may be communicated to and from external users via enterprise messaging applications (e.g., enterprise messaging application 110b) and/or third party messaging applications (e.g., third party messaging applications 116).
As detailed above, each pane or window may display information and/or interactive controls. For example, a third pane, i.e., right rail 206, may display context information, status information, recent activity, and the like. In some aspects, information displayed in the right rail 206 may be related to or associated with the category 210 selected in the left rail 202. For instance, where the central pane 204 displays communications, files, links, lists, hashtags, etc., related to a category 210a entitled “New Product Launch,” the right rail 206 may display one or more recent files 222, recent links 224, tags 226, or active people 228. In some aspects, at least some of the information displayed in the right rail 206 may be specific to a particular user (e.g., the particular user accessing the team portal via a client computing device 104). In aspects, the particular user accessing the team portal may be identified by a name, icon, or the like, within right rail 206. For example, the particular user may be identified by user name 230a or user icon 230b. That is, for example, the recent files 222 and/or recent links 224 may have been recently accessed or uploaded by the particular user. In another example, the right rail 206 displayed for another user accessing the same category 210 may display a different set of recent files 222 or recent links 224. In further examples, additional or different information relevant to a category 210 and a particular user may be displayed in the right rail 206, e.g., user tasks, user alerts, user calendar, user notes, etc.
According to additional aspects, center pane 204 may include a search field 240. For example, search field 240 may allow a user to search within a team portal for any communication, file, link, list, hashtag, term, team member, calendar, task, event, and the like. In aspects, search field 240 may allow for plain language searching, Boolean searching (e.g., searching using Boolean operators), or otherwise. Upon entering one or more search terms into the search field 240, any information related to the search terms within the team portal may be displayed as search results to the user.
As should be appreciated, the various features and functionalities of user interface 200 described with respect to
As illustrated by
Alternatively, the unified communication platform 105 may provide a reply link 234 associated with each communication 218 of a conversation. In some aspects, reply link 234 is displayed near each communication 218 of a conversation, e.g., to the right of a sender or subject line for a communication (not shown), indented below a communication (shown), up and to the right of a communication (not shown), and the like. Alternatively, reply link 234 may not be displayed unless and until a communication 218 is clicked, hovered over, touched or otherwise identified with an input device (e.g., mouse, pointer, etc.). Upon display and selection of a reply link 234 associated with a particular communication 218, a reply message text field may be displayed (not shown). Similar to the input entry field 232, the reply message text field may allow entry of text, entry of commands, entry of hashtags, attachment of files, insertion of emoticons, etc. However, in this case, upon inputting a message and hitting enter, a communication from the user may automatically post within a conversation thread 220 associated with the particular communication 218. In aspects, as illustrated by
Alternatively still, the unified communication platform 105 may provide an email control 236 for accessing an email interface object, e.g., email interface object 238, to send “email-like” communications. In aspects, email interface object 238 may allow similar actions to input entry field 232, such as a text field 276 for entry of text, entry of commands, entry of hashtags, etc., and controls 268 for attachment of files, insertion of emoticons, etc. Additionally, email interface object 238 may provide controls 278 for altering text font and size, bulleting text, etc., and controls 270 for sending, saving a draft email, deleting, etc. Email interface object 238 may further provide a recipient field 272 for inputting or selecting recipients and a subject field 274 for inputting a subject line, and the like. Upon inputting a message into an email interface object 238 and hitting enter, a communication from the user may automatically post to the conversation as a new “email-like” message.
As should be appreciated, the various features and functionalities of user interface 200 described with respect to
As described above, each tab 212 may display a different type of information associated with a category 210a in the center pane 204. For example, as illustrated by
In some aspects, files 242 displayed in file tab 212b include files 242 that were sent as attachments to communications 218 between team members. That is, the unified communication application may extract files sent as attachments and automatically save them in file tab 212b. In other aspects, as illustrated by
According to further aspects, a third tab (e.g., link tab 212c) may display links shared between team members. In some aspects, links displayed in the link tab 212c include links that were sent as attachments to communications 218 between team members. That is, the unified communication application may extract links sent as attachments and automatically save them to the link tab 212c. In other aspects, a link upload field (not shown) may be provided. Upon selecting a link upload field, one or more links may be saved to the link tab 212c by a user. For example, upon selection of a link upload field, a browsing box (not shown) may be activated for retrieving a link for upload. Alternatively, a command may be entered (e.g., /link) for retrieving a link for upload. Alternatively still, a link may be copied and pasted into the link upload field. In aspects, any suitable method for uploading and saving a link to the link tab 212c may be implemented.
A fourth tab (e.g., list tab 212d) may display list files or other information, data, objects, images, etc., shared between team members. In aspects, list files may include lists, tables, charts, or other organized forms of data. In some aspects, list files displayed in list tab 212d include list files that were sent as attachments to communications 218 between team members. That is, the unified communication application may extract list files sent as attachments and automatically save them to list tab 212d. In other aspects, a list may be created or uploaded by a user within list tab 212d. For example, a list creation control (not shown) may be provided for creating a list file. Upon selecting the list creation control, a list file may be created and saved to the list tab 212d by a user. Alternatively, a list upload field (not shown) may be provided. Upon selecting a list upload field, one or more list files may be saved to the list tab 212d by a user, as described similarly above. In at least some cases, a single copy of each list file may exist such that if data is updated in any view, e.g., within the communications tab 212a or the list tab 212d, the list file is automatically updated and synchronized across all other views.
According to aspects, any number of tabs 212 may be created for organizing and sequestering various information related to a category 210a. For example, a hashtag tab may be added to store various hashtags created within communications between team members. In additional examples, custom or extensibility tabs may be created, e.g., a tab for a spreadsheet dashboard, a tab for a webpage, a tab for a custom application, a tab for a system plugin, and the like. In further aspects, additional interactive controls or links (e.g., controls 246) may be provided in left rail 202 for accessing communications, files, lists, links, tags, etc., related to a team 208. For example, control 246a may access team members and/or conversations stored in the team portal, control 246b may access files stored in the team portal, control 246c may access lists stored in the team portal, control 246d may access links stored in the team portal, and control 246e may access hashtags stored in the team portal. In some aspects, selection of a control 246 may display a corresponding tab view within the center pane 204.
As illustrated by
As should be appreciated, the various features and functionalities of user interface 200 described with respect to
In further aspects, the left rail 202 may further include an email portal 214. Unlike a team portal, email portal 214 may be an access point through which a particular user can view and interact with his or her email messages. In aspects, upon selection of email portal 214, a second pane, e.g., center pane 204, may display a user's email messages. Center pane 204 may further display a user identifier 248 as a header, e.g., a user email address, a user name, a user icon, and the like. Center pane 204 may provide one or more tabs 250 for organizing the user's email messages. Tabs 250 may include, for instance, an inbox tab 250a, a file tab 250b, a link tab 250c, a sent tab 250d, a drafts tab 250e, a deleted tab 250f, and the like. For example, a user's inbox of messages may be displayed in the center pane 204 at inbox tab 250a. In further aspects, the user's inbox of messages may include all messages sent to the user, e.g., messages between team members, including internal and external users, as well as messages between entities and users that are not team members.
In some aspects, the user's email messages 280 in inbox tab 250a may be displayed in a summary list format (shown) in descending order based on a date the email message was received with the most recent email message displayed at the top of center pane 204. The summary list format may display a portion of each email message, e.g., a sender, a subject line, and a portion of text for each email message.
In alternative aspects, the user's email messages in inbox tab 250a may be displayed in a conversation thread format (not shown). A conversation thread format may display email messages which are replies to a primary email message as indented, bulleted, or otherwise offset below a primary email message. In at least some aspects, each conversation thread may be displayed in descending order based on a date the last email message in the conversation thread was received with the most recent conversation thread displayed at the top of center pane 204. In this case, individual communications (i.e., communications that have not been replied to) may be interspersed among conversation threads in descending order based on a date the individual communication was received. In other aspects, each conversation thread may be displayed in ascending order based on a date the last email message in the conversation thread was received with the most recent conversation thread displayed at the bottom of center pane 204. In this case, individual communications may be interspersed among conversation threads in ascending order based on a date the individual communication was received.
In further aspects, email messages that have been opened or viewed may be displayed within the in inbox tab 250a of center pane 204 with normal text, whereas email messages that have not been opened or viewed may be displayed within the center pane 204 with at least portions of the email message in bold text (e.g., a sender and/or a subject line may be displayed with bold text).
As should be appreciated, the various features and functionalities of user interface w200 described with respect to
As described above, upon selection of email portal 214, center pane 204 may display a user's email messages. In some aspects, as illustrated by
In aspects, by selecting a conversation 252 displayed in the left rail 202, communications between the one or more users may be displayed in center pane 204. As illustrated in
In aspects, communications 254 of conversation 252c may be displayed in descending order based on a date each communication 254 was received with the most recent communication 254 displayed at the top of center pane 204. In other aspects, communications 254 of conversation 252c may be displayed in ascending order based on a date each communication 254 was received with the most recent communication 254 displayed at the bottom of center pane 204.
In further aspects, information related to conversation 252c may be organized by tabs or pages. For example, each tab 258 may display a different type of information associated with conversation 252c in the center pane 204. When selected, a tab 258 may be identified by highlighting, with a different font or font color, by outlining, and the like. As illustrated by
As illustrated by
As should be appreciated, the various features and functionalities of user interface 200 described with respect to
In aspects, a version of the unified communication platform may provide a user interface 285 for mobile devices. The mobile user interface 285 may provide one or more panes or windows for viewing communications, files, lists, links, etc., associated with one or more teams of which a user is a member. In some aspects, a second pane may be displayed (e.g., second pane 288) upon swiping a first pane (e.g., first pane 286) in a left-to-right direction or a right-to-left direction. One skilled in the art will recognize that actions associated with changing panes (e.g. first pane 286 and second pane 288) are not limited to swiping and may be any input action that is understood by the unified communication platform.
As illustrated, first pane 286 displays one or more teams (e.g., team 287) and one or more categories (e.g., categories 291). In aspects, a notification (e.g., notification 292) may be displayed near a category (e.g., category 291a) when a new communication, file, list, hyperlink, etc., has been received within the category 291. As further illustrated, second pane 288 displays one or more communications 289 (e.g., communications 289a and 289b), which are each associated with a sender (e.g., senders 290a and 290b).
As should be appreciated, the various features and functionalities of user interface 285 described with respect to
As described above, mobile user interface 285 may allow a user to view a conversation (e.g., conversation 293) in a conversation pane (e.g., conversation pane 294). The mobile user interface 285 may further provide a new message input field 295 and an input interface 296 for inputting and sending communications to participants of the conversation 293. In aspects, when a communication is sent to the participants of an ongoing conversation (e.g., conversation 293), new message input field 295 does not require recipient information but may provide a subject input field, e.g., subject input field 297, for inputting a subject of the communication, e.g., “New UX.” In some aspects, new message input field 295 may be similar to an instant, chat, SMS, or similar communication interface. In other aspects, new message input field 295 may provide functionality similar to an email communication interface (e.g., allowing for attaching documents, list objects, images, etc.). As illustrated, a communication 298 has been partially input into new message input field 295.
As should be appreciated, the various features and functionalities of user interface 285 described with respect to
One of skill in the art will appreciate that the scale of systems such as system 300 may vary and may include more or fewer components than those described in
System 300 comprises a processing device 302, a network connection 304, command processing components 306 and storage(s) 314. The command processing components 306 may comprise one or more additional components such as user interface component 308, command line component 310 and command handler component 312. As an example the command processing components 306 including sub-components 308-312, may be included in the server computing device 106 of
Processing device 302 may be any device comprising at least one processor and at least one memory/storage. Examples of processing device 302 may include but are not limited to: mobile devices such as phones, tablets, phablets, slates, laptops, watches, computing devices including desktop computers, servers, etc. In one example processing device 302 may be a device of a user that is running an application/service associated with the collaborative communication system. For instance, processing device 302 may be a client device that interfaces with other components of system 300 such as server computing device 106 that may comprise command processing components 306. In examples, processing device 302 may communicate with command processing components 306 via a network 304. In one aspect, network 304 is a distributed computing network, such as the Internet.
The command processing components 306 are a collection of components that are used for command line processing to enable command input to be entered and processed during an interaction with a user of a collaborative communication system/service. Command processing components 306 comprise the user interface component 308. The user interface component 308 is one or more components that are configured to enable interaction with a user of the collaborative communication system/service. Transparency and organization are brought to users of the collaborative communication system/service through the user interface component 308 where a configurable and extensible workspace for collaboration is provided with a plurality of different views, features and customizable options. Examples of the user interface component 308 are shown in
The command line component 310 is a component of the command processing components 306 that interfaces with the user interface 308 and the command handler component 312 to enable command processing in a collaborative communication system/service. In one example, the command processing component 310 is implemented upon the middle tier 106b of the server computing device 106 and communicates with the front end 106a and backend 106c of the server computing device 106 to facilitate command processing. However, one skilled in the art will recognize that any processing device can be configured to perform specific operations of the command processing component 310. The command processing component 310 may exchange commands and information with the user interface component 308 may also exchange the commands and information with one or more components of the server computing device 106. In one example, the user interface component 308 may present an input entry field such as the input entry field 232 shown in at least
The command handler component 312 is a component of the command processing components 306 that interfaces with the user interface 308 and the command line component 310 to enable command processing in a collaborative communication system/service. In one example, the command handler component 312 is implemented upon the middle tier 106b of the server computing device 106 and communicates with the front end 106a and backend 106c of the server computing device 106 to facilitate command processing. However, one skilled in the art will recognize that any processing device can be configured to perform specific operations of the command handler component 312. The command handler component 312 may communicate with the user interface component 308 and the command line component 310 to provide registration and implementation of command options/command line processing within the collaborative communication system/service, for example as shown and described with respect to
Method 400 begins at operation 402 where a collaborative communication system/service interfaces with an external resource. As identified above external resources (e.g., external resources 114) are any resource (e.g., system, application/service, etc.) that exists and is manageable outside of the unified communication platform 105. External resources include but are not limited to systems, application/services that may be managed by a same organization as the unified communication platform 105 (e.g., other services provided by an organization such as web search services, e-mail applications, calendars, device management services, address book services, informational services, etc.) as well as services and/or websites that are hosted or controlled by third parties. In examples, the collaborative communication system/service may send/receive requests to enable interaction between the collaborative communication system/service and external resources. For instance, handshake operations may establish one or more communication channels between the collaborative communication system/service and an external resource. Handshake operations dynamically set parameters of a communications channel established between collaborative communication system/service and an external resource before normal communication over the channel begins. As an example, application agents (e.g., application agents 106d) may interface with external resources 114 using webhooks in order to facilitate integration between a unified communication platform and external resources. In other examples, application programming interfaces (APIs) may enable interaction between a collaborative communication system/service and external resources.
The collaborative communication system/service may be customizable and configurable to control interaction with an external resource/service. As an example, registration between the collaborative communication system/service and an external resource/service may be a single operation that occurs one time. The collaborative communication system/service may also be customizable and configurable to control interaction between a client and external resources/services. In some examples, once an external resource has registered with the collaborative communication system/service, the collaborative communication system/service may enable a client (e.g., client unified communication application 104a) to communicate directly with a registered external resource/service 114. That is, the collaborative communication system/service may be used to broker a connection between a client and an external resource.
Flow proceeds to operation 404 where registration data for a command handler is received from an external resource. As described in an example above, application agents (e.g., application agents 106d) may interface with external resources 114 using webhooks in order to facilitate integration between a collaborative communication system/service (e.g., a unified communication platform) and external resources. In other examples, APIs may enable interaction between a collaborative communication system/service and external resources to enable transmission of registration data. In one example, collaborative communication system/service enables a third-party service to register command handlers that may be utilized by the collaborative communication system/service. For example, a third-party service may provide a capability or functionality that may be included within the collaborative communication system/service to improve a user experience. Registration data is any data associated with a command/command handler that may be useful in communication between the collaborative communication system/service and an external resource for command line processing involving the command/command handler. As an example, registration data may comprise parameters that define a command/command handler. In examples, external resources may define parameters associated with a command/command handler. However, in other examples, the collaborative communication system/service may receive data from an external resource and generate registration data for managing a command/command handler. As identified above, registration data may also relate to command handlers for first-party resources controlled by the collaborative communication system/service. Portions of a command handler that may be defined for any commands within the collaborative communication system/service may comprise but are not limited to:
Further, another example of registration data may comprise exemplary parameter fields similar to (but not limited to):
Flow proceeds to operation 406 where registration data is stored in a storage of the collaborative communication system/service. The collaborative communication system/service may maintain registration data to enable command handlers to be exposed/displayed through the UI of the collaborative communication system/service. Users of the collaborative communication system/service may utilize such command handlers during use of the collaborative communication system/service. In one example a storage is storage 314 described in system 300. Storage is any technology consisting of computer components and recording media used to retain digital data. Examples of storage comprise but are not limited to memory, memory cells, data stores, and virtual memory, among other examples.
Flow may proceed to decision operation 408 where the collaborative communication system/service determined whether input is received through a UI of the collaborative communication system/service that may trigger display of the command handler. A trigger is an input received through the UI of the collaborative communication system/service and may comprise but is not limited to: an entered character, number, symbol, word, and selected UI item, among other examples. An exemplary format for entry of command input may be similar to (but not limited to): Command Format: /commandName/filterParam1/filterParam2 “stringParam.” However, command input may not include all parameters described in the exemplary command input format. Each command input may have zero or more filter parameters. In one example, filter parameters are always applied in order. In examples, each command input may be recognized as a string parameter including one or more characters. If no input is received that triggers display of the command handler, flow branches NO and processing of method 400 ends. However, if it detected that input has been entered that may trigger display of the command handler, flow branches YES and proceeds to operation 410. In examples, operation 408 may occur multiple times as user input is received by the collaborative communication system/service. For instance, an initial input may be entered and processed by the collaborative communication system/service, and further input may be received that modifies a received input. Operation 408 may occur anytime an input is received that comprises a command trigger or any other input that the collaborative communication system/service interprets as an intention of command processing.
In operation 410, the collaborative communication system/service presents the stored command handler in the UI to enable utilization/command line processing involving the stored command handler. As an example, the collaborative communication system/service may communicate with one or more storages of the collaborative communication system/service as well as an external resource (and system associated with such external resource) to enable processing and display of a command handler within the collaborative communication system/service. In one example, presenting of a command handler may comprise displaying a command handler. In another example, presenting of a command handler may comprise displaying a listing or grouping of commands that can be called/executed, for example, as shown in
In examples, method 400 may comprise decision operation 412 where it is determined whether update to the registration data is received. As an example, update to the registration data may be received from an external resource such as a third-party service. If no update to the registration data is received, flow branches NO and processing of method 400 ends. However, if an update to the registration data is received, flow branches YES and flow returns to operation 406 where the stored registration data is updated. In such examples, the updated registration data stored by the collaborative communication system/service may be utilized upon detection of input that may trigger use of commands associated with stored command handlers. In some examples, update to registration data may occur dynamically. In other examples, registration and update of registration data may be managed by administrators of the collaborative communication system/service. In one example, metadata associated with registrations data may be tied to an extension which is packaged as an add-in to be managed by administrators of the collaborative communication system/service. In response to a change in parameters of registration data, the add-in may be updated and handled by a predetermined update cycle to update one or more pieces of registration data. As a note, programming code and user interface elements associated with registered parameter data are likely to be updated when registration data is changed/updated. As such, the collaborative communication system/service may manage registration data and updates to the registration data appropriately to update the collaborative communication system/service in the best manner possible.
Flow of method 420 begins at operation 422 where the third-party service registers with a collaborative communication system/service. As described in an example above, application agents (e.g., application agents 106d) may interface with external resources 114 such as third-party services using webhooks in order to facilitate integration between a unified communication platform and third-party services. In other examples, APIs may enable interaction between a collaborative communication system/service and third-party services to enable transmission of registration data. Examples of registration data are provided above in the description of method 400 (
Flow proceeds to operation 424 where parameters are generated that define a command associated with a command handler. Examples of parameters that may be used to define a command/command handler are described above with respect to the description of method 400 of
Flow then proceeds to operation 426 where the third-party service registers the command handler with the collaborative communication system/service. In examples, a third party service may interface with the collaborative communication system service, through webhooks, APIs, and any other type of requests/responses such as (HTTP requests, JSON requests, etc.).
In decision operation 428, the third-party service may determine whether registration data for the command handler is to be updated. For example, the third-party service may update the parameters associated with a command/command handler. If the registration data (e.g., comprising parameters of for the command/command handler) is to be updated, flow branches YES and proceeds to operation 430 where the updated registration data is transmitted to the collaborative communication system/service. Flow then returns to operation 426 where the third-party service may interact with the collaborative communication system/service to confirm that the command handler is registered with collaborative communication system/service.
If the registration data (e.g., comprising parameters of for the command/command handler) is not updated, flow branches NO and processing of method 420 proceeds to decision operation 432. In decision operation 432, the third-party service determines whether a request associated with the command handler is received. As an example, the collaborative communication system/service may send a request that includes parameters indicating that the command handler is called in the collaborative communication system/service. If a request is not received from the collaborative communication system/service, flow branches NO and processing of method 420 ends. If a request is received from the collaborative communication system/service, flow branches YES and proceeds to operation 434 where the third-party service interacts with the collaborative communication system/service to execute processing associated with the command/command handler.
Flow of method 440 begins at operation 442 where a command input is received through a UI of a collaborative communication system/service. Input is any data (including indications of user action) received through the UI of the collaborative communication system/service. Input may be in any form and received by any of a plurality of input methods including but not limited to: keyboard entry (e.g., physical keyword or soft input panel (SIP), audio data, video data, touch/click actions (e.g., mouse clicks/touchscreens), and transmitted signals, etc. Command input is any input that is entered into input entry field 232 (described in description of
Receipt of a command input may be detected (operation 442) based on identification of a trigger. As identified above, a trigger is an input received through the UI of the collaborative communication system/service and may comprise but is not limited to: an entered character, number, symbol, word, and selected UI item, among other examples. An exemplary format for entry of command input may be similar to (but not limited to): Command Format: /commandName/filterParam1/filterParam2 “stringParam.” However, command input may not include all parameters described in the exemplary command input format. Each command input may have zero or more filter parameters. In one example, filter parameters may be applied in order. In examples, each command input may be recognized as a string parameter including one or more characters.
Flow proceeds to operation 444 where a first query is processed by the collaborative communication system/service. As an example, operation 444 may comprise generating a query and passing the query to a command resource for further processing. In one example, operation 444 may comprise transmitting a first query to a command resource. A command resource is a first-party resource, a second-party resource or a third-party resource that executes a command. In one example, a command resource may be an external resource as described previously. Continuing that example, processing (operation 444) of the first query may generate a query and transmit the query to an external resource upon identification/detection (operation 442) of receipt of the command input. In another example, operation 444 may comprise processing the command input using resources within the collaborative communication system/service. For instance, operation 444 may determine that a command input is to be processed by a first-party resource or resource embedded within the collaborative communication system/service. In that example, a generated query would be processed within the collaborative communication system/service.
In one example, the command input may be received during authoring in the collaborative communication system/service. For instance, a user may be generating a communication (e.g., email, message, message thread, etc.) as shown in
Flow may proceed to operation 446 where a response is generated to the received command input. In examples, a first response is generated by the command resource. In one example, a command resource may be an external resource. In that example, the external resource may receive a query and generate a response based on parameters associated with the command input received from the collaborative communication system/service and the context provided by the collaborative communication system/service. However, in alternative examples, context may not need to be provided by the collaborative communication system/service to enable command processing. In any example, a generated first response (operation 446) may comprise result data and parameters for interacting with the collaborative communication system/service. In some examples, a back and forth interaction (e.g. a plurality of back and forth communications/handshakes) may occur between a command resource and the collaborative communication system/service to generate a response to a received command input. Examples of parameters for interacting with the collaborative communication system/service may comprise ways to display and/or browse result data provided as well as checking whether further interaction is to occur such as whether an update to the command input has been received by the collaborative communication system/service. For instance, building off the example above where input is related to identification of children names of a user named Matthew, result data may include the names of Matthews' children names or a listing of potential options of names that a user may select from.
Flow proceeds to operation 448 where results data is presented in the UI of the collaborative communication system/service. In one example, presenting of the result data may comprise inserting the result data into a communication being authoring the UI of the collaborative communication system/service. For instance, building off the example above where input is related to identification of children names of a user named Matthew, if the personal assistant operation is confident with respect to the names to insert, such information may be inserted into the message for the user to include in the threaded message with Matthew. In one example result data is presented inline in a communication being authored. In another example, presenting of the result data may comprise displaying result data to be browsed and/or selected by a user of the collaborative communication system/service. As an example, result data may be inserted into a communication upon selection by a user of the collaborative communication system/service. That is the collaborative communication system/service may interface with a command resource to enable auto completion of a user command request, for example, allowing the user to pick the documents/data/files to incorporate (e.g., select from results data provided by a command resource) and then continue authoring a message.
Flow may proceed to decision operation 450 where it is determined whether update to the command input is received. If not, flow branches NO and processing of method 440. In examples, the collaborative communication system/service may enable a user to update a command input in real time. That is, a command input can change and the collaborative communication system/service may communicate with command resources (e.g., external resources) in real-time to correspond with an updated input. For instance, continuing the example above with respect to an input having a command for the personal assistant application, an input may be updated to “Matthew, it was great to see you and/assistant kidsnames and wifename.” The collaborative communication system/service is configured to interface with command resources to update result data in real-time.
If an update to the command input is received, flow branches YES and proceeds to operation 452 where a subsequent query is transmitted to the command resource. The subsequent query (e.g., second query) that is transmitted (operation 452) comprises parameters of the updated command input/and or context for the updated command input. In some examples, a back and forth interaction (e.g. a plurality of back and forth communications/handshakes) may occur between a command resource and the collaborative communication system/service to process the subsequent query and ultimately generate an updated response.
Flow proceeds to operation 454 where a response to the subsequent query is received from the command resource. In examples, a plurality of subsequent queries may be received and processed by the collaborative communication system/service. As one example, the response to the subsequent query may comprise updated results data based on the updated command input and/or the context, which may have been provided in a previous query. In the example described above where an input was updated requesting entry of the name of Matthews' wife, the collaborative communication system/service may interactive with a command resource (e.g., embedded resource and/or external resource) to identify and return data to satisfy the updated command input.
Flow proceeds to operation 456 where the updated result data is presented in the UI of the collaborative communication system/service. In one example, presenting of the updated result data may comprise inserting the updated result data into a communication being authoring the UI of the collaborative communication system/service. In one example updated result data is presented inline in a communication being authored. In another example, presenting of the result data may comprise displaying updated result data to be browsed and/or selected by a user of the collaborative communication system/service. As an example, updated result data may be inserted into a communication upon selection by a user of the collaborative communication system/service. In examples, updated result data may be inserted into an authoring replacing a previously inserted item/object or alternatively, being presented along with a previously inserted item/object. Flow may return back to operation 442 when additional command input is received.
Method 460 begins at decision operation 462 where it is determined whether a communication error occurred during interaction with a command resource. If a communication error is identified, flow branches YES and proceeds to operation 464 where a communication is re-initiated with a command resource. In one example, a request may be re-sent to the command resource such as the external resource. In examples, operation 464 may comprise multiple communications between the collaborative communication system/service and a command resource to re-initiate communication. Processing flow may end or start again (if another communication error is detected. In alternative examples, network administrators of the collaborative communication system/service may evaluate the communication error to and attempt to resolve the issue to enable communication between the collaborative communication system/service and external resources.
If a communication error is not identified, flow branches NO and proceeds to decision operation 466 where it is determined whether context of an authoring in the collaborative communication system/service was provided to the command resource. If not, flow branches NO and processing of method 460 ends. If context was provided, flow branches YES and proceeds to decision operation 468.
In decision operation 468, it is determined whether the context was understood by the command resource. If context was processed (e.g., a transmission is received with accurate result data) correctly, flow branches YES and processing of method 460 ends. If not, flow branches NO and proceeds to operation 470 where the context is clarified for the command resource. Operation 470 further comprises re-requesting result data from the command resource.
Flow may proceed to operation 472 where updated result data is received. In alternative examples, the collaborative communication system/service may evaluate the accuracy of the updated results data and interaction with the command resource may change depending on such a determination.
Flow may proceed to operation 474 where the updated result data is presented/displayed through the UI of the collaborative communication system/service.
In exemplary UI view 502, command input 502 is being entered during authoring of a conversation (e.g., communication between users/team members of the collaborative communication system/service). Item 212 of UI view 502 illustrates that the command input 504 is being entered within a conversation between a plurality of users (e.g., Sophia, Mike, Rob, Rachel). As can be seen in UI view 502, a left rail of the UI shows a listing of conversations that may be on-going. A user may use such a feature to conveniently switch between conversations/communications. Command input 504 may be entered into any of the conversations (e.g., communication threads, emails, etc.). However, one skilled in the art will recognize that command input 504 is not limited to conversation threads of the collaborative communication system/service. Command input 504 may be associated with any feature of the collaborative communication system/service including but not limited to communications/conversations, search functionality, files, text input, and links/URLs, semantic objects, etc. An example of a semantic object is illustrated in
As stated above, a number of program modules and data files may be stored in the system memory 704. While executing on the processing unit 702, the program modules 706 (e.g., search engine 711) may perform processes including, but not limited to, the aspects, as described herein. Other program modules that may be used in accordance with aspects of the present disclosure, and in particular for efficient factual question answering, may include extractor component 713, ranker component 715, and scorer component 717, etc.
Furthermore, examples of the present disclosure may be practiced in an electrical circuit comprising discrete electronic elements, packaged or integrated electronic chips containing logic gates, a circuit utilizing a microprocessor, or on a single chip containing electronic elements or microprocessors. For instance, examples may be practiced via a system-on-a-chip (SOC) where each or many of the components illustrated in
The computing device 700 may also have one or more input device(s) 712 such as a keyboard, a mouse, a pen, a sound or voice input device, a touch or swipe input device, etc. The output device(s) 714 such as a display, speakers, a printer, etc. may also be included. The aforementioned devices are examples and others may be used. The computing device 700 may include one or more communication connections 716 allowing communications with other computing devices 718. Examples of suitable communication connections 716 include, but are not limited to, radio frequency (RF) transmitter, receiver, and/or transceiver circuitry; universal serial bus (USB), parallel, and/or serial ports.
The term computer readable media as used herein may include computer storage media. Computer storage media 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, or program modules. The system memory 704, the removable storage device 709, and the non-removable storage device 710 are all computer storage media examples (e.g., memory storage). Computer storage media may include RAM, ROM, electrically erasable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other article of manufacture which can be used to store information and which can be accessed by the computing device 700. Any such computer storage media may be part of the computing device 700. Computer storage media does not include a carrier wave or other propagated or modulated data signal.
Communication media may be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media. The term “modulated data signal” may describe a signal that has one or more characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), infrared, and other wireless media.
One or more application programs 866 may be loaded into the memory 862 and run on or in association with the operating system 864. Examples of the application programs include phone dialer programs, e-mail programs, personal information management (PIM) programs, word processing programs, spreadsheet programs, Internet browser programs, messaging programs, and so forth. The system 802 also includes a non-volatile storage area 868 within the memory 862. The non-volatile storage area 868 may be used to store persistent information that should not be lost if the system 802 is powered down. The application programs 866 may use and store information in the non-volatile storage area 868, such as e-mail or other messages used by an e-mail application, and the like. A synchronization application (not shown) also resides on the system 802 and is programmed to interact with a corresponding synchronization application resident on a host computer to keep the information stored in the non-volatile storage area 868 synchronized with corresponding information stored at the host computer. As should be appreciated, other applications may be loaded into the memory 862 and run on the mobile computing device 800, including the instructions for efficient factual question answering as described herein (e.g., search engine, extractor module, relevancy ranking module, answer scoring module, etc.).
The system 802 has a power supply 870, which may be implemented as one or more batteries. The power supply 870 might further include an external power source, such as an AC adapter or a powered docking cradle that supplements or recharges the batteries.
The system 802 may also include a radio interface layer 872 that performs the function of transmitting and receiving radio frequency communications. The radio interface layer 872 facilitates wireless connectivity between the system 802 and the “outside world,” via a communications carrier or service provider. Transmissions to and from the radio interface layer 872 are conducted under control of the operating system 864. In other words, communications received by the radio interface layer 872 may be disseminated to the application programs 866 via the operating system 864, and vice versa.
The visual indicator 820 may be used to provide visual notifications, and/or an audio interface 874 may be used for producing audible notifications via the audio transducer 825. In the illustrated example, the visual indicator 820 is a light emitting diode (LED) and the audio transducer 825 is a speaker. These devices may be directly coupled to the power supply 870 so that when activated, they remain on for a duration dictated by the notification mechanism even though the processor 860 and other components might shut down for conserving battery power. The LED may be programmed to remain on indefinitely until the user takes action to indicate the powered-on status of the device. The audio interface 874 is used to provide audible signals to and receive audible signals from the user. For example, in addition to being coupled to the audio transducer 825, the audio interface 874 may also be coupled to a microphone to receive audible input, such as to facilitate a telephone conversation. In accordance with examples of the present disclosure, the microphone may also serve as an audio sensor to facilitate control of notifications, as will be described below. The system 802 may further include a video interface 876 that enables an operation of an on-board camera 830 to record still images, video stream, and the like.
A mobile computing device 800 implementing the system 802 may have additional features or functionality. For example, the mobile computing device 800 may also include additional data storage devices (removable and/or non-removable) such as, magnetic disks, optical disks, or tape. Such additional storage is illustrated in
Data/information generated or captured by the mobile computing device 800 and stored via the system 802 may be stored locally on the mobile computing device 800, as described above, or the data may be stored on any number of storage media that may be accessed by the device via the radio interface layer 872 or via a wired connection between the mobile computing device 800 and a separate computing device associated with the mobile computing device 800, for example, a server computer in a distributed computing network, such as the Internet. As should be appreciated such data/information may be accessed via the mobile computing device 800 via the radio interface layer 872 or via a distributed computing network. Similarly, such data/information may be readily transferred between computing devices for storage and use according to well-known data/information transfer and storage means, including electronic mail and collaborative data/information sharing systems.
Aspects of the present disclosure, for example, are described above with reference to block diagrams and/or operational illustrations of methods, systems, and computer program products according to aspects of the disclosure. The functions/acts noted in the blocks may occur out of the order as shown in any flowchart. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved.
The description and illustration of one or more aspects provided in this application are not intended to limit or restrict the scope of the disclosure as claimed in any way. The aspects, examples, and details provided in this application are considered sufficient to convey possession and enable others to make and use the best mode of claimed disclosure. The claimed disclosure should not be construed as being limited to any aspect, example, or detail provided in this application. Regardless of whether shown and described in combination or separately, the various features (both structural and methodological) are intended to be selectively included or omitted to produce an embodiment with a particular set of features. Having been provided with the description and illustration of the present application, one skilled in the art may envision variations, modifications, and alternate aspects falling within the spirit of the broader aspects of the general inventive concept embodied in this application that do not depart from the broader scope of the claimed disclosure.
This application claims priority to U.S. Provisional Application Ser. No. 62/165,739, entitled “INTERACTIVE COMMAND LINE FOR CONTENT CREATION,” filed on May 22, 2015, and U.S. Provisional Application Ser. No. 62/165,880, entitled “UNIFIED MESSAGING PLATFORM AND INTERFACE FOR PROVIDING RICH EMAIL MESSAGES,” filed on May 22, 2015, the entire disclosures of which are hereby incorporated herein by reference.
| Number | Date | Country | |
|---|---|---|---|
| 62165739 | May 2015 | US | |
| 62165856 | May 2015 | US |
