Task management system, information processing device, program, and information processing method

Abstract

To provide a system that facilitates necessary task management when providing different services to different clients. [Solution] The storage unit of the task management system includes a common library that stores template information including task templates that can be commonly applied to multiple clients, and a client library that stores tasks customized for each client for the common library. The control unit of the task management system manages service plans in which one or more services to be provided to clients are set, associates the service plans with the clients, imports template information set in the associated service plans into the client library, and performs tasks based on the template information imported into the client library. ,Ta Generates a sk.

Description

[Technical Field]

[0001] Embodiments of the present disclosure relate to a task management system, an information processing device, a program, and an information processing method. [Background technology]

[0002] Task management systems that can automatically generate tasks are known. [Prior art documents] [Patent documents]

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

[0004] On the other hand, in conventional task management systems, when the services provided to each client are different, it is difficult to manage the tasks required to provide the services.

[0005] The problem to be solved by the present disclosure is to provide a system that facilitates necessary task management when providing different services to different clients. [Means for solving the problem]

[0006] According to one aspect of the present disclosure, there is provided a system for managing tasks performed on clients, the system comprising a control unit and a storage unit. The storage unit includes a common library for storing template information including task templates applicable to a plurality of clients, and a client library for storing tasks customized for each client in the common library. The control unit includes a service plan management module for managing service plans in which one or more services to be provided to clients are set, a client management module for associating the service plans with clients and importing template information set in the associated service plans into the client library, and a task management module for managing tasks based on the template information imported into the client library. ,Ta and a task generation module for generating a task. [Brief explanation of the drawings]

[0007] [Figure 1] 1 is a block diagram showing a functional configuration of a task management system according to an embodiment; [Figure 2] FIG. 2 is a diagram illustrating an example of the configuration of a shared library stored in a storage unit. [Figure 3] FIG. 2 is a diagram illustrating an example of the configuration of a client library stored in a storage unit. [Figure 4] FIG. 1 is a diagram showing a flow of task management using a task management system. [Figure 5] FIG. 10 is a diagram illustrating an example of a provided plan list screen displayed on a user terminal. [Figure 6] FIG. 10 is a diagram illustrating an example of a provided service list screen displayed on a user terminal. [Figure 7] FIG. 10 is a diagram illustrating an example of a shared library screen displayed on a user terminal. [Figure 8] FIG. 10 is a diagram illustrating an example of a contract management screen displayed on a user terminal. [Figure 9] FIG. 10 is a diagram illustrating an example of a client library screen displayed on a user terminal. [Figure 10]FIG. 10 is a diagram illustrating an example of a task import screen displayed on a user terminal. [Figure 11] FIG. 10 is a diagram illustrating an example of a client library screen in which a task has been imported. [Figure 12] FIG. 10 is a diagram illustrating an example of a work procedure display screen displayed on a user terminal. [Figure 13] FIG. 10 is a diagram illustrating an example of a template message list screen displayed on a user terminal. [Figure 14] FIG. 10 is a diagram illustrating an example of a message template creation screen displayed on a user terminal. [Figure 15] FIG. 10 is a diagram illustrating an example of a task template detail display area displayed on a user terminal. [Figure 16] FIG. 10 is a diagram illustrating an example of a message management screen displayed on a user terminal. [Figure 17] FIG. 10 is a diagram illustrating an example of a message detail display area displayed on a user terminal. [Figure 18] FIG. 10 is a diagram illustrating an example of a corresponding task display area displayed on a user terminal. [Figure 19] FIG. 10 is a diagram illustrating an example of a task management screen displayed on a user terminal. [Figure 20] FIG. 10 is a diagram illustrating an example of a task detail display area displayed on a user terminal. [Figure 21] FIG. 10 is a diagram illustrating an example of a response message display area displayed on a user terminal. [Figure 22] FIG. 2 is a block diagram showing a hardware configuration of the task management system. [Figure 23] FIG. 10 is a diagram illustrating an example of an AI chatbot screen displayed on a user terminal. DETAILED DESCRIPTION OF THE INVENTION

