A service point business handling method and system based on a call numberer

Abstract

The application belongs to the technical field of queuing system, and discloses a service network business handling method and system based on a number calling device. The method comprises the following steps: obtaining the identity information and business information of a customer to generate a ticket number, and displaying the ticket number on the display panel of a number calling device; sending a first instruction to the number calling device to make it pop up and be obtained by the customer; sending a second instruction to the number calling device to remind the customer to go to a business window to handle the business; sending a third instruction to obtain the number calling device, and sending a fourth instruction to a staff when the ticket number in the number calling device is consistent with the ticket number of the customer to be served, and meanwhile, the number calling device is recovered and the ticket number in the number calling device is initialized; otherwise, a fifth instruction is sent to the number calling device to remind the customer to go to a correct business window or not to handle the business. The application not only avoids the waste of resources caused by the limitation of paper tickets in the existing queuing system, but also ensures the normal handling of various businesses.

Description

Technical Field

[0001] This invention relates to the field of queuing system technology, specifically to a service outlet business processing method and system based on a queuing system. Background Technology

[0002] Service outlets are the main locations where various service systems meet customers' business needs. Due to the limited number of service windows at service outlets, customers often need to queue using a queuing system and follow their assigned number to complete their business.

[0003] The existing service outlet queuing system works as follows: customers swipe their valid ID on the queuing machine's interactive terminal to allow the backend to obtain customer information and generate a ticket number after information recognition; then, customers can obtain a paper ticket corresponding to the ticket number on the queuing machine's interactive terminal; at this point, they can wait for their number to be called by the staff to process their business.

[0004] However, the existing system has the following drawbacks in practical application: Paper tickets are individually linked to each customer, but when the information on them is damaged, customers cannot obtain their correct queue number, or they may miss their turn due to not paying attention to the information displayed on the branch's screen or the call number system. In this case, they need to get a new number and queue again, affecting the normal business processing progress. Furthermore, the paper tickets are non-recyclable disposable tickets, while the daily business volume of service outlets is huge, inevitably leading to a large waste of disposable resources. Additionally, the paper tickets need to be manually replaced, and when the queuing machine runs out of paper, the normal queuing and number-taking process often cannot proceed smoothly. Summary of the Invention

[0005] The purpose of this invention is to provide a service outlet business processing method and system based on a queuing system, which solves the technical problems of resource waste and impact on normal business processing caused by the limitation of paper tickets in the existing queuing system.

[0006] To achieve the above objectives, the present invention proposes the following technical solution:

[0007] A service outlet business processing method based on a queuing system includes:

[0008] The system obtains the customer's identity information and business information to generate a ticket number, and displays the ticket number on the display panel of a queuing system; wherein, the customer, the ticket number, and the queuing system are bound one-to-one.

[0009] Send a first instruction to the queuing device to make it pop up and be received by the customer;

[0010] Send a second instruction to the queuing system to remind the customer to go to the service window to handle the business;

[0011] A third instruction is sent to retrieve the queuing device, and if the ticket number in the queuing device matches the ticket number of the customer with pending business, a fourth instruction is sent to the staff, and the queuing device is retrieved and its ticket number is initialized; otherwise, a fifth instruction is sent to the queuing device to remind the customer to go to the correct service window, or to remind the customer that they have not come to the window to conduct business.

[0012] Furthermore, after sending the first instruction to the queuing device to make it pop up and be received by the customer, the process includes:

[0013] The system obtains the number of ticket numbers between the ticket number currently being processed at the corresponding business window and the customer's ticket number in real time, using this number as the number of people the customer needs to wait for, and updates the number of people needing to wait to the display panel of the queuing system in real time.

[0014] The system obtains the pending business type of each person among the number of people who need to wait in real time to obtain the corresponding estimated time. The sum of the estimated times is taken as the waiting time for the customer, and the waiting time is updated in real time on the display panel of the queuing device.

[0015] Furthermore, after updating the number of people waiting in real time to the display panel of the queuing system, the process includes:

[0016] When the number of people waiting is less than a preset threshold, a first reminder message is sent to the queuing system;

[0017] When the number of people waiting is 0, a second reminder message is sent to the queuing device; wherein the first reminder message and the second reminder message include at least one of the following: sound reminder, light reminder, and vibration reminder.

