Recruitment support system control method, recruitment support system, and program

Abstract

To improve convenience in an invitation procedure between users using an invitation code. [Solution] A control method for a recruitment support system using an invitation code, comprising: an issuing step of issuing an invitation code in response to a request from a first user; a generating step of generating a service screen including a display description indicating information of the invitation code; a notifying step of notifying the first user of address information of the service screen; and a display control step of, after a message including the address information is posted to a communication tool based on instructions from the first user, identifiably displaying information of the invitation code available to the second user by referring to the display description of the service screen when displaying the message on the communication tool based on instructions from a second user.

Description

[Technical field]

[0001] The present invention relates to a control method for a recruitment support system, a recruitment support system, and a program. [Background technology]

[0002] In recent years, SNS (Social Networking Service) tools for communicating among multiple users via a network have become widespread. SNS are used, for example, in configurations using web browsers or in configurations of applications (hereinafter also referred to as "apps") installed on user terminals.

[0003] Also, matching services that match multiple users are becoming popular. Matching services are used for various purposes, one of which is a job-seeking / career change service that matches job seekers with companies with openings. In matching services, users who are already using the service invite other users to use the service. In such cases, the invitee may enter the shared invitation code on a registration screen or other screen as the inviter information.

[0004] For example, Patent Document 1 describes a configuration in which an invitation system issues an invitation code in response to a request from an inviting party, and the invited party is newly registered in a group by inputting the invitation code. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Patent Publication No. 2021-108040 Summary of the Invention [Problem to be solved by the invention]

[0006] For example, consider a situation where an invitee inputs an invitation code. When inputting the invitation code, it is difficult to know whether the invitation code is valid or not, which is an obstacle to input. As a result, it may deprive the opportunity for new users of the service, and there is a need to further improve the convenience of using the invitation code. For example, when an inviter shares a URL (Uniform Resource Locator) of a registration screen for registering a new user with an invitee via an SNS, there is a need to easily check an invitation code that can be input to the registration screen on the SNS screen. Patent Document 1 does not fully consider such points.

[0007] In view of the above problems, an object of the present invention is to improve the convenience of an invitation procedure between users using an invitation code. [Means for solving the problem]

[0008] In order to solve the above problems, one aspect of the present invention has the following configuration. That is, a method for controlling a recruitment support system using an invitation code, comprising: an issuing step of issuing an invitation code in response to a request from the first user; a generating step of generating a service screen including a display description showing information of the invitation code; a notification step of notifying the first user of address information of the service screen; a display control step of identifiably displaying information on the invitation code available to the second user by referring to a display description of the service screen when displaying the message on the communication tool based on an instruction from a second user after the message including the address information is posted to the communication tool based on an instruction from the first user; has.

[0009] Another aspect of the present invention has the following configuration. That is, a recruitment support system using an invitation code, an issuing unit that issues an invitation code in response to a request from a first user; a generating unit for generating a service screen including a display description showing information of the invitation code; a notification unit that notifies the first user of address information of the service screen; having After a message including the address information is posted to a communication tool based on instructions from the first user, when the message is displayed on the communication tool based on instructions from a second user, the display description of the service screen is referenced so that information about the invitation code available to the second user is identifiably displayed.

[0010] Another aspect of the present invention has the following configuration: Computer, an issuing unit that issues an invitation code in response to a request from the first user; a generation unit for generating a service screen including a display description showing information of the invitation code; a notification unit that notifies the first user of address information of the service screen; Functioning as a After a message including the address information is posted to a communication tool based on instructions from the first user, when the message is displayed on the communication tool based on instructions from a second user, the display description of the service screen is referenced so that information about the invitation code available to the second user is identifiably displayed. Effect of the Invention

[0011] According to the present invention, it is possible to improve the convenience of the invitation procedure between users using an invitation code. [Brief description of the drawings]

[0012] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a recruitment support system according to a first embodiment of the present invention. [Diagram 2] FIG. 2 is a functional block diagram showing a server device according to the first embodiment of the present invention; [Diagram 3] FIG. 1 is a functional block diagram showing a user terminal according to a first embodiment of the present invention; [Figure 4] FIG. 1 is a sequence diagram showing an invitation process according to a first embodiment of the present invention; [Diagram 5] 1 is a flowchart of a registration process according to a first embodiment of the present invention; [Figure 6] FIG. 1 is an example showing a configuration example of a UI screen according to a first embodiment of the present invention; [Figure 7] FIG. 1 is an example showing a configuration example of a UI screen according to a first embodiment of the present invention; [Figure 8] FIG. 11 is a sequence diagram showing an invitation process according to a modified example of the present invention. [Figure 9] Flowchart of application process according to a modified example of the present invention DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] Hereinafter, the embodiment for carrying out the present invention will be described with reference to the drawings. Note that the embodiment described below is one embodiment for explaining the present invention, and is not intended to be interpreted as limiting the present invention, and all configurations described in each embodiment are not necessarily essential configurations for solving the problems of the present invention. Also, in each drawing, the same components are given the same reference numbers to indicate their correspondence. Note that in order to avoid unnecessary redundancy and to facilitate understanding by those skilled in the art, some of the explanations may be omitted or simplified. For example, detailed explanations of already well-known matters or duplicate explanations of substantially the same configurations may be omitted.

[0014] First Embodiment [System Configuration] FIG. 1 is a schematic diagram showing an example of the configuration of a recruitment support system (information processing system) according to a first embodiment of the present invention. In this embodiment, a recruitment matching service that connects job seekers with companies offering jobs will be described as an example, but the present invention is not limited to this. The present invention is applicable to any service to which the invitation code, which is a feature of the present invention, and the configuration related to displaying and inputting the invitation code can be applied. In this embodiment, service collaboration using an SNS is assumed, but the type of SNS is not particularly limited, and any SNS tool may be used as long as the configuration specific to the present invention, which will be described later, functions.

