Notification system and notification method

Abstract

In a service provided at a window, processing related to the collection of a commission is performed before the service is provided.SOLUTION: When receiving a reception request from a user, a reception device executes processing related to collection of a fee related to a service, and issues a numbered ticket indicating a reception number. The notification device notifies the reception number related to the next user when the provision of the service to the user is completed.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a notification system and a notification method. [Background technology]

[0002] Patent Document 1 discloses a technique for guiding customers (users) whose turn it is to wait in a queue for a transaction at a teller counter of a bank or the like to the teller counter. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 10-320482 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in most cases, there is no set price for consultation services at bank counters and other institutions, and requesting payment of a fee after the consultation service has been completed can lead to disputes between the service provider and the user. An object of the present invention is to provide a notification system and method that can inform users of the presence or absence of a fee and the amount of the fee required before the service is provided at a counter. [Means for solving the problem]

[0005] According to the first aspect, the notification system is a notification system for notifying users who are waiting for their turn for service provision of the time when the service will be available for provision, and includes a reception device that, upon receiving a reception request from a user, executes processing related to the collection of fees for the service and issues a numbered ticket indicating a reception number, and a notification device that notifies the reception number for the next user when the provision of the service to the user has been completed.

[0006] According to the second aspect, in the notification system according to the first aspect, the process for collecting the fee may be a process for printing a code containing information used for collecting the fee on the numbered ticket.

[0007] According to a third aspect, the notification system according to the second aspect may include a fee collection device that reads the code and executes processing for collecting the fee.

[0008] According to a fourth aspect, the notification system relating to the third aspect may include a management device that stores the collection status of the fee in association with the value represented by the code, and the management device may rewrite the collection status to information indicating that collection has been completed when the fee collection process is executed.

[0009] According to a fifth aspect, the notification system relating to the third or fourth aspect may include a management device that stores the amount of the fee in association with the value represented by the code, and the management device may be configured to accept changes to the amount of the fee by the service provider.

[0010] According to a sixth aspect, in the notification system according to the first aspect, the process relating to the fee collection may be execution of the fee collection process.

[0011] According to the seventh aspect, in a notification system relating to any one of the first to sixth aspects, the reception device may receive a reception request from a terminal device operated by the user via a network and transmit data representing the numbered ticket to the terminal device.

[0012] According to the eighth aspect, in the notification system relating to any one of the first to seventh aspects, the reception device may present the fee for the service to the user when receiving a reception request from the user.

[0013] According to the ninth aspect, the notification method is a method for notifying a user waiting for service provision of the timing when the service can be provided, wherein when a reception device receives a reception request from a user, the reception device executes a process for collecting a fee for the service and issues a numbered ticket representing a reception number, and when the provision of the service to the user is completed, the notification device notifies the reception number for the next user. [Effects of the Invention]

[0014] According to the above aspect, in a service provided at a counter, it is possible to inform the user of information regarding whether or not a fee is required and the amount of the fee before the service is provided. [Brief explanation of the drawings]

[0015] [Figure 1] 1 is a schematic diagram illustrating a configuration of a notification system according to a first embodiment. [Figure 2] FIG. 2 is a schematic diagram illustrating a software configuration of a management device according to the first embodiment. [Figure 3] 10 is an example of a reception menu according to the first embodiment. [Figure 4] FIG. 2 is a schematic diagram illustrating an example of information stored in a storage unit according to the first embodiment. [Figure 5] FIG. 2 is a diagram showing an example of a numbered ticket according to the first embodiment. [Figure 6] 10 is a flowchart showing a procedure for issuing a numbered ticket using the notification system according to the first embodiment. [Figure 7] 10 is a flowchart showing a procedure for collecting a fee using the notification system according to the first embodiment. [Figure 8] 10 is a flowchart showing a procedure for notifying an order using the notification system according to the first embodiment. [Figure 9] FIG. 10 is a schematic diagram illustrating the configuration of a notification system according to a second embodiment. [Figure 10] FIG. 10 is a schematic diagram illustrating the configuration of a notification system according to a third embodiment. [Figure 11]FIG. 1 is a schematic block diagram illustrating the configuration of a computer according to at least one embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0016] First Embodiment 《Notification system configuration》 Hereinafter, the embodiments will be described in detail with reference to the drawings. 1 is a schematic diagram showing the configuration of a notification system according to a first embodiment. The notification system 1 is installed in a financial institution such as a bank, and is a system for guiding a user U to a counter when his or her turn comes in a queue for a service to be performed at the counter.

