Method for improving transport capacity utilization rate and optimizing transport capacity side responsibility judgment model

Abstract

The invention discloses a method for improving the transport capacity utilization rate and optimizing a transport capacity side responsibility judgment model, and the method comprises the steps: S1, enabling a three-party platform to receive the complaint of a passenger, and carrying out the issuing disposal and violation of an order; s2, receiving the disposition and violation by the online car-hailing transport capacity side open platform, and judging a punishment type according to background mapping type configuration; s3, if the customer complaint type is met, synchronizing the data to a customer service background, and after the customer service background receives the data, judging whether the disposal ID is empty or not; s4, the charging side receives the deduction amount; s5, after the vehicle management side receives the punishment notice and the punishment amount, punishment is issued to the driver; s6, the driver decides whether to appeal or not; s7, the vehicle management judges whether the complaint request of the driver can be complained to a three-party platform or not; s8, the vehicle management side of the transport capacity side records the appeal result according to the appeal ID; the transport capacity utilization rate of the transport capacity side can be improved, and the transport capacity waste of blacklist drivers is avoided; the efficiency of processing objection orders by customer service personnel is improved, and customer service human resources are saved; and optimizing the responsibility judgment model and the business process.

Description

Technical Field

[0001] The present invention belongs to the technical field of online car-hailing operation management, and specifically relates to a method for improving capacity utilization and optimizing a capacity-side accountability model. Background Art

[0002] For orders with passenger complaints, the third-party platform will take corresponding measures to control the drivers on the online ride-hailing capacity side, such as blacklisting the drivers. In such scenarios, the capacity side will again assign the blacklisted drivers to the third-party platform without any awareness. At the same time, orders from the third-party platform side that are complained to the capacity side require manual judgment and processing by customer service personnel within a time limit.

[0003] The drivers assigned to third parties by the transportation side are locked, but in fact they are on the third party's blacklist and cannot receive orders from the third party platform, resulting in reduced transportation capacity utilization; objection orders from the third party side will increase labor and time costs in the processing process, and there is a scenario where the processing time is delayed. Summary of the invention

[0004] The purpose of the present invention is to provide a method for improving the utilization rate of transportation capacity and optimizing the accountability model on the transportation capacity side, so as to solve the problem of avoiding the waste of transportation capacity caused by assigning blacklisted drivers to third parties in the current process, and at the same time to improve the efficiency of customer service on the transportation capacity side in handling and managing complaints and save customer service manpower costs. The accountability model optimization is introduced; through the internal interface flow and processing mechanism on the transportation capacity side, the original offline mode of processing third-party data is replaced.

[0005] To achieve the above object, the present invention provides the following technical solutions: A method for improving capacity utilization and optimizing the capacity-side accountability model, S1: The third-party platform receives a passenger complaint and issues a disposal and violation for the order, including a disposal ID, a disposal amount, a violation ID, and a violation amount;

[0006] S2: The open platform on the online car-hailing capacity side receives the disposal and violation information, and determines the penalty type based on the background mapping type configuration;

[0007] S3: If the complaint type is met, the data is synchronized to the customer service backend. After receiving the data, the customer service backend determines whether the disposal ID is empty.

[0008] S31: If it is not empty, the customer service backend will automatically generate a complaint record in which the driver is responsible, and the order will be exempted. The exemption amount is taken from the disposal amount included in the disposal. At the same time, the exemption amount value is synchronized with the billing side and the penalty notification is synchronized with the vehicle management side.

[0009] S32: In the scenario where it is empty, the system caches for X minutes. If the disposal ID is polled within X minutes, a complaint record is automatically generated for the driver to be responsible, and the order is exempted. The exemption amount is taken from the disposal amount included in the disposal. If the disposal ID is not polled within X minutes, a complaint record is automatically generated for the driver to be responsible, and the order is exempted. The exemption amount is taken from the violation amount in the violation. At the same time, the exemption value is synchronized with the billing side and the penalty notification is synchronized with the vehicle management side.

[0010] S4: The billing side receives the reduction amount;

[0011] S5: After receiving the penalty notice and penalty amount, the vehicle management department issues the penalty to the driver;

[0012] S6: The driver decides whether to appeal;

[0013] S7: The vehicle management department determines whether the driver’s appeal request can be appealed to the third-party platform;

[0014] S8: The vehicle management department on the transport capacity side records the appeal result according to the appeal ID.

[0015] Preferably, step S4 specifically includes: S41: operating to reduce or exempt the amount of the passenger-side order and record it synchronously; S42: calculating the amount to be deducted from the driver's turnover through the driver's commission ratio, and synchronizing the value to the vehicle management side.

[0016] Preferably, step S6 specifically includes: S61: if the driver does not appeal, a penalty is generated and a corresponding amount is deducted, and the process ends; S62: if the driver appeals, an appeal request may be initiated.

