Customer information management method and device and storage medium

Abstract

The invention provides a client information management method and device and a storage medium. The method comprises the steps of obtaining client information of a sending client; according to the customer information, whether the mailing customers have a flow risk is judged, wherein the flow risk refers to the risk that the mailing customers who carry out mailing in a plurality of different regions belong to the same real customer; judging whether the mailing customer triggers a mailing account to repeatedly establish a file or not; and comprehensively judging whether to file the customer information of the mailing customer or not according to the trigger state of the repeated filing request of the mailing account and the customer flow risk judgment condition. According to the method, whether the mailing customer can repeatedly establish the file or not is judged by judging the triggering state of the repeated file establishment request of the mailing account and the sum of customer flow risk judgment conditions, so that file establishment after flow of the mailing customer is avoided, risks caused by scattered mail receiving and mailing behaviors are avoided, and the problem of profit reduction caused by utilization of preferential mailing in different regions is solved.

Description

Technical Field

[0001] The present invention relates to the field of distributed data technology, and in particular to a customer information management method, device and storage medium. Background Art

[0002] In actual logistics scenarios, the users involved in the logistics process are very diverse, and users often send and receive parcels across regions. This can make the sending and receiving behaviors more scattered and difficult to manage, and users may suffer losses from using discounts multiple times in different regions. Summary of the invention

[0003] The present invention provides a customer information management method, device and storage medium, aiming to solve the problem in the prior art that users in different regions take advantage of regional preferential delivery and collection, causing losses to logistics companies.

[0004] In one aspect, the present invention provides a method for managing customer information, the method comprising:

[0005] Obtain customer information of the sender;

[0006] Determine whether the sender has a risk of migration based on the customer information, where the risk of migration refers to the risk that the sender who sends parcels in multiple different regions is the same real customer;

[0007] Determine whether the sender triggers a request for repeated file creation of a sender account;

[0008] Whether to create a file for the customer information of the sender is comprehensively determined based on the triggering status of the repeated file creation request of the sender account and the customer's risk of migration.

[0009] In some possible embodiments, judging whether the mailing customer has a risk of vagrancy according to the customer information includes:

[0010] Check whether there is a historical customer transfer approval request matching the customer information;

[0011] If there are any historical customer roaming approval requests, determining whether all of the historical customer roaming approval requests are approved;

[0012] If all the historical customer migration approval requests are approved, it is determined that the sender does not have the risk of migration;

[0013] If not all of the historical customer migration approval requests are approved, the migration risk check of the sender is re-performed to determine whether the sender has a migration risk.

[0014] In some possible embodiments, if the historical customer's wandering approval request is not all approved, re-checking the risk of wandering of the sender to determine whether the sender has the risk of wandering includes:

[0015] Call the preset flow risk level verification model;

[0016] Determine the risk level of the mailing customer by using the risk level verification model;

[0017] According to the risk level of the sender, it is determined whether the sender has the risk of wandering.

[0018] In some possible embodiments, the comprehensively determining whether to create a file for the customer information of the sender customer based on the triggering status of the repeated file creation request of the sender account and the customer migration risk judgment situation includes:

[0019] If a request for duplicate file creation of a mailing account is triggered, and the mailing customer does not have the risk of roaming, the request for duplicate file creation of a mailing account is obtained, and it is determined whether the request for duplicate file creation of a mailing account is approved;

[0020] If the repeated file creation request of the shipping account is approved, the customer information is filed according to the repeated file creation request.

[0021] In some possible embodiments,

[0022] The comprehensively judging whether to create a file for the customer information of the sender according to the triggering status of the repeated file creation request of the sender account and the customer migration risk judgment situation includes:

[0023] If the sender has a risk of wandering, obtaining a target wandering risk level of the sender;

[0024] Determining whether the target migration risk level is within a preset migration risk level range;

[0025] If the target risk level of movement is within the preset risk level range and the repeated file creation request of the mailing account is not triggered, then multiple mailing monthly settlement accounts of the mailing customer are obtained, and a new customer movement approval request is generated according to the multiple mailing monthly settlement accounts;

[0026] The approval result of the new customer flow approval request is obtained, and according to the approval result, it is determined whether to create a file for the customer information of the sender.

[0027] In some possible embodiments,

[0028] If the target risk level of movement is within the preset risk level range, multiple monthly shipping accounts of the mailing customer are obtained, and a new customer movement approval request is generated according to the multiple monthly shipping accounts, including:

[0029] If the target risk level of movement is within the preset risk level range, obtaining multiple monthly shipping accounts of the sender;

[0030] Acquire the approval account numbers corresponding to the multiple mailing monthly settlement accounts to obtain multiple approval account numbers;

[0031] Determining whether the multiple approval accounts are the same;

[0032] If the multiple approval accounts are different, different customer flow approval requests are generated for different approval accounts.

[0033] In some possible embodiments,

[0034] The comprehensively judging whether to create a file for the customer information of the sender customer according to the triggering status of the repeated file creation request of the sender account and the customer migration risk judgment situation also includes:

[0035] If the target risk level of movement is within the preset risk level range and triggers a repeated file creation request for the mailing account, determining whether a repeated file creation request is received;

[0036] If a duplicate file creation request is received, a customer flow approval request corresponding to the sender is automatically generated;

[0037] If the duplicate file creation request is approved and the customer roving approval request is approved, a file will be created for the sender according to the duplicate file creation request.

[0038] In some possible embodiments, the comprehensively determining whether to create a file for the customer information of the sender customer based on the triggering status of the repeated file creation request of the sender account and the customer migration risk judgment situation further includes:

[0039] If the target template's risk level is not within the preset risk level range, no file will be created for the sender's customer information.

[0040] In another aspect, the present invention provides a method and device for managing customer information, the method and device for managing customer information comprising:

[0041] An information acquisition module is used to obtain customer information of the sender;

[0042] A migration risk judgment module, used to judge whether the sender has migration risk according to the customer information, wherein the migration risk refers to the risk that the sender who sends parcels in multiple different regions is the same real customer;