[0017] The notification system 1 comprises a reception device 11, a notification device 12, a management device 13, a completion button 14, a code reader 15, and a fee collection device 16. The reception device 11 is operated by a user U and issues a numbered ticket T on which a reception number is printed. The reception device 11 is provided with a touch panel 111 which is an input / output device, a printing unit 112 which prints on the numbered ticket T, and a ticket issuing slot 113 which issues the printed numbered ticket T. The counter is further provided with a counter transaction device 17 which processes various transactions based on the user U's wishes.

[0018] The notification device 12 notifies the reception number of users who can be guided to the counter. The notification device 12 may be provided at each counter or may be shared by several counters. The management device 13 manages the reception status of users. The completion button 14 is pressed by the service provider P to notify the management device 13 that the service is complete. The completion button 14 is provided at each counter.

[0019] Code reader 15 reads two-dimensional codes such as QR Code (registered trademark). A code reader is installed at each counter. Fee collection device 16 performs processing to collect fees. Fee collection device 16 may be, for example, a cash processing machine, a CRM (Customer Relationship Management) system capable of reading cash cards, a payment terminal that performs payment processing based on IDs such as credit cards and two-dimensional codes, or a point processing terminal that performs payment using a point program. Bank account numbers, credit card numbers, and payment service IDs are examples of IDs related to payment processing.

[0020] 2 is a schematic diagram showing the software configuration of the management device 13 according to the first embodiment. The management device 13 includes a request receiving unit 131, a storage unit 132, a ticket issuance control unit 133, a status management unit 134, and a notification control unit 135. The request receiving unit 131 displays a reception menu on the touch panel of the reception device 11. FIG. 3 is an example of a reception menu according to the first embodiment. The reception menu includes a reception button for each service type. The reception button displays the name of the service and the fee for providing the service. The request receiving unit 131 receives reception requests from users by operating the touch panel of the reception device 11. Note that financial institutions such as banks generally display reception menus related to cash processing, such as "deposit processing," "withdrawal processing," and "public funds." The reception menu shown in FIG. 3 is an example of a display of an "other reception menu" related to processing other than cash processing. Examples of items in the other reception menu include items such as loans, inheritance, and insurance in addition to the reception menu items shown in FIG. 3. These items may be included in any of the reception menus shown in FIG. 3. In the reception menu shown in FIG. 3, if the service requested by the user is a "new transaction," which indicates a response regarding starting or wishing to start a new transaction with the bank or other financial institution, the reception menu also displays that the fee is set to "free." Similarly, if the service requested by the user is an "XX consultation," which indicates a consultation, the reception menu also displays that the fee is set to "1,000 yen per session." Furthermore, if the service requested by the user is an "XX investigation," which indicates an investigation or the like that takes more time than a consultation, the reception menu also displays that the fee is set to "2,000 yen per session." Data storing the fees set for each item, such as "new transaction," "XX consultation," and "XX investigation," is stored in advance in the storage unit 132. In addition, the items, subjects, etc. displayed on the reception menu can be selected and set as appropriate to those that can be handled by the bank or other financial institution, and a different amount may also be set as the fee required for handling and processing the items, subjects, etc. In the following explanation, it is assumed that the reception menu and fees shown in FIG. 3 are set in advance.