[0017] Preferably, step S7 specifically includes: S71: records that cannot be appealed to the third-party platform are transferred to the fleet for manual review; records that fail to pass the fleet review are punished and a corresponding amount is deducted, and the process ends; records that pass the fleet review are transferred to the customer service background, and the customer service background is manually reviewed; if the customer service review passes, the corresponding appeal result is recorded and the driver's responsibility result is updated to no responsibility, and the driver is not punished; if the customer service review fails, the driver is punished and a corresponding amount is deducted, and the process ends;

[0018] S72: A record of appeals to a third-party platform is generated. The third-party generates an appeal ID and synchronizes the appeal ID and appeal result on the transport side.

[0019] Preferably, step S8 specifically includes: S81: if the appeal result is approved, the vehicle management synchronizes the result to the customer service side, and the customer service side records the corresponding appeal approval result and updates the driver's fault judgment result to not responsible, and does not punish the driver;

[0020] S82: If the appeal result is rejected, the vehicle management department will synchronize the data to the fleet, and the fleet will conduct manual review;

[0021] For records that fail the fleet review, penalties will be imposed and the corresponding amount will be deducted, and the process will end. For records that pass the fleet review, the appeal will be transferred to the customer service backend for manual review. If the customer service review is passed, the corresponding appeal result will be recorded and the driver's fault result will be updated to not responsible, and the driver will not be punished. If the customer service review fails, the driver will be punished and the corresponding amount will be deducted, and the process will end.

[0022] Compared with the prior art, the beneficial effects of the present invention are: a method designed by the present invention to improve the capacity utilization rate and optimize the capacity-side accountability model can improve the capacity utilization rate on the capacity side and avoid waste of capacity of blacklisted drivers; improve the efficiency of customer service personnel in handling objection orders and save customer service human resources; optimize the accountability model and business processes. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 It is a schematic diagram of the process of the present invention. DETAILED DESCRIPTION

[0024] 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.

[0025] See also Figure 1 ,The present invention provides a technical solution: a method for improving capacity utilization and optimizing the capacity-side accountability model,S1: The third-party platform receives a passenger complaint and issues a disposal and violation for the order, including a disposal ID, a disposal amount, a violation ID and a violation amount;

[0026] S2: The open platform on the online car-hailing capacity side receives the disposal and violation information, and determines the penalty type based on the background mapping type configuration;

[0027] S3: If the complaint type is met, the data is synchronized to the customer service backend. After receiving the data, the customer service backend determines whether the disposal ID is empty.

[0028] S31: If it is not empty, the customer service backend will automatically generate a complaint record in which the driver is responsible, and the order will be exempted. The exemption amount is taken from the disposal amount included in the disposal. At the same time, the exemption amount value is synchronized with the billing side and the penalty notification is synchronized with the vehicle management side.

[0029] S32: In the scenario where it is empty, the system caches for X minutes. If the disposal ID is polled within X minutes, a complaint record is automatically generated for the driver to be responsible, and the order is exempted. The exemption amount is taken from the disposal amount included in the disposal. If the disposal ID is not polled within X minutes, a complaint record is automatically generated for the driver to be responsible, and the order is exempted. The exemption amount is taken from the violation amount in the violation. At the same time, the exemption value is synchronized with the billing side and the penalty notification is synchronized with the vehicle management side.

[0030] S4: The billing side receives the reduction amount;

[0031] In this embodiment, preferably, step S4 specifically includes: S41: operating to reduce or exempt the amount of the passenger-side order and record it synchronously; S42: calculating the amount to be deducted from the driver's turnover through the driver's commission ratio, and synchronizing the value to the vehicle management side.

[0032] S5: After receiving the penalty notice and penalty amount, the vehicle management department issues the penalty to the driver;

[0033] S6: The driver decides whether to appeal;

[0034] In this embodiment, preferably, step S6 specifically includes: S61: if the driver does not appeal, a penalty is generated and a corresponding amount is deducted, and the process ends; S62: if the driver appeals, an appeal request may be initiated;

[0035] S7: The vehicle management department determines whether the driver’s appeal request can be appealed to the third-party platform;

[0036] In this embodiment, preferably, step S7 specifically includes: S71: records that cannot be appealed to the third-party platform are transferred to the fleet for manual review; records that fail to pass the fleet review are punished and a corresponding amount is deducted, and the process ends; records that pass the fleet review are transferred to the customer service background, and the customer service background is manually reviewed; if the customer service review passes, the corresponding appeal result is recorded and the driver's responsibility result is updated to no responsibility, and the driver is not punished; if the customer service review fails, the driver is punished and a corresponding amount is deducted, and the process ends;

[0037] S72: A record of appeals to a third-party platform is generated. The third-party generates an appeal ID and synchronizes the appeal ID and appeal result on the transport side.

