Information pulling method, device and equipment and computer storage medium

Abstract

The invention provides an information pulling method and device, equipment and a computer storage medium. The information pulling method comprises the steps that account opening event information issued to an information list by a customer service system is acquired, and the customer service system issues the account opening event information to the information list in real time after receiving an account opening request of a user; under the condition that the user is of the target type, pulling user related information of the user according to the account opening event information; and adding the user to the customer management system according to the user related information. Through the information pulling method, the timeliness of user maintenance is improved.

Description

Technical Field

[0001] This application relates to the field of information processing, and in particular to an information retrieval method, apparatus, device, and computer storage medium. Background Technology

[0002] The enterprise's operating system includes a customer management system and a customer service system. The customer service system focuses on responding to customer needs and providing specific services to customers. It is the system for interaction between the enterprise and its customers. The customer management system focuses on the refined management of the entire customer lifecycle (such as obtaining complete customer information, identifying the person responsible for follow-up, smoothly initiating demand docking, product recommendation, and regular follow-up visits). It is the enterprise's internal management system.

[0003] Maintaining information from the customer service system in a timely manner in the customer management system is a prerequisite for ensuring the effectiveness of internal management. After opening an account in the customer service system, customers enter their information into the customer management system, enabling the company's internal teams to initiate internal management processes.

[0004] In existing technologies, for newly opened accounts, customer information is typically maintained in the customer management system manually: customers complete account opening through the customer service system, and account managers manually compile customer information from account opening records and enter it into the customer management system. This method relies on manual operation by account managers, and it often results in situations where the information is not entered into the customer management system even after several hours or even days have passed since the user opened the account, leading to low timeliness in user maintenance. Summary of the Invention

[0005] To address the aforementioned technical problems, this application proposes an information retrieval method, apparatus, device, and computer storage medium.

[0006] To address the aforementioned technical problems, this application proposes an information retrieval method, which includes: obtaining account opening event information sent to an information list by a customer service system, wherein the customer service system sends the account opening event information to the information list in real time after receiving a user's account opening request; if the user is a target type, retrieving the user's relevant user information based on the account opening event information; and adding the user to a customer management system based on the relevant user information.

[0007] The step of adding the user to the customer management system based on the user-related information includes: obtaining promotional slot information from the user-related information; determining a user addition strategy based on the promotional slot information; and adding the user to the customer management system based on the user addition strategy.

[0008] The process of adding the user to the customer management system based on the user addition strategy includes: creating a target link object corresponding to the promotion slot information in the customer management system; injecting dependencies into the target link object according to the user addition strategy; and adding the user to the customer management system through the target link object with injected dependencies.

[0009] The step of adding the user to the customer management system through the target link object after injecting dependencies includes: creating the user in the customer management system through the target link object after injecting dependencies, and recording the user's operation log.

[0010] The method further includes: obtaining business association object information from the user-related information; determining the target business object corresponding to the user based on the business association object information and the promotion slot information; and sending the user's account opening prompt information to the target business object.

[0011] The process of determining the target business object corresponding to the user based on the business-related object information and the promotion slot information includes: when the promotion slot information indicates that the promotion object is a business entity object, obtaining the first business object corresponding to the business-related object information and determining the first business object as the target business object; when the promotion slot information indicates that the promotion object is an advertiser object, obtaining the target advertiser object corresponding to the user; determining the second business object corresponding to the target advertiser object as the target business object; when the promotion slot information is empty and the business-related object information is not empty, obtaining the third business object corresponding to the business-related object information, and not setting the target business object for the user when the third business object does not belong to the preset business object.

[0012] Before adding the user to the customer management system based on the user-related information, the method further includes: determining whether the user identifier corresponding to the user has already been recorded in the customer management system; and deleting the account opening event information if the user identifier is included in the customer management system.

[0013] To address the aforementioned technical problems, this application proposes an information retrieval device, which includes: The acquisition module is used to acquire account opening event information sent to the information list by the customer service system. The customer service system sends the account opening event information to the information list in real time after receiving a user's account opening request.

