JP2022188652A - Alliance support system among staff agencies - Google Patents

Abstract

To provide an alliance support system among staff agencies which can support alliance among staff agencies.SOLUTION: The present invention is directed to an alliance support system among staff agencies. The alliance support system among the staff agencies has: a register unit for registering job seeker information in association with a staff agency as a registration source; a storing unit for storing the job seeker information registered by the register unit; a retrieval unit for retrieving the job seeker information stored by the storing unit; an alliance contact unit for receiving a message about predetermined job seeker information sent by other staff agency to the staff agency as the registration source of the job seeker information; a user history management unit for managing and storing history information for each of the staff agencies; and a display control unit for controlling display of the job seeker information stored by the storing unit, the message received by the alliance contact unit, and the history information managed by the user history management unit.SELECTED DRAWING: Figure 1

Description

Applied for application of Article 30, Paragraph 2 of the Patent Law July 1, 2020 https://47agent. Announced on the website of jp/

The present invention relates to an alliance support system between recruitment agencies.

Along with social changes such as changes in corporate employment patterns, changes in growth industries, and diversification of work styles, there is a growing need for recruitment agencies that provide fee-based employment placement services that introduce job seekers to companies. . In addition, recruitment agencies are required to act as an intermediary between companies seeking employment and job seekers, support companies in securing a labor force, and match job seekers with appropriate companies.

However, the job information of companies held by specific recruitment agencies is only a small part of the job information of a certain country or region, and the job applicant information held by specific recruitment agencies is is only part of the job seeker information for Therefore, it is difficult for a specific recruitment agency alone to introduce job seekers to a company to fill 100% of the number of job offers required by the company. It is difficult to introduce a desired company.

As a technique for alleviating such uneven distribution of job seeker information and job offer information, a system has been proposed in which a recruitment agency can purchase the right to introduce a job seeker. According to such a system, it is expected that recruiting agencies will be able to meet a wide range of recruiting needs by purchasing the right to introduce job seekers who match their own recruiting information.

However, in the conventional system, recruitment agencies would invest money in purchasing the right to introduce job seekers, which could lead to an increase in the cost of matching job seekers. There is a concern that this will put pressure on the earnings of recruiting agencies, and in fact, it may even hinder the smooth introduction of personnel.

Here, in order to eliminate the uneven distribution of job seeker information and job offer information without incurring unnecessary costs, it is effective to activate alliances among recruitment agencies. For example, if an alliance is formed in which the referral fee obtained by introducing human resources is shared between the company connected with the job seeker and the company connected with the company that is recruiting, both companies will Eliminate uneven distribution of job seeker information and job offer information without paying costs.

Patent No. 6718190

SUMMARY OF THE INVENTION The present invention has been made to solve the above-described problems, and provides an alliance support system between recruitment agencies capable of supporting alliances between recruitment agencies.

Means to be solved by the invention

The alliance support system between recruitment agencies according to the present invention is
An alliance support system among recruitment agencies for supporting alliances among a plurality of recruitment agencies,
a registration unit that registers job seeker information in association with a recruitment agency that is the source of the registration;
a storage unit that stores job applicant information registered by the registration unit;
a search unit for searching job applicant information stored in the storage unit;
an alliance contact department that receives messages sent by other recruitment agencies to the recruitment agency that registered the job seeker information regarding predetermined job applicant information;
For each recruitment agency, the number of job seeker information registered in the registration department during a predetermined period and the message to the recruitment agency that registered the job seeker information via the alliance contact department a user history management unit that manages history information related to the number of job seeker information sent;
a display control unit that controls display of the job seeker information stored in the storage unit, the message received by the alliance contact unit, and the history information managed by the user history management unit;

In the alliance support system among recruitment agencies according to the present invention, job seeker information, which is information on job seekers with whom an alliance is possible, is registered in association with the recruitment agency that is the registration source. In addition, if a recruitment agency searches for information on other job seekers not registered by itself and finds a job seeker who seems to match the conditions of the recruitment information held by itself, can apply for alliances. In this way, the alliance support system among recruitment agencies according to the present invention supports alliances among recruitment agencies, can activate alliances among recruitment agencies, and can provide information on job applicants. And the uneven distribution of job information can be eliminated.

In addition, by adopting the style of sharing information on job seekers and applying for alliances from the side of recruitment agencies that have job information of companies, each recruitment agency can reduce their own You can deepen your relationship with the recruiting company that is your customer. In addition, since each recruiting agency does not need to disclose the job information of its client companies on the system, it is possible to form alliances while preventing information leaks of client companies. .

