JP2023032573A - Contact information management device, method and program - Google Patents

Abstract

To provide a contact information management device, method and program that receives and manages contact information output from a terminal device of a previously registered person and that eliminates intricateness of management when an unregistered person is specified.SOLUTION: A contact information management device comprises: a storage part 21 which stores identification information on previously registered persons and information on registration candidates including registered persons and non-registered persons; a contact information reception part 22 which receives contact information output from terminal devices of the registered persons; and a management part 23 which manages contact information on the registered persons and the information on the non-registered persons based upon the information on the registration candidates and the identification information on the registered persons.SELECTED DRAWING: Figure 1

Description

The present invention relates to a contact information management device, method, and program for receiving and managing contact information output from a terminal device.

In the past, when notifying the school of a student's health condition (physical condition, body temperature, etc.), for example, they had to fill out a paper form and submit it.

However, with paper media, there are problems such as students forgetting to bring them to school, and paper media need to be managed.

Therefore, for example, a system is conceivable in which parents of students create contact information such as health conditions using terminal devices, and transmit the contact information to terminal devices installed at schools. The school side can check the health condition of the student by checking the contact information displayed on the terminal device.

JP 2009-277202 A

However, as described above, when a guardian uses a terminal device to contact contact information such as health status, guardians who do not have a terminal device or who have not registered a terminal device in the system described above cannot contact Information cannot be reported.

Therefore, on the school side, it is not possible to manage the contact information of students whose terminal devices are not registered on the same system as described above, and it is necessary to separately confirm whether or not the terminal device is registered. Work becomes complicated.

Patent Document 1 proposes a system for managing attendance at school lectures, which sends e-mails from mobile terminals and records attendance information based on the information in the received e-mails and pre-registered student information. It is In Patent Document 1, a method of collecting a handwritten attendance sheet from a student who could not send an outgoing e-mail because he forgot his mobile terminal or the battery of the mobile terminal ran out, and then inputting it into the system later. is proposed.

However, even in Patent Literature 1, students who have not been able to send attendance emails can only be confirmed by a handwritten attendance sheet, and cannot be confirmed on the same system, which complicates the work.

SUMMARY OF THE INVENTION In view of the above circumstances, it is an object of the present invention to provide a contact information management apparatus, method, and program capable of eliminating the complexity of management that occurs when identifying an unregistered person.

The contact information management device of the present invention comprises: a registrant identification information storage unit that stores pre-registered registrant identification information; a contact information reception unit that receives contact information output from a registrant's terminal device; and registered candidate information storage unit for storing information of registered candidates including unregistered persons, and registrant contact information and unregistered person information based on registered candidate information and registrant identification information. and a management unit that manages the

A contact information management program according to the present invention comprises steps of storing pre-registered identification information of registrants; storing the information of the registrants; and managing the contact information of the registrants and the information of the unregistered persons based on the information of the registrant candidates and the identification information of the registrants.

The contact information management method of the present invention stores pre-registered identification information of registrants and information of registrant candidates including registrants and unregistered persons, and accepts contact information output from registrant terminal devices. and managing contact information of registrants and information of non-registrants based on the information of registrant candidates and the identification information of registrants.

According to the contact information management device, method, and program of the present invention, the contact information of registrants and the information of unregistered persons are managed. can be resolved.

1 is a block diagram showing a schematic configuration of a contact information management system using an embodiment of a contact information management device of the present invention; Diagram showing an example of contact information setting input screen A diagram showing an example of a school management table A diagram showing an example of a grade management table A diagram showing an example of a class management table A diagram showing an example of a terminal registration management table A diagram showing an example of a contact information management table Diagram showing an example of approver confirmation screen Flowchart for explaining the flow of processing of the contact information management system shown in FIG.

Hereinafter, a contact information management system using an embodiment of the contact information management device of the present invention will be described in detail with reference to the drawings. FIG. 1 is a block diagram showing a schematic configuration of a contact information management system 1 of this embodiment.

The contact information management system 1 of this embodiment includes a registrant terminal device 10, a contact information management device 20, and an approver terminal device 30, as shown in FIG.

The registrant's terminal device 10 and the contact information management device 20, and the contact information management device 20 and the approver's terminal device 30 are connected via communication lines. The communication line may be an Internet line or a telephone line. Also, the communication line may be wired or wireless.

First, a rough flow of processing using the contact information management system 1 of this embodiment will be described.

