Invitation management device and program

Abstract

This reduces the burden of compiling a list of event invitees. [Solution] The invitation management device includes a display control unit that displays a candidate input screen, which is a screen for inputting identification information to identify the candidate invitee who is a candidate to be invited to the event, and an operation reception unit that receives an operation to exclude the candidate invitee from the invitee of the event.

Description

Technical Field

[0001] The present invention relates to an invitation management device and a program.

Background Art

[0002] Conventionally, a system has been proposed for assisting in sending invitation cards to guests for wedding receptions, second parties, etc. (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] When sending an invitation card to a guest, it is necessary to list up the guests. Such a listing operation may impose a workload on the organizer of the event. It is preferable that the workload of the organizer of the event can be reduced with respect to the listing operation.

[0005] An object of the present invention is to provide an invitation management device and a program capable of reducing the burden of the listing operation of the invitees of an event.

Means for Solving the Problems

[0006] One aspect of the present invention is an invitation management device including a display control unit that displays a candidate input screen which is a screen for inputting identification information for identifying an invitation candidate who is a candidate for an invitee to an event, and an operation reception unit that receives an operation for excluding the invitation candidate from the invitees of the event.

[0007] One aspect of the present invention is a program that causes a computer to display a candidate input screen, which is a screen for inputting identification information to identify a candidate who is a candidate to be invited to an event, and to accept an operation to exclude the candidate from being invited to the event. [Effects of the Invention]

[0008] According to the present invention, the burden of compiling a list of event invitees can be reduced. [Brief explanation of the drawing]

[0009] [Figure 1] This figure shows an example of the device configuration of the event management system according to this embodiment. [Figure 2] This figure shows an example of the functional configuration of the event management system of this embodiment. [Figure 3] This figure shows an example of the operation flow of the event management system of this embodiment. [Figure 4] This figure shows an example of the family and relatives setting screen in this embodiment. [Figure 5] This figure shows an example of a school-related settings screen (partial) of this embodiment. [Figure 6] This figure shows an example of the school-related settings screen (part of the remaining screen) in this embodiment. [Figure 7] This figure shows an example of a part of the workplace relationship settings screen of this embodiment. [Figure 8] This figure shows an example of the workplace relationship settings screen (part of the remaining screen) of this embodiment. [Figure 9] This figure shows an example of the acquaintance setting screen in this embodiment. [Figure 10] This figure shows an example of the invitation requirement setting screen in this embodiment. [Figure 11] This figure shows an example of the guest count screen in this embodiment. [Figure 12] This figure shows an example of the web invitation information selection screen of this embodiment. [Modes for carrying out the invention]

[0010] Next, the event management system 1 of this embodiment will be described with reference to the drawings. The embodiments described below are merely examples, and the embodiments to which the present invention is applied are not limited to the following embodiments. In all the drawings for explaining the embodiments, those having the same function are denoted by the same reference numerals, and repeated explanations are omitted. In addition, “based on XX” as used in the present application means “based on at least XX”, and includes cases where it is based on another element in addition to XX. Also, “based on XX” is not limited to the case where XX is directly used, and includes cases where it is based on something obtained by performing operations or processing on XX. “XX” is an arbitrary element (for example, arbitrary information).

[0011] (Embodiment) FIG. 1 is a diagram showing an example of the device configuration of the event management system 1 of this embodiment. The event management system 1 includes a guest terminal device 10, a host terminal device 20, and an event management device 30.

[0012] The guest terminal device 10, the host terminal device 20, and the event management device 30 can communicate with each other via a network NT. The network NT includes the Internet, a WAN (Wide Area Network), a LAN (Local Area Network), a public line, a provider device, a dedicated line, a wireless base station, and the like.

[0013] The event management system 1 can be connected via the network NT to an invitation printing server 40 of an invitation printing system 4 operated by a printing contractor or the like.

[0014] In the case where there are multiple guests G for an event, the guest terminal device 10 may be used one by one for each guest G. For example, when sending invitations to n guests G (n is a natural number), the guest terminal device 10 used by the first guest G may also be referred to as the guest terminal device 10-1. Similarly, the guest terminal device 10 used by the nth guest G may also be referred to as the guest terminal device 10-n.

[0015] The event management device 30 (invitation management device) functions as an arithmetic unit that operates a program to be processed by the guest terminal device 10 and the organizer terminal device 20, and a storage unit that stores data. For example, the event management device 30 functions as a so-called cloud server that provides various functions of the event management system 1. Note that some of the functions of the event management device 30 described below may be provided in the guest terminal device 10 or the organizer terminal device 20. That is, in the following description, some of the functions described as functions provided by the event management device 30 may be functions provided by the guest terminal device 10 or the organizer terminal device 20.

[0016] Both the guest terminal device 10 and the organizer terminal device 20 are computer devices such as so-called personal computers, tablets, and smartphones. The guest terminal device 10 includes a display unit 11 such as a liquid crystal display, an operation unit 12 such as a keyboard or a touch panel, an arithmetic unit 13 such as a CPU (Central Processing Unit), and a storage unit 14 such as a semiconductor memory or a hard disk device. Similarly, the organizer terminal device 20 includes a display unit 21, an operation unit 22, an arithmetic unit 23, and a storage unit 24.

