JP2012099095A - Banquet contracting support system, banquet contracting support program, and banquet contracting support method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a banquet contracting support system such that a user and a restaurant can be matched with each other and the restaurant side can know user's reactions.SOLUTION: The banquet contracting support system includes first reception means 111 of receiving transmission requests for desired banquet conditions from a user terminal and desired banquet conditions from a restaurant terminal; first storage means 121 of storing the desired banquet conditions; first retrieval means 112 of retrieving desired banquet conditions meeting conditions of the restaurant side; first transmission means 113 of transmitting the retrieved desired banquet conditions to the restaurant terminal; second reception means 114 of receiving banquet proposal conditions transmitted from the restaurant terminal for at least one of the desired banquet conditions; second storage means 122 of mutually linking and storing the banquet proposal conditions and corresponding desired banquet conditions; second retrieval means 115 of retrieving the banquet proposal conditions stored while linked to the desired banquet conditions from the banquet proposal conditions; and second transmission means 116 of transmitting screen configuration information for enabling the retrieved banquet proposal conditions to be browsed to the user terminal.

Description

  The present invention relates to a banquet agreement support system, a banquet agreement support program, and a banquet agreement support method using a communication network, and in particular, a banquet agreement that allows a user to make a banquet reservation for a restaurant or the like via a communication network. The present invention relates to a support system, a banquet agreement support program, and a banquet agreement support method.

  In recent years, using a personal computer that can be connected to the Internet (hereinafter also referred to as “PC”), a mobile phone, etc., a business provider (for example, a restaurant) that provides a service such as a banquet is selected. It is now possible to make a reservation for service provision by specifying (for example, Patent Document 1).

JP 2008-97050 A

  In the service provider selection support system disclosed in Patent Document 1, the service provider that can specify the contents (conditions) of the service that the user (person who wants to receive the service) wants to receive and can provide the specified service. The candidates can be narrowed down and the candidates can be asked to present prices and service contents, while the candidates can appeal to users for the selling points of services that they can provide. Then, after reaching the appeal deadline time, a list of the contents of the email transmitted from the service provider to the WEB server of the service provider selection support system is transmitted to the user terminal, and the user determines a store from the list of the mail contents. The store is inquired by telephone or ordinary e-mail (hereinafter also simply referred to as “mail”).

  However, on the user side, it is not possible to determine a store simply by looking at the list of email contents. When inquiring to multiple stores by email, the reply email from the store is another email. At the same time, the user's inbox is entered, and management of reply mail from the store may become complicated. In addition, after the store side appeals to the user about selling points of services that can be provided and additional services, whether the user is considering the appeal or not, if there is no reservation application However, it was not possible to know whether it was considered as a candidate or whether there was an appealing effect.

The present invention has been made in view of the above-described conventional problems. On the user side, a reply mail from a store is mixed with other mails (mails unrelated to store reservations). The purpose is to provide a banquet agreement support system and a banquet agreement support program that can be avoided.
In addition, the present invention is the effect of the appeal whether the appeal sent to the user is being considered at the shop side, whether the reservation application was not made when the reservation application was not made, but was considered as a candidate The purpose of the present invention is to provide a banquet agreement support system, a banquet agreement support program, and a banquet agreement support method that can know whether or not there has been.

In order to achieve the above object, the banquet closing support system of the present invention connects a user terminal used by a plurality of users and a store terminal used at a plurality of stores via a communication line, so that the user A banquet closing support system for supporting the closing of a reservation to use the store,
First receiving means for receiving banquet desired conditions and contact information from the user terminal;
First storage means for storing the banquet desired conditions and the contact information received by the first receiving means;
A search condition registered in advance for each store from one or a plurality of the banquet desired conditions stored by the first storage means when the store terminal requests transmission of the banquet desired conditions, or First search means for searching for the banquet desired conditions that satisfy the search conditions sent from the store terminal;
First transmission means for transmitting one or more banquet desired conditions searched by the first search means to the store terminal;
Second receiving means for receiving banquet proposal conditions transmitted from the store terminal for at least one of the banquet desired conditions transmitted by the first transmitting means;
Second storage means for storing the banquet proposal conditions in association with the corresponding banquet desired conditions;
Of the one or more banquet proposal conditions stored by the second storage means, stored in association with the banquet desired conditions transmitted from the user terminal that is the transmission source of the banquet desired conditions A second search means for searching for banquet proposal conditions when the user terminal is requested to view the banquet proposal conditions;
Second transmission means for transmitting to the user terminal screen configuration information capable of browsing one or more banquet proposal conditions searched by the second search means;
It is characterized by providing.

The banquet closing support system of the present invention further includes a third memory for storing status information that is a result of operation by the user terminal for each of the banquet proposal conditions transmitted to the user terminal by the second transmission unit. Having means,
The first transmission means also transmits the status information related to the banquet proposal conditions stored in association with the banquet desired conditions searched by the first search means to the store terminal,
The status information includes unanswered mail, opening of mail, determination of banquet closing, and deletion from reservation application candidates. The banquet closing support system of the present invention is further characterized in that the status information includes information related to registration in a favorite restaurant.

The banquet closing support method of the present invention is such that a user terminal used by a plurality of users and a store terminal used at a plurality of stores are connected via a communication line, and the user uses the store. A banquet closing support method that supports the closing of reservations for
Receiving search conditions from the store terminal, banquet desired conditions and contact information from the user terminal;
Storing the received search conditions, the banquet request conditions and the contact information;
Searching the banquet desired conditions satisfying the search conditions from the stored banquet desired conditions;
Sending a banquet wish list that lists the banquet wish conditions satisfying the search conditions to the store terminal;
Receiving from the store terminal a banquet desired condition detail screen request for requesting transmission of a banquet desired condition detail screen included in the banquet wish list;
Sending banquet desired condition detail screen configuration information corresponding to the banquet desired condition detail screen request to the store terminal;
Receiving banquet proposal conditions corresponding to the banquet desired conditions;
Storing the banquet proposal conditions in association with the corresponding banquet desired conditions;
Sending a banquet proposal list that lists the banquet proposal conditions stored in association with the banquet desired conditions to the user terminal;
Receiving, from the user terminal, a banquet proposal condition detail screen request for requesting transmission of a banquet proposal condition detail screen included in the banquet proposal list;
Transmitting banquet proposal condition detail screen configuration information corresponding to the banquet proposal condition detail screen request to the user terminal.

According to the banquet agreement support system, banquet agreement support program, and banquet agreement support method of the present invention, both the user (secretary) and the store have the following merits.
The user's merit is as follows.
Many shops can be compared on the WEB page, and proposals from the shops can be managed, making it easy to determine the shops.
Such a banquet closing support system is a system that can smoothly match a user and a shop that can satisfy the user's wishes, and is not merely a reservation application acceptance system.
The merits on the store side are as follows.
It is possible to grasp the status of the user's store selection (the progress of the store selection, such as whether or not it is under consideration), and even if it is not selected as a reservation application destination, it is possible to determine which stage by considering the store selection status. It can be inferred whether it has been excluded from the candidates for application in, and why it has been excluded from the candidates, so that it is possible to acquire a reservation application in another case.
In addition, it is possible to search for banquet requests of many users on the WEB page. Furthermore, on the WEB page, it is possible to make a proposal for the selected banquet request and efficiently manage the proposal made by the self (own store).

It is a figure which shows the whole structure of the banquet agreement support system which concerns on embodiment of this invention. It is a figure for demonstrating the flow of the process which concerns on embodiment of this invention. It is a figure for demonstrating the flow of the process which concerns on embodiment of this invention. It is a figure for demonstrating the flow of the process which concerns on embodiment of this invention. It is a flowchart for demonstrating the flow of the process which concerns on embodiment of this invention. It is a flowchart for demonstrating the flow of the process which concerns on embodiment of this invention. It is an example of a "shop comparison screen" according to an embodiment of the present invention. It is an example of the "delete from candidate" confirmation screen which concerns on embodiment of this invention. It is an example of the "delete from candidate" completion screen based on embodiment of this invention. It is an example of the mail management screen which concerns on embodiment of this invention. It is an example of the request content change screen which concerns on embodiment of this invention. It is an example of the demand deletion screen which concerns on embodiment of this invention. It is an example of the reply mail preparation screen which concerns on embodiment of this invention. It is an example of a "determine shop according to an embodiment of the present invention" screen. It is a flowchart for demonstrating the flow of the process which concerns on embodiment of this invention. It is an example of a “registration completion” mail, a “list addition notice” mail, a “store list” screen, a “mobile version store page” screen, and a “message from a store” screen according to an embodiment of the present invention. It is an example of a “list addition notice” mail, a “message history with store” screen, and a “past message” screen according to an embodiment of the present invention. It is an example of the "store list" screen, the "reply input" screen, and the "deletion confirmation" screen according to the embodiment of the present invention. It is an example of the status table which concerns on embodiment of this invention. It is an example of the "member store management" screen which concerns on embodiment of this invention. It is an example of a "notification mail reception setting" screen concerning an embodiment of the invention. It is an example of "notification mail" concerning an embodiment of the invention. It is an example of the sequence diagram which shows the flow of the process which concerns on embodiment of this invention.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. The technical scope of the present invention is not limited by the following embodiments.