[0014] The retrieval module is used to retrieve user-related information of the user based on the account opening event information when the user is the target type.

[0015] The add module is used to add the user to the customer management system based on the user's relevant information.

[0016] To address the aforementioned technical problems, this application also proposes an information retrieval device, which includes a memory and a processor coupled to the memory; wherein the memory is used to store program data, and the processor is used to execute the program data to implement the information retrieval method as described above.

[0017] To address the aforementioned technical problems, this application also proposes a computer storage medium for storing program data, which, when executed by a computer, is used to implement the aforementioned information retrieval method.

[0018] Compared with existing technologies, the beneficial effects of this application are as follows: When the customer service system receives an account opening request, it sends the account opening event information to the information list in real time. The customer management system retrieves the account opening event information from the information list, automatically pulls the user's relevant information, and adds the user to the customer management system based on the user's relevant information. This replaces the manual information retrieval method in related technologies. After an account opening event occurs, the user can be immediately maintained in the customer management system, reducing the time required to maintain user-related information from several hours / days to minutes after the account opening event occurs. This ensures that users can be promptly included in the customer management system after opening an account and avoids the problem of no one following up after the user opens an account. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. Wherein: Figure 1 This is a flowchart illustrating an embodiment of the information retrieval method provided in this application; Figure 2 This is a timeline diagram of the enterprise operation system provided in this application; Figure 3 This is a flowchart illustrating the process of adding users to the customer management system provided in this application; Figure 4 This is a schematic diagram of the structure of an embodiment of the information retrieval device provided in this application; Figure 5 This is a schematic diagram of the structure of an embodiment of the information retrieval device provided in this application; Figure 6 This is a schematic diagram of the structure of an embodiment of the computer storage medium provided in this application. Detailed Implementation

[0020] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0021] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the application described herein can be implemented, for example, in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0022] The information retrieval method of this application is applied to an information retrieval device, which can be a server, a terminal device, or a system in which the server and the terminal device cooperate with each other. Accordingly, the various parts of the information retrieval device, such as each unit, subunit, module, and submodule, can all be set in the server, all in the terminal device, or separately in the server and the terminal device.

[0023] Furthermore, the aforementioned server can be either hardware or software. When the server is hardware, it can be implemented as a distributed server cluster consisting of multiple servers, or as a single server. When the server is software, it can be implemented as multiple software programs or software modules, such as software or software modules used to provide distributed server functionality, or as a single software program or software module; no specific limitations are made here.

[0024] Please refer to details. Figure 1 , Figure 1 This is a flowchart illustrating an embodiment of the information retrieval method provided in this application, as shown below. Figure 1 As shown, the specific steps are as follows: Step S11: Obtain account opening event information sent to the information list by the customer service system, wherein the customer service system sends the account opening event information to the information list in real time after receiving the user's account opening request.

[0025] In the embodiments of this application, please refer to Figure 2 , Figure 2 This is a timeline diagram of the enterprise operation system provided in this application, such as... Figure 2 As shown, the entire enterprise operation system includes a customer service system (divided into front-end pages and counter side), an event system, and a customer management system.

[0026] Customers, or users, access the account opening interface through account opening promotion information on the front-end page, submit account opening materials to the counter, the counter receives the account opening materials, completes the account opening event, and records the account opening event information to the information list in the event system. Upon receiving the account opening event information, the event system sends it to the customer management system. After receiving the account opening event information, the customer management system retrieves the user-related information corresponding to the account opening event information from the customer service system and imports it into the customer management system for user maintenance.

[0027] Among them, account opening event information is data directly related to the account opening behavior that is automatically generated by the customer service system when a customer completes the account opening operation, including but not limited to account opening event identifier, user identifier, account opening service provider identifier, and account opening event time.

[0028] When the customer service system receives the account opening information, it means that the customer service system has received the user's account opening request. Upon receiving the account opening information, the customer service system immediately sends the account opening event information to the information list in the event system, and the customer management system retrieves the corresponding account opening event information from the information list.