[0017] [Function Configuration and Operation of Event Management System 1] The event management system 1 can be used for invitation management of various events if it is an invitation-type event. In one example of this embodiment, the event is a wedding reception or a so-called after-party following the reception. The organizer H is the couple getting married. Organizer H intends to invite their family, relatives, friends, colleagues (e.g., coworkers and superiors), and other people with whom they have a connection as guests G.

[0018] Organizer H may want to send electronic invitations to guest G via network NT. On the other hand, organizer H may want to send printed paper invitations to guest G, for example, a guest of honor or a guest G who is a supervisor at work. In this way, the organizer H can choose between an electronic invitation (hereinafter also referred to as a web invitation) or a paper invitation (hereinafter also referred to as a paper invitation) depending on the guest G.

[0019] Figure 2 shows an example of the functional configuration of the event management system 1 of this embodiment. Figure 3 shows an example of the operation flow of the event management system 1 of this embodiment. The following details of the functions of the event management system 1 will be explained with reference to Figures 2 and 3.

[0020] [Create a guest list] (Step S210) Organizer H operates the organizer terminal device 20 to create a guest list. The guest list is a compilation of information on guests G invited to the event hosted by organizer H.

[0021] The guest list is created by the organizer H operating the guest list settings screen P10 displayed on the display unit 21. The guest list settings screen P10 is prepared for each type of relationship between the organizer H and the guest G.

[0022] For example, on the guest list settings screen P10, (1) Family and relatives settings screen P1 (2) School-related settings screen P2 (3) Workplace-related settings screen P3 (4) Acquaintance settings screen P4 There are several options. The following explains each settings screen in order.

[0023] [Family and Relatives Settings Screen P1] Figure 4 shows an example of the family and relatives setting screen P1 of this embodiment. The family and relatives setting screen P1 is a screen for adding the family and relatives of the organizer H to the guest list. The family and relatives setting screen P1 includes four types of setting fields: family field P110, paternal relatives field P120, maternal relatives field P130, and neighbors and acquaintances field P140.

[0024] The Family section P110 is where you set the guest list for the organizer H's family, including parents, siblings, etc. The Family section P110 includes the Guest Settings section P111 and the Add Guest button P112. The Guest Settings section P111 displays the family members of organizer H who are registered in the guest list as Guest G. The Add Guest button P112 is an image of the operation performed when adding a family member to the guest list as Guest G.

[0025] The paternal relatives section P120 is where you set the guest list of the paternal relatives of the organizer H. The paternal relatives section P120 includes the guest settings section P121 and the guest add button P122. The guest settings section P121 displays the paternal relatives of the organizer H who are registered in the guest list as guest G. The guest add button P122 is an image of the operation performed when adding a paternal relative as guest G to the guest list.

[0026] The Maternal Relatives section (P130) is where you set the guest list of the organizer H's maternal relatives. The Maternal Relatives section (P130) includes the Guest Settings section (P131) and the Add Guest button (P132). The Guest Settings section (P131) displays the maternal relatives of the organizer H who are registered in the guest list as Guest G. The Add Guest button (P132) is an image of the operation performed when adding a maternal relative as Guest G to the guest list.

[0027] The "Neighbors and Acquaintances" section (P140) is where the organizer, H, sets up a guest list of people living nearby or acquaintances who have helped him. The "Neighbors and Acquaintances" section (P140) includes the "Guest Settings" section (P141) and the "Add Guest" button (P142). The "Guest Settings" section (P141) displays the neighbors and acquaintances of the organizer, H, who are registered in the guest list as Guest G. The "Add Guest" button (P142) is an image of the operation performed when adding a neighbor or acquaintance to the guest list as Guest G.

[0028] In other words, the display control unit 304 displays the guest list setting screen P10 (candidate input screen), which is a screen for inputting identification information to identify the invited candidates who are candidates for the guest G (inviter) to be invited to the event.

[0029] As mentioned above, the family and relatives settings screen P1 lists family members, relatives, and neighbors / acquaintances in that order, in order of social proximity from the perspective of the organizer H (for example, degree of kinship).

[0030] In other words, the display control unit 304 is a screen for inputting identification information to identify the invited candidates, who are candidates for the guest G (inviter) to be invited to the event. It displays a guest list setting screen P10 (candidate input screen), that is, a family / relative setting screen P1, in which the candidates are divided into multiple groups in order of their social proximity from the perspective of the organizer H.

[0031] Organizer H adds guest G to the guest list by using the add button in each field. The name used for guest G does not need to be guest G's official name; any name that identifies guest G is acceptable. This name that identifies guest G is also called identification information.

[0032] Identification information refers to information that can identify guest G, such as guest G's full name, the surname only, the given name only, or the name that organizer H uses to refer to guest G (for example, a nickname or common name).

[0033] The invitation information acquisition unit 301 (acquisition unit) acquires the identification information entered on the family / relative setting screen P1 (candidate input screen).

[0034] The invitation information acquisition unit 301 creates a guest list for the family / relative group based on the acquired identification information. In the following description, guest G included in the family / relative group guest list will also be referred to as family / relative group guest G.