<System configuration diagram>
FIG. 1 is a diagram showing an overall configuration of a banquet closing support system (hereinafter also referred to as “the present system”) according to an embodiment of the present invention. As shown in the figure, the user terminal 60 and the store terminal 70 can be connected to the system 100 via a communication network such as a mobile communication network 80 and the Internet 90.
The user terminal 60 and the store terminal 70 are a mobile phone having a Web browsing function, a mobile communication terminal, a personal computer, and the like, and can be connected to a communication network such as the mobile communication network 80 and the Internet 90 by wire or wireless.
The system 100 includes a first reception unit 111, a first search unit 112, a first transmission unit 113, a second reception unit 114, a second search unit 115, a second transmission unit 116, a first storage unit 121, and a second storage. Means 122 and third storage means 123.
The first storage unit 121, the second storage unit 122, and the third storage unit 123 do not need to be physically independent storage devices. For example, the first storage area, the second storage area, and the third storage area in one magnetic disk drive (HDD) are used as the first storage means, the second storage means, and the third storage means, respectively. Also good.

In the example shown in FIG. 2A, the first receiving means 111 receives the banquet desired condition 01 and the contact information 01 from the user terminal 60a, the banquet desired condition 02 and the contact information 02 from the user terminal 60b, and the user terminal 60c. The banquet request condition 03 and the contact information 03 are received.
The contact information is an e-mail address, a telephone number, or the like.

  In the example shown in FIG. 2B, the first storage unit 121 associates the banquet desired condition 01 with the contact information 01, associates the banquet desired condition 02 with the contact information 02, and associates the banquet desired condition 03 with the contact information. Each is associated with information 03. The first receiving unit 111 receives the search condition 01 from the store terminal 70a, the search condition 02 from the store terminal 70b, and the search condition 03 from the store terminal 70c.

  In the example shown in FIG. 3A, the first search means 112 searches for banquet desired conditions satisfying the search condition 01, and the first transmission means 113 stores the banquet desired conditions 01 to 03 obtained as a search result in the store terminal 70a. Send to. Moreover, the 1st search means 112 searches the banquet desired conditions which satisfy | fill the search conditions 02, and the 1st transmission means 113 transmits the banquet desired conditions 01-02 obtained as a search result to the shop terminal 70b. Further, the first search means 112 searches for banquet desired conditions satisfying the search condition 03, and the first transmission means 113 transmits the banquet desired conditions 01 obtained as a search result to the store terminal 70c.

  In the example shown in FIG. 3B, the second receiving means 114 includes a banquet proposal condition 0101 for the banquet desired condition 01, a banquet proposal condition 0201 for the banquet desired condition 02, and a banquet proposal condition 0301 for the banquet desired condition 03. And received from the store terminal 70a. Further, the second receiving means 114 receives the banquet proposal condition 0102 for the banquet desired condition 01 from the store terminal 70b. The banquet proposal condition for the banquet desired condition 02 is not transmitted from the store terminal 70b. Further, the second receiving means 114 receives the banquet proposal condition 0103 for the banquet desired condition 01 from the store terminal 70c.

In the example shown in FIG. 4A, the second storage unit 122 sets the banquet proposal condition 0101, the banquet proposal condition 0102, and the banquet proposal condition 0103 as the banquet desired condition 01, the banquet proposal condition 0201 as the banquet desired condition 02, The banquet proposal condition 0301 is associated with the banquet desired condition 03 and stored.
Further, the second receiving unit 114 receives browsing requests sent from the user terminals 60a to 60c.

The second search means 115 searches the banquet proposal conditions that are sent from the user terminal that is the source of the browsing request and stored in association with the stored banquet desired conditions. The search result is transmitted from the second transmission means 116 to the user terminal.
In the example shown in FIG. 4B, banquet proposal conditions 0101, 0102, and 0103 stored in association with the banquet desired condition 01 are transmitted to the user terminal 60a that has transmitted the banquet desired condition 01. These banquet proposal conditions are transmitted as a part of screen configuration information that constitutes a screen that can be browsed by the WEB browser on the user terminal 60a (a “compare shop” screen described later).
Similarly, the banquet proposal condition 0201 stored in association with the banquet desired condition 02 is transmitted to the user terminal 60b that has transmitted the banquet desired condition 02.
In addition, the banquet proposal condition 0301 stored in association with the banquet desired condition 03 is transmitted to the user terminal 60c that has transmitted the banquet desired condition 03.

<Overview>
FIG. 5 is a flowchart according to an example of the embodiment of the present invention. As shown in the figure, when a user registers a request (S101), a registration completion email is sent to the user's email address (S102), and a message email addressed to the user is sent to the system 100 from one or more shops. Sent (S103). When a predetermined URL in the message mail is clicked (S104), a transition is made to the store list screen (S105). Thereafter, for example, when the “Delete registration from candidate” button is pressed, the registration deletion screen is displayed, the registration is deleted (S106), and the registration deletion completion mail is sent to the mail address of the shop deleted from the candidate. It is transmitted (S107).