[0029] Step S12: If the user is the target type, retrieve the user's relevant information based on the account opening event information.

[0030] In this embodiment of the application, the customer management system, as a core management tool within the enterprise, has a clearly defined management scope, namely, it only manages users of a specified customer type. Therefore, after receiving the account opening event information, i.e. after the account opening event occurs, the customer management system first determines whether the user's customer type is the target type according to the preset judgment criteria. Only when the user's customer type is the target type will the system retrieve the user's relevant information based on the account opening event information.

[0031] User-related information is the core data of the user, including the user's basic identity information, promotional position information, and business-related object information. Promotional position information is used to indicate the promotional object that publishes account opening promotion information (such as promotional advertisements), including but not limited to advertisers, business entities, etc. Business-related object information is used to indicate the business entities associated with the user account after the user opens an account. The business entities refer to the account managers who provide business services such as consulting services to the user account.

[0032] For example, customer types can include large customer types and small customer types. Large customer types typically refer to users with higher business cooperation potential, longer cooperation cycles, and higher customer value, while small customer types generally refer to users with simple needs and smaller cooperation scales. Including large customer types in the customer management system helps to allocate more resources to demand discovery, relationship maintenance, and opportunity conversion. However, including small customers in the customer management system would divert internal team attention, increase system data redundancy, and ultimately reduce management efficiency; therefore, small customers are generally not included in the scope of the customer management system within an enterprise. Correspondingly, the target type specifically refers to the large customer type. After receiving account opening event information, the customer management system determines whether the user's customer type is a large customer type based on preset judgment criteria. Only if the user's customer type is a large customer type will the system retrieve the user's relevant information based on the account opening event information.

[0033] In one embodiment, a user's customer type can be determined based on the account opening service provider identifier in the account opening event information. The account opening service provider identifier indicates the service type, which may include, but is not limited to, corporate large customer service, personal premium service, and personal ordinary service. Corresponding account opening service provider identifiers include corporate large customer account opening identifiers, personal premium account opening identifiers, and personal ordinary account opening identifiers, etc. Specifically, when the account opening service provider identifier is a corporate large customer account opening identifier or a personal premium account opening identifier, it can be determined whether the customer belongs to the target customer type.

[0034] Step S13: Add the user to the customer management system based on the user-related information.

[0035] In this embodiment, after retrieving user-related information, the user is added to the customer management system based on the user-related information, and the customer manager can then implement the management process for the user in the customer management system.

[0036] Through the above embodiments, when the customer service system receives an account opening request, it sends the account opening event information to the information list in real time. The customer management system retrieves the account opening event information from the information list, automatically pulls the user's relevant information, and adds the user to the customer management system based on the user's relevant information. This replaces the manual information retrieval method in related technologies. After an account opening event occurs, the user can be immediately maintained in the customer management system, reducing the time required to maintain user-related information from several hours / days to minutes after the account opening event occurs. This ensures that users can be promptly included in the customer management system after opening an account and avoids the problem of no one following up after the user opens an account.

[0037] In an optional embodiment, adding the user to the customer management system based on the user-related information includes: obtaining promotional slot information from the user-related information; determining a user addition strategy based on the promotional slot information; and adding the user to the customer management system based on the user addition strategy.

[0038] The user addition strategy can be a consensus strategy between the customer service system and the customer management system, used to describe the operation instructions that the customer management system needs to perform based on the user's relevant information to generate the corresponding account. In this embodiment, when adding a user to the customer management system, different promotional information in the user's relevant information leads to different addition strategies.

[0039] The promotional slot information in the user's information indicates which specific account opening promotion information the user entered the account opening process through, and is used to trace the source of the user's account opening promotion. The promotional slot information includes promotional object information, such as the promotional object identifier and promotional object type information used to indicate the corresponding promotional object of the account opening promotion information. For example, the promotional object type may include the advertiser object type and the business object type. The promotional object identifier is used to uniquely identify the advertiser object or the business object. Furthermore, the promotional slot information may also include a null value or a null value identifier, indicating that there is no promotional slot.