Furthermore, in the alliance support system between recruitment agencies according to the present invention, the user history management unit manages history information related to information on job seekers registered in the system and information on job seekers to whom messages have been sent in order to sound out alliances. do. The user history management unit manages the usage history of each recruitment agency that uses the system, and the display control unit displays the history information in the form of a specific numerical value such as the number of cases in a predetermined period or in the form of a graph. , it is possible to recognize how active the alliance is through the system, and the administrator of the system can provide appropriate support according to the situation to the recruitment agency who is the user. It can be carried out.

Further, for example, the registration unit includes a data receiving unit that receives document data describing job applicant information, an automatic input unit that automatically inputs part of the job applicant information from the data received by the data receiving unit, may have a registration support unit with

According to such an alliance support system between recruitment agencies, the registration support section can reduce the user's burden of inputting and registering job seeker information and activate information sharing and alliances.

Further, for example, the history information managed by the user history management unit includes the job applicant information searched and viewed by each recruitment agency via the search unit and the search conditions specified at the time of search by the search unit. may include search history information including at least one of

By including search history information in the history information, system administrators and others can recognize the types of job applicant information that recruiting agencies are interested in, and provide more appropriate support to recruiting agencies who are users. can be done against

Further, for example, a notification unit may be provided for notifying predetermined job seeker information stored in the storage unit to a staffing agency other than the registration source of the job seeker information.

A staffing agency, who is a user, may search for job seeker information by himself/herself via the search section, but the system has a notification section so that new job seeker information can be learned without delay.

Further, for example, it may have a determination unit that determines a notification destination of the job applicant information using the history information managed by the user history management unit,
The notification unit may notify the job applicant information based on the determination of the determination unit.

Such a notification unit, by grasping the usage status and usage trends of each recruitment agency's system from history information, provides job seeker information to users who are highly likely to connect the job seeker information It is possible to notify the user information.

Further, for example, the history information managed by the user history management unit includes job applicant information registered by each recruitment agency in the registration unit and job applicant information sent to the registration source via the alliance contact unit. may include job information about the information;
The display control unit may display the history information of the target recruiting agency as a graph classified into the number of job types.

By managing such history information and displaying the graph by the display control unit, the administrator of the system can identify the types of job seekers that the recruitment agency is good at dealing with. It can be easily grasped, and more appropriate support can be provided.

FIG. 1 is a conceptual diagram showing a server device and its peripheral devices as an alliance support system between recruitment agencies according to one embodiment of the present invention. FIG. 2 is a conceptual diagram showing the configuration of the server device shown in FIG. FIG. 3 is a conceptual diagram showing a situation of personnel introduction when no alliance is formed. FIG. 4 is a conceptual diagram showing the situation of personnel introduction when alliances are actively formed by the system of the present invention. FIG. 5 is a conceptual diagram showing the flow of an alliance between recruitment agencies using the server apparatus shown in FIG. FIG. 6 is a conceptual diagram showing a configuration of a registration unit shown in FIG. 2; FIG. 7 is a conceptual diagram showing the configuration of a storage unit shown in FIG. 2; FIG. 8 is a conceptual diagram showing the configuration of the user history management section shown in FIG. 9 is a conceptual diagram showing a first display example by the display control unit shown in FIG. 2. FIG. 10 is a conceptual diagram showing a second display example by the display control unit shown in FIG. 2. FIG. 11 is a conceptual diagram showing a third display example by the display control unit shown in FIG. 2. FIG. 12 is a conceptual diagram showing a fourth display example by the display control unit shown in FIG. 2. FIG.

FIG. 1 is a conceptual diagram showing a server device 12 as an alliance support system between recruitment agencies and peripheral devices of the server device 12 according to one embodiment of the present invention. A server device 12 as an alliance support system between recruitment agencies is connected to recruitment agency terminals 94, 96, 98 as customer terminals, an administrator terminal 92, and the like via a network communication network 91 such as the Internet. be.

The server device 12 is mainly used by a plurality of recruiting agencies that operate with permission for fee-charging employment placement businesses to form alliances among the recruiting agencies. An administrator terminal 92 shown in FIG. 1 is a terminal of an administrator who manages the server device 12 . An administrator using the administrator terminal 92 manages and operates the server device 12 so that the server device 12 smoothly supports and activates alliances between recruitment agencies. Staffing agency terminals 94 , 96 , and 98 shown in FIG. 1 are terminals used by a plurality of staffing agencies using the server device 12 .

The administrator terminal 92 and the recruiter terminals 94, 96, and 98 are not particularly limited, but are composed of terminals such as PCs, smartphones, and tablets capable of network communication. The administrator terminal 92 and the recruiter terminals 94, 96, and 98 include, for example, a computing unit such as a microprocessor, a storage unit such as a flash memory or a hard disk, a display unit such as a liquid crystal display unit, and a communication unit such as a modem. have, but are not particularly limited to.