[0043] A duplicate file creation judgment module is used to judge whether the sender triggers a duplicate file creation request for the sender account;

[0044] The file creation judgment module is used to comprehensively judge whether to create a file for the customer information of the sender based on the trigger status of repeated file creation requests of the sender account and the customer migration risk judgment situation.

[0045] On the other hand, the present invention further provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program is loaded by a processor to execute the steps in the customer information management method as described in any one of the above items.

[0046] The present invention provides a customer information management method, device and storage medium, the method comprising: obtaining customer information of a mailing customer; judging whether the mailing customer has a risk of wandering according to the customer information, the risk of wandering referring to the risk that a mailing customer who sends mails in multiple different regions belongs to the same real customer; judging whether the mailing customer has triggered a request for repeated file creation of a mailing account; judging whether to create a file for the customer information of the mailing customer according to the triggering state of the repeated file creation request of the mailing account and the judgment of the risk of wandering of the customer. The present invention judges whether the mailing customer can be repeatedly filed by judging the triggering state of the repeated file creation request of the mailing account and the sum of the judgment of the risk of wandering of the customer, thereby avoiding the creation of a file after the mailing customer wanders, avoiding the risk of scattered mail collection and mailing behaviors, and the problem of reduced profits due to preferential mailing in different regions. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0048] Figure 1 Scenario diagram of the customer information management method system provided by an embodiment of the present invention

[0049] Figure 2 A schematic diagram of a flow chart of a method for managing customer information in an embodiment of the present invention;

[0050] Figure 3 A schematic diagram of a flow chart of an embodiment of the present invention for determining whether a mailing customer has a risk of vagrancy;

[0051] Figure 4 A schematic diagram of a process flow of a repeated file creation embodiment provided by an embodiment of the present invention;

[0052] Figure 5 A complete flow chart of an embodiment of a customer information management method provided by an embodiment of the present invention;

[0053] Figure 6 It is a schematic diagram of an embodiment of a customer information management method system provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0054] 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 those skilled in the art without creative work are within the scope of protection of the present invention.

[0055] In the description of the present invention, it should be understood that the terms "center", "longitudinal", "lateral", "length", "width", "thickness", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inside", "outside" and the like indicate positions or positional relationships based on the positions or positional relationships shown in the accompanying drawings, which are only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as limiting the present invention. In addition, the terms "first" and "second" are only used for descriptive purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of the present invention, the meaning of "multiple" is two or more, unless otherwise clearly and specifically defined.

[0056] In the present invention, the word "exemplary" is used to mean "used as an example, illustration or description". Any embodiment described as "exemplary" in the present invention is not necessarily to be construed as being preferred or advantageous over other embodiments. The following description is given to enable any technician in the field to implement and use the present invention. In the following description, details are listed for the purpose of explanation. It should be understood that a person of ordinary skill in the art can recognize that the present invention can be implemented without using these specific details. In other instances, well-known structures and processes will not be elaborated in detail to avoid obscuring the description of the present invention with unnecessary details. Therefore, the present invention is not intended to be limited to the embodiments shown, but is consistent with the widest scope consistent with the principles and features disclosed in the present invention.

[0057] The embodiments of the present invention provide a customer information management method, device and storage medium, which are described in detail below.

[0058] like Figure 1 , which is a schematic diagram of a scenario of a customer information management method system provided by an embodiment of the present invention. The customer information management method system may include a plurality of hosts 100 and servers 200. The hosts 100 and the servers 200 are connected via a network. The server 200 is integrated with a customer information management method device. Figure 1 In the server, host 100 can access server 200.

[0059] In the embodiment of the present invention, the server 200 is mainly used to obtain the customer information of the sender; determine whether the sender has a risk of migration based on the customer information, and the migration risk refers to the risk that the sender who sends parcels in multiple different regions belongs to the same real customer; determine whether the sender triggers a request for repeated filing of the sender account; and determine whether to file the customer information of the sender based on the triggering status of the request for repeated filing of the sender account and the judgment of the customer's migration risk.

[0060] In the embodiment of the present invention, the server 200 may be an independent server, or a server network or server cluster composed of servers. For example, the server 200 described in the embodiment of the present invention includes but is not limited to a computer, a network host, a single network server, a plurality of network server sets or a cloud server composed of a plurality of servers. Among them, the cloud server is composed of a large number of computers or network servers based on cloud computing. In the embodiment of the present invention, communication between the server and the host can be achieved through any communication method, including but not limited to mobile communications based on the 3rd Generation Partnership Project (3GPP), Long Term Evolution (LTE), Worldwide Interoperability for Microwave Access (WiMAX), or computer network communications based on TCP / IP Protocol Suite (TCP / IP), User Datagram Protocol (UDP), etc.

[0061] It is understandable that the host 100 used in the embodiment of the present invention may be a device including both receiving and transmitting hardware, that is, a device having receiving and transmitting hardware capable of performing two-way communication on a two-way communication link. Such a host may include: a cellular or other communication device having a single-line display or a multi-line display or a cellular or other communication device without a multi-line display. The specific host 100 may be a desktop terminal or a mobile terminal, and the host 100 may also be a mobile phone, a tablet computer, a laptop computer, etc.

[0062] Those skilled in the art will understand that Figure 1 The application environment shown in the figure is only one application scenario of the solution of the present invention and does not constitute a limitation on the application scenario of the solution of the present invention. Other application environments may also include Figure 1 More or fewer servers, or server network connections, as shown in Figure 1 Only one server and two hosts are shown. It can be understood that the customer information management method system can also include one or more other servers, and / or one or more hosts connected to the server network, which is not specifically limited here.

[0063] In addition, if Figure 1 As shown, the customer information management method system may also include a storage unit for storing data, such as the mailing information of the sender.

[0064] It should be noted that Figure 1 The scenario diagram of the customer information management method system shown is only an example. The customer information management method system and scenario described in the embodiment of the present invention are intended to more clearly illustrate the technical solution of the embodiment of the present invention, and do not constitute a limitation on the technical solution provided by the embodiment of the present invention. Ordinary technicians in this field can know that with the evolution of the customer information management method system and the emergence of new business scenarios, the technical solution provided by the embodiment of the present invention is also applicable to similar technical problems.