<First Embodiment>
<User side processing flow PC version>
The flow of processing on the user side of the PC version will be described with reference to FIG. As shown in the figure, the user accesses a predetermined URL from the user terminal (PC) and displays a request registration form on the display screen of the user terminal (S201).
When the user inputs a request (banquet request condition) in the request registration form and transmits it to the present system, a registration confirmation mail is transmitted from the present system to the user (S202).
If there is no approach from the store even if five days have passed since the request registration date (YES in S203), this system transmits a request deletion confirmation email (S223). If an email is sent from the store to the system before the elapse of 5 days (S204), an email notifying that the email has been sent from the store is sent from the system to the user, By clicking on the URL, a transition is made to a shop details list (hereinafter also referred to as “shop comparison screen” or “candidate shop list”) (S205).

<Compare shops>
FIG. 7 shows an example of a “shop comparison screen”. As shown in the figure, a “Delete from candidate” button 1101, a “Mail” button 1102, a “Register to favorite restaurant” button 1103, a check box 1104, and the like are displayed on the “shop comparison screen”.

<Compare shops and delete from candidates>
When the check box 1104 of “Compare shop screen” is checked and the “Delete from candidate” button 1101 is pressed (FIG. 6, S211), the shop corresponding to the checked check box 1104 is deleted from the candidate. The “delete from candidate” confirmation screen is displayed (S212).

FIG. 8 shows an example of the “delete from candidate” confirmation screen. As shown in the figure, on the “Delete from candidate” confirmation screen, the explanation 2111 of the effect caused by deleting from a candidate such as “If the specified store is deleted from the candidate list”, “Return” "Button 2112," delete "button 2113, etc. are displayed.
When the “Delete” button 2113 is pressed down, the information of the store whose check box 1104 is checked is deleted from the “Store comparison screen”, and the “Delete from candidate” completion screen is displayed (S213).

  FIG. 9 shows an example of the “delete from candidate” completion screen. As shown in the figure, a message 2121 indicating that the store has been deleted from the candidate such as “The store has been deleted from the candidate ....” is displayed on the “Delete from candidate” completion screen. In addition, when “return to candidate store list” 2122 is clicked, a transition is made to the “candidate store list” screen.

<Mail management>
When the “mail” button 1102 of the “shop comparison screen” 1100 is pressed (FIG. 6, S241), the screen changes to the mail management screen (S242).
FIG. 10 shows an example of the mail management screen. As shown in the figure, the mail management screen includes a list 1201 of shops that sent the message, a headline 1202 of each mail, a mail transmission date and time 1203, a mail text 1204, a “change request content” button 1205, and “request "Delete" button 1206, "To comparison list" button 1207, "Reply to shop" button 1208, "Determine this shop" button 1209, etc. are displayed.
Using such a mail management screen, messages such as questions from the user to the store, answers from the store to the user, suggestions from the store to the user, and the like are managed on the WEB.
When the “to comparison list” button 1207 is pressed, the screen changes to a “shop comparison” screen.

<Change request>
When the “change request content” button 1205 on the mail management screen 1200 is pressed (FIG. 6, S231), the screen changes to a screen for changing the content of the request (banquet desired conditions) (S232).
FIG. 11 shows an example of the request content change screen. As shown in the figure, the request content change screen includes a registrant / registration number display unit 1301, a visit date / time input unit 1302, an area input unit 1303, a number of people input unit 1304, a budget input unit 1305, a use purpose input unit 1306, a request. An input unit 1307, a reservation name input unit 1308, an organization name input unit 1309, a personal computer mail address input unit 1310, a mobile mail address input unit 1311, a received reply mail number input unit 1312, a “return” button 1313, and “change registered contents” ”Button 1314 and the like.
By increasing the numerical value of the reply mail reception number input unit 1312, the number of mails received from the store can be increased. When the “return” button 1313 is pressed, the screen changes to a “compare shop” screen. When the “change registered content” button 1314 is pressed, the desired registered content is changed, and the screen changes to the “change completed” screen (S233).

<Delete request>
When the “delete request content” button 1206 on the mail management screen 1200 is pressed (FIG. 6, S221), the screen shifts to a screen for deleting the content of the request (banquet desired conditions) (S222).
FIG. 12 shows an example of the request deletion screen. As shown in the figure, the request deletion screen includes an explanation 1501 about the effect caused by the request deletion, such as “When a request is deleted ...”, a radio button 1502 for selecting the reason for the request deletion, “ The button includes a “return” button 1503, a “delete” button 1504, and the like.
When the “return” button 1503 is pressed, the screen changes to a “compare shop” screen 1100. When the “delete” button 1504 is pressed down, the banquet desired conditions are deleted from the first storage unit 121 and the second storage unit 122. When the banquet desired conditions are deleted, a request deletion confirmation mail is transmitted (S223).

<Reply to store>
When the “Reply to Store” button 1208 on the mail management screen 1200 is depressed (FIG. 6, S251), the screen changes to a screen for creating a reply mail to the store (reply mail creation screen) (S252).
FIG. 13 shows an example of a reply mail creation screen. As shown in the figure, the “reply mail creation” screen includes a store name display portion 2171, a message display portion 2172 from the store, a desired date and time display portion 2173, a telephone number input portion 2174, a message input portion 2175 to the store, The button includes a “return” button 2176, a “confirm” button 2177, and the like.
When the “return” button 2176 is pressed, the screen transits to the mail management screen (FIG. 10).
When a message to be sent to the store is input to the message input unit 2175 and the “Confirm” button 2177 is pressed, a message is sent to the store (S253), and an email transmission screen (S 253) indicating that an email has been sent to the store. (S254). In addition, a copy of the transmission content is transmitted to the user as an email (S255).