A plurality of staffing agencies using the alliance support system among staffing agencies by the server device 12 access the server device 12 via the staffing agency terminals 94 , 96 , 98 and the network communication network 91 . Recruitment agency terminals 94, 96, 98 and administrator terminal 92 access server device 12 using an authentication means such as a password. The accessible range of the recruitment agent terminals 94 , 96 , 98 and the administrator terminal 92 to the server device 12 is appropriately managed by, for example, granting different access rights to each of the terminals 92 , 94 , 96 , 98 .

The server device 12 has a communication section, a storage section, a calculation section, and the like, and functions as a general computer having these. In the description of the server device 12, the description of common points with general computers will be omitted. Although the server device 12 shown in FIG. 1 is of a cloud type, the server device 12 is not limited to this, and the server device 12 may be of an on-premise type.

FIG. 2 is a conceptual diagram showing the configuration of the server device 12 shown in FIG. The server device 12 has a registration unit 20 for registering job applicant information, which is information about a job applicant seeking a new job, a storage unit 30 for storing the job applicant information, and a search unit 40 for searching the job applicant information. The server device 12 also has an alliance communication unit 50 that enables transmission and reception of messages between recruitment agencies, and a user history management unit 60 that manages history information related to usage history of the alliance support system by each recruitment agency. . Further, the server device 12 includes a display control unit 70 for controlling display of job applicant information and history information on each terminal 92, 94, 96, 98, a notification unit 80 for notifying the job applicant information to the recruitment agency, and a determination unit 88 that determines the destination of notification by the notification unit 80 .

Before explaining the internal configuration of the server device 12, the advantages of alliances between recruitment agencies realized by the server device 12 will be explained with reference to FIGS. 3 and 4. FIG. FIG. 3 is a conceptual diagram showing a case where one recruitment agency, a recruitment agency X, conducts recruitment activities without forming an alliance. Recruitment agency X collects job seeker information A to D, which are job seeker information, and recruiting information A to D, which is recruiting information of companies, etc., and performs matching between the two.

As shown in FIG. 3, the recruiting agency X compares the information about the job seekers in the job seeker information A to D with the information about the job offers in the job seeker information A to D, If companies, etc. related to information A match, and job applicants related to job applicant information A match as job offers related to job offer information A, job seekers related to job applicant information A and companies related to job applicant information A are matched. Introduce each other. Furthermore, if the job seeker related to the job seeker information A is found to be employed by the company etc. related to the recruitment information A, the recruitment agency X can obtain compensation from the company etc. that hired the job seeker.

However, the types of industries in which job seekers wish to work are diverse, and the types of human resources companies are looking for are also diverse. In the example, only 1/4) can establish a match. Therefore, the recruitment agency X normally has job applicant information B to D that cannot be matched and job offer information B to D that cannot be matched. As shown in Fig. 3, one of the reasons why job seeker information B to D and job information B to D that cannot be matched is generated is that the recruitment information of companies held by recruitment agency X is based on the recruitment information of a certain country or region. In addition, the job applicant information held by the recruitment agency X is only a part of the job applicant information in a certain country or region.

Under such circumstances, job seekers related to job seeker information B to D cannot receive introductions from companies, and companies related to job seekers information B to D cannot receive referrals from job applicants. This is a disadvantage for both the employer and the hiring company. In addition, since the recruitment agency X cannot introduce the job seeker information B to D or the job offer information B to D, it is not possible to obtain compensation from these information.

On the other hand, FIG. 4 is a conceptual diagram showing the matching situation of recruitment when the server apparatus 12 shown in FIG. 2 is used to support alliances among the recruitment agencies X, Y, and Z. As shown in FIG. 4, each recruiting agency X, Y, Z has some job seeker information A, F, L and job offer information A , F, and L (one-fourth in the example shown in FIG. 4) can establish a match.

However, as shown in FIG. 4, the alliance support system by the server device 12 supports alliances among the recruitment agencies X, Y, and Z, so that each of the recruitment agencies X, Y, and Z has two points in FIG. Job seeker information 32 enclosed by a dashed line can be shared. As a result, recruiting agency X will, for job seeker information C and D, which cannot be matched from its own job seeker information, to job seeker information E and I possessed by other recruiting agencies Y and Z, matching can be established.

In addition, recruitment agency X establishes matching with job seeker information C and D, which cannot be matched from its own recruitment information, by other recruitment agencies Y and Z who have recruitment information E and I. You will be able to This situation is the same for the other recruitment agencies Y and Z using the server device 12 .