The contact information management system 1 of this embodiment is a system used by a school and parents of students attending the school, and is mainly used by parents to contact the school with contact information such as the health status of their students. It is a system used for

In this embodiment, the students correspond to the registration candidates of the present invention, and there are registered students and unregistered students. A registrant is a person registered in advance in the contact information management device 20 , and identification information of the registrant is stored in the contact information management device 20 . An unregistered person is a person who has not yet been registered in the contact information management device 20 . A registration candidate is a person (student) who can be registered in the contact information management apparatus 20, and includes a registrant (student) who has already been registered and an unregistered person (student) who has not yet been registered.

In the contact information management system 1 of the present embodiment, first, the contact information management device 20 creates a contact information management table that stores the health condition of each student based on pre-registered school, class, and student information. .

Next, the guardian uses the registrant terminal device 10 to set and input contact information such as the student's (child's) health condition.

The contact information set and input by the guardian is output from the registrant's terminal device 10 to the contact information management device 20 and is stored and managed by the contact information management device 20 .

In response to a request from the approver's terminal device 30 installed at the school, each student's contact information stored in the contact information management device 20 is output and accepted by the approver's terminal device 30 at the school. At this time, the contact information management device 20 outputs not only the contact of the already registered student (registrant) but also the information of the unregistered student (unregistered person) to the approver's terminal device 30. - 特許庁

The approver's terminal device 30 receives the contact information of already registered students and the information of unregistered students, and displays them. The contact information such as the health condition displayed on the approver terminal device 30 is confirmed by the approver (staff) of the school, and the approver can check the already registered contact information of the student. At the same time, information on unregistered students can also be confirmed on the same screen.

The above is the general flow of processing using the contact information management system 1 of the present embodiment. Although FIG. 1 shows only one registrant terminal device 10 and one approver terminal device 30, in reality, the registrant terminal device 10 is registered in the contact information management device 20. Approver terminal devices 30 are provided as many as the number of schools.

Next, details of each device constituting the contact information management system 1 of the present embodiment will be described.

As described above, the registrant terminal device 10 is used by a parent, and mobile terminals such as smartphones and tablet terminals are used, for example. However, the computer is not limited to this, and may be a desktop computer or a notebook computer.

The registrant terminal device 10 includes a CPU (Central Processing Unit), semiconductor memory such as ROM (Read Only Memory) and RAM (Random Access Memory), storage such as a hard disk, and communication I/F (Interface). there is

The storage of the terminal device 10 for registrants is installed with an application for guardians that accepts setting inputs of contact information including health conditions such as body temperature and physical condition of students. When the guardian application is activated by the CPU, a contact information setting input screen is displayed on the registrant terminal device 10 .

FIG. 2 is a diagram showing an example of a contact information setting input screen. The contact information setting input screen shown in FIG. 2 displays a body temperature input field S1, a health condition selection field S2, a message input field S3, a pool participation permission/inhibition selection field S4, and a marathon participation permission/inhibition selection field S5. be.

The body temperature input field S1 is a field for receiving an input of a student's body temperature. The body temperature input field S1 displays a pull-down value of the body temperature, and is configured so that the guardian can select the measured body temperature.

The health condition selection column S2 is a column for receiving the health condition of the student. The health condition selection field S2 displays radio buttons that allow selection of whether the physical condition of the student is "good" or "poor".

The message input field S3 can accept text input, and the guardian sets and inputs more specific symptoms, for example, when the student is in poor physical condition.

The pool participation permission/prohibition selection column S4 is a column for accepting permission/prohibition of participation in the pool class. A radio button that allows selection of “participation” or “non-participation” is displayed in the pool participation permission/inhibition selection field S4.

The marathon participation approval/disapproval selection column S5 is a column for receiving approval/disapproval of participation in the marathon class. In the marathon participation permission/inhibition selection field S5, a radio button is displayed with which “participation” or “non-participation” can be selected.

Also, although not shown on the contact information setting input screen shown in FIG. Is displayed.

On the contact information setting input screen, a "report" button, a "clear input" button, and a "confirm past absence/late arrival/early leave contact" button are displayed.

Further, tags Tg1 to Tg3 are displayed on the contact information setting input screen. The tags Tg1 to Tg3 are for selecting the target student of the contact information, and in the example of FIG. 2, one of "Taro", "Hanako" and "Jiro" is selected. Such tags Tg1 to Tg3 are used, for example, when one parent registers multiple children (students) at the same or different schools. FIG. 2 shows an example of display when tag Tg1 is selected, but similar display is performed when tag Tg2 or tag Tg3 is selected.

