Matching support system, matching support method, and program

Abstract

The matched client and supporter will then coordinate their arrangements after the match is made. [Solution] A matching support system that matches a client who has a problem they want support for with a supporter who can provide support for that problem, comprising: an adjustment support unit that generates a talk room in which the client and the supporter exchange messages in a dialogue format; and a status management unit that displays a status indicating the progress of the adjustment work performed by the client and the supporter together with the talk room.

Description

Technical Field

[0001] The present invention relates to a matching support system, a matching support method, and a program.

Background Art

[0002] There is a system that matches a requester who has a problem for which support is desired with a supporter who can provide support for that problem. For example, Patent Document 1 discloses a technique that enables application even when employment is possible only during some time periods with respect to the desired date and time of employment, and enables easy adjustment of working hours.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in Patent Document 1, after matching, the matched requester and supporter cannot make adjustments. After the matching is established and the working hours can be adjusted, it is better if the detailed work content, treatment, job regulations, etc. can also be adjusted.

[0005] The present invention has been made in view of such a situation, and its object is to provide a matching support system, a matching support method, and a program in which the matched requester and supporter can make adjustments after matching.

Means for Solving the Problems

[0006] One aspect of the present invention is a matching support system for matching a client who has a problem they would like to be helped with with a supporter who can provide support for that problem, comprising: an adjustment support unit that generates a talk room in which the client and the supporter exchange messages in a dialogue format; and a status management unit that displays a status indicating the progress of the adjustment work performed by the client and the supporter together with the talk room.

[0007] One aspect of the present invention is a computer-based matching support method used in a matching support system that matches a client with a problem they want support for with a supporter who can provide support for that problem, wherein the adjustment support unit generates a talk room in which the client and the supporter exchange messages in a dialogue format, and the status management unit displays the status indicating the progress of the adjustment work performed by the client and the supporter along with the talk room.

[0008] One aspect of the present invention is a program used in a matching support system that matches a client with a problem they want help with with a supporter who can provide support for that problem. The program causes the computer to generate a talk room in which the client and the supporter can exchange messages in a dialogue format, and displays a status indicating the progress of the coordination work being carried out by the client and the supporter along with the talk room. [Effects of the Invention]

[0009] According to the present invention, the matched client and supporter can make adjustments after the matching process is complete. [Brief explanation of the drawing]

[0010] [Figure 1] This is a block diagram showing an example configuration of a matching support system in an embodiment. [Figure 2] This is a block diagram showing an example configuration of the matching support device according to the embodiment. [Figure 3] This figure shows an example of an image displayed in the matching support device of the embodiment. [Figure 4] This figure shows an example of an image displayed in the matching support device of the embodiment. [Figure 5] This figure shows an example of an image displayed in the matching support device of the embodiment. [Figure 6] This figure shows an example of an image displayed in the matching support device of the embodiment. [Figure 7] This figure shows an example of an image displayed in the matching support device of the embodiment. [Figure 8] This figure shows an example of an image displayed in the matching support device of the embodiment. [Figure 9] This figure shows an example of an image displayed in the matching support device of the embodiment. [Figure 10] This figure shows an example of an image displayed in the matching support device of the embodiment. [Figure 11] This figure shows an example of an image displayed in the matching support device of the embodiment. [Figure 12] This figure shows an example of an image displayed in the matching support device of the embodiment. [Figure 13] This figure shows an example of an image displayed in the matching support device of the embodiment. [Figure 14] This is a sequence diagram showing the processing flow of the matching support system in the embodiment. [Figure 15] This is a sequence diagram showing the processing flow of the matching support system in the embodiment. [Modes for carrying out the invention]

[0011] Embodiments of the present invention will be described below with reference to the drawings.

[0012] (Regarding Matching Support System 1) The matching support system 1 is a system that matches requesters and supporters. Here, the requesters are businesses, local governments, individuals, etc. who have issues (needs) for which they want to receive support. The supporters are businesses, local governments, individuals, etc. who can provide support (seeds) for the issues that the requesters have. In the following description, a case will be described as an example where an educational institution such as a school as a requester requests a local company or the like as a supporter to implement workplace experience and class support, etc. which are issues that the school has. However, it is not limited to this. For example, this embodiment can be applied to a case where a food bank as a requester requests support from a local government or the like that stocks disaster supplies with a short expiration date.

[0013] FIG. 1 is a diagram showing a configuration example of the matching support system 1 according to an embodiment of the present invention. The matching support system 1 includes a matching support device 10, a plurality of supporter terminals 20 (supporter terminals 20-1, 20-2, 20-3,...), and a plurality of requester terminals 30 (requester terminals 30-1, 30-2, 30-3,...). In the matching support system 1, each of the matching support device 10, the supporter terminal 20, and the requester terminal 30 is connected via a communication network NW. The communication network NW is, for example, an information communication network such as a LAN (Local Area Network), a WAN (Wide Area Network), or the Internet. The information communication network may be a wired or wireless network, or a combination thereof.

[0014] The supporter terminal 20 is a computer operated by an educational institution such as a school as a supporter. As the supporter terminal 20, for example, a personal computer (PC), a smartphone, a tablet terminal, etc. can be applied. The supporter terminal 20 is communicably connected to the matching support device 10 via the communication network NW.

[0015] The client terminal 30 is a computer operated by a company or other organization acting as a client. For example, a PC, smartphone, or tablet device can be used as the client terminal 30. The supporter terminal 20 is connected to the matching support device 10 via a communication network NW.

[0016] In this embodiment, the matching service provided by the matching support system 1 is a web service provided via a web browser. The supporter terminal 20 accesses a web page indicated by a predetermined URL in response to the supporter's operation, and registers as a supporter according to the user registration page indicated on the accessed web page. As a result, the supporter is registered as a user who requests support through the matching service provided by the matching support system 1. The client terminal 30 accesses a web page indicated by a predetermined URL in response to the client's operation, and registers as a client according to the user registration page indicated on the accessed web page. As a result, the client is registered as a user who provides support through the matching service provided by the matching support system 1.

