CN108509322B - Method for avoiding excessive return visit, electronic device and computer readable storage medium - Google Patents
Method for avoiding excessive return visit, electronic device and computer readable storage medium Download PDFInfo
- Publication number
- CN108509322B CN108509322B CN201810042705.8A CN201810042705A CN108509322B CN 108509322 B CN108509322 B CN 108509322B CN 201810042705 A CN201810042705 A CN 201810042705A CN 108509322 B CN108509322 B CN 108509322B
- Authority
- CN
- China
- Prior art keywords
- breakpoint
- class
- event information
- information
- triggered
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3438—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment monitoring of user actions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
- G06F11/3072—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/01—Customer relationship services
Abstract
The invention discloses a method for avoiding excessive return visit, and relates to the field of repeated breakpoint filtering. A method of avoiding excessive revisit comprising: s1, setting a buried point on the APP page; s2, receiving the start event information generated after the start type embedding point is triggered by the client; s3, judging whether repeated start time information is received in a preset breakpoint identification interval, and if so, sequencing according to the sequence of trigger time; s4, judging whether a completion class breakpoint generated after an ending class embedding point corresponding to the triggered starting class embedding point is triggered is received in a preset breakpoint identification interval, and if not, executing the step S5; and S5, generating a corresponding generation type breakpoint, storing the generation type breakpoint into a distribution list, and sending the generation type breakpoint to a customer service system. The invention filters repeated start event information in the breakpoint identification interval to avoid the situation that the customer service visits the customer excessively due to repeatedly generating a plurality of same generation type breakpoint data.
Description
Technical Field
The invention relates to the field of repeated breakpoint filtering, in particular to a method for avoiding excessive return visit, an electronic device and a computer readable storage medium.
Background
With the rapid development of the internet, various applications of APP are very widely used.
Customers often encounter various problems when operating APPs. Such as: failure of registration for a plurality of times; checking for multiple failures of the policy; no payment is made for a few days after the order is submitted, and so on. This may lose a portion of the customers to the company and the benefits may be affected. Through setting the buried point, the information can be issued to the customer service, and intervention is carried out through seat return visit so as to save some customers to a certain extent.
However, when a client triggers the same starting type burying point on the APP page for multiple times, the same information is repeatedly issued, the data volume is increased by multiple times, the data processing pressure of each system is caused, repeated return visits of the agents affect the system performance, and the waste of human resources and the deterioration of the client experience are also caused by the repeated return visits of the client.
Disclosure of Invention
The technical problem to be solved by the invention is to overcome the problem that in the prior art, repeated breakpoints are generated after repeated operation of a client fails, so that excessive return visit of the client is caused, and the method, the electronic device and the computer-readable storage medium for avoiding the excessive return visit are provided, and the repeated breakpoints are filtered to prevent the excessive return visit.
The invention solves the technical problems through the following technical scheme:
a method of avoiding excessive revisit comprising the steps of:
s1, setting embedded points on the APP page, wherein the embedded points record the operation behaviors of the client on the APP page, the embedded points comprise start embedded points and end embedded points, and the start embedded points and the end embedded points are arranged on the APP page in a one-to-one correspondence manner;
s2, receiving start event information generated after the start type buried point is triggered by a client, wherein the start event information comprises a buried point name, a telephone number, a device number, trigger time and a client number;
s3, judging whether more than two pieces of start event information generated after the start type embedding points are repeatedly triggered by the same client are received in a preset breakpoint identification interval, if so, regarding the more than two pieces of start event information as the same start event information and sequencing the start event information according to the triggering time;
s4, judging whether a completion class breakpoint generated after an end class embedded point corresponding to the triggered start class embedded point is triggered is received before a preset breakpoint identification interval from the first triggering time in the same starting event information, and if not, executing the step S5;
s5, generating a corresponding generation type breakpoint, storing the generation type breakpoint in a delivered list, and sending the information of the generation type breakpoint to a customer service system, wherein the information of the generation type breakpoint comprises the triggering time of the start type embedded point triggered for the first time, and other information except the triggering time in the start event information generated after the start type embedded point is triggered for the last time, and the other information comprises an embedded point name, a telephone number, an equipment number and a customer number.
Preferably, S4 further includes: and if a completion type breakpoint generated after the triggering of the completion type embedded point corresponding to the triggered start type embedded point is detected before a preset breakpoint identification interval from the first triggering time in the same start event information, deleting all the same start event information and the completion type breakpoint and then directly finishing.
Preferably, S5 is followed by:
and S6, deleting the same start event information corresponding to the breakpoint before the generated breakpoint is sent to the customer service system.
Preferably, S6 is followed by:
and S7, judging whether a completion class breakpoint corresponding to the generation class breakpoint contained in the issued list is received, if so, generating a shielding instruction and sending the shielding instruction to the customer service system to instruct the customer service system to shield the generation class breakpoint.
Preferably, S7 is preceded by:
and S70, judging whether feedback information after the information for generating the class breakpoint sent by the customer service system is processed is received, and if so, deleting the class breakpoint from the issued list.
Preferably, S7 further includes: and after a shielding instruction is sent, deleting the generated class breakpoint corresponding to the received completion class breakpoint in the issued list.
An electronic device comprising a memory and a processor, the memory having stored thereon a system executable by the processor for avoiding over-revisit, the system for avoiding over-revisit comprising:
the embedded point recording method comprises the steps that embedded points are arranged on an APP page, the embedded points record operation behaviors of a client on the APP page, the embedded points comprise beginning embedded points and ending embedded points, and the beginning embedded points and the ending embedded points are arranged on the APP page in a one-to-one corresponding mode;
the event information receiving module is used for receiving the starting event information generated after the starting type burial point is triggered by the client, and the starting event information comprises a burial point name, a telephone number, an equipment number, triggering time and a client number;
the same event judgment module is used for judging whether more than two pieces of start event information generated after the start type buried point is repeatedly triggered by the same client is received in a preset breakpoint identification interval;
the sequencing module is used for sequencing the same start event information according to the sequence of the triggering time after whether more than two pieces of start event information generated after the start type embedding points are repeatedly triggered by the same client are received in a preset breakpoint identification interval;
a generation class breakpoint generating module, configured to determine whether a completion class breakpoint generated after an end class embedded point corresponding to a triggered start class embedded point is triggered is received before a preset breakpoint identification interval from a first trigger time in the same start event information, and if not, generate a corresponding generation class breakpoint to be stored in an issued list, where the information of the generation class breakpoint includes a trigger time when the start class embedded point is triggered for the first time, and other information, except the trigger time, in start event information generated after the start class embedded point is triggered for the last time, where the other information includes an embedded point name, a telephone number, an equipment number, and a client number;
and the breakpoint sending module is used for sending the information of the generated class breakpoints to the customer service system.
Preferably, the system for avoiding excessive revisit further comprises:
the shielding instruction generating module is used for judging whether a completion class breakpoint corresponding to a generation class breakpoint contained in the issued list is received or not, and generating a shielding instruction after receiving the completion class breakpoint, and the shielding instruction is used for indicating the customer service system to shield the information of the generation class breakpoint;
and the shielding instruction sending module is used for sending the shielding instruction to the customer service system.
Preferably, the system for avoiding excessive revisit further comprises:
and the feedback receiving and processing module is used for judging whether the feedback information sent by the customer service system and processed by the information for generating the class breakpoint is received or not, and deleting the generated class breakpoint from the issued list after the feedback information is received.
A computer-readable storage medium having stored therein a system for avoiding over-revisit, the system for avoiding over-revisit being executable by at least one processor to cause the at least one processor to perform the steps of the method for avoiding over-revisit as claimed in any one of the preceding claims.
The positive progress effects of the invention are as follows:
1) in the invention, the condition that the customer service excessively visits the customer due to the repeated generation of a plurality of same generation type breakpoint data is avoided by recognizing that the same customer triggers the starting type burying point for a plurality of times but does not trigger the ending type burying point all the time in the breakpoint recognition interval and only generating one generation type breakpoint data when the recognition interval is ended.
2) The invention continuously monitors the client behavior in the time period when the generated class breakpoint is generated and not processed, so that the generated class breakpoint in the customer service system is shielded after the problem of the client is monitored, and the condition that the client visits again after the problem of the client is solved is avoided.
Drawings
FIG. 1 is a diagram illustrating a hardware architecture of an embodiment of an electronic device according to the invention;
FIG. 2 is a schematic diagram of program modules of a first embodiment of a system for avoiding excessive revisit in an electronic device according to the present invention;
FIG. 3 is a schematic diagram of program modules of a second embodiment of a system for avoiding excessive revisit in an electronic device according to the present invention;
FIG. 4 is a schematic diagram of program modules of a third embodiment of a system for avoiding excessive revisit in an electronic device according to the present invention;
FIG. 5 is a flow chart of a first embodiment of a method of avoiding excessive revisit according to the present invention;
FIG. 6 is a flow chart of a second embodiment of the method of avoiding excessive revisit according to the present invention;
FIG. 7 is a flow chart of a third embodiment of the method of the present invention for avoiding excessive revisit;
fig. 8 shows a flowchart of a fourth embodiment of the method for avoiding excessive revisit.
Detailed Description
The invention is further illustrated by the following examples, which are not intended to limit the scope of the invention.
First, the present invention provides an electronic device.
Fig. 1 is a schematic diagram of a hardware architecture of an electronic device according to an embodiment of the invention. In the present embodiment, the electronic device 2 is a device capable of automatically performing numerical calculation and/or information processing according to a preset or stored instruction. For example, the server may be a smart phone, a tablet computer, a notebook computer, a desktop computer, a rack server, a blade server, a tower server, or a rack server (including an independent server or a server cluster composed of a plurality of servers). As shown, the electronic device 2 includes, but is not limited to, at least a memory 21, a processor 22, a network interface 23, and a system 20 that can be communicatively coupled to each other via a system bus to avoid excessive revisits. Wherein:
the memory 21 includes at least one type of computer-readable storage medium including a flash memory, a hard disk, a multimedia card, a card type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Programmable Read Only Memory (PROM), a magnetic memory, a magnetic disk, an optical disk, etc. In some embodiments, the storage 21 may be an internal storage unit of the electronic device 2, such as a hard disk or a memory of the electronic device 2. In other embodiments, the memory 21 may also be an external storage device of the electronic apparatus 2, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), or the like, provided on the electronic apparatus 2. Of course, the memory 21 may also comprise both an internal memory unit of the electronic apparatus 2 and an external memory device thereof. In this embodiment, the memory 21 is generally used for storing an operating system installed in the electronic device 2 and various types of application software, such as program codes of the system for avoiding excessive revisit 20. Further, the memory 21 may also be used to temporarily store various types of data that have been output or are to be output.
The processor 22 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data Processing chip in some embodiments. The processor 22 is generally configured to control the overall operation of the electronic apparatus 2, such as performing data interaction or communication related control and processing with the electronic apparatus 2. In this embodiment, the processor 22 is configured to run the program codes stored in the memory 21 or process data, such as running the system 20 for avoiding excessive revisit.
The network interface 23 may comprise a wireless network interface or a wired network interface, and the network interface 23 is generally used for establishing communication connection between the electronic device 2 and other electronic devices. For example, the network interface 23 is used to connect the electronic apparatus 2 to an external terminal through a network, establish a data transmission channel and a communication connection between the electronic apparatus 2 and the external terminal, and the like. The network may be a wireless or wired network such as an Intranet (Intranet), the internet (Intranet), a Global System of Mobile communication (GSM), Wideband Code Division Multiple Access (WCDMA), a 4G network, a 5G network, Bluetooth (Bluetooth), Wi-Fi, and the like.
It is noted that fig. 1 only shows the electronic device 2 with components 21-23, but it is to be understood that not all of the shown components are required to be implemented, and that more or fewer components may be implemented instead.
In this embodiment, the system 20 for avoiding over-visiting, which is stored in the memory 21, can be divided into one or more program modules, which are stored in the memory 21 and can be executed by one or more processors (in this embodiment, the processor 22) to complete the present invention.
For example, fig. 2 shows a schematic program module diagram of a first embodiment of the system 20 for avoiding excessive revisit, in which the system 20 for avoiding excessive revisit may be divided into an APP page 201, an event information receiving module 202, an identical event determining module 203, a sorting module 204, a generation-like breakpoint generating module 205, and a breakpoint transmitting module 206. The program modules referred to herein are a series of computer program instruction segments that can perform specific functions, and are better suited than programs for describing the execution of the system 20 for avoiding excessive revisit in the electronic device 2. The following description will specifically describe the specific functions of the program module 201 and 206.
Setting embedded points on the APP page 201, wherein the embedded points record operation behaviors of clients on the APP page, the embedded points include start embedded points and end embedded points, and the start embedded points and the end embedded points are arranged on the APP page in a one-to-one correspondence manner;
the buried point is actually data collection and is mainly used for event statistics, and the events are self-defined events, such as registration failure, query failure and the like. Specifically, a starting type embedding point is set on a registration failure page, and a finishing type embedding point corresponding to the starting type embedding point is set on a registration success page; or setting a starting type embedding point on the page failed in the query, and setting a finishing type embedding point corresponding to the starting type embedding point on the page successful in the query; the correspondence between the beginning type buried point and the ending type buried point is identified by the buried point name.
The embedded point is realized by adding a statistical code into the code of the APP page, and when the statistical code is executed, the embedded point is triggered and corresponding event information is generated. The event information receiving module 202 is configured to receive start event information generated after the start type burial point is triggered by a client, where the start event information includes a burial point name, a telephone number, a device number, a trigger time, and a client number;
the telephone number is the telephone number of the client and is used for subsequent customer service return visits;
the same event judgment module 203 is configured to judge whether more than two pieces of start event information generated after the start type embedding point is repeatedly triggered by the same client are received within a preset breakpoint identification interval;
the sorting module 204 sorts the same start event information according to the triggering time after determining whether more than two pieces of start event information generated after the start type embedding points are repeatedly triggered by the same client are received in a preset breakpoint identification interval;
the generation-type breakpoint generating module 205 is configured to determine whether a completion-type breakpoint generated after an end-type embedded point corresponding to the triggered start-type embedded point is triggered is received before a preset breakpoint identification interval from a first trigger time in the same start event information, and if not, generate a corresponding generation-type breakpoint to be stored in an issued list, where the information of the generation-type breakpoint includes a trigger time when the start-type embedded point is triggered for the first time, and other information, except the trigger time, in start event information generated after the start-type embedded point is triggered for the last time, where the other information includes an embedded point name, a telephone number, a device number, and a client number;
the breakpoint sending module 206 is configured to send the information of generating the class breakpoint to the customer service system.
The following description takes the failure of the client to register an account on the APP page as an example:
suppose that: when an APP page is manufactured, embedding points aiming at registration failure and registration success in advance, wherein the registration failure is a starting type embedding point, and the registration success is a corresponding ending type embedding point; the customer wants to register the account through the APP page, but fails to register for three times repeatedly in a short time, and then does not perform the operation of account registration any more.
1. The client triggers the start class embedding point once every registration failure and generates start event information, the client registers for three times, so that three repeated start event information (only trigger time is different) is recorded by the background, and the background sequences the three repeated start event information according to the trigger time.
2. The background continuously detects whether a completion class breakpoint generated after an end class embedded point corresponding to the triggered start class embedded point is triggered is received or not in a breakpoint identification interval from the time of generation of the first start event information, in this example, the client does not continue to register after three times of registration failure, so that the background does not receive the completion class breakpoint generated after the end class embedded point corresponding to the triggered start class embedded point is triggered in the breakpoint identification interval, and then a generation class breakpoint is generated after the breakpoint identification interval passes, the generation time of the generation class breakpoint is set as the time when the start class embedded point is triggered by the client for the first time, and the other information of the generation class breakpoint is information except for the triggering time in the start event information generated by triggering the client for the third time of the start class embedded point.
3. After the generation of the class breakpoint, the background automatically saves the generation breakpoint into a delivered list and sends the information of the breakpoint to a customer service system so as to be visited back by the customer service system, and meanwhile, the background deletes the recorded three repeated start event information corresponding to the generation breakpoint.
In this embodiment, repeated start event information generated in a short time is filtered to prevent a background from generating multiple repeated generation-like breakpoints and sending the multiple repeated generation-like breakpoints to a customer service system, so that the occurrence of an excessive return visit is avoided.
For another example, fig. 3 shows a schematic program module diagram of a second embodiment of the system 20 for avoiding excessive revisit, in this embodiment, the system 20 for avoiding excessive revisit may be further divided into an APP page 201, an event information receiving module 202, an identical event judging module 203, a sorting module 204, a generation class breakpoint generating module 205, a breakpoint sending module 206, a mask instruction generating module 207, and a mask instruction sending module 208.
The modules 201 and 206 are the same as those of the first embodiment, and are not described herein again.
The shielding instruction generating module 207 is configured to determine whether a completion class breakpoint corresponding to a generation class breakpoint included in the issued list is received, and generate a shielding instruction after receiving the completion class breakpoint, where the shielding instruction is used to instruct the customer service system to shield information of the generation class breakpoint;
the blocking instruction sending module 208 is configured to send the blocking instruction to the customer service system.
In the above example, since the processing (return visit) of the generated class breakpoint is delayed after the generated class breakpoint is sent to the customer service system, and the customer may solve the registration problem by himself within a period of time before the generated class breakpoint is sent to the customer service system and the breakpoint is processed, in this embodiment, after the generated class breakpoint is sent to the customer service system, the behavior of the customer is continuously monitored, and once the completion class breakpoint generated by triggering the end of class burying after the successful registration of the customer is monitored, a shielding instruction is immediately generated and sent to the customer service system, so as to avoid the return visit to the customer after the successful registration of the customer, which causes poor experience of the customer.
For another example, fig. 4 shows a schematic program module diagram of a third embodiment of the system 20 for avoiding excessive revisit, in this embodiment, the system 20 for avoiding excessive revisit may be further divided into an APP page 201, an event information receiving module 202, an identical event judging module 203, a sorting module 204, a generation class breakpoint generating module 205, a breakpoint sending module 206, a masking instruction generating module 207, a masking instruction sending module 208, and a feedback receiving processing module 209.
The modules 201 and 208 are the same as those in the second embodiment, and are not described herein again.
The feedback receiving and processing module 209 is configured to determine whether to receive feedback information sent by the customer service system after the information for generating the class breakpoint is processed, and delete the class breakpoint from the delivered list after receiving the feedback information.
In the above example, to reduce the data processing amount of the background, in this embodiment, after the generation-type breakpoint sent to the customer service system is processed, the customer service system sends feedback information to the background, and the background deletes the processed generation-type breakpoint from the delivered list according to the feedback information.
Secondly, the invention provides a method for avoiding excessive return visit.
In the first embodiment, as shown in fig. 5, the method for avoiding excessive revisit includes the following steps:
s1, a buried point is set on the APP page, the operation behavior of the client on the APP page is recorded by the buried point, the buried point comprises a beginning type buried point and an ending type buried point, and the beginning type buried point and the ending type buried point are set on the APP page in a one-to-one correspondence mode.
The webpage embedding point is actually data collection and is mainly used for event statistics, wherein the events are self-defined events, such as registration failure, query failure and the like. Specifically, a starting type embedding point is set on a registration failure page, and a finishing type embedding point corresponding to the starting type embedding point is set on a registration success page; or setting a starting type embedding point on the page failed in the query, and setting a finishing type embedding point corresponding to the starting type embedding point on the page successful in the query; the correspondence between the beginning type buried point and the ending type buried point is identified by the buried point name.
The embedded point is realized by adding a statistical code into the code of the APP page, and when the statistical code is executed, the embedded point is triggered and corresponding event information is generated.
And S2, receiving the start event information generated after the start type buried point is triggered by the client, wherein the start event information comprises a buried point name, a telephone number, a device number, trigger time and a client number.
The telephone number refers to the telephone number of the client, so that subsequent customer service can return to the client.
And S3, judging whether more than two pieces of start event information generated after the start type embedding points are repeatedly triggered by the same client are received in a preset breakpoint identification interval, and if so, regarding the more than two pieces of start event information as the same start event information and sequencing the start event information according to the triggering time.
And S4, judging whether a completion type breakpoint generated after an end type embedded point corresponding to the triggered start type embedded point is triggered is received before a preset breakpoint identification interval from the first triggering time in the same starting event information, if not, executing a step S5, and if so, directly finishing after deleting all the same starting event information and the completion type breakpoint.
The completion type breakpoint contains the following information: the system comprises a completion class breakpoint, a buried point name, a telephone number of a client, a device number, trigger time and a client number, wherein information contained in the completion class breakpoint corresponds to the start event information.
S5, generating a corresponding generation type breakpoint, storing the generation type breakpoint in a delivered list, and sending the information of the generation type breakpoint to a customer service system, wherein the information of the generation type breakpoint comprises the triggering time of the start type embedded point triggered for the first time, and other information except the triggering time in the start event information generated after the start type embedded point is triggered for the last time, and the other information comprises an embedded point name, a telephone number, an equipment number and a customer number.
The customer service system is a general term and can be an artificial customer service system, an intelligent customer service system or a customer service system possibly combining artificial intelligence.
In this embodiment, filtering is performed for continuous registration failure or query failure of the same client in a short time, which is specifically as follows:
1. the client inquires the policy information, but the inquiry fails for three times, and an inquiry failure dialog box is popped up to trigger the starting type burying point of the policy inquiry, so that three same starting event information are generated in a short time, and the background sequences the three starting event information according to the triggering time.
2. After the third query fails, the client does not perform the operation of policy query any more, so that a generation type breakpoint is generated and stored in a delivery list and sent to the customer service system, and after the generation of the generation type breakpoint, three pieces of start event information corresponding to the generation type breakpoint are deleted, the generation time of the generated generation type breakpoint is set as the time when the start type embedding point is triggered by the client for the first time, and other information is information except the trigger time in the start event information generated by the third trigger of the start type embedding point by the client.
In this embodiment, the repeated triggering of the same breakpoint is filtered when the generation of the generation-like breakpoint, so as to avoid generating a plurality of same generation-like breakpoints, and further avoid the situation that the customer service system receives a plurality of same generation-like breakpoints and generates excessive return visit.
In the second embodiment, based on the first embodiment, as shown in fig. 6, the method for avoiding excessive revisit includes the following steps:
S1-S5 are the same as those in the first embodiment and are not described herein again.
And S6, deleting the same start event information corresponding to the breakpoint before the generated breakpoint is sent to the customer service system.
In the above example, in order to release the storage space of the background, after the generation of the class breakpoint, the present embodiment deletes all three pieces of the same start event information corresponding to the breakpoint, which are sorted by the trigger time before the generation.
In the third embodiment, based on the second embodiment, as shown in fig. 7, the method for avoiding excessive revisit includes the following steps:
S1-S6 are the same as those in the second embodiment, and are not repeated here.
And S7, judging whether a completion type breakpoint corresponding to the generation type breakpoint contained in the issued list is received, if so, generating a shielding instruction and sending the shielding instruction to the customer service system to instruct the customer service system to shield the information of the generation type breakpoint, and deleting the generation type breakpoint corresponding to the received completion type breakpoint in the issued list.
In the above example, since the processing (return visit) of the generated class breakpoint is delayed after the generated class breakpoint is sent to the customer service system, and the customer may solve the registration problem by himself within a period of time before the generated class breakpoint is sent to the customer service system and the breakpoint is processed, in this embodiment, after the generated class breakpoint is sent to the customer service system, the behavior of the customer is continuously monitored, and once the completion class breakpoint generated by triggering the end of class burying after the successful registration of the customer is monitored, a shielding instruction is immediately generated and sent to the customer service system, so as to avoid the return visit to the customer after the successful registration of the customer, which causes poor experience of the customer.
Specifically, it is continuously and uninterruptedly detected whether a completion class breakpoint corresponding to a generation class breakpoint included in the issued list is received, and once detected, a shielding instruction is immediately generated and sent to the customer service system, so that the customer service system shields the generation class breakpoints and does not process the generation class breakpoints.
In the fourth embodiment, based on the third embodiment, as shown in fig. 8, the method for avoiding excessive revisit includes the following steps:
S1-S7 are the same as those in the third embodiment, and are not repeated here.
Before S7, further comprising:
and S70, judging whether feedback information after the information for generating the class breakpoint sent by the customer service system is processed is received, and if so, deleting the class breakpoint from the issued list.
In the above example, in order to avoid that the data processing amount of the background is too large, in this embodiment, the background deletes the processed class breakpoint generation points from the delivered list according to the feedback information in a manner that the customer service system sends the feedback information to the background after the information of the class breakpoint generation point sent to the customer service system is processed, so that the background does not continuously monitor the processed class breakpoint generation points.
Furthermore, the present invention relates to a computer-readable storage medium, in which the system for avoiding over-visit 20 is stored, and when the system for avoiding over-visit 20 is executed by one or more processors, the method for avoiding over-visit or the operation of the electronic device are implemented.
While specific embodiments of the invention have been described above, it will be appreciated by those skilled in the art that this is by way of example only, and that the scope of the invention is defined by the appended claims. Various changes and modifications to these embodiments may be made by those skilled in the art without departing from the spirit and scope of the invention, and these changes and modifications are within the scope of the invention.
Claims (10)
1. A method of avoiding excessive revisit comprising the steps of:
s1, setting embedded points on the APP page, wherein the embedded points record the operation behaviors of the client on the APP page, the embedded points comprise start embedded points and end embedded points, and the start embedded points and the end embedded points are arranged on the APP page in a one-to-one correspondence manner;
s2, receiving start event information generated after the start type buried point is triggered by a client, wherein the start event information comprises a buried point name, a telephone number, a device number, trigger time and a client number;
s3, judging whether more than two pieces of start event information generated after the start type embedding points are repeatedly triggered by the same client are received in a preset breakpoint identification interval, if so, regarding the more than two pieces of start event information as the same start event information and sequencing the start event information according to the triggering time;
s4, judging whether a completion class breakpoint generated after an end class embedded point corresponding to the triggered start class embedded point is triggered is received before a preset breakpoint identification interval from the first triggering time in the same starting event information, and if not, executing the step S5;
s5, generating a corresponding generation type breakpoint, storing the generation type breakpoint in a delivered list, and sending the information of the generation type breakpoint to a customer service system, wherein the information of the generation type breakpoint comprises the triggering time of the start type embedded point triggered for the first time, and other information except the triggering time in the start event information generated after the start type embedded point is triggered for the last time, and the other information comprises an embedded point name, a telephone number, an equipment number and a customer number.
2. The method of avoiding excessive revisit as recited in claim 1, wherein S4 further comprises: and if a completion type breakpoint generated after the triggering of the completion type embedded point corresponding to the triggered start type embedded point is detected before a preset breakpoint identification interval from the first triggering time in the same start event information, deleting all the same start event information and the completion type breakpoint and then directly finishing.
3. The method for avoiding excessive revisit as recited in claim 1, further comprising, after S5:
s6, deleting the information of the generated class breakpoint and sending the same start event information corresponding to the breakpoint to the customer service system.
4. The method for avoiding excessive revisit as recited in claim 3, further comprising, after S6:
and S7, judging whether a completion class breakpoint corresponding to the generation class breakpoint contained in the issued list is received, if so, generating a shielding instruction and sending the shielding instruction to the customer service system so as to instruct the customer service system to shield the information of the generation class breakpoint.
5. The method for avoiding excessive revisit as recited in claim 4, wherein S7 is preceded by:
and S70, judging whether feedback information after the information for generating the class breakpoint sent by the customer service system is processed is received, and if so, deleting the class breakpoint from the issued list.
6. The method of avoiding excessive revisit as recited in claim 4, wherein S7 further comprises: and after a shielding instruction is sent, deleting the generated class breakpoint corresponding to the received completion class breakpoint in the issued list.
7. An electronic device comprising a memory and a processor, wherein the memory has stored thereon a system for avoiding excessive revisit executable by the processor, the system for avoiding excessive revisit comprising:
the embedded point recording method comprises the steps that embedded points are arranged on an APP page, the embedded points record operation behaviors of a client on the APP page, the embedded points comprise beginning embedded points and ending embedded points, and the beginning embedded points and the ending embedded points are arranged on the APP page in a one-to-one corresponding mode;
the event information receiving module is used for receiving the starting event information generated after the starting type burial point is triggered by the client, and the starting event information comprises a burial point name, a telephone number, an equipment number, triggering time and a client number;
the same event judgment module is used for judging whether more than two pieces of start event information generated after the start type buried point is repeatedly triggered by the same client is received in a preset breakpoint identification interval;
the sequencing module is used for sequencing the same start event information according to the sequence of the triggering time after whether more than two pieces of start event information generated after the start type embedding points are repeatedly triggered by the same client are received in a preset breakpoint identification interval;
a generation class breakpoint generating module, configured to determine whether a completion class breakpoint generated after an end class embedded point corresponding to the triggered start class embedded point is triggered is received before a preset breakpoint identification interval from a first trigger time in the same start event information, and if not, generate a corresponding generation class breakpoint to be stored in an issued list, where the information of the generation class breakpoint includes a trigger time when the start class embedded point is triggered for the first time, and other information, except the trigger time, in start event information generated after the start class embedded point is triggered for the last time, where the other information includes an embedded point name, a telephone number, an equipment number, and a client number;
and the breakpoint sending module is used for sending the information of the generated class breakpoints to the customer service system.
8. The electronic device of claim 7, wherein the system for avoiding excessive revisit further comprises:
the shielding instruction generating module is used for judging whether a completion class breakpoint corresponding to a generation class breakpoint contained in the issued list is received or not, and generating a shielding instruction after receiving the completion class breakpoint, and the shielding instruction is used for indicating the customer service system to shield the information of the generation class breakpoint;
and the shielding instruction sending module is used for sending the shielding instruction to the customer service system.
9. The electronic device of claim 8, wherein the system for avoiding excessive revisit further comprises:
and the feedback receiving and processing module is used for judging whether the feedback information sent by the customer service system and processed by the information for generating the class breakpoint is received or not, and deleting the generated class breakpoint from the issued list after the feedback information is received.
10. A computer-readable storage medium having stored therein a system for avoiding excessive revisit, the system for avoiding excessive revisit being executable by at least one processor to cause the at least one processor to perform the steps of the method for avoiding excessive revisit as claimed in any one of claims 1-6.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810042705.8A CN108509322B (en) | 2018-01-16 | 2018-01-16 | Method for avoiding excessive return visit, electronic device and computer readable storage medium |
| PCT/CN2018/077369 WO2019140738A1 (en) | 2018-01-16 | 2018-02-27 | Method for avoiding excess return visits, and electronic apparatus and computer-readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810042705.8A CN108509322B (en) | 2018-01-16 | 2018-01-16 | Method for avoiding excessive return visit, electronic device and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108509322A CN108509322A (en) | 2018-09-07 |
| CN108509322B true CN108509322B (en) | 2020-05-12 |
Family
ID=63375442
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810042705.8A Active CN108509322B (en) | 2018-01-16 | 2018-01-16 | Method for avoiding excessive return visit, electronic device and computer readable storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN108509322B (en) |
| WO (1) | WO2019140738A1 (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110908879B (en) * | 2019-10-16 | 2023-10-20 | 陕西合友网络科技有限公司 | Reporting method, reporting device, reporting terminal and recording medium of buried point data |
| CN111400714B (en) * | 2020-04-16 | 2023-06-02 | Oppo广东移动通信有限公司 | Virus detection method, device, equipment and storage medium |
| CN112150118A (en) * | 2020-09-30 | 2020-12-29 | 惠州市善居电子商务有限公司 | Return visit client record monitoring method and device, computer equipment and storage medium |
| CN112579408A (en) * | 2020-10-29 | 2021-03-30 | 上海钱拓网络技术有限公司 | Classification method of embedded point information |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7917651B2 (en) * | 2006-05-26 | 2011-03-29 | International Business Machines Corporation | Apparatus, system, and method for asynchronous complex inbound transactions from SAP applications using service oriented architecture |
| CN105550184A (en) * | 2014-10-31 | 2016-05-04 | 阿里巴巴集团控股有限公司 | Information obtaining method and device |
| CN106156212A (en) * | 2015-04-22 | 2016-11-23 | 阿里巴巴集团控股有限公司 | A kind of collecting method and system and terminal thereof and server |
| CN106649120A (en) * | 2016-12-28 | 2017-05-10 | 中国银联股份有限公司 | Data acquisition method, and data analysis method and system |
| CN106777244A (en) * | 2016-12-27 | 2017-05-31 | 国网浙江象山县供电公司 | A kind of power customer electricity consumption behavior analysis method and system |
| CN107229948A (en) * | 2017-05-19 | 2017-10-03 | 四川新网银行股份有限公司 | A kind of method for reducing customer churn on line based on customer problem forecast model |
-
2018
- 2018-01-16 CN CN201810042705.8A patent/CN108509322B/en active Active
- 2018-02-27 WO PCT/CN2018/077369 patent/WO2019140738A1/en active Application Filing
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7917651B2 (en) * | 2006-05-26 | 2011-03-29 | International Business Machines Corporation | Apparatus, system, and method for asynchronous complex inbound transactions from SAP applications using service oriented architecture |
| CN105550184A (en) * | 2014-10-31 | 2016-05-04 | 阿里巴巴集团控股有限公司 | Information obtaining method and device |
| CN106156212A (en) * | 2015-04-22 | 2016-11-23 | 阿里巴巴集团控股有限公司 | A kind of collecting method and system and terminal thereof and server |
| CN106777244A (en) * | 2016-12-27 | 2017-05-31 | 国网浙江象山县供电公司 | A kind of power customer electricity consumption behavior analysis method and system |
| CN106649120A (en) * | 2016-12-28 | 2017-05-10 | 中国银联股份有限公司 | Data acquisition method, and data analysis method and system |
| CN107229948A (en) * | 2017-05-19 | 2017-10-03 | 四川新网银行股份有限公司 | A kind of method for reducing customer churn on line based on customer problem forecast model |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2019140738A1 (en) | 2019-07-25 |
| CN108509322A (en) | 2018-09-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108509322B (en) | Method for avoiding excessive return visit, electronic device and computer readable storage medium | |
| CN108804299B (en) | Application program exception handling method and device | |
| CN108510287B (en) | Client return visit judgment method, electronic device and computer readable storage medium | |
| CN106997314B (en) | Exception handling method, device and system for distributed system | |
| CN110851159B (en) | Business rule updating method and device, computer equipment and storage medium | |
| CN109450869B (en) | Service safety protection method based on user feedback | |
| CN108650123B (en) | Fault information recording method, device, equipment and storage medium | |
| CN113886590A (en) | Data summarizing method and device, computer equipment and storage medium | |
| CN111143434A (en) | Intelligent data checking method, device, equipment and storage medium | |
| CN108923967B (en) | Duplication-removing flow recording method, duplication-removing flow recording device, server and storage medium | |
| CN109284331B (en) | Certificate making information acquisition method based on service data resources, terminal equipment and medium | |
| CN108491315A (en) | The page is resident statistical method, device and the computer readable storage medium of duration | |
| CN113360210A (en) | Data reconciliation method and device, computer equipment and storage medium | |
| CN112650674A (en) | Method for remotely acquiring and debugging webpage log, computer equipment and storage medium | |
| CN110866834B (en) | Execution method and system of batch processing program | |
| CN109298928B (en) | Service processing method and device | |
| CN104539449A (en) | Handling method and related device for fault information | |
| CN111813592A (en) | Method and device for optimizing system fault recovery plan and computer storage medium | |
| CN111782431A (en) | Exception processing method, exception processing device, terminal and storage medium | |
| CN111416857A (en) | Client crash processing method, device, system, equipment and storage medium | |
| CN110708231A (en) | Data breakpoint follow-up method, electronic device and storage medium | |
| CN112818204B (en) | Service processing method, device, equipment and storage medium | |
| CN111475335B (en) | Method, system, terminal and storage medium for quickly recovering database | |
| CN112650613A (en) | Error information processing method and device, electronic equipment and storage medium | |
| CN111367750A (en) | Exception handling method, device and equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |