A method, device, client and equipment for client application information feedback

Abstract

This article provides a method, device, client and equipment for client application information feedback. The method includes: determining the business type of user feedback according to user operation instructions; receiving user feedback information for the business type, and packaging the feedback information and the business type into a feedback file; sending the feedback file to a background server corresponding to the business type so that background personnel can process the feedback file. This article simplifies the customer problem feedback channel, improves the customer's processing efficiency of customer feedback information, and thus improves the customer's user experience.

Description

Technical Field

[0001] This article belongs to the field of automatic programming, and specifically relates to a client application information feedback method, device, client and equipment. Background Art

[0002] With the rapid development of Internet finance, banks are paying more and more attention to integrated and open business processing platforms, among which mobile banking is an important target for retail business. In order to improve customer loyalty and business experience, commercial banks actively apply more flexible and innovative business processing processes, continuously optimize the functions of mobile banking APPs, and emphasize online awareness to provide better and more comprehensive services to customers.

[0003] At present, when the application is launched, in order to promptly and properly handle the problems reported by customers, customers can report problems through business outlets, customer service telephones, portal websites, online banking, SMS banking, WeChat banking, etc. Simple problems can be directly processed successfully and fed back to customers, but for most personalized problems, such as problems found by customers when using mobile banking clients to handle business, after calling the customer service telephone, the customer service failed to give a clear explanation, or the explanation failed to satisfy the customer, and further contact with the technology department to analyze and find the cause. In this case, it is necessary to communicate with the customer many times, report the communication results to the complaint management department and relevant functional departments, and then the final feedback information will be manually assigned to the relevant technology department according to the business function type, and after analysis and processing, it will be fed back to the customer. It can be seen that for most of the problems reported by customers, they must go through manual links such as reporting and designation, and the steps are cumbersome. Customer feedback cannot be obtained in time, which affects customer use and reduces customer experience.

[0004] Therefore, how to improve the processing efficiency of user feedback information has become a technical problem that urgently needs to be solved. Summary of the invention

[0005] In view of the above problems in the prior art, the purpose of this article is to provide a method, apparatus, client and device for client application information feedback, which can improve the efficiency of processing user feedback information.

[0006] In order to solve the above technical problems, the specific technical solutions of this article are as follows:

[0007] On the one hand, this document provides a method for client application information feedback, the method comprising:

[0008] Determine the business type of user feedback based on user operation instructions;

[0009] receiving feedback information from a user regarding the service type, and packaging the feedback information and the service type into a feedback file;

[0010] The feedback file is sent to a backend server corresponding to the business type, so that backend personnel can process the feedback file.

[0011] Further, determining the service type of the user feedback according to the user operation instruction includes:

[0012] Obtain the user's operation instructions based on the tag library and determine the business type tag;

[0013] The service type reported by the user is determined according to the service type label.

[0014] Furthermore, the process of establishing the tag library includes:

[0015] Determine the client application system and the database corresponding to the application system;

[0016] According to the database, obtaining the business categories in the application system and the business types included in the business categories;

[0017] Establishing a first mapping relationship between the service type and a preset service type label, and establishing a second mapping relationship between the service type and a preset service type label;

[0018] Determining a relationship between the preset service category label and the preset service type label according to the relationship between the service category and the service type, the first mapping relationship, and the second mapping relationship;

[0019] A tag library is established according to the relationship between the preset service category tag and the preset service type tag.

[0020] Optionally, obtaining, according to the database, the business categories in the application system and the business types included in the business categories includes:

[0021] According to the database, obtaining the business types in the application system and the log information corresponding to each business type;

[0022] At least one service type corresponding to the service type in the application system is determined according to the service type and the log information.

[0023] Optionally, the preset service type tag acquisition process includes:

[0024] Get the index information table of the application system when the system runs a batch;

[0025] When the system runs a batch, frequency statistics are performed on the index information table;

[0026] Add business words with a frequency exceeding a preset value to a candidate business type label queue;

[0027] The candidate service type label queue is screened according to preset rules to determine a preset service type label.

[0028] Optionally, the preset service type tag acquisition process further includes:

[0029] Obtain the business vocabulary added by the backend personnel, and add the business vocabulary to the candidate business type label queue;

[0030] The candidate service type label queue is screened according to preset rules to determine a preset service type label.

[0031] Furthermore, screening the candidate service type label queue according to a preset rule to determine a preset service type label includes:

[0032] The business terms in the candidate business type label queue are processed in the following order:

[0033] Determine the business type corresponding to the business vocabulary and the business category to which the business type belongs;

[0034] According to the business category, obtaining a business type tag set related to the business category;

[0035] Calculating semantic similarity between the business vocabulary and each business type label in the business type label set, and obtaining all similarity values;

[0036] Determine whether all the similarity values ​​are greater than a preset threshold value;

[0037] If all the similarity values ​​are not greater than the preset threshold value, the business vocabulary is determined as a preset business type label.

[0038] Optionally, the feedback information includes user identification information and user operation information.

[0039] On the other hand, this document also provides a client application information feedback device, the device comprising:

[0040] A service type determination module is used to determine the service type reported by the user according to the user's operation instruction;

[0041] A feedback file forming module, used for receiving feedback information from users regarding the service type, and packaging the feedback information and the service type into a feedback file;

[0042] The feedback information processing module is used to send the feedback file to a background server corresponding to the business type, so that the background personnel can process the feedback file.

[0043] On the other hand, this document also provides a client, which runs an application and is configured with the method described above.

[0044] On the other hand, this document also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method described above when executing the computer program.

[0045] Finally, the present invention also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method described above is implemented.

[0046] By adopting the above technical scheme, a client application information feedback method, device, client and equipment described in this article, when a user needs to feedback information when using an application, determines the business type that the user needs to feedback, and packages the received user feedback information and business type into a feedback file, and finally sends the feedback file to the background server corresponding to the business type, so that the background personnel can process the feedback file. This article can promptly receive and feedback the user's feedback information to the background personnel. Compared with the existing technology that requires manual link flow and other steps, this article simplifies the customer problem feedback channel, improves the customer's processing efficiency of customer feedback information, and thus improves the customer's user experience.

[0047] In order to make the above and other purposes, features and advantages of this article more obvious and easy to understand, the following specifically cites preferred embodiments and describes them in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] In order to more clearly illustrate the technical solutions in the embodiments of this article or the prior art, the drawings required for use in the embodiments or the prior art descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments of this article. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0049] Figure 1 A schematic diagram of an implementation environment of the method provided in the embodiments of this article is shown;

[0050] Figure 2 A schematic diagram of the steps of the client application information feedback method provided in the embodiment of this article is shown;

[0051] Figure 3 A schematic diagram of the steps for determining the service type in the embodiment of this document is shown;

[0052] Figure 4 A schematic diagram of the steps for establishing a tag library in the embodiment of this article is shown;

[0053] Figure 5 A schematic diagram of the steps of recommending labels by the system in the embodiment of this article is shown;

[0054] Figure 6 A schematic diagram of the steps of manually entering labels in the embodiment of this article is shown;

[0055] Figure 7 A schematic diagram of the steps for determining a preset service type label in the embodiment of this document is shown;

[0056] Figure 8 A schematic diagram showing changes in the client interface of an embodiment of this invention is shown;

[0057] Fig. 9 A schematic diagram showing the structure of a client application information feedback device provided in an embodiment of this invention is shown;

[0058] Fig.10 A schematic diagram of the structure of a computer device provided in an embodiment of this invention is shown.

[0059] Description of the accompanying symbols:

[0060] 10. User;

[0061] 20. Client;

[0062] 30. Backend server;

[0063] 40. Backstage staff;

[0064] 100. Business type determination module;

[0065] 200. Feedback file forming module;

[0066] 300. Feedback information processing module;

[0067] 1002. Computer equipment;

[0068] 1004. Processor;

[0069] 1006. Memory;

[0070] 1008. Driving mechanism;

[0071] 1010, input / output module;

[0072] 1012. Input device;

[0073] 1014. Output device;

[0074] 1016. Presentation equipment;

[0075] 1018. Graphical user interface;

[0076] 1020. Network interface;

[0077] 1022. Communication link;

[0078] 1024. Communication bus. DETAILED DESCRIPTION