<Determine the store>
When the “determine this store” button 1209 on the mail management screen 1200 is depressed (FIG. 6, S261), the “determined store information display and request deletion” screen (hereinafter also referred to as “determine store” screen). The process proceeds to 1400 (S262).
FIG. 14 shows an example of the “determine shop” screen. As shown in the figure, the “determine store” screen 1400 includes an explanation 1401 regarding the influence caused by the store determination such as “when a store is determined ...”, store information 1402, a telephone number input unit 1404, A store message input unit 1405, a “return” button 1406, a “determine store and delete registration” button 1407, and the like.
When the “return” button 1406 is pressed, the screen changes to a “compare shop” screen 1100. When the “determine store and delete registration” button 1407 is pressed, the determination is completed (S263), and the banquet desired conditions are deleted from the first storage unit 121 and the second storage unit 122. When the banquet desired conditions are deleted, a request deletion confirmation mail is transmitted (S223).

<Register in favorite restaurant>
When the “Register to Favorite Restaurant” button 1103 on the “Shop Comparison Screen” 1100 is pressed (FIG. 6, S271), the screen changes to a “Register to Favorite Restaurant” screen (not shown) (S272).

<Second Embodiment>
A case where the user terminal is a mobile terminal such as a mobile phone will be described with reference to the drawings.
<User-side processing flow Mobile version>
The flow of processing on the user side of the mobile version will be described with reference to FIG. As shown in the figure, the user accesses a predetermined URL from the user terminal (mobile device) and displays a request registration form on the display screen of the user terminal (S301).
When the user inputs a request (banquet request condition) in the request registration form and transmits it to the system, a registration confirmation mail is transmitted from the system to the user (S302).
If there is no approach from the store even after five days have passed since the request registration date (YES in S303), the system transmits a request deletion confirmation email (S323). If an e-mail is sent from the store before the elapse of 5 days (S304), an e-mail notifying that the e-mail has been sent from the store is sent from the system to the user, and a predetermined URL in the e-mail is clicked. By doing so, a transition is made to a store details list (hereinafter also referred to as “store list”) (S205).

<View store information and latest messages from notification emails>
FIG. 16 shows an example of a “registration completion” mail, “list addition notice” mail, “store list” screen, “mobile version store page” screen, and “message from store” screen.
The “registration completion” mail 1810 displays the registration number assigned by the system, the date and time input by the user, the area, the number of people, and the like.
Clicking on the URL for accessing the latest message displayed in the “List Addition Notice” mail 1830 makes a transition to the latest message browsing screen, and clicking on the URL for accessing a past message makes a transition to the past message browsing screen. When the URL for accessing the store list is clicked, the screen changes to a “store list” screen 1850.

  The “store list” screen 1850 displays the number of shops that can meet the request. Clicking “Change Request” makes a transition to the “Change Request” screen, clicks “Delete Request”, makes a transition to the “Delete Request” screen, and clicks a portion 1853 in which the name of the store is displayed, and a store page screen 1870 If a portion 1855 where “Respond with a message” is displayed is clicked, a “Message from store” screen 1890 is displayed.

The “mobile store page” screen 1870 displays information about the store such as a budget, telephone number, business hours, holidays, number of seats, presence / absence of a parking lot, availability of a credit card, and address.
The “message from the store” screen 1890 includes not only a message from the store but also a reply input unit 1891 to the store, a telephone number input unit 1892, an email address input unit 1893, and a “return to list” button 1894. Is displayed. When the “return to list” button 1894 is pressed down, a transition is made to the “store list” screen 1850.

<View past exchanges with the store via notification email>
FIG. 17 shows an example of a “list addition notice” email, a “message history with store” screen, and a “past message” screen.
A “list addition notification” mail 1910 is a mail notifying that a message from the store has arrived. When the URL 1911 on the “message history” screen is clicked, a transition is made to the “message history with store” screen 1920.

On the “message history with store” screen 1920, the user name, date, part of the message, store manager name, date, part of the message, and the like are displayed. When a part of the message is clicked, a “past message” screen 1930 is displayed.
The “past message” screen 1930 displays the full text of the selected message. When a “return” button 1931 is clicked, a transition is made to the “message history with store” screen 1920.

<Delete a store from the candidate list>
FIG. 18 shows an example of a “store list” screen, a “reply input” screen, and a “deletion confirmation” screen.
When “deletion of request” is clicked on the “store list” screen 2010, a transition is made to a “deletion confirmation” screen 2030.
When the “delete” button 2031 on the “delete confirmation” screen 2030 is pressed, the store is deleted from the candidate list. When the “return” button 2032 is pressed, the screen changes to a “store list” screen 2010.

