JP7585129B2 - Information processing device and program - Google Patents

Description

An embodiment of the present invention relates to an information processing device and a program.

Conventionally, for example in restaurants and other establishments, systems have been used that accept orders from seated customers using terminal devices such as handheld terminals, and then notify the accepted data in the backroom, such as the kitchen.

However, in a business model where orders are taken at the tables, there may be cases where a seated customer puts their order on hold, or the number of people seated at a table is expected to increase because customers are waiting inside the restaurant. In these cases, it is cumbersome for the wait staff to have to periodically pay attention to the relevant table, and if the response is delayed contrary to the customer's intention, customer satisfaction will decrease, which is not desirable.

One of the problems mentioned above is the technology for dealing with the issue of putting orders on hold, which is disclosed in, for example, Patent Document 1. However, this technology does not take into account customers who are waiting.

The problem that this invention aims to solve is to prevent delays in serving customers when a seated customer puts an order on hold or when there is a waiting time inside the store.

The information processing device of the embodiment includes a waiting state writing unit that writes at least one of a waiting state for an order, which indicates that a customer has put an order on hold after sitting down, and a waiting state for a customer to be accompanied, which indicates that the seat is scheduled to have more people, to a specified memory unit in association with seat identification information, and a notification unit that periodically reads information about at least one of the seats in the waiting state for an order or the waiting state for a customer to be accompanied from the memory unit and notifies a customer service terminal used by a customer service staff member.

FIG. 1 is a diagram illustrating an example of a configuration of a customer service system according to an embodiment. FIG. 2 is a diagram illustrating an example of a hardware configuration of an order station according to an embodiment. FIG. 3 is a diagram illustrating an example of a functional configuration of an order station according to an embodiment. FIG. 4 is a diagram illustrating an example of a data configuration of the waiting state management storage unit according to the embodiment. FIG. 5 is a diagram illustrating an example of a seat information input screen according to the embodiment. FIG. 6 is a diagram illustrating an example of a current number of people input screen according to the embodiment. FIG. 7 is a diagram illustrating an example of an order waiting setting screen according to the embodiment. FIG. 8 is a diagram illustrating an example of the waiting-with-user setting screen according to the embodiment. FIG. 9 is a diagram illustrating an example of a flow of an alert process according to the embodiment. FIG. 10 is a diagram illustrating an example of an alert screen according to the embodiment. FIG. 11 is a diagram illustrating an example of a seat information input screen according to the embodiment. FIG. 12 is a diagram illustrating an example of the flow of the wait release process according to the embodiment. FIG. 13 is a diagram illustrating an example of the accompanying waiting cancellation confirmation screen according to the embodiment. FIG. 14 is a diagram illustrating an example of a product information storage unit according to a modified example. FIG. 15 is a diagram showing another example of the flow of the wait release process according to the modified example. FIG. 16 is a diagram showing another example of the waiting-with-user cancellation confirmation screen according to the modified example.

The embodiment will be described with reference to the drawings. FIG. 1 is a diagram showing an example of the configuration of a customer service system according to the embodiment. The customer service system is composed of an order station 100, a handheld terminal 200, a LAN (Local Area Network) 301, a router 302, a POS (Point Of Sales) terminal 400, a kitchen printer 501, a kitchen terminal 502, a server 503, etc.

The customer service system of this embodiment will be described below using as an example a restaurant, such as a coffee shop, that accepts orders after customers are seated. In such a store, the hall, where tables (seats) where customers can sit and eat are installed, is separated from the back yard, which includes the kitchen (cooking area). In the hall, customer service staff inputs customer orders into the handheld terminal 200, so that customer orders are accepted collectively for each seat.

The handheld terminal 200 is an example of a customer service terminal used by customer service staff, and includes a display device that displays information for the customer service staff, an operation device that accepts operations by the operator, and a control unit that controls these. The display panel is, for example, a liquid crystal panel. The operation device is, for example, a touch panel that is placed over the display panel and accepts operations according to the displayed content, a keyboard, or hard keys. The handheld terminal 200 notifies the order station 100 installed in the kitchen (or back yard) of the entered data.

The router 302 wirelessly connects the handheld terminal 200 to the LAN. The handheld terminal 200 wirelessly communicates with other devices (such as the order station 100) via the router 302 and the LAN 301.

