WO2024100437A1

WO2024100437A1 - System and method for collaborative communication

Info

Publication number: WO2024100437A1
Application number: PCT/IB2022/060856
Authority: WO
Inventors: Andrzej Turski; Izabella TURSKA; Dalia Hazhah Vanderzon TURSKI
Original assignee: Plusmonk Llc
Priority date: 2022-11-11
Filing date: 2022-11-11
Publication date: 2024-05-16

Abstract

A system and method in which collaborative communication may be initiated through a separate communication channel. Optionally communication may be initiated through a communication channel such as email. Invoking a collaborative space through the present invention, in at least some embodiments, may be performed by sending an email message to a server within the system. The email message may also include other recipients, such as other collaborators for example. Preferably, the email is sent as part of a regular communication process, such that special plug-ins, code within the email and the like are preferably not required.

Description

APPLICATION FOR PATENT

Title: SYSTEM AND METHOD FOR COLLABORATIVE COMMUNICATION

Inventors: Andrzej Turski, Izabella Turska and Dalia Hazhah Vanderzon Turski

FIELD OF THE INVENTION

The present invention, in at least some embodiments, is of a system and method for collaborative communication and in particular, to such a system and method in which collaborative communication may be initiated through a separate communication channel.

BACKGROUND OF THE INVENTION

Collaboration between different individuals, business units, companies and so forth is important for many business processes. Such collaboration may be accomplished through direct verbal communication. However many collaborative processes are improved when supported through collaborative software. Unfortunately such art known collaborative software requires intent from the beginning in order to capture all interactions; that is, if collaboration starts in another medium or through another channel, and is then transferred to the collaborative software, such initial interactions are not currently transferrable to the collaborative software. Such a lack of transferability may result in early communications and hence information being lost, which is problematic.

On the other hand, communication software such as email, while supporting direct communication, is not well organized for collaboration, such that it can be difficult to locate information within email threads.

BRIEF SUMMARY OF THE INVENTION

The background art does not provide a solution for collaboration in which initial communications and/or information may be easily transferred from another medium or through another channel to the solution. The background art also does not provide a solution for collaboration which is also able to accommodate and integrate information from emails.

The present invention, in at least some embodiments, is of a system and method in which collaborative communication may be initiated through a separate communication channel. Optionally communication may be initiated through a communication channel such as email. Invoking a new collaborative space through the present invention, in at least some embodiments, may be performed by sending an email message to a server within the system. The email message may also include other recipients, such as other collaborators for example. Preferably, the email is sent as part of a regular communication process, such that special plug-ins, code within the email and the like are preferably not required.

For example, a new created collaboration workspace may be created automatically from the data contained in the email, for example by including a general collaboration email address in the email message. Once the collaboration space has been created, preferably a unique email address is assigned to that collaboration space, so that subsequent email messages that include the unique email address may then be assigned to the collaboration space, preferably including both message contents and any attachments, if present. More preferably, members of the collaboration space do not need to access an additional external application. Instead, such members may send new messages to, and receive new messages or at least notifications of new messages from, the server operating the collaboration space. Such members may also log into the collaboration space with their email address, for example through two factor authentication, and may interact with the stored contents and/or store additional contents in the collaboration space.

Without wishing to be limited in any way, the present invention addresses the shortcomings of both e-mail and project collaboration workspaces by combining the best of both. When a user wants to start a group project, they simply add an e-mail address associated with the collaboration solution (for example, newproject@the-software.com) to a group e-mail containing the project participants. The collaboration solution creates the email address and may require emails to be sent to the unique address in order for the message contents to be added to the project collaboration website. The server supporting the collaboration solution then parses the e-mail, and preferably automatically, creates a project collaboration website containing all the replies in the e-mail chain in a simple format organized by date sent. The server then preferably automatically sends a link to the website to everyone in the e-mail chain. The server, or an engine at the server, automatically updates the project collaboration website with the reply, creating a single, automatically-updated project collaboration website. The server also preferably automatically uploads all attachments shared in e-mail replies to the website, allowing users to easily see attachments related to the project by time sent, supporting the management of versioning and/or forks in conversations or in attachments.