[0017] The matching support device 10 is a computer that provides matching services. The matching support device 10 can be, for example, a PC, an on-premise server, or a cloud server. The matching support device 10 is connected to the supporter terminal 20 and the requester terminal 30 via a communication network NW.

[0018] Requests for workplace experience programs and academic support are not unconditionally accepted by all companies; some companies are cooperative, while others are not. Furthermore, schools need to ensure that students can participate in workplace experience programs and academic support programs with peace of mind. Therefore, in the past, responses were made by making inquiries based on personal connections between school officials and company officials. As a result, it often became necessary to rely on the personal relationships and negotiation skills of school officials, which could lead to disparities in the quality of workplace experience and classroom support among schools. On the other hand, even if there are companies that want to contribute to the community, they are often unaware that workplace experience programs are offered at schools, or even if they are aware of such programs, they are unaware of when and how these programs are decided upon. As a result, even if companies have the desire to contribute to the community, they do not have the opportunity to offer this, and companies lose the opportunity for local students to learn about local businesses, which in turn leads to lost opportunities for local employment and employment in the area where students are returning to work.

[0019] In response to this, the matching support device 10 matches the requester (school, etc.) with a supporter who can provide the support they wish to receive. The matching support device 10 also matches the supporter (company, etc.) with a supporter who can provide the support they wish to receive. Specifically, the matching support device 10 receives requests for work experience and classroom support from clients (schools, etc.), displays the received requests in a list, and allows local supporters (companies, etc.) to view and search for them. This allows supporters (companies, etc.) to understand what kind of cooperation clients (schools, etc.) are requesting, and if there is a request in an area where they can help, they can propose support for that request. In this way, the matching support device 10 can match clients with supporters who can provide the support they are able to offer. Furthermore, the matching support device 10 accepts support from supporters (companies, etc.) who wish to contribute to the local community and society, displays the accepted support in a list, and allows requesters (schools, etc.) to view and search for it. This allows requesters (schools, etc.) to understand what areas local supporters (companies, etc.) can potentially support them, and if there is support that matches what the requester (school, etc.) wants, they can request that support. In this way, the matching support device 10 can match supporters with the content of the request made by the requester.

[0020] (Regarding the matching support device 10) The matching support device 10 will be described using Figures 2 to 13. Figure 2 is a block diagram showing an example configuration of the matching support device according to the embodiment. Figures 3 to 13 are diagrams showing examples of images of web pages displayed in the matching support device according to the embodiment.

[0021] As shown in Figure 2, the matching support device 10 includes, for example, a case reception unit 101, a search support unit 102, an adjustment support unit 103, a status management unit 104, a display control unit 105, a support information storage unit 106, a request information storage unit 107, and a matching information storage unit 108. The case reception unit 101 accepts registration of support content by supporters and registration of request content by requesters. The search support unit 102 provides support for searching for support content and request content. The adjustment support unit 103 supports the adjustment work carried out between the matched supporter and the requester. The status management unit 104 manages the status indicating the progress of the adjustment work carried out between the matched supporter and the requester. The display control unit 105 displays the web page provided by the matching service (for example, the images shown in Figures 3 to 13) on the supporter terminal 20 or the requester terminal 30. The support information storage unit 106 stores information indicating the support content registered by the supporter. The request information storage unit 107 stores information indicating the details of the request registered by the requester. The matching information storage unit 108 stores information such as the exchange of information regarding coordination work that takes place between the matched supporter and the requester.

[0022] The display control unit 105 transmits information regarding support and requests between the supporter terminal 20 and the requester terminal 30 by displaying a web page provided by the matching service.

[0023] Figure 3 shows an example of the matching service's My Page, which is displayed as a web page on the supporter terminal 20 after a user registers as a supporter. Display fields 20A, 20B, and 20C are shown on this My Page. For example, when a supporter operates the supporter terminal 20 and logs into the matching service, the web page shown in Figure 3 is displayed on the supporter terminal 20 via the display control unit 105 of the matching support device 10. Display area 20A shows tabs. In this diagram, an example of a supporter's My Page is shown, so display area 20A shows the following tabs: My Page, Register Support Details, View Local Support Details, View Requests from Schools, View Matching List, and View / Send Messages. When the "My Page" tab in this display area 20A is clicked, information indicating that a click has been made is sent from the supporter terminal 20 to the matching support device 10. Based on the information received from the supporter terminal 20 (information indicating that a click has been made), the matching support device 10, via the display control unit 105, displays the My Page screen shown in Figure 3 on the supporter terminal 20. Display area 20B shows new information. New information indicates newly notified support or request details. In this diagram, an example of the supporter's My Page is shown, so the request details notified by the requester (school) are displayed as new information. Display area 20C shows the progress status. This progress information indicates the progress of the coordination work being carried out between the matched supporter and the client. This diagram shows an example of the supporter's My Page display, showing the progress of the coordination work between the supporter and the matched client (school). This progress status will be explained in more detail later.

[0024] Furthermore, the My Page of the requester terminal 30, which has registered as a user as a requester, will display a My Page that is equivalent to that in Figure 3, but is centered on the requester (not the supporter). Specifically, in display field 20A#, which corresponds to display field 20A in Figure 3, the tabs for My Page, "Register Request Details", "View Local Support Details", "View Request Details from Schools", "View Matching List", and "View / Send Messages" are displayed. In addition, in display field 20B#, which corresponds to display field 20B in Figure 3, support details notified by supporters (companies) are displayed as new information.

[0025] The case reception unit 101 accepts registration of support details from supporters. In response to the supporter's operation to register the support details, the case reception unit 101 displays a registration screen for registering the support details on the supporter terminal 20 via the display control unit 105. The supporter terminal 20 inputs the support details according to the registration screen based on the supporter's operation and transmits information indicating the entered support details to the matching support device 10. The matching support device 10 receives the support details from the supporter terminal 20. The case reception unit 101 accepts the registration of support details from the supporter by acquiring the support details received by the matching support device 10 from the supporter terminal 20.