[0015] The recruitment support system 1 includes a server device 100, a plurality of user terminals 200, and a hiring company system 300. The devices constituting the recruitment support system 1 are configured to be able to communicate with each other via a network NW.

[0016] The server device 100 is a device for providing various functions provided by the recruitment support system 1 to the user terminal 200. The server device 100 provides applications for recruitment support to each of the user terminals 200 and the recruiting company system 300. The server device 100 also manages user information and recruitment information registered via the user terminal 200 and the recruiting company system 300. Note that the server device 100 may be configured to provide some or all of the functions described below on the user terminal 200 side or the recruiting company system 300 side that can be linked via the network NW. The server device 100 may be configured on-premise using a general-purpose computer such as a workstation or a personal computer, or may be logically realized by cloud computing. In this embodiment, for convenience of explanation, one server device 100 is illustrated as an example, but the present invention is not limited to this, and may be multiple units, and may have servers with different roles such as an authentication server and a database server.

[0017] The user terminal 200 is an operation terminal used by a user. The user terminal 200 may be configured, for example, by an information processing device such as a personal computer, a tablet terminal, a smartphone, or a wearable terminal. The user terminal 200 provides the user with a Web service provided by the server device 100 and functions of applications installed and operated in the user terminal 200. In the example of FIG. 1, three user terminals 200a, 200b, and 200c are illustrated, but more user terminals may be used. The configurations of the multiple user terminals 200 may be different from each other or may be the same. Here, for convenience, they will be collectively described as the user terminal 200. Note that when it is necessary to explain each user terminal separately, the subscripts (a, b, . . . ) will be added.

[0018] The hiring company system 300 is an external system that functions in cooperation with the server device 100 via the network NW. The hiring company system 300 is used, for example, by a hiring company to register job information in the server device 100 and to receive information on job applications from the server device 100. Although only one hiring company system 300 is shown, multiple systems may be connected depending on the hiring company.

[0019] The network NW is composed of the Internet, an intranet, a wireless LAN (Local Area Network), a WAN (Wide Area Network), etc. The communication standard and wired / wireless of the network NW are not particularly limited, and the network NW may be composed of a combination of multiple communication standards.

[0020] 2 is a block diagram showing an example of a functional configuration of the server device 100 according to this embodiment. The server device 100 includes a control unit 110, a storage unit 120, and a communication unit 130. Each unit is configured to be able to communicate with each other via an internal bus or the like.

[0021] The control unit 110 controls the operation of the server device 100. The control unit 110 is composed of, for example, a CPU (Central Processing Unit) and a GPU (Graphics Processing Unit), and provides various functions by reading and executing various programs and data stored in the storage unit 120. The control unit 110 functions as, for example, a data management unit 111, a display control unit 112, a user information registration unit 113, a job information registration unit 114, a screen generation unit 115, an invitation code issuing unit 116, a job application unit 117, an incentive derivation unit 118, and a communication control unit 119.

[0022] The data management unit 111 manages various data in cooperation with the storage unit 120, and provides, registers, updates, etc., various data in response to requests. The display control unit 112 controls the display of a UI (User Interface) screen displayed on the user terminal 200 side based on a user operation performed via the user terminal 200. The display control unit 112 also controls the user terminal 200 to provide various UI screens. An example of the configuration of a UI screen according to this embodiment will be described later.

[0023] The user information registration unit 113 accepts registration of users of the recruitment support service according to this embodiment and registers them in each DB. The user information may include information about the user input when using the service, as well as information when applying for a job.

[0024] In the recruitment support service according to this embodiment, the recruitment information registration unit 114 receives recruitment information from the recruiting company system 300 and registers it in each DB. The recruitment information may include information on the application status, hiring results, and the like, in addition to conditions related to the recruitment.

[0025] The screen generating unit 115 generates various screens according to the present embodiment. Although details will be described later, various screens are generated including information of the invitation code. In response to a request from a user, the invitation code issuing unit 116 issues an invitation code that can be used to invite other users. Examples of the use of the invitation code will be described later.

[0026] The job application unit 117 performs application processing for a job in response to a request from a user. The application processing here includes, for example, notifying the hiring company that issued the job and providing information about the job seeker. The job application unit 117 also provides the application results to the user terminal 200 of the user who is a job seeker.

[0027] The incentive derivation unit 118 derives an incentive that can be obtained when various processes are performed using the invitation code. The incentive here is not particularly limited, but may be, for example, points that can be used when using a specific service, or a license that allows the use of a specific service. The communication control unit 119 controls communication with an external device (for example, the user terminal 200 or the hiring company system 300) and transmits and receives data.

[0028] The storage unit 120 is a storage device for storing programs and data for executing various control processes and each function in the control unit 110. The storage unit 120 is composed of volatile / non-volatile storage devices such as a RAM (Random Access Memory), a ROM (Read Only Memory), a HDD (Hard disk Drive), and a flash memory. The storage unit 120 includes a database (hereinafter, referred to as DB) for managing data corresponding to the functions described below.

[0029] The user information DB121 manages various user information of users who use the recruitment support service according to this embodiment. The user information may include attribute information such as the user's name, date of birth, address, and qualifications, as well as history information related to job applications and hiring, and information related to incentives. The company information DB122 manages various company information of hiring companies who use the recruitment support service according to this embodiment. The company information may include attribute information such as the name, base, and service details of the hiring company, as well as evaluation information (such as word of mouth) and advertising information about the hiring company.

[0030] The employment information DB 123 manages employment information registered by companies offering jobs. The employment information may include information about companies offering jobs, as well as employment conditions and application status. The screen DB 124 manages various screen information generated by the screen generation unit 115 for display on the user terminal 200, etc. Examples of the generated screens will be described later. The invitation code DB 125 manages issued invitation codes.

[0031] 2 may be integrated into one, or one DB may be divided into multiple DBs. Also, a part of the DB may be managed by a device other than the server device 100.