Management of forks may for example include reducing unwanted/unintended forks through version control or at least collection of messages, attachments and/or other documents by version. Management of forks may also include support of the labeling and/or separation of different messages, attachments and/or other documents by version, by topic and/or by sub-topic. Labels may include a hashtag for example, to support searching by label.

The collaboration space preferably is be created by forwarding just a single e-mail message involving more than one participant to the software e-mail address (or by doing an equivalent action on other communication systems like instant messaging products). It can be done at any stage of the conversation in the other medium or channel, such as email for example, even if it was already ongoing for a while. The chain of previous messages and responses can be re-parsed from the message content, if present there. If the conversation involves multiple versions of attachments, multiple forks, or replies that were dropped, they may be included as well, providing there were also forwarded to the software (or, in some implementations, they may be included automatically if a software agent is installed on the e-mail server).

Once the collaboration space is created, the system creates a new e-mail address that is specific to the project. An e-mail from that e-mail address is preferably sent to all project participants with a private access link to the collaboration space. Optionally both new and old participants can get access to the collaboration webpage, as long they are in the Reply All chain of emails. Forwarding the link to other users preferably enables an invitation to the project (like forwarding of the e-mail conversations would do). Optionally, clicking the link will give access to the collaboration space, preferably with a password or other such authentication.

Each collaboration space preferably has a dedicated e-mail address that is included in the original email reply (for example, ProjectABC456@the software.com). Preferably this email address is the destination for all future replies pertaining to the project. From that point on, users are preferably provided a choice: they may continue using Reply All in e-mail and all subsequent messages will be added to the collaboration space, or they can access the software collaboration website and post replies there, and the software will send e-mail notifications about any changes made that way. In other words, communication by e- mail and the collaboration website are always synchronized.

The software may not attempt to reconcile multiple versions and forks of the documents automatically although optionally such reconciliation may be performed. In any case, preferably the system provides a visual illustration of document history and for each version it will provide a link to the e-mail the version came from. Conversely, if the document is edited on the collaboration space, the version comments are preferably included in the notification message.

Implementation of the method and system of the present invention involves performing or completing certain selected tasks or steps manually, automatically, or a combination thereof. Moreover, according to actual instrumentation and equipment of preferred embodiments of the method and system of the present invention, several selected steps could be implemented by hardware or by software on any operating system of any firmware or a combination thereof. For example, as hardware, selected steps of the invention could be implemented as a chip or a circuit. As software, selected steps of the invention could be implemented as a plurality of software instructions being executed by a computer using any suitable operating system. In any case, selected steps of the method and system of the invention could be described as being performed by a data processor, such as a computing platform for executing a plurality of instructions.

Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The materials, methods, and examples provided herein are illustrative only and not intended to be limiting.

An algorithm as described herein may refer to any series of functions, steps, one or more methods or one or more processes, for example for performing data analysis.

Implementation of the apparatuses, devices, methods and systems of the present disclosure involve performing or completing certain selected tasks or steps manually, automatically, or a combination thereof. Specifically, several selected steps can be implemented by hardware or by software on an operating system, of a firmware, and/or a combination thereof. For example, as hardware, selected steps of at least some embodiments of the disclosure can be implemented as a chip or circuit (e.g., ASIC). As software, selected steps of at least some embodiments of the disclosure can be implemented as a number of software instructions being executed by a computer (e.g., a processor of the computer) using an operating system. In any case, selected steps of methods of at least some embodiments of the disclosure can be described as being performed by a processor, such as a computing platform for executing a plurality of instructions. The processor is configured to execute a predefined set of operations in response to receiving a corresponding instruction selected from a predefined native instruction set of codes.

Software (e.g., an application, computer instructions) which is configured to perform (or cause to be performed) certain functionality may also be referred to as a “module” for performing that functionality, and also may be referred to a “processor” for performing such functionality. Thus, processor, according to some embodiments, may be a hardware component, or, according to some embodiments, a software component.

