Work support system, work support method, and program

Abstract

To improve the convenience for a user.SOLUTION: A work support system (1) includes: a posted data acquisition unit (101) configured to acquire posted data relating to a post in the work support system (1); a mention determination unit (102) configured to determine, based on the posted data, whether a mention designating an addressee and reaction information relating to a reaction requested to the addressee has been made; and a reaction request unit (103) configured to request the addressee to react when it is determined that the mention has been made.SELECTED DRAWING: Figure 5

Description

[Technical Field]

[0001] The present disclosure relates to a business support system, a business support method, and a program. [Background technology]

[0002] A mention function that allows a user to post a message by designating a specific person has been known. For example, Patent Document 1 describes a chat service that, in a chat with a mention function, when a user posts a message by designating another user to be mentioned, notifies the other user. A user can also use such a chat service to contact other users for business purposes. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2023-047417 Summary of the Invention [Problem to be solved by the invention]

[0004] However, with the technology of Patent Document 1, even if a user is requested to make a reaction, the mentioned user cannot understand what kind of reaction is requested unless he or she reads the body of the post. Therefore, the technology of Patent Document 1 requires a lot of effort from the user. Furthermore, with the technology of Patent Document 1, the user may overlook the reaction requested from the user. Therefore, the technology of Patent Document 1 does not sufficiently improve user convenience.

[0005] One of the purposes of the present disclosure is to improve user convenience. [Means for solving the problem]

[0006] A business support system according to one aspect of the present disclosure includes a post data acquisition unit that acquires post data related to posts in the business support system, a mention determination unit that determines whether a mention has been made that specifies a destination and reaction information related to a reaction requested from the destination based on the post data, and a reaction request unit that requests the destination to make the reaction when it is determined that the mention has been made. [Effects of the Invention]

[0007] According to the present disclosure, it is possible to improve convenience for users. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 illustrates an example of a hardware configuration of a business support system. [Figure 2] FIG. 10 is a diagram illustrating an example of a screen displayed on a user terminal. [Figure 3] FIG. 10 is a diagram illustrating an example of a screen displayed on a user terminal. [Figure 4] FIG. 10 is a diagram illustrating an example of a screen displayed on a user terminal. [Figure 5] FIG. 2 is a diagram illustrating an example of functions realized by the business support system. [Figure 6] FIG. 2 is a diagram illustrating an example of a user database. [Figure 7] FIG. 2 is a diagram illustrating an example of a posting database. [Figure 8] FIG. 10 is a diagram illustrating an example of a notification database. [Figure 9] FIG. 10 illustrates an example of a posting process. [Figure 10] FIG. 10 illustrates an example of a notification process. [Figure 11] FIG. 10 is a diagram illustrating an example of functions realized by a modified example of a business support system. [Figure 12] FIG. 13 is a diagram showing an example of a thread screen according to a fourth modification. [Figure 13] FIG. 20 is a diagram showing an example of a thread screen according to a sixth modification. [Figure 14] FIG. 20 is a diagram showing an example of a notification screen according to Modification 8. DETAILED DESCRIPTION OF THE INVENTION

[0009] [1. Hardware configuration] An example of an embodiment of a business support system, a business support method, and a program according to the present disclosure will be described. FIG. 1 is a diagram illustrating an example of the hardware configuration of a business support system. For example, the business support system 1 includes a server 10 and a user terminal 20. Each of the server 10 and the user terminal 20 is connected to a network N such as the Internet or a LAN. Although FIG. 1 illustrates one server 10 and one user terminal 20, multiple servers 10 and multiple user terminals 20 may exist.

[0010] The server 10 is a server computer. For example, the server 10 includes a control unit 11, a storage unit 12, and a communication unit 13. The control unit 11 includes at least one processor. The storage unit 12 includes at least one of a volatile memory such as RAM and a non-volatile memory such as a flash memory. The communication unit 13 includes at least one of a communication interface for wired communication and a communication interface for wireless communication.

[0011] The user terminal 20 is a user's computer. For example, the user terminal 20 is a personal computer, a tablet terminal, a smartphone, or a wearable terminal. For example, the user terminal 20 includes a control unit 21, a memory unit 22, a communication unit 23, an operation unit 24, and a display unit 25. The hardware configurations of the control unit 21, the memory unit 22, and the communication unit 23 may be similar to those of the control unit 11, the memory unit 12, and the communication unit 13, respectively. The operation unit 24 is an input device such as a mouse or a touch panel. The display unit 25 is a liquid crystal or organic EL display.

[0012] The programs stored in the storage units 12, 22 may be supplied via the network N. The hardware configurations of the server 10 and the user terminal 20 are not limited to the example in FIG. 1. For example, at least one of the server 10 and the user terminal 20 may include at least one of a reading unit (e.g., a memory card slot) that reads a computer-readable information storage medium and an input / output unit (e.g., a USB terminal) for direct connection to an external device. The programs stored in the information storage medium may be supplied to at least one of the server 10 and the user terminal 20 via at least one of the reading unit and the input / output unit.

[0013] Furthermore, the business support system 1 may include at least one computer. The computers included in the business support system 1 are not limited to the example in FIG. 1. For example, the business support system 1 may include only the server 10. In this case, the user terminal 20 exists outside the business support system 1. The business support system 1 may include the server 10 and other server computers.

[0014] [2. Overview of the business support system] In this embodiment, the business support system 1 has various functions for supporting the user's business. For example, the business support system 1 may provide the user with cloud-based or on-premise groupware. The business support system 1 may also provide the user with a service that supports the user's business, although it is not classified as groupware. For example, the user terminal 20 communicates with the server 10 and displays various screens in the business support system 1 on the display unit 25.

[0015] 2 to 4 are diagrams showing examples of screens displayed on the user terminal 20. For example, when a user logs in to the business support system 1, the user terminal 20 displays a portal screen SC1, which corresponds to the entrance to the business support system 1, on the display unit 25, as shown in the upper part of FIG. 2. The user can use various functions of the business support system 1 from the portal screen SC1. For example, the user can select any thread from the portal screen SC1 to communicate with other users or register data related to the user's own business in an app, which is a type of database.

[0016] In this embodiment, the mention function among the functions of the business support system 1 will be mainly described. The mention function is a function that allows a user who has posted on the business support system 1 to mention a specific person. A post is the content of communication between users. A post can also be called a message or a comment. A post may be made anywhere on the business support system 1. For example, a post may be made on a thread, a bulletin board not classified as a thread, an app, a shared email, a schedule, a chat, or any other place.

[0017] A mention is when a user designates a specific person as the recipient of a post. A user can mention anyone. The mentioned user is notified that a post has been made. For example, when a user is mentioned, the server 10 notifies the user using the notification function of the business support system 1. The notification may be made by any method. For example, the server 10 may notify the user by email, SMS, push notification, banner notification, badge notification, messaging app, SNS, or other method. These notification methods may be combined.

[0018] In this embodiment, an example is taken of a case where a post is made to a thread, which is a type of bulletin board. For example, when a user selects an arbitrary thread from the portal screen SC1, the user terminal 20 displays a thread screen SC2 showing the thread selected by the user on the display unit 25, as shown in the lower part of FIG. 2. The thread screen SC2 displays the content of the post made to the thread. The user can input a new post into the input form F20. Hereinafter, a case where user U1 makes a post by mentioning user U2 will be described.

[0019] For example, as shown in the upper part of FIG. 3, user U1 inputs a post into input form F20 that includes the character string "@user U2," which indicates that the mention is addressed to user U2. In this embodiment, an example is given in which a mention is made using the symbol "@," but a mention may also be made using other symbols. A mention may be made in any manner, and may also be made by selecting an image such as a button, rather than by inputting a symbol.

