Event management system and program

Abstract

To reduce a user's workload when selecting a type of a sending medium of an invitation with respect to an invitee of an event.SOLUTION: An event management system comprises an arithmetic unit of a computer device. The arithmetic unit: selects a type of a sending medium of an invitation with respect to an invitee of an event; and changes an input item of information about the invitee, according to the selected type of the sending medium.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an event management system and a program. [Background technology]

[0002] BACKGROUND ART Conventionally, a system has been proposed that supports sending invitations to guests of wedding receptions, wedding after-parties, and the like (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2013-178657 Summary of the Invention [Problem to be solved by the invention]

[0004] With the recent development of network technology, it is desirable to be able to send and receive invitations using a variety of media.

[0005] An object of the present invention is to provide an event management system and program that can reduce the workload of a user when selecting the type of medium for sending invitations to event invitees. [Means for solving the problem]

[0006] One aspect of the present invention is an event management system that includes a computing unit of a computer device that selects the type of medium for sending invitations to event invitees and changes the input items for information about the invitees depending on the selected type of medium.

[0007] One aspect of the present invention is a program for causing a computer to select the type of medium for sending invitations to event invitees and change the input items for information about the invitees depending on the selected type of medium. [Effects of the Invention]

[0008] According to the present invention, it is possible to obtain an effect of reducing the workload of a user when selecting the type of medium for sending invitations to event invitees. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram illustrating an example of a device configuration of an event management system according to an embodiment of the present invention. [Figure 2] FIG. 1 is a diagram illustrating an example of a functional configuration of an event management system according to an embodiment of the present invention. [Figure 3] FIG. 2 is a diagram illustrating an example of the flow of operations of the event management system according to the present embodiment. [Figure 4] FIG. 10 is a diagram illustrating an example of a guest list registration screen according to the present embodiment. [Figure 5] FIG. 10 is a diagram illustrating an example of a guest list screen according to the present embodiment. [Figure 6] FIG. 10 is a diagram illustrating an example of a guest editing screen according to the present embodiment. [Figure 7] FIG. 10 is a diagram illustrating an example of an invitation setting screen according to the present embodiment. [Figure 8] FIG. 10 is a diagram illustrating an example of an event setting screen according to the present embodiment. [Figure 9] FIG. 10 is a diagram illustrating an example of a Web invitation information selection screen according to the present embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of a guest list screen according to the present embodiment. [Figure 11] FIG. 10 is a diagram illustrating an example of a guest details screen according to the present embodiment. [Figure 12] FIG. 10 is a diagram showing an example of classification of guest information for creating an invitation card according to the present embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] Next, the event management system 1 of this embodiment will be described with reference to the drawings. The embodiment described below is merely an example, and the embodiments to which the present invention is applied are not limited to the following embodiment. In all the drawings for explaining the embodiments, the same reference numerals are used for components having the same functions, and repeated explanations will be omitted. Furthermore, in this application, "based on XX" means "based on at least XX," and includes cases where it is based on other elements in addition to XX. Furthermore, "based on XX" is not limited to cases where XX is used directly, but also includes cases where it is based on XX that has been calculated or processed. "XX" is any element (for example, any information).

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

[0012] The guest terminal device 10, the organizer terminal device 20, and the event management server 30 can communicate with each other via a network NT. The network NT includes the Internet, a wide area network (WAN), a local area network (LAN), a public line, a provider device, a dedicated line, a wireless base station, and the like. The event management system 1 can also connect via a network NT to an invitation print server 40 of an invitation print system 4 operated by a printing company or the like.

[0013] If there are multiple guests G at an event, one guest terminal device 10 may be used for each guest G. For example, if invitations are sent to n guests G (n is a natural number), the guest terminal device 10 used by the first guest G will also be referred to as guest terminal device 10-1. Similarly, the guest terminal device 10 used by the nth guest G will also be referred to as guest terminal device 10-n.

[0014] The event management server 30 functions as a computing unit that runs programs to be processed by the guest terminal device 10 and the host terminal device 20, and as a storage unit that stores data. For example, the event management server 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 server 30 described below may be provided in the guest terminal device 10 or the organizer terminal device 20. In other words, some of the functions described below as functions provided by the event management server 30 may be functions provided by the guest terminal device 10 or the organizer terminal device 20.

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

[0016] [Functional configuration and operation of Event Management System 1] The event management system 1 can be used to manage invitations to various events, as long as the events are invitation-based. In one example of this embodiment, the event is a wedding reception or a so-called after-party after the reception. The organizer H is the couple getting married. The organizer H intends to invite guests G, including their family, relatives, friends, coworkers (e.g., colleagues and superiors), and other people with whom they have a connection.