[0008] <1. Embodiment> A task management system 1 according to an embodiment of the present disclosure will be described below with reference to the drawings. In the present specification and the drawings, elements similar to those already described are designated by the same reference numerals, and detailed description will not be repeated. In the present disclosure, a user uses the task management system 1 to manage tasks with a client. As an example, the user is a person in charge of an accounting firm where tax accountants, certified public accountants, etc. work, and the client is a business company that has an advisory contract with the accounting firm. However, the present disclosure is not limited to this example.

[0009] (1.1. Functional configuration of task management system 1) The functional configuration of a task management system 1 according to an embodiment will be described with reference to FIG. 1, the task management system 1 includes a server 100 and a user terminal 200. The server 100 and the user terminal 200 are configured to be able to communicate with each other.

[0010] The server 100 is, for example, an information processing device that manages tasks for clients by a user U. The hardware configuration of the information processing device will be described later. Tasks for clients include various operations such as creating documents, making inquiries to clients, and sending invoices. Furthermore, tasks for clients can occur at various times, such as monthly tasks, yearly tasks, and occasional tasks.

[0011] The server 100 includes a control unit 110 and a storage unit 120. The control unit 110 functions as a processor to control the processing of the server 100. The control unit 110 includes a service plan management module 111, a client management module 112, and a task generation module 113.

[0012] The service plan management module 111 manages service plans in which one or more services to be provided to clients are set. The processing of the service plan management module 111 will be described in detail later.

[0013] The client management module 112 associates a service plan with a client, and imports a template task set in the associated service plan into the client library. The processing of the client management module 112 will be described in detail later.

[0014] The task generation module 113 generates a task required for each client based on the template task loaded into the client library. The processing of the task generation module 113 will be described in detail later.

[0015] The storage unit 120 stores programs and data necessary for the processing of the control unit 110, data obtained by the processing of the control unit 110, etc. As an example, the storage unit 120 stores a shared library 121 and a client library 122. Details of each library will be described later.

[0016] The user terminal 200 is an information processing device that has input and output means and can be operated by a user or an administrator. The user terminal 200 may be a general-purpose or dedicated personal computer, a smart device, etc. Smart devices include tablet terminals, smartphones, smart glasses, smart watches, etc.

[0017] If the user terminal 200 is a tablet terminal or a smartphone, the user terminal 200 has a display that functions as an input means and an output means. The user terminal 200 accepts data input by a touch operation on the display by the debtor user.

[0018] (1.2. Library Configuration) The structure of the library stored in storage unit 120 will be described with reference to Figures 2 and 3. Note that the data structure described below is merely an example, and some data may not be included, or other data may be included. Furthermore, the specific data structure of the database held in the library may be appropriately designed using known database-related technology.

[0019] 2, the common library 121 stores information about one or more services associated with service plans and the templates linked to them. Specifically, the common library 121 stores template tasks, template work procedures, and template messages corresponding to the individual services included in each service plan.

[0020] A service plan is a combination of one or more services provided to a client, and the contract fee varies for each plan. For example, as shown in Figure 2, Service Plan A includes "Service a1" and "Service a2," while Service Plan B includes "Service b1," "Service b2," and "Service b3."

[0021] Each service included in a service plan is associated with template information stored in a common library, which may include template tasks, template work procedures, and template messages.

[0022] A template task is a template for work (tasks) to be performed for a client. For example, template tasks can include work templates such as "confirming a contract" and "sending an invoice." In other words, a template task does not have settings such as the date for performing the task, the specific content of the data to be exchanged, the target client, or the person in charge, and only holds information as a template indicating what kind of task should be performed.

[0023] A template work procedure is a model of a work procedure that combines multiple tasks in a chronological order. Like a template task, a template work procedure does not have specific content set, and only holds template information on what tasks should be performed in chronological order.

[0024] A template message is a template for a message to be sent to a client. Like a template task, a template message does not have specific message content set, but only holds template information such as the purpose of the message and the timing at which it should be sent to the client.