[0020] For example, when user U1 selects button B21, the input of the post is completed. The server 10 can determine that user U1 has mentioned user U2 based on the character string "@user U2" in the post made by user U1. If the server 10 determines that user U2 has been mentioned, it notifies user U2 that user U2 has been mentioned. When user U2 selects icon I10 on the portal screen SC1 of user U2, as shown in the lower part of FIG. 3, the user terminal 20 of user U2 displays a notification screen SC3 indicating the notification received by user U2 on the display unit 25 of the user terminal 20.

[0021] In this embodiment, user U1 can specify not only the recipient of the mention but also reaction information regarding the reaction requested from the recipient. Reaction information is the portion of a post that indicates a reaction. For example, when user U1 requests a reply as a reaction from user U2, as shown in the upper part of Figure 4, user U1 specifies user U2 as the recipient and inputs a post including the string "@[reply]user U2", which indicates that the mention is requesting a reply as a reaction to the post. The string "@[reply]user U2" may be input at any position in the post. The string "@[reply]user U2" may be input at a position other than the beginning of the post as shown in the upper part of Figure 4.

[0022] For example, in the string "@[reply]userU2", the parentheses indicate the specification of reaction information. The string "reply" in the parentheses indicates the content of the reaction. If a reaction other than a reply is requested, the part in the parentheses will be another string. For example, if confirmation of the post is requested as another reaction, the part in the parentheses may be the string "check?". In the string "@[reply]userU2", the string "userU2" after the part indicating the reaction indicates the recipient of the mention.

[0023] For example, based on the character string "@[reply]user U2" in the post by user U1, the server 10 determines that user U2 has been designated as the recipient and that a mention has been made in which a reply has been requested as a reaction from user U2. This determination may be made by the user terminal 20. The server 10 notifies user U2 that user U2 has been designated as the recipient and that a reply has been requested as a reaction. Hereinafter, a notification in which reaction information has been designated will be referred to as a reaction notification N31. A notification in which reaction information has not been designated will be referred to as a normal notification N30. The normal notification N30 is displayed on the notification screen SC3 at the bottom of FIG. 3.

[0024] As shown in the lower part of FIG. 4, the notification screen SC3 of user U2 displays a reaction notification N31 received by user U2. In the example shown in the lower part of FIG. 4, the normal notification N30 and the reaction notification N31 are distinguished from each other on the notification screen SC3. For example, the normal notification N30 is displayed in a first display area of ​​the notification screen SC3 that is assigned to the normal notification N30. The reaction notification N31 is displayed in a second display area of ​​the notification screen SC3 that is assigned to the reaction notification N31. When user U2 selects the reaction notification N31, the user terminal 20 of user U2 displays a thread screen SC2 that shows details of the post indicated by the reaction notification N31.

[0025] As described above, user U1 can not only designate user U2 as a recipient, but also request a reaction from user U2. By checking the reaction notification N31 displayed on the notification screen SC3, user U2 can easily understand that he or she has not only been designated as a recipient, but also that a reaction is being requested from him or her. The business support system 1 can improve the convenience of users U1 and U2 through this mention mechanism. Details of the business support system 1 will be described below.

[0026] [3. Functions realized by the business support system] 5 is a diagram showing an example of functions realized by the business support system 1. In this embodiment, of the functions of the business support system, a mention function for mentioning in which reaction information is specified will be mainly described.

[0027] [3-1. Functions realized by the server] For example, the server 10 includes a data storage unit 100, a post data acquisition unit 101, a mention determination unit 102, and a reaction request unit 103. The data storage unit 100 is realized by the memory unit 12. The post data acquisition unit 101, the mention determination unit 102, and the reaction request unit 103 are each realized by the control unit 11.

[0028] [Data storage section] The data storage unit 100 stores data necessary for supporting business operations. For example, the data storage unit 100 stores a user database DB1 in which various data of users is stored, a posting database DB2 in which various data of posts made to the business support system 1 is stored, and a notification database DB3 in which various data of notifications made to users is stored.

[0029] FIG. 6 is a diagram illustrating an example of the user database DB1. For example, the user database DB1 stores data such as a user ID, password, and user name for identifying each user, and the organization to which the user belongs. The user database DB1 may store any data related to the user. For example, the user database DB1 may store data indicating the user's job title, department, year of joining the company, years of service, or other information. In this embodiment, an example is given in which a user name is used to specify the recipient of a mention, but other information such as a user ID may also be specified to specify the recipient of a mention.

[0030] 7 is a diagram illustrating an example of the posting database DB2. In this embodiment, a post to a thread is taken as an example, and therefore the posting database DB2 stores a thread ID that is an ID for identifying a thread, a post ID that is an ID for identifying a post, and post data indicating a post to a thread. The posting database DB2 may store any data. The data stored in the posting database DB2 is not limited to the example of FIG. 7. For example, the posting database DB2 may store the user ID of the user who posted, the posting date and time, the destination specified in the mention, the reaction content requested in the mention, etc.

[0031] For example, when a user creates a new thread, the server 10 issues a thread ID for the thread. When a new post is made to the thread, the post data acquisition unit 101, which will be described later, issues a post ID for the post. The post data acquisition unit 101 associates post data indicating the new post with the thread ID and the post ID and stores the data in the post database DB2. The post data may include not only text indicating the content of the post, but also other data such as files included in the post. The post database DB2 may also store data on notifications made by posts.

[0032] 8 is a diagram showing an example of the notification database DB3. For example, the notification database DB3 stores a notification ID for identifying a notification, a post ID of a post that caused the notification, and notification data related to the specific content of the notification. For example, when a new post that mentions a user is made, the server 10 issues a notification ID for the new notification. The server 10 stores the notification ID, post ID, and notification data of the new notification in the notification database DB3 in association with each other.

[0033] The notification data indicates information necessary for the notification. For example, the notification data indicates information regarding the type of notification, the recipient, and the display of the notification. The type of notification indicates whether it is a normal notification N30 or a reaction notification N31. The type of the reaction notification N31 may indicate the specific content of the reaction. For example, the type of the reaction notification N31 may indicate the specific content of the reaction, such as a reply to a post, a confirmation of a post, or another reaction.

[0034] The recipient is a person designated by the user who posted the message. The recipient can also be called a mention recipient. The recipient may be either an individual or a group. A group is a collection of at least one user. A group may be any unit. When users of an organization such as a company use the business support system 1, the group may be the organization or a department within the organization. Another example of a group may be a team or a project. Users may be allowed to create any group they like. When an individual is mentioned, the recipient indicates the user ID of the user who is mentioned as an individual. When a group is mentioned, the recipient indicates the group ID of the mentioned group.

[0035] The specific content of the notification may be all or part of the text of the post, the user ID or username of the user who posted the post, the posting date and time, the unread / read status of the notification, or a combination of these. The notification data may also include other information necessary for the notification. The format of the notification data is not limited to the example in this embodiment. The notification data may indicate whether the reaction requested of the destination has been completed. In other words, the notification data may indicate the current status of the reaction requested of the destination. When the server 10 detects that the destination user has made a reaction in the business support system 1, it updates the notification data to indicate that the reaction by the user has been completed.

[0036] The data stored in the data storage unit 100 is not limited to the above example. The data storage unit 100 can store any data. For example, the data storage unit 100 may store data indicating a specific symbol (e.g., "@") that serves as a criterion for determining whether a mention has been made. The data storage unit 100 may store reaction definition data that defines the relationship between each of a plurality of reactions and a character string for specifying the reaction information. The reaction definition data may be in any format, such as a table format, a mathematical formula format, data written in a markup language, a part of a program, a machine learning model, or any other format. For example, the data storage unit 100 may store data (e.g., HTML data) required to display each of the portal screen SC1, the thread screen SC2, and the notification screen SC3.

