WO2019140738A1 - 避免过度回访的方法、电子装置及计算机可读存储介质 - Google Patents

避免过度回访的方法、电子装置及计算机可读存储介质 Download PDF

Info

Publication number
WO2019140738A1
WO2019140738A1 PCT/CN2018/077369 CN2018077369W WO2019140738A1 WO 2019140738 A1 WO2019140738 A1 WO 2019140738A1 CN 2018077369 W CN2018077369 W CN 2018077369W WO 2019140738 A1 WO2019140738 A1 WO 2019140738A1
Authority
WO
WIPO (PCT)
Prior art keywords
breakpoint
generated
information
class
triggered
Prior art date
Application number
PCT/CN2018/077369
Other languages
English (en)
French (fr)
Inventor
谢富华
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2019140738A1 publication Critical patent/WO2019140738A1/zh

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

Definitions

  • the present application relates to the field of repeated breakpoint filtering, and relates to a method, an electronic device and a computer readable storage medium for avoiding excessive return visits.
  • the purpose of the present application is to propose a method, an electronic device, and a computer readable storage medium for avoiding excessive return visits, which are used to prevent excessive return visits by filtering repeated breakpoints.
  • a method for avoiding excessive return visit includes the following steps: S1, setting a burying point on an APP page, the burying point recording an operation behavior of a client on an APP page, where the burying point includes starting a burying point and ending a burying point
  • the start class burying point and the end class burying point are set on the APP page in a one-to-one correspondence manner; S2, receiving start event information generated after the start class burying point is triggered by the client, the start event information Including a buried point name, a phone number, a device number, a trigger time, and a customer number; S3.
  • step S5 determining whether two or more generated after the start-type buried point is repeatedly triggered by the same client is received within a preset breakpoint identification interval.
  • the start event information if yes, two or more of the start event information are considered to be the same start event information and are sorted according to the trigger time; S4, determining the first one from the same start event information From the trigger time, whether there is a completion type breakpoint generated after the end type buried point corresponding to the triggered start type buried point is triggered before the preset break point recognition interval, if Then, step S5 is performed; S5, generating a corresponding generation type breakpoint is saved in the delivery list, and the information of generating the breakpoint is sent to the customer service system, and the information for generating the breakpoint includes the start class a trigger time when the buried point is triggered for the first time, and other information except the trigger time in the start event information generated after the start type of the buried point is triggered, the other information including the buried point name, the telephone number, the device number,
  • An electronic device includes a memory and a processor, wherein the memory stores a system for avoiding excessive return visits that can be executed by the processor, and the system for avoiding excessive return visit includes: an APP page, and the APP page is set to be buried.
  • the burying point records an operation behavior of the client on the APP page, where the burying point includes a starting class burying point and a ending class burying point, and the starting class burying point and the ending class burying point are in a one-to-one correspondence manner
  • the event information receiving module is configured to receive start event information generated after the start type burying point is triggered by the client, where the start event information includes a burying point name, a phone number, a device number, a trigger time, and a client.
  • the same event judging module is configured to determine whether more than two pieces of the start event information generated after the start-type embedding point is repeatedly triggered by the same client in the preset breakpoint identification interval; the sorting module, Means for receiving two or more of the start event information generated after the start type burying point is repeatedly triggered by the same client within a preset breakpoint identification interval And sorting the same start event information according to a trigger time sequence; generating a breakpoint generation module, configured to determine, at a preset breakpoint, from a first trigger time in the same start event information Whether the completion type breakpoint generated after the end type buried point corresponding to the triggered start type buried point is triggered is received before the interval, and if the corresponding generated type breakpoint is generated and saved to the delivery list,
  • the information for generating the breakpoint includes the trigger time when the start type buried point is triggered for the first time, and other information except the trigger time in the start event information generated after the start type buried point is triggered by the last time, the other information includes
  • a computer readable storage medium having stored therein a system for avoiding excessive return visits, the system for avoiding excessive return visits being executable by at least one processor to cause the at least one processor to perform the following Step: S1, setting a burying point on the APP page, the burying point records an operation behavior of the client on the APP page, where the burying point includes a starting class burying point and a ending class burying point, the starting class burying point and the The ending class burying point is set on the APP page in a one-to-one correspondence manner; S2, receiving start event information generated after the start class burying point is triggered by the client, the start event information including a burying point name, a phone number, and a device number And triggering the time and the customer number; S3, determining whether two or more of the start event information generated after the start-type buried point is repeatedly triggered by the same client is received within the preset breakpoint identification interval, and if yes, Two or more of the start event information are considered to be
  • the information about generating the breakpoint includes the first class of the buried point being triggered.
  • the positive progress of the present application is that, by identifying the same client repeatedly triggering the starting class burying point within the breakpoint identification interval, but never triggering the ending class burying point, only one generating class break is generated at the end of the identifying interval. Point data to avoid repeatedly generating multiple identical generated breakpoint data and the customer service is excessively returning to the customer.
  • FIG. 1 is a schematic diagram showing the hardware architecture of an embodiment of an electronic device of the present application.
  • FIG. 2 is a schematic diagram of a program module of a first embodiment of a system for avoiding excessive return visits in an electronic device of the present application
  • FIG. 3 is a schematic diagram of a program module of a second embodiment of a system for avoiding excessive return visits in an electronic device of the present application;
  • FIG. 4 is a schematic diagram showing a program module of a third embodiment of a system for avoiding excessive return visit in the electronic device of the present application;
  • FIG. 5 is a flowchart of Embodiment 1 of a method for avoiding excessive return visit according to the present application
  • Embodiment 6 is a flowchart of Embodiment 2 of a method for avoiding excessive return visit according to the present application;
  • FIG. 7 is a flowchart of Embodiment 3 of a method for avoiding excessive return visit according to the present application.
  • FIG. 8 is a flow chart showing a fourth embodiment of the method for avoiding excessive return visit.
  • the present application proposes an electronic device.
  • the electronic device 2 is an apparatus capable of automatically performing numerical calculation and/or information processing in accordance with an instruction set or stored in advance.
  • the electronic device 2 can be a smartphone, a tablet, a laptop, a desktop computer, a rack server, a blade server, a tower server, or a rack server (including a stand-alone server, or a server cluster composed of multiple servers).
  • the electronic device 2 includes at least, but not limited to, a system 20 that can communicate with each other via a system bus to connect the memory 21, the processor 22, the network interface 23, and avoid excessive recall. among them:
  • 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 (eg, SD or DX memory, etc.), a random access memory (RAM), Static Random Access Memory (SRAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), Programmable Read Only Memory (PROM), magnetic memory, magnetic disk, optical disk, and the like.
  • the memory 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.
  • the memory 21 may also be an external storage device of the electronic device 2, such as a plug-in hard disk equipped on the electronic device 2, a smart memory card (SMC), and a secure digital device. (Secure Digital, SD) card, flash card, etc.
  • the memory 21 can also include both the internal storage unit of the electronic device 2 and its external storage device.
  • the memory 21 is generally used to store an operating system installed on the electronic device 2 and various types of application software, such as the program code of the system 20 for avoiding excessive return visits. Further, the memory 21 can 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 typically used to control the overall operation of the electronic device 2, such as performing control and processing associated with data interaction or communication with the electronic device 2.
  • the processor 22 is configured to run program code or process data stored in the memory 21, such as running the system 20 to avoid excessive return visits.
  • the network interface 23 may comprise a wireless network interface or a wired network interface, which is typically used to establish a communication connection between the electronic device 2 and other electronic devices.
  • the network interface 23 is configured to connect the electronic device 2 to an external terminal through a network, establish a data transmission channel, a communication connection, and the like between the electronic device 2 and an external terminal.
  • the network may be an intranet, an Internet, a Global System of Mobile communication (GSM), a Wideband Code Division Multiple Access (WCDMA), a 4G network, or a 5G network.
  • Wireless or wired networks such as network, Bluetooth, Wi-Fi, etc.
  • FIG. 1 only shows the electronic device 2 with the components 21-23, but it should be understood that not all illustrated components are required to be implemented, and more or fewer components may be implemented instead.
  • the system 20 for avoiding excessive return visits stored in the memory 21 may be divided into one or more program modules, the one or more program modules being stored in the memory 21, and may be one or more A plurality of processors (this embodiment is processor 22) are executed to complete the application.
  • FIG. 2 shows a schematic diagram of a program module of the first embodiment of the system 20 for avoiding excessive return visits.
  • the system 20 for avoiding excessive return visits may be divided into an APP page 201 and an event information receiving module 202.
  • the following description will specifically describe the specific functions of the program modules 201-206.
  • a burying point is set on the APP page 201, and the burying point records an operation behavior of the client on the APP page, where the burying point includes a starting class burying point and a ending class burying point, the starting class burying point and the ending class Buried points are set on the APP page in a one-to-one correspondence;
  • the buried point is actually data collection, mainly used for event statistics.
  • the events are custom events, such as registration failure, query failure, and the like.
  • the start class burying point is set on the registration failure page, and the corresponding end class burying point is set on the registration success page; or the start class burying point is set on the query failure page, and the Query Success page is set and The corresponding end class burying point; the correspondence between the starting class burial point and the ending class burying point is identified by the burial point name.
  • the burying point is specifically implemented by adding a statistical code to the code of the APP page, and triggering the burying point and generating corresponding event information when the statistic code is executed.
  • the event information receiving module 202 is configured to receive start event information generated after the start type buried point is triggered by a client, where the start event information includes a buried point name, a phone number, a device number, a trigger time, and a customer number;
  • the phone number is a customer's phone number, and is used for subsequent customer service return visits;
  • the same event judging module 203 is configured to determine whether two or more start event information generated after the start-type embedding point is repeatedly triggered by the same client is received within a preset breakpoint identification interval;
  • the sorting module 204 after receiving two or more of the start event information generated after the start-type buried point is repeatedly triggered by the same client in the preset breakpoint identification interval, the same start event The information is sorted in order of trigger time;
  • the generating breakpoint generation module 205 is configured to determine whether, before the preset breakpoint identification interval, the received start type burying point is received from the first trigger time in the same start event information.
  • the completion class breakpoint generated after the corresponding end class is triggered, and if the corresponding generated class breakpoint is generated and saved to the delivery list, the information of the generated breakpoint includes the start class buried point for the first time.
  • the breakpoint sending module 206 is configured to send the information about generating a breakpoint to the customer service system.
  • the registration failure and the registration success are buried in advance, and the registration failure is the starting class burying point, and the registration success is the corresponding ending class burying point; the customer wants to pass the APP page. Registered account, but failed to register three times in a short period of time failed, and then no account registration operation.
  • the background continuously detects whether there is a completion class generated after the end class buried point corresponding to the triggered start type buried point is triggered in the breakpoint recognition interval.
  • Breakpoint in this example, the client does not continue to register after three registration failures, so the background does not receive the completion class break after the end class buried point corresponding to the triggered start class is triggered within the breakpoint recognition interval.
  • Point and then generate a generation breakpoint after the breakpoint recognition interval elapses, the generation time of the generated breakpoint is set to the time when the start type buried point is triggered by the client for the first time, and the other information of the breakpoint is generated.
  • the information other than the trigger time is included in the start event information generated by the third trigger of the start class.
  • the background automatically saves the generated breakpoint to the delivery list and sends the breakpoint information to the customer service system, waiting for the customer service to return, and the backstage will record the generated class.
  • the three repeated start event information corresponding to the breakpoint is deleted.
  • the repeated start event information generated in a short period of time is filtered to prevent the background generation of multiple duplicate generated breakpoints from being sent to the customer service system, thereby avoiding excessive return visits.
  • FIG. 3 shows a schematic diagram of a program module of the second embodiment of the system 20 for avoiding excessive return visits.
  • the system 20 for avoiding excessive return visits may also be divided into APP pages 201 and event information receiving.
  • the modules 201-206 are the same as the first embodiment, and are not described herein again.
  • the masking instruction generating module 207 is configured to determine whether a completion type breakpoint corresponding to the generated class breakpoint included in the delivery list is received, and generate a masking instruction after receiving, to indicate that the customer service system shields The information that generates a breakpoint;
  • the masking instruction sending module 208 is configured to send the masking instruction to the customer service system.
  • the processing of the generated breakpoint will be delayed, and before the generated breakpoint is sent to the customer service system and the breakpoint is processed.
  • the customer may solve the registration problem by himself. Therefore, in this embodiment, after the generation breakpoint is sent to the customer service system, the behavior of the customer is continuously monitored, and the trigger termination class is triggered once the client registration is successfully detected.
  • the completion type breakpoint generated by the burying point is generated, the mask command is immediately sent to the customer service system to avoid returning the customer after the customer is successfully registered, resulting in poor customer experience.
  • FIG. 4 shows a schematic diagram of a program module of the third embodiment of the system 20 for avoiding excessive return visits.
  • the system 20 for avoiding excessive return visits may also be divided into APP pages 201 and event information receiving.
  • the modules 201-208 are the same as the second embodiment, and are not described herein again.
  • the feedback receiving processing module 209 is configured to determine whether the feedback information of the generated breakpoint information sent by the customer service system is received, and the generated breakpoint is taken from the next after receiving Remove from the list.
  • the customer service system sends feedback information to the background, and the background generates the processed according to the feedback information. Class breakpoints are removed from the dispatch list.
  • the present application proposes a method of avoiding excessive return visits.
  • the method for avoiding excessive return visit includes the following steps:
  • S1 setting a burying point on the APP page, where the burying point records an operation behavior of the client on the APP page, where the burying point includes a starting class burying point and a ending class burying point, the starting class burying point and the ending class Buried points are set on the APP page in a one-to-one correspondence.
  • the burying point of the webpage is actually data collection, and is mainly used for event statistics.
  • the events are custom events, such as registration failure, query failure, and the like.
  • the start class burying point is set on the registration failure page, and the corresponding end class burying point is set on the registration success page; or the start class burying point is set on the query failure page, and the Query Success page is set and The corresponding end class burying point; the correspondence between the starting class burial point and the ending class burying point is identified by the burial point name.
  • the burying point is specifically implemented by adding a statistical code to the code of the APP page, and triggering the burying point and generating corresponding event information when the statistic code is executed.
  • S2 Receive start event information generated after the start-type buried point is triggered by a client, where the start event information includes a buried point name, a phone number, a device number, a trigger time, and a customer number.
  • the phone number refers to the customer's phone number, so that the follow-up customer service can return the customer.
  • S3. Determine whether two or more start event information generated after the start-type buried point is repeatedly triggered by the same client is received within a preset breakpoint identification interval, and if yes, two or more of the start events are started.
  • the event information is considered to be the same start event information and sorted by the trigger time.
  • step S4 Determine, after the first trigger time in the same start event information, whether the end class burying point corresponding to the triggered start type burying point is triggered before the preset breakpoint recognition interval is triggered.
  • the generated completion type breakpoint if otherwise, performs step S5, and if so, the same start event information and the completion type breakpoint are all deleted and directly ended.
  • the completion type breakpoint includes the following information: a buried point name, a customer's telephone number, a device number, a trigger time, and a customer number, and the information included in the completion type breakpoint corresponds to the start event information.
  • S5. Generate a corresponding generated class breakpoint and save the information to the delivery list, and send the information about the generated breakpoint to the customer service system, where the information about generating the breakpoint includes the first class of the buried point being triggered.
  • the customer service system mentioned here is a general reference, which can be a manual customer service system, an intelligent customer service system, or a customer service system that may be a combination of artificial intelligence.
  • the same client fails to register consecutively in a short time or fails to query, as follows:
  • the query failure dialog box pops up, triggering the start of the policy query, and then generating three identical start event information in a short period of time.
  • the start event information is sorted by the trigger time.
  • a generation class breakpoint is generated and saved to the delivery list and sent to the customer service system, and after the generated class breakpoint is generated, the deletion is performed.
  • Corresponding three start event information, and the generated generation time of a generated breakpoint is set to the time when the start type buried point is triggered by the customer for the first time, and other information is that the start type is buried by the customer. Information other than the trigger time in the start event information generated by the three triggers.
  • the repeated trigger of the same breakpoint is filtered to avoid generating multiple identical breakpoints, thereby preventing the customer service system from receiving multiple identical breakpoints. Excessive return visits.
  • the method for avoiding excessive return visit includes the following steps:
  • S1-S5 is the same as the first embodiment, and details are not described herein again.
  • the three same start event information corresponding to the breakpoints that are sorted by the trigger time are generated and deleted.
  • the method for avoiding excessive return visit includes the following steps:
  • S1-S6 is the same as the second embodiment, and details are not described herein again.
  • S7 Determine whether a completion type breakpoint corresponding to the generated breakpoint included in the delivery list is received, and if yes, generate a mask instruction and send it to the customer service system to instruct the customer service system to block the generated breakpoint. And deleting the generated class breakpoint corresponding to the received completion class breakpoint in the issued list.
  • the processing of the generated breakpoint will be delayed, and before the generated breakpoint is sent to the customer service system and the breakpoint is processed.
  • the customer may solve the registration problem by himself. Therefore, in this embodiment, after the generation breakpoint is sent to the customer service system, the behavior of the customer is continuously monitored, and the trigger termination class is triggered once the client registration is successfully detected.
  • the completion type breakpoint generated by the burying point is generated, the mask command is immediately sent to the customer service system to avoid returning the customer after the customer is successfully registered, resulting in poor customer experience.
  • the method for avoiding excessive return visit includes the following steps:
  • S1-S7 is the same as the third embodiment, and details are not described herein again.
  • S70 Determine whether the feedback information of the generated breakpoint information sent by the customer service system is processed, and if so, delete the generated breakpoint from the delivery list.
  • the customer service system sends feedback information to the background, so that the background will be based on the feedback information.
  • the processed generation class breakpoints are removed from the dispatch list so that the backends for these processed generation class breakpoints are no longer continuously monitored.
  • the present application is a computer readable storage medium having stored therein a system 20 for avoiding excessive return visits, which can be over-recognized when the system 20 avoiding excessive return visits can be executed by one or more processors The method of returning visits or the operation of the electronic device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Marketing (AREA)
  • Finance (AREA)
  • Economics (AREA)
  • Computer Vision & Pattern Recognition (AREA)
  • Development Economics (AREA)
  • Accounting & Taxation (AREA)
  • Computer Hardware Design (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Storage Device Security (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本申请公开了一种避免过度回访的方法，涉及重复断点过滤领域。一种避免过度回访的方法，包括：S1、在 APP 页面上设置埋点；S2、接收开始类埋点被客户触发后产生的开始事件信息；S3、判断在预设的断点识别间隔内是否接收到重复的开始时间信息，若是则按触发时间的先后进行排序；S4、判断在预设的断点识别间隔内是否有接收到与所触发的开始类埋点相对应的结束类埋点被触发后产生的完成类断点，若否则执行步骤 S5；S5、生成相对应的产生类断点保存至下发清单中，并将所述产生类断点发送至客服***。本申请通过在断点识别间隔内过滤重复的开始事件信息，以避免重复生成多条相同的产生类断点数据而发生客服对该客户过度回访的情况。

Description

避免过度回访的方法、电子装置及计算机可读存储介质
本申请申明享有2018年1月16日递交的申请号为201810042705.8、名称为“避免过度回访的方法、电子装置及计算机可读存储介质”的中国专利申请的优先权，该中国专利申请的整体内容以参考的方式结合在本申请中。
技术领域
本申请涉及重复断点过滤领域，涉及一种避免过度回访的方法、电子装置及计算机可读存储介质。
背景技术
随着互联网的飞速发展，各种APP的使用十分广泛。客户在操作APP时，经常会遇到各种各样的问题。比如：注册多次失败；查看保单多次失败；提交了订单几天都未进行付款等等。这样对公司来说可能丢失一部分客户，效益也可能受到影响。通过设置埋点，可以将这些信息下发至客服，通过坐席回访进行干预，以在一定程度上挽留一些客户。
但是当客户在APP页面上触发多次同一个开始类埋点，会导致同一条信息的重复下发，数据量成倍增加，导致各***数据处理压力，坐席的重复回访，影响***性能，也对客户多次回访导致人力资源浪费和客户体验变差。
发明内容
本申请的目的在于提出了一种避免过度回访的方法、电子装置及计算机可读存储介质，通过对重复断点进行过滤，以防止过度回访的情况发生。
本申请是通过下述技术方案来解决上述技术问题：
一种避免过度回访的方法，包括如下步骤：S1、在APP页面上设置埋点，所述埋点记录客户在APP页面上的操作行为，所述埋点包括开始类埋 点和结束类埋点，所述开始类埋点和所述结束类埋点以一一对应的方式设置在APP页面上；S2、接收所述开始类埋点被客户触发后产生的开始事件信息，所述开始事件信息包括埋点名称、电话号码、设备号、触发时间和客户号；S3、判断在预设的断点识别间隔内是否接收到所述开始类埋点被同一个客户重复触发后产生的两个以上的所述开始事件信息，若是则将两个以上的所述开始事件信息认为是相同的开始事件信息并按触发时间的先后进行排序；S4、判断自所述相同的开始事件信息中的首个触发时间起，在预设的断点识别间隔之前是否有接收到与所触发的开始类埋点相对应的结束类埋点被触发后产生的完成类断点，若否则执行步骤S5；S5、生成相对应的产生类断点保存至下发清单中，同时将所述产生类断点的信息发送至客服***，所述产生类断点的信息包括所述开始类埋点被首次触发的触发时间，以及所述开始类埋点被末次触发后产生的开始事件信息中除触发时间以外的其他信息，所述其他信息包括埋点名称、电话号码、设备号和客户号。
一种电子装置，包括存储器和处理器，所述存储器上存储有可被所述处理器执行的避免过度回访的***，所述避免过度回访的***包括：APP页面，所述APP页面上设置埋点，所述埋点记录客户在APP页面上的操作行为，所述埋点包括开始类埋点和结束类埋点，所述开始类埋点和所述结束类埋点以一一对应的方式设置在APP页面上；事件信息接收模块，用于接收所述开始类埋点被客户触发后产生的开始事件信息，所述开始事件信息包括埋点名称、电话号码、设备号、触发时间和客户号；相同事件判断模块，用于判断在预设的断点识别间隔内是否接收到所述开始类埋点被同一个客户重复触发后产生的两个以上的所述开始事件信息；排序模块，用于在预设的断点识别间隔内是否接收到所述开始类埋点被同一个客户重复触发后产生的两个以上的所述开始事件信息后，将所述相同的开始事件信息按触发时间的先后进行排序；产生类断点生成模块，用于判断自所述相同的开始事件信息中的首个触发时间起，在预设的断点识别间隔之前是否有接收到与所触发的开 始类埋点相对应的结束类埋点被触发后产生的完成类断点，若否则生成相对应的产生类断点保存至下发清单中，所述产生类断点的信息包括所述开始类埋点被首次触发的触发时间，以及所述开始类埋点被末次触发后产生的开始事件信息中除触发时间以外的其他信息，所述其他信息包括埋点名称、电话号码、设备号和客户号；断点发送模块，用于将所述产生类断点的信息发送至客服***。
一种计算机可读存储介质，所述计算机可读存储介质内存储有避免过度回访的***，所述避免过度回访的***可被至少一个处理器所执行，以使所述至少一个处理器执行以下步骤：S1、在APP页面上设置埋点，所述埋点记录客户在APP页面上的操作行为，所述埋点包括开始类埋点和结束类埋点，所述开始类埋点和所述结束类埋点以一一对应的方式设置在APP页面上；S2、接收所述开始类埋点被客户触发后产生的开始事件信息，所述开始事件信息包括埋点名称、电话号码、设备号、触发时间和客户号；S3、判断在预设的断点识别间隔内是否接收到所述开始类埋点被同一个客户重复触发后产生的两个以上的所述开始事件信息，若是则将两个以上的所述开始事件信息认为是相同的开始事件信息并按触发时间的先后进行排序；S4、判断自所述相同的开始事件信息中的首个触发时间起，在预设的断点识别间隔之前是否有接收到与所触发的开始类埋点相对应的结束类埋点被触发后产生的完成类断点，若否则执行步骤S5；S5、生成相对应的产生类断点保存至下发清单中，同时将所述产生类断点的信息发送至客服***，所述产生类断点的信息包括所述开始类埋点被首次触发的触发时间，以及所述开始类埋点被末次触发后产生的开始事件信息中除触发时间以外的其他信息，所述其他信息包括埋点名称、电话号码、设备号和客户号。
本申请的积极进步效果在于：通过在断点识别间隔内，识别到同一个客户多次触发了开始类埋点，但一直没触发结束类埋点，在识别间隔结束时只生成一条产生类断点数据，以避免重复生成多条相同的产生类断点数据而发 生客服对该客户过度回访的情况。
附图说明
图1示出了本申请电子装置一实施例的硬件架构示意图；
图2示出了本申请电子装置中避免过度回访的***第一实施例的程序模块示意图；
图3示出了本申请电子装置中避免过度回访的***第二实施例的程序模块示意图；
图4示出了本申请电子装置中避免过度回访的***第三实施例的程序模块示意图；
图5示出了本申请避免过度回访的方法实施例一的流程图；
图6示出了本申请避免过度回访的方法实施例二的流程图；
图7示出了本申请避免过度回访的方法实施例三的流程图；
图8示出了本申请避免过度回访的方法实施例四的流程图。
具体实施方式
下面通过实施例的方式进一步说明本申请，但并不因此将本申请限制在所述的实施例范围之中。
首先，本申请提出了一种电子装置。
参阅图1所示，是本申请电子装置一实施例的硬件架构示意图。本实施例中，所述电子装置2是一种能够按照事先设定或者存储的指令，自动进行数值计算和/或信息处理的设备。例如，可以是智能手机、平板电脑、笔记本电脑、台式计算机、机架式服务器、刀片式服务器、塔式服务器或机柜式服务器(包括独立的服务器，或者多个服务器所组成的服务器集群)等。如图所示，所述电子装置2至少包括，但不限于，可通过***总线相互通信连接存储器21、处理器22、网络接口23、以及避免过度回访的***20。其中：
所述存储器21至少包括一种类型的计算机可读存储介质，所述可读存储介质包括闪存、硬盘、多媒体卡、卡型存储器(例如，SD或DX存储器等)、随机访问存储器(RAM)、静态随机访问存储器(SRAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、可编程只读存储器(PROM)、磁性存储器、磁盘、光盘等。在一些实施例中，所述存储器21可以是所述电子装置2的内部存储单元，例如该电子装置2的硬盘或内存。在另一些实施例中，所述存储器21也可以是所述电子装置2的外部存储设备，例如该电子装置2上配备的插接式硬盘，智能存储卡(Smart Media Card,SMC)，安全数字(Secure Digital,SD)卡，闪存卡(Flash Card)等。当然，所述存储器21还可以既包括所述电子装置2的内部存储单元也包括其外部存储设备。本实施例中，所述存储器21通常用于存储安装于所述电子装置2的操作***和各类应用软件，例如所述避免过度回访的***20的程序代码等。此外，所述存储器21还可以用于暂时地存储已经输出或者将要输出的各类数据。
所述处理器22在一些实施例中可以是中央处理器(Central Processing Unit，CPU)、控制器、微控制器、微处理器、或其他数据处理芯片。该处理器22通常用于控制所述电子装置2的总体操作，例如执行与所述电子装置2进行数据交互或者通信相关的控制和处理等。本实施例中，所述处理器22用于运行所述存储器21中存储的程序代码或者处理数据，例如运行所述的避免过度回访的***20等。
所述网络接口23可包括无线网络接口或有线网络接口，该网络接口23通常用于在所述电子装置2与其他电子装置之间建立通信连接。例如，所述网络接口23用于通过网络将所述电子装置2与外部终端相连，在所述电子装置2与外部终端之间的建立数据传输通道和通信连接等。所述网络可以是企业内部网(Intranet)、互联网(Internet)、全球移动通讯***(Global System of Mobile communication，GSM)、宽带码分多址(Wideband Code Division  Multiple Access，WCDMA)、4G网络、5G网络、蓝牙(Bluetooth)、Wi-Fi等无线或有线网络。
需要指出的是，图1仅示出了具有组件21-23的电子装置2，但是应理解的是，并不要求实施所有示出的组件，可以替代的实施更多或者更少的组件。
在本实施例中，存储于存储器21中的所述避免过度回访的***20可以被分割为一个或者多个程序模块，所述一个或者多个程序模块被存储于存储器21中，并可由一个或多个处理器(本实施例为处理器22)所执行，以完成本申请。
例如，图2示出了所述避免过度回访的***20第一实施例的程序模块示意图，该实施例中，所述避免过度回访的***20可以被分割为APP页面201、事件信息接收模块202、相同事件判断模块203、排序模块204、产生类断点生成模块205和断点发送模块206。以下描述将具体介绍所述程序模块201-206的具体功能。
所述APP页面201上设置埋点，所述埋点记录客户在APP页面上的操作行为，所述埋点包括开始类埋点和结束类埋点，所述开始类埋点和所述结束类埋点以一一对应的方式设置在APP页面上；
所述埋点实际就是数据采集，主要用于事件统计，此处的事件为自定义事件，比如注册失败、查询失败等。具体地，在注册失败页面上设置开始类埋点，在注册成功页面上设置与之相对应的结束类埋点；又或者在查询失败页面上设置开始类埋点，在查询成功页面上设置与之相对应的结束类埋点；开始类埋点与结束类埋点的对应关系通过埋点名称来识别。
所述埋点具体采用在APP页面的代码中加入统计代码的方式实现，当统计代码被执行时触发所述埋点并产生的相应的事件信息。所述事件信息接收模块202用于接收所述开始类埋点被客户触发后产生的开始事件信息，所述开始事件信息包括埋点名称、电话号码、设备号、触发时间和客户号；
所述电话号码为客户的电话号码，用于后续的客服回访；
所述相同事件判断模块203用于判断在预设的断点识别间隔内是否接收到所述开始类埋点被同一个客户重复触发后产生的两个以上的所述开始事件信息；
所述排序模块204在预设的断点识别间隔内是否接收到所述开始类埋点被同一个客户重复触发后产生的两个以上的所述开始事件信息后，将所述相同的开始事件信息按触发时间的先后进行排序；
所述产生类断点生成模块205用于判断自所述相同的开始事件信息中的首个触发时间起，在预设的断点识别间隔之前是否有接收到与所触发的开始类埋点相对应的结束类埋点被触发后产生的完成类断点，若否则生成相对应的产生类断点保存至下发清单中，所述产生类断点的信息包括所述开始类埋点被首次触发的触发时间，以及所述开始类埋点被末次触发后产生的开始事件信息中除触发时间以外的其他信息，所述其他信息包括埋点名称、电话号码、设备号和客户号；
所述断点发送模块206用于将所述产生类断点的信息发送至客服***。
下面以客户在APP页面上注册账号失败为例做具体说明：
假设：在制作APP页面时，事先针对注册失败和注册成功进行埋点，所述注册失败为开始类埋点，所述注册成功则为与之相对应的结束类埋点；客户想通过APP页面注册账号，但在短时间内反复进行了三次注册均失败了，之后不再进行账号注册的操作。
1、客户每注册失败一次都会触发一次开始类埋点并产生一个开始事件信息，该客户共注册了三次，因而产生了三个重复的开始事件信息(仅触发时间不同)被后台记录下来，且后台将三个重复的开始事件信息按触发时间前后进行了排序。
2、自第一个开始事件信息产生之时起，后台在断点识别间隔内会不断检测是否有接收到与所触发的开始类埋点相对应的结束类埋点被触发后产 生的完成类断点，本例中客户三次注册失败后不再继续注册，因而后台在断点识别间隔内没有接收到与所触发的开始类埋点相对应的结束类埋点被触发后产生的完成类断点，继而在断点识别间隔经过之后生成一个产生类断点，这个产生类断点的生成时间设置为所述开始类埋点被该客户首次触发的时间，所述产生类断点的其他信息为所述开始类埋点被该客户第三次触发产生的开始事件信息中除触发时间以外的信息。
3、产生类断点生成后，后台自动将该产生类断点保存至下发清单中并将该断点的信息发送至客服***，以待客服进行回访，同时后台将记录的与该产生类断点相对应的三个重复的开始事件信息删除。
本实施例中，通过对短时间内产生的重复的开始事件信息进行过滤，以防止后台生成多个重复的产生类断点发送至客服***，以此避免过度回访的情况发生。
又例如，图3示出了所述避免过度回访的***20第二实施例的程序模块示意图，该实施例中，所述避免过度回访的***20还可以被分割为APP页面201、事件信息接收模块202、相同事件判断模块203、排序模块204、产生类断点生成模块205、断点发送模块206、屏蔽指令生成模块207和屏蔽指令发送模块208。
其中，模块201-206同第一实施例，此处不再赘述。
所述屏蔽指令生成模块207用于判断是否接收到与所述下发清单中所包含的产生类断点相对应的完成类断点，并在接收到之后生成屏蔽指令，用于指示客服***屏蔽该产生类断点的信息；
所述屏蔽指令发送模块208用于将所述屏蔽指令发送至客服***。
接上例，由于产生类断点发送至客服***后，对该产生类断点的处理(回访)会有所延时，而在产生类断点发送至客服***与该断点被处理之前的一段时间内，客户可能会自己解决该注册问题，因而本实施例中加入了在产生类断点发送至客服***后，还持续监控该客户的行为，一旦监测到该客户注 册成功后触发结束类埋点而产生的完成类断点时，立即生成屏蔽指令发送至客服***，以避免在客户注册成功后还对该客户进行回访，造成客户的体验不佳。
又例如，图4示出了所述避免过度回访的***20第三实施例的程序模块示意图，该实施例中，所述避免过度回访的***20还可以被分割为APP页面201、事件信息接收模块202、相同事件判断模块203、排序模块204、产生类断点生成模块205、断点发送模块206、屏蔽指令生成模块207、屏蔽指令发送模块208和反馈接收处理模块209。
其中，模块201-208同第二实施例，此处不再赘述。
所述反馈接收处理模块209用于判断是否接收到所述客服***发来的所述产生类断点的信息被处理后的反馈信息，并在接收到之后将该产生类断点从所述下发清单中删除。
接上例，为减轻后台的数据处理量，本实施例中，在发送至客服***的产生类断点被处理后，客服***会发送反馈信息给后台，后台根据该反馈信息将已处理的产生类断点从下发清单中删除。
其次，本申请提出一种避免过度回访的方法。
在实施例一中，如图5所示，所述的避免过度回访的方法包括如下步骤：
S1、在APP页面上设置埋点，所述埋点记录客户在APP页面上的操作行为，所述埋点包括开始类埋点和结束类埋点，所述开始类埋点和所述结束类埋点以一一对应的方式设置在APP页面上。
所述网页埋点实际就是数据采集，主要用于事件统计，此处的事件为自定义事件，比如注册失败、查询失败等。具体地，在注册失败页面上设置开始类埋点，在注册成功页面上设置与之相对应的结束类埋点；又或者在查询失败页面上设置开始类埋点，在查询成功页面上设置与之相对应的结束类埋点；开始类埋点与结束类埋点的对应关系通过埋点名称来识别。
所述埋点具体采用在APP页面的代码中加入统计代码的方式实现，当 统计代码被执行时触发所述埋点并产生的相应的事件信息。
S2、接收所述开始类埋点被客户触发后产生的开始事件信息，所述开始事件信息包括埋点名称、电话号码、设备号、触发时间和客户号。
所述电话号码是指客户的电话号码，以便后续客服对该客户进行回访。
S3、判断在预设的断点识别间隔内是否接收到所述开始类埋点被同一个客户重复触发后产生的两个以上的所述开始事件信息，若是则将两个以上的所述开始事件信息认为是相同的开始事件信息并按触发时间的先后进行排序。
S4、判断自所述相同的开始事件信息中的首个触发时间起，在预设的断点识别间隔之前是否有接收到与所触发的开始类埋点相对应的结束类埋点被触发后产生的完成类断点，若否则执行步骤S5，若是则将所述相同的开始事件信息和所述完成类断点全部删除后直接结束。
所述完成类断点中包含有如下信息：埋点名称、客户的电话号码、设备号、触发时间和客户号，所述完成类断点中包含的信息与所述开始事件信息相对应。
S5、生成相对应的产生类断点保存至下发清单中，同时将所述产生类断点的信息发送至客服***，所述产生类断点的信息包括所述开始类埋点被首次触发的触发时间，以及所述开始类埋点被末次触发后产生的开始事件信息中除触发时间以外的其他信息，所述其他信息包括埋点名称、电话号码、设备号和客户号。
这里所述客服***为泛指，可以是人工客服***、智能客服***，还有可能是人工智能相结合的客服***。
本实施例中，针对同一个客户在短时间内连续的注册失败或者查询失败进行过滤，具体如下：
1、客户查询保单信息，但是连续三次查询均失败，均弹出查询失败对话框，触发了保单查询的开始类埋点，进而在短时间内产生了三个相同的开 始事件信息，后台对这三个开始事件信息按触发时间的先后进行排序。
2、在三次查询失败后客户不再进行保单查询的操作，因而生成了一个产生类断点保存至下发清单中并发送至客服***，并在所述产生类断点生成之后，删除与之相对应的三个开始事件信息，而生成的一个产生类断点的生成时间设置为所述开始类埋点被该客户首次触发的时间，其他信息则为所述开始类埋点被该客户第三次触发产生的开始事件信息中除触发时间以外的信息。
本实施例通过产生类断点生成之时就对同一断点的重复触发进行过滤，以避免生成多个相同的产生类断点，进而避免客服***收到多个相同的产生类断点而发生过度回访的情况。
在实施例二中，基于实施例一的基础上，如图6所示，所述的避免过度回访的方法包括如下步骤：
S1-S5同实施例一，此处不再赘述。
S6、删除所述产生类断点发送至客服***之前与该断点相对应的所述相同的开始事件信息。
接上例，为了释放后台的储存空间，本实施例在产生类断点生成之后，将生成之前按触发时间排序的与该断点相对应的三个相同的开始事件信息均做删除处理。
在实施例三中，基于实施例二的基础上，如图7所示，所述的避免过度回访的方法包括如下步骤：
S1-S6同实施例二，此处不再赘述。
S7、判断是否接收到与所述下发清单中所包含的产生类断点相对应的完成类断点，若是则生成屏蔽指令并发送至客服***中，以指示客服***屏蔽该产生类断点的信息，且将所述下发清单中与接收到的所述完成类断点相对应的产生类断点删除。
接上例，由于产生类断点发送至客服***后，对该产生类断点的处理(回 访)会有所延时，而在产生类断点发送至客服***与该断点被处理之前的一段时间内，客户可能会自己解决该注册问题，因而本实施例中加入了在产生类断点发送至客服***后，还持续监控该客户的行为，一旦监测到该客户注册成功后触发结束类埋点而产生的完成类断点时，立即生成屏蔽指令发送至客服***，以避免在客户注册成功后还对该客户进行回访，造成客户的体验不佳。
具体为，持续不间断地检测是否接收到与所述下发清单中所包含的产生类断点相对应的完成类断点，一旦检测到，则立即生成屏蔽指令发送至客服***，使得客服***屏蔽这些产生类断点不进行处理。
在实施例四中，基于实施例三的基础上，如图8所示，所述的避免过度回访的方法包括如下步骤：
S1-S7同实施例三，此处不再赘述。
在S7之前还包括：
S70、判断是否接收到所述客服***发来的所述产生类断点的信息被处理后的反馈信息，若是则将该产生类断点从所述下发清单中删除。
接上例，为避免后台的数据处理量太大，本实施例通过在发送至客服***的产生类断点的信息被处理后客服***发送反馈信息给后台的方式，使得后台根据该反馈信息将已处理的产生类断点从下发清单中删除，以使后台对这些已处理产生类断点不再持续监控。
此外，本申请一种计算机可读存储介质，该计算机可读存储介质内存储有避免过度回访的***20，该避免过度回访的***20可被一个或多个处理器执行时，实现上述避免过度回访的方法或电子装置的操作。
虽然以上描述了本申请的具体实施方式，但是本领域的技术人员应当理解，这仅是举例说明，本申请的保护范围是由所附权利要求书限定的。本领域的技术人员在不背离本申请的原理和实质的前提下，可以对这些实施方式做出多种变更或修改，但这些变更和修改均落入本申请的保护范围。

Claims (15)

  1. 一种避免过度回访的方法，其特征在于，包括如下步骤：
    S1、在APP页面上设置埋点，所述埋点记录客户在APP页面上的操作行为，所述埋点包括开始类埋点和结束类埋点，所述开始类埋点和所述结束类埋点以一一对应的方式设置在APP页面上；
    S2、接收所述开始类埋点被客户触发后产生的开始事件信息，所述开始事件信息包括埋点名称、电话号码、设备号、触发时间和客户号；
    S3、判断在预设的断点识别间隔内是否接收到所述开始类埋点被同一个客户重复触发后产生的两个以上的所述开始事件信息，若是则将两个以上的所述开始事件信息认为是相同的开始事件信息并按触发时间的先后进行排序；
    S4、判断自所述相同的开始事件信息中的首个触发时间起，在预设的断点识别间隔之前是否有接收到与所触发的开始类埋点相对应的结束类埋点被触发后产生的完成类断点，若没有则执行步骤S5；
    S5、生成相对应的产生类断点保存至下发清单中，同时将所述产生类断点的信息发送至客服***，所述产生类断点的信息包括所述开始类埋点被首次触发的触发时间，以及所述开始类埋点被末次触发后产生的开始事件信息中除触发时间以外的其他信息，所述其他信息包括埋点名称、电话号码、设备号和客户号。
  2. 根据权利要求1所述的避免过度回访的方法，其特征在于，S4还包括：若自所述相同的开始事件信息中的首个触发时间起，在预设的断点识别间隔之前检测到与所触发的开始类埋点相对应的结束类埋点被触发后产生的完成类断点，则将所述相同的开始事件信息和所述完成类断点全部删除后直接结束。
  3. 根据权利要求1所述的避免过度回访的方法，其特征在于，S5之后 还包括：S6、删除所述产生类断点的信息发送至客服***之前与该断点相对应的所述相同的开始事件信息。
  4. 根据权利要求3所述的避免过度回访的方法，其特征在于，S6之后还包括：S7、判断是否接收到与所述下发清单中所包含的产生类断点相对应的完成类断点，若是则生成屏蔽指令并发送至客服***中，以指示客服***屏蔽该产生类断点的信息。
  5. 根据权利要求4所述的避免过度回访的方法，其特征在于，S7之前还包括：S70、判断是否接收到所述客服***发来的所述产生类断点的信息被处理后的反馈信息，若是则将该产生类断点从所述下发清单中删除。
  6. 根据权利要求4所述的避免过度回访的方法，其特征在于，S7还包括：发送屏蔽指令后，将所述下发清单中与接收到的所述完成类断点相对应的产生类断点删除。
  7. 一种电子装置，包括存储器和处理器，其特征在于，所述存储器上存储有可被所述处理器执行的避免过度回访的***，所述避免过度回访的***包括：
    APP页面，所述APP页面上设置埋点，所述埋点记录客户在APP页面上的操作行为，所述埋点包括开始类埋点和结束类埋点，所述开始类埋点和所述结束类埋点以一一对应的方式设置在APP页面上；
    事件信息接收模块，用于接收所述开始类埋点被客户触发后产生的开始事件信息，所述开始事件信息包括埋点名称、电话号码、设备号、触发时间和客户号；
    相同事件判断模块，用于判断在预设的断点识别间隔内是否接收到所述开始类埋点被同一个客户重复触发后产生的两个以上的所述开始事件信息；
    排序模块，用于在预设的断点识别间隔内是否接收到所述开始类埋点被同一个客户重复触发后产生的两个以上的所述开始事件信息后，将所述相同的开始事件信息按触发时间的先后进行排序；
    产生类断点生成模块，用于判断自所述相同的开始事件信息中的首个触发时间起算经过预设的断点识别间隔之前是否有接收到与所触发的开始类埋点相对应的结束类埋点被触发后产生的完成类断点，若是则生成相对应的产生类断点保存至下发清单中，所述产生类断点的信息包括所述开始类埋点被首次触发的触发时间，以及所述开始类埋点被末次触发后产生的开始事件信息中除触发时间以外的其他信息，所述其他信息包括埋点名称、电话号码、设备号和客户号；
    断点发送模块，用于将所述产生类断点的信息发送至客服***。
  8. 根据权利要求7所述的电子装置，其特征在于，所述避免过度回访的***还包括：
    屏蔽指令生成模块，用于判断是否接收到与所述下发清单中所包含的产生类断点相对应的完成类断点，并在接收到之后生成屏蔽指令，用于指示客服***屏蔽该产生类断点的信息；
    屏蔽指令发送模块，用于将所述屏蔽指令发送至客服***。
  9. 根据权利要求8所述的电子装置，其特征在于，所述避免过度回访的***还包括：反馈接收处理模块，用于判断是否接收到所述客服***发来的所述产生类断点的信息被处理后的反馈信息，并在接收到之后将该产生类断点从所述下发清单中删除。
  10. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质内存储有避免过度回访的***，所述避免过度回访的***可被至少一个处理器所执行，以使所述至少一个处理器执行以下步骤：
    S1、在APP页面上设置埋点，所述埋点记录客户在APP页面上的操作行为，所述埋点包括开始类埋点和结束类埋点，所述开始类埋点和所述结束类埋点以一一对应的方式设置在APP页面上；
    S2、接收所述开始类埋点被客户触发后产生的开始事件信息，所述开始事件信息包括埋点名称、电话号码、设备号、触发时间和客户号；
    S3、判断在预设的断点识别间隔内是否接收到所述开始类埋点被同一个客户重复触发后产生的两个以上的所述开始事件信息，若是则将两个以上的所述开始事件信息认为是相同的开始事件信息并按触发时间的先后进行排序；
    S4、判断自所述相同的开始事件信息中的首个触发时间起，在预设的断点识别间隔之前是否有接收到与所触发的开始类埋点相对应的结束类埋点被触发后产生的完成类断点，若没有则执行步骤S5；
    S5、生成相对应的产生类断点保存至下发清单中，同时将所述产生类断点的信息发送至客服***，所述产生类断点的信息包括所述开始类埋点被首次触发的触发时间，以及所述开始类埋点被末次触发后产生的开始事件信息中除触发时间以外的其他信息，所述其他信息包括埋点名称、电话号码、设备号和客户号。
  11. 根据权利要求10所述的计算机可读存储介质，其特征在于，S4还包括：若自所述相同的开始事件信息中的首个触发时间起，在预设的断点识别间隔之前检测到与所触发的开始类埋点相对应的结束类埋点被触发后产生的完成类断点，则将所述相同的开始事件信息和所述完成类断点全部删除后直接结束。
  12. 根据权利要求10所述的计算机可读存储介质，其特征在于，S5之后还包括：S6、删除所述产生类断点的信息发送至客服***之前与该断点相对应的所述相同的开始事件信息。
  13. 根据权利要求12所述的计算机可读存储介质，其特征在于，S6之后还包括：S7、判断是否接收到与所述下发清单中所包含的产生类断点相对应的完成类断点，若是则生成屏蔽指令并发送至客服***中，以指示客服***屏蔽该产生类断点的信息。
  14. 根据权利要求12所述的计算机可读存储介质，其特征在于，S7之前还包括：S70、判断是否接收到所述客服***发来的所述产生类断点的信 息被处理后的反馈信息，若是则将该产生类断点从所述下发清单中删除。
  15. 根据权利要求12所述的计算机可读存储介质，其特征在于，S7还包括：发送屏蔽指令后，将所述下发清单中与接收到的所述完成类断点相对应的产生类断点删除。
PCT/CN2018/077369 2018-01-16 2018-02-27 避免过度回访的方法、电子装置及计算机可读存储介质 WO2019140738A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810042705.8A CN108509322B (zh) 2018-01-16 2018-01-16 避免过度回访的方法、电子装置及计算机可读存储介质
CN201810042705.8 2018-01-16

Publications (1)

Publication Number Publication Date
WO2019140738A1 true WO2019140738A1 (zh) 2019-07-25

Family

ID=63375442

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/077369 WO2019140738A1 (zh) 2018-01-16 2018-02-27 避免过度回访的方法、电子装置及计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN108509322B (zh)
WO (1) WO2019140738A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110908879A (zh) * 2019-10-16 2020-03-24 平安普惠企业管理有限公司 埋点数据的上报方法、装置、终端和存储介质

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111400714B (zh) * 2020-04-16 2023-06-02 Oppo广东移动通信有限公司 病毒检测方法、装置、设备及存储介质
CN112150118A (zh) * 2020-09-30 2020-12-29 惠州市善居电子商务有限公司 回访客户记录监测方法、装置、计算机设备和存储介质
CN112579408A (zh) * 2020-10-29 2021-03-30 上海钱拓网络技术有限公司 一种埋点信息的分类方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070288934A1 (en) * 2006-05-26 2007-12-13 International Business Machines Corporation Apparatus, system, and method for asynchronous complex inbound transactions from sap applications using service oriented architecture
CN105550184A (zh) * 2014-10-31 2016-05-04 阿里巴巴集团控股有限公司 一种信息获取方法及装置
CN106156212A (zh) * 2015-04-22 2016-11-23 阿里巴巴集团控股有限公司 一种数据采集方法和***、及其终端和服务器
CN107229948A (zh) * 2017-05-19 2017-10-03 四川新网银行股份有限公司 一种基于用户问题预测模型的减小线上客户流失的方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106777244A (zh) * 2016-12-27 2017-05-31 国网浙江象山县供电公司 一种电力客户用电行为分析方法及***
CN106649120A (zh) * 2016-12-28 2017-05-10 ***股份有限公司 一种数据获取方法、分析方法及***

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070288934A1 (en) * 2006-05-26 2007-12-13 International Business Machines Corporation Apparatus, system, and method for asynchronous complex inbound transactions from sap applications using service oriented architecture
CN105550184A (zh) * 2014-10-31 2016-05-04 阿里巴巴集团控股有限公司 一种信息获取方法及装置
CN106156212A (zh) * 2015-04-22 2016-11-23 阿里巴巴集团控股有限公司 一种数据采集方法和***、及其终端和服务器
CN107229948A (zh) * 2017-05-19 2017-10-03 四川新网银行股份有限公司 一种基于用户问题预测模型的减小线上客户流失的方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110908879A (zh) * 2019-10-16 2020-03-24 平安普惠企业管理有限公司 埋点数据的上报方法、装置、终端和存储介质
CN110908879B (zh) * 2019-10-16 2023-10-20 陕西合友网络科技有限公司 埋点数据的上报方法、装置、终端和存储介质

Also Published As

Publication number Publication date
CN108509322A (zh) 2018-09-07
CN108509322B (zh) 2020-05-12

Similar Documents

Publication Publication Date Title
CN109857737B (zh) 一种冷热数据存储方法及装置、电子设备
WO2019140738A1 (zh) 避免过度回访的方法、电子装置及计算机可读存储介质
US10817386B2 (en) Virtual machine recovery method and virtual machine management device
US10838838B2 (en) Method and apparatus for dealing with abnormality of application program and storage medium
CN107451040B (zh) 故障原因的定位方法、装置及计算机可读存储介质
US7925856B1 (en) Method and apparatus for maintaining an amount of reserve space using virtual placeholders
WO2019140739A1 (zh) 客户回访的判断方法、电子装置及计算机可读存储介质
US11169901B2 (en) Storage-based log file management
WO2020042503A1 (zh) 风控***的验证方法、装置、设备及存储介质
CN112035472A (zh) 数据处理方法、装置、计算机设备和存储介质
CN111901176B (zh) 故障确定方法、装置、设备及存储介质
CN110650164A (zh) 文件的上传方法、装置、终端以及计算机存储介质
CN112217684A (zh) Api网关监控方法、装置及***
CN112256551A (zh) 一种远程日志抓取方法、装置、电子设备和存储介质
CN110647463B (zh) 一种恢复测试断点的方法、装置、电子设备
CN108923967B (zh) 一种去重流量记录方法、装置、服务器及存储介质
CN110851300A (zh) 程序进程监控的方法、装置、计算机设备及可读存储介质
CN111813592A (zh) ***故障恢复预案的优化方法、装置及计算机存储介质
CN113238815A (zh) 一种接口访问控制方法、装置、设备及存储介质
CN112650674A (zh) 远程获取、调试网页日志的方法、计算机设备及存储介质
CN109298928B (zh) 业务的处理方法及装置
WO2020177495A1 (zh) 一种数据库连接管理方法及装置、设备
CN112559445B (zh) 数据写入方法及装置
CN114490196A (zh) 数据库切换方法、***、设备及介质
CN110737649B (zh) 一种数据库的事务日志的处理方法、设备以及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18901044

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 17.12.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18901044

Country of ref document: EP

Kind code of ref document: A1