Further to this end, in some embodiments: a processor may also be referred to as a module; in some embodiments, a processor may comprise one or more modules; in some embodiments, a module may comprise computer instructions - which can be a set of instructions, an application, software - which are operable on a computational device (e.g., a processor) to cause the computational device to conduct and/or achieve one or more specific functionality. Some embodiments are described with regard to a "computer," a "computer network," and/or a “computer operational on a computer network.” It is noted that any device featuring a processor (which may be referred to as “data processor”; “pre-processor” may also be referred to as “processor”) and the ability to execute one or more instructions may be described as a computer, a computational device, and a processor (e.g., see above), including but not limited to a personal computer (PC), a server, a cellular telephone, an IP telephone, a smart phone, a PDA (personal digital assistant), a thin client, a mobile communication device, a smart watch, head mounted display or other wearable that is able to communicate externally, a virtual or cloud based processor, a pager, and/or a similar device. Two or more of such devices in communication with each other may be a "computer network." BRIEF DESCRIPTION OF THE DRAWINGS

The invention is herein described, by way of example only, with reference to the accompanying drawings. With specific reference now to the drawings in detail, it is stressed that the particulars shown are by way of example and for purposes of illustrative discussion of the preferred embodiments of the present invention only, and are presented in order to provide what is believed to be the most useful and readily understood description of the principles and conceptual aspects of the invention. In this regard, no attempt is made to show structural details of the invention in more detail than is necessary for a fundamental understanding of the invention, the description taken with the drawings making apparent to those skilled in the art how the several forms of the invention may be embodied in practice. In the drawings:

Figures 1A and IB show non-limiting, exemplary systems for a collaborative solution according to at least some embodiments;

Figure 2 shows a non-limiting exemplary method for collaboration according to at least some embodiments;

Figure 3 shows a non-limiting exemplary set of functions for the collaboration service backend according to at least some embodiments;

Figure 4 shows a non-limiting exemplary communication stack according to at least some embodiments;

Figure 5 shows a non-limiting exemplary method for document version tracking according to at least some embodiments; and

Figure 6 shows a flow through functions of a collaborative website according to at least some embodiments.

DESCRIPTION OF AT LEAST SOME EMBODIMENTS

Figures 1A and IB show non-limiting, exemplary systems for a collaborative solution according to at least some embodiments. Turning now to Figure 1A, a system 100A features a user computational device 110, a collaboration service 160 and a communication server 120, all communicating through a computer network 150 such as the internet for example. User computational device 110 preferably includes a user app interface 118. User computational device 110 may also include a user input device and a user display device (not shown). The user input device may optionally be any type of suitable input device including but not limited to a keyboard, microphone, mouse, or other pointing device and the like. Preferably user input device includes a microphone and a keyboard, mouse, or keyboard mouse combination. User computational device 110 preferably includes an electronic storage 112 for storing information, including but not limited to documents.

In this non-limiting example, user app interface 118 may be an email client or other software for sending/receiving messages. User app interface 118 may also comprise a web client. The email client and web client may be combined. The user may send an email message through user app interface 118, which is then received by communication server 120 if the email message includes an email address which is associated with collaboration service 160. Communication server 120 then passes the email message to collaboration service 160, to check to see if a collaboration space associated with that email address exists. If such a space exists, then the email message is preferably added to the space. If such a space does not exist, then preferably a new collaboration space is created and the message is added to it.