[0037] [Posted Data Acquisition Department] The post data acquisition unit 101 acquires post data indicating posts in the business support system 1. For example, the post data acquisition unit 101 acquires post data from the user terminal 20. The post data indicates a character string entered by the user. The post data may indicate information other than a character string. For example, the post data may indicate an emoticon, file, image, video, link, or other information specified by the user. In the example of the thread screen SC2 in Figures 3 and 4, the post data indicates a post entered by the user in the input form F20. The post data acquisition unit 101 may not store the post data acquired from the user terminal 20 directly in the post database DB2, but may add information to the post data, or delete or change some of the information in the post data, and then store the post data in the post database DB2.

[0038] For example, when a user makes a new post in a thread, the user terminal 20 transmits to the server 10 the thread ID of the thread in which the new post was made and post data indicating the new post. The post data acquisition unit 101 acquires the thread ID and post data from the user terminal 20. The post data acquisition unit 101 associates the thread ID and post data acquired from the user terminal 20 with each other and stores them in the post database DB2. The post data acquisition unit 101 can acquire the post data stored in the post database DB2 at any timing. The post data acquisition unit 101 may generate post data based on the data acquired from the user terminal 20, rather than acquiring the post data itself from the user terminal 20.

[0039] [Mention Determination Section] The mention determination unit 102 determines, based on the posting data, whether a mention has been made in which a destination and reaction information related to a reaction requested from the destination have been specified. In this embodiment, mentions in which a destination has been specified but reaction information has not been specified, and mentions in which both a destination and reaction information have been specified are possible. The method for determining a mention in which a destination has been specified but reaction information has not been specified may be the same as a known method. The method for determining a mention in which both a destination and reaction information have been specified may be a method that partially uses a known method.

[0040] In this embodiment, an example is given of a case where a mention is made by inputting a character string indicating a destination (e.g., a user name) after a specific symbol (e.g., "@"), thereby specifying the destination but not the reaction information. A mention is made by inputting a character string indicating a reaction between the specific symbol and the character string indicating the destination, thereby specifying both the destination and the reaction information. A symbol other than "@" may be used for the mention, or an image such as a button may be used instead of inputting a symbol.

[0041] For example, the mention determination unit 102 determines, based on the reaction definition data, whether a character string indicating a reaction has been input after a specific symbol in the post indicated by the post data. If the mention determination unit 102 determines that a character string indicating a reaction has not been input after the specific symbol, it does not determine that a mention in which both a destination and reaction information have been specified has been made. If the mention determination unit 102 determines that a character string indicating a reaction has been input after the specific symbol, it determines that a mention in which both a destination and reaction information have been specified has been made. Furthermore, based on the reaction definition data, the mention determination unit 102 identifies which reaction information has been specified among multiple reactions.

[0042] Note that a series of determinations regarding a mention for which a destination and reaction information are specified may be performed by the user terminal 20. In this case, the posting data may indicate the determination result by the user terminal 20. The determination result by the user terminal 20 may be indicated in data separate from the posting data. The user terminal 20 may determine whether or not a mention for which a destination and reaction information are specified has been made based on the result of an input made by the user. The mention determination unit 102 may determine whether or not a mention for which a destination and reaction information are specified has been made based on the determination result by the user terminal 20.

[0043] Furthermore, the mention determination unit 102 may make a determination according to the mention method defined in the business support system 1. For example, if a mention is made by selecting a specific image or text displayed on the thread screen SC2, the mention determination unit 102 may determine whether a mention has been made by determining whether the specific image or text has been selected. The mention determination unit 102 may determine whether a mention has been made by determining whether information in a specific format indicating a mention is included in the posted data. The information in the specific format may be data separate from the posted data. For example, the mention determination unit 102 may determine whether data accompanying the posted data indicates that it is a mention.

[0044] [Reaction request section] The reaction request unit 103 requests a reaction from the destination when it is determined that a mention specifying the destination and reaction information has been made. The reaction request unit 103 requests a reaction from the destination by transmitting data indicating that a reaction has been requested to the user terminal 20 of the destination user, or by recording data necessary for transmitting the data in the data storage unit 100. For example, the reaction request unit 103 associates destination identification information that can identify the destination with reaction identification information that can identify the reaction. The destination identification information is a user ID or a group ID. The reaction identification information may indicate whether a reaction has been requested or may indicate the specific content of the reaction. The reaction identification information can also be called meta information for the destination.

[0045] For example, the reaction request unit 103 requests a reaction from the destination by associating destination identification information with reaction identification information and storing them in the notification database DB3. In this embodiment, an example is taken of a case where destination identification information and reaction identification information are associated in the notification data. When an individual is specified as the destination, the reaction request unit 103 associates the user ID of the user specified as the individual with the reaction identification information and stores them in the notification database DB3. When a group is specified as the destination, the reaction request unit 103 associates the user ID of at least one user belonging to the group with the reaction identification information and stores them in the notification database DB3.

[0046] The method by which the reaction request unit 103 requests a reaction from a destination is not limited to the above example. For example, the reaction request unit 103 may associate the destination identification information with the reaction identification information and store them in another database such as the posting database DB2. When the reaction request unit 103 receives a request to display the notification screen SC3 from the user terminal 20 of the mentioned user, the reaction request unit 103 may obtain, from the notification database DB3, notification data of a notification in which the user ID of the mentioned user is specified as a destination, and may request a reaction from the mentioned user by displaying the notification screen SC3 on the user terminal 20 based on the notification data.

[0047] Alternatively, for example, the reaction request unit 103 may request a reaction from the destination by transmitting reaction request data indicating that the destination is a request for a reaction. When an individual is designated as the destination, the reaction request unit 103 may transmit an e-mail indicating that a reaction has been requested as reaction request data to the e-mail address of the user designated as the individual. When a group is designated as the destination, the reaction request unit 103 may transmit an e-mail indicating that a reaction has been requested as reaction request data to the entire address of the group or to the e-mail addresses of at least one user belonging to the group.

[0048] In this embodiment, the reaction request unit 103 issues a reaction notification N31 that is distinguished from the normal notification N30. The reaction notification N31 that is distinguished from the normal notification N30 is a reaction notification N31 that the user can recognize as a notification different from the normal notification N30. For example, a reaction notification N31 that is displayed in a display area or screen that is different from the display area or screen on which the normal notification N30 is displayed corresponds to the reaction notification N31 that is distinguished from the normal notification N30. A reaction notification N31 that is filtered and displayed separately from the normal notification N30 corresponds to the reaction notification N31 that is distinguished from the normal notification N30.

[0049] For example, the reaction request unit 103 may perform a reaction notification N31 that is distinguished from the normal notification N30 by displaying the reaction notification N31 on a notification screen SC3 (second notification screen) that is different from the notification screen SC3 (first notification screen) on which the normal notification N30 is displayed. The reaction request unit 103 generating data for displaying the reaction notification N31 may correspond to the reaction request unit 103 performing the reaction notification N31. When other means such as e-mail is used instead of displaying on a screen such as the notification screen SC3, the reaction request unit 103 performs the reaction notification N31 using the other means so as to be distinguished from the normal notification N30. In the case of e-mail, the subject or body of the e-mail indicates that it is a reaction notification N31.