[0032] The communication unit 130 is a communication interface for communicating with an external device via the network NW. The communication unit 130 may be configured to be compatible with a plurality of communication standards depending on the configuration of the network NW.

[0033] 3 is a block diagram showing an example of a functional configuration of a user terminal 200 according to this embodiment. The user terminal 200 includes a control unit 210, a storage unit 220, a communication unit 230, an operation unit 240, a display unit 250, and an external IF (Interface) 260.

[0034] The control unit 210 is responsible for controlling the operation of the user terminal 200. The control unit 210 is composed of, for example, a CPU (Central Processing Unit) and a GPU (Graphics Processing Unit), and provides various functions by reading and executing various programs and data stored in the storage unit 220.

[0035] The storage unit 220 is a storage device for storing programs and data for executing various control processes and each function of the control unit 210. The storage unit 220 is composed of a volatile / non-volatile storage device such as a random access memory (RAM), a read only memory (ROM), a hard disk drive (HDD), and a flash memory. For example, the storage unit 220 stores a recruitment support application 221 for using the recruitment support service according to the present embodiment, an SNS application 222 for using an SNS, and a data group 223 including various data. The control unit 210 can provide various services by starting and operating each application. Note that there are various types of SNS, such as LINE (registered trademark), Instagram (registered trademark), X, and Facebook (registered trademark), but they are not particularly limited.

[0036] The communication unit 230 is a communication interface for communicating with an external device via the network NW. The communication unit 230 may be configured to be compatible with a plurality of communication standards depending on the configuration of the network NW.

[0037] The operation unit 240 is an interface for accepting operations from a user of the user terminal 200. The operation unit 240 may be composed of a mouse, a keyboard, and the like. The display unit 250 is an interface for displaying various screens and is composed of a display, and the like. A touch panel display in which the operation unit 240 and the display unit 250 are integrated may be used. The external IF 260 is an interface for connecting to various devices, and may be, for example, a connection interface with an imaging unit (not shown) for capturing images, sensors for acquiring predetermined information, and the like.

[0038] [Processing sequence] In this embodiment, an example is shown assuming that a user (for convenience, referred to as "user A") who is using the recruitment support service invites another unregistered user (for convenience, referred to as "user B") to register for the service. Also assume that user A and user B each use an SNS and are capable of communicating with each other via an SNS application 222. Here, the explanation will be given assuming that user A owns user terminal 200a and user B owns user terminal 200b.

[0039] In addition, in the recruitment support service according to this embodiment, user A invites user B using an invitation code. User B enters the invitation code when registering, and an incentive is given to user A and / or user B. Here, since it is assumed that the invitation code is used in the registration process, it is also referred to as a "registration invitation code."

[0040] In step S401, the user terminal 200a starts the recruitment support application 221 based on a user instruction, and accepts a registration invitation instruction. An example of a screen for accepting a registration invitation instruction will be described later with reference to FIG.

[0041] In step S402, based on the registration invitation instruction accepted in step S401, the user terminal 200a transmits a registration invitation request to the server device 100. The request at this time may include identification information for uniquely identifying user A.

[0042] In step S403, the server device 100 receives the registration invitation request from the user terminal 200a. Furthermore, the server device 100 identifies user A, who is the sender, based on the information included in the received registration invitation request.

[0043] In step S404, the server device 100 issues a new registration invitation code in association with the user A. The registration invitation code may be set with an expiration date, a number of times it can be used, an upper limit on issuance, etc. Also, if there is a registration invitation code already issued in association with the user A and it is usable, it may be used.

[0044] In step S405, the server device 100 generates a registration screen including a display description indicating a registration invitation code. In this embodiment, OGP (Open Graph Protocol) is used as the display description here. Since OGP is a known method, detailed description will be omitted here, but it is a method for displaying information described in OGP on an SNS screen when a URL (Uniform Resource Locator) of a web page is posted on an SNS. In other words, in this embodiment, when a message including the URL of a registration screen of a business support service is posted on an SNS to encourage new users to use the service, a screen is generated to display information of a registration invitation code that can be entered on the registration screen.

[0045] In step S406, the server device 100 notifies the user terminal 200a of the URL of the registration screen generated in step S405.

[0046] In step S407, the user terminal 200a acquires the URL of the registration screen from the server device 100, and presents it to the user A. An example of the display screen will be described later with reference to FIG.

[0047] In step S408, the user terminal 200a posts a message including the URL acquired in step S407 to the SNS. Posting to the SNS is performed by starting the SNS application 222 provided in the user terminal 200a and specifying a destination. Here, it will be explained that the message is posted by specifying user B as an invitee to encourage new use of the recruitment support service according to this embodiment. The content of the posted message is not particularly limited, but it is assumed that it includes at least the above URL. Note that the destination of a message posted on the SNS is not limited to one person, and it may be sent to multiple recipients at the same time, or may be sent to a group to which multiple people belong.

[0048] In step S409, the user terminal 200b displays the message posted by the user A via the SNS application 222 provided in the user terminal 200b based on an instruction from the user B. As described above, when the message is displayed via the SNS application 222, a thumbnail of the registration screen indicated by the URL included in the message and a registration invitation code indicated by the OGP included in the registration screen are displayed. An example of the display screen will be described later with reference to FIG. 7(a).

[0049] In step S410, the user terminal 200b accesses the URL displayed on the SNS application using a browser (not shown) or the like based on a user instruction, thereby making a request to display a registration screen.

[0050] In step S411, the server device 100 receives a request to access the registration screen from the user terminal 200b.

[0051] In step S412, the server device 100 provides a corresponding registration screen to the user terminal 200b in response to the access request in step S411.