[0026] Figure 4 shows an example of a registration screen, which is a web page displayed on the supporter terminal 20 of a user who has registered as a supporter, for registering support details. This registration screen displays display fields 20A and 20D, and operation button B1. When the "Register support details" tab in display area 20A is clicked, information indicating that a click has been made is sent from the supporter terminal 20 to the matching support device 10. Based on the information received from the supporter terminal 20 (information indicating that a click has been made), the matching support device 10, via the display control unit 105, displays the registration screen shown in Figure 4 on the supporter terminal 20. Display area 20D shows a list of support services registered by the supporter. Display area 20D visually displays the support ID, main category, subcategory, support title, target grade level, implementation format, unavailable times / dates, display expiration date (start date, end date), and operation details for each registered support service. The support ID is the identifying information for the support service. The main category and subcategory indicate the category of the support service. The support title is the text set by the supporter as the title of the support service. The target grade level indicates the grade level for which the support service will be provided if it is classroom support. The implementation format, if the support service is classroom support, indicates the format of implementation, specifically whether it will be online, in-person (real-world), or video. Unavailable times / dates indicate the times or dates when the supporter cannot provide the service. The display expiration date (start date, end date) indicates the deadline for posting the request. Icons are provided for editing, copying, and deleting. When the support ID displayed in display area 20D is clicked, details of the support corresponding to the clicked support ID will be displayed. When the edit icon is clicked in the display area 20D, a screen for editing the support content corresponding to the clicked field is displayed, and the support content can be edited from this screen. When the copy icon is clicked, the support content corresponding to the clicked field is copied. When the delete icon is clicked, the support content corresponding to the clicked field is deleted. Operation button B1 is used to register a new support service. When operation button B1 is clicked, a settings screen for configuring the new support service to be registered will appear in a separate window (for example, a modal window) on top of the registration screen shown in Figure 4.

[0027] Figure 5 shows an example of screen W1 (a settings screen for configuring newly registered support content) that appears when operation button B1 in Figure 4 is clicked. This screen W1 has setting fields for the items shown in the list of support content in display field 20D in Figure 4. In this diagram, screen W1 has settings fields for setting the main category, subcategory, support title, display expiration date (start date, end date), icon image, summary, target grade level, etc. Of these, the main category, subcategory, support title, display expiration date (start date, end date), and target grade level correspond to the items shown in the list of support content in display field 20D in Figure 4. For example, when a major or minor category item is clicked in this diagram, options for the clicked item are displayed. For instance, options corresponding to the major category include work experience, classroom support, and other. Options corresponding to the minor category are displayed based on the selection made in the major category. For example, if "classroom support" is selected as the major category, options corresponding to the minor category include SDGs, career education, programming, and local exploration. The selected options are then reflected in the major and minor categories in display area 20D of Figure 4. Furthermore, in this diagram, the item for the target grade level has checkboxes corresponding to each grade level. The grade levels checked in these checkboxes are reflected in the target grade level in display column 20D of Figure 4. Although not shown in this diagram, screen W1 is also provided with setting fields for items such as the implementation format, unimplementable time / date, and display validity period (start date, end date) shown in display field 20D in Figure 4. The implementation format and dates / times set here are reflected in the implementation format, unimplementable time / date, and display validity period (start date, end date) in display field 20D in Figure 4. Screen W1 includes a settings field for setting icon images, allowing users to set icon images corresponding to the type of support provided. The icon images set here will be displayed in the display fields 20B and 20C shown in Figure 3, for example, in association with the type of support (or request). Screen W1 has a settings field for configuring the overview, where an overview corresponding to the support content can be entered. The overview entered here will be reflected in the details of the support content that are displayed when, for example, the support ID displayed in display field 20D shown in Figure 4 is clicked.

[0028] Thus, the case reception unit 101 provides a setting field on screen W1 (a setting screen for setting the support details to be newly registered) for setting items, such as categories (in this case, major categories and minor categories) and target grade levels. This setting field has predefined options. The case reception unit 101 is configured to register the setting items of the request when an option corresponding to the setting field is selected. This allows supporters to register the setting items of the request simply by selecting an option, saving them the effort of inputting information. Furthermore, by having users select setting items from a list of options, the setting items of the request can be limited to one of the pre-prepared options. Therefore, when viewing a list of requests, it is easy to understand what category the request belongs to, or which grade level the request is for.

[0029] Furthermore, the case reception unit 101 accepts the registration of request details by the requester. In response to the requester's operation to register the request details, the case reception unit 101 displays a registration screen for registering the request details on the requester terminal 30 via the display control unit 105. The requester terminal 30 inputs the request details according to the registration screen based on the requester's operation and transmits information indicating the entered request details to the matching support device 10. The matching support device 10 receives the request details from the requester terminal 30. The case reception unit 101 accepts the registration of request details by the requester by acquiring the request details received by the matching support device 10 from the requester terminal 30.

[0030] On the client terminal 30, which has registered as a user requesting the service, a registration screen is displayed that is equivalent to Figures 4 and 5, but with the client (not the supporter) as the main focus, titled "Register Request Details". Specifically, in display field 20A#, which corresponds to display field 20A in Figure 4, a tab titled "Register Request Details" is displayed. When this "Register Request Details" tab is clicked, the "Register Request Details" screen, which corresponds to the registration screen in Figure 4, is displayed on the client terminal 30. On this "Register Request Details" screen, the display field 20D# corresponding to display field 20D in Figure 4 displays a list of the request details registered by the requester. Furthermore, on the "Register Request Details" screen, clicking operation button B1#, which corresponds to operation button B1 in Figure 4, displays a settings screen for setting the new request details. This settings screen is equivalent to screen W1 in Figure 5, but it includes setting items and fields corresponding to the request details (not the support details). The setting items corresponding to the request details are the same as the setting items shown on screen W1 in Figure 5, and include fields for inputting or setting major category, minor category, request title, display expiration date (start date, end date), icon image, summary, target grade level, etc. Of these, the major category, minor category, display expiration date (start date, end date), icon image, and target grade level are equivalent to the setting items shown on screen W1 in Figure 5. The request title is set and displayed by the requester. The summary is set and displayed by the requester. The information entered here will be reflected in the list of requests on the "Register Request Details" screen, which corresponds to the registration screen in Figure 4.