[0065] The present invention provides a customer information management method to prevent customers from wandering to different regions to take advantage of regional discounts to collect and send parcels, thereby causing economic losses to logistics companies. Customer wandering refers to the situation where customers register accounts in different regions to take advantage of the preferential activities of collecting and sending parcels in different regions to collect and send parcels.

[0066] like Figure 2 FIG. 1 is a flow chart of an embodiment of a customer information management method in an embodiment of the present invention. The customer information management method includes:

[0067] 201. Obtain the customer information of the sender.

[0068] In some embodiments of the present invention, the customer information of the sender may include three different types of information, specifically including the basic information of the sender, such as the sender and collection address, customer contact person, contact information, monthly settlement account number, etc. Among them, the monthly settlement account number refers to the account number registered by the sender in the logistics provider system for settling the fees incurred by sending and receiving parcels.

[0069] It can also include the collection and delivery order information generated by the sender within a period of time, such as the specific sender and recipient, the sending address and the receiving address within three months. Of course, when obtaining the collection and delivery order information, it is necessary to filter out invalid orders, such as orders with incorrect mobile phone numbers or addresses. Customer information can also include registered corporate information. This is because compared with individual users, corporate users generate more shipping behaviors, so corporate users are more likely to generate shipping behaviors in different regions. Therefore, the risk of corporate users wandering is greater, and the economic losses generated are also greater. Therefore, when the sender is a company, it is also necessary to obtain the registered corporate information on public platforms such as Tianyancha, such as corporate contacts, corporate contact contact information, company name, company registration address, etc. Of course, if the sender is an individual, there is no need to obtain registered corporate information.

[0070] It should be noted that, since only the sending behavior usually incurs fees, the customer information actually obtained may only include relevant information about the sending behavior, and there is no need to obtain relevant information about the receiving behavior. In the present invention, relevant data can be obtained from different systems or databases respectively and stored in the same database. Specifically, it can be stored in the form of a hive table.

[0071] 202. Determine whether the sender has a risk of vagrancy based on the customer information.

[0072] After obtaining the customer information of the sender, it is also necessary to verify whether the sender is a vagrant customer based on the customer information, or to determine whether the sender has the risk of vagrant. If the sender has the risk of vagrant, it needs to be paid special attention.

[0073] like Figure 3 As shown, a schematic diagram of a flow chart of an embodiment of the present invention for determining whether a mailing customer has a risk of diversion may include:

[0074] 301. Check whether there is any historical customer approval request that matches the customer information.

[0075] 302. If there are any historical customer roaming approval requests, determine whether all of the historical customer roaming approval requests have been approved.

[0076] 303. If all historical customer migration approval requests are approved, it is determined that there is no risk of migration for the sender.

[0077] 304. If not all historical customer migration approval requests are approved, re-check the migration risk of the sender to determine whether the sender has migration risk.

[0078] Specifically, in an embodiment of the present invention, if there is a risk of the sender wandering, a customer wandering approval request associated with the sender will be generated, and the customer wandering approval request needs to be approved to determine whether the sender really has a risk of wandering. Even if it is determined after approval that the customer does not have a risk of wandering, the generated customer wandering approval request still exists, indicating that the sender may have been at risk of wandering. Therefore, it can be determined whether there is a historical customer wandering approval request that matches the customer information. If so, it means that some previous behaviors of the sender may have caused the sender to have a risk of wandering. Among them, since the customer wandering approval request is generated based on the customer information, after obtaining new customer information, it can be determined whether there is a historical customer wandering approval request that matches the newly obtained customer information by comparing the newly obtained customer information with the customer information in the historical customer wandering approval request.

[0079] In the above embodiment, if it is determined through query that there are customer wandering approval requests that match the customer information, it is necessary to further determine whether all these customer wandering approval requests have been approved. The customer wandering approval request is manually approved, and the corresponding approval result will be generated. Each customer wandering approval request corresponds to an approval result; the approval result can be passed or not. If the approval results of all historical customer wandering approval requests are approved, it can be determined that all historical customer wandering approval requests have been approved, and the sender does not have a wandering risk. As long as there are customer wandering approval requests that have not been approved or customer wandering approval requests that are under review, it means that the sender has a certain degree of wandering risk, and it is necessary to pay special attention to the sender. Therefore, only when all customer wandering approval requests are approved can it be confirmed that the sender currently does not have a wandering risk.

[0080] If all historical customer migration approval requests are not approved, it means that the previous approval process determined that the sender has a migration risk. At this time, the sender needs to be re-verified for migration risk when the file is repeatedly created. In some embodiments, a preset migration risk level verification model can be directly called to determine the migration risk level of the sender, and further determine whether the sender has a migration risk based on the migration risk level of the sender.

[0081] Specifically, calling the wandering risk level judgment model may include: obtaining an initial wandering risk level judgment model and a training data set, the training data set including a plurality of training customer information and a first training customer wandering level of a plurality of training mailing customers; using the initial wandering risk level judgment model to perform feature extraction on the training customer information to obtain training wandering risk features; performing wandering risk level judgment on the training wandering risk features to determine a second training customer wandering level; calculating training loss values ​​of the first training wandering risk level and the second training customer wandering level; adjusting model parameters in the initial wandering risk level judgment model according to the training loss values ​​until a preset condition is reached, then stopping adjusting the model parameters in the initial wandering risk level judgment model to obtain a wandering risk level judgment model.

[0082] In the above embodiment, the initial wandering risk level judgment model may include a wandering risk feature extraction module, which can extract the training wandering risk features in the customer information; and further determine the second training wandering risk level based on the extracted training wandering risk features, thereby calculating the training loss value between the second training wandering risk level and the actual first wandering risk level. The model parameters in the initial wandering risk level judgment model are adjusted according to the training loss value, that is, the initial wandering risk level judgment model is adjusted. When the training wandering risk level determined by the wandering risk level judgment model after a certain adjustment reaches a preset loss value range with the training loss value between the actual wandering risk level, the training of the initial wandering risk level judgment model can be stopped, and it can be confirmed that the wandering risk level judgment model at this time has met the requirements.