[0025] The common library 121 holds information that can be commonly applied to all of the user's clients. The user associates a service plan with each client, and the services included in the associated service plan are applied to the client.

[0026] In the example shown in Figure 2, a template task, a template work procedure, and a template message are included in parallel in service b3, but this is not limited to this form, and a template task may contain multiple template work procedures, and a template task may contain multiple template messages.

[0027] 3, the client library 122 holds information customized for each user client. Specifically, the client library 122 holds information on a service plan set for each client, and information on specific tasks, work procedures, and messages in the services included in the service plan.

[0028] The tasks, work procedures, and messages included in the client library 122 hold the specific task contents and message contents. This information is imported (taken in) from the common library and generated in the client library. The tasks and messages are then edited by the user. The process of importing from the common library 121 to the client library will be described in detail later.

[0029] (1.3. Processing Procedure) The flow of processing in the task management system 1 will be described with reference to FIGS.

[0030] 5, in step S110, the service plan management module 111 sets a service plan based on data from the user terminal 200. The user terminal 200 transmits data necessary for setting a service plan to the server 100 based on user operations on each screen displayed on the display.

[0031] 5 is a diagram illustrating an example of a provided plan list screen 210 displayed on the user terminal 200. As shown in FIG. 5, the provided plan list screen 210 includes a provided plan list 211 and an add provided plan button 212.

[0032] The provision plan list 211 is a list of service plans that can be provided to clients. As an example, the provision plan list 211 includes a provided service column 211a and a price column 211b. The provided service column 211a contains data on services associated with each service plan. As shown in FIG. 5, one or more services are associated with one service plan. The price column 211b contains data on prices set for each service plan. The prices set for a service plan may be incurred continuously (for example, monthly) or on a spot (one-off) basis.

[0033] The add provision plan button 212 is a button for adding a service plan. The user can add a new service plan by pressing the add provision plan button 212. For the new service plan, the user sets the name of the service plan, the contract type (quasi-entrustment, contract, etc.), the contract period, the associated service, the price, etc.

[0034] 6 is a diagram illustrating an example of a provided service list screen 220 displayed on the user terminal 200. As shown in FIG. 6, the provided service list screen 220 includes a provided service list 221 and an add provided service button 222.

[0035] The provided service list 221 is a list of services that can be provided to clients. As an example, the provided service list 221 includes an automatically created task column 221a. The automatically created task column 221a is data on template tasks associated with each service. As shown in Fig. 5, any number of services can be associated with one service.

[0036] The add provided service button 222 is a button for adding a service. The user can add a new service by pressing the add provided service button 222. For the new service, the user sets the service name, type (continuous, spot, etc.), service description, associated template task, etc.

[0037] 7 is a diagram illustrating an example of a shared library screen 230 displayed on the user terminal 200. As shown in FIG. 7, the shared library screen 230 includes a task list 231 and an add task button 232.

[0038] The task list 231 is a list of template tasks stored in the common library. As an example, the task list 231 includes an associated service column 231a. The associated service column 231a contains data on services associated with each template task. As shown in FIG. 7, any number of services can be associated with one template task.

[0039] The add task button 232 is a button for adding a template task. The user can add a new template task by pressing the add task button 232. The user sets the name, work procedure, person in charge, creation timing, linked services, etc. of the template task for the new template task.

[0040] 4, the client management module 112 associates the client with the service plan. The user terminal 200 transmits data necessary for associating the client with the service plan to the server 100 based on the user's operations on each screen displayed on the display.

[0041] 8 is a diagram illustrating an example of a contract management screen 240 displayed on the user terminal 200. As shown in FIG. 8, the contract management screen 240 includes a client name field 241, a contract plan display field 242, and a plan allocation button 243.

[0042] The client name field 241 displays the name of the client to whom the user provides services. The contract plan display field 242 displays the service plan associated with the client displayed in the client name field 241 as the contracted plan. Any number of service plans can be associated with a client. In the example shown in FIG. 8, the service plans "Light Plan" and "Bookkeeping Agency Plan" are displayed in association with the client "ABC Co., Ltd."