[0040] When the promotional information indicates that the target of the promotion is a business entity, i.e., sales account opening, the corresponding account opening promotion information includes an exclusive account opening link held by the business entity (such as internal sales personnel of an enterprise) and pushed to the customer. The corresponding user addition strategy includes instructions on operation items to associate with the corresponding business entity when adding users.

[0041] When the promotional information indicates that the target audience is an advertiser, i.e., channel account opening, the corresponding account opening promotional information includes a unique account opening link generated by the advertiser (such as an external advertiser), such as an account opening link jointly produced by the enterprise and the advertising platform of an external advertiser, to cover potential users in batches. The corresponding user addition strategy includes instructions on how to associate the user with the corresponding advertiser and the business object mapped by the advertiser when adding them.

[0042] When the promotion slot information is empty or has an empty value indicator, it means there is no promotion slot and users can directly enter the account opening process through the platform's official website.

[0043] Specifically, different user addition strategies can be set for different promotional targets, and different promotional slots can be matched one-to-one with different user addition strategies. After obtaining user-related information, promotional slot information can be parsed from the user-related information, and then the received user-related information can be processed based on the user addition strategy corresponding to the promotional slot information to generate corresponding user data in the customer management system.

[0044] In an optional embodiment, adding the user to the customer management system based on the user addition strategy includes: creating a target link object corresponding to the promotion slot information in the customer management system; injecting dependencies into the target link object according to the user addition strategy; and adding the user to the customer management system through the target link object with injected dependencies.

[0045] Alternatively, the factory pattern can be used to create the target linked object. The factory pattern uses a common interface to point to the newly created object when creating the object, without exposing the creation logic to the client.

[0046] In this embodiment, when adding a user to the customer management system, a processing object, namely the target link object, is first generated. Dependencies are injected into the target link object, and the user is successfully added to the customer management system based on the dependencies.

[0047] The processing object is a dedicated logical unit that carries out the user's addition task. It is used to manage the entire addition process of the user and avoid information confusion or operation omissions. Different promotion slot information corresponds to different target link objects: when the promotion object type of the promotion object in the promotion slot information is the business party object type, the target link object is the business party account opening processing object; when the promotion object type of the promotion object in the promotion slot information is the advertiser object type, the target link object is the advertiser account opening processing object; when the promotion slot information is empty or has an empty value identifier, the target link object is the no-promotion processing object. Injecting dependencies into the target link object involves injecting the necessary resources, rules, and interface permissions required for the user to add tasks. Dependencies include data source dependencies, permission dependencies, rule dependencies, and operation functions.

[0048] As described above, the user addition strategy describes the operation instructions that the customer management system needs to perform for the account corresponding to the user, generated internally based on user-related information. After determining the user addition strategy, the system can obtain the dependencies that match the operation instructions and the execution order of each dependency according to the operation instructions in the user addition strategy. Then, the system can obtain the link information corresponding to the dependencies and inject it into the target link object, so that the target link object can directly call the execution dependencies according to the execution order of each dependency, based on the link information, to perform the data operation of the corresponding operation instructions.

[0049] The operation item indications include operation data indications and operation action indications. The matching data indication refers to the data source corresponding to the operation item, and the operation action indication is used to perform the operation on the data after obtaining the corresponding data source (such as user-related information), such as obtaining storage space, writing, sending notification information, etc.

[0050] Specifically, according to the execution order of dependencies, the link information corresponding to each dependency is added to the working message queue of the target link object in turn. Subsequently, the target link object can read the link information corresponding to the dependency in turn from the working message queue, so as to directly call and execute the corresponding dependency based on the link information, and perform the data operation indicated by the corresponding operation.