[0018] Furthermore, including:

[0019] Obtain a first request to reclaim the queuing device and initialize the ticket numbers within it; wherein, the first request is used to request the cancellation of the corresponding business processing request.

[0020] Furthermore, including:

[0021] A second request is obtained to re-acquire business information to generate a new ticket number, and the new ticket number is displayed on the display panel of the queuing device; wherein, the second request is used to request a change of business information.

[0022] A service outlet business processing system based on a queuing system includes:

[0023] The first acquisition module is used to acquire the customer's identity information and business information to generate a ticket number, and display the ticket number on the display panel of a queuing device; wherein, the customer, the ticket number and the queuing device are bound one-to-one;

[0024] The first sending module is used to send a first instruction to the queuing device to make it pop up and be received by the customer;

[0025] The second sending module is used to send a second instruction to the queuing device to remind the customer to go to the service window to handle the business;

[0026] The third sending module is used to send a third instruction to obtain the queuing device, and when it confirms that the ticket number in the queuing device matches the ticket number of the customer with pending business, it sends a fourth instruction to the staff, and at the same time retrieves the queuing device and initializes the ticket number in it; otherwise, it sends a fifth instruction to the queuing device to remind the customer to go to the correct service window, or to remind the customer that they have not come to the window to handle their business.

[0027] Furthermore, including:

[0028] The second acquisition module is used to acquire in real time the number of ticket numbers between the ticket number currently being processed at the corresponding business window and the customer's ticket number as the number of people the customer needs to wait for, and to update the number of people needing to wait to the display panel of the queuing device in real time.

[0029] The third acquisition module is used to acquire the pending business type of each person among the number of people who need to wait in real time to obtain the corresponding estimated time, and use the sum of the estimated times as the waiting time of the customer, and update the waiting time to the display panel of the queuing device in real time.

[0030] Furthermore, the second acquisition module includes:

[0031] The first reminder unit is used to send a first reminder message to the queuing device when the number of people who need to wait is less than a preset number threshold.

[0032] The second reminder unit is used to send a second reminder message to the queuing device when the number of people waiting is 0; wherein the first reminder message and the second reminder message include at least one of the following: sound reminder, light reminder, and vibration reminder.

[0033] Furthermore, including:

[0034] The fourth acquisition module is used to acquire a first request to reclaim the queuing device and initialize the ticket numbers within it; wherein, the first request is used to request the cancellation of the corresponding business processing requirement.

[0035] Furthermore, including:

[0036] The fifth acquisition module is used to acquire a second request to reacquire business information to generate a new ticket number, and to display the new ticket number on the display panel of the queuing device; wherein, the second request is used to request to change the business information.

[0037] Beneficial effects:

[0038] As can be seen from the above technical solutions, the technical solution of the present invention provides a service outlet business processing method based on a queuing system to improve the existing business processing process, which suffers from resource waste and technical defects that affect normal business processing.

[0039] The method includes: First, obtaining the customer's identity information and business information to generate a ticket number, and displaying the ticket number on the display panel of a queuing device; wherein, the customer, the ticket number, and the queuing device are bound one-to-one; sending a first instruction to the queuing device to make it pop up and be acquired by the customer; second, sending a second instruction to the queuing device to remind the customer to go to the business window for business processing; then sending a third instruction to acquire the queuing device, and when confirming that the ticket number in the queuing device matches the ticket number of the customer with pending business, sending a fourth instruction to the staff, and simultaneously retrieving the queuing device and initializing the ticket number in it; otherwise, sending a fifth instruction to the queuing device to remind the customer to go to the correct business window, or to remind the customer that they have not come to the correct window for business processing.

[0040] As can be seen from the above, the entire process of handling service transactions, from queuing and waiting to being called, is based on a queuing system. As a reusable hardware device, the queuing system avoids the resource waste caused by paper tickets compared to the existing paper-based queuing process. Furthermore, since the initialization process of the queuing system is also considered in this method, it avoids the inconvenience caused to customers by the untimely replacement of tickets, a process common in existing paper-based queuing processes. Moreover, unlike the static information display of paper tickets, it allows for more interactive functions. Therefore, it can guide customers through the process, effectively preventing missed numbers and directing them to the correct service window. Compared to the existing method where staff need to manually verify the ticket number on the paper ticket to confirm customer and service information, this is faster and more accurate, ensuring the smooth processing of relevant services.