[0031] The search support unit 102 provides assistance in searching for support details and request details. The search support unit 102 also provides a viewing screen that displays a list of support registered by supporters and requests registered by requesters.

[0032] Figure 6 shows an example of a viewing screen that displays a list of support registered by supporters. This viewing screen displays display fields 20A and 20E, a search box KW, and an operation button B2. When the "View local support details" tab in display area 20A is clicked, information indicating that a click has been made is sent from the supporter terminal 20 to the matching support device 10. Based on the information received from the supporter terminal 20 (information indicating that a click has been made), the matching support device 10 displays the browsing screen shown in Figure 6 on the supporter terminal 20 via the display control unit 105. Display area 20E shows a list of support services registered by each regional supporter (not just the logged-in supporter). Display area 20E displays information corresponding to the support services registered by each regional supporter, such as an icon image, main category, and support title. The icon image, main category, and support title displayed here are the same as those set in screen W1 in Figure 5. When any of the icon images, main categories, or request titles displayed in display area 20E are clicked, the details of the clicked request will be displayed. The search box KW is a screen for setting search criteria when searching the list of support services displayed in display area 20E. The search criteria set in this search box KW are configured to use the settings items set on screen W1 in Figure 5 as search criteria. In other words, search criteria are set by selecting all or some of the items such as category, target grade level, and implementation method as search criteria. For example, when the "Select Category" item is clicked in the search box KW, the options set in the major category on screen W1 in Figure 5 (such as work experience, classroom support, and others) are displayed as choices for the clicked item. If "Classroom Support" is selected as the category for the search criteria, checkboxes corresponding to each of the options set in the minor category (such as SDGs, career education, programming, and local exploration) are displayed as search criteria. The items checked in these checkboxes are set as search criteria. Operation button B2 is used to search for support that matches the search criteria from a list of support. When operation button B2 is clicked, the search support unit 102 extracts support that matches the search criteria set in the search window KW from the list of support displayed in the display area 20E, and displays the extracted results in the display area 20E. For example, suppose the search criteria include selecting "Classroom Support" as the category and checking the checkbox corresponding to "SDGs". In this case, when registering support content, the search support unit 102 extracts support where "Classroom Support" is selected as the major category and "SDGs" is selected as the minor category on screen W1 in Figure 5 as search results, and displays the extracted results in display field 20E.

[0033] Figure 7 shows an example of a viewing screen that displays a list of requests registered by clients. This viewing screen displays display fields 20A and 20F, a search box KW, and an operation button B3. When the "View requests from schools" tab in display area 20A is clicked, information indicating that a click has been made is sent from the support terminal 20 to the matching support device 10. Based on the information received from the support terminal 20 (information indicating that a click has been made), the matching support device 10, via the display control unit 105, displays the browsing screen shown in Figure 7 on the support terminal 20. Display area 20F shows a list of requests registered by the requester (school). Display area 20F displays information corresponding to the requests registered by the requester (school), such as an icon image, main category, and request title. The icon image, main category, and request title displayed here are the same as those set on the screen corresponding to screen W1 in Figure 5, which is displayed on the requester terminal 30 registered as the requester. When any of the icon images, main categories, or request titles displayed in the 20F display area are clicked, the details of the clicked support will be displayed. The search box KW is a screen for setting search criteria when searching the list of support services displayed in display area 20F. The search criteria set in this search box KW are configured to use the settings items that are set when registering a request. In other words, the search criteria are set by selecting all or some of the items such as category, target grade level, and implementation method.

[0034] The search box keyword shown in Figure 7 is equivalent to the search box keyword shown in Figure 6. In other words, the search conditions are set by selecting all or some of the items that are set during registration, such as category, target grade level, and implementation method. Here, the case reception unit 101 sets the same settings (category, target grade level, implementation method, etc.) as registration settings for both support and requests. The search support unit 102 uses the same settings as registration settings as search conditions. Therefore, supporters can search for requests using the settings they have set for their registered support content as search criteria. Requesters can also search for support using the settings they have set for their registered request content as search criteria. In other words, supporters can easily search for requests with the same conditions as the support content they have registered, making it easy for supporters to find requests they can support. Similarly, requesters can easily search for support with the same conditions as the request they have registered, making it easy for them to find supporters who can provide that support. Consequently, it becomes easier for supporters or requesters to find a suitable partner, facilitating matching.

[0035] The Coordination Support Unit 103 assists with the coordination work that takes place between matched supporters and clients. In this embodiment, matching is established when a client requests support based on the support content registered in the matching service, or when a support provider proposes support based on the requested content.

[0036] Figure 8 shows an example of a details screen displaying the details of a request. This details screen displays display fields 20A and 20G, and operation button B4. In the browsing screen shown in Figure 7, when any of the icon image, main category, or request title displayed in display area 20F is clicked, the details screen shown in this figure will be displayed as details of the clicked support. Display area 20G shows details of the support provided. Operation button B4 is used by supporters to propose support in response to a request. When operation button B4 is clicked, a proposal screen is displayed where supporters can propose support in response to the request.

[0037] Figure 9 shows an example of a suggestion screen that appears when operation button B4 in Figure 8 is clicked. This suggestion screen displays display fields 20A and 20H, and operation button B5. Display area 20H shows input fields for entering the proposed support services and a remarks field. Supporters enter the support services in the input fields. In addition, if there is anything they would like to convey to the client, they should enter it in the remarks field. Operation button B5 is used to confirm the proposed support services. When operation button B5 is clicked, a confirmation screen for reviewing the proposed support services will be displayed. This confirmation screen displays the support details proposed by the supporter (the content entered in the input field and remarks field in display area 20H) along with an operation button labeled "Propose Support," etc. The supporter reviews the support details displayed on the confirmation screen, and if the support details are satisfactory, clicks the operation button indicated by "Propose Support" or similar. Upon clicking this operation button, the matching support device 10 notifies the requester (school, etc.) who registered the request details that support has been proposed for. This notification is sent, for example, to the requester's pre-registered email address. This completes the matching process.