[0038] S8: The vehicle management department on the transport capacity side records the appeal result according to the appeal ID.

[0039] In this embodiment, preferably, step S8 specifically includes: S81: if the appeal result is approved, the vehicle management synchronizes the result to the customer service side, and the customer service side records the corresponding appeal approval result and updates the driver's fault judgment result to not responsible, and does not punish the driver;

[0040] S82: If the appeal result is rejected, the vehicle management department will synchronize the data to the fleet, and the fleet will conduct manual review;

[0041] For records that fail the fleet review, penalties will be imposed and the corresponding amount will be deducted, and the process will end. For records that pass the fleet review, the appeal will be transferred to the customer service backend for manual review. If the customer service review is passed, the corresponding appeal result will be recorded and the driver's fault result will be updated to not responsible, and the driver will not be punished. If the customer service review fails, the driver will be punished and the corresponding amount will be deducted, and the process will end.

[0042] 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 improving capacity utilization and optimizing a capacity-side accountability model, characterized in that: S1: The third-party platform receives a passenger complaint and issues a disposal and violation statement for the order, including the disposal ID, disposal amount, violation ID, and violation amount; S2: The open platform on the online car-hailing capacity side receives the disposal and violation information, and determines the penalty type based on the background mapping type configuration; S3: If the complaint type is met, the data is synchronized to the customer service backend. After receiving the data, the customer service backend determines whether the disposal ID is empty. S31: If it is not empty, the customer service backend will automatically generate a complaint record in which the driver is responsible, and the order will be exempted. The exemption amount is taken from the disposal amount included in the disposal. At the same time, the exemption amount value is synchronized with the billing side and the penalty notification is synchronized with the vehicle management side. S32: In the scenario where it is empty, the system caches for X minutes. If the disposal ID is polled within X minutes, a complaint record is automatically generated for the driver to be responsible, and the order is exempted. The exemption amount is taken from the disposal amount included in the disposal. If the disposal ID is not polled within X minutes, a complaint record is automatically generated for the driver to be responsible, and the order is exempted. The exemption amount is taken from the violation amount in the violation. At the same time, the exemption value is synchronized with the billing side and the penalty notification is synchronized with the vehicle management side. S4: The billing side receives the reduction amount; S5: After receiving the penalty notice and penalty amount, the vehicle management department issues the penalty to the driver; S6: The driver decides whether to appeal; S7: The vehicle management department determines whether the driver’s appeal request can be appealed to the third-party platform; S8: The vehicle management department on the transport capacity side records the appeal result according to the appeal ID.

2. A method for improving capacity utilization and optimizing the capacity-side accountability model according to claim 1, characterized in that: Step S4 specifically includes: S41: reducing or exempting the amount of the passenger-side order and recording it synchronously; S42: calculating the amount to be deducted from the driver's turnover through the driver's commission ratio, and synchronizing the value to the vehicle management side.

3. The method for improving capacity utilization and optimizing the capacity-side accountability model according to claim 1, characterized in that: Step S6 specifically includes: S61: if the driver does not appeal, a penalty is generated and a corresponding amount is deducted, and the process ends; S62: if the driver appeals, an appeal request can be initiated.

4. The method for improving capacity utilization and optimizing the capacity-side accountability model according to claim 1, characterized in that: Step S7 specifically includes: S71: For records that cannot be appealed to the third-party platform, the appeal record is transferred to the fleet, and the fleet conducts manual review; for records that fail the fleet review, a penalty is imposed and a corresponding amount is deducted, and the process ends; for records that pass the fleet review, the appeal is transferred to the customer service background, and the customer service background conducts manual review; if the customer service review passes, the corresponding appeal result is recorded and the driver's fault result is updated to no fault, and the driver is not punished; if the customer service review fails, the driver is punished and a corresponding amount is deducted, and the process ends; S72: A record of appeals to a third-party platform is generated. The third-party generates an appeal ID and synchronizes the appeal ID and appeal result on the transport side.

5. The method for improving capacity utilization and optimizing the capacity-side accountability model according to claim 1, characterized in that: Step S8 specifically includes: S81: if the appeal result is approved, the vehicle management synchronizes the result to the customer service side, and the customer service side records the corresponding appeal approval result and updates the driver's fault judgment result to not responsible, and does not punish the driver; S82: If the appeal result is rejected, the vehicle management side will synchronize the data to the fleet, and the fleet will conduct a manual review. For records that fail the fleet review, penalties will be imposed and the corresponding amount will be deducted, and the process will end. For records that pass the fleet review, the appeal will be transferred to the customer service background, and the customer service background will conduct a manual review. If the customer service review is passed, the corresponding appeal result will be recorded and the driver’s liability result will be updated to not responsible, and the driver will not be punished. If the customer service review fails, the driver will be punished and the corresponding amount will be deducted, and the process will end.

Images