User computational device 110 also comprises a processor 116 and a memory 114. Functions of processor 116 preferably relate to those performed by any suitable computational processor, which generally refers to a device or combination of devices having circuitry used for implementing the communication and/or logic functions of a particular system. For example, a processor may include a digital signal processor device, a microprocessor device, and various analog-to-digital converters, digital-to- analog converters, and other support circuits and/or combinations of the foregoing. Control and signal processing functions of the system are allocated between these processing devices according to their respective capabilities. The processor may further include functionality to operate one or more software programs based on computer-executable program code thereof, which may be stored in a memory, such as a memory 114 in this non-limiting example. As the phrase is used herein, the processor may be "configured to" perform a certain function in a variety of ways, including, for example, by having one or more general-purpose circuits perform the function by executing particular computer-executable program code embodied in computer-readable medium, and/or by having one or more application-specific circuits perform the function. Also optionally, memory 114 is configured for storing a defined native instruction set of codes. Processor 116 is configured to perform a defined set of basic operations in response to receiving a corresponding basic instruction selected from the defined native instruction set of codes stored in memory 114. For example and without limitation, memory 114 may store a first set of machine codes selected from the native instruction set for receiving an email from the user through user app interface 118, a second set of machine codes selected from the native instruction set for transmitting such information to communication server 120 and a third set of machine codes selected from the native instruction set for accessing a collaboration space at collaboration service 160.

Similarly, collaboration service 160 preferably comprises a processor(s) (not shown) and memory with machine readable instructions (not shown) with related or at least similar functions, including without limitation functions of collaboration service 160 as described herein. For example and without limitation, the memory may store a first set of machine codes selected from the native instruction set for receiving an email from communication server 120, and a second set of machine codes selected from the native instruction set for executing functions of real time collaboration tools 134. Other such sets of machine codes may be used to execute functions of a webpage presentation 132 and an internet transport layer 136, to facilitate creating a collaboration space in response to an email request, and then updating the collaboration space directly and/or through email messages. For example, webpage presentation 132 may enable users to access the collaboration space through a web app or other web software platform. Webpage presentation 132 may enable such users to view received email messages, attachments and other documents, and optionally to add or amend documents.

Communication server 120 preferably comprises a communication interface 122 for receiving email messages which contain an email address associated with communication server 120. For example, the email address may comprise a particular domain name and/or sub-domain name. A mailbox module 124 preferably then parses the email message and address. The address is parsed to locate the portion before the “@” symbol, as that portion (or a segment of that portion) preferably indicates the “address” or identifier for the collaboration space. Other information which may be parsed includes but is not limited to one or more other addresses on the email message, if any; the sender of the email message; and the content of the message, optionally including any attachments. Such parsing may also be performed at collaboration service 160 (not shown). Mailbox module 124 may also handle parsing of email threads and/or other types of messaging conversations, and/or may log received messages.

Communication server 120 also preferably comprises a data storage 125, which may for example store a log of messages received. Communication server 120 may also comprise an internet transport layer interface 126, through which parsed addresses and/or messages are sent to a collaboration service processing engine 140 which is operated by collaboration service 160. Collaboration service processing engine 140 executes a plurality of backend functions for collaboration service 160. These functions enable emails that are received by collaboration service 160 to be analyzed and then stored in a collaboration space associated with a particular email address. The collaboration space is preferably determined according to at least a segment of the collaboration email address before the “@”.

If no collaboration space is associated with at least one email address, then preferably collaboration service processing engine 140 creates such a collaboration space and then invites users to join the space, more preferably according to email addresses that were included in the received email message that triggered formation of the collaboration space. The collaboration space is associated with a specific email address for that space, such that subsequent messages that are addressed to the specific email address associated with the collaboration space may then be stored in, and accessed through, that collaboration space. To initiate creation of the collaboration space, a user may include a generic email address that causes the email message to be routed to collaboration service processing engine 140.

The invitation of member(s) to the new collaboration space may for example be performed by sending an email from the new e-mail address that is specific to the project to all project participants. The email preferably includes a private access link to the collaboration space. Optionally both new and old participants can get access to the collaboration webpage, as long they are in the Reply All chain of emails. Forwarding the link to other users may enable an invitation to the project (like forwarding of the e-mail conversations would do). Preferably, new members are invited by including them on an email message to the new email address that is specific to the project (collaboration space). Once a new participant is added, they preferably receive a unique link to the workspace, followed by the standard login procedures. Optionally, clicking a collaboration space link gives access to the collaboration space, preferably with a password or other such authentication. To support these activities, for example and without limitation, collaboration service processing engine 140 preferably operates a communication bot 142, a data processing 144, an organization of ongoing communication 146, and a storage and archiving 148. These modules preferably perform the required functions of collaboration service processing engine 140 as described herein.