[0021] The storage unit 132 stores the status of the service associated with the reception number. FIG. 4 is a schematic diagram illustrating an example of information stored in the storage unit 132 according to the first embodiment. The storage unit 132 stores the reception number, service type, fee, counter number, collection status, and provision status in association with the reception ID. The reception ID is information displayed as a two-dimensional code, as described below. The reception number preferably has a small number of digits and character types to facilitate recognition by the user U, while the reception ID preferably has a large number of digits and character types to distinguish it from two-dimensional codes issued by other systems. For example, the reception ID may include a value unique to the notification system 1. The service type is the service type corresponding to the reception accepted by the request accepting unit 131. The fee is the amount charged to the user for the provision of the service. The fee is a preset amount associated with the service type. However, individual fees may be changed by the service provider P. For example, the service provider P may increase the fee depending on the effort required to provide the service, or may reduce or waive the fee if a new transaction can be initiated through the service. When increasing the fee, the state management unit 134 may request approval from the user U, and the fee may be increased only if approval is obtained. Examples of means for approval by the user U include verbal approval, inputting a password, writing a signature, etc.

[0022] When the ticket issuance control unit 133 receives a reception request from the request reception unit 131, it adds a new record related to the reception request to the memory unit 132. The values ​​related to the new record are as follows: The reception ID is a value newly generated by the ticket issuance control unit 133. The reception ID is unique. For example, the ticket issuance control unit 133 may use the same reception number as a previously issued number if the service provision has already been completed and the number is not in the queue. However, the ticket issuance control unit 133 cannot use the same reception ID as a previously issued reception ID even if the service provision has been completed. The reception number is a value obtained by adding 1 to the last reception number stored in the memory unit 132. Note that if the reception number reaches a predetermined value (e.g., 999), the ticket issuance control unit 133 may reset the reception number. The service type and fee are the same values ​​as the service type and fee included in the reception request. The counter number is unnumbered (blank, null, etc.). The collection status and provision status are incomplete. However, if the fee is 0, the receipt status is complete. In addition to this, the receipt ID generally records the transaction date and time information when the receipt request is made, and the receipt number may also be reset every time the day changes.

[0023] When the ticket issuance control unit 133 generates a new record, it transmits an instruction to issue a numbered ticket related to that record to the reception device 11. FIG. 5 is a diagram showing an example of a numbered ticket T according to the first embodiment. The numbered ticket T includes characters representing the reception number, a two-dimensional code representing the reception ID, and characters representing the fee. The printing of the two-dimensional code used to collect the fee and the display of the characters representing the fee are both examples of processing related to the collection of the fee.

[0024] The status management unit 134 manages the status of the service stored in the memory unit 132. For example, when the status management unit 134 receives a press of the Complete button 14, it changes the provision status of the record related to the service handled at the counter corresponding to the Complete button 14 stored in the memory unit 132 to Completed. The status management unit 134 also changes the counter number of the record related to the reception number at the top of the queue to the number of the counter related to the Complete button 14 that was last pressed. When the status management unit 134 receives an input from the fee collection device 16 indicating the completion of the collection of the fee related to the service, it changes the collection status of the record related to the service stored in the memory unit 132 to Completed.

[0025] When the completion button 14 is pressed, the notification control unit 135 outputs an instruction to display the next reception number on the notification device 12 of the counter corresponding to the completion button 14. Note that the above example shows an example in which all services can be processed at all counters, but the services that can be processed at each counter may be limited. In this case, when a reception request is obtained from the request reception unit 131, a counter number based on the service type included in the reception request is set in the record. When the service at that counter number is changed to completed, the status management unit 134 outputs an instruction to display the reception number of the record corresponding to the reception number at the top of the queue, which has a counter number that matches the reception number of the record.