[0050] The method by which the reaction request unit 103 distinguishes between the normal notification N30 and the reaction notification N31 is not limited to the above example. For example, the reaction request unit 103 may distinguish between the normal notification N30 and the reaction notification N31 by notifying them in a first notification manner and a second notification manner. The notification manner is the manner of notification. The notification manner can also be referred to as a notification method. For example, the notification manner may be the color, size, shape, display position, character string, or a combination thereof of the notification. The second notification manner is a notification manner different from the first notification manner. If the notification manner is color, the reaction request unit 103 distinguishes between the normal notification N30 and the reaction notification N31 by notifying them in a first color and a second color. If the notification manner is a notification manner other than color, the reaction request unit 103 may distinguish between the normal notification N30 and the reaction notification N31 by using another notification manner.

[0051] Furthermore, the fact that the reaction request unit 103 performs the reaction notification N31 may mean generating display data for the notification screen SC3, or may mean that the reaction request unit 103 generates data necessary for displaying the reaction notification N31 and stores it in the notification database DB3. In this embodiment, an example is given in which both of these correspond to the reaction request unit 103 performing the reaction notification N31, but only one of these may correspond to the reaction request unit 103 performing the reaction notification N31. This also applies to cases in which the reaction notification N31 is performed by a method other than the notification screen SC3.

[0052] For example, when the reaction request unit 103 determines that a mention with a specified destination and reaction information has been made, it issues a notification ID of the reaction notification N31. The reaction request unit 103 associates the post ID of the post in which the mention with the specified destination and reaction information was made, the notification ID of the notification, and the notification data of the reaction notification N31 in the notification database DB3. When a user logs in to the business support system 1, the reaction request unit 103 issues a reaction notification N31 to the user based on this data associated with the user ID of the user.

[0053] In this embodiment, the reaction request unit 103 displays a notification screen SC3 showing a reaction notification N31 including at least a part of a post for which a destination and reaction information have been specified, on the user terminal 20. When a user instructs the display of the notification screen SC3, the reaction request unit 103 displays the notification screen SC3 showing the reaction notification N31 for the user on the user terminal 20 of the user, based on the notification database DB3.

[0054] [3-2. Functions implemented on user devices] For example, the user terminal 20 includes a data storage unit 200, a display control unit 201, and an operation reception unit 202. The data storage unit 200 is realized by the storage unit 22. The display control unit 201 and the operation reception unit 202 are each realized by the control unit 21.

[0055] [Data storage section] The data storage unit 200 stores data for business support. For example, the data storage unit 200 stores a browser for displaying various screens of the business support system 1. For example, the data storage unit 200 stores an application dedicated to the business support system 1.

[0056] [Display control section] The display control unit 201 causes the display unit 25 to display various screens in the business support system 1. For example, the display control unit 201 causes the display unit 25 to display each of a portal screen SC1, a thread screen SC2, and a notification screen SC3 based on data received from the server 10.

[0057] [Operation reception section] The operation reception unit 202 receives various operations in the business support system 1. For example, the operation reception unit 202 receives operations on the portal screen SC1, the thread screen SC2, and the notification screen SC3. Data indicating the operation content received by the operation reception unit 202 is transmitted to the server 10 as appropriate.

[0058] [4. Processing performed by the business support system] This section describes an example of processing executed in the business support system 1. In this embodiment, a posting process that is executed when a user posts, and a notification process that is executed when the user requests display of a notification, are described. The control units 11 and 21 execute programs stored in the storage units 12 and 22, respectively, to execute the posting process and the notification process.

[0059] [4-1. Posting process] FIG. 9 is a diagram showing an example of the posting process. In this embodiment, an example is taken of a case where a user posts to a thread, so the posting process is executed when the user selects any thread. The server 10 executes a process for displaying a thread screen SC2 indicating the thread selected by the user with the user terminal 20 based on the posting database DB2 (S10). In S10, the server 10 generates display data (e.g., HTML data) for the thread screen SC2 based on the posting data of existing posts in the thread and transmits the generated data to the user terminal 20. The user terminal 20 displays the thread screen SC2 shown in the lower part of FIG. 2 on the display unit 25 based on the display data.

[0060] The user terminal 20 accepts input of a post into the input form F20 (S11). In S11, the user can post a post that includes a character string for specifying the destination and reaction information, or can post a post that does not include the character string. When the user selects button B21, the user terminal 20 transmits to the server 10 the thread ID of the currently displayed thread and post data indicating the post entered by the user (S12). The server 10 acquires the thread ID and post data from the user terminal 20 (S13). In S13, the server 10 issues a post ID and stores the thread ID, post ID, and post data in association with each other in the post database DB2.

[0061] The server 10 determines whether a mention has been made based on the user database DB1 and the posting data (S14). In S14, the server 10 determines whether a mention has been made in which only a destination is specified, or a mention in which a destination and reaction information are specified. If it is determined in S14 that no mention has been made (S14: N), the posting process ends. In this case, no notification is made.

[0062] If it is determined in S14 that a mention specifying only the destination has been made (S14: destination only), the server 10 performs processing for a normal notification N30 for the destination (S15), and the posting process ends. In S15, the server 10 generates a notification ID and stores it in the notification database DB3 together with notification data indicating the mention specifying only the destination. The server 10 generates notification data indicating normal notification N30 as the notification type. The server 10 issues a new notification ID and stores it in the notification database DB3 together with the posting ID and notification data.

[0063] If it is determined in S14 that a mention specifying the destination and reaction information has been made (S14: Destination and Reaction), the server 10 performs processing for a reaction notification N31 for the destination (S16), and the posting process ends. In S16, the server 10 generates a notification ID and stores it in the notification database DB3 together with notification data indicating the mention specifying the destination and reaction information, thereby requesting a reaction indicated by the reaction information specified in the mention from the destination specified in the mention. The server 10 generates notification data that indicates reaction notification N31 as the notification type and indicates the specific content of the reaction identified by the reaction definition data. The server 10 issues a new notification ID and stores it in the notification database DB3 together with the posting ID and notification data.

[0064] [4-2. Notification Processing] 10 is a diagram showing an example of the notification process. For example, when a user selects icon I10, the notification process is executed. The user terminal 20 transmits a display request for a notification screen SC3 to the server 10 (S20). The server 10 receives the display request for the notification screen SC3 (S21), and acquires notification data related to the user ID of the user who made the display request from the notification data stored in the notification database DB3 (S22). In S22, the server 10 acquires the notification data for which the user ID is designated as the destination.

[0065] The server 10 generates display data for a notification screen SC3 based on the notification data acquired in S22 and transmits the display data to the user terminal 20 (S23). In S23, if the user who requested the display of the notification screen SC3 is specified as the destination and there is a mention notification for which reaction information is also specified, the server 10 generates display data for the notification screen SC3 including a reaction notification N31 indicating that a reaction has been requested from the user. The server 10 transmits the display data for the notification screen SC3 to the user terminal 20, thereby requesting a reaction from the user.

[0066] The user terminal 20 receives display data for the notification screen SC3 from the server 10 (S24). The user terminal 20 displays the notification screen SC3 on the display unit 25 (S25), and the notification process ends. The user checks the notification screen SC3, and if a reaction notification N31 is displayed on the notification screen SC3, the user checks the contents of the reaction notification N31 and performs the requested reaction. If the user selects the reaction notification N31, the user terminal 20 executes processing with the server 10 to display the post indicated by the reaction notification N31 on a screen such as the thread screen SC2.

[0067] [5. Summary of embodiments] The business support system 1 of this embodiment determines, based on the posting data, whether a mention has been made specifying a destination and reaction information requested from the destination. If it is determined that a mention has been made, the business support system 1 requests a reaction from the destination. This allows the mentioned user to know that a reaction is requested without having to read the entire body of the post, so the business support system 1 can improve user convenience. For example, if a user receives many notifications, the user may overlook the notification even if a reaction is requested, and may not easily notice that a reaction is requested from the user. In this regard, if a mention specifying a destination and reaction information is made, the user is more likely to notice that a reaction is requested.