[0052] In step S413, user terminal 200b displays the registration screen provided by server device 100 on a browser (not shown) or the like. Furthermore, user terminal 200b accepts input of registration information on the registration screen based on an operation by user B. At this time, user B can visually confirm the available registration invitation code displayed on SNS application 222 in step S409 and input it into the registration screen. In addition, control may be performed so as to prompt download and installation of recruitment support application 221 in conjunction with user registration for the recruitment support service according to this embodiment.

[0053] In step S414, the user terminal 200b transmits to the server device 100 the registration information regarding the user B that was input in step S413.

[0054] In step S415, the server device 100 performs registration processing for the user B based on the registration information transmitted from the user terminal 200b. Details of this processing will be described in detail with reference to Fig. 5. After that, the processing of the server device 100 proceeds to step S416.

[0055] In step S416, the server device 100 notifies each of the user terminals 200a and 200b of the result of the registration process in step S415.

[0056] In step S417, the user terminal 200b displays the information notified in step S416 from the server device 100. The display here may be performed via a registration screen or via the recruitment support application 221.

[0057] In step S418, the user terminal 200a displays the information notified in step S416 from the server device 100. This display may be performed via the recruitment support application 221.

[0058] (Registration process) 5 is a flowchart of a user registration process by the server device 100 according to this embodiment. This process corresponds to step S415 in FIG.

[0059] In step S501, the server device 100 receives registration information input from the user terminal 200b via a registration screen. At this time, it is assumed that a registration invitation code is specified in the registration information.

[0060] In step S502, the server device 100 stores the received registration information in each DB.

[0061] In step S503, the server device 100 invalidates the registration invitation code designated in the registration information after the registration invitation code is used. If the registration invitation code can be used multiple times, the number of times it can be used may be reduced by one.

[0062] In step S504, the server device 100 updates the display description on the registration screen where the registration information was entered, that is, the OGP description, in response to the use of the registration invitation code. In other words, when a character string including the URL of the registration screen is posted on an SNS, the registration screen is updated so that it is possible to identify that the registration invitation code that has been used is invalid. The update here may involve rewriting the OGP description so that the registration invitation code that has been used is hidden, or may involve rewriting it to clearly indicate that it has been used.

[0063] In step S505, the server device 100 derives an incentive for the inviting user A and / or the invited user B in response to the new registration of the user B. The contents of the incentive may be different between the invited side and the inviting side, or may be the same. Alternatively, the incentive may be given to only one of the sides. The contents of the incentive may be predefined, or may be switched according to a predetermined calculation formula or conditions defined.

[0064] In step S506, the server device 100 registers the incentive derived in step S505 in association with information about the user to whom the incentive is to be given.

[0065] In step S507, the server device 100 generates notification information for notifying the inviting user A that user B has newly registered. At this time, if an incentive is to be given to user A, the server device 100 may also notify the user A of the incentive information derived in step S505.

[0066] In step S508, the server device 100 generates notification information for notifying the newly registered user B of the registration result. At this time, if an incentive is to be given to user B, the server device 100 may also notify the user B of the result of the registration. Then, this processing flow ends, and the process of the server device 100 proceeds to step S416 in FIG. 4.

[0067] [UI screen example] A configuration example of a UI screen according to this embodiment will be described. Each UI screen described in this embodiment is displayed, for example, on the display unit 250 of the user terminal 200 and operated by the user. In this embodiment, the UI screen is appropriately switched based on the user's operation. Here, the description focuses on the functions according to this embodiment, but each UI screen may be provided with even more functions.

[0068] Fig. 6 shows an example of the configuration of a UI screen displayed on user terminal 200a held by user A, who is the inviting party. Fig. 6(a) is, for example, a registration invitation screen 600 by the recruitment support app 221 installed in user terminal 200a, and is a screen for inviting other users to register as users in the recruitment support service according to this embodiment. For example, user A operates the recruitment support app 221, causing the registration invitation screen 600 to be displayed. The registration invitation screen 600 is displayed, for example, in the process of step S401 in Fig. 4.

[0069] When the registration invitation button 601 is pressed on the registration invitation screen 600, a registration screen for user registration and an invitation code are requested to be generated. This executes the invitation request in the process of step S402 in Fig. 4. The URL of the registration screen (specifically, the registration screen 710 shown in Fig. 7(b)) and the registration invitation code generated as a result are notified to the user terminal 200a and are displayed in the registration screen URL 602 and invitation code 603 fields on the registration invitation screen 600.

[0070] The SNS link buttons 604 to 606 are buttons for launching the corresponding SNS application. Here, an example of three types of SNS is shown, and the SNS link buttons 604 to 606 correspond to SNS_A, SNS_B, and SNS_C, respectively. Note that the number of buttons may vary depending on the SNS used by the user. The close button 607 is a button used to close the registration invitation screen 600.

[0071] FIG. 6(b) shows an example of the configuration of an SNS screen 610 by the SNS application 222 installed in the user terminal 200a, for example. The SNS screen 610 is displayed, for example, in the process of step S408. Here, as shown in the destination 611, user B is specified as the communication partner of the SNS. The communication partner may be specified by specifying a group to which a plurality of users belong. By inputting a desired message in the message input area 613 and pressing the post button 614, the posted content is displayed in the message display area 612. The posted content in the message display area 612 can also be confirmed by the communication partner via the SNS application 222 of the user terminal 200 owned by the communication partner. In order to improve visibility, in the message display area 612, the message posted by the user is displayed right-justified, and the message posted by the communication partner is displayed left-justified. The display mode of the message is not limited to this.