[0026] <<Control of Notification System 1>> FIG. 6 is a flowchart showing the procedure for issuing a numbered ticket T using the notification system 1 according to the first embodiment. The user U operates the touch panel of the reception device 11 and presses the reception button associated with the desired service type (step S1). The reception device 11 transmits a reception request including the service type to the management device 13 (step S2). When the request reception unit 131 of the management device 13 receives the reception request, the ticket issuance control unit 133 issues a new reception ID and reception number and creates a new record in the memory unit 132 (step S3). The ticket issuance control unit 133 transmits a ticket issuance instruction including the reception number, reception ID, and fee information associated with the new record to the reception device 11 (step S4). The reception device 11 prints and issues a numbered ticket T including characters representing the reception number, a two-dimensional code representing the reception ID, and characters representing the fee. The user obtains the issued numbered ticket and waits.

[0027] 7 is a flowchart showing the procedure for collecting a fee using the notification system 1 according to the first embodiment. The service provider P receives a numbered ticket T from the user U and has the code reader 15 read the two-dimensional code displayed on the numbered ticket T (step S11). The code reader 15 transmits the reception ID indicated by the read two-dimensional code to the management device 13 (step S12). The status management unit 134 of the management device 13 identifies a record associated with the transmitted reception ID from the records stored in the memory unit 132 (step S13).

[0028] The service provider P checks the service type of the identified record, and while repeatedly interacting with the user, confirms the details of the service desired by the user, and then performs the necessary procedures and processes using the counter transaction device 17. For example, if the service type requested by the user is "XX consultation" and the details of the service confirmed through the interaction are services that correspond to "XX consultation," the service provider P simply performs the necessary procedures and processes for the service desired by the user. Here, even if the service type requested by the user is "XX consultation," the details of the service confirmed through dialogue may not correspond to the "XX consultation" but may refer to a different service, such as "XX investigation," or the "XX consultation" may be performed after the different service is performed. If the service type selected by the user differs from the service type actually provided, the service provider P will explain to the user the change in the service type to be requested and that the fee for processing the service will differ from the fee printed on the numbered ticket T issued by the reception device 11 before proceeding with the necessary procedures and processing. The service provider P confirms with the user U whether it is okay to proceed with the necessary procedures and processing for the desired service, and then proceeds with the necessary procedures and processing using the counter transaction device 17. Note that such a change in service type can occur for any service type, and the fee may increase, decrease, or even become free. If there is consent to change the service type, the service type and fee information stored in the record associated with the reception ID will also be modified as appropriate. For example, the service provider P sends a service type change instruction, including the record ID and the changed service type, to the management device 13 via the counter transaction device 17. The status management unit 134 of the management device 13 rewrites the service type associated with the record ID included in the received change instruction to the service type included in the change instruction. Therefore, it is desirable to collect the fee after completing the necessary procedures and processing for the service desired by the user U.

[0029] Then, when service provider P completes the necessary procedures and processing for user U using counter transaction device 17, status management unit 134 of management device 13 determines whether the collection status of the identified record is incomplete (step S14). As described above, normally, fees are not collected before the service is provided. Therefore, if the collection status is incomplete (step S14: YES), status management unit 134 outputs the amount of the fee to fee collection device 16 and causes fee collection device 16 to execute collection processing (step S15). When collection processing by fee collection device 16 is completed, status management unit 134 rewrites the collection status of the record identified in step S13 to completed (step S16).

[0030] On the other hand, if the collection status is not incomplete (step S14: NO), the status management unit 13 determines whether the difference between the amount of the fee already collected and the amount of the fee associated with the target record in the storage unit 132 is zero (step S17). If the difference is zero (step S17: YES), a message indicating that collection is complete is output to the counter transaction device 17 (step S18).