[0017] Here, guest G (for example, relatives or people with ties to the host) may include people whose email or SNS (Social Networking Service; also known as Social Media or Direct Message) addresses the host knows, but whose official names or addresses the host does not. For example, there may be a case where the host wants to invite a relative, "an uncle from Yokohama," as guest G. There may also be a case where the host wants to invite the "owner" of the place (for example, a cafe) where a couple first met as guest G. The event management system 1 provides a function that allows the organizer H to invite as guest G an "old man from Yokohama" or a "cafe owner" whose official name or official address he does not know.

[0018] In addition, the organizer H may wish to send an electronic invitation via the network NT to invite the guest G. On the other hand, the organizer H may wish to send a printed paper invitation to, for example, the guest G who is a guest of honor or the guest G who is the organizer's superior at work. In this way, it is preferable that the organizer H be able to select between an electronic invitation (also referred to as a web invitation in the following description) or a paper invitation (also referred to as a paper invitation 41 in the following description) depending on the guest G. The event management system 1 provides a function that allows a user to select a web invitation or a paper invitation 41 for each guest G or for each group to which the guest G belongs.

[0019] FIG. 2 is a diagram showing an example of the functional configuration of the event management system 1 of this embodiment. FIG. 3 is a diagram showing an example of the flow of operations of the event management system 1 of this embodiment. The functions of the event management system 1 will be described in detail below with reference to FIGS.

[0020] [Create guest list] (Step S210) The organizer H creates a guest list by operating the organizer terminal device 20. The guest list is a compilation of information about guests G who will be invited to an event that the organizer H is holding.

[0021] 4 is a diagram showing an example of a guest list registration screen P1 according to this embodiment. The guest list registration screen P1 is an image that displays summary information such as the number of guests G listed in a list format. The guest list registration screen P1 functions as the top screen when creating a guest list.

[0022] The display control unit 304 of the event management server 30 transmits information (display information 52) for displaying the guest list registration screen P1 to the organizer terminal device 20. The organizer terminal device 20 causes the display unit 21 to display the guest list registration screen P1. The guest list registration screen P1 includes a guest number screen P11 and a guest number screen P12. The guest number screen P11 and the guest number screen P12 are screens that display the number of guests G that each couple intends to invite, group by group. For example, if a couple, A and B, intend to invite guests G to an event (e.g., a wedding reception) as organizer H, the guest number screen P11 displays the number of guests G that A will invite. The guest number screen P12 displays the number of guests G that B will invite.

[0023] When the organizer H wants to check the details of the guests G, he operates the guest number screen P11 (or the guest number screen P12; the same applies in the following explanations) to display the guest list screen P2. When the display control unit 304 detects an operation by the host H on the guest count screen P11, it displays the guest list screen P2.

[0024] 5 is a diagram showing an example of the guest list screen P2 of this embodiment. The guest list screen P2 is a screen for displaying a list of guests G and editing (updating) information about the guests G. The guest list screen P2 has a group tab P21, an individual guest screen P22, an add guest button P23, and an invitation setting button P24.

[0025] The group tab P21 is an operation image for selecting a group to which the guest G belongs. A group is a classification of the guest G according to the guest G's attributes, such as the guest's family, relatives, friends, coworkers, and other people with whom the guest G has a connection. In this embodiment, a group is also called a "community."

[0026] That is, the event management system 1 manages the guests G by dividing them into a plurality of types.

[0027] The relationship between organizer H and guest G may differ from community to community. For example, if guest G is a friend of organizer H, they may have a relatively frank and relaxed relationship. On the other hand, if guest G is a coworker of organizer H, they may have a relationship that requires them to be relatively polite. The event management system 1 of this embodiment can classify guests G into communities. Therefore, according to the event management system 1, when the relationship between the organizer H and guests G differs for each community, the relationship can be managed collectively on a community basis, thereby reducing the management effort required by the organizer H.

[0028] The individual guest screen P22 is a screen that lists and displays the abbreviations of each guest G. Here, the abbreviations of guest G include the guest G's full name, the last name only, the first name only, the name that the organizer H uses to call guest G (for example, a nickname), etc. The abbreviations of guest G do not necessarily have to be the official name. The individual guest screen P22 includes an operation image for deleting the guest G and an operation image for editing the detailed information of the guest G (edit button P221).

[0029] The add guest button P23 is an operation image for adding a new guest G to the group (community).

[0030] When the edit button P221 or the add guest button P23 is operated, the display control unit 304 displays on the display unit 21 a guest edit screen P3, which is an image for editing detailed information about an individual guest G.

[0031] [Select invitation specifications for each guest group] 6 is a diagram showing an example of the guest edit screen P3 of this embodiment. The guest edit screen P3 is a screen for setting the attributes of the guest G and the specifications of the invitation for each individual guest G.

[0032] The guest editing screen P3 includes a guest relationship selection button P31, an invitation type selection field P32, and an address input field P33. The guest relationship selection button P31 is an operation image for setting the relationship between the host H and the guest G. The invitation type selection field P32 is an operation image for selecting the medium of the invitation. In this embodiment, the invitation type selection field P32 includes a Web invitation button P321 and a paper invitation button P322.

[0033] The Web invitation button P321 is an operation image for selecting to send a Web invitation to the guest G in question. The paper invitation button P322 is an operation image for selecting to send (also referred to as sending) a paper invitation 41 to the guest G.

[0034] The delivery medium selection unit 302 selects the type of delivery medium based on the operation by the organizer H on the invitation type selection field P32.

[0035] As described above, when inviting guest G, the organizer H may wish to send an electronic invitation (i.e., a Web invitation) via the network NT. On the other hand, the organizer H may wish to send a printed paper invitation (i.e., a paper invitation 41). The event management system 1 of this embodiment can set whether to send a web invitation or a paper invitation 41 for each guest G. In this way, the event management system 1 can select whether to send a web invitation or a paper invitation 41 within one system (or one screen). According to the event management system 1 configured in this manner, the organizer H can set the invitation sending method individually for each guest G, allowing him / her to respond flexibly to the relationship with the guest G, etc., thereby improving convenience when sending invitations.

[0036] The address input field P33 is an input screen that is displayed when the paper invitation button P322 is operated to select sending the paper invitation 41. The address input field P33 is an input field for entering the official address of the recipient of the paper invitation 41 (i.e., a character string that allows a postal or courier delivery person to identify the recipient of the paper invitation 41).

[0037] The input item control unit 303 controls whether the address input field P33 is displayed or hidden. That is, when the paper invitation 41 is selected, the input item control unit 303 controls to display the address input field P33. When the web invitation is selected, the input item control unit 303 controls to not display the address input field P33.

[0038] The display control unit 304 displays the guest editing screen P3 on the display unit 21 based on the control of the input item control unit 303. As a result, when the Web invitation button P321 is operated and sending a Web invitation is selected, the address input field P33 is not displayed on the guest editing screen P3.

[0039] That is, the delivery medium selection unit 302 selects the type of delivery medium for the invitation to the event to guest G. The display control unit 304 changes the input items for information about guest G according to the selected type of delivery medium.

[0040] As mentioned above, guest G (especially relatives or people with ties to the host) may include people whose email addresses or social media addresses the host knows, but whose official names or addresses the host does not. For example, the host may want to invite a relative, "an uncle from Yokohama," as guest G. Or, for example, the host may want to invite the "owner" of the place where the couple first met (e.g., a cafe) as guest G. In this example, organizer H may not know the official names or addresses of the "man in Yokohama" or the "cafe owner."

[0041] In this example, when sending an invitation to guest G whose official name and address are not known, if the entry of the official name and address is required, the setup for sending the invitation will not be complete until organizer H obtains (confirms) guest G's official name and address.

[0042] In the event management system 1 of this embodiment, for guests G whose official names and addresses are unknown, the guest can select to send a Web invitation by operating the Web invitation button P321. Organizer H can send an invitation to guest G (for example, the "cafe owner" or "the man in Yokohama" shown in Figure 5) whose email address or social media address he knows but whose official name or address he does not know, by selecting to send a web invitation.

[0043] So far, we have explained the case where the type of medium for the invitation is set individually for each guest G. Next, we will explain the case where the type of medium for the invitation is set for each group of guests G.

[0044] [Select invitation specifications for each community] 7 is a diagram showing an example of an invitation setting screen P4 of this embodiment. The invitation setting screen P4 is a screen for setting invitation specifications for each group (i.e., community) in which multiple guests G are classified according to their attributes. The figure shows an example of an invitation setting screen for the "friends" group, out of the above-mentioned "family and relatives," "friends," "work associates," and "other" groups. The invitation setting screen P4 includes a group invitation setting button P41.

[0045] The group invitation setting button P41 is an operation image for collectively setting the type of medium for invitations for all guests G who belong to the displayed group (for example, the "friends" group). When the group invitation setting button P41 is operated, the delivery medium selection unit 302 collectively sets the type of invitation medium (for example, Web invitation or paper invitation 41) for all guests G who belong to the same type of group. In other words, the group type is the type of guest G that is managed in multiple categories. The delivery medium selection unit 302 can also be said to associate the type of guest G that is managed in multiple categories (i.e., the type of group) with the type of invitation medium.