[0068] [6. Modifications] The present disclosure is not limited to the above-described embodiments, and may be modified as appropriate without departing from the spirit of the present disclosure.

[0069] 11 is a diagram showing an example of functions realized in a modified business support system 1. As shown in FIG. 11, in the modified example described below, a display control unit 104, a completion determination unit 105, and a reminding unit 106 are realized. Each of the display control unit 104, the completion determination unit 105, and the reminding unit 106 is realized by the control unit 11.

[0070] [6-1. Variation 1] For example, in the embodiment, a mention in which reaction information is specified to one destination is taken as an example. A mention may specify multiple destinations. In this case, the same reaction information may be specified for each of the multiple destinations, or different reaction information may be specified for each of the multiple destinations. In Variation 1, an example is taken of a case in which user U1 requests a reply reaction from user U2 and also requests a viewing reaction from user U3.

[0071] In the example post of Figure 4, user U1 enters a post that includes not only the string "@[reply]user U2" but also the string "@[check?]user U3." The string "@[reply]user U2" means that user U2 is specified as the recipient, and a reply is specified as the reaction information. The string "@[check?]user U3" means that user U3 is specified as the recipient, and confirmation is specified as the reaction information. The same process can be used when other reactions are requested or when three or more recipients are specified, so that reaction information is specified for the recipient.

[0072] The mention determination unit 102 of the first modification determines, based on the posting data, whether a mention has been made in which multiple destinations and requested reaction information for each of the multiple destinations are specified. In the above example, when the reaction request unit 103 detects, based on the posting data, that the post contains the character strings "@[reply]user U2" and "@[check?]user U3," it determines that a mention has been made in which users U2 and U3 are specified as destinations and reaction information is specified for each of users U2 and U3. For example, the reaction request unit 103 determines that a first reaction has been requested from a first destination and a second reaction has been requested from a second destination.

[0073] When a mention is made specifying multiple destinations and different reaction information for the multiple destinations, the reaction request unit 103 of the first modification requests different reactions from each of the multiple destinations. For example, the reaction request unit 103 generates, for each destination specified in the mention, notification data indicating reaction information specified for the destination and a reaction different from that of at least one other destination. The reaction request unit 103 stores the notification data for each of the multiple destinations in a notification database DB3, thereby requesting different reactions from each of the multiple destinations. For example, the reaction request unit 103 requests a first reaction from a first destination and a second reaction from a second destination.

[0074] For example, when the reaction request unit 103 receives a display request for a notification screen SC3 from a user terminal 20 of a certain user, it refers to the notification database DB3 and acquires notification data for a mention for which the user is designated as a destination. If the notification data indicates a reaction for the mention that differs from that for other destinations, the reaction request unit 103 generates display data for the notification screen SC3 indicating the reaction that differs from that for other destinations based on the notification data. The reaction request unit 103 requests a reaction from the user that differs from that for other destinations by transmitting the display data for the notification screen SC3 to the user terminal 20.

[0075] When a mention is made specifying multiple destinations and different reaction information for the multiple destinations, the business support system 1 of the first modification requests different reactions from each of the multiple destinations. This allows a user to request different reactions from each of the multiple destinations with a single post, so the business support system 1 can further improve user convenience. In the example of the first modification, user U1 no longer needs to separately post a request for a reply from user U2 and a request for confirmation from user U3, so the business support system 1 can further improve user convenience for user U1. From the perspective of users U2 and U3, they can also accurately know the reactions requested of them, so the business support system 1 can also improve user convenience for users U2 and U3.

[0076] [6-2. Variation 2] For example, the reaction request unit 103 may request a task related to a business in the business support system 1 as a reaction from the destination. The task is not a general reaction such as viewing a post or a notification, but a reaction specific to a certain user. For example, the task may be an approval task performed in an organization, a task for creating a document or email, a task that involves an appointment such as a meeting or an outing, or other tasks. The user's tasks may be managed by a task management app in the business support system 1. For example, the task may be an individual task that constitutes a workflow.

[0077] In the second modification, the task requested by the destination is specified by the character string "[todo]". The mention determination unit 102 determines whether the post contains the character string "[todo]", which indicates that a task has been specified, based on the post data. If the mention determination unit 102 determines that the post contains the character string, it determines that a task has been requested from the destination as a reaction. If there are multiple types of tasks, the mention determination unit 102 may determine which task has been specified based on a numerical value or the like in the character string "[todo]".

[0078] For example, the reaction request unit 103 generates notification data indicating that a task has been requested as a reaction to a destination specified in the mention. The reaction request unit 103 stores the notification data in the notification database DB3, thereby requesting a task as a reaction from the destination. When the reaction request unit 103 receives a display request for a notification screen SC3 from the user terminal 20 of a certain user, it refers to the notification database DB3 and acquires notification data for the mention to which the user is specified as a destination. When a task is indicated as a reaction in the notification data, the reaction request unit 103 requests a task from the user based on the notification data.

[0079] The business support system 1 of the second modification example requests, as a reaction, the destination to perform a task related to the business in the business support system 1. This allows the user to know that a task that is a reaction specific to the business support system 1 has been requested, and therefore the business support system 1 can further improve user convenience.

[0080] The business support system 1 may manage a task requested of a certain user using a task management app, which is a task management app. For example, when a certain user is designated as a destination and a reaction is also requested from the user, the business support system 1 may associate the user ID of the user with the content of the reaction and register them in the task management app. Data of each record in the task management app is stored in the data storage unit 100. For example, when the user terminal 20 accesses the task management app, the server 10 displays the content of the record in the task management app on the user terminal 20. In this way, when a mention with specified reaction information is made, a task may be automatically registered in the task management app.

[0081] Furthermore, the business support system 1 may manage tasks in a task management app without requesting a reaction as described in Modification Example 2. The business support system 1 may include a post data acquisition unit 101 and a mention determination unit 102, and may further include a task management unit that manages a task in the task management app when it is determined that a mention specifying a task has been made to a recipient. In this case, the business support system 1 may not include the reaction request unit 103. The task management unit of the business support system 1 registers task data related to a task specified to a recipient in the task management app along with recipient identification information. A user can access the task management app by operating the user terminal 20 and display their own tasks on the user terminal 20. The problem to be solved by the present disclosure may be a problem other than the problem described in the problem to be solved by the invention. In this way, according to an aspect in which the business support system 1 does not include the reaction request unit 103, another problem, such as efficiently managing user tasks, can be solved. Such an aspect is also within the scope of the present disclosure.

[0082] [6-3. Variation 3] For example, when multiple recipients are specified in a mention, a reaction may be requested from all of them or from some of them. When a group is specified as a recipient, a reaction may be requested from all of the members of the group or from some of them.

[0083] In Variation 3, an example is taken of a case where a user belonging to a certain company mentions an all-company group, which is a group of all employees. For example, the all-company group is specified by the character string "all company". Furthermore, it is assumed that a user can request a reply reaction from all members of the all-company group by inputting the character string "@[reply][all]all company". It is assumed that a user can request a reply reaction from some members of the all-company group (for example, one person) by inputting the character string "@[reply][some]all company". It is assumed that data indicating the group is stored in advance in the data storage unit 100.

[0084] The mention determination unit 102 of the third modification example determines, based on the post data, whether a reaction has been requested from all of the recipients or from some of the recipients. For example, if the post contains the string "[all]", the mention determination unit 102 determines that a reaction has been requested from all of the recipients. If the post contains the string "[some]", the mention determination unit 102 determines that a reaction has been requested from some of the recipients. These rules may be indicated in the reaction definition data. The mention determination unit 102 analyzes the post data based on the reaction definition data and determines whether a reaction has been requested from all of the recipients or from some of the recipients.