Then, for example, when Taro of tag Tg1 has been entered into each column, the "report" button shown in FIG. is output from the registrant terminal device 10 to the contact information management device 20 . When the contact information of "Taro" is output from the registrant terminal device 10, the identification information of "Taro" is also output together. This identification information is a student ID registered in a terminal registration management table T4, which will be described later.

Note that when the "clear input" button shown in FIG. 2 is tapped, the information set and input in each column is cleared. As for the processing when the "Check past absence/lateness/early leaving contact" button shown in FIG.

Next, the contact information management device 20 will be described. The contact information management device 20, which is a server device, receives the contact information output from the registrant terminal device 10, and stores and manages it for each student.

Specifically, the contact information management device 20 includes a storage unit 21, a contact information reception unit 22, and a management unit 23, as shown in FIG.

The storage unit 21 stores a school management table T1, a grade management table T2, a class management table T3, a terminal registration management table T4, and a contact information management table T5.

FIG. 3 is a diagram showing an example of the school management table T1. The school management table T1 is a table that stores the identification number (school ID) of each school in which the approver terminal device 30 is installed and the school name.

FIG. 4 is a diagram showing an example of the grade management table T2. The grade management table T2 is a table that stores the identification number (school ID) of each school stored in the school management table T1, the identification number (grade ID) of each school, and the name of the grade.

FIG. 5 is a diagram showing an example of the class management table T3. The class management table T3 stores the identification number (grade ID) of each grade stored in the grade management table T2, the identification number (class ID) of each class of each grade, the name of the class, and the number of students in each class. It is a table. In this embodiment, the class management table T3 corresponds to the registered candidate information storage unit of the present invention, and the number of people in each class in the class management table T3 corresponds to the number of registered candidates of the present invention. In the present embodiment, the number of people in a class is stored as information about registrant candidates. can be

FIG. 6 is a diagram showing an example of the terminal registration management table T4. The terminal registration management table T4 contains the identification number (class ID) of each class stored in the class management table T3 and the identification number (child student ID) and the student's attendance number. In this embodiment, the terminal registration management table T4 corresponds to the registrant identification information storage section of the present invention.

FIG. 7 is a diagram showing an example of the contact information management table T5. The contact information management table T5 is a table generated by the management unit 23, which will be described later, using the school management table T1, the grade management table T2, the class management table T3, and the terminal registration management table T4.

The contact information management table T5 contains class identification numbers (class IDs) stored in the class management table T3, registered student identification numbers (child student IDs) stored in the terminal registration management table T4, and each class This is a table that stores contact information such as the attendance numbers of all the students belonging to each class and the health conditions (body temperature and physical condition) of the students belonging to each class.

At a preset time, the management unit 23 refers to the school management table T1, the grade management table T2, the class management table T3, and the terminal registration management table T4, and generates a contact information management table T5 for each school. do. The preset time is, for example, a time at which contact information management device 20 is not accessed from registrant terminal device 10 and approver terminal device 30, such as midnight.

Specifically, the management unit 23 identifies the school ID of a predetermined school using the school management table T1, refers to the grade management table T2 based on the school ID, and identifies the grade ID corresponding to the school ID. do. Then, the management unit 23 refers to the class management table T3 based on the identified grade ID, and obtains the class ID corresponding to the grade ID and the number of students in the class.

Then, based on the obtained number of students in the class, the management unit 23 creates records for the number of students, and records the class ID and the attendance number in the record. Note that the record in this embodiment is a field for recording information for each student, and is generated for each student.

Furthermore, the management unit 23 refers to the terminal registration management table T4 based on the class ID and attendance number of each record, acquires the registered student ID, and records the acquired student ID in the corresponding record. to generate a contact information management table T5.

Contact information management table T5 generated at this time does not yet include contact information such as body temperature and physical condition of each student.

The contact information management table T5 includes not only records of students (child student IDs) stored in the terminal registration management table T4, but also records of students (unregistered persons) who have not yet been registered in the terminal registration management table T4. The identification number (student ID) column for unregistered students is left blank. For example, in the case of the contact information management table T5 shown in FIG. 7, the student with attendance number 5 is an unregistered student.