[0038] Furthermore, in the viewing screen shown in Figure 6, supporters can propose support in response to requests registered in the matching service, via screens equivalent to those in Figures 8 and 9. Specifically, when any of the icon image, main category, or request title displayed in display area 20E in Figure 6 is clicked, a details screen showing the details of the clicked request is displayed in a format equivalent to that of Figure 8. On this details screen, when operation button B4#, which corresponds to operation button B4 in Figure 8, is clicked, a request screen (corresponding to the proposal screen shown in Figure 9) is displayed for requesting support for the support content. This request screen displays an input field for entering the requested support, a remarks field, and an operation button B5# (corresponding to operation button B5 in Figure 9) for confirming the request. When operation button B5# is clicked, a confirmation screen for the request is displayed. The confirmation screen displays the content entered in the remarks field and an operation button labeled "Request Support," etc. The requester reviews the request details displayed on the confirmation screen, and if the request details are acceptable, clicks the operation button indicated by "Request Support" or similar. Upon clicking this operation button, the matching support device 10 notifies the supporter (company, etc.) who registered the support details for which the support request has been made that a request for support has been made. This notification is sent, for example, to the supporter's pre-registered email address. This completes the matching process.

[0039] The Coordination Support Unit 103 generates a chat room where the matched client and supporter can exchange messages in a conversational format, in response to a successful match.

[0040] In this context, school staff may not have an accurate understanding of the actual situation of local businesses, such as what kinds of businesses exist or what kinds of work they do. Furthermore, the purpose of workplace experience programs is simply for students to gain experience in different occupations and jobs, and to interact with working people. Therefore, the specific occupations and job content can be left to the school's discretion. For this reason, when approaching local businesses about conducting workplace experience programs, it is likely that the priority should be to first confirm whether or not they are willing to cooperate. For example, when registering a request from a school, it is likely that the title of the request could be something like, "We are looking for local businesses in the medical and welfare fields that would be willing to accept students for workplace experience," without specifying the details of the request too much, thus broadly appealing to businesses for cooperation. In such cases, after a school is matched with a company willing to cooperate, it is necessary to adjust the schedule and content of the work experience, taking into account the intentions of the other party (the supporter), and decide on the specific implementation details, such as whether students will experience caregiving, nursing, or medical office administration. Such adjustments are made through communication between school teachers and company representatives using telephone, fax, email, etc. School teachers and company representatives are often unfamiliar with such adjustments, and the burden is significant as they have to perform these adjustment tasks in addition to their regular duties.

[0041] As a countermeasure, the coordination support unit 103 generates a chat room for message exchange in a conversational format after the requester and supporter have been matched, and displays the coordination screen, including the generated chat room, on the supporter terminal 20 and the requester terminal 30 via the display control unit 105. This makes it easy for the requester and supporter to coordinate the details of the case, such as the specific content and implementation date and time of the occupation or work that the student will experience, using the chat room. Furthermore, in this embodiment, a status is set for each case. Here, the status is an indicator that shows the progress of the case (request or support content), or more specifically, the progress of the coordination work carried out between the requester and the support provider. The status management unit 104 sets a status for each case and displays the status set for that case along with the corresponding chat room. This makes it easier for school teachers and company representatives who are unfamiliar with coordination to coordinate cases in the matching support device 10 of this embodiment, and also makes it easier to understand the status of the coordination work. For example, in workplace experience programs, students in the target grade level are often divided into several groups, and each group is arranged to experience different workplaces. In such cases, teachers need to coordinate with multiple companies that are cooperating with the workplace experience program at the same time. Even in such situations, by setting a status for each case and displaying the status along with the corresponding chat room, it becomes easier to understand the status of coordination with each of the multiple companies. Therefore, even if a teacher who is unfamiliar with coordination has to manage coordination with multiple companies at the same time, the coordination work becomes easier.

[0042] Figure 10 shows an example of the adjustment screen. This adjustment screen displays display fields 20A, 20J-20M, and operation buttons B6-B7. When the "View / Send Message" tab in display area 20A is clicked, information indicating that a click has been made is sent from the supporter terminal 20 to the matching support device 10. Based on the information received from the supporter terminal 20 (information indicating that a click has been made), the matching support device 10 displays the adjustment screen shown in Figure 10 on the supporter terminal 20 via the display control unit 105.

[0043] Display area 20J shows a list of projects that supporters who are logged into the matching service have matched with clients. The projects displayed here include both projects that clients have requested in response to support registered by supporters, and projects that supporters have proposed in response to requests registered by clients. Display area 20J, like display area 20E in Figure 6 and display area 20F in Figure 7, shows an icon image corresponding to the case, a major category, and a support title (or request title). Additionally, some of the cases shown in display area 20J have a number enclosed in a circle to the right of the case description. This number indicates the number of unread messages that have not been viewed by the supporter logged into the matching service. In this context, since the chat room is a space where supporters and clients exchange messages in a dialogue format, the presence of unread messages on the supporter's end indicates that a message has been received from the client, the person they are communicating with, but the supporter has not yet seen or read it. In other words, in display area 20J, cases with numbers enclosed in a circle indicate that the client has notified the supporter of some questions or matters to be confirmed, and the client is waiting for the supporter's response. For example, the supporter should prioritize checking the chat room for cases with numbers enclosed in a circle and respond to the supporter's questions or matters to be confirmed. This allows the supporter to proceed with the coordination work that is awaiting the supporter's response. On the other hand, in display area 20J, cases where no number enclosed in a circle is shown indicate that the supporter has not yet responded to the questions or inquiries made by the requester. For example, in the chat room for cases where no number enclosed in a circle is shown, the supporter can send reminders about the questions or inquiries made by the requester previously, or send notifications to check when a response is expected. This allows the requester to be informed that the supporter is waiting for a response. When any of the project icon image, main category, or request title in display area 20J is clicked, the chat room corresponding to the clicked project will be displayed in display area 20K.

[0044] Display area 20K displays the chat room corresponding to the selected case from the list of cases displayed in display area 20J. For example, on the left side of the chat room, messages notified by the person you are talking to in the chat room, in this case the requester (school, etc.), are displayed. At the bottom of the display area 20K, there is an input field for entering a message to notify the other party in the chat room, and an operation button B6. Operation button B6 is used to send the message entered in this input field. The supporter enters the message in the input field and clicks operation button B6. This sends the message in the chat room. In this chat room, you can send not only messages (text) but also electronic files such as images, audio, tables, and documents. Supporters attach electronic files by clicking the icon (showing a plus sign) located between the input field and operation button B6, and then clicking operation button B6. This sends the attached electronic file within the chat room.