For example, communication bot 142 preferably receives the email messages (optionally without parsing) and determines with which collaboration space they are associated. As noted previously, such a collaboration space is preferably determined according to at least a segment of the collaboration email address before the “@”. The collaboration email address is preferably unique to the collaboration space, although a generic email address may be used to trigger formation of the collaboration space as noted above. If the collaboration space has not yet been created, then communication bot 142 preferably creates such an collaboration space as noted above.

Preferably, organization of ongoing communication module 146 then stores the parsed email message in the appropriate collaboration space, preferably according to a timestamp of when the email message was sent. Optionally the email message is analyzed for a “thread” or more than one email exchange contained within the message. If such a thread is detected, then organization of ongoing communication module 146 preferably analyzes and separates different portions of the email message and stores them with their own timestamp, if each such portion has an available timestamp. Also preferably organization of ongoing communication module 146 sorts different email messages according to who sent them, who received them, timestamp, attachments and so forth, to provide an organized and sorted record of the email messages within the collaboration space. Storage and retrieval of stored messages are preferably handled through storage and archiving module 148, and optionally then in data storage 145 for storing messages in and retrieving message contents from. Storage and archiving module 148 may also operate as an interface for storage and retrieval of attachments and other documents, which may also be stored in data storage 145.

When a new email message is received, preferably a notification is sent through communication bot 142 to members of the collaboration space, identified according to their email address. The identified email addresses preferably at least include those email addresses to which the new email message was sent, apart from the email address associated with collaboration service 160. Optionally other members of the space may be associated with different email address(es), such that a notification is preferably sent to these different email address(es), additionally or alternatively.

Members may then login to collaboration service 160 and view the new email message, along with any associated attachments, through a collaboration service presentation 130. Collaboration service presentation 130 preferably supports front-end functions for collaboration service 160, supporting member interactions with the collaboration space, including but not limited to viewing new and previously posted messages, viewing message threads; and viewing, uploading and/or editing message attachments and other documents. Collaboration service presentation 130 also preferably supports version tracking for messages, message attachments and other documents.

Collaboration service presentation 130 preferably features real time collaboration tools 134. Real time collaboration tools 134 may also support editing, commenting on, annotating email messages and/or attachments and/or other documents, and/or the creation of new messages and/or attachment(s) and/or other documents. In the latter case, the messages and/or attachments and/or other documents may be sent directly to members of the collaboration space, directly or in the form of a notification, indicating that the member may login to collaboration service 160 to view the new information. In this case, the “message” may not in fact be an email message and the “attachment(s)” may not in fact be attachments. An attachment may comprise any suitable type of document, including but not limited to, editable documents, PDF documents, images, audio, video and so forth.

Real time collaboration tools 134 preferably communicate with collaboration service processing engine 140 for message, attachment and/or document storage and retrieval, for example to interact with storage and archiving 148 for such message, attachment and/or document storage and retrieval.

Collaboration service presentation 130 preferably features an internet transport layer 136 for supporting communication through computer network 150.

Figure IB shows another system 100B, in which components with the same numbers have the same or similar function as in Figure 1 A. A plurality of user computational devices 110, shown as user computational device 110A and HOB for the sake of illustration only and without any intention of being limiting, send email messages to communication server 120. These email messages are parsed at communication server 120 and/or collaboration service 160. Optionally a log and/or the messages and/or other metadata is stored at data storage 145 and/or data storage 125. Collaboration service 160 also preferably operates the website for interactive collaboration 130, which may be then displayed to each user computational device 110.

Collaboration service 160 also preferably operates collaboration service processing engine 140 as previously described, which may for example also support operation of communication bot 142 as previously described. As emails are sent from each user computational device 110, preferably one or more additionally emailed users receive a notification of updates to collaboration service 160, for example through one or more additional user computational devices 110. Each user computational device 110A and HOB, through the respective user app interface 118A and 118B, is able to login to collaboration service 160, to access collaboration service presentation 130, through a webpage access 132.

Figure 2 shows a non-limiting exemplary method for collaboration according to at least some embodiments. As shown in a method 200, the flow begins when the user, through the previously described user computational device, sends an email that includes a collaboration service email address on the recipient list at 202. The email message may be in the form of a “reply all” message in which other users may also receive the message at their respective computational devices.

At 204, the collaboration system receives the new email. If the collaboration space indicated by the email address already exists, the flow skips to 214. Otherwise, at 206, a new collaboration space is preferably created for <project_name>. For example, the identifier for the collaboration space may be “identifier” followed by the @ and the remainder of the email address for addressing the collaboration server.

At 208, a unique email address is created for the project, for example if a general collaboration service email address is used to start a new collaboration workspace. The email parser preferably determines whether the collaboration service email address is specific to an existing collaboration workspace, or is more general, for example for collaboration workspaces for a particular group or company, or even for any new collaboration workspace. If the email address is not specific, then receipt of the general collaboration service email address indicates a new collaboration space is to be created and hence that a unique email address needs to be created, to specifically address the new collaboration space. At 210, optionally a welcome email is sent to all addressees on the original email from 202, inviting them to join the collaboration workspace. The welcome email at 210 is preferably sent from the unique email address associated with the collaboration space (project), which uniquely identifies that collaboration space. This unique email address may then be used by each user to include additional email messages in the collaboration space. Further email messages that have the unique address are received at 212, and are then added to the project collaboration space. Other email messages may be added directly to the project collaboration space at 214.

Figure 3 shows a non-limiting exemplary set of functions for the collaboration service backend according to at least some embodiments. As shown, a set of functions operating as a flow 300 preferably includes receipt of an email by an email server at 302. This email may contain a unique email address associated with a specific collaboration space (project), or a general email address that is used to initiate creation of the collaboration space. The email is sent to a mail notification receiver 304, for example at the previously described communication and/or collaboration servers. A mail parser 306 extracts the content of the email, which may include the content of the message and of one or more attachment(s), if any. Messages and attachments are then stored at a storage 308. The parsed email content is sorted into projects and hence into specific collaboration spaces, optionally with timestamps and versioning, at 310, according to the unique email address associated with each such collaboration space. Such content may be stored at a collaboration database 312. Alternatively, unique email addresses and optionally login information are stored at collaboration database 312, and messages and attachments are stored in the separate storage 308.

Mail parser 306 preferably communicates with a mail access component 318 to identify the associated email address, whether a unique email address associated with a specific collaboration space, or a general email address that is used to set up the collaboration space. If the unique email address is found in the email message, then the email message and optionally one or more attachments may be stored in storage 308 and/or collaboration database 312. A reply email generator 316 then preferably generates an email message to notify members of the collaboration space regarding the availability of new content in the collaboration space.

If no unique email address associated with a specific collaboration space is found, but the general email address to request initiation of the collaboration space is instead found, then preferably an email address generator 314 generates a new unique email address associated with that collaboration space. Email address generator 314 may then create an invitation email to invite those to whom the original email messages was sent, or alternatively reply email generator 316 may create this invitation email.

Mail access component 318 then adds any necessary information to the email message so that it may be transmitted to the members of the collaboration space. A mail sending module 320 then sends the email through standard email server 302.

Figure 4 shows a non-limiting exemplary communication stack according to at least some embodiments. As shown a communication stack 400 preferably comprises an SMTP stack 402, for handling email messages and an HTTP stack 404 for handling web based (markup language document) communication. SMTP stack 402 receives a new email message at a mail server 408. Backend processing 410 preferably parses the message as described herein and stores the parsed information in a data storage 412. A query engine 416 is able to query data storage 412 for retrieving new messages and associated content, for example in response to a query received through a web server 414. New messages and documents uploaded or modified through the web server interface may also be announced to collaboration space members through a notification email generator 406.