The management unit 23 stores the contact information management table T5 generated as described above in the storage unit 21 .

The contact information receiving unit 22 receives the contact information of each student output from each registrant terminal device 10 .

The management unit 23 acquires the contact information of each student accepted by the contact information accepting unit 22, and records the acquired contact information of each student in each record in the contact information management table T5.

In response to a request from the approver's terminal device 30, the management unit 23 outputs the contact information management table T5 and causes the approver's terminal device 30 to display it. A method of displaying the contact information management table T5 will be described in detail later.

In addition, the management unit 23 accepts editing of contact information of registered students in the contact information management table T5. The management unit 23 also accepts editing of the contact information of the unregistered person in the contact information management table T5. The contact information may be edited using the approver's terminal device 30, which will be described later, or using an input device connected to the contact information management device 20. FIG.

The contact information management device 20 includes a semiconductor memory such as a CPU, a ROM and a RAM, a storage such as a hard disk, and a communication I/F. A contact information management program is installed in the storage of the contact information management device 20 . By executing this contact information management program by the CPU, the functions of the storage unit 21, the contact information reception unit 22, and the management unit 23 described above are realized. and data transmission and reception between the contact information management device 20 and the approver terminal device 30 are performed.

In the present embodiment, the communication information management program is executed by the CPU to cause the above-described units of the contact information management device 20 to function. The functions may be configured from hardware such as ASCI (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), and other electric circuits.

The approver's terminal device 30 is used by the approver (staff) of the school as described above. A terminal may be used.

The approver terminal device 30 receives the contact information management table T5 output from the contact information management device 20, and displays the approver confirmation screen using the received contact information management table T5.

The approver terminal device 30 has a display device such as a liquid crystal display, and an approver confirmation screen is displayed on this display device. When a tablet terminal is used as the approver terminal device 30, the approver confirmation screen is displayed on the touch panel of the tablet terminal.

The approver terminal device 30 includes a CPU, a semiconductor memory such as a ROM and a RAM, a storage such as a hard disk, and a communication I/F.

An approver application is installed in the storage of the approver terminal device 30 . When this approver application is activated by the CPU, the approver confirmation screen is displayed on the approver terminal device 30 . Instead of using the approver application installed in the storage as in this embodiment, an approver application provided via a web browser may be used.

FIG. 8 is a diagram showing an example of an approver confirmation screen. The approver confirmation screen shown in FIG. 8 shows a display example of the contact information of "Riso Elementary School". On the approver confirmation screen shown in FIG. 8, each record in which contact information for each student is recorded is displayed in a list in the contact information display field R1. A grade selection field R2 and a class selection field R3 are also displayed on the approver confirmation screen shown in FIG. Buttons such as "All grades", "1st year", and "2nd year" are displayed in the grade selection column R2. Buttons such as "1 group", "2 group", and "3 group" are displayed in the class selection column R3.

In the contact information display field R1, the contact information of the grade selected in the grade selection field R2 and the class selected in the class selection field R3 are extracted and displayed as a list.

In the contact information display field R1, as shown in FIG. Columns for "additional observation 1", "additional observation 2" and "report date and time" are displayed. The "grade", "class" and "attendance number" columns display the student's grade, class and attendance number.

In addition, in the "Attendance" column, information such as absence, leaving early, arriving late, etc. set and input on the registrant terminal device 10 is displayed. In addition, the body temperature set and input in the body temperature input field S1 shown in FIG. 2 is displayed in the "measured temperature" column.

In addition, the contents selected in the health condition selection field S2 shown in FIG. 2 are displayed in the "health condition" column. In addition, the contents entered in the message input field S3 shown in FIG. 2 are displayed in the column of "message".

Further, in the "additional observation 1" column, the content selected in the pool participation permission/inhibition selection column S4 shown in FIG. 2 is displayed. Further, in the "additional observation 2" column, the contents selected in the marathon participation permission/inhibition selection column S5 shown in FIG. 2 are displayed.

In addition, the date when the contact information was output from the registrant terminal device 10 is displayed in the "report date and time" column.

Further, the contact information display field R1 includes records of students (child student IDs) registered in the terminal registration management table T4, records of students (unregistered persons) not yet registered in the terminal registration management table T4, and terminal Records of students registered in the registration management table T4, but whose contact information has not yet been received by the contact information management device 20, are displayed so as to be identifiable.