[0043] The plan allocation button 243 is a button for allocating another service plan to the client. By pressing the plan allocation button 243, the user can add, change, or delete a service plan associated with the client.

[0044] 4, the client management module 112 imports the template from the shared library. The user terminal 200 transmits data necessary for importing the template to the server 100 based on the user's operations on the screens displayed on the display.

[0045] Fig. 9 is a diagram illustrating a client library screen 250 displayed on the user terminal 200. The client library screen 250 in Fig. 9 displays the state before the template is imported, and includes a client name field 251 and a common library import button 252.

[0046] The client name field 251 displays the name of the client that identifies the client library. The common library import button 252 is a button for importing (taking in) template information. When the user presses the common library import button 252, a task import screen 260 (FIG. 10) is displayed.

[0047] 10 is a diagram illustrating an example of a task import screen 260 displayed on the user terminal 200. The task import screen 260 includes an import task display area 261 and an import button 262.

[0048] The import task display area 261 displays template tasks, template work procedures, and template messages to be imported as templates. In the example shown in Fig. 10, template task categories (folders for classifying template tasks) are displayed in the upper section of the import task display area 261, and template tasks included in a selected category are displayed in the upper section of the import task display area 261. The user can appropriately select tasks to import into the client library 122. When the user presses the import button 262, the selected template information is imported into the client library 122.

[0049] 11 is a diagram illustrating an example of a client library screen 250 in which a template has been imported. When template information is imported into the client library 122, a task list 253 and an add task button 254 are displayed on the client library screen 250.

[0050] Task list 253 is a list of tasks imported from templates in shared library 121. Task list 253 has a details confirmation button 253a. When the user presses details confirmation button 253a, task template details display area 255 (FIG. 14) is displayed, and the user can confirm the details of the task.

[0051] The add task button 254 is a button for adding a task to the client library 122. The user can add a new task by pressing the add task button 254. The user sets the task name, work procedure, person in charge, creation timing, linked services, etc. for the new task.

[0052] 12 is a diagram illustrating an example of a work procedure display screen 270 displayed on the user terminal 200. The work procedure display screen 270 includes a work procedure list 271, a task order display field 272, and an add work procedure button 273.

[0053] The work procedure list 271 is a list of work procedures in which multiple tasks are combined in chronological order. When the user selects a work procedure, information on multiple tasks in the selected work procedure is displayed in a task order display field 272.

[0054] The task order display field 272 displays multiple tasks included in the selected work procedure in chronological order. The task order display field 272 includes a details confirmation button 272a. When the user presses the details confirmation button 272a, details of each task are displayed. Note that the task order display field 272 may also generate and display a checklist of each task in the work procedure.

[0055] The add work procedure button 273 is a button for adding a work procedure. The user can add a new work procedure by pressing the add work procedure button 273. For the new work procedure, the user sets a combination of multiple tasks and a chronological order of the multiple tasks.

[0056] 13 is a diagram showing an example of a template message list screen 280 displayed on the user terminal 200. The template message list screen 280 includes a message list 281 and an add message button 282.

[0057] The message list 281 is a draft of a message to be sent to a client, which is generated from a template message in the shared library 121. The user can edit the content of the message by clicking on each message in the message list 281. The user then sends the edited message to the client. The message whose draft has been checked and edited by the user may be sent to the client on a preset schedule. The message may be sent by email or electronic fax, or by other communication tools such as a social networking service (SNS).

[0058] Add message button 282 is a button for adding a message template. By pressing add message button 282, the user can transition to message template creation screen 285 and add a new message template. The user sets the message name, message content, storage folder, attached files, etc. for the new message template.

[0059] 14 is a diagram showing an example of a message template creation screen 285 displayed on the user terminal 200. The message template creation screen 285 includes a message content area 286 and a collaboration tool setting area 287.

[0060] The message content area 286 is an area for setting the content of the message template, and specifically includes the message name, message content, storage folder, attached files, person in charge, and the like.