[0079] The following will be combined with the drawings in the embodiments of this article to clearly and completely describe the technical solutions in the embodiments of this article. Obviously, the described embodiments are only part of the embodiments of this article, not all of the embodiments. Based on the embodiments of this article, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this article.

[0080] It should be noted that the terms "first", "second", etc. in the specification and claims of this article and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of this article described here can be implemented in an order other than those illustrated or described here. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, device, product or equipment that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0081] In the prior art, problem feedback for applications generally requires multiple manual steps to collect and classify feedback information, and finally the specific problems that need to be solved can be fed back to the relevant technology department for processing. The above process steps are cumbersome and fail to obtain customer problem feedback in a timely manner, which affects the customer's user experience and thus reduces the competitiveness of the application.

[0082] In order to solve the above problems, the embodiment of this specification provides a method for client application information feedback, such as Figure 1As shown, it is a schematic diagram of the implementation environment of the method. A user 10 uses an application on a client 20, wherein the client 20 may be a mobile terminal, and the application runs on the mobile terminal. When some functions of the application have problems and cannot be used normally, the client 10 needs to feedback the relevant problems to the developer of the application. Therefore, the operation can be performed on the client 20, which can be implemented specifically through the display interface of the mobile terminal. The business type that needs feedback is selected in the problem feedback function on the interactive interface of the application, and then the feedback information that needs feedback is input, such as text information, screenshot information, etc. The client processor packages the feedback information and the business type into a feedback file, and sends the feedback file to the background server 30 corresponding to the business type, so that the background personnel 40 can process the feedback file. This article can facilitate customers to feedback problems, thereby improving the competitiveness of the application and reducing the risk of business production.

[0083] Specifically, the embodiments of this document provide a method for client application information feedback, which can improve the efficiency of application information feedback. Figure 2 This is a schematic diagram of the steps of a client application information feedback method provided in the embodiments of this article. This specification provides the method operation steps described in the embodiments or flowcharts, but may include more or fewer operation steps based on conventional or non-creative labor. The order of steps listed in the embodiments is only one way of executing the steps among many orders, and does not represent the only order of execution. When the actual system or device product is executed, it can be executed in the order of the methods shown in the embodiments or drawings or in parallel. Specifically, Figure 2 As shown, the method may include:

[0084] S101: Determine the service type reported by the user according to the user operation instruction;

[0085] S102: receiving feedback information from a user regarding the service type, and packaging the feedback information and the service type into a feedback file;

[0086] S103: Send the feedback file to a backend server corresponding to the business type, so that backend personnel can process the feedback file.

[0087] In the embodiment of the present specification, when a user needs to feedback a problem while using an application, the business type that needs feedback is determined, and feedback information from the user regarding the business type is received. Based on the feedback information and business type, the feedback file is packaged into a feedback file, and the feedback file is sent to a background server corresponding to the business type so that background personnel can process the feedback file. In the embodiment of the present specification, labels for different business types of user feedback are set on the application running on the client. For example, the application has a user interaction interface, and a problem feedback button is set in the interaction interface. The user can enter the problem feedback page by clicking the feedback button. The user operates through the label options in the problem feedback page, so that the application determines the business type of the user feedback. Therefore, this article can facilitate users to actively select the business type for feedback, and then actively input feedback information, so that the feedback information can be directly sent to the background server that can be directly processed by background personnel, which greatly simplifies the way of customer problem feedback, and also facilitates users to quickly feedback, reduces unnecessary manual links, and improves user experience.

[0088] The business type may be a business function for a specified application, that is, each business type corresponds to a function. When a fault occurs during the use of the application, it is actually because the business function cannot operate normally. Therefore, by determining the business type, it is convenient for backend personnel, such as operation and maintenance personnel, to quickly locate the fault and then quickly maintain the business function, thereby reducing the risk of business commissioning.

[0089] The feedback information may be a specific problem that the user needs to report. In order to improve the pertinence and efficiency of fault handling, the feedback information may be user identification information and user operation information.

[0090] The user identification information may be information such as a user account, user number, mobile phone number, operation time, etc., which is used to identify the customer's identity. The user identification information may be automatically obtained through the application background. For example, the user mobile phone number may be the mobile phone number used by the user to register the application, the user account may be an account for conducting financial services, and the user number may be the user's number in different financial entities (financial institutions, such as banks, etc.). Therefore, the user identification information is unique and can accurately locate the user, thereby achieving targeted processing of user feedback issues and improving user experience.

[0091] The user operation information may be specific issues that the user needs to feedback, such as text information, error screenshot information, etc. The text information may be input on the feedback interface to ensure that the fault information can be described objectively and completely. The error screenshot information needs to be uploaded by the customer, which can facilitate the backend personnel to quickly locate the fault location and realize rapid and timely handling of the fault.

[0092] This article provides timely feedback of user identification information and user operation information, which facilitates the collection and location of problems in the first place, improves the efficiency of solving customer problems, reduces the risk of business commissioning, and improves the market competitiveness of application business.

[0093] In the embodiments of this specification, since different functions in the application program correspond to different business types, as a comprehensive service program (such as mobile banking, etc.), in order to meet the needs of more users, the application program must have many functions. Figure 3 As shown, in order to facilitate the user to quickly determine the service type to which the fault belongs, the service type reported by the user is determined according to the user operation instruction, including:

[0094] S201: Obtaining the user's operation instruction based on the tag library and determining the business type tag;

[0095] S202: Determine the service type reported by the user according to the service type label.

[0096] It can be understood that the tag library is a collection of corresponding tags for all business types in the application, so that users can determine the corresponding function running in the background by selecting a tag. Starting from the businessization of data, this article uses tag technology to realize the businessization of application functions (such as mobile banking). Each function corresponds to a tag, which makes it convenient for customers to feedback specific problems according to the corresponding tags of business functions, realize unified and standardized management, and improve user experience.

[0097] In actual work, the tag library can be an independent functional module of the application, and can realize the collection and transmission of user feedback information, so as to quickly feedback the user feedback information, further improve the speed of back-end personnel receiving feedback information, and improve processing efficiency. For example, the tag library can be constructed as a function button of the application in the client page. When the user clicks the function button, the tag selection page pops up. Each business type tag corresponds to a business type, and the user can quickly determine the business type tag according to the business type that needs feedback, that is, the business type tag can be quickly identified by the user. After the user selects the business type tag, the page will enter the feedback page, and the user will input the feedback information, so as to quickly and directly feedback the fault information, which improves the convenience of information feedback.

[0098] In the embodiments of this specification, Figure 4 As shown, the process of establishing the tag library includes:

[0099] S301: Determine a client application system and a database corresponding to the application system;

[0100] S302: Acquire, according to the database, the business categories in the application system and the business types included in the business categories;

[0101] S303: Establishing a first mapping relationship between the service type and a preset service type label, and establishing a second mapping relationship between the service type and a preset service type label;

[0102] S304: Determine a relationship between the preset service category label and the preset service type label according to the relationship between the service category and the service type, the first mapping relationship, and the second mapping relationship;

[0103] S305: Establish a tag library according to the relationship between the preset service category tag and the preset service type tag.

[0104] It can be understood that this article starts from the database corresponding to each application system (application), analyzes the different functions of the application system, that is, the business category and the business type, and processes the mapping relationship between the business category and the business type through preset tags, so that it is convenient for users to quickly determine the corresponding functions through corresponding tags (such as business category tags and business type tags), wherein the preset tags can represent the characteristics of the corresponding business objects, which is convenient for users to identify. For example, the business category can be credit card repayment, and the business types included in the business category can be immediate repayment, automatic repayment, installment payment, local currency payment, foreign currency repayment, etc. Accordingly, the business category tag can be set to credit card repayment, and the business type tags included under the business category tag can be immediate repayment, automatic repayment, installment payment, local currency payment, foreign currency repayment, etc.

[0105] Among them, the first mapping relationship can be the correspondence between the business type and the business type label, that is, through the business type label, the backend personnel can quickly locate the business type, thereby narrowing the scope of business type processing. The second mapping relationship can be the correspondence between the business type and the business type label, that is, through the business type label, combined with the above-determined business type, the target business type can be quickly located, such as the location of its running code, the code storage location, etc., so that the problem fault can be handled and adjusted in time.