[0046] That is, the delivery medium selection unit 302 selects the type of delivery medium for the guest G by associating the type (group) of the guest G, which is managed in a plurality of groups, with the type of delivery medium.

[0047] In the event management system 1, the type of invitation medium can be set either by individual setting for each guest G shown on the guest editing screen P3 or by collective setting for each group shown on the invitation setting screen P4. In this case, the event management system 1 may treat the type of invitation medium set later as the valid setting (i.e., overwrite the setting), or may be set so that the setting content for each individual guest G always takes priority over the collective setting content for each group. The invitation specifications (for example, type of delivery medium) selected for each group (that is, community) on the invitation setting screen P4 can also be changed for each individual guest G on the guest editing screen P3.

[0048] In other words, the delivery medium selection unit 302 accepts an operation to change the type of delivery medium for an individual guest G, by associating the type of delivery medium with the type of guest G, which is managed in multiple categories.

[0049] With the event management system 1 configured in this way, the type of invitation medium can be set collectively for each group, and then changed individually for each guest G who needs to change the setting. Furthermore, if the settings individually set for each guest G are designed to take priority over the settings collectively set for each group, it is possible to prevent the carefully set individual settings from being overwritten by the collectively set settings. In other words, the event management system 1 reduces the effort required by the organizer H to set the type of invitation medium, improving convenience.

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

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

[0052] [Creating and sending invitation data] Once the guest list is created, the next step is to edit the contents of the invitations and send them. The event management system 1 of this embodiment provides various functions for creating and sending invitation data.

[0053] 8 is a diagram showing an example of the event setting screen P5 of this embodiment. The event setting screen P5 functions as a top screen for the procedure for sending invitations to the guests G listed in the above procedure. The organizer H operates the organizer terminal device 20 to select (or edit) the design of the invitation. Selecting (or editing) the design of the invitation is also called creating the invitation. The invitation design can be selected separately for the web invitation and the paper invitation 41. Note that the editing screen for designing the invitation is not shown in the figure.

[0054] (Step S220) When the organizer terminal device 20 accepts the operation to create the invitation by the organizer H, it transmits information indicating the operation result to the event management server 30. (Step S320) Upon receiving information indicating the operation result of the invitation creation operation from the organizer terminal device 20, the event management server 30 stores the invitation design created by the organizer H in the storage unit 390 as invitation data.

[0055] Next, a more specific workflow when a paper invitation 41 is selected and a more specific workflow when a Web invitation is selected will be described.

[0056] [If paper invitation is selected] If the paper invitation 41 is selected, the event management system 1 (1) 41 types of paper invitations (2) Whether to prepare a paper copy of the reply (3) Whether to print the reply address code 532 on the paper invitation 41 It provides various setting functions such as:

[0057] [1: Select the type of paper invitation] The organizer H can select the type of paper invitation 41 for each guest G (or for each group). The types of paper invitation 41 include the paper type (e.g., thickness, color, folding method, Japanese paper / Western paper, etc.), the design of the text on the paper invitation 41 (e.g., Japanese style / Western style, vertical writing / horizontal writing, whether illustrations are included, type of illustration, etc.), etc. The organizer terminal device 20 transmits the type of paper invitation 41 selected by the organizer H to the event management server 30. The invitation information acquisition unit 301 of the event management server 30 stores the type of paper invitation 41 selected by the organizer H in the memory unit 390 for each guest G (or for each group).

[0058] [2: Setting whether or not to require a reply form] The paper invitation 41 may include a reply form medium for replying to the organizer H regarding whether or not the guest G will be attending the event. The reply form medium is, for example, a postcard addressed to the organizer H and bearing the means of payment for the reply fee (for example, postage stamps or a notice of postage due to the recipient). The reply form medium may have the name of the guest G printed on it in advance. If a reply form is enclosed with the paper invitation 41, the guest G writes whether he / she will attend the event on the reply form (for example, a postcard) and returns it to the organizer H. The organizer H can operate the organizer terminal device 20 to set whether or not a reply form medium is provided. The invitation information acquisition unit 301 acquires the information set by the organizer H as to whether or not a reply form medium is required.

[0059] That is, the types of delivery media include paper invitations 41 (paper media). When a paper invitation 41 is selected as the type of delivery medium, the invitation information acquisition unit 301 acquires information about guest G using at least one of the input items of the type of paper invitation 41 and whether or not a reply paper medium is required.