[0061] The collaboration tool setting area 287 is an area for setting collaboration between the message and an external tool. Examples of external tools include email and social networking services. In this way, the task management system 1 can centrally manage interactions using different communication tools for each client, thereby reducing the complexity of interactions using different communication tools and the risk of overlooking received messages.

[0062] 4, the task generation module 113 generates a task based on the template imported into the client library 122. The task is automatically generated at a timing preset in the template task. Examples of the timing of task generation include, but are not limited to, once a month (end of the month), once every six months (end of the term), once a year (end of the fiscal year), etc.

[0063] Next, in step S150, the task generation module 113 accepts editing of the generated task. The user terminal 200 transmits data necessary for associating the client with the service plan to the server 100 based on the user's operation on the screen displayed on the display.

[0064] 15 is a diagram illustrating an example of the task template detail display area 255 displayed on the client library screen 250. As described above, when the user presses the check details button 253a in the task list 253 on the client library screen 250, the task template detail display area 255 is displayed. The task template detail display area 255 includes an edit button 255a.

[0065] The edit button 255a is a button that allows the user to edit a task generated in the client library 122. By pressing the edit button 255a, the user can edit a task that has been automatically generated by the task generation module 113 according to a schedule that has been set in advance.

[0066] 16 is a diagram showing an example of a message management screen 290 displayed on the user terminal 200. The message management screen 290 includes a message list 291.

[0067] Message list 291 is a list in which multiple messages received from the client are displayed in a predetermined order. An example of the predetermined order is the chronological order of the dates and times when the messages were received from the client. When a message included in message list 291 is selected, message details display area 295 is displayed.

[0068] 17 is a diagram illustrating an example of a message details display area 295 displayed on the message management screen 290. The message details display area 295 includes a message body 295a, an attached file 295b, and a task display tab 296.

[0069] The message body 295a is the body of the message received from the client, and the attached file 295b is an electronic file attached to the message.

[0070] The task display tab 296 is a tab for displaying the task associated with the message. When the user presses the task display tab 296, a corresponding task display area 297 is displayed.

[0071] 18 is a diagram illustrating an example of the corresponding task display area 297 displayed on the message management screen 290. The corresponding task display area 297 includes a corresponding task list 297a.

[0072] The corresponding task list 297a is a list of one or more tasks associated with the message. In this way, one or more tasks are associated with a message. By checking the corresponding task display area 297, the user can check the tasks associated with the message from the client, making it easy to understand the tasks that should be performed based on the message from the client.

[0073] 19 is a diagram illustrating an example of a task management screen 300 displayed on the user terminal 200. The task management screen 300 includes a task list 301.

[0074] The task list 301 is a list in which a plurality of tasks generated for the client are displayed in a predetermined order. An example of the predetermined order is the order according to the chronological order of the schedule (as an example, deadline) of the task. When a task included in the task list 301 is selected, a task detail display area 305 is displayed.

[0075] 20 is a diagram illustrating an example of the task details display area 305 displayed on the task management screen 300. The task details display area 305 includes a task details column 305a and a message display tab 306.

[0076] The task details column 305a contains detailed information about a task related to a client. For example, the detailed information about a task may include the task status (progress), priority, deadline, and person in charge.

[0077] The message display tab 306 is a tab for displaying a message associated with the task. When the user presses the message display tab 306, a corresponding message display area 307 is displayed.

[0078] 21 is a diagram illustrating an example of the response message display area 307 displayed on the task management screen 300. The response message display area 307 includes a response message list 307a.

[0079] The response message list 307a is a list of one or more messages associated with the task. In this way, one or more messages are associated with a task. By checking the response message display area 307, the user can check the messages associated with the task related to the client, so that the user can easily understand the inquiries made to the client regarding the task, and the like, thereby enabling the task to be carried out smoothly.

[0080] (1.4. Hardware configuration of information processing device) The hardware configuration of an information processing device used as the server 100 and the user terminal 200 will be described with reference to Fig. 22. The information processing device is realized, as an example, by a computer 90 shown in Fig. 22. The computer 90 may include a CPU 91, a ROM 92, a RAM 93, a storage 94, an input interface 95, an output interface 96, and a communication interface 97.

[0081] The CPU 91 functions as a processor that executes processing. Specifically, the CPU 91 uses the RAM 93 as a work memory and executes a program stored in at least one of the ROM 92 and the storage 94. During program execution, the CPU 91 controls each component via a system bus 98 and executes various processes. As an example, the CPU 91 functions as a control unit 110.

[0082] The ROM 92 stores a program that controls the operation of the computer 90. The ROM 92 stores a program necessary for causing the computer 90 to perform each of the above-described processes. The RAM 93 functions as a storage area in which the programs stored in the ROM 92 are expanded.

[0083] The storage 94 stores data necessary for executing the program and data obtained by executing the program. The storage 94 includes one or more selected from a hard disk drive (HDD) and a solid state drive (SSD). As an example, the storage 94 functions as a memory unit 120.

[0084] The input interface (I / F) 95 can connect the computer 90 to an input device 95a. The input interface 95 is, for example, a serial bus interface such as USB. The CPU 91 can read various data from the input device 95a via the input interface 95.

[0085] The output interface (I / F) 96 can connect the computer 90 and an output device 96a. The output interface 96 is, for example, a video output interface such as a Digital Visual Interface (DVI) or a High-Definition Multimedia Interface (HDMI (registered trademark)). The CPU 91 can transmit data to the output device 96a via the output interface 96 and cause the output device 96a to output the data.

[0086] The input device 95a is an example of an input means and includes one or more selected from a mouse, a keyboard, a microphone (voice input), and a touchpad. The output device 96a is an example of an output means and includes one or more selected from a display, a projector, a printer, and a speaker. A device having the functions of both the input device 95a and the output device 96a, such as a touch panel, may also be used.

[0087] The communication interface (I / F) 97 can connect the computer 90 to an external server 97a located outside the computer 90. The communication interface 97 is, for example, a network card such as a LAN card. The CPU 91 can read various data from the external server 97a via the communication interface 97.

[0088] Each process executed by the server 100 may be realized by one computer 90 or by a plurality of computers 90 working together.

[0089] The various data processing operations described above may be recorded as a computer-executable program on a magnetic disk (such as a flexible disk or hard disk), an optical disk (such as a CD-ROM, CD-R, CD-RW, DVD-ROM, DVD±R, or DVD±RW), a semiconductor memory, or other non-transitory computer-readable storage medium.

[0090] For example, information recorded on a recording medium can be read by a computer (or an embedded system). The recording medium may have any recording format (storage format). For example, the computer reads a program from the recording medium and causes a processor to execute instructions written in the program based on the program. The computer may acquire (or read) the program via a network.

[0091] (1.5.Summary) As described above, the task management system 1 according to the present disclosure includes a common library 121 that stores template information including task templates that can be commonly applied to multiple clients, a client library 122 that stores tasks customized for each client in the common library, a service plan management module 111 that manages service plans in which one or more services to be provided to clients are set, a client management module 112 that associates service plans with clients and imports template information set in the associated service plans into the client library, and a task generation module 113 that generates tasks required for each client based on the template information imported into the client library. With this configuration, when different services are provided for each client, tasks can be customized and used for each client based on the template information centrally managed in the common library 121, facilitating task management required for providing services to clients.

[0092] Furthermore, the task generation module 113 may be configured to receive a schedule for generating tasks and generate tasks based on the set schedule. With such specifications, tasks required for providing services to clients are automatically generated at the required timing, preventing tasks from being overlooked and indicating the timing when the person in charge should work on the tasks, thereby providing a pacemaker function for task execution.

[0093] Furthermore, the task generation module 113 may be configured to accept edits by the user for the generated tasks. This allows the user to change the automatically generated tasks, enabling flexible task management.

[0094] Furthermore, the task generation module 113 may be configured to generate a work procedure that is a chronological combination of multiple tasks and a checklist corresponding to the work procedure. By using such a specification, even when providing a complex service that combines multiple tasks, it becomes easy to prevent tasks from being overlooked and ensure that the tasks are performed reliably.

[0095] The task generation module 113 may also be configured to generate a message to a client in addition to generating a task. This configuration makes it possible to transmit information to a client and collect information from a client that is necessary for the execution of a task without omission.

[0096] <2. Other embodiments> Although the task management system 1 according to the present embodiment has been described above, application of the technical concept of the present disclosure is not limited to the above embodiment. For example, the client management module 112 may generate a trained model for a client (hereinafter referred to as a client trained model) based on data received from the client, the content of messages with the client, and data generated in tasks, and manage tasks related to the client. As an example, the client management module 112 may use the client trained model to provide an AI chatbot that accepts questions about the client's business.

[0097] 23 is a diagram illustrating an example of an AI chatbot screen 310 displayed on the user terminal 200. The AI ​​chatbot screen 310 includes a Q&A display area 311, a question entry area 312, and a question submission button 313.

[0098] The Q&A display area 311 is an area that displays a question entered by the user and an answer to the question from the client-trained model. The question entry area 312 is an area where the user enters a question for the client. The question from the user may be a question about the client's company information or a question about a specific task for the client, but is not limited to these examples. When the user enters a question in the question entry area 312 and presses the question submit button 313, the question and an answer based on the client-trained model are displayed in the Q&A display area 311.

[0099] In this way, by generating a trained model for a client based on various data accumulated in the client library 122 during the provision of services to the client, specifically, for example, data related to tasks (task content, work procedures, etc.) and data related to messages (message text and attached data, etc.), it becomes easier to more appropriately perform tasks related to the client. Furthermore, when the amount of work required to perform a task related to a client exceeds the contracted fee for the service plan, the client management module 112 may be configured to issue an alert based on inferences made by the trained model. In this case, for example, the trained model may be configured to infer the amount of work performed by a staff member based on the content of a message sent by the staff member to the client and determine whether the contracted fee has been exceeded. Note that it is preferable to generate a client trained model for each client. Furthermore, a more general trained model for all clients may be generated separately from the client trained model.

[0100] Furthermore, the client management module 112 may be configured to issue an electronic contract to a client, and when the conclusion of the electronic contract is completed, generate a client library that matches the service plan of the client. In this way, the client management module 112 automatically performs a series of processes, such as issuing an electronic contract, concluding the contract, and generating a client library based on the completion of the conclusion, thereby reducing the user's workload for client management.

[0101] In this case, the client management module 112 may be configured to automatically send a notification regarding a billing request according to the service plan associated with the client at a predetermined timing, which can prevent oversight of billing requests to the client and reduce the workload of billing operations.

[0102] Although several embodiments of the present disclosure have been illustrated above, these embodiments are presented by way of example only and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, substitutions, modifications, etc. can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, as well as within the scope of the invention and its equivalents as set forth in the claims. Furthermore, the above-described embodiments can be implemented in combination with each other. [Explanation of symbols]

[0103] 1: task management system, 90: computer, 91: CPU, 92: ROM, 93: RAM, 94: storage, 95: input interface, 95a: input device, 96: output interface, 96a: output device, 97: communication interface, 97a: external server, 98: system bus, 100: server, 110: control unit, 111: service plan management module, 112: client management module, 113: task generation module, 120: memory unit, 121: common library, 122: client library, 200: user terminal, 210: Offered plan list screen, 211: offered plan list, 211a: offered service column, 211b: price column, 212: offered plan add button, 220: offered service list screen, 221: offered service list, 221a: automatically created task column, 222: offered service add button, 230: common library screen, 231: task list, 231a: linked service column, 232: task add button, 240: contract management screen, 241: client name column, 242: contract plan display column, 243: plan allocation button, 250: client library screen, 251: client name Name column, 252: Common library import button, 253: Task list, 253a: Details confirmation button, 254: Add task button, 255: Task template details display area, 255a: Edit button, 260: Task import screen, 261: Import task display area, 262: Import button, 270: Work procedure display screen, 271: Work procedure list, 272: Task order display column, 272a: Details confirmation button, 273: Add work procedure button, 280: Template message list screen, 281: Message list, 282: Add message button, 2 85: Message template creation screen, 286: Message content area, 287: Collaboration tool setting area, 290: Message management screen, 291: Message list, 295: Message details display area, 295a: Message body, 295b: Attachments, 296: Task display tab, 297: Corresponding task display area, 297a: Corresponding task list, 300: Task management screen, 301: Task list, 305: Task details display area, 305a: Task details column, 306: Message display tab, 307: Corresponding message display area, 307a: Corresponding message list