[0035] The next button P15 is an operation image that is pressed when the guest list settings on the family / relative settings screen P1 are completed and the next screen is displayed. When the next button P15 is pressed, the organizer terminal device 20 displays the school-related settings screen P2 on the display unit 21.

[0036] [School-related settings screen P2] Figure 5 shows an example of the school-related settings screen P2 (partial) of this embodiment. Figure 6 shows an example of the school-related settings screen P2 (part of the remaining section) of this embodiment.

[0037] The School Relationship Settings screen P2 is for adding people related to the organizer H during their school days to the guest list. These people include classmates, upperclassmen, underclassmen, and teachers of the organizer H. The School Relationship Settings screen P2 includes five setting fields: Preschool / Kindergarten (P210), Elementary School (P220), Junior High School (P230), High School (P240), and University / Vocational School (P250).

[0038] The Nursery / Kindergarten Years section (P210) is where the guest list of people related to the organizer H during their nursery / kindergarten years is set. The Nursery / Kindergarten Years section (P210) includes the Guest Settings section (P211) and the Add Guest button (P212). The Guest Settings section (P211) displays the people related to the organizer H during their nursery / kindergarten years who are registered as Guest G in the guest list. The Add Guest button (P212) is an image of the operation performed when adding someone related to the nursery / kindergarten years as Guest G to the guest list.

[0039] The "Elementary School Years" section (P220) is where you set the guest list of people related to the organizer H during their elementary school years. The "Elementary School Years" section (P220) includes the guest settings section (P221) and the "Add Guest" button (P222). The guest settings section (P221) displays the people related to the organizer H during their elementary school years who are registered as Guest G in the guest list. The "Add Guest" button (P222) is an image of the operation performed when adding someone related to the organizer H during their elementary school years as Guest G to the guest list.

[0040] Similarly, the sections for junior high school (P230), high school (P240), and university / vocational school (P250) include fields displaying the individuals registered in the guest list for each period of the organizer H's school life, as well as operation images used when adding them as guests (G).

[0041] As shown above, the school-related settings screen P2 is arranged in chronological order of the organizer H's life, starting with preschool / kindergarten, elementary school, middle school, high school, and university / vocational school.

[0042] In other words, the display control unit 304 displays a screen for inputting identification information to identify the invited candidates, who are candidates for the guest G (inviter) to be invited to the event. This screen displays a guest list setting screen P10 (candidate input screen), or school-related setting screen P2, which is a screen for inputting identification information to identify the invited candidates, who are candidates for the guest G (inviter) to be invited to the event. The list is divided into multiple groups in chronological order of the timeline of the lives of the individuals up to the time the event occurred.

[0043] The invitation information acquisition unit 301 (acquisition unit) acquires the identification information entered on the school-related settings screen P2.

[0044] The invitation information acquisition unit 301 creates a guest list for school-related groups based on the acquired identification information. In the following description, guest G included in the guest list for school-related groups will also be referred to as guest G of the school-related group.

[0045] The next button P26 is an operation image that is pressed when the guest list settings on the school-related settings screen P2 are completed and the next screen is displayed. When the next button P26 is pressed, the organizer terminal device 20 displays the workplace-related settings screen P3 on the display unit 21. Furthermore, the school-related settings screen P2 may also display a "back button" (not shown) in addition to the next button P26. The back button is an operation image used to return to the previous screen (for example, the family and relatives settings screen P1). There may be cases where there are unentered items on the previous screen (for example, the family and relatives settings screen P1), or where, as a result of entering information on the school-related settings screen P2, the user may remember which guest G should be invited on the family and relatives settings screen P1. In such cases, having a back button improves the convenience for the organizer H who is performing the operation. The same applies to each of the following screens.

[0046] [Workplace-related settings screen P3] Figure 7 shows an example of the workplace relationship settings screen P3 (partial) of this embodiment. Figure 8 shows an example of the workplace relationship settings screen P3 (part of the remaining area) in this embodiment.

[0047] The Workplace Relationship Settings screen P3 is for adding people related to the organizer H's workplace (also called the place of employment; the same applies in the following explanation) to the guest list. People related to the workplace include the organizer H's superiors, senior colleagues, coworkers, junior colleagues, and, if the organizer H has changed jobs, people from their previous workplace. If the organizer H has changed jobs, their previous workplace is also abbreviated as the previous company. The Workplace Relationship Settings screen P3 includes five setting fields: Superior field P310, Senior colleague field P320, Coworker field P330, Junior colleague field P340, and Previous company field P350.

[0048] The Supervisor field P310 is where you set the guest list of supervisors at the organizer H's workplace. The Supervisor field P310 includes the Guest Settings field P311 and the Add Guest button P312. The Guest Settings field P311 displays the supervisors at the organizer H's workplace who are registered in the guest list as Guest G. The Add Guest button P312 is an image of the operation performed when adding a supervisor from the workplace as Guest G to the guest list.

[0049] Similarly, the Senior Staff section (P320), Colleagues section (P330), Junior Staff section (P340), and Previous Company section (P350) include fields that display individuals registered in the guest list who are affiliated with the organizer H's current or previous company, as well as operation images used when adding them as Guest G.

[0050] Thus, the workplace relationship settings screen P3 lists attendees in the order of superiors, seniors, colleagues, juniors, and former company contacts, in order of priority for event invitations within the organizational structure of the organizer H's workplace (for example, in order of social standing that makes it more appropriate to invite them, or in order of the degree to which they have helped the organizer).