<Common to PC and mobile terminals>
<Understanding user store selection status>
FIG. 19 shows an example of a status table stored in the third storage means. When a message sent from the store to the user via this system is opened at the user terminal, a value (for example, “1”) indicating that the message has been opened is input to the “open” column C201.
When a reply message is sent from the user to the store via this system, a value (for example, “1”) indicating that the reply has been sent is input to the “unanswered” column C202.
When the “determine store and delete registration” button 1407 in FIG. 14 is pressed, a value (for example, “1”) indicating that the store has been determined is input to the “determine” column C203.
When the “delete from candidate” button 1101 in FIG. 7 is pressed, a value (for example, “1”) indicating that the shop corresponding to the check box 1104 checked when the button is pressed is deleted from the candidate. Is entered in the “delete” column C204.
Further, when the “Register to Favorite Restaurant” button 1103 in FIG. 7 is depressed, the store corresponding to the depressed “Register to Favorite Restaurant” button 1103 is registered as “Favorite Restaurant” (favorite restaurant). The indicated value (for example, “1”) is input to the “Register to Favorite Restaurant” column C205.

  In the conventional reservation support system, it is possible to know the conclusion that the reservation is applied or not applied, but there is no way of knowing the process leading to the conclusion. However, in the contract support system described in the specification of the present application, by allowing the status information to be referred to, even if the store does not reach a banquet (reservation), the user's reaction to the store proposal (I didn't open the email, opened the email, wasn't chosen this time but was registered in a favorite restaurant, etc.). For this reason, even if the “reservation” is not established, it can be a customer collection tool that leads to the next visit.

FIG. 20 shows an example of the “member store management” screen. As shown in the figure, the “member store management” screen has a setting area part 2311, a status part 2312, a registration terminal part 2313, a desired date and time part 2314, a number of people part 2315, an amount part 2316, a “search with this condition” button 2317, The button includes a “cancel condition” button 2318, a search result display portion 2320, and the like.
In the initial state of the member store management screen, information related to banquet desired conditions with the area displayed in the setting area 2311 (“Ochanomizu, Iidabashi, Yotsuya” in the example of FIG. 23) as the desired area is displayed in the search result display section. 2320.
In addition, a search condition is set using a check box of the status part 2312, the registration terminal part 2313, a pull-down menu of the desired date / time part 2314, the number of people part 2315, and the amount part 2316, and a “search with this condition” button is set. When 2317 is depressed, information related to banquet desired conditions that satisfy the set search conditions is displayed on the search result display unit 2320.

<Request registration notification email function>
FIG. 21 shows an example of the “notification mail reception setting” screen. As shown in the figure, by checking a check box corresponding to a personal computer or a mobile terminal in the receiving method setting unit 2610, one or both of the personal computer and the mobile terminal can receive a notification mail. The number of people is specified using the number of people setting unit 2620, the budget is specified using the budget setting unit 2630, and the desired date is set using the desired date setting unit 2640, time setting unit 2650, day of week setting unit 2660, and usage purpose setting unit 2670. By specifying the time, day of the week, and purpose of use, conditions that do not match the needs of the store can be filtered out. It can be used for banquets with a large number of people or high-cost banquets.

  FIG. 22 shows an example of “notification mail”. As shown in the figure, in the notification mail, request contents 2710 such as date and time, area, number of people, budget, and request are described. When a message is sent to the secretary, a predetermined URL 2720 is clicked to change to the login screen of the management screen, and a login ID and a login password are input to log in to the management screen.

<Process flow>
In the case where the search conditions are received in advance from the store terminal, the flow of processing will be described based on the sequence diagram of FIG.
First, the system receives search conditions from the store terminal and banquet request conditions and contact information from the user terminal (step S2311).
The search conditions are “desired date”, “time”, “number of people”, “budget (per person)” and the like shown in FIG.
The system stores the received search criteria, banquet preferences and contact information.
The system searches for the banquet desired conditions satisfying the search conditions from the stored banquet desired conditions.
When the system receives a banquet wish list transmission request from the store terminal (step 2312), the system sends a banquet wish list in which banquet desired conditions satisfying the search conditions are listed to the store terminal (step S2313).
A banquet wish list is displayed on the screen of the store terminal, and when the store number is clicked on the registration number of the banquet request for which the desired content is to be confirmed in detail, a request to send the details screen of the banquet desired conditions is sent from the store terminal to the system. Sent to.
The system receives this banquet desired condition detail screen request (step S2314).
The system transmits banquet desired condition detailed screen configuration information corresponding to the banquet desired condition detailed screen request to the store terminal (step S2315).
Detailed banquet request conditions are displayed on the screen of the store terminal, and the store side confirms the user's banquet request conditions well. If the request can be met, a banquet proposal condition is created and transmitted to the system.
The system receives banquet proposal conditions corresponding to the banquet desired conditions (step S2316).