[0060] [3: Reply-to code printing settings] The event management system 1 provides a setting function for determining whether or not to print a reply address code 532 on the paper invitation 41. By printing the reply destination code 532 on the paper invitation 41, the guest G can reply to indicate their attendance by reading the reply destination code 532 with the guest terminal device 10. The reply destination code 532 is information that can be read by the guest terminal device 10, such as a two-dimensional code that indicates a reply destination address (e.g., a URL) on a computer system. In this example, the guest terminal device 10 is equipped with an imaging unit such as a camera, and by capturing an image of the reply destination code 532 printed on the paper invitation 41, the web page of the reply destination address indicated by the reply destination code 532 is displayed on the display unit 11.

[0061] The event management system 1 configured in this way allows the guest G to reduce the effort of replying to the paper invitation 41 on paper (for example, a reply postcard). In addition, the organizer H can reduce the effort of manually inputting information such as attendance information returned by the guest G on paper into the event management system 1.

[0062] [If Web invitation is selected] If Web invitation is selected, the event management system 1 (1) Type of transmission medium and response medium (2) Editing the invitation text It provides various setting functions such as: The invitation text can also be edited using an existing text editor that runs on the organizer terminal device 20. A description of the invitation text editing function will be omitted. The following describes the function of selecting the type of transmission medium.

[0063] The web invitation is sent from the organizer H to the guest G as invitation information 54. When the guest G receives the invitation information 54, he or she can reply with information such as attendance at the event and a message as a response to the web invitation. The content of the response to the web invitation, such as attendance or a message, is also referred to as response information 55. In the following description, the means for sending the invitation information 54 to the guest G is also referred to as a transmission medium. The means for returning the response information 55, which is the guest G's response to the invitation information 54, to the organizer H is also referred to as a reply medium.

[0064] The sending medium for the web invitation is email, SNS, etc. The reply medium is the URL (link information or character string) of the web page that is the input screen for the answer information 55, a two-dimensional code representing this URL, SNS that displays the input screen for the answer information 55, etc.

[0065] In this way, the event management system 1 allows the selection of email or SNS as the transmission medium for web invitations, so that the organizer H can send event invitations even if he does not know the official name or address of the guest G. Furthermore, the event management system 1 provides a mechanism (for example, a URL, a two-dimensional code, or linkage with an SNS) for accessing the input screen for the response information 55 in the reply medium for the web invitation. This reduces the work of organiser H in compiling the response contents compared to when responses are received from guests G on paper.

[0066] 9 is a diagram showing an example of the Web invitation information selection screen P6 of this embodiment. The Web invitation information selection screen P6 is a screen for selecting a transmission medium for the Web invitation and a response medium.

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

[0068] The two-dimensional code field P62 is a field for acquiring a two-dimensional code indicating the URL of the web page for inputting the answer information 55. A two-dimensional code acquisition button P621 is displayed in the two-dimensional code field P62. When the organizer H operates the two-dimensional code acquisition button P621, image information of the two-dimensional code indicating the URL displayed in the URL field P61 is temporarily stored in the clipboard. When the organizer H creates an invitation addressed to the guest G using email software or SNS software running on the organizer terminal device 20 and performs a pasting (so-called paste) operation, the image of the two-dimensional code stored in the clipboard is pasted into the text of the email or SNS.

[0069] As described above, the URL field P61 and the two-dimensional code field P62 are operated by the organizer H when email or SNS is used as the transmission medium and a URL or two-dimensional code is used as the response medium.

[0070] The SNS field P63 is used when SNS is used as both the transmission medium and the reply medium. The SNS field P63 displays an invitation message preview field P631 and a send button P632. When the organizer H operates the send button P632, the text displayed in the invitation message preview field P631 is sent via SNS. When the guest G replies to the invitation received via SNS, the SNS reply is received as reply information 55 by the SNS application on the organizer H side. The SNS account may be a dedicated account created for each organizer H (or for each event), or may be a personal account that the organizer H normally uses.

[0071] So far, we have explained the process of setting the invitation specifications, such as the invitation design, content, transmission medium, and response medium. Once the invitation specifications have been finalized, the next step is to send the invitation to guest G. Returning to Figure 3, we will continue to explain the flow of operations of the event management system 1.

[0072] (Step S230) When the organizer terminal device 20 receives an invitation sending operation from the organizer H, it sends an invitation sending instruction to the event management server 30. (Step S330) When the event management server 30 receives the invitation sending instruction from the host terminal device 20, it instructs the guest terminal device 10 and the invitation print server 40 to send the invitation. The process of sending a paper invitation 41 and a Web invitation will now be described.

[0073] [Sending paper invitations] The paper invitation 41 is printed by an organization (for example, a printing company) that uses the invitation printing system 4 and sent to the guest G. In step S330, the event management system 1 sends the 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 the paper invitation 41. The invitation data includes design data for the printing surface of the paper invitation 41. The address data includes the official name and address of guest G.