[0051] In other words, the display control unit 304 displays a screen for inputting identification information to identify the invited candidates, who are candidates for the guest G (inviter) to be invited to the event. This screen displays a guest list setting screen P10 (candidate input screen), or workplace relationship setting screen P3, which is divided into multiple groups in order of workplace relationship.

[0052] The invitation information acquisition unit 301 (acquisition unit) acquires the identification information entered on the workplace relationship settings screen P3.

[0053] The invitation information acquisition unit 301 creates a guest list for the workplace group based on the acquired identification information. In the following description, guest G included in the workplace group guest list will also be referred to as workplace group guest G.

[0054] The next button P36 is an operation image that is pressed when the guest list settings on the workplace relationship settings screen P3 are completed and the next screen is displayed. When the next button P36 is pressed, the organizer terminal device 20 displays the acquaintance settings screen P4 on the display unit 21.

[0055] [Acquaintance Settings Screen P4] Figure 9 shows an example of the acquaintance setting screen P4 in this embodiment.

[0056] The acquaintance settings screen P4 is for adding acquaintances of organizer H other than those mentioned above to the guest list. Acquaintances of organizer H include people from organizer H's part-time job, people from hobby groups that share the same hobbies as organizer H, and other people who have helped organizer H (for example, the owner of their favorite cafe). The acquaintance settings screen P4 includes three types of setting fields: part-time job section P410, hobby section P420, and other section P430.

[0057] The Part-Time Worker section P410 is where you set the guest list of people associated with the organizer H's part-time job. The Part-Time Worker section P410 includes the Guest Settings section P411 and the Add Guest button P412. The Guest Settings section P411 displays the people associated with the organizer H's part-time job who are registered in the guest list as Guest G. The Add Guest button P412 is an image of the operation performed when adding people associated with the part-time job as Guest G to the guest list.

[0058] Similarly, the Hobbies section (P420) and the Other section (P430) include fields that display individuals registered in the guest list who are affiliated with the organizer H's current or former company, as well as operation images used when adding them as guest G.

[0059] Thus, the acquaintances settings screen P4 was not included in the family and relatives settings screen P1 through the workplace relationship settings screen P3, but it lists the people that organizer H might want to invite to the event.

[0060] The invitation information acquisition unit 301 (acquisition unit) acquires the identification information entered on the acquaintance setting screen P4.

[0061] The invitation information acquisition unit 301 creates a guest list for the other acquaintance group based on the acquired identification information. In the following description, guest G included in the guest list for the other acquaintance group will also be referred to as guest G of the other acquaintance group.

[0062] The Next button P44 is an operation image that is pressed when the guest list settings on the acquaintance settings screen P4 are completed and the next screen is displayed. When the Next button P44 is pressed, the organizer terminal device 20 sends the above-mentioned guest lists to the event management device 30.

[0063] In the following explanation, when the above-mentioned guest lists (guest list for family and relatives, guest list for school-related groups, guest list for work-related groups, and guest list for other acquaintance groups) are not distinguished, they will be collectively referred to as the guest list.

[0064] The invitation information acquisition unit 301 of the event management device 30 acquires the identification information of guests G entered for each screen of the guest list setting screen P10. Based on the acquired identification information, the invitation information acquisition unit 301 generates a guest list for each organizer H.

[0065] The guest list settings screen P10 is displayed separately for each event organizer H if there are multiple organizers H. For example, if the event is a wedding reception and the organizers H are the bride and groom, there are two organizers H. In this case, each organizer H (e.g., the bride and groom) will operate the guest list settings screen P10 separately to create their own guest list.

[0066] In other words, in this embodiment, the event has multiple organizers H (for example, the bride and groom). The display control unit 304 displays the guest list setting screen P10 (candidate input screen) for each organizer H. The invitation information acquisition unit 301 (acquisition unit) acquires identification information for each organizer H.

[0067] As explained above, the event management system 1 prompts the user to input identification information for each guest G to be listed in the guest list, according to the group to which guest G belongs. A group is a classification of guest G based on their attributes, such as family, relatives, friends, colleagues, or other people with whom they have a connection. In this embodiment, a group is also referred to as a "community."

[0068] In other words, the guest list setting screen P10 (candidate input screen) has fields for entering identification information that is categorized into multiple categories based on the relationship with the organizer H within the group.

[0069] Generally, deciding who to invite and who not to an event is a significant burden for the organizer, H. Furthermore, there's a risk that organizer H might forget to create a list of people they would have liked to invite, resulting in them being left out of the guest list.

[0070] In this embodiment, the event management system 1 has a guest list setting screen P10 configured to list guests G in order of the strength of their relationship with the organizer H. Alternatively, the event management system 1 has a guest list setting screen P10 configured to list guests G in order of chronological order of the organizer H's life.

[0071] For example, the groups on the guest list settings screen P10 include at least three groups: a first group for entering the family and relatives of the event organizer H (family and relatives settings screen P1), a second group for entering people related to organizer H from their school days (school-related settings screen P2), and a third group for entering people related to organizer H's workplace (workplace-related settings screen P3). The display control unit 304 displays the guest list setting screen P10 (candidate input screen) in the order of the first group, the second group, and the third group.