Then, as shown in FIG. 4, according to the alliance support system realized by the server device 12, many of the job seekers who could not be introduced to the job seeker companies in the state shown in FIG. In addition, many recruiting companies, etc. that were unable to receive referrals from job seekers will now be able to receive referrals from job seekers, which is advantageous for both job seekers and recruiting companies. In addition, when recruiting agents X, Y, and Z establish matching using the job seeker information 32 of other companies, by sharing the compensation obtained by introduction with the agent that provided the job seeker information 32 ( 50% each), both merchants involved in the alliance can receive more compensation than the situation shown in FIG.

FIG. 5 is a conceptual diagram showing the flow of alliance realized by the server device 12 shown in FIGS. 1 and 2. As shown in FIG. As explained in FIG. 4, the alliance among recruitment agencies X, Y, and Z consists of a job applicant information provider (left side of FIG. 5) that provides job applicant information 32, and a job applicant information receiver that receives job applicant information 32. side (the right side of FIG. 5, the side that has the job offer information to be matched with the received job seeker information). Recruitment agencies X, Y, and Z that use recruitment agency terminals 94, 96, and 98 shown in FIG. 1 also serve as job seeker information providers in FIG. It can also be the job seeker information receiving side (right side of FIG. 5).

As shown in FIG. 4, all recruitment agencies X, Y, and Z are server devices from the standpoint of both job applicant information provider (left side of FIG. 5) and job applicant information receiver (right side of FIG. 5). It is preferred to use 12. However, unlike this, some recruitment agencies that use the server device 12 use the server only as a job applicant information provider (left side of FIG. 5) or only as a job applicant information receiver (right side of FIG. 5). Device 12 may also be used.

As shown on the left side of FIG. 5, recruitment agencies X, Y, and Z on the job seeker information providing side use the server device 12 to perform “job seeker information registration,” “message reception,” “additional information provision/ Request", etc., and form an alliance with other recruitment agencies X, Y, and Z for job seekers related to their own job seeker information. After that, recruitment agencies X, Y, and Z on the job seeker information providing side receive notification of whether or not to hire the job seeker related to the alliance, and perform completion processing such as payment receipt.

On the other hand, as shown on the right side of FIG. Provide and request additional information, etc., and form alliances with job seekers related to job seeker information held by other recruitment agencies. After that, the job seekers related to the alliance are introduced to the companies, etc. related to their own recruitment information, and the job seekers are supported to find employment at the companies, etc. recruiting them. Finally, recruitment agencies X, Y, and Z on the receiving side of the job seeker information contact the recruitment agencies X, Y, and Z on the side providing the job seeker information, Completion processing such as provision of consideration is performed.

The function of each component of the server device 12 shown in FIG. 2 will be described below. The registration unit 20 of the server device 12 registers the job seeker information 32 shown in FIG. 4 in association with the recruitment agencies X, Y, and Z that are the registration sources. As indicated by "A" in FIG. 5, "job seeker information registration" is performed first by staffing agencies X, Y, and Z on the job seeker information providing side in the flow of alliances in the server device 12. FIG.

FIG. 6 is a conceptual diagram showing the internal configuration of the registration unit 20 shown in FIG. The registration unit 20 allows the recruitment agencies X, Y, and Z to register the job seeker information in the server device 12, via the display control unit 70, to the display units of the recruitment agency terminals 94, 96, and 98. Displays an input screen, etc. The registration unit 20 also has a registration support unit 22 that supports input of job seeker information by the recruitment agencies X, Y, and Z. FIG. The registration support section 22 has a data receiving section 24 for receiving document data describing job seeker information, and an automatic input section 26 for automatically inputting part of the job seeker information from the data received by the data receiving section 24. - 特許庁

FIG. 9 shows an example of a job applicant information registration screen (first display example 71) displayed by the registration unit 20 of the server device 12 on the display units of the recruitment agency terminals 94, 96, and 98 via the display control unit 70. ) is a conceptual diagram showing As shown in FIG. 9, the registration unit 20 and the display control unit 70 display the name of the job seeker and the most recent annual income of the job seeker on the display units of the terminals 94, 96, and 98 of the job seeker information. , desired job title, desired work location, qualifications possessed by the job seeker, the most recent years of service, etc. are displayed. In addition, the registration unit 20 acquires the job seeker information input from the recruiting agency terminals 94, 96, and 98 together with the information of the recruiting agencies X, Y, and Z that registered the job seeker information. to complete the registration of job applicant information in the system.

Job applicant information registered by the registration unit 20 shown in FIG. 2 is stored in the storage unit 30 of the server device 12 shown in FIG. The job seeker information registered by the registration unit 20 and stored by the storage unit 30 is used by the search unit 40 of the server device 12 as well as other recruitment agencies X, Y, Z using the server device 12 (other than the registration source). etc., can be searched. The search for the job seeker information 32 by the search unit 40 will be described later with reference to FIG. 10 and the like.