[0051] For each dependency, the target link object calls the corresponding execution code to perform the corresponding operation, generating a unique user identifier based on user-related information. Simultaneously, based on the account opening event information, the business entity identifier is used to retrieve the physical storage space identifier from the customer management system's database. Then, based on the physical storage space identifier, the physical storage partition corresponding to the promotion identifier is determined in the storage unit indicated by the storage space identifier in the customer management system, and user-related data is written to this storage partition. At the same time, the target link object can generate storage mapping information between the user-related information, the user-unique identifier, and the storage partition, and return the user-unique identifier to the customer service system. This allows the customer service system to read the corresponding user-related information from the customer management system based on the user's unique identifier when performing related business services.

[0052] After obtaining the operation instructions, a target link object can be generated based on the operation data instructions and operation action instructions in the operation instructions, as well as the execution order of the various operation instructions.

[0053] Different user addition strategies result in different dependencies required to complete the user addition task. Therefore, after generating the target link object, it is necessary to determine the dependencies corresponding to the current user addition strategy and then inject the dependencies into the target link object, that is, inject the corresponding dependencies according to the user addition strategy.

[0054] The user is created in the customer management system based on the target link object after dependency injection, and the user's operation log is recorded to complete the user addition task. That is, adding the user to the customer management system through the target link object after dependency injection includes: creating the user in the customer management system through the target link object after dependency injection, and recording the user's operation log.

[0055] In another optional embodiment, the method further includes: obtaining business association object information from the user-related information; determining the target business object corresponding to the user based on the business association object information and the promotion slot information; and sending the user's account opening prompt information to the target business object.

[0056] The process of determining the target business object corresponding to the user based on the business-related object information and the promotion slot information includes: when the promotion slot information indicates that the promotion object is a business entity object, obtaining the first business object corresponding to the business-related object information and determining the first business object as the target business object; when the promotion slot information indicates that the promotion object is an advertiser object, obtaining the target advertiser object corresponding to the user; determining the second business object corresponding to the target advertiser object as the target business object; when the promotion slot information is empty and the business-related object information is not empty, obtaining the third business object corresponding to the business-related object information, and not setting the target business object for the user when the third business object does not belong to the preset business object.

[0057] In this embodiment of the application, a target business object is identified for the user, and an account opening prompt message is sent to the target business object to prompt the target business object to follow up on the user's subsequent needs.

[0058] The user's information includes initial business association object information, generated by the customer service system. If the user enters the account opening process through the business party's promotional information, the business association object information is the identity information of that business party, which is recorded as the first business object. The customer management system directly identifies the first business object as the user's target business object. If the user enters the account opening process through the advertiser's promotional information, the corresponding target advertiser object is obtained. Different target advertiser objects correspond to at least one business object. The customer management system selects a contact person, i.e., the second business object, from this business object and directly identifies the second business object as the user's target business object.

[0059] When the promotion slot information is empty, meaning there is no promotion slot, the customer service system will not generate initial business association object information if the user has no specified business object. In other words, the business association object information is empty, and no target business object will be set for this customer.

[0060] When the promotion slot information is empty, meaning there is no promotion slot, the user can specify a business object, i.e., a third business object. At this time, the business association object information is not empty. It is determined whether the third business object specified by the user is a valid business object, i.e., a preset business object, such as whether it is a specifyable business object. Specifiable business objects are such as actual existing business objects or business objects belonging to the target team.

[0061] Optionally, when the promotion slot information is empty, indicating that there is no promotion slot, the customer service system can randomly assign a business object in the target team, generate initial business association object information, and directly determine the fourth business object corresponding to the business association object information as the user's target business object.

[0062] In addition, if the target business object set for a user does not exist in the customer management system (for example, the target business object is a departed employee), a business object reassignment prompt is sent to the administrator to reassign the target business object to the user.

[0063] In another optional embodiment, before adding the user to the customer management system based on the user-related information, the method further includes: determining whether the user identifier corresponding to the user has already been recorded in the customer management system; and deleting the account opening event information if the user identifier is included in the customer management system.

[0064] In this embodiment of the application, by determining whether the user identifier has been maintained in the customer management system, if the user identifier has been recorded in the customer management system, the account opening event information is deleted, and no subsequent user addition task is performed, thus automatically filtering out existing customer data and reducing data redundancy.