[0106] Furthermore, the feedback information and the business type are packaged into a feedback file, which is convenient for back-end personnel to quickly locate the fault location according to the business type, and then perform timely and targeted processing based on the customer's feedback information. The business type in the feedback file can be understood as a business type label, which can improve the efficiency of file packaging and reduce the size of the feedback file, thereby improving the efficiency of file transmission. Back-end personnel can also quickly locate the corresponding business type through the business type label, ensuring the speed of fault processing.

[0107] For an application, to meet the needs of more users, it is necessary to fully explore the application's usage scenarios and functions. Therefore, in the case where the application has many functions, in order to quickly determine different business categories and business types, the business categories in the application system and the business types included in the business categories are obtained according to the database, including:

[0108] According to the database, obtaining the business types in the application system and the log information corresponding to each business type;

[0109] At least one service type corresponding to the service type in the application system is determined according to the service type and the log information.

[0110] It can be understood that the business type can be determined based on the configuration file set in advance in the application system, such as the directory file information configured in advance, so that the corresponding business type can be determined, and the business type can be determined through log information. Specifically, the different functions appearing in the business type can be extracted today to determine the corresponding business type. In actual applications, different business types can be targeted at different business types. When classifying and refining the business, the configuration files corresponding to the different functions extracted by classification are dynamically processed to form a state that can be directly processed, so that the corresponding function configuration file can be quickly located. Further, by setting data tags (such as business category tags and business type tags), the data tags are associated with the above-mentioned corresponding function configuration files that can be processed (such as establishing a mapping relationship), and the business type that needs feedback can be directly located through the data tags. Therefore, this process greatly reduces the participation of intermediate manual links, simplifies the feedback path, and improves the efficiency of fault location and processing.

[0111] In some other embodiments, the business category and the business type can also be obtained through other means, such as through the function configuration directory in the configuration file, which can improve the speed of determining the business function. When performing subsequent fault processing and locating, it is also necessary to query through the directory, which can avoid dynamic processing of configuration files of different functional objects, reduce the difficulty of business function determination and subsequent fault locating, and thus save the cost of putting the business project into production.

[0112] In actual work, the determination of the data label, especially the business type label, is particularly important, which can ensure that the business type represented by the business type label can be quickly identified by the user and avoid conflicts with other labels. Figure 5 As shown, the preset business type tag acquisition process includes:

[0113] S401: Obtaining the index information table of the application system when the system runs a batch;

[0114] S402: When the system runs a batch, performing word frequency statistics on the index information table;

[0115] S403: adding the business words with a frequency exceeding a preset value into a candidate business type label queue;

[0116] S404: Screening the candidate service type label queue according to preset rules to determine a preset service type label.

[0117] The index information table can be index words for different functions when the system runs in batches, so that the data generated by different functions in daily use can be processed and calculated in a centralized manner. In this way, the vocabulary in the index information table represents the corresponding business type to a certain extent, but the usage frequency of different functions is different. For functions with higher usage frequency, more users are also familiar with them. Therefore, users can directly associate the corresponding business type through the corresponding business vocabulary. For functions with low usage frequency, they may only be used by a smaller range of users. Therefore, when other users encounter a malfunction, it may be difficult to directly identify the function through the business vocabulary in the index information table. Therefore, it can avoid the addition of related unfamiliar words to the label library. The preset value is set according to the actual situation and is not limited in this manual. By using business vocabulary with higher frequency in the index information table as labels, the identifiable efficiency of labels in the label library can be improved, which is convenient for users to quickly feedback fault information.

[0118] Exemplarily, during the process of running a batch of the system, the frequency of the business words in the index information table is counted, and the frequency of occurrence of all business words can be sorted from high to low, and then the sequence with an occurrence frequency exceeding a preset value is added to the candidate business type label queue. In some other embodiments, the frequency of occurrence of all business words can also be sorted from high to low to form a vocabulary queue, and then a certain percentage of words can be selected from high to low according to the length of the vocabulary queue. The specific selection percentage is not limited in this specification.