Kitchen printer 501, kitchen terminal 502, and server 503 are specific examples of output devices installed in the back yard. Kitchen printer 501 and kitchen terminal 502 are installed in the kitchen. Kitchen printer 501 prints out information for kitchen staff (e.g., order details and waiting seat information described below) based on input information. Kitchen terminal 502 displays information for kitchen staff on a display device based on input information, and accepts operation input with an input device. Server 503 stores data for the GUI (Graphic User Interface) displayed by kitchen terminal 502, and provides (transmits) the data to kitchen terminal 502.

The POS terminal 400 obtains information from the order station 100 and performs accounting processing.

Figure 2 is a diagram showing an example of the hardware configuration of the order station 100. The order station 100 has a computer configuration including a CPU (Central Processing Circuit) 101, a ROM (Read Only Memory) 102, and a RAM (Random Access Memory) 103.

The CPU 101 is an example of a processor, and controls each part of the order station 100. The ROM 102 stores various programs. The RAM 103 is a workspace in which programs and various data are expanded.

The order station 100 also includes a communication I/F (Interface) 104 and a memory unit 120. The communication I/F 104 is a communication interface that can be connected to a router 302. The communication I/F 104 communicates with the order station 100 and the like via the router 302 and the LAN 301.

The memory unit 120 is composed of a storage medium such as a hard disk drive (HDD) or flash memory, and maintains the stored contents even when the power is cut off. The memory unit 120 stores programs that the CPU 101 can execute and various setting information. The CPU 101 executes various processes by operating according to the programs stored in the ROM 102 or the memory unit 120 and expanded in the RAM 103.

Note that the hardware configuration of the order station 100 is merely an example, and implementation is not limited to the configuration shown in FIG. 2. In addition, in this embodiment, the server 503 will be described as having the same hardware configuration as the order station 100.

The memory unit 120 of the order station 100 also stores a product information memory unit 121, a waiting state memory unit 122, etc. The product information memory unit 121 is a so-called product master, and stores product information such as the product name (product name) and price in association with a product code (an example of product identification information). The waiting state memory unit 122 will be described later.

Figure 3 is a diagram showing an example of the functional configuration of the order station 100. The CPU 101 of the order station 100 executes programs stored in the ROM 102 and the memory unit 120 to realize a control unit 110 that performs overall control of each unit of the order station 100. By executing various programs, the control unit 110 functions as a wait status writing unit 111, a notification unit 112, an output unit 113, and a wait release unit 114.

In this embodiment, some or all of the functional units of the order station 100 are described as being software configurations realized by cooperation between the processor (e.g., CPU 101) of the order station 100 and a program stored in a memory (e.g., ROM 102, storage unit 120). However, in practice, some or all of the functional units of the order station 100 may be hardware configurations realized by dedicated circuits or the like mounted on the order station 100.

The waiting state writing unit 111 updates the information stored in the waiting state memory unit 122 based on the input received via the handheld terminal 200 about tables (seats) in a waiting state. The waiting state writing unit 111 writes the type of waiting state into the waiting state memory unit 122 (an example of a specified memory unit) in association with the table number (an example of seat identification information). Types include "waiting for order," which indicates that a customer has put an order on hold after being seated, and "waiting for additional customers," which indicates that the seat is scheduled to accommodate more people.

Figure 4 is a diagram showing an example of the data configuration of the waiting state storage unit 122 according to the embodiment. The waiting state storage unit 122 stores the registration time of the data, the state of the target seat, the number of people, etc., in association with the identification number (table number) of the target seat (table). Here, the seat state can be "waiting for order", which indicates that a customer has put an order on hold after sitting down, or "waiting for accompanying customers", which indicates that a customer is waiting inside the store and that more people are expected to be seated later. In addition, in the case of a waiting for accompanying customers state, the waiting state storage unit 122 stores the number of people, including the current number of people and the number of people expected to be waiting for accompanying customers (the number of people who are ultimately expected to be seated).

The notification unit 112 periodically reads information about at least one of the seats that are in the order waiting state or the accompanying waiting state (waiting seat information) from the waiting state memory unit 122 and notifies the handheld terminal 200.

The output unit 113 outputs information (waiting seat information) about at least one of the seats that are in an order waiting state or a companion waiting state stored in the waiting state memory unit 122 to the kitchen printer 501, the kitchen terminal 502, or the server 503.