The input of job seeker information as shown in FIG. 9 can be manually input from terminals 94, 96, and 98 of recruitment agencies. can be easily registered. That is, as shown in FIG. 9, an input field 24a for inputting a data directory of documents describing job seeker information is displayed on the job seeker information input screen. The data receiving section 24 of the registration support section 22 can receive document data describing job seeker information, such as a resume and job history, from the directory entered in the input field 24a. Examples of the format of data received by the data receiving unit 24 include, but are not limited to, image data of resumes and resumes, text data of resumes and resumes, and the like.

The automatic input unit 26 of the registration support unit 22 shown in FIG. 6 extracts the job seeker information required for registration from the data received by the data receiving unit 24, and instead of manual input by recruitment agencies X, Y, and Z, Auto-populate some of the candidate information. The automatic input unit 26 may have, for example, an OCR (optical character recognition) function for extracting job seeker information from image data of resumes and career history sheets.

FIG. 7 is a conceptual diagram showing the job seeker information 32 stored by the storage unit 30 shown in FIG. The job seeker information 32 includes, for example, the job seeker's name, initials, gender, age, job seekers (first and second choices), current annual income, desired annual income, desired work location, employment classification, number of times of job change, and registration date. , renewal date, source recruitment agency and contact person, nationality, visa, etc. The job seeker information 32 is assigned an ID to each job seeker information relating to individual job seekers and managed by the server device 12 .

The search unit 40 shown in FIG. 2 searches the job applicant information 32 registered by the registration unit 20 and stored by the storage unit 30 . As indicated by "B" in FIG. 5, in the flow of the alliance in the server device 12, the "job seeker information search" by the search unit 40 is performed by the recruitment agencies X, Y, and Z on the job seeker information receiving side. It should be noted that the recruitment agencies X, Y, and Z on the receiving side of the job applicant information can also receive the job applicant information from the server device 12 by notification by the notification unit 80 of the server device 12 instead of searching by the search unit 40. be. Notification of job applicant information by the notification unit 80 will be described later.

FIG. 10 shows an example of a job applicant information search screen (second display example 72) displayed by the search unit 40 of the server device 12 on the display units of the recruitment agency terminals 94, 96, and 98 via the display control unit 70. ) is a conceptual diagram showing As shown in FIG. 10, the search unit 40 and the display control unit 70 of the server device 12 display a job applicant information search screen (second display example 72) on the display units of the recruitment agency terminals 94, 96, and 98. do.

As shown in FIG. 10, on the job applicant information search screen shown as the second display example 72, a search input portion 42 for entering search conditions and the like for searching for job applicant information stored in the storage unit 30 is displayed. be done. The search input part 42 includes an input field for specifying the ID of the job seeker information to be viewed, an input field for designating the desired work location and desired industry included in the job seeker information, and the like. The search input part 42 may be provided with a search condition saving function for naming and saving the search conditions used for the search, and a calling function for calling up previously saved search conditions. This makes it possible, for example, to store search conditions that match the personnel sought by a particular company. Recruitment agencies using recruitment agency terminals 94 , 96 and 98 click search execution button 44 after inputting search conditions for job seeker information in search input section 42 .

When the search unit 40 of the server device 12 recognizes that the search execution button 44 has been clicked by the recruitment agent terminals 94, 96, 98, the job applicant information that matches the search conditions entered in the search input part 42 is The job seeker information 32 stored in the storage unit 30 is searched, and the search results are displayed in the search result display portion 46 shown in FIG.

The search result display portion 46 displays the number of pieces of job applicant information that meet the search conditions and a portion 32a of the job applicant information that matches the search conditions. In this way, the recruitment agencies X, Y, and Z on the job applicant information receiving side shown in FIG. Job applicant information 32 can be browsed.

Recruitment agencies X, Y, and Z on the receiving side of the job seeker information, from the part 32a of the displayed job seeker information, the job seeker related to the job seeker information is It can be examined whether the conditions are likely to be met. In addition, the search unit 40 and the display control unit 70 of the server device 12 display the job applicant information displayed in the search result display part 46 as part of the job applicant information 32a or separately from the job applicant information. 12, the information of the recruiting agencies X, Y, Z and their persons in charge is displayed.

As shown in FIG. 10, part 32a of the job seeker information displayed in the search result display area 46 does not include information that can identify the individual, such as only the initials of the job seeker, not the name of the job seeker. It is not disclosed and the individual job applicant cannot be identified.

The alliance contact unit 50 shown in FIG. 2, regarding the predetermined job seeker information 32 stored in the storage unit 30, sends the job seeker information to the recruiting agencies X, Y, and Z that are the registration sources of the job seeker information. Accept messages sent by X, Y, Z. As indicated by "C" in FIG. 5, in the flow of the alliance in the server device 12, the recruiting agents X, Y, and Z on the side that take over the job applicant information must When job seeker information that is likely to match is found by searching or the like, the alliance communication unit 50 of the server device 12 is used to send a message to the recruitment agencies X, Y, and Z that are the registration sources.