Figure 5 shows a non-limiting exemplary method for version tracking according to at least some embodiments. The version tracking is preferably performed for messages and attachments as described herein. As shown in a method 500, an email message is parsed at 502, for example as described herein. At 504, any attachment(s), if present, are analyzed. The analysis preferably comprises at least a determination of the file name for the attachment, but preferably also considers the file type, date of last modification and optionally also the content.

A timestamp associated with the email message is preferably determined at 506. Optionally, if the email message includes a thread, then preferably each portion of the message and its timestamp are analyzed separately.

The analysis and the timestamp are then preferably used at 508 to determine a version of the message and also of the attachment(s), if any. Preferably, the analysis is also used to determine which email thread is associated with the email message. For example, earlier messages in the email thread may have been analyzed already, in which case the new message may be associated with the earlier messages in the thread. At 510, the various versions of the message and/or attachments and/or other documents are preferably stored in the collaboration space, preferably in an organized manner. The timestamp analysis may be used to sort the message and/or attachments. Optionally, differences between different versions of the same attachment may also be sorted within the collaboration space.

At 512, collaboration space members are preferably notified of the new content, for example by receiving a new email message. Optionally such members are notified even if they weren’t on the original email message.

Optionally at 514, the message and/or attachment and/or other document is edited within the collaboration space, and/or a new message and/or attachment is added to the collaboration space. Editing may also comprise commenting. At 516, the edited version is preferably sorted, at which point the process may return to 512.

Figure 6 shows a flow through functions of a collaborative website according to at least some embodiments. As shown in a flow 600, the process begins with one or more components of the website interface for the collaboration workspace being initiated at 602. The user may then choose to interact with one or more communication tools 610, including but not limited to tools for editing 612, a wiki-page 614, a whiteboard 616, a message sending function 618, a file upload tool 620 and a file update tool 622.

The user may also choose to interact with a display of prior communication information, which may include but is not limited to previously sent emails, attachments and/or other previously sent documents, and/or documents that are specifically directly uploaded to and/or edited in the collaborative website. Non-limiting examples of various display modalities include chronological display of received emails 632, visual representation of messaging and/or other documentation forks and/or threads 634, hashtags and other filters 636, and a visual representation of unreconciled versions of documents 638. Such display modalities support management of forks and/or versions of messages, attachments and/or other documents. Management of forks may for example include reducing unwanted/unintended forks through version control or at least collection of messages, attachments and/or other documents by version. Management of forks may also include support of the labeling and/or separation of different messages, attachments and/or other documents by version, by topic and/or by sub-topic. Labels may include a hashtag for example, to support searching by label. In either case, the flow then continues to a detection of the occurrence of one or more changes 650, including whether any such changes have occurred. If one or more changes have occurred then a notification is sent to one or more participants in the collaboration space at 652, for example through the previously described communication bot.

It is appreciated that certain features of the invention, which are, for clarity, described in the context of separate embodiments, may also be provided in combination in a single embodiment. Conversely, various features of the invention, which are, for brevity, described in the context of a single embodiment, may also be provided separately or in any suitable subcombination.

Although the invention has been described in conjunction with specific embodiments thereof, it is evident that many alternatives, modifications and variations will be apparent to those skilled in the art. Accordingly, it is intended to embrace all such alternatives, modifications and variations that fall within the spirit and broad scope of the appended claims. All publications, patents and patent applications mentioned in this specification are herein incorporated in their entirety by reference into the specification, to the same extent as if each individual publication, patent or patent application was specifically and individually indicated to be incorporated herein by reference. In addition, citation or identification of any reference in this application shall not be construed as an admission that such reference is available as prior art to the present invention.

Claims

WHAT IS CLAIMED IS:

1. A system for collaborative communication, comprising a user computational device, an email communication server and a collaboration service, communicating through a computer network; wherein each of said user computational device, said email communication server and said collaboration server comprises a memory for storing a plurality of instructions and a processor configured to execute said instructions; wherein said user computational device is configured to send an email message to said email communication server, wherein said email message comprises an email address associated with said collaboration service; wherein said email communication server sends said email message with said email address to said collaboration service; wherein said collaboration service receives said email message and analyzes said email address, to determine whether a collaboration space is to be created; wherein if said collaboration space is to be created, said collaboration service creates said collaboration space and a unique email address associated with said collaboration space, such that email message content from an email message having said unique email address is stored by said collaboration service in said collaboration space; and wherein if said collaboration space associated with said email address already exists, said collaboration service adds said email message to said collaboration space.

2. The system of claim 1 , wherein said collaboration service creates an invitation email to each other email address on said email message, inviting each email address to become a member of said collaboration space.

3. The system of claim 2, wherein said collaboration service receives an additional email with said unique email address and stores said additional email, and one or more attachments if present, in said collaboration space; and transmits a notification of new content to each member of said collaboration space.

4. The system of any of the above claims, wherein said collaboration service receives another email message having said unique email address, wherein said other email message includes an additional email address, wherein said additional email address is not a member of said collaboration space; wherein said collaboration service creates an invitation email to said additional email address, inviting said additional email address to become a member of said collaboration space. The system of any of the above claims, wherein said collaboration service parses said email message, and adds each attachment and a body of said email message to said collaboration space. The system of claim 5, wherein said collaboration service receives a chain of previous messages and responses, and parses same to add to said collaboration space according to said collaboration space email address. The system of claim 6, wherein said collaboration service determines a version of each attachment or other document in said collaboration space. The system of any of claims 5-7, wherein said collaboration service determines at least one label for a message, attachment or other document or a combination thereof, wherein said label relates to a fork, a version, a topic or a sub-topic. The system of any of the above claims, wherein said collaboration service further comprises a collaboration service presentation, said collaboration service presentation comprising a website or web app, and wherein each member of said collaboration space is able to access said website or web app through said collaboration service presentation. The system of claim 9, wherein said collaboration service presentation supports editing a document, wherein said collaboration service transmits a notification to other members upon said editing. The system of claim 10, wherein said collaboration service presentation supports uploading a document, wherein said collaboration service transmits a notification to other members upon said uploading. The system of claim 11, wherein said document comprises an editable document, a text document, a PDF document, an image, audio, and/or video. The system of any of the above claims, wherein said collaboration service further comprises a memory for storing instructions and a processor for executing said instructions, memory may store a first set of machine codes selected from the native instruction set for receiving an email from said email communication server, and a second set of machine codes selected from the native instruction set for executing functions of real time collaboration tools. The system of claim 13, wherein said real time collaboration tools are selected from the group consisting of text document viewer, text document editor, slides document viewer, slides document editor, image document viewer and image document editor. The system of claims 13 or 14, wherein said memory further stores sets of machine codes for executing functions of a webpage presentation and an internet transport layer, to facilitate creating a collaboration space in response to an email request, and for then updating the collaboration space directly and/or through email messages. The system of claim 15, wherein said webpage presentation further comprises a website, a web app or other web software platform. The system of claims 15 or 16, wherein said webpage presentation supports viewing received email messages, attachments and other documents, amending said documents and adding new documents. The system of any of the above claims, wherein said email communication server further comprises a communication interface for receiving email messages which contain an email address associated with said email communication server, and a mailbox module for parsing said email message and address; wherein said address is parsed to locate a portion before the “@” symbol, such that said portion (or a segment of said portion) indicates an identifier for said collaboration space. The system of any of the above claims, wherein said webpage presentation supports at least one display modality selected from the group consisting of chronological display of received emails, visual representation of messaging, visual representation of documentation forks, visual representation of messaging threads, hashtags or other filters, and a visual representation of unreconciled versions of documents.