[0072] In this example, the character string "https: / / AAAAA.bbbb / ccccccccccccccc" displayed in the registration screen URL 602 in FIG. 6(a) is entered in the message input area 613, and the post button 614 is pressed, whereby a message including the character string is posted. As a result, a message 615 is displayed in the message display area 612. Furthermore, the SNS application 222 refers to the registration screen, which is the destination indicated by the URL included in the message 615, and displays information indicated in the description of the OGP of the registration screen as a display item 616. Here, a thumbnail image 617 of the registration screen and a list 618 of available registration invitation codes are displayed in the display item 616. The list 618 may include, in addition to available registration invitation codes, registration invitation codes that have already become unavailable in an identifiable manner. Here, three available registration invitation codes "AAAcode", "BBBcode", and "CCCcode" are illustrated. In addition, in the list 618, the registration invitation codes are displayed with a hashtag (#), but the display manner is not limited to this and may be other display manners.

[0073] 7 shows an example of the configuration of a UI screen displayed on the user terminal 200b held by user B, who is the invitee. FIG. 7(a) shows an example of the configuration of an SNS screen 700 by the SNS application 222 installed on the user terminal 200b, for example. The SNS screen 700 is displayed, for example, in the process of step S409 in FIG. 4. Here, as shown in destination 701, user A is specified as the communication partner on the SNS. As with the SNS screen 610 in FIG. 6(b), a desired message is entered in a message input area 703, and the post button 704 is pressed, whereby the posted content is displayed in a message display area 702.

[0074] In this example, as shown in FIG. 6(b), a message including the character string "https: / / AAAAA.bbbb / ccccccccccccccc" is posted by user A, and is displayed as message 705 in message display area 702. Furthermore, SNS application 222 of user terminal 200b refers to information on a registration screen that is the destination indicated by the URL included in message 705, and displays information indicated by the description of the OGP of the registration screen as display item 706. Here, a thumbnail image 707 of the registration screen and a list 708 of available registration invitation codes are displayed in display item 706. The display form here is the same as that in FIG. 6(b).

[0075] 7(b) shows an example of the configuration of a registration screen 710 for newly registering a user, which in this example is displayed by accessing the URL indicated by "https: / / AAAAA.bbbb / ccccccccccccccc". The registration screen 710 may be displayed, for example, via a Web browser (not shown) provided on the user terminal 200b owned by user B. The registration screen 710 is displayed, for example, in the process of step S413 in FIG. 4.

[0076] The registration screen 710 is provided with a plurality of input areas for inputting various information when a user registers in the recruitment support service according to this embodiment. The information to be input when registering a user is not particularly limited, and may include, for example, an invitation code, an inviter's name, a name, an account number, and recruitment conditions. In the input area 711, it is possible to input available registration invitation codes shown in the list 708 displayed on the SNS screen 700 of FIG. 7(a). For example, user B checks available registration invitation codes by referring to the SNS screen 700, and inputs them in the input area 711 of the registration screen 710. In addition, since the registration invitation code is linked to the inviting user, for example, in response to inputting the registration invitation code in the input area 711, the information of the inviter may be automatically displayed in the input area 712. In addition, user B inputs information such as a name in the input area 713, etc. After input, by pressing the new registration button 714, the server device 100 performs the registration process. In addition, when the cancel button 715 is pressed, the input is discarded and the registration is interrupted.

[0077] As described above, this embodiment makes it possible to improve the convenience of the invitation procedure between users using the invitation code. In particular, when an invitation to register for a specific service is made via SNS, the invited user can easily check the available invitation code, and can smoothly perform the input process related to the invitation.

[0078] [Variations] In the above embodiment, an embodiment assuming a case where a user newly registers to a specific service has been described. The features of the present invention can also be applied to other situations where an invitation code is used. Therefore, as a modification of this embodiment, a modification applied to a case where a recruitment support service invites applications for a job posting from a certain recruiting company will be described. For example, a case where multiple users simultaneously apply for one job posting can be mentioned.

[0079] The configuration of the system is omitted here because it is the same as that described with reference to Figures 1 to 3. Also, this modified example and the above-mentioned first embodiment are not mutually exclusive, and both may be implemented in the same system.

[0080] [Processing sequence] In this modification, an example is shown in which user A and user B, who are using the recruiting support service, invite user B to a job offer. It is also assumed that user A and user B each use an SNS and can communicate with each other via SNS application 222. The recruiting support application 221 may provide a communication function that allows service registrants to communicate with each other. In this case, the communication function provided by the recruiting support application 221 may be used instead of the SNS application 222 to execute the sequence described below. In this modification, the description will be given assuming that user A owns user terminal 200a and user B owns user terminal 200b.

[0081] In addition, in the recruitment support service according to this modified example, user A invites user B using an invitation code. User B enters the invitation code when applying for a job, and an incentive is given to user A and / or user B. Here, as it is assumed that the invitation code is used in the job application process, it is also referred to as a "recruitment invitation code."

[0082] For example, the server device 100 presents each user with job information registered by companies offering jobs in a list format or the like via the recruitment support application 221. User A may then specify one of the presented job information that meets the desired job requirements as the job to apply for, and perform operations related to application in the recruitment support application 221, thereby causing the following processing sequence to operate. Note that with regard to the job to be applied for, User A, the inviting party, may already be applying or working, or User A and User B, the invited party, may both apply for the job at the same time.

[0083] In step S801, the user terminal 200a accepts a job invitation instruction corresponding to the desired job information based on a user instruction. An example of a screen for accepting the job invitation instruction may be a screen equivalent to the registration invitation screen 600 shown in FIG. 6(a).

[0084] In step S802, based on the job offer invitation instruction received in step S801, the user terminal 200a transmits a job offer invitation request to the server device 100. The job offer invitation request at this time may include identification information for uniquely identifying user A.

[0085] In step S803, the server device 100 receives the job offer invitation request from the user terminal 200a. Furthermore, the server device 100 identifies user A, who is the sender, based on the information included in the received job offer invitation request.

[0086] In step S804, the server device 100 issues a new job offer invitation code in association with the user A. The job offer invitation code may be set with an expiration date, a number of uses, an issuance limit, etc. Also, if there is a job offer invitation code already issued in association with the user A and it is usable, it may be used.

[0087] In step S805, the server device 100 generates a job offer screen (not shown) including a display description indicating the job offer invitation code. In this modification, OGP (Open Graph Protocol) is used as the display description here. In this modification, when a message including the URL of the job offer screen for the job offer is posted on an SNS to encourage user B to apply for the job, a screen is generated to display information about the job offer invitation code that can be entered on the job offer screen.

[0088] In step S806, the server device 100 notifies the user terminal 200a of the URL of the job offer screen generated in step S805.

[0089] In step S807, the user terminal 200a acquires the URL of the job advertisement screen from the server device 100, and presents it to the user A. An example of the display screen may be the same as the registration invitation screen 600 shown in FIG.

[0090] In step S808, the user terminal 200a posts a message including the URL acquired in step S807 to the SNS. Posting to the SNS is performed by starting the SNS application 222 and specifying a destination. The content of the posted message is not particularly limited, but it is assumed that the message includes at least the above URL. Note that the destination of a message posted to an SNS is not limited to one person, and the message may be sent to multiple recipients at the same time, or may be sent to a group to which multiple people belong.

[0091] In step S809, the user terminal 200b displays the message posted by the user A via the SNS application 222 based on an instruction from the user B. As described above, when the message is displayed via the SNS application 222, a thumbnail of the job offer screen indicated by the URL included in the message and a job offer invitation code indicated by the OGP included in the job offer screen are displayed. An example of the display screen may be the same as the SNS screen 700 shown in FIG. 7(a).

[0092] In step S810, the user terminal 200b accesses the URL displayed on the SNS application 222 using a browser (not shown) or the like based on a user instruction, thereby making a request to display a job offer screen.

[0093] In step S811, the server device 100 receives a request to access the job offer screen from the user terminal 200b.

[0094] In step S812, the server device 100 provides the corresponding job offer screen to the user terminal 200b in response to the access request in step S811.

[0095] In step S813, the user terminal 200b displays the job offer screen provided by the server device 100 on a browser (not shown) or the like. Furthermore, the user terminal 200b accepts input of application information on the job offer screen based on the operation of user B. At this time, user B can visually confirm the available job offer invitation code displayed on the SNS application 222 in step S809 and input it into the job offer screen.

[0096] In step S814, the user terminal 200b transmits to the server device 100 the application information regarding the user B that was input in step S813.

[0097] In step S815, the server device 100 processes the application of user B to the desired job offer based on the application information transmitted from the user terminal 200b. The details of this process will be described in detail with reference to Fig. 9. After that, the process of the server device 100 proceeds to step S816.

[0098] In step S816, the server device 100 notifies each of the user terminals 200a and 200b of the result of the application process in step S815.

[0099] In step S817, the user terminal 200b displays the information notified in step S816 from the server device 100. This display may be performed via the recruitment support application 221.

[0100] In step S818, the user terminal 200a displays the information notified in step S816 from the server device 100. This display may be performed via the recruitment support application 221.

[0101] (Application processing) 9 is a flowchart of a user application process performed by the server device 100 according to this modification. This process corresponds to step S815 in FIG.

[0102] In step S901, the server device 100 receives application information input from the user terminal 200b via a job offer screen (not shown). At this time, it is assumed that a job offer invitation code is specified in the application information.

[0103] In step S902, the server device 100 stores the received application information in each DB.

[0104] In step S903, the server device 100 transmits the application information to the hiring company system 300 of the hiring company that registered the job information. In response, the hiring company screens the application to determine whether to hire or not based on the job information. The hiring company system 300 then notifies the server device 100 of the screening result according to instructions from the hiring company's staff.

[0105] In step S904, the server device 100 receives the examination result from the hiring company system 300.

[0106] In step S905, the server device 100 determines whether the candidate is accepted based on the screening result received in step S904. If the candidate is accepted (step S905: YES), the process of the server device 100 proceeds to step S906. On the other hand, if the candidate is not accepted (step S905: NO), the process of the server device 100 proceeds to step S910.

[0107] In step S906, the server device 100 invalidates the job offer invitation code specified in the application information when the job offer invitation code is used. If the job offer invitation code can be used multiple times, the number of times it can be used may be reduced by one. In this example, the job offer invitation code is invalidated when the job offer is screened for adoption, but this is not limited to this. For example, the job offer invitation code entered may be invalidated regardless of whether the job offer is adopted or rejected.

[0108] In step S907, the server device 100 updates the display description on the job offer screen where the application information was entered, that is, the OGP description, in response to the use of the job offer invitation code. In other words, when a character string including the URL of the application screen is posted on an SNS, the job offer screen is updated so that it is possible to identify that the job offer invitation code that has been used is invalid. The update here may involve rewriting the OGP description so that the job offer invitation code that has been used is hidden, or it may be rewritten to clearly indicate that it has been used.

[0109] In step S908, the server device 100 derives an incentive for the inviting user A and / or the invited user B in response to the user B being hired for the job offer. The contents of the incentive may be different between the invited party and the inviting party, or may be the same. Also, it may be given to only one of them. The contents of the incentive may be predefined, or may be switched according to a predetermined calculation formula or conditions defined. Also, although this modified example is configured to give an incentive when a user is hired, it may be configured to give some kind of incentive even when the user is not hired.

[0110] In step S909, the server device 100 registers the incentive derived in step S908 in association with information about the user to whom the incentive is to be given.

[0111] In step S910, the server device 100 generates notification information for notifying the inviting user A that user B has applied for the job. At this time, if an incentive is to be given to user A, the server device 100 may also notify the user A of the incentive information derived in step S908. The server device 100 may also notify the user A of the screening result of user B regarding the job.

[0112] In step S911, the server device 100 generates notification information for notifying the invited user B of the application result. At this time, if an incentive is to be given to user B, the server device 100 may also notify the user B of the incentive information derived in step S908. Then, this processing flow ends, and the process of the server device 100 proceeds to step S816 in FIG. 8.

[0113] As described above, this modified example makes it possible to improve the convenience of the invitation procedure between users using invitation codes. In particular, when an invitation to apply for a job is sent via SNS, the invited user can easily check the available invitation codes, and can smoothly input the invitation.

[0114] <Other embodiments> The trigger for invalidating the invitation code is not limited to the above. In addition to use by the invited user as described above, the invitation code may be invalidated based on the expiration date from the issuance of the invitation code, the job status (full capacity exceeded, job expiration date expired), cancellation at the request of the inviting user, rejection of the job offer by the inviting user, etc.

[0115] In the above embodiment, a recruitment support service has been described as an example. However, the present invention is not limited to this, and the features of the present invention can be applied to various services that use an invitation function when the service is via an SNS. Furthermore, the features of the present invention can be applied to application processing that uses an invitation function within the same service.

[0116] In addition, in the present invention, a program or application for realizing the functions of one or more of the above-mentioned embodiments can be supplied to a system or device via a network or a storage medium, etc., and one or more processors in a computer of the system or device can read and execute the program, thereby realizing the present invention.

[0117] Moreover, it may be realized by a circuit that realizes one or more functions (for example, an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA)).