FIG. 11 is an example of a communication display screen (third display example 73) displayed by the alliance contact unit 50 of the server device 12 on the display units of the recruitment agency terminals 94, 96, and 98 via the display control unit 70. It is a conceptual diagram showing As shown in FIG. 11, the alliance communication unit 50 and the display control unit 70 of the server device 12 communicate messages between the job applicant information providing side and the job applicant information receiving side shown in FIG. In order to establish a relationship, communication means in chat format (see message section 54) are displayed on the displays of both staffing agency terminals 94, 96, and 98. FIG.

As shown in FIG. 10 , in the third display example 73 by the contact/communication means provided by the alliance contact section 50 , predetermined job seeker information specified as the destination of the message is displayed as the destination designation portion 53 . For example, when it is desired to form an alliance for the job applicant information displayed in the search result display area 46 shown in FIG. Specify the job applicant information as the destination of the message.

Further, the staffing agencies X, Y, and Z on the job applicant information receiving side enter a message 51 regarding questions and requests to the job applicant information provider side in the message portion 54 shown in FIG. The alliance communication unit 50 sends the message 51 on the job applicant information receiving side received in the message part 54 to the recruitment agencies X, Y, and Z on the job applicant information providing side. As a result, recruitment agencies X, Y, and Z on the receiving side of job applicant information will contact recruitment agencies X, Y, and Z on the side of providing job applicant information, which are the sources of registration of the specified job applicant information, regarding the alliance. It can be performed.

The contents of the message 51 sent by the recruitment agencies X, Y, and Z on the receiving side of the job seeker information are not particularly limited. Examples include requests for additional information 52 and confirmation of the job seeker's intentions regarding the job seeker. Recruitment agencies X, Y, and Z on the job seeker information provider side, who registered the job seeker information, are also notified to the recruiting agencies X, Y, and Z on the job seeker information receiving side via the alliance contact department 50. A message 51 can be sent to the

The contents of the message 51 sent by the recruitment agencies X, Y, and Z on the job seeker information providing side (registration source) are not particularly limited, but for example, a job seeker related to the target job seeker information, such as a company's job advertisement. There are those that seek information on the referral destination of a person, and those that seek information on the consideration received from a company after a job is decided. The contact/communication means provided by the alliance contact unit 50 to the job applicant information provider (registration source) is provided to recruitment agencies X, Y, and Z on the job applicant information receiving side, as shown in FIG. can be the same as

As described above, the alliance contact unit 50 accepts and sends the initial message indicated by "C" in FIG. receive and send two-way messages. As a result, the alliance communication unit 50 performs communication/communication 56 surrounded by a two-dot chain line in FIG. provide a means of contact for The communication/contact tool provided by the alliance contact unit 50 may be in the form of a chat as shown in FIG. can be anything.

As shown in FIG. 5, information is exchanged between the job applicant information provider (registration source) and the job applicant information receiver, and when the alliance progresses, the recruitment agencies X, Y, and Z on the job applicant information receiver side , the job seeker related to the target job seeker information is contacted directly or via the recruiting agency of the registration source, and introduces the job seeker to the company. In addition, recruitment agencies X, Y, and Z on the receiving side of job seeker information contact the job seeker information provider (registration source) as to whether or not the job seeker can be hired, as indicated by "E" in FIG. Complete the alliance for the job seeker by completing the payment process.

The alliance communication unit 50 in the server device 12 can also receive and send messages regarding the communication about whether or not a job seeker can be hired, indicated by "E" in FIG. However, the job applicant information providing side (registration source) and the job applicant information receiving side may communicate by means of communication other than the alliance communication section 50 . In addition to the alliance contact unit 50, the server device 12 may provide contact means in a format that does not specify target job seeker information as contact means between a plurality of recruitment agencies using the server device 12. good.

The user history management unit 60 shown in FIG. 2 manages the staffing agencies X, Y, and Z using the server device 12 via the staffing agency terminals 94, 96, and 98 shown in FIG. and manages history information 61 relating to the history of using the server device 12 . The user history management unit 60 stores at least part of history information 61 to be managed. For example, the user history management unit 60 manages the job applicant information (including information such as the registration date and time of the job applicant information) registered by the predetermined recruitment agencies X, Y, and Z from the registration unit 20, among the history information 61 managed by the user history management unit 60. ) and job seeker information (including information such as the date and time when the message was sent) that sent a message to the recruiting agency that registered the job seeker information via the alliance contact unit 50.