[0074] When it is set that the reply destination code 532 is to be printed on the paper invitation 41, the invitation order unit 311 includes information for printing the reply destination code 532 in the invitation order information 53 and sends it to the invitation printing system 4. The information for printing the reply destination code 532 is also called reply destination address information 531. The reply destination code 532 includes a character string of the reply destination URL (Uniform Resource Locator), a two-dimensional code representing the reply destination URL, etc. Note that the reply destination code 532 does not include a character string of the reply destination address (a character string that allows a person to identify the location on a map, for example, the home address of organizer H).

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

[0076] In addition, the invitation ordering unit 311 outputs invitation ordering information 53 (ordering information) that includes information about guest G as well as instructions for delivering a paper invitation 41 (paper medium) with the event details printed on it to the event organizer.

[0077] (Step S410) The printing business receives invitation order information 53 including the 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 41 based on the generated print data. At this time, the recipient of the paper invitations 41 is set in advance by the organizer H. Specifically, the organizer sets whether to send the printed paper invitations 41 all at once to the organizer H (for example, by mail or courier) or to send them individually to each guest G. By setting the paper invitations 41 to be sent to the organizer H, the organizer H can check the finished paper invitations 41 before sending them to the guests G. On the other hand, by setting the paper invitations to be sent directly to the guests G, the organizer H can save the trouble of mailing the paper invitations 41. In this case, the organizer H also needs to select the type of postage to affix to the paper invitations 41. The setting information for the recipient of the paper invitations 41 and the postage selection information if sending directly to the guests G is selected are included in the invitation order information 53.

[0078] In this example, the invitation printing system 4 is described as being used by an organization (for example, a printing company) separate from the organization using the event management system 1, but this is not limited to this; the invitation printing system 4 may be used by the organization using the event management system 1 (or a related organization such as a subsidiary or affiliated company) as an integrated unit with 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 41.

[0079] [Web invitation sending process] On the other hand, in step S330, the Web invitation is sent from the event management server 30 to the invitee 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 a paper invitation 41, such as the invitation printing system 4. As described above, the event management server 30 stores in the storage unit 390 a guest list including destination information such as email addresses and SNS addresses of the guests G. The event management system 1 transmits the invitation information 54 to the invitee terminal device 10 based on the destination information for the guest G included in this guest list.

[0080] (Step S110) When the invitee terminal device 10 receives the invitation information 54, it displays an image (i.e., a Web invitation) based on the invitation information 54 on the display unit 11. As described above, the Web invitation includes access information (e.g., a URL, a two-dimensional code, an SNS account, etc.) to the input screen for the answer information 55 using the answer medium set by the organizer H. (Step S120) The guest G uses the access information to the input screen to input information 55 about whether or not he will be attending the event and a message to the organizer H.

[0081] (Step S240) The reply receiving unit 331 of the event management server 30 receives the response information 55 sent from the invitee terminal device 10. The invitation ordering unit 311 stores the received response information 55 in the storage unit 390. The attendance information acquiring unit 332 acquires information on attendance at the event from the received response information 55. The organizer H can use the organizer terminal device 20 to view the response information 55 stored in the storage unit 390 of the event management server 30.

[0082] If the guest G replies on paper, the organizer H manually inputs the response (attendance, message, etc.) into the event management system 1. In other words, the event management system 1 of this embodiment also provides a function for manually inputting the response to the invitation.

[0083] 10 is a diagram showing an example of a guest list screen P7 according to this embodiment. The guest list screen P7 is a screen that displays, in summary form, the responses from guests G to invitations. The guest list screen P7 displays, among the guests G to whom invitations were sent, the number of guests who responded that they will attend and the number of guests who responded that they will not attend. Furthermore, the event management system 1 of this embodiment can also include monetary payment information such as event participation fees and gifts in the response information 55. This monetary payment information indicates the amount to be paid by the guest G to the organizer H using a so-called cashless payment application. The guest list screen P7 may display a summary of the payment status of these payments.

[0084] 11 is a diagram showing an example of the guest details screen P8 of this embodiment. The guest details screen P8 is a screen that displays detailed information about the guest G listed in the guest list screen P7, such as the answers and contact information of the guest G.

[0085] That is, the reply to the invitation includes attendance information 551 regarding guest G's attendance at the event. The display control unit 304 displays the attendance request status for each guest G based on the attendance information 551 included in the received reply. As a result, the display unit 21 of the host terminal device 20 displays the attendance status for each guest G.