[0072] More specifically, the guest list settings screen P10 (candidate input screen) has fields for entering identification information that is categorized into multiple categories based on the relationship with the organizer H within the group. The first group is categorized based on the degree of kinship with the organizer, H. The second group is categorized in chronological order. The third group is categorized in order based on organizational structure.

[0073] Therefore, with the event management system 1 of this embodiment, the process of listing guests G is structured as a continuous flow, making it less likely for the organizer H to be interrupted. As a result, with the event management system 1, the organizer H can concentrate on the listing process, which reduces the likelihood of guests G being missed or omitted.

[0074] The organizer terminal device 20 transmits the guest list created based on the operations of organizer H described above to the event management device 30 as invitee information 51.

[0075] (Step S310) When the calculation unit 300 of the event management device 30 receives the invitee information 51 from the organizer terminal device 20, it stores it in the storage unit 390 as a guest list.

[0076] [Creating and editing invitation data] Once the guest list is created, the next step is to create and edit the content of the invitations. The event management system 1 of this embodiment provides various functions for creating and editing invitation data. The creation and editing of invitation data provided by the event management system 1 will not be explained in detail.

[0077] [Setting whether invitations are required] Next, we will explain the operation flow of setting whether an invitation is required using the event management system 1.

[0078] (Step S220) The organizer terminal device 20 receives an operation from organizer H to start setting whether or not to invite guest G. When the organizer terminal device 20 receives the operation to start setting whether or not to invite guest G, it displays the invitation requirement setting screen P5 on the display unit 21.

[0079] Figure 10 shows an example of the invitation requirement setting screen P5 of this embodiment. The invitation requirement setting screen P5 is a screen that displays the guests G registered in the guest list created in the above-described procedure, grouped by group.

[0080] The invitation requirement setting screen P5 includes the nursery / kindergarten section P510, the elementary school section P520, and the high school section P530. In the example of the invitation requirement setting screen P5 shown in the figure, only a portion of the school-related setting screen P2 is shown, while the other illustrations are omitted, as these correspond to the invitation requirement setting screens P1, P2, P3, and P4 mentioned above.

[0081] The nursery / kindergarten section on page 510 includes the guest display section on page 511, the invitation / request setting button on page 512, the guest addition button on page 513, and the number of planned invitees section on page 514.

[0082] The guest display area P511 is a field that displays a list of guests G registered in the guest settings area P211, among the guests G registered in the guest list created in the above procedure. In the following explanation, guests G registered in the guest settings area P211 will also be referred to as guests G of the nursery / kindergarten group.

[0083] The "Invite / Not Invite" button P512 is an image showing the operation where the organizer H can choose whether or not to invite guest G, who is displayed in the guest display area P511, to the event (for example, whether or not to send an invitation). Organizer H can use the "Invite / Not Invite" button P512 to decide whether or not to invite guest G.

[0084] In other words, the display control unit 304 displays an invitation requirement setting screen P5 (invitation operation acceptance screen) that accepts an operation to decide whether or not to invite the candidate indicated by the identification information entered in the guest list setting screen P10 (candidate input screen).

[0085] The "Add Guest" button (P513) is an image showing the operation to add guest G, who was not registered in the guest settings section (P211) of the school-related settings screen (P2) mentioned above, to the guest list of the school-related group.

[0086] The "Number of Invited Guests" column (P514) displays the number of Guests G registered in the school-related group's guest list (hereinafter also referred to as the "number of registered guests") and the number of Guests G registered in the school-related group's guest list who have been selected to be invited to the event (hereinafter also referred to as the "number of invited guests").

[0087] For example, the number of people to invite (page 514) will display the number of invitations in fractional format. For instance, the number of registered attendees will be displayed as the denominator, and the number of invitees as the numerator.

[0088] The following sections, P520 for elementary school students and P530 for high school students, also include fields corresponding to the guest display field P511, the invitation / invitation setting button P512, the guest addition button P513, and the number of planned invitees field P514, similar to the nursery / kindergarten section P510.

[0089] Here, within the school-related group, the subdivisions such as nurseries / kindergartens, elementary schools, junior high schools, high schools, universities / vocational schools are also called categories. In other words, a group includes multiple categories.

[0090] For example, a family and kinship group includes categories such as family, paternal relatives, maternal relatives, and neighbors / acquaintances. The workplace group includes categories such as superiors, senior colleagues, peers, junior colleagues, and people from previous companies. Other acquaintance groups include those from part-time jobs, hobby groups, and other general acquaintances.

[0091] As mentioned above, the number of people to invite (P514) displays the number of registered users and the number of people to invite in the nursery / kindergarten category. On the other hand, the number of people to be invited (page 524) displays the number of registered users and the number of people to be invited in the elementary school category. The "Number of people to invite" column (P534) displays the number of registered users and the number of people to invite in the high school category.

[0092] In other words, the display control unit 304 displays the number of guests G (inviters) to be invited to the event for each of several groups or categories classified based on the relationship between the organizer H and the invited candidates.

[0093] (Step S320) The organizer terminal device 20 transmits the invitation requirement setting information to the event management device 30. When the event management device 30 receives the invitation requirement setting information from the organizer terminal device 20, it associates the invitation requirement setting information with the guest list stored in step S310 and stores it in the storage unit 390.