[0118] Although various embodiments have been described above with reference to the drawings, it goes without saying that the present disclosure is not limited to the examples. It is clear to a person skilled in the art that various modifications, corrections, substitutions, additions, deletions, and equivalents may be made within the scope of the claims, and it is understood that these also naturally belong to the technical scope of the present disclosure. In addition, the components in the various embodiments described above may be arbitrarily combined within the scope of the invention.

[0119] Furthermore, in this specification, expressions such as "first" and "second" are used merely for convenience to distinguish from other elements. Therefore, it is not intended to limit the interpretation to a specific component. Therefore, when there are more components, it goes without saying that these expressions may be interpreted appropriately according to the applied configuration.

[0120] As such, the present invention is not limited to the above-described embodiments, and the present invention also contemplates the mutual combination of the various components of the embodiments, as well as modifications and applications by those skilled in the art based on the description in the specification and well-known techniques, and these are included in the scope of protection sought.

[0121] As described above, the present specification discloses the following:

[0122] (Technology 1) A method for controlling a recruitment support system (e.g., 1) using an invitation code, an issuing step of issuing an invitation code in response to a request from the first user; a generating step of generating a service screen including a display description showing information of the invitation code; a notification step of notifying the first user of address information of the service screen; a display control step of identifiably displaying information on the invitation code available to the second user by referring to a display description of the service screen when displaying the message on the communication tool based on an instruction from a second user after the message including the address information is posted to the communication tool based on an instruction from the first user; A control method for a recruitment support system having the above-mentioned features. This configuration makes it possible to improve the convenience of the invitation procedure between users using the invitation code, for example. In particular, when an invitation to a specific service is sent via a communication tool, the invited user can easily check the available invitation code, and can smoothly input the invitation.