In the example shown in FIG. 8, a student with attendance number 1 in class 1, a student with attendance number 2 in class 1, and a student with attendance number 4 in class 1 are students registered in the terminal registration management table T4. (student ID) and is a student whose contact information has already been received.

In the contact information display field R1, the characters of the contact information that meet the preset conditions are displayed in red, and the other characters are displayed in black, thereby displaying the contact information that satisfies the preset conditions. You may make it highlight so that it can identify. In the example shown in FIG. 8, for example, "absence", "leaving early", and "late" in the "attendance" column and "poor condition" in the "physical condition" column are displayed in red. In addition, in the column of "measured temperature", temperature measurement results of 37.5 degrees or higher are displayed in red.

Also, in the example shown in FIG. 8, the student of class 1 attendance number 3 in the first grade is the student (student ID) registered in the terminal registration management table T4, and is the student whose contact information has not yet been received. As for this student's record, all the contact information columns are displayed as blank, as shown in FIG.

Also, in the example shown in FIG. 8, the student with attendance number 5 in class 1 of the first year is a student (unregistered person) who has not yet been registered in the terminal registration management table T4. For this student's record, as shown in FIG. 8, the column of contact information displays all "-" (hyphens), and the grade, class, and attendance number are displayed in red.

By displaying the contact information display column R1 as described above, the records of the students (child student IDs) registered in the terminal registration management table T4 and the records of the students (unregistered persons) who have not yet been registered in the terminal registration management table T4 can be displayed. ) and records of students registered in the terminal registration management table T4 but whose contact information has not yet been accepted by the contact information management device 20 can be displayed in a distinguishable manner.

Further, on the approver confirmation screen shown in FIG. 8, a "Download unreported persons (CSV)" button, a "Download list (CSV)" button, and a "Print" button are displayed.

Then, when the "Download unreported person (CSV)" button is selected, in the management unit 23 of the contact information management device 20, it is displayed in the contact information display field R1 based on the contact information management table T5. Of the records of each student registered, only the records of students who have been registered and whose contact information has not yet been received are extracted, and data in CSV format is generated. The management unit 23 then outputs the data in CSV format to the approver's terminal device 30 .

In addition, when the "download list (CSV)" button is selected, in the management unit 23 of the contact information management device 20, based on the contact information management table T5, all displayed in the contact information display column R1 data in CSV format containing student records of . The management unit 23 then outputs the data in CSV format to the approver's terminal device 30 .

Also, when the "Print" button is selected, the approver confirmation screen is output to a predetermined printing device and printed.

Next, the processing of the contact information management system 1 of this embodiment will be described in detail with reference to the flowchart shown in FIG.

First, the management unit 23 of the contact information management device 20 uses the school management table T1, the grade management table T2, the class management table T3, and the terminal registration management table T4 at midnight as described above. An information management table T5 is generated (S10). At this time, a contact information management table T5 is generated in which the contact information of each student has not yet been recorded.

Next, the guardian activates the guardian application installed in the registrant terminal device 10, displays a contact information setting input screen as shown in FIG. 2, and sets the contact information on the contact information setting input screen. Input is performed (S12), and contact information is output from the registrant terminal device 10 (S14). At this time, the student ID is also output from the registrant terminal device 10 as described above.

When the contact information and the student ID are output from the registrant terminal device 10 to the contact information management device 20, they are accepted by the contact information reception unit 22 of the contact information management device 20 (S16). Then, the management unit 23 refers to the contact information management table T5 generated in S10 based on the child/student ID received by the contact information receiving unit 22, and stores the child/student ID and The contact information received together is recorded (S18).

Next, when the approver of the school starts the approver application installed in the approver terminal device 30, the approver terminal device 30 requests the contact information management device 20 to output the contact information management table T5. A signal is output (S20).

When receiving the output request signal output from the approver terminal device 30, the management unit 23 of the contact information management device 20 sends the contact information management table T5 generated at the time of reception to the approver terminal device 30. Output (S22). In the contact information management table T5 output at this point, the contact information of the students that have already been accepted (contacted) is recorded, but the contact information of the students that have not yet been accepted (not contacted) is recorded. No information recorded. That is, the management unit 23 sequentially records the contact information received by the contact information receiving unit 22 in the contact information management table T5, and does not record the contact information that has not yet been received by the contact information receiving unit 22. Output contact information management table T5.