[0083] When using the trained risk level judgment model to judge the risk level of wandering, the customer information is also extracted to obtain the risk characteristics of wandering, and the risk level of wandering is further determined based on the risk characteristics of wandering to obtain the risk level judgment result of wandering. It is also necessary to calculate the loss value corresponding to the risk level judgment result of wandering to determine whether the loss value is within the preset loss value range; if the loss value is within the preset loss value range, it can be confirmed that the risk level judgment result of wandering is the risk level of wandering corresponding to the sender. If the loss value is not within the preset loss value range, the process risk level judgment result is not the risk level of wandering corresponding to the sender, and it needs to be re-judged.

[0084] In the above embodiment, the judgment standard of the risk level of roaming corresponding to the mailing account in the training data set can be determined according to the actual situation. For example, the mailing address of all mailing orders generated by the mailing customer within a preset period of time, such as three months, is different from the registered address of the company corresponding to the mailing customer. If the proportion of different orders with different addresses in all orders within three months is within different ranges, it is determined that the risk level of roaming of the mailing customer is different. For example, if there are no orders with different addresses, it is considered that the mailing customer has no risk of roaming; if the proportion of orders with different addresses is between 0-10%, the risk of roaming of the mailing customer is level one; if the proportion of orders with different addresses is between 10-20%, the risk of roaming of the mailing customer is level two; if the proportion of orders with different addresses is greater than 20%, the risk of roaming of the mailing customer is level three.

[0085] 203. Determine whether the sender triggers a repeated file creation request for the sender account.

[0086] In an embodiment of the present invention, a sender can register multiple sender accounts for sending parcels, and the process of registering a sender account is also a process of creating a file within the logistics provider's system. The sender account file creation means that the logistics provider collects certain information of the sender to provide the sender with a shipping service; and because a sender can register multiple sender accounts, a sender can create files multiple times, that is, repeatedly create files. If the sender has already created a file, wanting to create a file again will trigger the repeated creation of the sender account file, and generate a request for repeated creation of the sender account file. Therefore, the present invention also needs to determine whether the sender has triggered the request for repeated creation of the sender account file, and only if it is triggered will the subsequent file creation be performed.

[0087] Among them, the sender usually operates in the business interface provided by the logistics company to perform duplicate filing. Usually, you first need to click the file creation button on the terminal page. At this time, it can only be said that the action of the duplicate filing request has been triggered, and the duplicate filing request has not been actually generated; and after the sender further fills in and submits the customer information, the duplicate filing request can be actually generated. That is, triggering a duplicate filing request and actually generating a duplicate filing request in the present invention are two different actions. Triggering a duplicate filing request for a sender account does not necessarily generate a duplicate filing request, but if you want to generate a duplicate filing request, you need to trigger a duplicate filing request for the sender account. And the generated duplicate filing request includes the customer information filled in or provided by the sender, so the generated duplicate filing request can be bound to the sender to determine that the duplicate filing request is generated based on the customer information corresponding to the current sender.

[0088] In an embodiment of the present invention, a mailing customer can trigger a request for duplicate file creation of a mailing account in a terminal device, and submit the customer information of the mailing customer. When a mailing customer triggers a request for duplicate file creation in a terminal device, a different prompt will pop up regardless of whether the mailing customer can duplicate file creation, to remind the mailing customer of the processing status of the current duplicate file creation process. For example, if it is determined that the mailing customer can duplicate file creation, the mailing customer is prompted to manually submit a duplicate file creation application, and the mailing customer is guided to the duplicate file creation application page on the operation interface of the terminal device to submit the file creation application.

[0089] 204. Based on the triggering status of repeated file creation requests for the mailing account and the risk assessment of customer migration, it is comprehensively determined whether to create a file for the customer information of the mailing customer.

[0090] In the present invention, the triggering status of the repeated filing request for the sender account number not only includes whether the repeated filing request for the sender account number is triggered on the terminal operation page, but also includes whether the repeated filing request for the sender account number is generated. At the same time, in the embodiment of the present invention, it is not only necessary to judge whether the sender has triggered the repeated filing request for the sender account number and whether the repeated filing request for the sender account number is generated, but also necessary to judge the risk of customer wandering, and comprehensively judge whether to repeat the filing of the sender; and repeating the filing of the sender is actually to repeat the filing of the customer information submitted by the sender. In the embodiment of the present invention, the judgment of the customer's wandering risk level includes not only judging whether the sender has the risk of wandering, but also judging the risk level of the sender. Generally speaking, if the sender's wandering risk level is high, it means that the risk of the sender's sending causing losses to the logistics company is high, and repeated filing is usually not allowed.

[0091] In the above embodiment, after determining the risk level of the sender, it is also necessary to determine whether the risk level is within the preset process risk level range. If the risk level of the sender is within the controllable range, the sender can usually be repeatedly profiled. If the risk level of the sender is level 1 or level 2, the sender can be profiled; if the risk level of the sender is level 3, the profile is not allowed regardless of the operation performed by the sender.

[0092] When the risk level of the sender's migration risk is within a controllable range and repeated filing is possible, it is necessary to further determine the trigger status of the repeated filing request for the sender's account and the risk status of the customer's migration risk, and then determine whether it is necessary to repeatedly file the sender's customer information.

[0093] Specifically, in some embodiments, if a repeated filing request for a mailing account is triggered, and it is determined that the mailing customer does not have a risk of evacuation, then the file can be created. At this time, it is necessary to generate a repeated filing request based on the specific customer information filled in or provided by the user, and approve the repeated filing request. If the repeated filing request is approved, the mailing customer can be filed according to the repeated filing request; if the repeated filing request is not approved, repeated filing of the mailing customer is not allowed. Approval of repeated filing requests usually involves reviewing whether the customer information filled in by the mailing customer is correct, or whether it meets the field filling rules, etc.

[0094] like Figure 4 As shown, a schematic diagram of a process flow of a repeated file creation embodiment provided by an embodiment of the present invention may include:

[0095] 401. If the sender has a risk of wandering, obtain the target wandering risk level of the sender.

[0096] 402. Determine whether the target migration risk level is within a preset migration risk level range.

[0097] When it is determined that the sender has a risk of wandering, it is necessary to further determine whether the sender's target wandering risk level is within the preset wandering risk level range; if it is within the wandering risk level range, it means that there is a possibility of duplicate file creation for the sender, and further approval of the sender is required to determine whether a duplicate file can be created.

[0098] 403. If the target risk level of movement is within the preset risk level range and the repeated file creation request for the mailing account is not triggered, multiple monthly mailing account numbers of the mailing customer are obtained, and a new customer movement approval request is generated based on the multiple monthly mailing account numbers.

[0099] 404. Obtain the approval result of the new customer movement approval request, and determine whether to create a file for the customer information of the sender according to the approval result.

[0100] At this point, you first need to determine whether the request for duplicate filing of the sender account has been triggered. It should be noted that this only means that the request for duplicate filing of the sender account has been triggered, and does not mean that the request for duplicate filing of the sender account has actually been generated. First, you need to obtain multiple monthly shipping accounts corresponding to the sender. The monthly shipping account is an account that the sender applies for at the logistics provider for settlement of fees. A sender can have multiple different monthly shipping accounts. And regenerate a new customer flow approval request based on multiple monthly shipping accounts, and obtain the corresponding approval results, so as to further determine whether the customer information of the sender can be filed based on the approval results.

[0101] In the above embodiment, generating a new customer roaming approval request may include:

[0102] If the target movement risk level is within the preset movement risk level range, multiple monthly settlement accounts of the sender are obtained; the approval accounts corresponding to the multiple monthly settlement accounts are obtained to obtain multiple approval accounts; it is determined whether the multiple approval accounts are the same; if the multiple approval accounts are different, different customer movement approval requests are generated for different approval accounts.

[0103] After determining multiple monthly shipping accounts, different customer movement approval requests can be generated for different monthly shipping accounts, and multiple customer movement approval requests can be obtained. However, when actually generating customer movement approval requests, it is necessary not only to obtain all the monthly shipping accounts corresponding to the shipping customer, but also to determine the approval account corresponding to each monthly shipping account. This is because in the actual file creation process, multiple monthly shipping accounts corresponding to a shipping customer may be approved by the same person or by different people; therefore, it is also necessary to determine the approval account corresponding to each monthly shipping account, so as to determine which approval account the customer movement approval request generated according to the monthly shipping account should be sent to for approval.

[0104] After obtaining multiple approval accounts, it is necessary to further determine whether the multiple approval accounts are the same; if the multiple approval accounts are different, different customer flow application processes need to be generated for different approval accounts, so as to send different customer flow application processes to different approval accounts for approval. That is, in the embodiment of the present invention, different customer flow approval requests are actually generated for different approval accounts, rather than generating different customer flow application processes for all the mailing monthly settlement accounts corresponding to the acquired mailing customers.

[0105] In the above embodiment, in the process of generating a customer's fugitive approval request, a notification pop-up window also needs to be popped up on the duplicate file creation interface of the terminal device to remind the sender that due to the risk of fugitive movement, the system automatically generates and submits relevant processes such as customer fugitive approval requests, etc., and reminds the sender that the sender can view relevant information at the designated location on the operation page.

[0106] After generating multiple customer flow approval requests, it is also necessary to determine whether a file can be created based on the multiple customer flow approval requests. Specifically, it is necessary to submit multiple customer flow approval requests to the corresponding approval account, and obtain the approval results of each approval account for the newly reviewed customer flow approval requests, and determine whether a file can be created based on the approval results. For example, when all customer flow approval requests corresponding to the sender are approved, that is, all approval results are passed, repeated file creation can be allowed; if some customer flow approval requests are being approved, or all customer flow approval requests are being approved, file creation is not allowed; at the same time, a notification pop-up window will pop up to remind the sender that there are still customer flow approval requests under approval, and the file cannot be created temporarily.

[0107] In the above embodiment, if any customer's roving approval request is not approved, that is, the approval result is not passed, then the other customer's roving approval requests that are being approved will be automatically withdrawn, and no further approval is required. At the same time, a notification pop-up window will pop up to remind the sender that the roving approval request of the mailing customer has not been approved, so the file cannot be created.

[0108] The above-mentioned embodiment discloses the filing process when there is a risk of migration for the sender and the risk level of migration is within the preset risk level range, but the repeated filing request for the sender account is not triggered. In other embodiments of the present invention, if it is determined that the sender has a risk of migration and the risk level of migration meets the preset risk level, and the repeated filing request for the sender account is also triggered; then it is necessary to determine whether a repeated filing request has been received. In the embodiment of the present invention, triggering a repeated filing request for the sender account and actually generating a repeated filing request are two different steps, so it is necessary to further determine whether a repeated filing request has been received.

[0109] If a duplicate filing request is received, a customer movement approval request corresponding to the sender will be automatically generated and approved. If no duplicate filing request is received, a notification pop-up window can be popped up on the operation interface to prompt the sender to fill in information to generate a duplicate filing request. After receiving a duplicate filing request, a notification pop-up window can also be popped up on the operation interface to remind the sender that due to the risk of movement, the background automatically generated and submitted a customer movement approval request, and the customer movement approval request needs to be approved; and the sender is reminded that the generated customer movement approval request can be viewed on the duplicate filing application list page.

[0110] In the above embodiment, repeated file creation requests also need approval. Only when all repeated file creation requests are approved and all customer wandering approval requests are approved, can repeated file creation be allowed for the mailing customer. For repeated file creation requests and customer wandering approval requests, as long as there are repeated file creation requests or customer wandering approval requests under approval, repeated file creation is not allowed; and if any repeated file creation request or customer wandering approval request fails to pass the approval, repeated file creation is also not allowed. Regardless of the status of the repeated file creation request or customer wandering approval request, a notification pop-up window will pop up to prompt the mailing customer whether a file can be created. For example, if the repeated file creation request or customer wandering approval request is under approval, a notification pop-up window will pop up to prompt: the repeated file creation request and / or customer wandering approval request is under approval. Please try again after the repeated file creation request and / or customer wandering approval request is approved. Or if the repeated file creation request and / or customer wandering approval request fails to pass the approval, a notification pop-up window will pop up to prompt: the repeated file creation request and / or customer wandering approval request is rejected, and file creation is not supported for the time being. Or when the sender actively withdraws the duplicate file creation, a notification pop-up window will pop up to remind you: the duplicate file creation request and / or the customer's flow approval request has been withdrawn, and file creation is not supported at the moment.