When the waiting release unit 114 receives a specific input via the handheld terminal 200 for any table (seat) in a waiting state, it updates the information stored in the waiting state storage unit 122 based on the content of the input. For example, the waiting release unit 114 releases the waiting state when an order is received from a customer at a seat stored in the waiting state storage unit 122 as being in a waiting state.

Figure 5 is a diagram showing an example of a seating information input screen 610 according to an embodiment. The input screen 610 is a screen displayed by the display device of the handheld terminal 200, and is a screen for inputting information about customers after they have sat down. This input screen 610 includes a new tab 611 and an additional tab 612, various items (table number 613, ticket number 614, number of people 615, person in charge number 616, waiting for orders 617, waiting for companions 618, etc.), and an operation/display field 619 used to display values and accept operations. The tabs 611, 612 and the operation/display field 619 are operated via a touch panel.

When the new tab 611 is selected, the input screen 610 accepts the input of information about the customer who has been shown to the vacant seat (the new customer who will be using the vacant table). When the add tab 612 is selected, the input screen 610 accepts the input of information related to the seating of a second customer for whom the seated customer was waiting. Note that the add tab 612 cannot be operated until the new tab 611 is selected and information is input from the input screen 610. The operation/display column 619 accepts the input of information about each of the adjacent items 613 to 618.

Figure 5 shows the state when the new tab 611 is selected. For example, when the operation/display field 619 adjacent to the number of people 615 is operated, the handheld terminal 200 displays a screen (Figure 6) for accepting input of the current number of people on the display device. The current number of people is the number of customers who have been guided to vacant seats (customers who will newly use the vacant table).

FIG. 6 is a diagram showing an example of a current number of people input screen 620 according to an embodiment. The current number of people input screen 620 includes an input value display field 621, numeric keypads 622, a clear key 623, and a confirm/back button 624. The numeric keypads 622 are a keypad including 10 keys on which the numbers 0 to 9 are displayed. The input value display field 621 displays the numerical value input by the numeric keypads 622. The clear key 623 erases the numerical value displayed in the input value display field 621.

When the Confirm/Back button 624 is operated, the display on the display device of the handheld terminal 200 returns to the input screen 610. If a number is displayed in the input value display field 621 when the Confirm/Back button 624 is operated, that number is determined as the value of the number of people 615 and is displayed in the operation/display field 619 next to the number of people 615 on the input screen 610.

An example of determining the value of the number of people 615 has been explained using Figure 6, but for the table number 613 and person in charge number 616, an input screen similar to the current number of people input screen 620 is used, which includes an input value display field, number keys, clear key, and enter/return key.

Returning to FIG. 5, when the operation/display field 619 adjacent to the order waiting field 617 is operated, the handheld terminal 200 displays a screen (FIG. 7) for setting the order waiting state on the display device.

Figure 7 is a diagram showing an example of an order waiting setting screen 630 according to an embodiment. The order waiting setting screen 630 includes a Yes button 631, a No button 632, and a Back button 633.

The Yes button 631 accepts a declaration that the seat is waiting for an order. When the Yes button 631 is operated, the handheld terminal 200 outputs information indicating that the seat is waiting for an order to the order station 100. This causes the fact that the seat is waiting for an order to be registered in the waiting state storage unit 122. The No button 632 accepts a declaration that the seat is not waiting for an order. When the No button 632 is operated, the handheld terminal 200 deletes the corresponding record from the waiting state storage unit 122.

When the Yes button 631 or No button 632 is operated, the display on the display device of the handheld terminal 200 returns to the input screen 610. When the Back button 633 is operated, the display on the display device of the handheld terminal 200 returns to the input screen 610. When the Yes button 631 is operated to return to the input screen 610, "Yes" is displayed in the operation/display column 619 next to Waiting for order 617.

Returning to FIG. 5, when the operation/display field 619 adjacent to waiting for companion 618 is operated, the handheld terminal 200 displays a screen (FIG. 8) for setting the waiting for companion state on the display device.

Figure 8 is a diagram showing an example of a waiting-with-person setting screen 640 according to an embodiment. The waiting-with-person setting screen 640 includes a Yes button 641, a No button 642, and a Back button 643.

When the Yes button 641 is operated, the handheld terminal 200 displays on the display device a planned number of people input screen 650 for accepting input of the planned number of people. The planned number of people is the number of people who are expected to be seated at the table at the end of the meeting. The planned number of people input screen 650 has the same configuration as the current number of people input screen 620 in Figure 6, so a detailed explanation will be omitted.