[0045] Display area 20L shows the details of the project corresponding to the chat room displayed in display area 20K. For example, display area 20L displays the request title registered by the requester, the support details proposed by the supporter, etc.

[0046] The display area 20M shows the status. For example, the status includes options such as "Requested," "Proposed," "Under Negotiation," "Implementation Decided," "Implemented," and "Completed."

[0047] "Request in Progress" is a status indicating that a requester (school, etc.) has requested support from a supporter (company, etc.) for the support services they have registered. The "Request in Progress" status indicates that a request has been made for the support services registered by the supporter (company, etc.), and the requester (school, etc.) is waiting for a response from the supporter (company, etc.). For example, a request for support is made by the requester terminal 30 for a case (support content) registered in the matching service. In response to this request from the requester terminal 30, the coordination support unit 103 generates a chat room in which the requester who requested support for the case (support content) and the supporter who registered the case (support content) can communicate. The status management unit 104 sets a status of "Request in Progress" for the case (support content) corresponding to the chat room generated here.

[0048] In this diagram, the chat room displayed in display field 20K only shows messages notified by the requester (school, etc.). In other words, the requester (school, etc.) has requested support for the support content registered by the supporter (company, etc.), but the supporter (company, etc.) has not yet responded to the request. In this case, the status management unit 104 sets the status of the case corresponding to this chat room to "Request in Progress". The coordination support unit 103 displays the status "Request in Progress" in display field 20M via the display control unit 105.

[0049] "Proposal in Progress" is a status indicating that a supporter (company, etc.) has proposed support for a request registered by the requester (school, etc.). The "Proposal in Progress" status indicates that support has been proposed for a request registered by the requester (school, etc.), and the supporter (company, etc.) is waiting for a response from the requester (school, etc.). For example, a supporter terminal 20 makes a support proposal for a case (request) registered in the matching service. In response to this support proposal from the supporter terminal 20, the coordination support unit 103 generates a chat room in which the supporter who proposed support for the case (request) and the requester who registered the case (request) can communicate. The status management unit 104 sets a status of "Proposal in Progress" for the case (request) corresponding to the chat room generated here.

[0050] "Under Negotiation" is a status indicating that the supporter (company, etc.) and the requester (school, etc.) are in the process of negotiating the details of the project (request or support). The "Under Negotiation" status indicates that the supporter (company, etc.) has responded to a request from the school (requester) regarding the support content registered by the supporter (company, etc.), or that the requester (school, etc.) has responded to a support proposal from the supporter (company, etc.) regarding the request content registered by the requester (school, etc.), but the specific details of the support are still undecided (under negotiation) and a decision to implement has not yet been made. For example, when a supporter proposes support in response to a request registered on the matching service, and the requester sends a message to the supporter via a chat room, the status management unit 104 sets the status to "In Progress" for the case corresponding to the chat room from which the message was sent. Alternatively, when a client requests assistance based on the support details registered in the matching service, and the support provider sends a message to the client via the chat room, the status management unit 104 sets the status to "In Progress" for the case corresponding to the chat room from which the message was sent.

[0051] "Implementation Decision" is a status that indicates that the specific support details (or requested details) for the project have been finalized and the project has been approved for implementation. The status management unit 104 sets the status of "Implementation Decision" for a project when the setting items described later (for example, the implementation date) have been set for that project. "Completed" is a status indicating that the implementation of a project has been completed. The status management unit 104 sets the status to "Completed" for a project, for example, when the project's implementation date has passed. "Completed" is a status indicating that a project has been completed. The status management unit 104 sets the status to "Completed" for a project based on whether the client (and / or supporter) has responded to the questionnaire after the project has been completed.

[0052] Figure 11 shows an example of the adjustment screen when the case corresponding to the chat room is in the "adjustment" stage. This adjustment screen displays display fields 20A, 20J-20M, and operation buttons B6-B7.

[0053] The chat room in display field 20K shows that a message MG has been sent from the supporter (company, etc.) in response to a notification from the requester (school, etc.) shown on the left. In response to the sending of this message MG, the coordination support unit 103 changes the status of this case from "Requested" to "In Adjustment." The coordination support unit 103, via the display control unit 105, displays the status "In Adjustment" in the display field 20M shown in this figure.

[0054] In Figures 10 and 11, operation button B7 is used to change the status of the project from "Under Adjustment" to "Implementation Decision". When operation button B7 is clicked, a settings screen will appear showing the settings items and their corresponding fields for changing the status from "Under Adjustment" to "Implementation Decision".

[0055] Figure 12 shows an example of screen W2 (a settings screen for configuring settings to change the status from "Adjusting" to "Implementation Decision") that appears when operation button B7 in Figures 10 and 11 is clicked. This screen W2 shows the settings items and their corresponding settings fields. In this diagram, screen W2 has a setting item called Implementation Date (start date and end date), and a setting field is provided for setting this setting item, Implementation Date (start date and end date). When the Implementation Date (start date and end date) is set in this setting field and the operation button labeled "Register" is clicked, the status management unit 104 changes the status of this case from "Under Adjustment" to "Implementation Decision". In this case, the status management unit 104 sets the status of the case corresponding to this talk room to "Implementation Decision". The adjustment support unit 103 displays the status "Implementation Decision" in the display field 20M via the display control unit 105.

[0056] Figure 13 shows an example of the adjustment screen that appears when the operation button labeled "Register" on screen W2 in Figure 12 is clicked. On this adjustment screen, the status "Implementation Decision" is displayed in display field 20M.

[0057] In this way, the status management unit 104 advances the current status to the next stage when predetermined settings are made according to the status of the case. Furthermore, by providing an operation button B7 and displaying screen W2 when operation button B7 is clicked, the status management unit 104 presents the settings that need to be made to advance the current status to the next stage, making them accessible from the chat room. As a result, in the matching support device 10 of this embodiment, it becomes easy for school teachers and company personnel who are unfamiliar with coordination to grasp the progress of the case coordination work and to have a common understanding of what needs to be decided to advance to the next stage.