[0065] Please see Figure 3 , Figure 3 This application provides a flowchart illustrating the process of adding users to the customer management system. The customer management system monitors the information list, and when new account opening event information appears in the information list, it retrieves the newly added account opening event information from the information list, such as... Figure 3 As shown, Step S31: The customer management system receives account opening event information; Step S32: Determine whether the user is the target type. If yes, proceed to step S33; otherwise, proceed to step S310. Step S33: Extract user-related information based on account opening event information. The user-related information includes at least basic identity information, promotional slot information, and business-related object information. Step S34: Determine whether the user already exists in the customer management system. If not, proceed to step S35; if yes, proceed to step S310. Step S35: Determine if the promotion slot information is empty. If not, proceed to step S36; if yes, proceed to step S39. Step S36: The promotion position information indicates whether the promotion target is a business target. If yes, proceed to step S37; otherwise, proceed to step S38. Step S37: Generate a business account opening processing object, inject dependencies into the business account opening processing object, create the user in the customer management system and record the user's operation log. Step S38: Generate an advertiser account opening processing object, inject dependencies into the advertiser account opening processing object, create the user in the customer management system and record the user's operation log. Step S39: Generate a no-promotion processing object, inject dependencies into the no-promotion processing object, create the user in the customer management system and record the user's operation log. Step S310, End.

[0066] Optionally, after successfully adding the user to the customer management system, information can be sent to relevant personnel, such as target business objects, using internal corporate communication tools.

[0067] Those skilled in the art will understand that, in the above-described method of the specific implementation, the order in which each step is written does not imply a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of each step should be determined by its function and possible internal logic.

[0068] To implement the above information retrieval method, this application also proposes an information retrieval device, for details please refer to [link / reference needed]. Figure 4 , Figure 4 This is a schematic diagram of an embodiment of the information retrieval device provided in this application.

[0069] The information retrieval device 500 in this embodiment includes: The acquisition module 51 is used to acquire account opening event information sent to the information list by the customer service system, wherein the customer service system sends the account opening event information to the information list in real time after receiving the user's account opening request; The retrieval module 52 is used to retrieve user-related information of the user based on the account opening event information when the user is the target type. Add module 53 is used to add the user to the customer management system based on the user-related information.

[0070] The addition module is also used to obtain promotional information from the user-related information; determine a user addition strategy based on the promotional information; and add the user to the customer management system based on the user addition strategy.

[0071] The addition module is further configured to create a target link object corresponding to the promotion slot information in the customer management system; inject dependencies into the target link object according to the addition strategy; and add the user to the customer management system through the dependencies.

[0072] The add module is also used to create the user in the customer management system through the dependency and record the user's operation log.

[0073] The information retrieval device further includes: a sending module, used to obtain business association object information from the user-related information; determine the target business object corresponding to the user based on the business association object information and the promotion slot information; and send the user's account opening prompt information to the target business object.

[0074] The sending module is further configured to: when the promotion slot information indicates that the promotion object is a business entity object, obtain a first business object corresponding to the business-related object information and determine the first business object as the target business object; when the promotion slot information indicates that the promotion object is an advertiser object, obtain the target advertiser object corresponding to the user; determine the second business object corresponding to the target advertiser object as the target business object; when the promotion slot information is empty and the business-related object information is not empty, obtain a third business object corresponding to the business-related object information, and if the third business object does not belong to the target team or does not exist, not set the target business object for the user.

[0075] The information retrieval device further includes a judgment module, used to determine whether the user identifier corresponding to the user has been recorded in the customer management system before adding the user to the customer management system based on the user-related information; if the user identifier is included in the customer management system, the account opening event information is deleted.

[0076] To implement the above information retrieval method, this application also proposes an information retrieval device, please refer to the details below. Figure 5 , Figure 5 This is a schematic diagram of an embodiment of the information retrieval device provided in this application.