When the Confirm/Back button 624 is operated on the planned number of people input screen 650, the display on the display device of the handheld terminal 200 returns to the input screen 610. If a number is displayed in the input value display field 621 when the Confirm/Back button 624 is operated, that number is determined as the value of the planned number of people and recorded in the waiting state memory unit 122, and is displayed in the operation/display field 619 next to waiting for companions 618 on the input screen 610.

The None button 642 accepts a declaration that the seat is not in a waiting state, and deletes the corresponding record from the waiting state memory unit 122. When the None button 642 is operated, the display on the display device of the handheld terminal 200 returns to the input screen 610. When the Back button 643 is operated, the display on the display device of the handheld terminal 200 returns to the input screen 610.

Figure 9 is a diagram showing an example of the flow of the alert process according to the embodiment. This process is performed by the notification unit 112. First, the notification unit 112 reads out the waiting seat information from the waiting state storage unit 122 (step S1). Next, the notification unit 112 performs an order waiting seat alert (step S2) and a companion waiting seat alert (step S3) based on the information read out in step S1. Note that here, steps S2 and S3 are shown separately, but they do not have to be separated in practice. In addition, in the order waiting seat alert and companion waiting alert, specifically, the notification unit 112 transmits the waiting seat information read out in step S1 to the handheld terminal 200, the kitchen printer 501, and the kitchen terminal 502. Then, the notification unit 112 waits for a predetermined time (e.g., 5 minutes) to elapse (No in step S4), and when the predetermined time has elapsed (step S4), the process returns to step S1.

Figure 10 is a diagram showing an example of an alert screen 660 according to an embodiment. When the handheld terminal 200 receives waiting seat information from the notification unit 112, the handheld terminal 200 displays the alert screen 660 on the display device in the form of a dialog box (pop-up display) superimposed on the currently displayed screen. However, the handheld terminal 200 may operate not to display the alert screen 660 while accepting an operation. The alert screen 660 includes, for example, a list 661 that displays waiting seat information and a back button 662 that closes the alert screen 660.

The list 661 displays, for example, the type of waiting status and the time this data was registered in association with the table number. If the type of waiting status is "waiting for a companion," for example, if the expected number of people is three and the current number is one, adding "1/3" or the like is convenient for the wait staff to visually check the table and compare it with the actual number of people seated.

Figure 11 is a diagram showing an example of a seating information input screen 610 according to an embodiment. In Figure 11, the additional tab 612 is selected. In this state, a set of information has already been input in the operation/display field 619. When the second customer who the seated customer was waiting for sits down, the customer service staff displays the input screen 610 with the additional tab 612 selected on the handheld terminal 200 as shown in Figure 11, and accepts an order from at least the second customer.

Figure 12 is a diagram showing an example of the flow of the wait release process according to the embodiment. This process is performed by the wait release unit 114. First, when the handheld terminal 200 accepts an input related to an order using a well-known method, the contents of the order are sent to the order station 100 (step S11). When an order is placed at the order station 100, the wait release unit 114 refers to the wait state storage unit 122 and checks whether the seat of the orderer is in a wait state (step S12).

If the seat of the orderer is in a waiting state in step S12 (Yes in step S12), the waiting release unit 114 sends information to the handheld terminal 200 to display a release confirmation message (step S13).

Figure 13 is a diagram showing an example of a confirmation screen 670 for canceling waiting with a user according to an embodiment. The handheld terminal 200 displays the confirmation screen 670 for canceling waiting with a user upon receiving information transmitted from the order station 100. The confirmation screen 670 for canceling waiting with a user includes a message 671, a cancel button 672, and a back button 673.

Message 671 is, for example, "We are waiting for your companion. If you are all together, please cancel." When the customer sees this, the waiter asks the customer, "Are you all together?" and operates the cancel button 672 if the customer responds that all the people are together. If the customer responds that all the people are not together yet, the waiter operates the back button 673.

When the release button 672 is operated, the handheld terminal 200 transmits information (signal) indicating this to the order station 100. Also, when the release button 672 or the back button 673 is operated, the display on the display device of the handheld terminal 200 returns to the input screen 610.