FIG. 8 is a conceptual diagram showing the internal configuration of the user history management section 60 shown in FIG. As shown in FIG. 8, the user history management unit 60 stores the job applicant information registration history (including registration date and time) related to the job applicant information registered by the predetermined recruitment agencies X, Y, and Z from the registration unit 20, A message sending history (including sending date and time) of sending messages to other recruitment agencies via the alliance contact unit 50 is stored as history information 61 . Further, as shown in FIG. 8, the usage history management unit 60 not only stores information, but also has a history display calculation unit 68 that performs calculation using the stored information. The history display calculation unit 68 calculates, from the information stored by the user history management unit 60, some of the history information 61 that is not directly stored, such as the monthly number of registered job applicant information and the total number of registered job applicant information. can be extracted. Also, the history display calculation unit 68 performs calculation processing necessary for numerical display and graph display regarding the history information 61 .

The history information 61 managed by the user history management unit 60 includes the monthly number of registered job seeker information and the total number of registered job seeker information, as well as information on the desired job type, age group, gender, etc. of the job seeker related to the registered job seeker information. may be included. In addition, the history information 61 extracted by the history display calculation unit 68 and managed by the user history management unit 60 includes the monthly number and total number of information on job applicants who have newly sent messages to the registrant, as well as the number of messages sent. The job seeker's desired occupation, age group, gender, etc. related to the job seeker information may be included. The history information 61 includes job applicant information registered in the registration unit 20 by each staffing agency and job information related to job applicant information sent to the registration source via the alliance contact unit 50, so that the administrator terminal 92 The administrator of the server device 12 who browses the history information 61 via the can analyze the possibility of future alliances between users.

In addition, as shown in FIG. 8, the history information 61 managed by the user history management unit 60 includes job seeker information and Search history information 69 including at least one of the search conditions specified at the time of search by the search unit 40 may be included. By managing and storing job seeker information viewed in the past by predetermined recruitment agencies X, Y, and Z, and search information searched in the past, the server device 12 can be used by the predetermined recruitment agencies X, Y, and Z. Recognize characteristics and trends in the job candidate information you are looking for.

FIG. 12 shows an example of a user history display screen (fourth display example 74) displayed by the user history management unit 60 of the server device 12 on the display unit of the administrator terminal 92 via the display control unit 70. It is a conceptual diagram. As shown in FIG. 12 , the user history management unit 60 and the display control unit 70 of the server device 12 can display managed history information 61 on the administrator terminal 92 .

As shown in FIG. 12, the user history display screen according to the fourth display example 74 includes a user information display portion 62 that is information about the recruitment agency displaying the usage history. Information contained in the user information display portion 62 includes the company name of the user, the employment agency, license number for fee-charging employment placement business, office location, representative name, contact information, and the like.

In addition, in the first number display portion 63 in the fourth display example 74, the average monthly number of registered job seeker information of the relevant recruitment agency is displayed, and in the second number display portion 64, the corresponding recruitment agency is displayed. The average monthly number of job seeker information messages sent via the alliance contact section 50 is displayed. The information displayed in the first number display portion 63 and the second number display portion 64 is the history information 61 stored in the user history management section 60, or the history display calculation section 68 is stored. This is the history information 61 calculated from the history information 61 that is present.

Also, in the first graph display portion 65 in the fourth display example 74, the percentage of job seekers by age group related to the job seeker information registered by the target recruitment agency is displayed in a pie chart. In addition, in the second graph display portion 66 in the fourth display example 74, the percentage of each job seeker's desired occupation related to the job seeker information to which the target recruitment agency sent a message is displayed in a pie chart. . In this manner, the display control unit 70 in the server device 12 can display the history information 61 of the target recruitment agency in the form of a graph classified into the number of cases by occupation or age.

As described with reference to FIGS. 9 to 12, the display control unit 70 shown in FIG. controls the display of history information 61 managed by . The server device 12 appropriately displays various information stored in the server device 12 on the displays of the recruitment agent terminals 94 , 96 , 98 and the administrator terminal 92 by interlocking the display control unit 70 and other components. can be displayed in the form

The notification unit 80 shown in FIG. 2 notifies the predetermined job seeker information 32 stored in the storage unit 30 to one other recruitment agency other than the registration source of the job seeker information 32 . For example, when new job applicant information is registered in the server device 12 from one of the recruitment agencies X, Y, and Z, the notification unit 80 uses the server device 12 for the job applicant information. Other recruitment agencies may be notified.

With such notification unit 80, recruitment agencies X, Y, and Z on the receiving side of job seeker information shown in FIG. certain job applicant information can be received from the server device 12 . Further, the determination unit 88 can determine the notification destination of the job applicant information 32 using the history information 61 managed by the user history management unit 60 .