[0119] In addition to obtaining labels through system recommendations, labels that are not recommended by the system can also be supplemented through manual entry, ensuring that more functions of the application software are labeled. As an option, Figure 6 As shown, the preset business type label acquisition process also includes:

[0120] S501: Acquire the business vocabulary added by the backend personnel, and add the business vocabulary to the candidate business type label queue;

[0121] S502: Screening the candidate service type label queue according to preset rules to determine a preset service type label.

[0122] It can be understood that, through manual entry, the system recommendation can be supplemented, and the user's usage habits and ability to understand vocabulary can be considered to select easy-to-recognize vocabulary. Specifically, multiple groups of candidate business vocabulary can be pre-set for the same function, and multiple groups of users can select the multiple groups of business vocabulary, and determine the business vocabulary with better user preferences as the business vocabulary of the corresponding function for manual entry. In this way, the business vocabulary is entered according to the user's preferences, which can improve the readability and recognizability of data use. In some other embodiments, personalized manual recommendations can also be made according to the user. For example, after different users log in to the corresponding account, they will set the label library on the setting page, where the business type label includes multiple options, and personalized selection is made according to the user's own preferences, so as to avoid the failure of some functional failures caused by individual preference differences to be fed back to the background operation and maintenance personnel in a timely and accurate manner. It should be noted that personalized manual recommendations refer to user recommendations, not recommendations entered by backend staff. User-recommended tags also need to be filtered through preset rules to prevent the recommended tags from being configured in advance. For example, when a user-recommended tag fails the filter, the client will prompt "The recommended tag is already occupied, please reselect the tag" and other prompts to allow the user to make a second choice.

[0123] It should be noted that the process of obtaining the business type label in the above steps can be set by the developer during the application development process, so that the framework of the label library can be built in advance and most of the labels can be filled into the label library. However, as the application adapts to the increase of scenarios, its implementation functions are also increasing. When adding corresponding functions, corresponding labels can also be configured. Therefore, the business category labels and business type labels in the label library can be increased with the increase of application functions. The specific configuration method can be manual entry by back-end personnel, which can improve the configuration efficiency of the expected increase of labels later.

[0124] In the embodiment of this specification, in order to quickly filter out suitable labels from the candidate service type label queue, such as Figure 7 As shown, the candidate service type label queue is screened according to a preset rule to determine a preset service type label, including:

[0125] The business terms in the candidate business type label queue are processed in the following order:

[0126] S601: Determine the service type corresponding to the service vocabulary and the service category to which the service type belongs;

[0127] S602: According to the service type, obtain a service type tag set related to the service type;

[0128] S603: Calculating semantic similarity between the business vocabulary and each business type label in the business type label set, and obtaining all similarity values;

[0129] S604: Determine whether all the similarity values ​​are greater than a preset threshold value;

[0130] S605: If all the similarity values ​​are not greater than a preset threshold value, the business vocabulary is determined as a preset business type label.

[0131] It can be understood that in order to avoid label redundancy, the candidate business type label queue needs to be screened. Since the business types in the same business category are similar, the similarity rate of the business type labels is relatively high. Redundant processing is only performed through the business type labels under the business category, which can improve the efficiency and accuracy of processing. For example, for a new business type label A, it cannot be blindly added to the label library, because this may cause label redundancy, that is, there are duplicate labels in the label library. In order to avoid label redundancy, it is necessary to perform a conflict detection on this new label, that is, to check whether there is a similar label in the label library. If there is, it will not be selected for storage, otherwise it will be selected to be stored in the label library. The conflict detection method used in this article is: analyze the maximum similarity between Ar (with all business type label sets in the business category to which the business type belongs) and A. The similarity algorithm here can use the similarity at the character level. When the similarity is greater than the preset threshold value (such as 0.8), it can be considered that there is a similar label, so the system does not need to continue to store the label. When the similarity is less than the preset threshold value (such as 0.8), it is considered that there is no similar label in the label library and it continues to be stored in the label library.