[0085] The method by which the mention determination unit 102 distinguishes between a reaction requested by all and a reaction requested by some is not limited to the above example. For example, the mention determination unit 102 may distinguish between a reaction requested by all and a reaction requested by some based on a character string other than the character string "[all]" and the character string "[some]". As another example, a character string indicating whether the reaction is requested by all or some may be added in parentheses immediately after "@" along with a character string indicating a reaction, such as "reply". In this case, the mention determination unit 102 determines whether a reaction requested by all or some has been made based on the added part.

[0086] In the third modification, the reaction request unit 103 requests a reaction from all of the recipients when a mention requests a reaction from all of the recipients, and requests a reaction from only a portion of the recipients when a mention requests a reaction from only a portion of the recipients. For example, the reaction request unit 103 generates notification data indicating that a reaction has been requested from all of the recipients specified in the mention. The reaction request unit 103 stores the notification data in the notification database DB3, thereby requesting a reaction from all of the recipients. For example, the reaction request unit 103 generates notification data indicating that a reaction has been requested from only a portion of the recipients specified in the mention. The reaction request unit 103 stores the notification data in the notification database DB3, thereby requesting a reaction from only a portion of the recipients.

[0087] For example, when the reaction request unit 103 receives a display request for the notification screen SC3 from the user terminal 20 of a certain user, it refers to the notification database DB3 and acquires notification data for the mention for which the user is designated as the destination. The reaction request unit 103 requests a task from the user based on the notification data. When a reaction is requested from all users, notification data indicating that a reaction has been requested is acquired regardless of which user sent the display request, so the reaction request unit 103 can perform the requested reaction from all users by reacting to the user. When a reaction is requested from only a certain user, notification data indicating that a reaction has been requested is acquired when the certain user sends a display request, so the reaction request unit 103 can perform the requested reaction from only a certain user by reacting to the user.

[0088] In addition, a status indicating whether or not a reaction specified for a destination has been completed may be managed. In this case, the status of each individual reaction may be stored in the notification database DB3 or in another database. The status of a reaction requested from all users indicates completion when all users have completed the reaction. The status of a reaction requested from some users indicates completion when some users have completed the reaction. The server 10 may determine whether or not a reaction has been completed based on data received from the user terminal 20 and update the status.

[0089] The business support system 1 of the third modification example requests a reaction from all of the recipients when a mention requests a reaction from all of the recipients, and requests a reaction from only a portion of the recipients when a mention requests a reaction from only a portion of the recipients. This allows the user to flexibly use mentions that request a reaction from all of the recipients and mentions that request a reaction from only a portion of the recipients, thereby enabling the business support system 1 to further improve user convenience.

[0090] [6-4. Variation 4] For example, if a user is designated as a destination and is also requested to make a reaction, a message indicating that a reaction has been requested from the user may be displayed on the thread screen SC2 of the user. The reaction request unit 103 of the fourth modification example requests a reaction from the destination by displaying the thread screen SC2 showing the post and the reaction requested from the user on the user terminal 20 of the user corresponding to the destination.

[0091] FIG. 12 is a diagram showing an example of a thread screen SC2 of Modification Example 4. FIG. 12 shows an example of the thread screen SC2 that is displayed when the user U2 selects a reaction notification N31 requesting a reply reaction from the notification screen SC3 at the bottom of FIG. 4. For example, the reaction request unit 103 displays a button B22 indicating the content of the reaction requested of the user U2 on the thread screen SC2, along with the post indicated by the reaction notification N31 selected by the user U2. When the user selects the button B22, the user terminal 20 notifies the server 10 that the reaction has been completed. Upon receiving the notification that the reaction has been completed, the server 10 records data indicating that the reaction has been completed (for example, the status described in Modification Example 3) in the data storage unit 100.

[0092] For example, the reaction request unit 103 refers to the post database and acquires post data of the post to be displayed. In the example of FIG. 12, the post to be displayed is the post indicated by the reaction notification N31 selected by the user. The post to be displayed may be another post. For example, the post to be displayed may be another post whose posting date and time is close to the post indicated by the reaction notification N31 selected by the user. The reaction request unit 103 refers to the notification database DB3 and identifies the reaction requested for the post to be displayed. The reaction request unit 103 generates display data for the thread screen SC2 that includes the post indicated by the acquired post data and a button B22 corresponding to the identified reaction. The reaction request unit 103 transmits the display data for the thread screen SC2 to the user terminal 20, thereby displaying the thread screen SC2 of FIG. 12 on the user terminal 20.

[0093] The thread screen SC2 is an example of a posting screen. Therefore, the description "thread screen SC2" can be read as "posting screen." The posting screen is a screen on which at least a portion of a post is displayed. The posting screen may be a screen other than the thread screen SC2. For example, since the notification on the notification screen SC3 shows at least a portion of the post, the notification screen SC3 may correspond to the posting screen. Other examples of the posting screen may include a screen showing comments posted to an app of the business support system 1, a screen showing comments posted to a shared email, a screen showing comments posted to a schedule, or another screen. The reaction request unit 103 can display, on any posting screen, a post in which a certain destination is specified by a mention and a reaction requested from the destination.

[0094] The business support system 1 of the fourth modification example requests a reaction from a destination by displaying a thread screen SC2 showing a post and a reaction requested from the user on the user terminal of the user corresponding to the destination. This allows the user to understand in more detail and clearly what kind of post requests what kind of reaction, so the business support system 1 can further improve user convenience.

[0095] [6-5. Variation 5] For example, in the fourth modification, the thread screen SC2 of the mentioned user U2 is taken as an example, but the thread screen SC2 of the mentioning user U1 may also show the content of the reaction requested from user U2. That is, user U1 may be able to know the reaction he or she requested from user U2 on his or her own thread screen SC2. The business support system 1 of the fifth modification includes a display control unit 104. The display control unit 104 causes the user terminal 20 of user U1 who posted to display a thread screen SC2 showing the post and the reaction requested by the user.

[0096] For example, after user U1 posts the top part of FIG. 4, a button B22 similar to that shown in FIG. 12 is displayed on the thread screen SC2 displayed on the user terminal 20 of user U1. For example, the display control unit 104 displays a button B23 indicating the content of a reaction requested by user U1 to user U2 on the thread screen SC2 along with the post by user U1. The content of the reaction may be indicated by an image other than the button B23. The content of the reaction may be indicated by other information such as text instead of an image. Data necessary for displaying the content of the reaction is assumed to be stored in the data storage unit 100. Data indicating which information should be displayed when which reaction information is specified is also assumed to be stored in the data storage unit 100. The display control unit 104 may display the thread screen SC2 on the user terminal 20 based on this data. The same applies to Modification Example 4, in that these pieces of data may be used.

[0097] For example, the display control unit 104 refers to the posting database and acquires posting data of the post to be displayed. The post to be displayed is a post made by the user. As in variant example 4, the post to be displayed may be another post. The display control unit 104 refers to the notification database DB3 and identifies the reaction requested for the post to be displayed. The display control unit 104 generates display data for a thread screen SC2 that includes the post indicated by the acquired posting data and a button B23 corresponding to the identified reaction. The display control unit 104 causes the thread screen SC2 to be displayed on the user terminal 20 by transmitting the display data for the thread screen SC2 to the user terminal 20.

[0098] As in Variation 4, the thread screen SC2 is an example of a posting screen. In Variation 5, the reference to thread screen SC2 can also be read as posting screen. As in Variation 4, the posting screen in Variation 5 may be a screen other than the thread screen SC2. The display control unit 104 can display, on any posting screen, posts made by the user who displayed the posting screen and reactions requested by the user from the recipients.