[0041] It should be understood that all combinations of the foregoing concepts and the additional concepts described in more detail below can be considered part of the inventive subject matter of this disclosure, provided that such concepts do not contradict each other.

[0042] The foregoing and other aspects, embodiments, and features of the teachings of the present invention will be more fully understood from the following description in conjunction with the accompanying drawings. Other additional aspects of the invention, such as features and / or beneficial effects of exemplary embodiments, will become apparent from the following description or may be learned through practice of specific embodiments according to the teachings of the present invention. Attached Figure Description

[0043] The accompanying drawings are not intended to be drawn to scale. In the drawings, each identical or nearly identical component shown in the various figures may be denoted by the same reference numeral. For clarity, not every component is labeled in each figure. Embodiments of various aspects of the invention will now be described by way of example and with reference to the accompanying drawings, wherein:

[0044] Figure 1 This is a flowchart of the service outlet business processing method based on a queuing system described in this embodiment;

[0045] Figure 2 A flowchart showing the display of relevant information for a specific business transaction;

[0046] Figure 3 This is a flowchart for providing customer reminders;

[0047] Figure 4 A flowchart illustrating the process for handling customer cancellations of transactions;

[0048] Figure 5 This is a flowchart for handling customer changes in business type. Detailed Implementation

[0049] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. All other embodiments obtained by those skilled in the art based on the described embodiments of the present invention without creative effort are within the scope of protection of the present invention. Unless otherwise defined, the technical or scientific terms used herein should have the ordinary meaning understood by those skilled in the art.

[0050] The terms "first," "second," and similar words used in the specification and claims of this patent application do not indicate any order, quantity, or importance, but are merely used to distinguish different components. Similarly, unless the context clearly indicates otherwise, the singular forms of "an," "a," or "the," etc., do not indicate a quantity limitation, but rather indicate the presence of at least one. Terms such as "comprising" or "including" mean that the element or object preceding "comprising" encompasses the features, wholes, steps, operations, elements, and / or components listed following "comprising" or "including," and do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components, and / or collections thereof. Terms such as "upper," "lower," "left," and "right" are used only to indicate relative positional relationships; when the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0051] While existing service outlets have queuing systems in place to guide customers and ensure efficient processing, these systems primarily rely on paper tickets distributed to each customer. This presents several challenges. First, damaged tickets prevent customers from obtaining their correct queue number, and customers may miss their turn due to not paying attention to the information displayed on the outlet's screen or the call number system, requiring them to re-enter the queue and disrupting the normal processing flow. Second, the non-recyclable disposable paper tickets inevitably lead to significant waste of resources; furthermore, manual replacement of these tickets is necessary, and shortages in the queuing machine often disrupt the queuing process. Therefore, this embodiment aims to provide a service outlet processing method based on a call number system to address the aforementioned shortcomings of existing queuing systems.

[0052] The following description, in conjunction with the accompanying drawings, details the service outlet business processing method based on a queuing system disclosed in this embodiment.

[0053] like Figure 1 As shown, the method includes:

[0054] Step S102: Obtain the customer's identity information and business information to generate a ticket number, and display the ticket number on the display panel of a queuing device; wherein, the customer, the ticket number, and the queuing device are bound one-to-one.

[0055] In practice, the identity information is obtained by swiping a card or ID card, while the business information is obtained by the business type selected by the customer on the queuing machine interface installed in the branch lobby.

[0056] In terms of hardware structure, a storage box is also provided, in which several call queuing devices are arranged in a regular pattern. To facilitate the retrieval of the call queuing devices, the storage box is located on one side of the queuing machine's interactive terminal installed in the branch lobby. When a call queuing device is bound, its status within the storage box changes from silent to active.

[0057] Step S104: Send a first instruction to the queuing device to make it pop up and be obtained by the customer.

[0058] In practical implementation, the first instruction is used to confirm that the customer has agreed to conduct the corresponding business. At this time, the queuing device, which is in an active state, will be moved to the retrieval port of the storage box by the drive mechanism inside the storage box and popped out. As a preferred embodiment, the retrieval port and the interaction panel of the queuing machine are set on the same plane so that the customer can obtain the queuing device.