Claims

1. A system for managing tasks performed on a client, the system comprising: a control unit; and a storage unit, The storage unit a common library that stores template information including task templates that can be commonly applied to a plurality of clients; a client library that stores tasks customized for each client with respect to the common library; The control unit a service plan management module for managing a service plan in which one or more services to be provided to a client are set; a client management module that associates the service plan with a client and imports template information set in the associated service plan into a client library; a task generation module that generates a task based on template information imported into the client library.

2. The task generation module Accepting a schedule setting for generating the task; The task management system according to claim 1 , wherein the tasks are generated based on a set schedule.

3. The task management system according to claim 1 , wherein the task generation module accepts editing of the generated task by a user.

4. The task generation module The task management system according to claim 1, wherein a work procedure is generated, which is a combination of a plurality of tasks in chronological order, and a checklist corresponding to the work procedure is generated.

5. The task management system according to claim 1 , wherein the task generation module generates a message for the client in conjunction with the generation of the task.

6. The task management system according to claim 5 , wherein one or more messages are associated with each of the generated tasks.

7. The task management system according to claim 6, wherein a plurality of tasks are associated with one of the generated messages.

8. The client management module The task management system according to claim 5 , wherein the plurality of messages associated with the plurality of tasks are displayed in chronological order of the dates and times when the messages are received from the client.

9. The client management module The task management system according to claim 8 , wherein the task associated with the message is displayed.

10. The client management module The task management system according to claim 5 , wherein the tasks are displayed in chronological order of the schedules of the tasks.

11. The client management module The task management system according to claim 10 , wherein a message associated with the task is displayed.

12. The task management system according to claim 1 , wherein the client management module issues an electronic contract to the client, and when the electronic contract is concluded, generates a client library that matches the service plan of the client.

13. The task management system of claim 1 , wherein the client management module sends a bill to the client according to the service plan.

14. The task management system of claim 1 , wherein the client management module generates a trained model for the client based on data received from the client, content of messages with the client, and data generated in the task.

15. An information processing device that includes a control unit and a storage unit and manages tasks performed on a client, The storage unit a common library that stores template information including task templates that can be commonly applied to a plurality of clients; a client library that stores tasks customized for each client with respect to the common library; The control unit a service plan management module for managing a service plan in which one or more services to be provided to a client are set; a client management module that associates the service plan with a client and imports template information set in the associated service plan into a client library; a task generation module that generates a task based on template information imported into the client library.

16. A program for causing an information processing device to function, the information processing device comprising a control unit and a storage unit, and managing tasks performed on a client, The storage unit a common library that stores template information including task templates that can be commonly applied to a plurality of clients; a client library that stores tasks customized for each client with respect to the common library; The program causes the control unit to managing a service plan that defines one or more services to be provided to clients; A step of associating the service plan with a client and importing template information set in the associated service plan into a client library; and generating a task based on the template information imported into the client library.

17. An information processing method for causing an information processing device to function, the information processing device including a control unit and a storage unit, and managing tasks performed on a client, The storage unit a common library that stores template information including task templates that can be commonly applied to a plurality of clients; a client library that stores tasks customized for each client with respect to the common library; In the information processing method, the control unit managing a service plan that defines one or more services to be provided to clients; A step of associating the service plan with a client and importing template information set in the associated service plan into a client library; and generating a task based on template information imported into the client library.

Images