[0123] (Technology 2) The invitation code is an invitation code for a new user registration for a recruitment support service provided by the recruitment support system, The control method for a recruitment support system described in Technology 1, wherein the service screen is a registration screen for new user registration and is configured to allow the invitation code to be input. With this configuration, for example, when an invitation to register as a user for a specific service is made via a communication tool, the invited user can easily check the available registration invitation codes, enabling the input process related to registration to be carried out smoothly.

[0124] (Technology 3) The invitation code is an invitation code for applying for a job offered by a job offering support service provided by the job offering support system, The control method for a recruitment support system according to Technology 1 or Technology 2, wherein the service screen is an application screen for applying for a job and is configured to allow the invitation code to be input. With this configuration, for example, when an invitation to apply for a specific job is made via a communication tool, the invited user can easily check the available job invitation codes, enabling the input process related to the job application to be carried out smoothly.

[0125] (Technology 4) A control method for a recruitment support system described in Technology 2 or Technology 3, in which a predetermined incentive is given to at least one of the first user and the second user when the second user uses the invitation code. With this configuration, for example, by making it possible to provide incentives to both the inviter and the invitee using the invitation code, it is possible to encourage the use of the invitation code and further encourage the use of the service.

[0126] (Technology 5) A control method for a recruitment support system described in any one of Technology 2 to Technology 4, wherein the invitation code is invalidated based on any one of use by the second user, a usage deadline, a recruitment status, or cancellation by the first user. With this configuration, for example, it is possible to invalidate the invitation code based on a predetermined condition and prevent abuse of the invitation code.

[0127] (Technology 6) A control method for a recruitment support system according to any one of techniques 1 to 5, wherein the invitation code is issued so that it can be used once or multiple times. With this configuration, for example, it is possible to issue an invitation code that can be used a desired number of times.

[0128] (Technology 7) The method for controlling a recruitment support system according to any one of techniques 1 to 6, wherein the invitation code is issued so that it can be used by one or more people. With this configuration, for example, it is possible to issue an invitation code that can be shared among a desired number of users.

[0129] (Technology 8) A control method for a recruitment support system described in any one of Technology 1 to Technology 7, wherein a display description of the service screen is written so that the invitation code is displayed on the communication tool in list format or hashtag format. With this configuration, for example, the invitation code can be displayed in a list format or hashtag format on a communication tool, thereby improving the visibility of the invitation code.

[0130] (Technology 9) A control method for a recruitment support system described in any one of Technology 1 to Technology 8, wherein a display description of the service screen is written so that only invitation codes available to the second user among the issued invitation codes are displayed on the communication tool. With this configuration, for example, by displaying only invitation codes that can be used on a communication tool, it is possible to improve the visibility of the invitation codes.

[0131] (Technology 10) The control method for a recruitment support system according to any one of Techniques 1 to 9, wherein the communication tool is a social networking service (SNS) tool. This configuration makes it possible to send invitations via SNS tools, for example, and to check available invitation codes on the SNS tools.