Returning to FIG. 12, when the order station 100 receives a signal from the operation of the release button 672 (Yes in step S14), the wait release unit 114 deletes the corresponding record from the wait state storage unit 122 (step S15) and ends this process. Note that if the seat where the order originated was not in a wait state in step S12 (No in step S12) or if a signal from the operation of the back button 673 is received in step S14 (No in step S14), the wait release unit 114 ends this process.

In this configuration, the customer service staff can refer to the alert screen 660 displayed by the handheld terminal 200 to ascertain which tables are waiting for orders or for a customer to be picked up, and how long they have been in this state. Furthermore, the alert screen 660 is displayed periodically, so it functions as a reminder to the customer service staff. This makes it easier to avoid the inconvenience of a waiting table being left unattended due to a customer service staff member's carelessness.

As described above, this embodiment makes it possible to prevent delays in serving customers when a seated customer puts an order on hold or when a waiter waits inside the store.

In this embodiment, the customer service system has been described using as an example a restaurant such as a coffee shop that accepts orders after customers are seated, but in practice, the store to which the customer service system is applied is not limited to that of this embodiment.

Although not performed in this embodiment, in implementation, the handheld terminal 200 may be configured to allow the customer service staff to refer to the waiting seat information at any time. In other words, in implementation, when the notification unit 112 receives information from the handheld terminal 200 indicating that a specific operation has been accepted, the notification unit 112 may be configured to read information (waiting seat information) about at least one of the seats that are in the order waiting state or the accompanying waiting state from the waiting state storage unit 122 and notify the handheld terminal 200.

In addition, in this embodiment, the waiting seat information is notified not only by the handheld terminal 200 but also by the kitchen printer 501 and kitchen terminal 502, but in practice, it is sufficient if the waiting seat information is notified by any of them, not all of them. It is desirable to notify the waiting seat information by a configuration according to the size and needs of the store.

(Modification)
Next, a modified example of the above embodiment will be described. In the description, detailed description of the same things as in the above embodiment will be omitted, and the same reference numerals will be used. FIG. 14 is a diagram showing an example of a product information storage unit 121 according to the modified example. In this modified example, the product information storage unit 121 stores an expected number of people in addition to the product name, price, etc., in association with the product code. The expected number of people is the number of people expected to be consumers of the product identified by the product code.

For example, it is generally assumed that a single consumer will order curry or a set meal. Furthermore, a platter of fried foods, sashimi, skewers, etc., may be too much for one person to consume, and may be shared by several people. In contrast, no expected number of people is set for items such as coffee or tea, since even if multiple orders are placed, one person may order a refill. In this modified example, the expected number of consumers for each product is used to cancel the waiting state.

Figure 15 shows another example of the flow of the wait release process according to the modified example. Steps S21 to S22 are the same as steps S11 to S12, so a description thereof will be omitted.

In step S23, the waiting release unit 114 refers to the product information storage unit 121, and if the total number of expected customers for the order is equal to or greater than the planned number (Yes in step S23), it deletes the corresponding record from the waiting status storage unit 122 (step S24). Next, the waiting release unit 114 displays a message on the waiting release confirmation screen 680 (FIG. 16) (step S25), and ends this process.

Figure 16 is a diagram showing another example of the accompanying waiting cancellation confirmation screen 680 according to the modified example. The handheld terminal 200 receives information transmitted from the order station 100 and displays the accompanying waiting cancellation confirmation screen 680. The accompanying waiting cancellation confirmation screen 680 includes a message 681, a reset button 682, and a back button 683.

The message 681 may be, for example, "Waiting for companions has been cancelled. Please reset as necessary." When the customer service staff sees this, they will operate the back button 683 if they are sure that the required number of people is complete. Alternatively, the customer service staff may ask the customer, "Are you and your companions ready?" and if the answer is that they are not yet complete, they will operate the reset button 682.

When the reset button 682 is operated, the handheld terminal 200 transmits information (signal) indicating this to the order station 100. In this case, in response to an instruction from the order station 100, the handheld terminal 200 displays the planned number of people input screen 650 (right side of Figure 8) and accepts the operation. Also, when the back button 683 is operated, the display on the display device of the handheld terminal 200 returns to the input screen 610.

In preparation for the possibility that the reset button 682 will be operated, in step S24, the deletion process may be left uncompleted by, for example, preparing the record for deletion, and the deletion process may be completed when the back button 683 is operated. In this case, when the reset button 682 is operated, the prepared deletion process can be canceled, eliminating the need for the customer service staff to manually reset the settings.