[0077] The information retrieval device 400 in this embodiment includes a processor 41, a memory 42, an input / output device 43, and a bus 44.

[0078] The processor 41, memory 42, and input / output device 43 are respectively connected to the bus 44. The memory 42 stores program data, and the processor 41 is used to execute the program data to implement the information retrieval method described in the above embodiment.

[0079] In this embodiment, processor 41 can also be referred to as a CPU (Central Processing Unit). Processor 41 may be an integrated circuit chip with signal processing capabilities. Processor 41 can also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The general-purpose processor can be a microprocessor, or processor 41 can be any conventional processor.

[0080] This application also provides a computer storage medium; please refer to the following: Figure 6 , Figure 6 This is a schematic diagram of a computer storage medium according to an embodiment of the present application. The computer storage medium 600 stores a computer program 61, which, when executed by a processor, is used to implement the information retrieval method of the above embodiment.

[0081] When the embodiments of this application are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0082] The above description is merely an embodiment of this application and does not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. An information retrieval method, characterized in that, The information retrieval method includes: Obtain account opening event information sent to the information list by the customer service system, wherein the customer service system sends the account opening event information to the information list in real time after receiving a user's account opening request; If the user is the target type, retrieve the user's relevant information based on the account opening event information; The user is added to the customer management system based on the user's relevant information.

2. The information retrieval method according to claim 1, characterized in that, Adding the user to the customer management system based on the user-related information includes: Obtain the promotional information from the user-related information; Based on the promotional slot information, a user addition strategy is determined, and the user is added to the customer management system based on the user addition strategy.

3. The information retrieval method according to claim 2, characterized in that, Adding the user to the customer management system based on the user addition strategy includes: Create the target link object corresponding to the promotion slot information in the customer management system; Inject dependencies into the target link object according to the user-added strategy; The user is added to the customer management system by injecting the target link object with the dependency.

4. The information retrieval method according to claim 3, characterized in that, Adding the user to the customer management system by injecting the dependency into the target link object includes: The user is created in the customer management system by injecting the target linked object with the dependency, and the user's operation log is recorded.

5. The information retrieval method according to claim 2, characterized in that, The method further includes: Obtain the business-related object information from the user-related information; The target business object corresponding to the user is determined based on the business association object information and the promotion slot information; Send the user's account opening prompt information to the target business object.

6. The information retrieval method according to claim 5, characterized in that, Determining the target business object corresponding to the user based on the business association object information and the promotion slot information includes: When the promotion position information indicates that the promotion target is a business object, the first business object corresponding to the business associated object information is obtained, and the first business object is determined as the target business object; When the promotion slot information indicates that the promotion target is an advertiser object, obtain the target advertiser object corresponding to the user; determine the second business object corresponding to the target advertiser object as the target business object; If the promotion slot information is empty and the business association object information is not empty, obtain the third business object corresponding to the business association object information. If the third business object does not belong to the preset business object, do not set the target business object for the user.

7. The information retrieval method according to claim 1, characterized in that, Before adding the user to the customer management system based on the user-related information, the method further includes: Determine whether the user identifier corresponding to the user has been recorded in the customer management system; If the user identifier is included in the customer management system, the account opening event information will be deleted.

8. An information retrieval device, characterized in that, The information retrieval device includes: The acquisition module is used to acquire account opening event information sent to the information list by the customer service system, wherein the customer service system sends the account opening event information to the information list in real time after receiving the user's account opening request; The retrieval module is used to retrieve user-related information of the user based on the account opening event information when the user is the target type. The add module is used to add the user to the customer management system based on the user's relevant information.

9. An information retrieval device, characterized in that, The information retrieval device includes a memory and a processor coupled to the memory; The memory is used to store program data, and the processor is used to execute the program data to implement the information retrieval method as described in any one of claims 1 to 7.

10. A computer storage medium, characterized in that, The computer storage medium is used to store program data, which, when executed by the computer, is used to implement the information retrieval method as described in any one of claims 1 to 7.

Images