[0132] The embodiment of this specification provides a method for client application information feedback, such as Figure 8As shown, it is a change process of the client page in the method, wherein when the user uses the application to handle credit card business, such as repayment business, the page freezes so that the business cannot be handled normally. The user can first take a screenshot to determine the true situation of the problem, then forcefully exit the program, and then re-enter the interactive interface of the application, click the feedback button, and a selection button constructed by the tag library will appear. First, select the business type button marked with repayment, and then enter the selection content of the business type label. The user makes a selection according to the actual situation. For example, if a failure occurs during the installment payment process, click the installment payment button, and finally enter the feedback interface. The user can provide feedback in the form of text input and file (screenshot information) upload, and finally click the completion and feedback button, that is, the rapid feedback of the fault problem is realized. This article can promptly accept and feedback the user's feedback information to the back-end personnel. Compared with the existing technology that requires manual link flow and other steps, this article simplifies the customer problem feedback channel, improves the customer's processing efficiency of customer feedback information, and thus improves the customer's user experience.

[0133] It should be noted that Figure 8 This is just one way of displaying the method provided in the embodiments of this specification. There may be other ways of displaying, which will not be elaborated in this specification.

[0134] Based on the above-mentioned method for providing feedback of client application information, the embodiment of this specification also provides a device for providing feedback of client application information, such as Fig. 9 As shown, the device comprises:

[0135] The service type determination module 100 is used to determine the service type reported by the user according to the user operation instruction;

[0136] A feedback file forming module 200, configured to receive user feedback information regarding the service type, and package the feedback information and the service type into a feedback file;

[0137] The feedback information processing module 300 is used to send the feedback file to a backend server corresponding to the business type, so that backend personnel can process the feedback file.

[0138] The beneficial effects obtained by the above-mentioned device are consistent with the beneficial effects obtained by the above-mentioned method, and will not be described in detail in this specification.

[0139] Based on the same inventive concept, an embodiment of this specification further provides a client, the client runs an application, and the client is configured with the above-described method.

[0140] like Fig.10As shown, a computer device provided in an embodiment of the present invention, the computer device 1002 may include one or more processors 1004, such as one or more central processing units (CPUs), each of which may implement one or more hardware threads. The computer device 1002 may also include any memory 1006, which is used to store any kind of information such as code, settings, data, etc. Non-restrictive, for example, the memory 1006 may include any one or more combinations of the following: any type of RAM, any type of ROM, flash memory device, hard disk, optical disk, etc. More generally, any memory may use any technology to store information. Further, any memory may provide volatile or non-volatile retention of information. Further, any memory may represent a fixed or removable component of the computer device 1002. In one case, when the processor 1004 executes an associated instruction stored in any memory or a combination of memories, the computer device 1002 may perform any operation of the associated instruction. The computer device 1002 also includes one or more drive mechanisms 1008 for interacting with any memory, such as a hard disk drive mechanism, an optical disk drive mechanism, etc.

[0141] The computer device 1002 may also include an input / output module 1010 (I / O) for receiving various inputs (via input device 1012) and for providing various outputs (via output device 1014). A specific output mechanism may include a presentation device 1016 and an associated graphical user interface (GUI) 1018. In other embodiments, the input / output module 1010 (I / O), input device 1012, and output device 1014 may not be included, and the computer device 1002 may be used as a computer device in a network. The computer device 1002 may also include one or more network interfaces 1020 for exchanging data with other devices via one or more communication links 1022. One or more communication buses 1024 couple the components described above together.

[0142] The communication link 1022 may be implemented in any manner, for example, through a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. The communication link 1022 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc. governed by any protocol or combination of protocols.

[0143] Corresponds to Figure 2-Figure 7 The method in this article also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above method are executed.

[0144] The embodiment of the present invention also provides a computer readable instruction, wherein when the processor executes the instruction, the program therein causes the processor to execute the following Figures 2 to 7 The method shown.

[0145] It should be understood that in the various embodiments of this document, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this document.

[0146] It should also be understood that in the embodiments of this article, the term "and / or" is only a description of the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0147] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this article.

[0148] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0149] In the several embodiments provided herein, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or can be electrical, mechanical or other forms of connection.

[0150] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments of this article.

[0151] In addition, each functional unit in each embodiment of this invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit may be implemented in the form of hardware or in the form of software functional unit.

[0152] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this article is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of this article. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0153] Specific embodiments are used in this article to illustrate the principles and implementation methods of this article. The description of the above embodiments is only used to help understand the methods and core ideas of this article. At the same time, for general technicians in this field, according to the ideas of this article, there will be changes in the specific implementation methods and application scopes. In summary, the content of this specification should not be understood as a limitation on this article.

Claims

1. A method for client application information feedback, characterized in that: The method comprises: Determine the service type of the user feedback according to the user operation instruction, where the service type is a service function in a specified application program; Obtain the user's operation instructions based on the tag library and determine the business type tag; Determining the service type reported by the user according to the service type label; The process of establishing the label library includes: Determine the client application system and the database corresponding to the application system; According to the database, obtaining the business categories in the application system and the business types included in the business categories; According to the database, obtaining the business types in the application system and the log information corresponding to each business type; Determine at least one service type corresponding to the service type in the application system according to the service type and the log information; Establishing a first mapping relationship between the service type and a preset service type label, and establishing a second mapping relationship between the service type and a preset service type label; Wherein, the preset label represents the characteristics of the corresponding business object; Determining a relationship between the preset service category label and the preset service type label according to the relationship between the service category and the service type, the first mapping relationship, and the second mapping relationship; Establishing the tag library according to the relationship between the preset service category tag and the preset service type tag; receiving feedback information from a user regarding the service type, and packaging the feedback information and the service type into a feedback file; The feedback file is sent to a backend server corresponding to the business type, so that backend personnel can process the feedback file.

2. The method for client application information feedback according to claim 1, characterized in that: The preset service type label acquisition process includes: Get the index information table of the application system when the system runs a batch; When the system runs a batch, frequency statistics are performed on the index information table; Add business words with a frequency exceeding a preset value to a candidate business type label queue; The candidate service type label queue is screened according to preset rules to determine a preset service type label.

3. The method for client application information feedback according to claim 1, characterized in that: The preset service type label acquisition process also includes: Obtain the business vocabulary added by the backend personnel, and add the business vocabulary to the candidate business type label queue; The candidate service type label queue is screened according to preset rules to determine a preset service type label.

4. The client application information feedback method according to claim 2 or 3, characterized in that: The screening of the candidate service type label queue according to a preset rule to determine a preset service type label includes: The business terms in the candidate business type label queue are processed in the following order: Determine the business type corresponding to the business vocabulary and the business category to which the business type belongs; According to the business category, obtaining a business type tag set related to the business category; Calculating semantic similarity between the business vocabulary and each business type label in the business type label set, and obtaining all similarity values; Determine whether all the similarity values ​​are greater than a preset threshold value; If all the similarity values ​​are not greater than the preset threshold value, the business vocabulary is determined as a preset business type label.

5. The client application information feedback method according to claim 1, characterized in that: The feedback information includes user identification information and user operation information.

6. A client application information feedback device, characterized in that: The device comprises: A service type determination module is used to determine the service type reported by the user according to the user's operation instruction; The business type is a business function in a specified application program; Obtain the user's operation instructions based on the tag library and determine the business type tag; Determining the service type reported by the user according to the service type label; The process of establishing the label library includes: Determine the client application system and the database corresponding to the application system; According to the database, obtaining the business categories in the application system and the business types included in the business categories; According to the database, obtaining the business types in the application system and the log information corresponding to each business type; Determine at least one service type corresponding to the service type in the application system according to the service type and the log information; Establishing a first mapping relationship between the service type and a preset service type label, and establishing a second mapping relationship between the service type and a preset service type label; Wherein, the preset label represents the characteristics of the corresponding business object; Determining a relationship between the preset service category label and the preset service type label according to the relationship between the service category and the service type, the first mapping relationship, and the second mapping relationship; Establishing the tag library according to the relationship between the preset service category tag and the preset service type tag; A feedback file forming module, used for receiving feedback information from users regarding the service type, and packaging the feedback information and the service type into a feedback file; The feedback information processing module is used to send the feedback file to a background server corresponding to the business type, so that background personnel can process the feedback file.

7. A client, characterized in that: The client runs an application, and the client is configured with the method according to any one of claims 1 to 5.

8. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 5 is implemented.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 5 is implemented.

Images