[0094] The operation performed on the invitation requirement setting button P512, as described above, can also be described as an operation performed on the invitation acceptance screen to exclude the invited candidate from the event's guests G (inviters).

[0095] In other words, the operation reception unit 305 receives operations performed on the invitation operation reception screen to exclude an invitation candidate from the event's guests G (inviters).

[0096] Among the listed guests G, there may be some guests G who should not be invited to the event due to constraints on the number of participants due to the event venue or budget, or because their relationship with the organizer H is weaker compared to other guests G. After creating the guest list, the event management system 1 can set whether or not to invite each listed guest G to the event.

[0097] Therefore, according to the event management system 1, after listing potential guests G, it is possible to narrow down the guests G to be actually invited. For example, according to the event management system 1, it is possible to list guests G without considering constraints on the number of participants or the closeness of their relationship with the organizer H compared to other guests G.

[0098] In other words, the event management system 1 of this embodiment has a function to set the guest G to be invited in two stages: a listing stage in which a list of guest G candidates for invitation is compiled, and a filtering stage in which the guest G to be invited is narrowed down from the listed guest G.

[0099] With the event management system 1 configured in this way, there is no need to narrow down the list of guests G during the guest listing stage, so it is possible to easily identify who should be guests G without much deliberation during the listing stage. Thus, with the event management system 1 of this embodiment, the organizer H can concentrate on the listing work. Therefore, the event management system 1 can reduce the chances of guests G who should be invited being omitted from the guest list.