[0059] Step S106: Send a second instruction to the queuing system to remind the customer to go to the service window to handle the business.

[0060] Step S108: Send a third instruction to obtain the queuing device, and when it is confirmed that the ticket number in the queuing device matches the ticket number of the customer with pending business, send a fourth instruction to the staff, and simultaneously retrieve the queuing device and initialize the ticket number in it; otherwise, send a fifth instruction to the queuing device to remind the customer to go to the correct service window, or to remind the customer that they have not come to the window to conduct business.

[0061] In practice, a recycling unit is installed at each service window. The recycling unit has a built-in identification chip to identify the ticket number within the queuing device when it is returned (i.e., retrieved) to the recycling unit. It also includes a transmission channel, with its two ends connected to the recycling unit and the storage box, respectively. After being recycled and initialized within the queuing device, the ticket is moved from the recycling unit back to the storage box for reuse.

[0062] As a preferred implementation method, such as Figure 2 As shown, the number of customers who need to wait and the waiting time are also dynamically displayed on the display panel of the queuing system in the following way, so that customers can make reasonable time arrangements during the waiting process and further avoid events such as missing their number that affect business processing.

[0063] Step S105.2: Obtain in real time the number of ticket numbers between the ticket number currently being processed at the corresponding business window and the customer's ticket number to determine the number of people the customer needs to wait for, and update the number of people needing to wait to the display panel of the queuing system in real time.

[0064] For example, if the customer's ticket number is E020, and the ticket number currently being processed is E011; the ticket numbers assigned to this service window are E012, E015, and E017. In this case, the total number of ticket numbers is 3.

[0065] Step S105.4: Obtain the pending business type of each person among the number of people who need to wait in real time to obtain the corresponding estimated time. Use the sum of the estimated times as the waiting time for the customer and update the waiting time to the display panel of the queuing device in real time.

[0066] Based on the above process, it can be seen that the ticket dispenser is bound to the service window during each use. Therefore, the pending service type is introduced when calculating the waiting time, making the obtained waiting time more accurate.

[0067] As a further preferred implementation, such as Figure 3 As shown, the following methods are used to further prevent incidents such as missing the registration number.

[0068] Step S105.2.2: When the number of people waiting is less than a preset threshold, send a first reminder message to the queuing device.

[0069] As an optional implementation, the triggering instruction for the first reminder message may also be that the waiting time is less than a preset time threshold.

[0070] Step S105.2.4: When the number of people waiting is 0, send a second reminder message to the queuing device.

[0071] The first reminder information and the second reminder information both include at least one of the following: sound reminder, light reminder, and vibration reminder.

[0072] Therefore, when customers are waiting to complete their business, two reminder messages that directly stimulate their senses can effectively prevent incidents such as missing their turn due to subjective behavior.

[0073] In actual business transactions, it is common for customers to have already obtained a number but cancel their service due to various factors. To address this situation, one possible solution is... Figure 4 As shown, it also includes:

[0074] Step S202: Obtain a first request to reclaim the queuing device and initialize the ticket numbers within it; wherein, the first request is used to request the cancellation of the corresponding business processing requirement.

[0075] As an alternative implementation method, a questionnaire can be sent to customers to inquire about the reasons for canceling their service. This helps to identify situations where cancellations are caused by deficiencies at service outlets, such as insufficient service windows leading to long waiting times, poor lobby environment, or staff lacking proficiency or having poor service attitudes. This facilitates improvements and optimizations to the service outlets to address these shortcomings.

[0076] In actual business transactions, there are often situations where customers have already selected a service type but need to change it midway through the process. To address this, one possible solution is... Figure 5 As shown, it also includes:

[0077] Step S302: Obtain a second request to re-obtain business information to generate a new ticket number, and display the new ticket number on the display panel of the queuing device; wherein, the second request is used to request the replacement of business information.

[0078] At this point, when sorting the customer, the customer's waiting time will be obtained by the difference between the generation time of the old ticket number and the generation time of the new ticket number, and the waiting time will be compared with each waiting threshold to confirm the customer's sorting in the new business window.