The system stores the banquet proposal conditions in association with the corresponding banquet desired conditions.
If the user wishes, the system sends an email to the user terminal notifying that the banquet proposal conditions have been received.
Next, when the system is requested to transmit a banquet proposal list in which the banquet proposal conditions stored in association with the banquet desired conditions are listed (step S2321), the banquet proposal list is transmitted to the user terminal. (Step S2322).
Next, when the system receives a banquet proposal condition detail screen request for requesting transmission of a banquet proposal condition detail screen included in the banquet proposal list from the user terminal (step S2323), the system responds to the banquet proposal condition detail screen request. The banquet proposal condition detailed screen configuration information is transmitted to the user terminal (step S2324).
The user (secretary) who confirmed the detailed banquet proposal conditions may send a message about the banquet proposal conditions to the store side via the system, or to the store side by telephone or the like without going through the system. good.

Based on FIG. 23, the case where the secretary's message is transmitted to the store via the system will be described.
When the user (secretary) message is received (step S2325) and the store side desires, the system transmits an email notifying that the message has been received from the user (secretary) to the store terminal (step S2331). ).
Next, when the system is requested to send a message list that lists the messages (step S2332), the system sends the message list to the store terminal (step S2333).
Next, when the system receives a message transmission request for requesting transmission of a message display screen included in the message list from the store terminal (step S2334), the system transmits a corresponding message to the store terminal (step S2335).
When the content of the message of the user (secretary) requires a reply from the store side, the message is transmitted from the store terminal, and the system receives the message (step S2336).
Note that it is preferable to create a message template for each store and store it in the system, since a message can be created based on this template, and the effort for message creation can be reduced.

If the user desires, the system transmits an email notifying that the message has been received from the store to the user terminal (step S2341).
Next, when the system is requested to transmit a message list that lists the messages (step S2342), the system transmits the message list to the user terminal (step S2343).
Next, when the system receives a message transmission request for requesting transmission of the message display screen included in the message list from the user terminal (step S2344), the system transmits a corresponding message to the user terminal (step S2345).

60 User terminal 70 Store terminal 80 Mobile communication network 90 Internet 100 Banquet closing support system

Claims (8)