[0099] The business support system 1 of the fifth modification displays a thread screen SC2 showing the post and the reactions requested by the user on the user terminal 20 of the user who posted the post. This allows the user to understand in more detail and clearly what kind of reaction the user requested from the recipients based on what kind of post, so the business support system 1 can further improve user convenience.

[0100] [6-6. Variation 6] For example, in a mention in the business support system 1, not only the destination and reaction but also the completion time of the reaction may be specified. In Variation 6, an example is taken of a case where user U1 specifies February 29, 2024 as the completion time of the reply reaction to user U2. For example, in the upper thread screen SC2 of FIG. 4, user U1 inputs the character string "@[reply][2024 / 2 / 29]user U2" to request user U2 to complete the reply reaction by February 29, 2024.

[0101] The mention determination unit 102 of the sixth modification determines whether a mention has been made in which the completion time of the reaction is further specified. For example, the mention determination unit 102 determines whether a specific character string indicating the completion time of the reaction is included based on the post data. In the above example, the mention determination unit 102 determines whether a mention in which the completion time is further specified has been made by determining whether a character string indicating the completion time is included in the second set of parentheses after the specific symbol "@".

[0102] The character string indicating the completion time may be in a predetermined format. For example, the character string indicating the completion time may be the character string "YYYY / MM / DD" indicating the date and year, "MM / DD" indicating only the date and month without indicating the year, the character string "urgent" indicating urgency, the character string "ASAP" indicating as soon as possible, or any other character string. Completion time format data indicating the format of the character string indicating the completion time is stored in the data storage unit 100. The mention determination unit 102 determines that a completion time has not been specified if the post indicated by the post data does not include a character string in the format indicated by the completion time format data, and determines that a completion time has been specified if the post includes a character string in that format.

[0103] FIG. 13 is a diagram showing an example of a thread screen SC2 of Modification Example 6. FIG. 13 shows an example in which a completion time is notified on a thread screen SC2 similar to that of Modification Example 4. The reaction request unit 103 of Modification Example 6 requests the destination specified in the mention to complete the reaction by the completion time. For example, the reaction request unit 103 displays, on the thread screen SC2, the post in which user U2 is mentioned, a button B22 indicating the content of the reaction requested of user U2, and the character string "February 29, 2024" indicating the completion time.

[0104] The business support system 1 of the sixth modification determines whether a mention has been made in which a completion time for the reaction is further specified. The business support system 1 requests the recipient to complete the reaction by the completion time. The mentioned user can know not only the reaction requested of them but also the completion time, so the business support system 1 can improve user convenience.

[0105] [6-7. Variation 7] For example, even if a reaction is requested, a user may forget to react. For this reason, a reminder may be sent to users who have not reacted. In Variation 7, as in Variation 6, an example is given in which a completion time for the reaction is specified. For example, user U1 requests user U2 to make a reply reaction, specifying February 29, 2024 as the completion time. In Variation 7, if user U2 has not replied to user U1's post by February 29, 2024, user U2 will receive a reminder.

[0106] The business support system 1 of the seventh modification includes a completion determination unit 105 and a reminding unit 106. The completion determination unit 105 determines whether or not a reaction has been completed. For example, the completion determination unit 105 determines whether or not a reaction has been completed based on data indicating that the reaction described in the fourth modification has been completed. When the sixth and seventh modifications are combined, the completion determination unit 105 may acquire the current date and time based on a known method such as a real-time clock or GPS, and determine whether or not the completion time has passed.

[0107] If it is determined that the reaction is not complete, the reminding unit 106 sends a reminder to the destination. For example, the reminding unit 106 sends a reminder to the destination using a notification function of the business support system 1. The reminding may be performed by any method. For example, the reminding unit 106 may send a reminder to the destination by email, SMS, push notification, banner notification, badge notification, message app, SNS, or other method. These multiple reminding methods may be combined.

[0108] In addition, in the seventh modification, the completion time of the reaction may not be specified as in the sixth modification. In this case, the completion determination unit 105 may determine whether the reaction is completed when a predetermined time has passed since the posting was made. The predetermined time may be any length. For example, the predetermined time may be about three days, one week, or one month. Data indicating the length of the predetermined time is stored in advance in the data storage unit 100. The reminding unit 106 may send a reminder to the recipient when a predetermined time has passed since the posting was made and no reaction has been made. As another example, the reminding unit 106 may send a reminder to the recipient when a user who made a post to which no reaction has been made performs an operation for reminding.

[0109] The business support system 1 of the seventh modification determines whether the reaction is complete. If it is determined that the reaction is not complete, the business support system 1 sends a reminder to the destination. The reminder allows the user to become aware of the reaction that the user has not completed, so the business support system 1 can improve the convenience of the user to whom the reaction is requested. From the perspective of the user who requested the reaction, the reminder can prevent the reaction from being forgotten, so the business support system 1 can also improve the convenience of the user who requested the reaction.

[0110] [6-8. Variation 8] For example, as described in the embodiment, at least one of a plurality of pieces of reaction information is specified in a mention in the business support system 1. In the example of Fig. 4, regardless of which of a plurality of pieces of reaction information is specified, the reaction notification N31 is displayed together in the reaction notification N31 column on the notification screen SC3. In the eighth modification, an example is given in which the reaction notification N31 is displayed so as to be distinguished for each reaction.

[0111] 14 is a diagram showing an example of a notification screen SC3 of Modification 8. The reaction request unit 103 of Modification 8 requests a reaction from a destination by displaying, on the user terminal 20 of the user corresponding to the destination, a notification screen SC3 showing a notification regarding the post for which a reaction has been requested for each reaction requested by the user. For example, the reaction request unit 103 filters and displays multiple reaction notifications N31 based on the content of the reaction specified by the user. The reaction request unit 103 may identify the content of the reaction based on the notification data stored in the notification database DB3.

[0112] For example, when the user inputs a reply reaction in the input form F32 as shown in the upper part of Fig. 14, the reaction request unit 103 filters and displays the reaction notifications N31 for which the reply specified by the user is requested as a reaction from among the reaction notifications N31 for the user. When the user inputs a confirmation reaction in the input form F32 as shown in the lower part of Fig. 14, the reaction request unit 103 filters and displays the reaction notifications N31 for which the confirmation specified by the user is requested as a reaction from among the reaction notifications N31 for the user.

[0113] The reaction request unit 103 may display, for each reaction, a reaction notification N31 for the post for which the reaction was requested on the notification screen SC3 without any particular filtering. For example, the reaction request unit 103 may display, on the notification screen SC3 of user U1, each of the multiple reactions requested by user U1 in association with the reaction notification N31 for that reaction. The reaction request unit 103 may associate the reaction with the reaction notification N31 by placing the reaction notification N31 for that reaction below the content of the reaction.

[0114] Furthermore, the method by which the reaction request unit 103 associates a reaction with the reaction notification N31 is not limited to the example in Fig. 14. For example, the reaction request unit 103 may display the reaction and the reaction notification N31 in association with each other by placing the reaction notification N31 above, to the left, or to the right of the content of the reaction. When the user U1 selects a reaction, the reaction request unit 103 may filter the reaction notification N31 of the post for which the reaction is requested and display it on the notification screen SC3, thereby displaying the reaction and the reaction notification N31 in association with each other.

[0115] The business support system 1 of the eighth modification example requests a reaction from a destination by displaying, on the user terminal 20 of the user corresponding to the destination, a notification screen SC3 showing a notification regarding the post for which a reaction is requested for each reaction requested from the user. The notification screen SC3 makes it easier for the user to grasp the reaction requested for the user, so the business support system 1 can further improve user convenience.