[0058] The above describes the settings that must be configured to move from the "Under Adjustment" status to the next stage, "Implementation Decision," but the system is not limited to these settings. The system may be configured so that each status has its own set of settings required to move to the next status. In this case, the status management unit 104 will display the settings that must be configured to move to the next status, according to the status of the case, in a way that can be viewed from the chat room.

[0059] Furthermore, the settings required to proceed to the next status may be arbitrarily set according to the content of the request or support. For example, if the request or support is to conduct a work experience program, the date of implementation, the location of the program, the meeting time, the duration of the program, the number of participants, and the compensation may be set as settings that need to be specifically decided before the work experience program is implemented.

[0060] Here, we will explain the progress status shown in display column 20C of Figure 3. The progress status displayed in display column 20C corresponds to display column 20J in Figure 10, and shows the progress status of each project that the supporter has matched with the client. Display area 20C shows the progress of each project according to items such as title, message, status, implementation date, and memo. The title field displays the icon image, main category, and support title (or request title) corresponding to the project, similar to display area 20J in Figure 10. The message field shows the beginning of the latest message received in the chat room corresponding to the project. The number enclosed in a circle to the right of the displayed message indicates the number of unread messages that the supporter has not yet viewed. The status is the status displayed in display area 20M in Figures 10, 11, and 13. The implementation date is the project implementation date set on screen W2 in Figure 12. The memo field is where the supporter can write notes as needed. By displaying the progress status as shown in display field 20C on the user's page, supporters can easily grasp at a glance the details of each project they have matched with a client, its progress status, and whether they are currently waiting for a response from the client or whether they are waiting for a response from the client.

[0061] The functional units of the matching support device 10 (including the case reception unit 101, search support unit 102, adjustment support unit 103, status management unit 104, and display control unit 105) are realized by a hardware processor such as a CPU (Central Processing Unit) in the matching support device 10 executing a program (software). Some or all of these functional units may be realized by hardware (including circuitry) such as LSI (Large Scale Integration), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), and GPU (Graphics Processing Unit), or by the cooperation of software and hardware. The program may be stored in advance in a storage device such as an HDD (Hard Disk Drive), SSD (Solid State Drive), or flash memory (a storage device with a non-transient storage medium), or it may be stored in a removable storage medium such as a DVD or CD-ROM (a non-transient storage medium) and installed when the storage medium is inserted into a drive device.

[0062] (Regarding the processing flow) Figures 14 and 15 are sequence diagrams showing the processing flow of the matching support system 1. Figure 14 shows the processing flow when a case is registered by a supporter registering the support details. Figure 15 shows the processing flow when a case is registered by a requester registering the request details.

[0063] As shown in Figure 14, the supporter terminal 20 transmits the support details to the matching support device 10 and registers the support details with the matching service (step S10). The matching support device 10 displays the registered support details on the matching service's web page so that the supporter terminal 20 and the requester terminal 30 can view them (step S11). For example, the matching support device 10 displays the registered support details on the display area 20A of the matching service's web page, such as the supporter's "My Page" new arrivals screen, the requester's "Register a Request" support list screen, and the "View Regional Support Details" support list screen. The requester terminal 30 performs an operation to request the support displayed on the matching service's web page and sends the support request to the matching support device 10 (step S12). When the matching support device 10 receives a request for support from the requester terminal 30, it notifies the supporter terminal 20 of this fact and generates a chat room for the case (the case related to the support details registered by the supporter in step S10) (step S13). When the matching support device 10 generates the chat room, it sets the status of the case to "Requested" and displays the status "Requested" along with the chat room on the web page (step S14). In response to a request for assistance from the requesting terminal 30, the supporter terminal 20 sends a response to the request for assistance via the case's chat room (step S15). The matching support device 10 sets the status of the case to "In Adjustment" in response to a response being sent via the chat room, and displays the status "In Adjustment" along with the chat room on the web page (step S16). In the chat room, the supporter and the requester communicate through dialogue to coordinate the project. The matching support device 10 determines whether a setting item (a setting item to change the status from "Under Adjustment" to "Implementation Decision") has been set (step S17), and if this setting item has been set, it sets the status of the project to "Implementation Decision" and displays the status "Implementation Decision" on the web page along with the chat room (step S18).

[0064] As shown in Figure 15, the requester terminal 30 sends the request details to the matching support device 10 and registers the request details with the matching service (step S20). The matching support device 10 displays the registered request details on the matching service's web page so that the supporter terminal 20 and the requester terminal 30 can view them (step S21). For example, the matching support device 10 displays the registered request details on the display area 20A of the matching service's web page, such as the supporter's "My Page" new arrivals screen, the requester's "Register a Request" request list screen, and the "View Requests from Schools" request list screen. The supporter terminal 20 performs an operation to propose support for the request displayed on the matching service's web page and sends the proposal to the matching support device 10 (step S22). When the matching support device 10 receives a support proposal from the supporter terminal 20, it notifies the requester terminal 30 of this fact and generates a chat room for the case (the case related to the request details registered by the requester in step S20) (step S23). When the matching support device 10 generates the chat room, it sets the status of the case to "Proposal in Progress" and displays the status "Proposal in Progress" along with the chat room on the web page (step S24). In response to the supporter terminal 20 making a support offer, the requester terminal 30 sends a response to the support offer via the case's chat room (step S25). The processes shown in steps S26 to S28 are equivalent to the processes shown in steps S16 to S18 in Figure 14, so their explanation is omitted.

[0065] As described above, the matching support system 1 of this embodiment is a system that matches a client who has a problem they want support for with a supporter who can provide support for that problem. The matching support system 1 comprises an adjustment support unit 103 and a status management unit 104. The adjustment support unit 103 generates a talk room in which the client and the supporter exchange messages in a dialogue format. The status management unit 104 displays the status of the adjustment work being carried out by the client and the supporter along with the talk room. As a result, in the matching support system 1 of this embodiment, a talk room is generated when a client and a supporter are matched, so that the matched client and supporter can perform adjustments after matching. By using a dialogue-style talk room, it becomes easy to perform adjustment work related to the matched case. In addition, by displaying the status along with the talk room, both parties can easily recognize the current status of the adjustment work for the case.