That is, the server device 12 may have job offer information that can match newly registered job seeker information with the job seeker information using the history information 61 managed by the user history management unit 60. Recruitment agencies with high For example, the determination unit 88 of the server device 12 analyzes the desired occupation in the newly registered job seeker information, and determines a recruitment agency with a track record of forming an alliance with respect to the desired occupation as a notification destination of the registered job seeker information. be able to.

In addition, the determination unit 88 uses the history information 61 managed by the user history management unit 60 to set a recruitment agency with no browsing record as a notification destination of the job seeker information, or The introduction agency can be excluded from the target of notification of the job seeker information.

As described above, according to the alliance support system between recruitment agencies realized by the server device 12 according to the embodiment, it is possible to support alliances among recruitment agencies and activate alliances among recruitment agencies. It is possible, and the uneven distribution of job seeker information and job offer information can be eliminated. In addition, the user history management unit 60 manages the usage history of each of the recruitment agencies X, Y, and Z that use the system, thereby recognizing how active the alliance is through the system. This allows the system administrator or the like to provide appropriate support according to the situation to the recruiting agency who is the user.

In addition, the registration support unit 22, the notification unit 80, the user history management unit 60, and the like function in conjunction with each other, thereby promoting the sharing of job seeker information and activating alliances. Also, as shown in FIG. 4, an increase in the number of matchings accompanying the promotion of alliances by the server device 12 benefits all recruiting agencies participating in the system, and no participant suffers a disadvantage due to an increase in matching. . Therefore, in the alliance support system realized by the server device 12, the content of the alliance contract of each recruitment agency and the content of the recruitment activities themselves may be freely handled by each recruitment agency. can devote themselves to supporting the revitalization of the Alliance.

It should be noted that the server device 12 shown in the embodiment is merely one embodiment for realizing an alliance support system between recruitment agencies according to the present invention, and it goes without saying that the present invention has various other embodiments. stomach. For example, the number of recruiting agencies participating in the system is not particularly limited, nor is the scale of participating recruiting agencies.

12 Server device 20 Registration unit 22 Registration support unit 24 Data reception unit 24a Input field 26 Automatic input unit 30 Storage unit 32, 32a Job applicant information 40 Search unit 42 Search input unit 44 Search Execution button 46 Search result display portion 50 Alliance contact portion 51 Message 53 Destination designation portion 54 Message portion 56 Communication/contact 60 User history management portion 61 History information 62 User information display portion 63 First number display portion 64 Second number display portion 65 First graph display portion 66 Second graph display portion 68 History display calculation section 69 Search history information 70 Display control section 71 First display example 72 ... second display example 73 ... third display example 74 ... fourth display example 80 ... notification unit 91 ... network communication network 92 ... administrator terminals 94, 94, 96 ... recruitment agent terminals
X, Y, Z... Recruitment agencies

Claims (6)

An alliance support system among recruitment agencies for supporting alliances among a plurality of recruitment agencies,
a registration unit that registers job seeker information in association with a recruitment agency that is the source of the registration;
a storage unit that stores job applicant information registered by the registration unit;
a search unit for searching job applicant information stored in the storage unit;
an alliance contact department that receives messages sent by other recruitment agencies to the recruitment agency that registered the job seeker information regarding predetermined job applicant information;
For each recruiting agency, during a predetermined period, send a message to the recruiting agency that registered the job seeker information via the alliance contact department and the number of job seeker information registered in the registration department. a user history management unit that manages history information related to the number of job seeker information that has been collected;
A display control unit that controls display of the job seeker information stored in the storage unit, the message received by the alliance contact unit, and the history information managed by the user history management unit Alliance support system. The registration unit has a data receiving unit that receives document data describing job applicant information, and an automatic input unit that automatically inputs part of the job applicant information from the data received by the data receiving unit. 2. The alliance support system among recruitment agencies according to claim 1, comprising a unit. The history information managed by the user history management unit is at least one of the job applicant information searched and viewed by each recruitment agency through the search unit and the search conditions specified at the time of search by the search unit. 3. The alliance support system among recruitment agencies according to claim 1 or claim 2, which includes search history information including . 4. The method according to any one of claims 1 to 3, further comprising a notification unit for notifying a job applicant information stored in the storage unit to a staffing agency other than a registration source of the job applicant information. Alliance support system between recruitment agencies. a determination unit that determines a notification destination of the job applicant information using the history information managed by the user history management unit;
5. The alliance support system among recruitment agencies according to claim 4, wherein said notification unit notifies said job seeker information based on the determination of said determination unit. The history information managed by the user history management unit is occupational information related to job applicant information registered by each recruitment agency in the registration unit and job applicant information sent to the registration source via the alliance contact unit. including
6. The alliance support between recruitment agencies according to claim 1, wherein the display control unit displays the history information of the target recruitment agency as a graph classified into the number of job types. system.

Images