[0111] In an embodiment of the present invention, a sender can trigger a request for repeated file creation of a sender account on a terminal device, and a pop-up window on the terminal device operation interface prompts the sender to fill in information to repeat the file creation based on the filled-in information. For example, when a sender triggers a request for repeated file creation of a sender account on a terminal device, the terminal device enters the "Create Customer File" interface, adds a "Primary Sender" field to the interface, and pops up a prompt "Please Add" to prompt the sender to add a sender. The sender can enter the interface for adding a primary sender by clicking the "Primary Sender" field. The interface displays two primary sender information sections with empty values ​​by default, and supports adding and deleting primary senders.

[0112] When the "name" or "contact information" of the primary sender section displayed on the operation interface is empty, or the primary sender is deleted, it cannot be saved; when the sender clicks the "Save" button on the operation interface to save, the operation interface will pop up a prompt "Please fill in the correct primary sender information". At the same time, the primary sender is limited to five; if the information of five senders has been filled in, if the sender continues to click the button to add a new primary sender, the operation interface will pop up a prompt "The primary sender can only enter five digits at most."

[0113] When filling in the main sender information, the main sender's contact information includes the extension number and mobile phone number; the extension number is optional and supports the input of "+" and numbers. When the partition number is empty, the verification number input box must enter a number starting with "1" and 11 digits long, that is, the mobile phone number. The verification number input box must enter a string of "no more than 14 digits"; that is, the length of the password does not exceed 14 digits. If the contact information entered does not meet the above requirements, a prompt "Please enter the correct contact information" will pop up.

[0114] The backend of the terminal device will encrypt the input information and obtain the encrypted information. When the sender completes the creation of the customer profile information and clicks "Next" on the operation interface, the sender will be subject to risk management inspection, including but not limited to determining whether the sender has a risk of vagrancy and the level of vagrancy risk, determining whether the sender triggers a repeated file creation request for the sender account, and whether a repeated file creation request is generated. At this time, different operation instructions and pop-up prompts can be triggered according to the different types of risk management triggered.

[0115] For example, if no risk is triggered, a pop-up window will be displayed: According to the current logic, the file creation is supported. If there is no risk of migration and the repeated file creation request of the mailing account is triggered, a pop-up window will be displayed to guide the user to the repeated file creation application page, and prompt the customer to manually submit the repeated file creation application. If the mailing customer has a risk of migration and the repeated file creation request of the mailing account is not triggered, the backend will automatically generate and submit the customer migration approval request, and a pop-up window will be displayed on the front-end operation interface: There is a risk of customer migration, and the backend has automatically submitted the application for it. For details, please go to the "Customer Migration Approval Request List". If the mailing customer has a risk of migration and the repeated file creation request of the mailing account is triggered, the mailing customer will be guided to the repeated file creation page to manually submit the repeated file creation application. At the same time, multiple mailing monthly settlement accounts suspected of migration corresponding to the mailing customer and the approval accounts corresponding to the multiple mailing monthly settlement accounts are obtained. Compare whether the multiple approval accounts are the same approval account, and only generate one customer migration approval request for the same approval account, and generate different customer migration approval requests for different approval accounts. At the same time, the front-end operation interface will prompt the user: this customer is at risk of customer migration, and the background has automatically submitted an application for him. Details can be viewed in the "Customer Migration Approval Request List".

[0116] On the basis of the above embodiment, if the customer continues to click "Next" on the "Create File Page", the operation interface will generate different pop-up prompts according to the different process approval status. For example, if a duplicate file creation request is generated and submitted but the customer does not have the risk of evacuation, if the duplicate file creation request is under review at this time, a pop-up window will prompt: The duplicate file creation process application is under review, please try again after the process is approved. If the duplicate file creation request is actively withdrawn by the customer, a pop-up window will prompt: The duplicate file creation process application has been withdrawn, and file creation is not supported for the time being. Or if the duplicate file creation request is not approved, a pop-up window will prompt: The duplicate file creation request is not approved, and file creation is not supported for the time being. In the embodiment of the present invention, the specific content of the pop-up window can be determined according to the actual process situation, and is not limited here.

[0117] In some embodiments, a new customer wandering approval request list page entry is required in the operation interface of the terminal device, and it is supported to enter the customer wandering approval request list page and the details page for query after clicking. The customer wandering approval request list page can be displayed according to: "Application in progress", "Application successful", and "Application failed" respectively; the application information only displays the customer name, process code (for example, the process code for triggering repeated file creation requests is 1, and the process code for customers with wandering risks is 2) and the application date. The details page is displayed in two sections: "Information on customers to be filed" and "Information on suspected wandering customers". The "Information on customers to be filed" section displays four fields: "Customer name", "Customer decision maker", "Customer contact number" and "Customer first-level industry", and the "Information on suspected wandering customers" section displays four fields: "Customer name", "Monthly settlement account", "Customer decision maker" and "Customer contact number".

[0118] It should be emphasized that in the above embodiment, triggering a request for repeated file creation of a mailing account and generating a request for repeated file creation of a mailing account are two different actions, and the generated request for repeated file creation of a mailing account also needs to be approved, and the main thing is to approve whether the customer information in the request for repeated file creation of the mailing account is correct and whether it meets the preset filling rules. At the same time, after determining the target risk level of the mailing customer, if the target risk level is within the preset risk level range, such as the first or second risk, it is necessary to further generate a new customer movement approval request, and determine whether the file can be repeated based on the approval result of the new customer movement approval request. If it is not within the risk level range, such as the third risk, it means that the mailing customer has a high risk of movement at this time, and there is no need to generate a new customer movement approval request, and the file is not allowed to be created directly.