[0031] If the difference is not zero (step S17: NO), the difference is displayed and information for depositing or withdrawing is output to the counter transaction device 17 and the fee collection device 16 (step S19). The fee collection device 16 deposits or withdraws the difference (step S20). For example, if a fee has been collected in advance, the amount of the fee already collected may differ from the final fee amount (which, as described above, may have been revised by requesting confirmation from user U) due to the necessary procedures and processing actually performed. Therefore, the status management unit 13 determines whether or not such a difference exists, and if there is a difference, displays the difference on the display unit (not shown) of the counter transaction device 17. If there is a fee shortfall, the service provider P can notify user U while displaying the amount. This allows the service provider P to receive cash from user U, insert the received cash into the fee collection device 16, and have the deposit process performed. When change is required for the received cash or when the fee already received is excessive, the amount or the difference is displayed and the status management unit 13 causes the fee collection device 16 to perform a dispensing process to dispense the difference, and the service provider P takes out the dispensed cash from the fee collection device 16 and returns it to the user U.

[0032] 8 is a flowchart showing the procedure for notifying the order using the notification system 1 according to the first embodiment. When the service provider P has completed providing the service and collecting the fee, the service provider P presses the Complete button 14 (step S21). When the Complete button 14 is pressed, the status management unit 134 of the management device 13 identifies the counter number corresponding to the pressed Complete button 14 (step S22). The status management unit 134 identifies, from the records stored in the storage unit 132, records that are associated with the counter number identified in step S22 and whose service status is incomplete (step S23). Since the counter number is assigned immediately before calling the user U, records whose service status is incomplete and to which a counter number is assigned are records in which the call is in progress or the service is being provided.

[0033] The status management unit 134 determines whether the receipt status of the identified record is complete (step S24). If the receipt status is not complete (step S24: NO), the status management unit 134 notifies the service provider P that the receipt is not complete, and ends the process.

[0034] On the other hand, if the receipt status is "completed" (step S24: YES), the status management unit 134 rewrites the delivery status of the record identified in step S23 to "completed" (step S25). Next, the status management unit 134 identifies the record stored in the storage unit 132 whose delivery status is "incomplete" and whose record creation time is the oldest (step S26). In other words, the status management unit 134 identifies the record at the head of the queue. The status management unit 134 rewrites the counter number of the record identified in step S26 to the counter number identified in step S22 (step S27). The notification control unit 135 transmits a notification instruction to the notification device 12 corresponding to the counter number identified in step S22 to notify it of the reception number of the record identified in step S25 (step S28).

[0035] Actions and Effects In this way, when the reception device 11 of the notification system 1 according to the first embodiment receives a ticket issuance instruction from the user U, it issues a numbered ticket on which is printed a reception number and a two-dimensional code associated with the service information desired by the user U. In addition to these, the numbered ticket also prints information on fees incurred for the procedure and processing of the service. Therefore, the user can know the amount of fees to be incurred before receiving the service from the service provider, thereby preventing problems with payment claims.

[0036] Second Embodiment 9 is a schematic diagram showing the configuration of a notification system 1 according to the second embodiment. The notification system 1 according to the second embodiment reads the cash card of a user U, and identifies user information and executes collection and receipt processing in cooperation with a CRM. The reception device 11 according to the second embodiment further includes a card reader 114 in addition to the configuration of the first embodiment. The card reader 114 may further include authentication means based on biometric information (fingerprint, vein, palm print, face, voiceprint, iris, etc.). The reception device 11 according to the second embodiment transmits a reception request including the ID read by the card reader 114 to the management device 13. The management device 13 inquires about the information of the user U from the CRM, which is the fee collection device 16, based on the ID included in the reception request. The reception device 11 may include a bankbook reader that reads a bankbook instead of or in addition to the card reader 114.

[0037] The status management unit 134 of the management device 13 deducts the fee from the account when the numbered ticket T is issued or after the service is provided, based on the information of user U obtained from the CRM. Note that "when the numbered ticket T is issued" does not necessarily mean simultaneously with the issuance of the ticket, but also includes immediately before or after the issuance of the ticket. Deducting the fee and obtaining the information of user U from the CRM for the purpose of deducting the fee are examples of processing related to the collection of the fee. When deducting the fee when the ticket is issued, the reception device 11 may print receipt information on the numbered ticket T. Furthermore, the status management unit 134 can be expected to facilitate the provision of the service by presenting the acquired information of user U to the service provider P when the service is provided.