[0132] (Technology 11) A control method for a recruitment support system according to any one of Technology 1 to Technology 10, wherein the display description of the service screen is based on OGP (Open Graph Protocol). With this configuration, for example, it is possible to use OGP to generate a screen for displaying available invitation codes on a communication tool.

[0133] (Technology 12) A recruitment support system using an invitation code (e.g., 1, 100), an issuing unit (e.g., 110, 116) that issues an invitation code in response to a request from a first user; A generating unit (e.g., 110, 115) for generating a service screen including a display description showing information of the invitation code; A notification unit (e.g., 110, 112, 119) that notifies the first user of address information of the service screen; having A recruitment support system in which, after a message including the address information is posted to a communication tool based on instructions from the first user, when the message is displayed on the communication tool based on instructions from a second user, information on the invitation code available to the second user is identifiably displayed by referencing a display description of the service screen. This configuration makes it possible to improve the convenience of the invitation procedure between users using the invitation code, for example. In particular, when an invitation to a specific service is sent via a communication tool, the invited user can easily check the available invitation code, and can smoothly input the invitation.

[0134] (Technology 13) A computer (e.g., 100), an issuing unit (e.g., 110, 116) that issues an invitation code in response to a request from a first user; A generating unit (e.g., 110, 115) for generating a service screen including a display description showing information of the invitation code; a notification unit (e.g., 110, 112, 119) that notifies the first user of address information of the service screen; Functioning as a A program which, after a message including the address information is posted to a communication tool based on instructions from the first user, when the message is displayed on the communication tool based on instructions from a second user, references a display description of the service screen to identifiably display information about the invitation code available to the second user. This configuration makes it possible to improve the convenience of the invitation procedure between users using the invitation code, for example. In particular, when an invitation to a specific service is sent via a communication tool, the invited user can easily check the available invitation code, and can smoothly input the invitation. [Industrial Applicability]

[0135] INDUSTRIAL APPLICABILITY The present invention is useful, for example, as an apparatus, system, and method for a service that employs an invitation procedure between users using an invitation code. [Explanation of symbols]

[0136] 1. Recruitment support system (information processing system) 100...Server device 110...Control unit 111…Data Management Department 112...Display control unit 113...User information registration section 114…Job Information Registration Department 115...Screen generation section 116…Invitation Code Issuance Department 117…Job Application Department 118…Incentive Derivation Department 119…Communication control unit 120...Storage section 121...User information DB 122…Company information DB 123…Job information database 124…Screen DB 125…Invitation code DB 130…Communications Department 200 (200a, 200b, 200c) - User terminal 210...Control unit 220...Storage section 221…Recruitment support app 222…SNS app 223...Data group 230…Communications Department 240...Operation unit 250...Display section 260…External IF 300…Recruitment company system

Claims

1. A method for controlling a recruitment support system using an invitation code, comprising: an issuing step of issuing an invitation code in response to a request from the first user; a generating step of generating a service screen including a display description showing information of the invitation code; a notification step of notifying the first user of address information of the service screen; a display control step of identifiably displaying information on the invitation code available to the second user by referring to a display description of the service screen when displaying the message on the communication tool based on an instruction from a second user after the message including the address information is posted to the communication tool based on an instruction from the first user; an update step of updating a display description showing information about the invitation code included in the service screen when the invitation code has been used, so as to show that the invitation code has been used; A control method for a recruitment support system having the above-mentioned features.

2. The invitation code is an invitation code for a new user registration for a recruitment support service provided by the recruitment support system, 2. The method for controlling a recruitment support system according to claim 1, wherein the service screen is a registration screen for new user registration and is configured so that the invitation code can be input.

3. The invitation code is an invitation code for applying for a job offered by a job offering support service provided by the job offering support system, 2. The method for controlling a recruitment support system according to claim 1, wherein the service screen is an application screen for applying for a job and is configured so that the invitation code can be input.

4. 4. The method of claim 2, wherein a predetermined incentive is given to at least one of the first user and the second user when the second user uses the invitation code.

5. 4. The method of claim 2, wherein the invitation code is invalidated based on any one of use by the second user, a usage period, a job status, and cancellation by the first user.

6. 2. The method of claim 1, wherein the invitation code is issued so as to be usable once or multiple times.

7. 2. The method of claim 1, wherein the invitation code is issued so that it can be used by one or more people.

8. 2. The method of claim 1, wherein the display description of the service screen is written so that the invitation code is displayed on the communication tool in a list format or a hashtag format.

9. A method for controlling a recruitment support system as described in claim 1, wherein the display description of the service screen is written so that only invitation codes available to the second user among the issued invitation codes are displayed on the communication tool.

10. 2. The method for controlling a recruitment support system according to claim 1, wherein the communication tool is a social networking service (SNS) tool.

11. 2. The method of claim 1, wherein the display description of the service screen is based on OGP (Open Graph Protocol).

12. A recruitment support system using an invitation code, an issuing unit that issues an invitation code in response to a request from a first user; a generating unit for generating a service screen including a display description showing information of the invitation code; a notification unit that notifies the first user of address information of the service screen; having after a message including the address information is posted to a communication tool based on an instruction from the first user, when the message is displayed on the communication tool based on an instruction from a second user, information on the invitation code available to the second user is identifiably displayed by referring to a display description of the service screen; A recruitment support system in which, when the invitation code is used, the generation unit updates a display description indicating information about the invitation code included on the service screen to indicate that the invitation code has been used.

13. Computer, an issuing unit that issues an invitation code in response to a request from the first user; a generating unit for generating a service screen including a display description showing information of the invitation code; a notification unit that notifies the first user of address information of the service screen; Functioning as a after a message including the address information is posted to a communication tool based on an instruction from the first user, when the message is displayed on the communication tool based on an instruction from a second user, information on the invitation code available to the second user is identifiably displayed by referring to a display description of the service screen; The generation unit is a program that, when the invitation code is used, updates a display description indicating information about the invitation code included on the service screen to indicate that the invitation code has been used.

Images