[0086] In the event management system 1 of this embodiment, the guest G's response to the invitation (for example, response information 55) includes fields for entering the guest G's official name and official address. When guest G responds to the invitation, he or she also writes down the official name and address of guest G. Therefore, organizer H can obtain guest G's official name and address from guest G's response. In other words, according to the event management system 1 of this embodiment, the organizer H can send an invitation to guest G without knowing the official name and address of guest G, and can further learn the official name and address of guest G from the response from guest G.

[0087] [Summary of the embodiment] As described above, the event management system 1 changes the information to be acquired from the organizer H before sending the invitation depending on the type of delivery medium. Specifically, if the delivery medium is a paper invitation 41 (i.e., a paper medium), the event management system 1 prompts the organizer H to input the official name and address of guest G. Furthermore, if the delivery medium is a web invitation (i.e., an electronic medium), the event management system 1 prompts the organizer H to input information to identify guest G, such as guest G's abbreviation (nickname or nickname), email address, or SNS address, but does not prompt the organizer H to input guest G's official name or address.

[0088] As described above, in this embodiment, information for identifying guest G, such as the nickname of guest G, email address, or SNS address, is also referred to as first information 511. Also, guest G's official name, address, etc. are also referred to as second information 512.

[0089] 12 is a diagram showing an example of classification of information of guest G for creating an invitation card according to this embodiment. As described above, the information items of guest G include official name, abbreviation (nickname or street name), official address, SNS account, email address, etc. In the figure, a circle (○) indicates a required input item, a triangle (△) indicates an optional input item, and a dash (-) indicates an unnecessary item. An x (×) indicates an unselectable combination. The name must be entered for the paper invitation 41, but is not required for the web invitation. The name belongs to the second information 512. Regarding abbreviations, they cannot be selected on paper invitations 41. Furthermore, on web invitations, the abbreviation is an optional field if the official name is known, but is required if the official name is not known. Abbreviations belong to the first information 511. The address must be entered for the paper invitation 41, but not for the web invitation. The address belongs to the second information 512. The SNS account and email address do not need to be entered for a paper invitation 41, but at least one of them is required for a web invitation. The SNS account and email address belong to first information 511.

[0090] Note that this classification is an example and is not limiting. For example, there may be cases where the mobile phone number of guest G is known and a web invitation can be sent using SMS (Short Message Service) of the mobile phone. In this case, the mobile phone number may be used as first information 511 instead of (or in addition to) the SNS account and email address described above.

[0091] In this way, the information regarding guest G includes first information 511, which is information for identifying guest G when sending the delivery medium, and second information 512, which is information regarding guest G that is of a different type from first information 511. The first information 511 includes, for example, a nickname (e.g., cafe owner), a nickname (e.g., the uncle from Yokohama), or other names that are not formal names. The first information 511 also includes contact information that is not a formal address, such as an SNS account, an email address, or a phone number for SMS. That is, the first information 511 includes information that allows the organizer H and the guest G to identify and contact each other as individuals, but makes it difficult for a third party (for example, a delivery company) to identify the individual. On the other hand, the second information 512 includes information that allows a third party (for example, a delivery company) to identify an individual, such as a formal name or a formal address. In addition to the above-mentioned information that makes it difficult to identify an individual, the first information 511 may also include information that allows a third party (for example, a delivery company) to identify an individual, such as a formal name or a formal address.

[0092] However, depending on the relationship between the organizer H and the guest G, there may be cases where the organizer H does not know the official name or address of the guest G before sending the invitation. Therefore, the event management system 1 provides a function that allows the organizer H to send an invitation without inputting the official name and address of the guest G as the first information 511.

[0093] That is, the first information 511 may not include at least one of the name and address of the guest G among the information for identifying the guest G.

[0094] Furthermore, if guest G responds to the invitation by filling in his / her official name and address, even if organizer H does not know guest G's official name or address, organizer H will be able to know guest G's official name and address from the response to the invitation.

[0095] In other words, if an invitation is sent to guest G using first information 511 and guest G's reply to the invitation includes second information 512, organizer H will be able to know guest G's official name and address.

[0096] That is, the event management system 1 acquires at least the first information 511 before sending the invitation, and acquires the second information 512 after the guest G replies to the invitation.

[0097] As described above, the host terminal device 20 acquires the second information 552 sent by the invitee terminal device 10 to the event management server 30 based on an operation by the guest G to whom the invitation was sent. This second information 552 (for example, the official name and address of guest G) can be used as the second information 512 described above.

[0098] The event management system 1 can also link the completed guest information to another system (for example, a seating arrangement system or a system for ordering items such as wedding favors) for subsequent creation of a seating chart, etc.