[0116] [6-9. Variation 9] For example, the method of specifying reaction information in a mention is not limited to the example of the embodiment. In the embodiment, a case has been described in which reaction information is specified by a character string in parentheses after a specific symbol "@" indicating a mention. This specification method is a method of specifying reaction information using a posting notation. The mention determination unit 102 of the ninth modification, which may specify reaction information using other notations, determines whether a mention has been made based on a predetermined notation for specifying reaction information.

[0117] The notation is an input method that indicates that reaction information has been specified. The mention determination unit 102 may determine that reaction information has been specified by a mention based on a notation other than the notation described in the embodiment. For example, the mention determination unit 102 may identify the reaction information specified by a mention based on a notation that uses a certain symbol. In the ninth modification, an example is given in which the symbol "?" indicates a reply reaction and the symbol "!" indicates a confirmation reaction. It is assumed that notation data indicating which symbol means which reaction is stored in the data storage unit 100.

[0118] For example, the mention determination unit 102 determines whether a post is made in the notation indicated by the notation data, based on the post data and the notation data. In the above example, the mention determination unit 102 determines that reply reaction information has been specified if the specific symbol "@" indicating a mention is followed by the symbol "?" indicating a reply reaction in the post indicated by the post data. The mention determination unit 102 determines that confirmation reaction information has been specified if the specific symbol "@" indicating a mention is followed by the symbol "!" indicating a confirmation reaction in the post indicated by the post data.

[0119] The business support system 1 of the ninth modification determines whether a mention has been made based on a predetermined notation for specifying reaction information. By posting according to the predetermined notation, a user can request a reaction from the destination, so the business support system 1 can simplify the method for specifying reaction information.

[0120] [6-10. Variation 10] For example, the method of specifying reaction information in a mention is not limited to the notation used in the embodiment and Variation 9. In Variation 10, when a user posts, options for each of multiple pieces of reaction information are displayed on the thread screen SC2. The user specifies reaction information by selecting an option. The business support system 1 of Variation 10 includes a display control unit 104. The display control unit 104 displays the thread screen SC2, which accepts the selection of at least one of the multiple pieces of reaction information, on the user terminal 20 of the user who posts. Note that, as in Variation 4, the thread screen SC2 is an example of a posting screen.

[0121] For example, on the thread screen SC2 of Modification Example 10, when the user inputs the specific symbol "@" indicating a mention, options indicating each of multiple pieces of reaction information are displayed. When the user selects one of the options, the thread screen SC2 displays the reaction information specified by the user. The display control unit 104 generates display data for the thread screen SC2 including a script for displaying the options. The display control unit 104 transmits the display data for the thread screen SC2 to the user terminal 20, thereby causing the user terminal 20 to display the thread screen SC2, which accepts the selection of at least one piece of reaction information.

[0122] The mention determination unit 102 of the tenth modification determines whether or not a mention has been made in which reaction information selected by the user on the thread screen SC2 is specified. For example, the reaction information selected by the user is indicated in the post data received by the post data acquisition unit 101 from the user terminal 20. The mention determination unit 102 may determine whether or not a mention in which reaction information is specified has been made by determining whether or not reaction information is indicated in the post data.

[0123] The business support system 1 of the tenth modification displays, on the user terminal 20 of the user who posts, a thread screen SC2 that accepts the selection of at least one of a plurality of pieces of reaction information. The business support system 1 determines whether a mention has been made that specifies the reaction information selected by the user on the thread screen SC2. The user can specify the reaction information by making a selection on the thread screen SC2 without having to memorize any particular notation, so the business support system 1 can further improve user convenience.

[0124] [6-11. Other variations] For example, two or more of the modifications 1 to 10 may be combined.

[0125] For example, the functions described as being realized by the server 10 may be realized by the user terminal 20. In this case, the functions may be realized by a browser script or an application installed on the user terminal 20. For example, each function may be shared among multiple computers or may be realized by a single computer. [Explanation of symbols]

[0126] 1 Business support system, 10 Server, 11, 21 Control unit, 12, 22 Memory unit, 13, 23 Communication unit, 20 User terminal, 24 Operation unit, 25 Display unit, N Network, 100 Data storage unit, 101 Post data acquisition unit, 102 Mention determination unit, 103 Reaction request unit, 104 Display control unit, 105 Completion determination unit, 106 Remind unit, 200 Data storage unit, 201 Display control unit, 202 Operation reception unit, B21, B22, B23 Button, DB1 User database, DB2 Post database, DB3 Notification database, F20, F32 Input form, I10 Icon, N30 Normal notification, N31 Reaction notification, SC1 Portal screen, SC2 Thread screen, SC3 Notification screen.

Claims

1. a posting data acquisition unit that acquires posting data related to posts in the business support system; a mention determination unit that determines whether a mention has been made that specifies a destination and reaction information regarding a reaction requested from the destination, based on the posting data; a reaction request unit that requests the destination to make the reaction when it is determined that the mention has been made; Business support system including.

2. the reaction request unit, when the mention is made specifying a plurality of destinations and reaction information that differs from one another among the plurality of destinations, requests the plurality of destinations to each of the plurality of destinations to perform the reaction that differs from one another; The business support system according to claim 1 .

3. the reaction request unit requests the destination to perform a task related to the business in the business support system as the reaction; The business support system according to claim 1 or 2.

4. When the mention requests the reaction from all of the destinations, the reaction request unit requests the reaction from all of the destinations, and when the mention requests the reaction from some of the destinations, the reaction request unit requests the reaction from some of the destinations. The business support system according to claim 1 or 2.

5. the reaction request unit requests the destination to make a reaction by displaying a posting screen showing the post and the reaction requested from the user on a user terminal of the destination; The business support system according to claim 1 or 2.

6. The business support system further includes a display control unit that displays, on a user terminal of the user who posted the post, a posting screen that shows the post and the reaction requested by the user. The business support system according to claim 1 or 2.

7. the mention determination unit determines whether the mention has been made with a further specified completion time of the reaction; the reaction request unit requests the destination to complete the reaction by the completion time. The business support system according to claim 1 or 2.

8. The business support system includes: a completion determination unit that determines whether the reaction has been completed; a reminding unit that, when it is determined that the reaction has not been completed, sends a reminder to the destination; The business support system according to claim 1 or 2, further comprising:

9. In the mention, at least one of the plurality of pieces of reaction information is specified; the reaction request unit requests the destination to react by displaying, on a user terminal of the user corresponding to the destination, a notification screen showing a notification regarding the post for which the reaction is requested, for each of the reactions requested from the user; The business support system according to claim 1 or 2.

10. the mention determination unit determines whether the mention has been made based on a predetermined notation for specifying the reaction information; The business support system according to claim 1 or 2.

11. the business support system further includes a display control unit that displays, on a user terminal of the user who posts, a posting screen that accepts selection of at least one of the plurality of pieces of reaction information; the mention determination unit determines whether the mention is made in accordance with the reaction information selected by the user on the posting screen; The business support system according to claim 1 or 2.

12. Acquire posting data regarding posts in the business support system; Determine whether a mention was made that specifies a destination and reaction information regarding a reaction requested from the destination, based on the posting data; When it is determined that the mention has been made, the destination is requested to react. Business support methods.

13. a posting data acquisition unit that acquires posting data related to posts in the business support system; a mention determination unit that determines whether a mention specifying a destination and reaction information regarding a reaction requested to the destination has been made based on the posting data; a reaction request unit that requests the destination to make the reaction when it is determined that the mention has been made; A program that allows a computer to function as a

Images