[0119] like Figure 5 FIG. 1 is a complete flow chart of an embodiment of a customer information management method provided by an embodiment of the present invention. Figure 5It includes a customer relationship management system (CRM system) and a risk control system. The mailing customer uses the CRM system to create a customer file and fill in the customer's primary sender information. If the primary sender is an enterprise, it is also necessary to query the CRM system whether the newly added primary sender exists, or to determine whether the newly added primary sender has been archived. In the embodiment of the present invention, it is mainly to query whether there is customer information matching the newly added primary sender information in the CRM system to determine whether the newly added primary sender has been archived.

[0120] If it exists, it triggers the duplicate filing process, that is, it triggers the duplicate filing request of the sender account. The sender needs to further fill in the customer information and generate a duplicate filing request to submit for approval; if it is approved, the newly added customer information needs to be added to the CRM system. If the newly added main sender does not exist in the CMR system, it will enter the process of determining whether the sender is a wandering customer. If the sender is a wanderer, it is necessary to submit the customer information corresponding to the wandering customer, and further generate and submit the customer wandering approval request. At the same time, the submitted wandering customer information is approved, and the wandering data such as the customer information corresponding to the wandering customer is synchronized to the wandering system approval platform. For the sender, if it is determined that the sender has a wandering risk, it is necessary to notify the customer by SMS to inform the customer that the customer is a wandering customer; at the same time, the sender can also query the approval status of the customer wandering approval request through the wandering system approval platform.

[0121] After the customer flow approval request is submitted for approval, if the customer flow approval request is approved, the customer information of the newly added sender can be added to the CRM system; if the approval is not passed, the sender is required to resubmit new customer information and be approved.

[0122] exist Figure 5 In the process, the CRM system will also regularly query the customer information and monthly shipment settlement information in its own database to send the customer information and monthly shipment settlement information corresponding to the customers with the risk of vagrancy to the data platform, and further send them to the risk control database in the risk control system through the data platform. The risk control system can then query whether there is customer information corresponding to the vagrancy customers based on the acquired data.

[0123] In order to better implement the customer information management method in the embodiment of the present invention, based on the customer information management method, the embodiment of the present invention also provides a customer information management method device, such as Figure 6 As shown, the customer information management method system includes:

[0124] The information acquisition module 601 is used to acquire the customer information of the mailing customer.

[0125] The risk of migration judgment module 602 is used to judge whether the sender has the risk of migration based on the customer information. The risk of migration refers to the risk that the sender who sends parcels in multiple different regions belongs to the same real customer.

[0126] The duplicate file establishment judgment module 603 is used to judge whether the sender triggers duplicate file establishment of the sender account.

[0127] The file creation judgment module 604 is used to comprehensively judge whether to create a file for the customer information of the sender based on the trigger status of repeated file creation requests of the sender account and the customer's risk of migration.

[0128] The present invention provides a customer information management method and device, firstly obtaining the customer information of the sender; judging whether the sender has the risk of wandering according to the customer information, the wandering risk refers to the risk that the sender who sends parcels in multiple different regions belongs to the same real customer; judging whether the sender triggers the repeated filing of the sender account; judging whether to file the customer information of the sender according to the triggering state of the repeated filing request of the sender account and the judgment of the risk of wandering of the customer. The present invention comprehensively judges whether the sender can repeatedly file by judging the triggering state of the repeated filing request of the sender account and the judgment of the risk of wandering of the customer, thereby avoiding the file creation after the sender wanders, avoiding the risk of scattered collection and sending behaviors, and avoiding the problem of reduced profits due to preferential shipping in different regions.

[0129] In some embodiments, the risk determination module 602 is mainly used to:

[0130] Check whether there is a historical customer transfer approval request that matches the customer information;

[0131] If there are any historical customer migration approval requests, determine whether all of the historical customer migration approval requests have been approved; if all of the historical customer migration approval requests have been approved, it is determined that the sender does not have a migration risk;

[0132] If not all historical customer migration approval requests are approved, the migration risk check of the sender will be conducted again to determine whether the sender has a migration risk.

[0133] In some embodiments, the risk determination module 602 is mainly used to:

[0134] Call a preset risk level verification model; determine the risk level of the sender using the risk level verification model; and determine whether the sender has a risk of wandering based on the risk level of the sender.

[0135] The file creation judgment module 604 is mainly used for: if a repeated file creation request for a sender account is triggered and there is no risk of the sender customer flowing into the mail, then the repeated file creation request for the sender account is obtained, and it is determined whether the repeated file creation request for the sender account is approved; if the repeated file creation request for the sender account is approved, the customer information is archived according to the repeated file creation request.

[0136] In some embodiments, the profile determination module 604 is mainly used to:

[0137] If the sender has a risk of wandering, then obtain the sender's target wandering risk level;

[0138] Determine whether the target's risk level is within the preset risk level range;

[0139] If the target risk level of movement is within the preset risk level range and the request for duplicate file creation of the mailing account is not triggered, multiple monthly mailing account numbers of the mailing customer are obtained, and a new customer movement approval request is generated based on the multiple monthly mailing account numbers;

[0140] Get the approval result of the new customer flow approval request, and determine whether to create a file for the sender's customer information based on the approval result.

[0141] In some embodiments, the profile determination module 604 is mainly used to:

[0142] If the target movement risk level is within the preset movement risk level range, multiple monthly settlement accounts of the sender are obtained; the approval accounts corresponding to the multiple monthly settlement accounts are obtained to obtain multiple approval accounts; it is determined whether the multiple approval accounts are the same; if the multiple approval accounts are different, different customer movement approval requests are generated for different approval accounts.

[0143] In some embodiments, the profile determination module 604 is mainly used to:

[0144] If the target risk level is within the preset risk level range and triggers a repeated file creation request for the mailing account, determine whether a repeated file creation request is received;

[0145] If a duplicate file creation request is received, a customer flow approval request corresponding to the sender will be automatically generated;