In this way, with this modified version, the waiting can be cancelled automatically.

The information processing device of this embodiment is equipped with a control device such as a CPU, a storage device such as a ROM (Read Only Memory) or RAM, an external storage device such as a HDD or a CD drive, a display device such as a display device, and input devices such as a keyboard and a mouse, and has a hardware configuration that utilizes a normal computer.

The program executed by the information processing device of this embodiment is provided in the form of an installable or executable file recorded on a computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a DVD (Digital Versatile Disk).

The program executed by the information processing device of this embodiment may be stored on a computer connected to a network such as the Internet and provided by downloading it via the network. The program executed by the information processing device of this embodiment may be provided or distributed via a network such as the Internet.

The program of this embodiment may also be configured to be provided pre-installed in a ROM or the like.

The program executed by the information processing device of this embodiment has a modular configuration including the above-mentioned units (waiting state writing unit 111, notification unit 112, output unit 113, and waiting release unit 114). The CPU (processor) loads the above-mentioned units onto the main memory device by reading and executing the program from the above-mentioned storage device. As a result, the waiting state writing unit 111, notification unit 112, output unit 113, and waiting release unit 114 are generated on the main memory device.

Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the gist of the invention. These embodiments and their modifications are included in the scope and gist of the invention, and are included in the scope of the invention and its equivalents described in the claims.

100...Order Station,
101...CPU, 102...ROM, 103...RAM, 104...Communication I/F,
110...control unit,
111: Waiting state writing unit, 112: Notification unit, 113: Output unit, 114: Waiting release unit,
120: storage unit, 121: product information storage unit, 122: waiting state storage unit,
200: Handheld terminal,
301...LAN, 302...router,
400...POS terminal,
501... kitchen printer, 502... kitchen terminal, 503... server,
610...input screen,
620...Current number of people input screen,
630...Order waiting setting screen,
640... Waiting for someone to come along setting screen,
650... Planned number of people input screen,
660: Alert screen, 661: List, 662: Back button,
670... Waiting cancellation confirmation screen,
671: Message, 672: Cancel button, 673: Back button,
680... Waiting cancellation confirmation screen,
681...Message, 682...Reset button, 683...Back button.

Japanese Patent Application Publication No. 11-195070

Claims (6)

a waiting state writing unit that writes at least one of an order waiting state, which indicates that a customer who has sat down has reserved an order, and a waiting state, which indicates that the seat is for a planned increase in the number of customers, into a predetermined storage unit in association with seat identification information;
a notification unit that periodically reads out information about at least one of the seats in the order waiting state or the seat in the accompanying waiting state from the storage unit and notifies the information to a customer service terminal used by a customer service staff member;
An information processing device comprising: The information processing device according to claim 1 , further comprising: an output unit that outputs information about at least one of the seats in the order waiting state or the seat waiting for accompanying person, which is stored in the memory unit, to an output device installed in a back yard. The information processing device according to claim 1 or 2, further comprising a waiting cancellation unit that cancels the waiting-for-accompanying state upon receipt of an order from a customer at a seat stored in the memory unit as the waiting-for-accompanying state. A product information storage unit is capable of storing information on a product to be provided and storing the number of people expected to be consumers of the product in association with the product information,
The waiting state writing unit, when writing the accompanying waiting state, further associates the number of people who are expected to finally sit down,
The information processing device of claim 1 or 2, further comprising a waiting cancellation unit that cancels the waiting state when the total number of people associated in the product information storage unit with information on products ordered at the seat that has been set in the waiting state in the storage unit becomes equal to or greater than the planned number of people associated with the waiting state. An information processing device as described in any one of claims 1 to 4, wherein when the notification unit receives information indicating that a specified operation has been accepted from the customer service terminal, it reads information about at least one of the seats that are in the order waiting state or the pick-up waiting state from the memory unit and notifies the customer service terminal. Computer,
a waiting state writing unit that writes at least one of an order waiting state, which indicates that a customer who has sat down has reserved an order, and a waiting state, which indicates that the seat is for a planned increase in the number of customers, into a predetermined storage unit in association with seat identification information;
a notification unit that periodically reads out information about at least one of the seats in the order waiting state or the seat in the accompanying waiting state from the storage unit and notifies the information to a customer service terminal used by a customer service staff member;
A program to function as a

Images