A banquet closing support system for connecting a user terminal used by a plurality of users and a shop terminal used in a plurality of stores via a communication line to support the closing of a reservation that the user uses the store. Because
First receiving means for receiving a banquet request condition and contact information from the user terminal, a banquet request condition transmission request from the store terminal,
First storage means for storing the banquet desired conditions and the contact information received by the first receiving means;
When receiving a request for sending the banquet desired condition from the store terminal, a search condition registered in advance for each store from the one or more banquet desired conditions stored by the first storage means, or First search means for searching for the banquet desired conditions that satisfy the search conditions sent from the store terminal;
First transmission means for transmitting one or more banquet desired conditions searched by the first search means to the store terminal;
Second receiving means for receiving banquet proposal conditions transmitted from the store terminal for at least one of the banquet desired conditions transmitted by the first transmitting means;
Second storage means for storing the banquet proposal conditions in association with the corresponding banquet desired conditions;
Of the one or more banquet proposal conditions stored by the second storage means, stored in association with the banquet desired conditions transmitted from the user terminal that is the transmission source of the banquet desired conditions A second search means for searching for banquet proposal conditions when the user terminal is requested to view the banquet proposal conditions;
Second transmission means for transmitting to the user terminal screen configuration information capable of browsing one or more banquet proposal conditions searched by the second search means;
A banquet closing support system characterized by comprising: further,
Third storage means for storing status information that is a result of operation by the user's terminal for each of the banquet proposal conditions transmitted to the user terminal by the second transmission means,
The first transmission means also transmits the status information related to the banquet proposal conditions stored in association with the banquet desired conditions searched by the first search means to the store terminal,
2. The banquet closing support system according to claim 1, wherein the status information includes unanswered e-mail, opening of e-mail, determination of banquet closing, and deletion from reservation application candidates.   The banquet closing support system according to claim 2, wherein the status information includes information on registration in a favorite restaurant. A banquet closing support system for connecting a user terminal used by a plurality of users and a shop terminal used in a plurality of stores via a communication line to support the closing of a reservation that the user uses the store. In
Computer
First receiving means for receiving banquet desired conditions and contact information from the user terminal;
First storage means for storing the desired banquet conditions received by the first receiving means and the contact information;
A search condition registered in advance for each store from one or a plurality of the banquet desired conditions stored by the first storage means when the store terminal requests transmission of the banquet desired conditions, or First search means for searching for the banquet desired condition that satisfies the search condition sent from the store terminal;
First transmission means for transmitting one or more banquet desired conditions searched by the first search means to the store terminal;
Second receiving means for receiving a banquet proposal condition transmitted from the store terminal for at least one of the banquet desired conditions transmitted by the first transmitting means;
Second storage means for storing the banquet proposal conditions in association with the corresponding banquet desired conditions;
Of the one or more banquet proposal conditions stored by the second storage means, stored in association with the banquet desired conditions transmitted from the user terminal that is the transmission source of the banquet desired conditions Second search means for searching for banquet proposal conditions when the user terminal is requested to view the banquet proposal conditions;
Second transmission means for transmitting to the user terminal screen configuration information capable of browsing one or more of the banquet proposal conditions searched by the second search means;
A banquet closing support program characterized by functioning as Further, the computer
A third storage unit that stores status information that is a result of an operation performed by the user terminal for each of the banquet proposal conditions transmitted to the user terminal by the second transmission unit;
In the first transmission means, the status information regarding the banquet proposal conditions stored in association with the banquet desired conditions searched by the first search means is also transmitted to the store terminal,
5. The banquet closing support program according to claim 4, wherein the status information includes unanswered e-mail, opening of e-mail, determination of banquet closing, and deletion from reservation application candidates. A banquet closing support method for connecting a user terminal used by a plurality of users and a store terminal used in a plurality of stores via a communication line to support the closing of a reservation that the user uses the store Because
A first receiving step of receiving banquet desired conditions and contact information from the user terminal;
A first storage step of storing the received banquet request conditions and the contact information;
A search condition registered in advance for each store from the one or more banquet request conditions stored in the first storage step when transmission of the banquet request conditions is requested from the store terminal or A first search step of searching for the banquet desired condition that satisfies the search condition sent from the store terminal;
A first transmission step of transmitting one or more banquet desired conditions searched in the first search step to the store terminal;
A second receiving step of receiving a banquet proposal condition transmitted from the store terminal for at least one of the banquet desired conditions transmitted in the first transmission step;
A second storage step of storing the banquet proposal conditions in association with the corresponding banquet desired conditions;
The one or more banquet proposal conditions stored in the second storage step are stored in association with the banquet desired conditions transmitted from the user terminal that is the transmission source of the banquet desired conditions. A second search step for searching for banquet proposal conditions when the user terminal is requested to view the banquet proposal conditions;
A banquet closing support method, comprising: a second transmission step of transmitting to the user terminal screen configuration information capable of browsing one or more banquet proposal conditions searched in the second searching step. A banquet closing support method for connecting a user terminal used by a plurality of users and a store terminal used in a plurality of stores via a communication line to support the closing of a reservation that the user uses the store Because
Receiving search conditions from the store terminal, banquet desired conditions and contact information from the user terminal;
Storing the received search conditions, the banquet request conditions and the contact information;
Searching the banquet desired conditions satisfying the search conditions from the stored banquet desired conditions;
Sending a banquet wish list that lists the banquet wish conditions satisfying the search conditions to the store terminal;
Receiving from the store terminal a banquet desired condition detail screen request for requesting transmission of a banquet desired condition detail screen included in the banquet wish list;
Sending banquet desired condition detail screen configuration information corresponding to the banquet desired condition detail screen request to the store terminal;
Receiving banquet proposal conditions corresponding to the banquet desired conditions;
Storing the banquet proposal conditions in association with the corresponding banquet desired conditions;
Sending a banquet proposal list that lists the banquet proposal conditions stored in association with the banquet desired conditions to the user terminal;
Receiving, from the user terminal, a banquet proposal condition detail screen request for requesting transmission of a banquet proposal condition detail screen included in the banquet proposal list;
Transmitting banquet proposal condition detail screen configuration information corresponding to the banquet proposal condition detail screen request to the user terminal. A banquet closing support system for connecting a user terminal used by a plurality of users and a shop terminal used in a plurality of stores via a communication line to support the closing of a reservation that the user uses the store. In
On the computer,
Receiving search conditions from the store terminal, banquet request conditions and contact information from the user terminal;
Storing the received search conditions, the banquet request conditions and the contact information;
Searching the banquet desired conditions satisfying the search conditions from the stored banquet desired conditions;
Sending a banquet wish list that lists the banquet wish conditions satisfying the search conditions to the store terminal;
Receiving from the store terminal a banquet desired condition detail screen request for requesting transmission of a banquet desired condition detail screen included in the banquet wish list;
Sending banquet desired condition detail screen configuration information corresponding to the banquet desired condition detail screen request to the store terminal;
Receiving banquet proposal conditions corresponding to the banquet desired conditions;
Storing the banquet proposal conditions in association with the corresponding banquet desired conditions;
Sending a banquet proposal list that lists the banquet proposal conditions stored in association with the banquet desired conditions to the user terminal;
Receiving, from the user terminal, a banquet proposal condition detail screen request for requesting transmission of a banquet proposal condition detail screen included in the banquet proposal list;
And a step of transmitting banquet proposal condition detail screen configuration information corresponding to the banquet proposal condition detail screen request to the user terminal.

Images