[0079] As can be seen from the above, the method described in this embodiment is based on the queuing system, thereby avoiding the resource waste and impact on business processing that may be caused by the existing queuing and calling system based on paper tickets. It also considers the situations where business processing is cancelled or the type of business is changed, which often occur in actual applications, and has formulated corresponding countermeasures to further ensure the normal operation of business processing.

[0080] The aforementioned program can run in a processor or be stored in memory (or a computer-readable storage medium). Computer-readable media includes both permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include temporary computer-readable media, such as modulated data signals and carrier waves.

[0081] These computer programs may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes can be implemented using different modules, and different steps can be implemented using different modules.

[0082] This embodiment also provides a service outlet business processing system based on a queuing system. The system includes:

[0083] The first acquisition module is used to acquire the customer's identity information and business information to generate a ticket number, and display the ticket number on the display panel of a queuing device; wherein, the customer, the ticket number and the queuing device are bound one-to-one.

[0084] The first sending module is used to send a first instruction to the queuing device so that it pops up and can be obtained by the customer.

[0085] The second sending module is used to send a second instruction to the queuing device to remind the customer to go to the service window to handle the business.

[0086] The third sending module is used to send a third instruction to obtain the queuing device, and when it confirms that the ticket number in the queuing device matches the ticket number of the customer with pending business, it sends a fourth instruction to the staff, and at the same time retrieves the queuing device and initializes the ticket number in it; otherwise, it sends a fifth instruction to the queuing device to remind the customer to go to the correct service window, or to remind the customer that they have not come to the window to handle their business.

[0087] The apparatus is used to implement the steps of the above method, and therefore, as already described, will not be repeated here.

[0088] For example, the system includes:

[0089] The second acquisition module is used to acquire in real time the number of ticket numbers between the ticket number currently being processed at the corresponding business window and the customer's ticket number, as the number of people the customer needs to wait for, and to update the number of people needing to wait to the display panel of the queuing device in real time.

[0090] The third acquisition module is used to acquire the pending business type of each person among the number of people who need to wait in real time to obtain the corresponding estimated time, and use the sum of the estimated times as the waiting time of the customer, and update the waiting time to the display panel of the queuing device in real time.

[0091] For example, the second acquisition module includes:

[0092] The first reminder unit is used to send a first reminder message to the queuing device when the number of people waiting is less than a preset number threshold.

[0093] The second reminder unit is used to send a second reminder message to the queuing device when the number of people waiting is 0; wherein the first reminder message and the second reminder message include at least one of the following: sound reminder, light reminder, and vibration reminder.

[0094] For example, the system includes:

[0095] The fourth acquisition module is used to acquire a first request to reclaim the queuing device and initialize the ticket numbers within it; wherein, the first request is used to request the cancellation of the corresponding business processing requirement.

[0096] For example, the system also includes:

[0097] The fifth acquisition module is used to acquire a second request to reacquire business information to generate a new ticket number, and to display the new ticket number on the display panel of the queuing device; wherein, the second request is used to request to change the business information.

[0098] Since the system is built based on the method described above, it effectively solves the resource waste and disruption to normal business operations caused by existing paper-based invoices. It also addresses common issues such as customer cancellations and changes in service type.

[0099] While the present invention has been disclosed above with reference to preferred embodiments, it is not intended to limit the invention. Those skilled in the art can make various modifications and refinements without departing from the spirit and scope of the invention. Therefore, the scope of protection of the present invention shall be determined by the claims.

Claims

1. A service outlet business processing method based on a queuing system, characterized in that, It includes a storage box and a recycling bin located at the service window; several callers are arranged in a regular pattern inside the storage box, and the storage box is located on one side of the queuing machine's interactive end; when a caller is bound, the caller's state in the storage box changes from a silent state to an active state; and the caller that has changed to an active state will be moved to the storage box's retrieval port by the drive mechanism inside the storage box and ejected. The recycling unit has a built-in identification chip and a transmission channel. The identification chip identifies the ticket number in the calling device when it is placed back into the recycling unit. The two ends of the transmission channel are connected to the recycling unit and the storage box, respectively. After the corresponding calling device is recycled and initialized, it is moved from the recycling unit to the storage box for reuse. Includes the following steps: The system obtains the customer's identity information and business information to generate a ticket number, and displays the ticket number on the display panel of a queuing system; wherein, the customer, the ticket number, and the queuing system are bound one-to-one. Send a first instruction to the queuing device to make it pop up and be received by the customer; Send a second instruction to the queuing system to remind the customer to go to the service window to handle the business; If a third instruction is sent to retrieve the queuing device and it is confirmed that the ticket number in the queuing device matches the ticket number of the customer with pending business, a fourth instruction is sent to the staff, and the queuing device is retrieved and its ticket number is initialized; otherwise, a fifth instruction is sent to the queuing device to remind the customer to go to the correct service window, or to remind the customer that they have not come to the window to conduct business. Simultaneously, a second request is obtained to re-acquire business information to generate a new ticket number, and the new ticket number is displayed on the display panel of the queuing device; wherein, the second request is used to request a change of business information; the customer's waiting time is obtained based on the difference between the generation time of the old ticket number and the generation time of the new ticket number, and the waiting time is compared with each waiting threshold to confirm the customer's ranking in the new business window.