[0100] [Viewing Guest G's attendance response status] Figure 11 shows an example of the guest count screen P6 in this embodiment. The guest count screen P6 is a screen that displays the number of guests G that are scheduled to be invited. The guest count screen P6 includes the total number of guests column P61, the number of guests hosted by the organizer column P62, and the number of guests hosted by the organizer column P63.

[0101] The "Total Guests" column on page 61 displays the sum of the number of guests invited by person A (guest G) and the number of guests invited by person B (guest G).

[0102] Pages P62 and P63 of the "Number of Guests per Organizer" section display the number of guests G that each organizer H (for example, the bride and groom) intends to invite. For example, if the bride and groom, A and B, are planning to invite guest G to an event (for example, a wedding reception) as organizers H, the number of guest G invited by A will be displayed in the organizer guest count field P62. Additionally, the number of guest G invited by B will be displayed in the organizer guest count field P63.

[0103] In other words, the display control unit 304 displays the number of guests G (inviters) invited by each organizer H.

[0104] The group number display fields P621 and P631 are screens that display the number of guests G that each organizer H (for example, the bride and groom) intends to invite, separated by organizer H and by group.

[0105] As described above, in one example of this embodiment, the groups include family and relative groups, school-related groups, workplace groups, and other acquaintance groups. The group size display field P621 shows the number of people invited by person A to guest G, with the number of people invited by each group in the numerator and the number of registered guests in the denominator. The group size display field P631 shows the number of people invited by B to guest G, with the number of invited people per group in the numerator and the number of registered people in the denominator.

[0106] In other words, the display control unit 304 displays the total number of guests G (inviters) invited by each of the multiple organizers H, for each of the multiple organizers H classified into multiple groups or categories based on the relationship between the organizer H and the invited candidates.

[0107] As described above, the event management system 1 of this embodiment displays the number of guests invited by each organizer H (for example, the bride and groom) in comparison to the number of guests invited by each organizer H when multiple organizers H (e.g., the bride and groom) have individually created guest lists. With the event management system 1 configured in this way, it becomes possible to grasp at a glance the balance between the number of guests invited by one organizer H and the number of guests invited by another organizer H. Therefore, the event management system 1 can reduce the effort required when multiple organizers H need to adjust the number of guests invited.

[0108] The operation fields P622 and P632 for changing the number of guests are images used to change the number of guests G that each organizer H (for example, the bride and groom) intends to invite, both for each organizer H and for each group.

[0109] Note that both the number of guests change operation fields P622 and P632 may be initially set to invite all guests G.

[0110] The operation reception unit 305 accepts operations to change the number of guests (inviters) on a screen that displays the number of guests (inviters) for each of several groups or categories classified based on the relationship between the organizer H and the invited candidates. The display control unit 304 displays an invitation operation acceptance screen for each group or category, and when an operation to change the number of participants is accepted, it displays the invitation operation acceptance screen for the group or category for which the operation to change the number of participants was accepted.

[0111] With the event management system 1 configured in this way, multiple organizers H can easily increase or decrease the number of invitees while keeping track of the number of invitees, and the effort required to adjust the number of invitees can be reduced.

[0112] Furthermore, as described above, the event management system 1 of this embodiment does not consist only of invited guests G, but rather includes both invited guests G and guests G that are not invited. Therefore, with the event management system 1, when increasing the number of invited guests G, it is only necessary to select the uninvited guests G registered in the guest list. Thus, when increasing the number of invited guests G, the effort required to adjust the number of invitees can be reduced compared to the case where information on guests G must be registered in the guest list.

[0113] [Selection of the method for sending web invitations] Figure 12 shows an example of the Web invitation information selection screen P7 of this embodiment. The Web invitation information selection screen P7 is a screen for selecting the sending medium and response medium for the Web invitation.

[0114] The URL field P71 displays the URL of the web page where the response information 55 is entered. This URL is unique to each organizer H (or each event) and is issued by the event management system 1. A copy button P711 is displayed in the URL field P71. When organizer H operates the copy button P711, the URL displayed in the URL field P71 is temporarily stored in the storage unit 24 (so-called clipboard) of the organizer terminal device 20. When organizer H creates an invitation to guest G using the email software or SNS software running on the organizer terminal device 20 and performs a paste operation, the URL stored in the clipboard is pasted into the email or SNS message.

[0115] The QR code field P72 is for obtaining a QR code that shows the URL of the web page where the answer information 55 is entered. The QR code acquisition button P721 is displayed in the QR code field P72. When the organizer H operates the QR code acquisition button P721, the image information of the QR code showing the URL displayed in the URL field P71 is temporarily stored in the clipboard. When the organizer H creates an invitation to guest G using the email software or SNS software running on the organizer terminal device 20 and performs a paste operation, the image of the QR code stored in the clipboard is pasted into the text of the email or SNS message.

[0116] As mentioned above, the URL field P71 and the QR code field P72 are operated by the organizer H when using email or social networking services as the transmission medium and using a URL or QR code as the response medium.

[0117] The SNS section P73 is used when both the sending and replying methods utilize social networking services (SNS). The SNS section P73 displays the invitation preview section P731 and the send button P732. When the organizer H operates the send button P732, the text displayed in the invitation preview section P731 is sent via SNS. When guest G replies to the invitation received via SNS, the SNS reply is received as reply information 55 by the organizer H's SNS application. This SNS account may be a dedicated account created for each organizer H (or for each event), or it may be a personal account that organizer H normally uses.

[0118] Up to this point, we have explained the process of selecting the guest G to invite, and setting the specifications of the invitation, such as its design, content, sending method, and response method. Once the guest G to be invited and the invitation specifications are finalized, the next step is to send the invitation to guest G. Returning to Figure 3, we will explain the flow of the invitation sending process.

[0119] [Sending invitations] (Step S230) When the organizer terminal device 20 receives the invitation sending operation from organizer H, it sends an invitation sending instruction to the event management device 30. (Step S330) When the event management device 30 receives an invitation sending instruction from the organizer terminal device 20, it instructs the guest terminal device 10 and the invitation printing server 40 to send the invitations. The procedures for sending paper invitations and sending web invitations will be explained separately.

[0120] [Sending out paper invitations] Paper invitations are printed by an organization using the invitation printing system 4 (for example, a printing company) and sent to guest G. In step S330, the event management system 1 sends invitation data and address data as invitation order information 53 to the invitation printing server 40 of the invitation printing system 4, as information for creating paper invitations. The invitation data includes the design data for the printed surface of the paper invitation. The address data includes the official name and address information of guest G.

[0121] If the invitation order unit 311 is configured to print the reply-address code 532 on the paper invitation, it includes the information for printing the reply-address code 532 in the invitation order information 53 and sends it to the invitation printing system 4. The information for printing the reply-address code 532 is also called the reply-address information 531. Reply-to code 532 includes the string of the reply-to URL (Uniform Resource Locator), a QR code representing the reply-to URL, etc. However, reply-to code 532 does not include the string of the reply-to address (a string that allows a human to pinpoint its location on a map; for example, the home address of organizer H).

[0122] In other words, when a paper invitation (paper media) is selected as the type of mailing medium, the invitation ordering unit 311 outputs reply address information 531, along with information about guest G, for printing a reply address code 532 indicating the reply address on the computer system onto the paper invitation (paper media).

[0123] Furthermore, the invitation ordering unit 311 outputs invitation ordering information 53 (ordering information) which includes information about guest G, as well as instructions for delivering printed paper invitations (paper media) containing the event details to the event organizer.

[0124] (Step S410) The printing company receives invitation order information 53, which includes these invitation data and address data. (Step S420) The printing company generates print data based on the received invitation order information 53. The printing company prints and sends paper invitations based on the generated print data. In this case, the destination for the paper invitations is set in advance by the organizer H. Specifically, it is set whether the printed paper invitations are sent to the organizer H in a batch (for example, by mail or courier) or sent to each guest G. By setting it to be sent to the organizer H, the organizer H can check the finished paper invitations before they are sent to the guests G. On the other hand, by setting it to be sent directly to the guests G, the organizer H can avoid the trouble of mailing the paper invitations. In this case, the organizer H also needs to select the type of stamp to be attached to the paper invitations. The information for setting the destination for the paper invitations and the information for selecting the stamp when sending directly to the guests G is selected are included in the invitation order information 53.

[0125] In this example, the invitation printing system 4 is described as being used by an organization separate from the organization using the event management system 1 (for example, a printing company). However, this is not limited to this; the invitation printing system 4 may also be used by the organization using the event management system 1 (or related organizations such as subsidiaries or affiliates) as an integral part of the event management system 1. In other words, the organization using the event management system 1 may use the invitation printing system 4 to print paper invitations.

[0126] [Sending web invitations] On the other hand, in step S330, the web invitation is sent from the event management device 30 to the guest terminal device 10 used by each guest G. At this time, the web invitation is sent (for example, directly) without going through a system that creates paper invitations, such as the invitation printing system 4. As described above, the event management device 30 stores a guest list in its storage unit 390, which includes information about the recipients of guest G, such as their email addresses and SNS addresses. The event management system 1 sends invitation information 54 to the guest terminal device 10 based on the destination information for guest G included in this guest list.

[0127] (Step S110) When the guest terminal device 10 receives the invitation information 54, it displays an image based on the invitation information 54 (i.e., a web invitation) on the display unit 11. As described above, the web invitation includes access information to the input screen for the response information 55 via the response medium set by the organizer H (e.g., a URL, a QR code, an SNS account, etc.). (Step S120) Guest G uses the access information to the input screen to enter their attendance status for the event and a message to the organizer H as response information 55.

[0128] (Step S240) The reply receiving unit 331 of the event management device 30 receives the reply information 55 sent from the guest terminal device 10. The invitation ordering unit 311 stores the received reply information 55 in the storage unit 390. The attendance information acquisition unit 332 acquires attendance information for the event from the received reply information 55. Organizer H can use the organizer terminal device 20 to view the response information 55 stored in the memory unit 390 of the event management device 30.

[0129] Furthermore, if the organizer H receives a response from guest G in paper form, the organizer H will manually input the response details (attendance status, message, etc.) into the event management system 1. In other words, the event management system 1 in this embodiment also provides a function for manually inputting the content of responses to invitations.

[0130] [Summary of Embodiments] As described above, the event management system 1 of this embodiment can reduce the burden on the organizer H in compiling a list of event invitees.

[0131] Furthermore, the event management system 1 can also link the completed guest information to other systems (for example, a seating arrangement system or a system for ordering items such as wedding favors) for subsequent tasks such as creating seating charts.

[0132] Although embodiments of the present invention have been described in detail above with reference to the drawings, the specific configuration is not limited to these embodiments, and design modifications and the like are also included within the scope of the gist of the present invention. For example, a computer program to implement the functions of each of the above-mentioned devices may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be loaded into a computer system and executed. The term "computer system" here may include hardware such as an operating system and peripheral devices.

[0133] Furthermore, "computer-readable recording media" refers to writable non-volatile memory such as flexible disks, magneto-optical disks, ROMs, and flash memory, portable media such as DVDs (Digital Versatile Discs), and storage devices such as hard disks built into computer systems. Furthermore, "computer-readable recording media" also includes volatile memory (such as DRAM (Dynamic Random Access Memory)) within computer systems that act as servers or clients when programs are transmitted via networks such as the Internet or communication lines such as telephone lines, which retain programs for a certain period of time.

[0134] Furthermore, the above program may be transmitted from a computer system that stores the program in a memory device or the like to another computer system via a transmission medium or by transmission waves within the transmission medium. Here, the "transmission medium" used to transmit the program refers to a medium that has the function of transmitting information, such as a network (communication network) like the Internet or a communication line (communication line) like a telephone line. Furthermore, the above program may be intended to implement some of the functions described above. It may also be a so-called differential file (differential program) that can implement the aforementioned functions in combination with programs already recorded in the computer system. [Explanation of Symbols]

[0135] 1…Event management system, 10…Guest terminal device, 11…Display unit, 12…Operation unit, 13…Calculation unit, 14…Storage unit, 20…Organizer terminal device, 21…Display unit, 22…Operation unit, 23…Calculation unit, 24…Storage unit, 30…Event management device, 300…Calculation unit, 390…Storage unit

Claims

1. A display control unit that displays a candidate input screen, which is a screen for inputting identification information to identify potential invitees who are candidates to be invited to an event, An operation reception unit that receives an operation to exclude the aforementioned candidate from the list of invitees to the event, An invitation management device equipped with the following features.

2. The display control unit displays the number of invitees to the event for each of several groups or categories classified based on the relationship between the organizer and the invited guests. The invitation management device according to claim 1.

3. The aforementioned event had multiple organizers, The display control unit displays the number of invitees invited by each organizer. The invitation management device according to claim 1.

4. The display control unit displays the total number of invitees invited by each of the multiple organizers, categorized into multiple groups or categories based on the relationship between the organizers and the invited guests. The invitation management device according to claim 1.

5. The display control unit further displays an invitation operation reception screen that accepts an operation to decide whether or not to invite the candidate indicated by the identification information entered on the candidate input screen. The operation reception unit receives an operation performed on the invitation operation reception screen to exclude the invited candidate from the list of invitees to the event. The invitation management device according to claim 1.

6. The aforementioned operation reception unit receives an operation to change the number of invitees on a screen that displays the number of invitees for each of several groups or categories classified based on the relationship between the organizer and the invited candidates. The display control unit displays the invitation operation acceptance screen for each group or category, and when the operation to change the number of people is accepted, it displays the invitation operation acceptance screen for the group or category for which the operation to change the number of people was accepted. The invitation management device according to claim 5.

7. On the computer, The system displays a candidate input screen where the user enters identification information to identify potential invitees to the event. The system accepts the operation of excluding the aforementioned invited candidate from the list of invitees to the aforementioned event, A program to execute.

Images