[0038] The management device 13 causes the reception device 11 to display a message indicating that the fee will be deducted, and if permission is obtained from the user U, executes the deduct from the registered account based on the information obtained from the CRM. Displaying the message indicating that the fee will be deducted and receiving permission to deduct the fee are examples of processing related to fee collection. If permission is not obtained from the user U, the collection processing is performed after the service is provided, as in the first embodiment. The management device 13 may determine the fee based on information about the user U acquired from the CRM. For example, if the information acquired from the CRM determines that the user U is a good customer, the management device 13 may discount or waive the fee. That is, if the information about the user U acquired from the CRM indicates that the user U is an important customer, such as a good customer, and if information indicating that the fee is fully or partially waived or subject to a reduction is assigned based on the user U's information, information to that effect, such as "The fee may be reduced or waived," may be additionally printed.

[0039] Third Embodiment 10 is a schematic diagram showing the configuration of a notification system 1 according to the third embodiment. The notification system 1 according to the third embodiment includes a code reader 15 and a fee collection device 16 that can be operated by a user U. The fee collection device 16 that can be operated by a user U is, for example, a cash acceptor. In this way, the notification system 1 according to the third embodiment includes the fee collection device 16 that can be operated by the user U, so that the user U can complete the fee collection process while waiting for the service to be provided. Note that the service provider P can determine whether the user U has completed the fee collection by the procedure shown in Fig. 7 or 8 above.

[0040] The information stored in the memory unit 132 in association with the reception ID should preferably include information that can identify the user U. While the provision of services may be completed in a single visit, it is more likely that multiple visits are required. Therefore, the service provider P may waive or partially waive the originally scheduled fee, or reduce it, as appropriate, depending on the level of service provided, not just if the user U is a loyal customer. The notification system 1 keeps a record of this information in the memory unit 132 for reference, and by displaying this information at the user's next or subsequent visits, the waived or reduced fee can be collected. Again, depending on the complexity of the actual procedures and processing, the fee may be increased or increased, subject to the user U's consent.

[0041] Other Embodiments Although one embodiment has been described in detail above with reference to the drawings, the specific configuration is not limited to the above, and various design modifications are possible. That is, in other embodiments, the order of the above-described processes may be changed as appropriate. Furthermore, some processes may be executed in parallel. The management device 13 according to the above-described embodiment may be configured by a single computer, or the configuration of the management device 13 may be divided into multiple computers that cooperate with each other to function as the management device 13. On the other hand, the management device 13 may be a computer built into another device such as the reception device 11, the notification device 12, or the fee collection device 16.

[0042] The reception device 11 according to the embodiment described above is installed in a store and issues sheet-like numbered tickets T, but is not limited to this. For example, the reception device 11 according to another embodiment may be one that makes reservations for reception via a network such as the Internet. In this case, the reception device 11 receives a reception request from a terminal device such as a smartphone carried by the user U. In accordance with the ticket issuance instruction, the reception device 11 transmits data for displaying the screen of the numbered ticket T shown in FIG. 5 to the terminal device. In other words, the numbered ticket T is not limited to a physical sheet, but includes electronic data.

[0043] The notification system 1 according to the embodiment described above is installed in a branch of a financial institution such as a bank, but is not limited thereto. For example, the notification system 1 according to another embodiment may be installed in a facility that provides services other than financial services (sales of goods, repairs, consultations, consulting, document preparation, customer support, etc.).

[0044] The notification system 1 according to the embodiment described above manages the status of a service using a two-dimensional code, but is not limited to this. For example, the notification system 1 according to other embodiments may manage the status of a service using information stored in other codes such as barcodes. Furthermore, the notification system 1 according to other embodiments may manage the status of a service using information stored in a recording medium such as a magnetic card or RFID tag.