2. The service outlet business processing method based on a queuing system according to claim 1, characterized in that, After sending the first instruction to the queuing device to make it pop up and be received by the customer, the process includes: The system obtains the number of ticket numbers between the ticket number currently being processed at the corresponding business window and the customer's ticket number in real time, using this number as the number of people the customer needs to wait for, and updates the number of people needing to wait to the display panel of the queuing system in real time. The system obtains the pending business type of each person among the number of people who need to wait in real time to obtain the corresponding estimated time. The sum of the estimated times is taken as the waiting time for the customer, and the waiting time is updated in real time on the display panel of the queuing device.

3. The service outlet business processing method based on a queuing system according to claim 2, characterized in that, After updating the number of people waiting in real time to the display panel of the queuing system, the process includes: When the number of people waiting is less than a preset threshold, a first reminder message is sent to the queuing system; When the number of people waiting is 0, a second reminder message is sent to the queuing device; wherein the first reminder message and the second reminder message include at least one of the following: sound reminder, light reminder, and vibration reminder.

4. The service outlet business processing method based on a queuing system according to claim 1, characterized in that, include: Obtain a first request to reclaim the queuing device and initialize the ticket numbers within it; wherein, the first request is used to request the cancellation of the corresponding business processing request.

5. A service outlet business processing system based on a queuing system, characterized in that, To implement the method of claim 1, the method comprises: The first acquisition module is used to acquire the customer's identity information and business information to generate a ticket number, and display the ticket number on the display panel of a queuing device; wherein, the customer, the ticket number and the queuing device are bound one-to-one; The first sending module is used to send a first instruction to the queuing device to make it pop up and be received by the customer; The second sending module is used to send a second instruction to the queuing device to remind the customer to go to the service window to handle the business; The third sending module is used to send a third instruction to obtain the queuing device, and when it confirms that the ticket number in the queuing device matches the ticket number of the customer with pending business, it sends a fourth instruction to the staff, and at the same time retrieves the queuing device and initializes the ticket number in it; otherwise, it sends a fifth instruction to the queuing device to remind the customer to go to the correct service window, or to remind the customer that they have not come to the window to handle their business.

6. The service outlet business processing system based on a queuing system according to claim 5, characterized in that, include: The second acquisition module is used to acquire in real time the number of ticket numbers between the ticket number currently being processed at the corresponding business window and the customer's ticket number as the number of people the customer needs to wait for, and to update the number of people needing to wait to the display panel of the queuing device in real time. The third acquisition module is used to acquire the pending business type of each person among the number of people who need to wait in real time to obtain the corresponding estimated time, and use the sum of the estimated times as the waiting time of the customer, and update the waiting time to the display panel of the queuing device in real time.

7. The service outlet business processing system based on a queuing system according to claim 6, characterized in that, The second acquisition module includes: The first reminder unit is used to send a first reminder message to the queuing device when the number of people who need to wait is less than a preset number threshold. The second reminder unit is used to send a second reminder message to the queuing device when the number of people waiting is 0; wherein the first reminder message and the second reminder message include at least one of the following: sound reminder, light reminder, and vibration reminder.

8. The service outlet business processing system based on a queuing system according to claim 5, characterized in that, include: The fourth acquisition module is used to acquire a first request to reclaim the queuing device and initialize the ticket numbers within it; wherein, the first request is used to request the cancellation of the corresponding business processing requirement.

Images