[0099] Although an embodiment of the present invention has been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like are also included within the scope that does not deviate from the gist of the present invention. For example, a computer program for implementing the functions of each of the above-described devices may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read and executed by a computer system. Note that the term "computer system" may include hardware such as an OS and peripheral devices.

[0100] In addition, "computer-readable recording medium" refers to writable non-volatile memory such as a flexible disk, optical magnetic disk, ROM, or flash memory, portable media such as a DVD (Digital Versatile Disc), or a storage device such as a hard disk built into a computer system. Furthermore, "computer-readable recording medium" also includes those that retain a program for a certain period of time, such as volatile memory (e.g., DRAM (Dynamic Random Access Memory)) within a computer system that serves as a server or client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line.

[0101] The program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by transmission waves in the transmission medium. Here, the "transmission medium" that transmits the program refers to a medium that has the function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. The program may also be a program for implementing some of the functions described above, or may be a so-called differential file (differential program) that can implement the functions described above in combination with a program already stored in the computer system. [Explanation of symbols]

[0102] 1...Event management system, 10...Invitee terminal device, 11...Display unit, 12...Operation unit, 13...Calculation unit, 14...Memory unit, 20...Organizer terminal device, 21...Display unit, 22...Operation unit, 23...Calculation unit, 24...Memory unit, 30...Event management server, 300...Calculation unit, 301...Invitation information acquisition unit, 302...Delivery medium selection unit, 303...Input item control unit, 304...Display control unit, 311...Invitation ordering unit, 312...Invitation sending unit, 331...Reply receiving unit, 332...Attendance information acquisition unit, 390...Memory unit, 4...Invitation printing system, 40...Invitation printing server, 41...Paper invitation, 51...Invitee information, 511...First information, 512...Second information, 52...Display information, 53...Invitation ordering information, 531...Reply-to address information, 532...Reply-to code, 5 4...Invitation information, 55...Response information, 551...Attendance information, 552...Secondary information, P1...Guest list registration screen, P11...Guest number screen, P12...Guest number screen, P2...Guest list screen, P21...Group tab, P22...Individual guest screen, P23...Add guest button, P24...Invitation setting button, P3...Guest editing screen, P31...Guest relationship selection button, P32...Invitation type selection field, P321...Web invitation button, P322...Paper invitation button, P34...Delivery address field, P4...Invitation setting screen, P41...Group invitation setting button, P5...Event setting screen, P6...Web invitation information selection screen, P61...URL field, P62...2D code field, P63...SNS field, P7...Guest list screen, P8...Guest details screen

Claims

1. A computing unit of a computer device, Selecting a type of medium for sending invitations to event invitees; changing input items for information about the invitee according to the selected type of delivery medium; An event management system comprising a computing unit that executes the above.

2. The information about the invitee includes first information, which is information for identifying the invitee when sending the delivery medium, and second information, which is information about the invitee that is different in type from the first information, The calculation unit acquiring at least the first information before sending the invitation; The second information is obtained after the invitee replies to the invitation. The event management system of claim 1 .

3. The first information does not include at least one of the name and address of the invitee among the information for identifying the invitee. The event management system of claim 2 .

4. The calculation unit The second information is acquired based on an operation by the invitee to whom the invitation was sent. The event management system according to claim 2 or 3.

5. The type of delivery medium includes paper media, The calculation unit When a paper medium is selected as the type of delivery medium, at least one of the items of the type of paper medium and whether a reply paper medium is required is input as the input item, and information about the invitee is acquired. The event management system of claim 1 .

6. The calculation unit When a paper medium is selected as the type of delivery medium, reply address information for printing a reply address code indicating a reply address on a computer system on the paper medium is output together with information about the invitee. The event management system of claim 5 .

7. The calculation unit Outputting order information including instructions for delivering paper media on which the details of the event are printed to the organizer of the event together with information about the invitees. The event management system according to claim 5 or 6.

8. a reply to the invitation containing attendance information regarding the invitee's attendance at the event; The calculation unit Displaying the attendance status for each invitee based on the attendance information included in the received reply The event management system of claim 1 .

9. The calculation unit The types of invitees are managed by dividing them into multiple categories. The event management system of claim 1 .

10. The calculation unit The type of the delivery medium for the invitee is selected by associating the type of the invitee, which is managed in a plurality of categories, with the type of the delivery medium. The event management system of claim 9.

11. The calculation unit The type of delivery medium for the selected invitee is associated with the type of delivery medium managed in a plurality of categories, and an operation to change the type of delivery medium for each invitee is accepted. The event management system of claim 10.

12. On the computer, Selecting a type of medium for sending invitations to event invitees; changing input items for information about the invitee according to the selected type of delivery medium; A program to execute.

Images