[0045] <Computer Configuration> FIG. 11 is a schematic block diagram illustrating the configuration of a computer according to at least one embodiment. The computer 90 includes a processor 91 , a main memory 92 , a storage 93 , and an interface 94 . The above-mentioned management device 13 is implemented in a computer 90. The operations of the above-mentioned processing units are stored in the form of a program in a storage 93. A processor 91 reads the program from the storage 93, loads it into a main memory 92, and executes the above-mentioned processing in accordance with the program. The processor 91 also allocates storage areas in the main memory 92 corresponding to the above-mentioned storage units in accordance with the program. Examples of the processor 91 include a CPU (Central Processing Unit), a GPU (Graphic Processing Unit), and a microprocessor.

[0046] The program may be for realizing some of the functions to be performed by the computer 90. For example, the program may be combined with other programs already stored in storage or implemented in other devices to perform the functions. In another embodiment, the computer 90 may include a custom LSI (Large Scale Integrated Circuit) such as a PLD (Programmable Logic Device) in addition to or instead of the above configuration. Examples of PLDs include PAL (Programmable Array Logic), GAL (Generic Array Logic), CPLD (Complex Programmable Logic Device), and FPGA (Field Programmable Gate Array). In this case, some or all of the functions realized by the processor 91 may be realized by the integrated circuit. Such an integrated circuit is also an example of a processor. In another embodiment, the computer 90 may be virtualized on one or more computers.

[0047] Examples of storage 93 include a magnetic disk, a magneto-optical disk, an optical disk, and a semiconductor memory. Storage 93 may be an internal medium directly connected to the bus of computer 90, or an external medium connected to computer 90 via interface 94 or a communication line. Furthermore, when this program is distributed to computer 90 via a communication line, computer 90 that receives the program may load the program into main memory 92 and execute the above-described processing. In at least one embodiment, storage 93 is a non-transitory tangible storage medium.

[0048] The program may also be a program for realizing part of the above-described functions. Furthermore, the program may be a so-called differential file (differential program) that realizes the above-described functions in combination with another program already stored in storage 93. [Explanation of symbols]

[0049] 1...Notification system 11...Reception device 111...Touch panel 112...Printing unit 113...Ticket issuing port 114...Card reader 12...Notification device 13...Management device 131...Request reception unit 132...Memory unit 133...Ticket issuing control unit 134...Status management unit 135...Notification control unit 14...Completion button 15...Code reader 16...Fee collection device 90...Computer 91...Processor 92...Main memory 93...Storage 94...Interface P...Service provider T...Numbered ticket U...User

Claims

1. A notification system for notifying a user who is waiting for a service of the timing when the service becomes available, a reception device that, upon receiving a reception request from a user, executes a process for receiving a fee for the service and issues a numbered ticket indicating a reception number; a notification device that notifies the next user of the reception number when the provision of service to the user is completed; A notification system comprising:

2. The process for collecting the fee is a process for printing a code on the numbered ticket, the code recording information used for collecting the fee. The notification system of claim 1 .

3. a fee collection device that reads the code and executes the fee collection process; The notification system of claim 2 .

4. a management device that stores the fee collection status in association with the value represented by the code; When the fee collection process is executed, the management device rewrites the collection status to information indicating that collection has been completed. The notification system of claim 3 .

5. a management device that stores the amount of the fee in association with the value represented by the code; the management device accepts a change in the amount of the fee from the service provider; The notification system of claim 3 .

6. The processing related to the fee collection is the execution of the fee collection processing. The notification system of claim 1 .

7. the reception device receives a reception request from a terminal device operated by the user via a network, and transmits data representing the numbered ticket to the terminal device; The notification system of claim 1 .

8. the reception device presents a fee for the service to the user when receiving a reception request from the user; The notification system of claim 1 .

9. A notification method for notifying a user who is waiting for a service of a time when the service will be available, comprising: When the reception device receives a reception request from a user, it executes a process for receiving a fee for the service and issues a numbered ticket indicating a reception number; the notification device notifies the next user of the reception number when the provision of the service to the user is completed; Notification method.

Images