[0066] Furthermore, in the matching support system 1 of the embodiment, the coordination support unit 103 generates a talk room in response to a case registered by either the requester or the supporter. This allows the matching support system 1 of the embodiment to smoothly carry out coordination work in cases where it is difficult to execute the case simply by matching with a partner, such as work experience or classroom support, and where specific coordination with the matched partner is necessary.

[0067] Furthermore, in the matching support system 1 of the embodiment, the status management unit 104 advances the status to the next stage when predetermined setting items are set according to the status. As a result, in the matching support system 1 of the embodiment, even if the supporter and the client are unfamiliar with negotiation, negotiations can proceed with the aim of creating a situation where both parties have a common understanding and can set the setting items.

[0068] Furthermore, the matching support system 1 of this embodiment is further equipped with a case reception unit 101. The case reception unit 101 registers a case in accordance with the selection of an option provided in a predetermined setting item. As a result, the matching support system 1 of this embodiment can reduce the effort required for registration compared to sequentially inputting the support details (or request details). In addition, by limiting the setting items for the request details (or request details) to one of the pre-prepared options, a third party viewing the request details (or request details) can easily understand the request details (or request details).

[0069] Furthermore, the matching support system 1 of the embodiment further includes a search support unit 102. The search support unit 102 displays the options of the setting items used when registering a case as search items for searching for cases from the list of cases registered by the case reception unit 101. As a result, the matching support system 1 of the embodiment can link the setting items used when registering a case with the search items for cases, making it easy for the searcher to set search conditions, and reducing the processing load related to the search compared to a search method that performs a full-text search on text freely entered by the supporter (for example, the overview on screen W1 in Figure 5).

[0070] Furthermore, in the matching support system 1 of the embodiment, the requester requests support for workplace experience or classroom support in education-related businesses, and the supporter proposes support for workplace experience or classroom support. Implementing projects such as workplace experience or classroom support, where the purpose is to allow students to experience occupations and jobs, and the specific occupations or jobs they will experience are at the discretion of the provider, is difficult because it requires various adjustments. In contrast, the matching support system 1 of the embodiment simplifies this process by generating chat rooms and managing statuses, enabling workplace experience or classroom support to be realized even when handled by school teachers or company representatives who are unfamiliar with negotiations.

[0071] Furthermore, the matching support system 1 of this embodiment includes a supporter terminal 20, a client terminal 30, and a matching support device 10. This allows the matching support system 1 of this embodiment to match supporters and clients, thereby facilitating coordination work related to the case.

[0072] The matching support system 1 and matching support device 10 in the above-described embodiment may be implemented in whole or in part by a computer. In that case, the program for implementing this function may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be loaded into the computer system and executed. The term "computer system" here includes hardware such as the OS and peripheral devices. The term "computer-readable recording medium" refers to portable media such as flexible disks, magneto-optical disks, ROMs, CD-ROMs, and storage devices such as hard disks built into the computer system. Furthermore, the term "computer-readable recording medium" may also include those that dynamically hold programs for a short period of time, such as communication lines used when transmitting programs via networks such as the Internet or communication lines such as telephone lines, and those that hold programs for a certain period of time, such as volatile memory inside the computer system that acts as a server or client in such cases. The program may be for implementing a part of the functions described above, or it may be a program that can implement the functions described above in combination with a program already recorded in the computer system, or it may be implemented using a programmable logic device such as an FPGA.

[0073] Although embodiments of this invention have been described in detail above with reference to the drawings, the specific configuration is not limited to these embodiments and includes designs and the like that do not depart from the spirit of this invention. [Explanation of Symbols]

[0074] 1…Matching support system 10…Matching support device 101...Case Reception Department 102…Search Support Department 103…Coordination Support Department 104...Status Management Department 105...Display Control Unit 20... Supporter terminal 30...Client terminal

Claims

1. A matching support system that connects clients who have issues they need support with supporters who can provide support for those issues, A coordination support unit generates a talk room in which the client and the supporter exchange messages in a dialogue format, Along with the aforementioned talk room, a status management unit that displays the status indicating the progress of the coordination work performed by the requester and the supporter, A matching support system equipped with the following features.

2. The aforementioned coordination support unit generates the aforementioned talk room in response to a case registered by either the requester or the supporter. The matching support system according to claim 1.

3. The status management unit advances the status to the next stage when a predetermined setting item is set according to the status, and makes the setting item available for reference from the talk room. The matching support system according to claim 1.

4. The case reception department registers cases based on the selection of options provided in the predetermined settings. The matching support system according to claim 1, further comprising:

5. A search support unit displays the options as selectable search criteria for searching for cases from a list of cases registered by the aforementioned case reception unit, and extracts cases from the list corresponding to the selected options. The matching support system according to claim 4, further comprising:

6. The aforementioned client requested support for workplace experience or classroom support in education-related projects. The supporter proposes support for the aforementioned workplace experience or the aforementioned classroom support. The matching support system according to claim 1.

7. A client terminal operated by the aforementioned client, A supporter terminal operated by the aforementioned supporter, A matching support device having a coordination support unit and a status management unit, which is connected to the aforementioned client terminal and the aforementioned supporter terminal in a manner that enables communication with them. Equipped with, The matching support system according to claim 1.

8. A computer-based matching support method used in a matching support system that matches clients who have a problem they want support for with supporters who can provide support for that problem, The Coordination Support Department creates a chat room in which the requester and the supporter can exchange messages in a dialogue format. The status management unit displays the status, along with the chat room, indicating the progress of the coordination work performed by the requester and the supporter. Matching support methods.

9. The computer used in the matching support system, which matches clients with issues they need help with with supporters who can provide assistance with those issues, A chat room is created in which the client and the supporter can exchange messages in a dialogue format. Along with the aforementioned chat room, the status of the coordination work performed by the client and the supporter will be displayed. program.

Images