[0146] If the duplicate file creation request is approved and the customer's flow approval request is approved, the sender will be filed according to the duplicate file creation request.

[0147] In some embodiments, the profile building determination module 604 is mainly used to:

[0148] If the target template's risk level is not within the preset risk level range, the sender's customer information will not be filed.

[0149] The present invention also provides a computer-readable storage medium, which may include: a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, etc. The storage medium stores a computer program, which is loaded by a processor to execute the steps of any one of the customer information management methods provided in the embodiments of the present invention. For example, the computer program may be loaded by a processor to execute the following steps:

[0150] Obtain the customer information of the sender; determine whether the sender has a risk of migration based on the customer information. Migration risk refers to the risk that a sender who sends parcels in multiple different regions belongs to the same real customer; determine whether the sender has triggered duplicate filing of the sender account; and comprehensively determine whether to file the sender's customer information based on the trigger status of the duplicate filing request for the sender account and the customer migration risk determination.

[0151] It should be noted that since the method of the embodiment of the present invention is executed in an electronic device, the processing objects of each electronic device exist in the form of data or information. For example, time is actually time information. It can be understood that if size, quantity, position, etc. are mentioned in subsequent embodiments, they are all corresponding data for processing by the electronic device. The details will not be repeated here.

[0152] The above is a detailed introduction to a customer information management method, device and storage medium provided in an embodiment of the present invention. Specific examples are used in this article to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea; at the same time, for technical personnel in this field, according to the idea of ​​the present invention, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present invention.

Claims

1. A customer information management method, characterized in that: The method comprises: Obtain customer information of the sender; Determine whether the sender has a risk of migration according to the customer information, where the risk of migration refers to the risk that the sender who sends parcels in multiple different regions is the same real customer; Determine whether the sender triggers a request for repeated file creation of a sender account; Whether to create a file for the customer information of the sender is comprehensively determined based on the triggering status of the repeated file creation request of the sender account and the customer's risk of migration.

2. The customer information management method according to claim 1, characterized in that: The determining, based on the customer information, whether the mailing customer has a risk of vagrancy includes: Check whether there is a historical customer transfer approval request matching the customer information; If there are any historical customer roaming approval requests, determining whether all of the historical customer roaming approval requests are approved; If all the historical customer migration approval requests are approved, it is determined that the sender does not have the risk of migration; If not all of the historical customer migration approval requests are approved, the migration risk check of the sender is re-performed to determine whether the sender has a migration risk.

3. The customer information management method according to claim 2, characterized in that: If the historical customer's wandering approval request is not fully approved, re-checking the risk of wandering of the sender to determine whether the sender has the risk of wandering, including: Call the preset flow risk level verification model; Determine the risk level of the mailing customer by using the risk level verification model; According to the risk level of the sender, it is determined whether the sender has the risk of wandering.

4. The customer information management method according to claim 3, characterized in that: The comprehensively judging whether to create a file for the customer information of the sender according to the triggering status of the repeated file creation request of the sender account and the customer migration risk judgment situation includes: If a request for duplicate file creation of a mailing account is triggered, and the mailing customer does not have the risk of roaming, the request for duplicate file creation of a mailing account is obtained, and it is determined whether the request for duplicate file creation of a mailing account is approved; If the repeated file creation request of the shipping account is approved, the customer information is filed according to the repeated file creation request.

5. The customer information management method according to claim 3, characterized in that: The comprehensively judging whether to create a file for the customer information of the sender according to the triggering status of the repeated file creation request of the sender account and the customer migration risk judgment situation includes: If the sender has a risk of wandering, obtaining a target wandering risk level of the sender; Determining whether the target migration risk level is within a preset migration risk level range; If the target risk level of movement is within the preset risk level range and the repeated file creation request of the mailing account is not triggered, then multiple mailing monthly settlement accounts of the mailing customer are obtained, and a new customer movement approval request is generated according to the multiple mailing monthly settlement accounts; The approval result of the new customer flow approval request is obtained, and according to the approval result, it is determined whether to create a file for the customer information of the sender.

6. The customer information management method according to claim 5, characterized in that: If the target risk level of movement is within the preset risk level range, multiple monthly shipping accounts of the mailing customer are obtained, and a new customer movement approval request is generated according to the multiple monthly shipping accounts, including: If the target risk level of movement is within the preset risk level range, obtaining multiple monthly shipping accounts of the sender; Acquire the approval account numbers corresponding to the multiple mailing monthly settlement accounts to obtain multiple approval account numbers; Determining whether the multiple approval accounts are the same; If the multiple approval accounts are different, different customer flow approval requests are generated for different approval accounts.

7. The customer information management method according to claim 5, characterized in that: The comprehensively judging whether to create a file for the customer information of the sender customer according to the triggering status of the repeated file creation request of the sender account and the customer migration risk judgment situation also includes: If the target risk level of movement is within the preset risk level range and triggers a repeated file creation request for the mailing account, determining whether a repeated file creation request is received; If a duplicate file creation request is received, a customer flow approval request corresponding to the sender is automatically generated; If the duplicate file creation request is approved and the customer roving approval request is approved, a file will be created for the sender according to the duplicate file creation request.

8. The customer information management method according to claim 5, characterized in that: The comprehensively judging whether to create a file for the customer information of the sender customer according to the triggering status of the repeated file creation request of the sender account and the customer migration risk judgment situation also includes: If the target template's risk level is not within the preset risk level range, no file will be created for the sender's customer information.

9. A customer information management method and device, characterized in that: The device comprises: An information acquisition module is used to obtain customer information of the sender; A migration risk judgment module, used to judge whether the sender has migration risk according to the customer information, wherein the migration risk refers to the risk that the sender who sends parcels in multiple different regions is the same real customer; A duplicate file creation judgment module is used to judge whether the sender triggers a duplicate file creation request for the sender account; The file creation judgment module is used to comprehensively judge whether to create a file for the customer information of the sender based on the trigger status of repeated file creation requests of the sender account and the customer's risk of migration.

10. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and the computer program is loaded by a processor to execute the steps in the customer information management method according to any one of claims 1 to 8.

Images