Method for identifying and processing abnormal order of enterprise

Abstract

The invention discloses a method for identifying and processing an abnormal order of an enterprise, and the method comprises the steps: triggering an identification request of the abnormal order of the enterprise when a driver completes a driving task and completes the settlement at a driver end, and specifically comprises the steps: S1, receiving the abnormal order identification request of the driver through a system; s2, querying order information, and obtaining enterprise information, service type information and service city information to which an order belongs; s3, abnormal order configuration information is acquired; s4, whether order enterprise information is configured or not is judged, if not, the step S13 is executed, and if yes, follow-up operation is executed; s5, judging whether to configure an order service type, if not, executing a step S13, and if so, executing subsequent operation; the method comprises the steps of judging whether actual estimation, actual mileage and actual get-on and get-off addresses of an order are greater than configured thresholds or not through triggering when a driver operates settlement, if so, determining that the order is an abnormal order of an enterprise, otherwise, determining that the order is a normal order; functional experience is optimized, user complaints are reduced, and customer service pressure is reduced.

Description

Technical Field

[0001] The present invention belongs to the technical field of online car-hailing platforms, and specifically relates to a method for identifying and processing abnormal orders of an enterprise. Background Art

[0002] On the online car-hailing platform, corporate users place orders for cars, and drivers pick up and drop off users at their destinations, completing the service process. In reality, corporate users are less sensitive to order amounts because they do not need to pay personally, and drivers use devices to cheat by floating points or taking detours to get more money. This has led to complaints from corporate users and affected the online car-hailing service and brand image.

[0003] To this end, the present invention designs a method for identifying and processing abnormal orders of an enterprise. Summary of the invention

[0004] The purpose of the present invention is to provide a method for identifying and processing abnormal orders of an enterprise to solve the problems raised in the above background technology.

[0005] To achieve the above-mentioned purpose, the present invention provides the following technical solutions: a method for identifying and processing abnormal orders of an enterprise, wherein after the driver completes the delivery task and completes the settlement on the driver's side, an identification request for abnormal orders of the enterprise is triggered, specifically comprising:

[0006] Enterprise abnormal order identification and processing process:

[0007] S1: The system receives a driver’s abnormal order identification request;

[0008] S2: Query order information to obtain the company information, service type information, and service city information to which the order belongs;

[0009] S3: Get abnormal order configuration information;

[0010] S4: Determine whether to configure the order enterprise information, if not: execute step S13, if yes: execute subsequent operations;

[0011] S5: Determine whether to configure the order service type, if not: execute step S13, if yes: execute subsequent operations;

[0012] S6: Determine whether to configure the order city information, if not: execute step S13, if yes: execute subsequent operations;

[0013] S7: Call the enterprise order abnormality identification interface to determine whether it is an abnormal order of the enterprise, if not: execute step S13, if yes: execute subsequent operations;

[0014] S8: Call the order update interface and set the order as the enterprise abnormal order mark;

[0015] S9: The driver displays a pop-up window "Do you want to take a detour" according to the "abnormal order" mark, and the driver chooses whether to take a detour. If not, execute step S13; if yes, execute subsequent operations;

[0016] S10: Call the fee objection interface to create a fee objection with the source being the abnormal order;

[0017] S11: The scheduled task automatically handles the cost objection from the abnormal order, and determines whether the actual amount of the order is greater than the estimated amount. If not, execute step S13; if yes, execute the subsequent operation;

[0018] S12: Processing of abnormal orders to reduce the excess estimated amount;

[0019] S13: End;

[0020] User processing abnormal order process:

[0021] A1: The user enters the order details page in the online ride-hailing app;

[0022] A2: Determine whether it is an abnormal order of the enterprise. If not, proceed to step A9. If yes, proceed to the subsequent operations.

[0023] A3: The online car-hailing app displays the abnormal order page, showing the approve and reject buttons;

[0024] A4: The user determines whether to approve the fee based on the actual situation. If yes, proceed to step A8; if no, proceed to the subsequent operation.

[0025] A5: The user clicks the "Disagree" button to submit a fee objection;

[0026] A6: The customer service system receives a fee objection, and the customer service staff intervenes to judge whether to reduce or waive the fee. If not, proceed to step A9. If yes, proceed to the subsequent process.

[0027] A7: Customer service reduces the order fee, and the user receives the reduced amount. Go to step A9.

[0028] A8: The user clicks the approval button, and the system cancels the order exception mark;

[0029] A9: End.

[0030] Preferably, after an abnormal order from a company is generated, users can view and handle it in the online ride-hailing APP.

[0031] Preferably, in step S3, the configuration information includes enterprise information configuration, service type configuration, and city information configuration.

[0032] Preferably,

[0033] In step S7, the enterprise abnormal order identification process:

[0034] B1: After receiving the call request, the system obtains the basic information of the order;

[0035] B2: The system obtains abnormal order identification configuration information;

[0036] B3: Calculate whether the value of actual cost / estimated cost is greater than or equal to the configured threshold. If not, execute step B8. If yes, execute the subsequent process.

[0037] B4: Calculate whether the actual mileage / estimated mileage value is greater than or equal to the configured threshold. If not, execute step B8. If yes, execute the subsequent process.

[0038] B5: Calculate whether the actual boarding address deviates from the estimated boarding address by more than the configured threshold. If not, execute step B8. If yes, execute the subsequent process.

[0039] B6: Calculate whether the actual drop-off address deviates from the estimated drop-off address by more than the configured threshold. If not, execute step B8. If yes, execute the subsequent process.

[0040] B7: The order returned by the system is an abnormal order;

[0041] B8: The order returned by the system is not an abnormal order;

[0042] B9: End.

[0043] Preferably, in steps B3-B6, the configuration threshold can be manually set according to the platform conditions.

[0044] Compared with the prior art, the beneficial effects of the present invention are as follows: the present invention is triggered when the driver's operation settlement is completed, and determines whether the actual estimate, actual mileage, and actual pick-up and drop-off address of the order are greater than the configured threshold. If they are greater than or equal to the configured threshold, it is an abnormal order for the enterprise, otherwise it is a normal order; it optimizes the functional experience, reduces user complaints, and reduces customer service pressure. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] Figure 1 The figure is a schematic diagram of the abnormal order identification and processing flow of an enterprise according to the present invention.

[0046] Figure 2 A schematic diagram of the process of processing abnormal orders by users of the present invention.

[0047] Figure 3 The figure is a flow chart of abnormal order identification for an enterprise according to the present invention. DETAILED DESCRIPTION

[0048] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0049] See also Figure 1-3 , the present invention provides a technical solution: a method for identifying and processing abnormal orders of an enterprise, after the driver completes the delivery task, the driver triggers the identification request of the abnormal order of the enterprise when the settlement is completed on the driver's side;

[0050] Enterprise abnormal order identification and processing process:

[0051] S1: The system receives a driver’s abnormal order identification request;

[0052] S2: Query order information to obtain the company information, service type information, and service city information to which the order belongs;

[0053] S3: Get the abnormal order configuration information, which includes enterprise information configuration, service type configuration, and city information configuration;

[0054] S4: Determine whether to configure the order enterprise information, if not: execute step S13, if yes: execute subsequent operations;

[0055] S5: Determine whether to configure the order service type, if not: execute step S13, if yes: execute subsequent operations;

[0056] S6: Determine whether to configure the order city information, if not: execute step S13, if yes: execute subsequent operations;

[0057] S7: Call the enterprise order abnormality identification interface to determine whether it is an abnormal order of the enterprise, if not: execute step S13, if yes: execute subsequent operations;

[0058] S8: Call the order update interface and set the order as the enterprise abnormal order mark;

[0059] S9: The driver displays a pop-up window "Do you want to take a detour" according to the "abnormal order" mark, and the driver chooses whether to take a detour. If not, execute step S13; if yes, execute subsequent operations;

[0060] S10: Call the fee objection interface to create a fee objection with the source being the abnormal order;

[0061] S11: The scheduled task automatically handles the cost objection from the abnormal order, and determines whether the actual amount of the order is greater than the estimated amount. If not, execute step S13; if yes, execute the subsequent operation;

[0062] S12: Processing of abnormal orders to reduce the excess estimated amount;

[0063] S13: End.

[0064] After an abnormal order is generated by an enterprise, users can view and handle it in the online ride-hailing APP.

[0065] User processing abnormal order process:

[0066] A1: The user enters the order details page in the online ride-hailing app;

[0067] A2: Determine whether it is an abnormal order of the enterprise. If not, proceed to step A9. If yes, proceed to the subsequent operations.

[0068] A3: The online car-hailing app displays the abnormal order page, showing the approve and reject buttons;

[0069] A4: The user determines whether to approve the fee based on the actual situation. If yes, proceed to step A8; if no, proceed to the subsequent operation.

[0070] A5: The user clicks the "Disagree" button to submit a fee objection;

[0071] A6: The customer service system receives a fee objection, and the customer service staff intervenes to judge whether to reduce or waive the fee. If not, proceed to step A9. If yes, proceed to the subsequent process.

[0072] A7: Customer service reduces the order fee, and the user receives the reduced amount. Go to step A9.

[0073] A8: The user clicks the approval button, and the system cancels the order exception mark;

[0074] A9: End;

[0075] "Calling abnormal order identification interface" in the enterprise abnormal order identification processing flow.

[0076] Enterprise abnormal order identification process:

[0077] B1: After receiving the call request, the system obtains the basic information of the order;

[0078] B2: The system obtains abnormal order identification configuration information;

[0079] B3: Calculate whether the value of actual cost / estimated cost is greater than or equal to the configured threshold. If not, execute step B8. If yes, execute the subsequent process.

[0080] B4: Calculate whether the actual mileage / estimated mileage value is greater than or equal to the configured threshold. If not, execute step B8. If yes, execute the subsequent process.

[0081] B5: Calculate whether the actual boarding address deviates from the estimated boarding address by more than the configured threshold. If not, execute step B8. If yes, execute the subsequent process.

[0082] B6: Calculate whether the actual drop-off address deviates from the estimated drop-off address by more than the configured threshold. If not, execute step B8. If yes, execute the subsequent process.

[0083] B7: The order returned by the system is an abnormal order;

[0084] B8: The order returned by the system is not an abnormal order;

[0085] B9: End.

[0086] Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the appended claims and their equivalents.

Claims

1. A method for identifying and processing abnormal orders of an enterprise, characterized by: After the driver completes the delivery task, the driver triggers the enterprise's abnormal order identification request when completing the settlement operation on the driver's end, including: Enterprise abnormal order identification and processing process: S1: The system receives a driver’s abnormal order identification request; S2: Query order information to obtain the company information, service type information, and service city information to which the order belongs; S3: Get abnormal order configuration information; S4: Determine whether to configure the order enterprise information, if not: execute step S13, if yes: execute subsequent operations; S5: Determine whether to configure the order service type, if not: execute step S13, if yes: execute subsequent operations; S6: Determine whether to configure the order city information, if not: execute step S13, if yes: execute subsequent operations; S7: Call the enterprise order abnormality identification interface to determine whether it is an abnormal order of the enterprise, if not: execute step S13, if yes: execute subsequent operations; S8: Call the order update interface and set the order as the enterprise abnormal order mark; S9: The driver side displays a pop-up window "Do you want to take a detour" according to the "abnormal order" mark, and the driver chooses whether to take a detour. If not, execute step S13; if yes, execute subsequent operations; S10: Call the fee objection interface to create a fee objection with the source being the abnormal order; S11: The scheduled task automatically handles the cost objection from the abnormal order, and determines whether the actual amount of the order is greater than the estimated amount. If not, execute step S13; if yes, execute the subsequent operation; S12: Processing of abnormal orders to reduce the excess estimated amount; S13: End; User processing abnormal order process: A1: The user enters the order details page in the online ride-hailing app; A2: Determine whether it is an abnormal order of the enterprise. If not, proceed to step A9. If yes, proceed to the subsequent operations. A3: The online car-hailing app displays the abnormal order page, showing the approve and reject buttons; A4: The user determines whether to approve the fee based on the actual situation. If yes, proceed to step A8; if no, proceed to the subsequent operation. A5: The user clicks the "Disagree" button to submit a fee objection; A6: The customer service system receives a fee objection, and the customer service staff intervenes to judge whether to reduce or waive the fee. If not, proceed to step A9. If yes, proceed to the subsequent process. A7: Customer service reduces the order fee, and the user receives the reduced amount. Go to step A9. A8: The user clicks the approval button, and the system cancels the order exception mark; A9: End.

2. A method for identifying and processing abnormal orders of an enterprise according to claim 1, characterized in that: After an abnormal order is generated by an enterprise, users can view and handle it in the online ride-hailing APP.

3. A method for identifying and processing abnormal orders of an enterprise according to claim 1, characterized in that: In step S3, the configuration information includes enterprise information configuration, service type configuration, and city information configuration.

4. A method for identifying and processing abnormal orders of an enterprise according to claim 1, characterized in that: In step S7, the enterprise abnormal order identification process: B1: After receiving the call request, the system obtains the basic information of the order; B2: The system obtains abnormal order identification configuration information; B3: Calculate whether the value of actual cost / estimated cost is greater than or equal to the configured threshold. If not, execute step B8. If yes, execute the subsequent process. B4: Calculate whether the actual mileage / estimated mileage value is greater than or equal to the configured threshold. If not, execute step B8. If yes, execute the subsequent process. B5: Calculate whether the actual boarding address deviates from the estimated boarding address by more than the configured threshold. If not, execute step B8. If yes, execute the subsequent process. B6: Calculate whether the actual drop-off address deviates from the estimated drop-off address by more than the configured threshold. If not, execute step B8. If yes, execute the subsequent process. B7: The order returned by the system is an abnormal order; B8: The order returned by the system is not an abnormal order; B9: End.

5. A method for identifying and processing abnormal orders of an enterprise according to claim 4, characterized in that: In steps B3-B6, the configuration threshold can be manually set according to the platform conditions.

Images