Then, the contact information management table T5 output from the management unit 23 is received by the approver terminal device 30, and the approver terminal device 30 displays the approver confirmation screen based on the contact information management table T5 (S24). ). Then, on the approver confirmation screen, as described above, the state where the contact information of the student who is the registrant is accepted, the state where the contact information of the student who is the registrant is not accepted, and the information of the unregistered person are displayed. be displayed in an identifiable manner.

According to the contact information management system 1 of this embodiment, based on the number of registered candidates (classes) and the identification information of registrants, the contact information of registrants and the information of unregistered persons are identified within the same system. Since management is made possible, it is possible to eliminate the complexity of management that occurs when identifying an unregistered person as in the conventional art.

In addition, in the contact information management system of the above-described embodiment, the state in which the contact information of the registrant is not accepted and the information of the unregistered person are managed in a distinguishable manner, so that confusion and mistake of these can be prevented. can be prevented.

In addition, in the contact information management system of the above embodiment, attendance numbers are added as identification information to all registered candidates (for example, all students). By doing so, an individual can be identified.

In addition, in the contact information management system of the above-described embodiment, the state in which the contact information of the registrant is accepted, the state in which the contact information of the registrant is not accepted, and the information of the unregistered person are identifiably displayed. Therefore, the approver can immediately recognize it by checking this display.

In addition, in the contact information management system of the above embodiment, since at least one edit of the contact information of the registrant and the contact information of the unregistered person is accepted, for example, a parent can temporarily use the terminal device to access the system. Even if the contact information management device 20 cannot access the contact information, the contact information can be edited. In addition, as for the contact information of the unregistered person, the separately obtained contact information can be recorded.

The following notes are further disclosed with respect to the present invention.
(Appendix)

In the contact information management device of the present invention, the management unit manages the state in which the contact information of the registrant is accepted, the state in which the contact information of the registrant is not accepted, and the information of the unregistered person so as to be identifiable. can be done.

In addition, in the contact information management device of the present invention, the management section can add identification information to all registered candidates.

In addition, in the contact information management device of the present invention, the management unit identifiably displays a state in which the contact information of the registrant is accepted, a state in which the contact information of the registrant is not accepted, and information on the unregistered person. can be made

Also, in the contact information management device of the present invention, the management unit can accept editing of at least one of the contact information of the registrant and the contact information of the unregistered person.

1 contact information management system 10 terminal device for registrant 20 contact information management device 21 storage unit 22 contact information reception unit 23 management unit 30 terminal device for approver R1 contact information display field R2 grade selection field R3 class selection field S1 body temperature input field S2 Health condition selection field S3 Message entry field S4 Pool participation availability selection field S5 Marathon participation availability selection field Tg1 to Tg3 Tag T1 School management table T2 Grade management table T3 Class management table T4 Terminal registration management table T5 Contact information management table

Claims (7)

a registrant identification information storage unit that stores pre-registered registrant identification information;
a contact information reception unit that receives contact information output from the registrant's terminal device;
a registered candidate information storage unit for storing information of registered candidates including the registrants and unregistered persons;
A contact information management device comprising: a management unit that manages the contact information of the registrant and the information of the unregistered person based on the information of the registration candidate and the identification information of the registrant. 2. The communication according to claim 1, wherein the management unit manages a state in which the contact information of the registrant is accepted, a state in which the contact information of the registrant is not accepted, and information of the unregistered person so as to be identifiable. Information management device. 3. The contact information management device according to claim 2, wherein said management unit adds identification information to all said registered candidates. 4. The management section according to claim 2 or 3, wherein a state in which the contact information of the registrant is accepted, a state in which the contact information of the registrant is not accepted, and information on the unregistered person are identifiably displayed. contact information management device. 5. The contact information management device according to any one of claims 1 to 4, wherein said management unit accepts editing of at least one of contact information of said registrant and contact information of said unregistered person. a step of storing pre-registered registrant identification information;
a step of receiving contact information output from the registrant's terminal device;
a step of storing information of registered candidates including said registrants and unregistered persons;
A contact information management program for causing a computer to execute a step of managing the contact information of the registrant and the information of the unregistered person based on the information of the candidate for registration and the identification information of the registrant. storing pre-registered identification information of registrants and information of registrant candidates including said registrants and unregistered persons;
Receiving contact information output from the registrant's terminal device,
A contact information management method for managing the contact information of the registrant and the information of the unregistered person based on the information of the registrant candidate and the identification information of the registrant.

Images