Customer service function configuration method and device, equipment, medium and program product

Abstract

The application discloses a customer service function configuration method, device, equipment, medium and program product. The method comprises the following steps: receiving a component creation operation in a first client. The component creation operation is used to create a customer service component. The customer service component is used to establish a customer service channel between the first client and a third-party platform. The customer service channel is used to synchronize a customer service message received in the third-party platform to the first client. In response to the component creation operation, a component creation interface is displayed. The component creation interface is used to configure component parameters of the customer service component. The configuration operation on the component parameters in the component creation interface is received. The component parameters comprise platform information corresponding to the third-party platform. The customer service component between the first client and the third-party platform is created based on the component parameters. The customer service message of the third-party platform can be synchronized to the first client by creating the customer service component, and the customer service message interaction efficiency between the two can be improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a configuration method, apparatus, device, medium, and program product for customer service functions. Background Technology

[0002] To achieve efficient message management, enterprises typically forward messages from third-party platforms to designated clients, where customer service personnel can reply to messages centrally through their customer service accounts within the client, which helps improve message processing efficiency.

[0003] In related technologies, third-party service providers, after obtaining authorization from the client and the enterprise, acquire relevant interface documentation to develop third-party applications. Once the enterprise integrates the third-party application into the client, it can transmit messages from various third-party platforms to the client through the customer service functions provided by the third-party application.

[0004] However, third-party service providers face a heavy workload when developing third-party applications. Integrating third-party applications into clients requires configuring a large amount of information, making the process cumbersome and resulting in low overall efficiency. Summary of the Invention

[0005] This application provides a configuration method, apparatus, device, medium, and program product for customer service functions, which can improve the efficiency of customer service message interaction between a first client and a third-party platform. The technical solution is as follows:

[0006] On the one hand, a method for configuring a customer service function is provided, the method including:

[0007] The system receives a component creation operation in the first client. The component creation operation is used to create a customer service component. The customer service component is used to establish a customer service channel between the first client and a third-party platform. The customer service channel is used to synchronize customer service messages received in the third-party platform to the first client.

[0008] In response to the component creation operation, a component creation interface is displayed, which is used to configure the component parameters of the customer service component;

[0009] The component parameter configuration operation is received in the component creation interface, and the component parameter includes platform information corresponding to the third-party platform.

[0010] A customer service component is created between the first client and the third-party platform based on the component parameters.

[0011] On the other hand, a configuration device for a customer service function is provided, the device comprising:

[0012] A creation module is used to receive a component creation operation in a first client. The component creation operation is used to create a customer service component. The customer service component is used to establish a customer service channel between the first client and a third-party platform. The customer service channel is used to synchronize customer service messages received from the third-party platform to the first client.

[0013] The display module is used to display the component creation interface in response to the component creation operation. The component creation interface is used to configure the component parameters of the customer service component.

[0014] A configuration module is used to receive configuration operations for the component parameters in the component creation interface, wherein the component parameters include platform information corresponding to the third-party platform;

[0015] The creation module is also used to create a customer service component between the first client and the third-party platform based on the component parameters.

[0016] In an optional embodiment, the configuration module is further configured to receive a platform identifier input operation for the third-party platform in the component creation interface; and to receive a protection information input operation in the component creation interface, wherein the protection information is protection information pre-generated in the first client corresponding to the third-party platform.

[0017] In an optional embodiment, the configuration module is further configured to display at least two candidate scenarios, which are pre-provided scenarios that support the creation of the customer service component. The candidate scenarios include at least two of the following: client scenario, mini-program scenario, and webpage scenario. In response to receiving a selection operation for a first scenario among the at least two candidate scenarios, the selection operation is used as a configuration operation for the component parameters.

[0018] In an optional embodiment, the creation module is further configured to determine the matching relationship between the platform identifier and the entity that creates the customer service component; and, if the matching relationship indicates that the third-party platform corresponding to the platform identifier and the entity that creates the customer service component meet preset entity requirements, create the customer service component between the first client and the third-party platform based on the component parameters.

[0019] In an optional embodiment, the configuration module is further configured to receive an input operation for the platform name of the third-party platform in the component creation interface; or, to receive an upload operation for a screenshot of the interface of the third-party platform in the component creation interface.

[0020] In an optional embodiment, the configuration module is further configured to receive a callback input operation in the component creation interface and obtain callback information, wherein the callback information is used to indicate the information sending and receiving address when the third-party platform and the first client perform message interaction.

[0021] In an optional embodiment, the configuration module is further configured to receive input operations on the callback information input area in the component creation interface to obtain candidate callback information; verify the candidate callback information to obtain a verification result, wherein the verification result is used to indicate the send / receive capability corresponding to the information send / receive address of the candidate callback information; and determine the candidate callback information as the callback information if the verification result indicates that the candidate callback information meets the information send / receive address requirements.

[0022] In an optional embodiment, the apparatus further includes:

[0023] The sharing module is used to generate sharing information corresponding to the customer service component in response to receiving a sharing operation for the customer service component. The sharing information is used to share the creation interface of the customer service component with the registered account of the third-party platform. The sharing information includes at least one of a sharing link and a sharing graphic code. The registered account is the account of the registered entity registered on the third-party platform in the first client.

[0024] On the other hand, a computer device is provided, the computer device including a processor and a memory, the memory storing at least one instruction, at least one program, code set or instruction set, the at least one instruction, the at least one program, the code set or instruction set being loaded and executed by the processor to implement the configuration method of customer service functions as described in any of the above embodiments of this application.

[0025] On the other hand, a computer-readable storage medium is provided, wherein at least one instruction, at least one program, code set, or instruction set is stored therein, wherein the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by a processor to implement a configuration method for customer service functions as described in any of the embodiments of this application above.

[0026] On the other hand, a computer program product or computer program is provided, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the configuration method for the customer service function described in any of the above embodiments.

[0027] The beneficial effects of the technical solutions provided in this application include at least the following:

[0028] Creating a customer service component via a receiving component creation operation allows for the establishment of a customer service channel between the primary client and a third-party platform without the need for third-party application development. This enables customer service message transmission, reduces the workload for service providers developing third-party applications, improves the efficiency of establishing customer service channels, and eliminates the maintenance costs of third-party applications. Synchronizing customer service messages received from the third-party platform to the primary client facilitates timely message processing by customer service personnel, improving message processing efficiency. Configuring the parameters of the customer service component during creation allows for the identification of the third-party platform with which the primary client will establish a customer service channel, satisfying users' personalized needs for customizable settings at both ends of the channel. Attached Figure Description

[0029] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0030] Figure 1 This is a schematic diagram of a configuration system for customer service functions provided in an exemplary embodiment of this application;

[0031] Figure 2 This is a flowchart of a configuration method for a customer service function provided in an exemplary embodiment of this application;

[0032] Figure 3 This is a schematic diagram of a component creation interface provided in an exemplary embodiment of this application;

[0033] Figure 4 This is a schematic diagram of the review process provided by an exemplary embodiment of this application;

[0034] Figure 5 This is a flowchart of a method for invoking a customer service function provided in an exemplary embodiment of this application;

[0035] Figure 6 This is a schematic diagram of a component licensing interface provided in an exemplary embodiment of this application;

[0036] Figure 7 This is a schematic diagram of the permission verification process for an account provided in an exemplary embodiment of this application;

[0037] Figure 8 This is a schematic diagram illustrating the influence of visible labels on the workbench on the component distribution results, provided in an exemplary embodiment of this application.

[0038] Figure 9 This is a flowchart of a configuration method for a customer service function provided in another exemplary embodiment of this application;

[0039] Figure 10 This is a structural block diagram of a configuration device for customer service functions provided in an exemplary embodiment of this application;

[0040] Figure 11 This is a structural block diagram of a configuration device for a customer service function provided in another exemplary embodiment of this application;

[0041] Figure 12 This is a structural block diagram of a computer device provided in an exemplary embodiment of this application. Detailed Implementation

[0042] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0043] The terminology used in this application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The singular forms “a,” “the,” and “the” used in this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more of the associated listed items.

[0044] It should be noted that all information and data involved in this application are authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0045] First, a brief introduction to the terms used in the embodiments of this application:

[0046] Application Programming Interface (API): An API is an interface that allows different software applications to interact and communicate. It enables various software systems to share data, invoke functions, etc., according to certain rules and conventions.

[0047] Callback Uniform Resource Locator (URL): A URL is a standard format used to identify the location of resources on the Internet. Common website addresses are a type of URL. A URL accurately locates a resource on the network, facilitating user access to and retrieval of various online resources such as web pages, images, and videos. A callback URL is a special type of URL primarily used for communication between different systems or applications. When a specific event occurs or an operation is completed, the server or application sends relevant data or information to a specified target address based on the pre-defined callback URL. For example, if system A requests system B to perform an operation, system B, after completing the operation, will return the result to the specified location in system A via the callback URL. This allows system A to receive timely feedback and perform subsequent processing.

[0048] Token: In the computer field, a token is a string or number that represents a certain right or permission. It is an authentication and authorization mechanism used to verify the identity of a user or system and grant them permission to access specific resources or perform specific operations.

[0049] Advanced Encryption Standard Key (AESKey / aeskey): The aeskey is the key used for the AES encryption algorithm. AES is a symmetric encryption algorithm that uses the same key for encryption and decryption. The aeskey's role is to encrypt and decrypt data, ensuring the confidentiality and integrity of the data.

[0050] Third-party service providers: These are third parties that provide services to users of the first client. They use the API provided by the first client to perform secondary development and provide richer functions. They can also be simply referred to as "service providers".

[0051] Third-party applications: These are the carriers through which third-party service providers offer services. Users can use the functions provided by the service provider within the first client by authorizing the installation of third-party applications within the first client.

[0052] Authorizing application installation: After a service provider releases a third-party application, it can reach users by providing installation QR codes, installation links, and other promotional methods to guide users to authorize the installation of the application.

[0053] Application permissions: A permission system is set for certain data that an application needs to access. Service providers need to select the required permissions in advance, and the service provider can only obtain the corresponding data after the user agrees.

[0054] Development information: refers to configuration information such as callback URL, token, and AES key. Some events during the user's use of the third-party application will trigger a callback to this callback URL, and the service provider needs to handle these events accordingly.

[0055] To expand their business scope and enhance market influence, companies often choose to join multiple third-party platforms to increase exposure and attract more potential customers. To achieve efficient message management and ensure timely and accurate responses to customer inquiries and feedback from various platforms, companies typically aggregate messages generated from third-party platforms into a unified client application. Within this client, companies assign dedicated customer service personnel to centrally process and respond to these messages. This customer service message processing model significantly improves message processing efficiency, helps companies enhance customer service quality, and increases customer satisfaction.

[0056] For each third-party platform, the platform typically provides message transmission services to the companies that join the platform, forwarding messages from the platform to the client to meet the company's need for unified processing of customer service messages.

[0057] In related technologies, customer service functions are primarily implemented through the creation of third-party applications. After obtaining legal authorization from both the client and the enterprise, a third-party service provider corresponding to the third-party platform develops the application by acquiring the relevant interface documentation. Once the enterprise successfully integrates the third-party application into its client-side account, it can leverage the customer service functions provided by the application to transmit messages from the third-party platform to the client, where the enterprise's customer service account handles the messages centrally.

[0058] For related technical solutions, third-party service providers face a heavy workload when developing applications, requiring significant investment of manpower, resources, and time. Secondly, integrating the application with the client requires configuring a large amount of information, resulting in low application integration efficiency. Furthermore, enterprises face high application maintenance costs after integration. Therefore, reducing development workload, improving configuration efficiency when integrating customer service functions, and lowering enterprise application maintenance costs are urgent issues that need to be addressed.

[0059] This application provides a configuration method for customer service functions, which can synchronize messages from third-party platforms to the client by creating customer service components, providing a lighter-weight customer service function access method, reducing workload and the threshold for use.

[0060] Third-party service providers corresponding to third-party platforms can create customer service components within the first client. They do not need to develop a complete application; they only need to fill in the relevant configuration information. The third-party service provider then shares the created customer service component with enterprises registered on the third-party platform. These enterprises authorize the integration of the customer service component into the first client and set up customer service accounts within the first client to receive messages. This allows messages received by the enterprise on the third-party platform to be synchronized to the first client, with the customer service accounts handling all messages uniformly.

[0061] The customer service components created by the third-party service provider corresponding to the third-party platform enable message interaction between the third-party platform and the first client. The third-party service provider can be an external service provider authorized by the third-party platform to create customer service components for its own platform, or it can be an internal technical staff member of the third-party platform (i.e., in this case, the third-party platform is equivalent to the third-party service provider). This application does not impose any limitations on this. The customer service components created by the third-party service provider can be used by all enterprises registered on the third-party platform.

[0062] The configuration method for customer service functions provided in this application can reduce the workload of service providers in creating third-party applications to implement customer service functions, save enterprises the cost of maintaining applications, and meet the needs of enterprises for cross-platform message interaction by using components, which are a lighter-weight customer service function access method than applications, thereby improving the processing efficiency of customer service messages.

[0063] Secondly, the configuration system for the customer service function involved in the embodiments of this application will be described, for illustrative purposes only. Please refer to [the relevant documentation / reference]. Figure 1 The system involves a first terminal 110 and a second terminal 120. A first client 100 is installed in the first terminal 110 and the second terminal 120. The first client 100 is a client that provides customer service component creation services. Messages from third-party platforms can be transmitted to the first client 100 through the customer service component 103.

[0064] For example, the first terminal 110 is a terminal device used by a third-party service provider, and the second terminal 120 is a terminal device used by enterprise personnel. The third-party service provider corresponds to the third-party platform, and the enterprise is the company registered on the third-party platform.

[0065] In this process, a third-party service provider logs into a first account 101 on a first client 100 of a first terminal 110 and creates a customer service component 103. The created customer service component 103 is then shared with enterprise personnel via a second account 102 logged into the first client 100. After authorizing the customer service component 103 through the second account 102, the enterprise personnel install the customer service component 103 on the first client 100 and configure the customer service account within the first client 100. The customer service account can then receive messages from the third-party platform through the customer service component 103 and process them within the first client 100.

[0066] The component creation interface 130 for creating customer service component 103 includes multiple input areas for configuring component parameters, which include platform information corresponding to the third-party platform. The third-party service provider inputs the component parameters through first account 101, configures customer service component 103, and submits it for review. The first client 100's backend reviews the compliance of customer service component 103 and returns the review result. If the review is successful, first account 101 can obtain the sharing information of customer service component 103, which includes at least one of a sharing link and a sharing graphic code. First account 101 sends the sharing information to second account 102, which triggers access authorization, thus enabling customer service component 103 to access the first client 100.

[0067] The component authorization interface 140 corresponding to customer service component 103 is used to configure authorization permission information, making it easier for third-party service providers to develop more services based on the permissions provided by enterprise personnel and the APIs provided by the first client 100. For example, the component authorization interface 140 includes a customer service account selection area, which is used to configure the customer service account for receiving messages from third-party platforms.

[0068] After authorization, the second account 102 will not add any applications to the workbench interface within the first client 100, but will display authorization record information. This authorization record information is used to record relevant information about the third-party platforms that have been authorized to receive messages. For example, third-party platform A creates a customer service component 'a' within the first client 100 and shares it with enterprise B. After enterprise B authorizes and installs customer service component 'a' by logging into its enterprise account within the first client 100, it can receive customer service messages sent by third-party platform A through customer service component 'a' on the first client 100.

[0069] The first terminal 110 and the second terminal 120 mentioned above can be various forms of terminal devices such as mobile phones, tablets, desktop computers, portable laptops, smart TVs, vehicle terminals, and smart home devices. This application embodiment does not limit them in this way.

[0070] In some embodiments, the terminal that logs in to the first account 101 and the second account 102 can be the same.

[0071] In some embodiments, the configuration system for the customer service function also involves a server 150. When the first terminal 110 shares the customer service component 103 with the second terminal 120, the sharing is forwarded through the server 150. There is a communication connection between the first terminal 110 and the server 150, and there is a communication connection between the second terminal 120 and the server 150.

[0072] It is worth noting that the aforementioned server 150 can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms.

[0073] In some embodiments, the server 150 described above can also be implemented as a node in a blockchain system.

[0074] Based on the above-described terms and application scenarios, the configuration method for the customer service function provided in this application will be explained. This method can be executed by a server or a terminal, or by both a server and a terminal. In this embodiment, the method is illustrated by being executed by a terminal. Figure 2 As shown, Figure 2 This is a flowchart of a configuration method for a customer service function provided in an exemplary embodiment of this application. The method includes the following steps.

[0075] Step 210: Receive the component creation operation from the first client.

[0076] The component creation operation is used to create a customer service component, which is used to establish a customer service channel between the first client and the third-party platform. The customer service channel is used to synchronize customer service messages received from the third-party platform to the first client.

[0077] Among them, the first client in the terminal is a client that can provide office services and message transmission services. The types of the first client include, but are not limited to, the following: (1) applications / software installed in the terminal; (2) web pages opened in the terminal; (3) small programs running in the terminal, etc.

[0078] The first client supports user account registration and message interaction through these accounts. For example, user A registers account A within the first client, and user B registers account B within the first client. When a message association is established between account A and account B, it means that user A can send messages to account B through account A, and user B can view messages within the first client by logging into account B. Here, the message association refers to the relationship between the accounts that allows for message transmission.

[0079] Third-party platforms are independent of the primary client. Businesses or individuals can register accounts on these platforms and conduct business through the space they provide. Accounts on third-party platforms can receive customer service messages. These messages are generated when users make business inquiries and are handled by customer service personnel through their customer service accounts.

[0080] Optionally, the first client may currently have a first account logged in. This first account is created by a third-party service provider within the first client, and the third-party service provider corresponds to the third-party platform. For example, the third-party service provider is an external service provider authorized by the third-party platform to create customer service components for its own platform, or it can directly refer to the third-party platform.

[0081] Alternatively, the first account belongs to a third-party platform. The third-party service provider logs into the first account with authorization from the third-party platform and initiates a component creation operation within the first client to create a customer service component.

[0082] The customer service component is used to establish a customer service channel between the first client and the third-party platform. It can be used by enterprises or individual users who are registered on the third-party platform to transmit customer service messages received by enterprises or individuals on the third-party platform to a designated account in the first client for processing.

[0083] Step 220: In response to the component creation operation, display the component creation interface.

[0084] The component creation interface is used to configure the component parameters of the customer service component. The component creation interface contains multiple component parameter display areas, which are used to configure different types of component parameters.

[0085] Optionally, the component parameters include the following types of parameters.

[0086] 1. Protected Information Parameters: SuiteID (Suite Identifier) ​​and secret. SuiteID is used to uniquely identify the currently created customer service component, facilitating the management of the customer service component by the primary client; secret refers to the key used for encryption, decryption, authentication, and authorization operations, ensuring data security and authentication during message interaction between the third-party platform and the primary client, and preventing information leakage and unauthorized access.

[0087] The protection information parameters are automatically generated by the first client for the customer service component after receiving the component creation operation. In some embodiments, the protection information parameters can be retrieved again when creating the customer service component. For example, after receiving a protection information parameter reset operation, the first client will automatically generate new protection information parameters and display them through the component creation interface.

[0088] For example, the first client randomly generates protection information parameters based on the account identifier of the first account currently creating the customer service component. Taking the account identifier of the first account as a string of numbers as an example, the first client obtains n random numbers, randomly selects m numbers from the account identifier of the first account, randomly combines the above m+n random numbers into a string, and uses a hash algorithm to calculate a fixed hash value as the information protection parameter. Here, m and n are positive integers.

[0089] Automatically and randomly generating protection information parameters through the first client can improve the configuration efficiency of component parameters, facilitate the management of customer service components by the first client, ensure that the identifier assigned to each customer service component when it is created is unique, and enhance data security.

[0090] 2. Platform Information Parameters: This includes at least one of the following: access scenario, scenario description, and scenario screenshot, used to indicate the platform information of the third-party platform. The access scenario indicates the platform identifier of the third-party platform, which uniquely identifies the third-party platform and includes, but is not limited to, the platform name, platform ID, and platform icon. In other words, it indicates the type of third-party platform the customer service component needs to pass messages to the first client. The scenario description introduces the basic information of the third-party platform. The scenario screenshot refers to an image obtained by taking a screenshot of the third-party platform's display interface on the terminal, visually demonstrating the specific information of the third-party platform.

[0091] 3. Component permission parameters: These indicate the permissions that the customer service component has, such as the permission to obtain relevant information about companies that have joined third-party platforms, and the permission to manage messages received from third-party platforms.

[0092] 4. Development parameters: include callback URL, token, and EncodingAESkey (i.e., aeskey).

[0093] The callback URL is used to indicate the information sending and receiving address when the third-party platform and the first client interact with each other. When the first client interacts with the third-party platform, after the third-party platform completes a specific operation or an event occurs, it will send relevant data or messages to the designated receiving point corresponding to the first client based on the callback URL.

[0094] The token serves as an authentication tool in interactions between the first client and the third-party platform. For example, when a user account initiates an operation request related to the third-party platform from the first client, the first client includes the token in the request and sends it to the third-party platform. Upon receiving the request, the third-party platform verifies the token to confirm the legitimacy of the request's origin and the user's operational permissions. Only after successful token verification will the third-party platform respond to the request and execute the corresponding operation.

[0095] AESKey is primarily used for data encryption and decryption. When transmitting messages between a primary client and a third-party platform, AESKey is used to encrypt the message content to prevent data from being stolen or tampered with during transmission.

[0096] Indicative, such as Figure 3 As shown, Figure 3 This is a schematic diagram of a component creation interface.

[0097] The component creation interface 300 includes a first display area 301 for displaying protection information parameters, a second display area 302 for displaying platform information parameters, a third display area 303 for displaying component permission parameters, and a fourth display area 304 for displaying development parameters.

[0098] The first display area 301 includes a target control 3011. Triggering the target control 3011 allows it to reacquire protection information parameters. In other words, the first client responds to the triggering operation of the target control 3011 and reassigns protection information parameters to the client component. The second display area 302, the third display area 303, and the fourth display area 304 are editable areas used to receive input information.

[0099] Step 230: Receive configuration operations for component parameters in the component creation interface.

[0100] The component parameters include platform information corresponding to the third-party platform. This platform information, which appears in step 220, indicates the third-party platform from which the created customer service component will transmit messages.

[0101] Optionally, it can receive input operations for the platform identifier of a third-party platform in the component creation interface.

[0102] The platform identifier of a third-party platform is used to uniquely indicate the identity of the third-party platform. The types of platform identifiers include, but are not limited to: (1) platform name; (2) platform icon; (3) appid created by the platform, which can be an ID (Identity) composed of at least one of Chinese characters, English characters, numbers, and special symbols; and (4) platform homepage information.

[0103] Optionally, the component can receive input of the platform name of a third-party platform in the component creation interface. Alternatively, it can receive input of a screenshot of the third-party platform's interface uploaded in the component creation interface. Or, it can receive input of a platform description of the third-party platform in the component creation interface.

[0104] Obtaining platform identifiers from third-party platforms through various methods can improve user input efficiency, allowing users to freely choose the most convenient input method to enter the platform identifier and meeting their diverse needs when entering configuration information. Obtaining platform identifiers from user-uploaded platform interface screenshots can avoid errors when manually typing identifier information and improve input accuracy.

[0105] The component creation interface includes a platform identifier input area for entering the platform identifier, that is, Figure 3 The second display area 302 receives the platform name input operation in the platform identifier input area, obtains the platform identifier of the third-party platform, and completes the configuration of the platform information corresponding to the third-party platform in the component parameters.

[0106] Optionally, the system receives protection information input from the component creation interface. This protection information is pre-generated in the first client and corresponds to the third-party platform. The protection information refers to the protection information parameters that appear in step 220.

[0107] In some embodiments, the protection information can be pre-generated by the first client or actively entered when a third-party service provider creates a customer service component. The protection information can be changed during the parameter configuration process.

[0108] Optionally, at least two candidate scenarios are displayed. These at least two candidate scenarios are pre-provided scenarios that support the creation of customer service components. The candidate scenarios include at least two of the following: client-side scenarios, mini-program scenarios, and web page scenarios.

[0109] In response to receiving a selection operation for a first scenario among at least two candidate scenarios, the selection operation is treated as a configuration operation for component parameters.

[0110] In other words, having at least two candidate scenarios indicates that the third-party platform can be any type, including clients, mini-programs, and web pages. Receiving a selection operation for the first scenario signifies that the customer service component has been created and is used to implement message interaction between the first client and the first scenario.

[0111] It offers multiple access scenarios, providing services for creating customer service components for different types of third-party platforms. This meets the message interaction needs of various platforms using customer service components, attracting more third-party platforms to establish partnerships with the First Client. It expands the customer base of the First Client, covering more user scenarios and meeting the needs of enterprise users to transmit messages from different platforms to the First Client for processing via customer service components, thereby improving the efficiency of enterprise users in handling customer service messages.

[0112] Optionally, the system receives callback input from the component creation interface and obtains callback information. The callback information is used to indicate the message sending and receiving addresses when the third-party platform and the first client interact with each other.

[0113] The callback information refers to the development parameter in step 220: the callback URL.

[0114] For example, input is received into the callback information input area of ​​the component creation interface to obtain candidate callback information.

[0115] The callback information input area refers to Figure 3 The fourth display area 304 in the text.

[0116] The candidate callback information is verified to obtain the verification result. The verification result is used to indicate the sending and receiving capabilities corresponding to the sending and receiving addresses of the candidate callback information. The sending and receiving capabilities include two aspects: transmitting customer service messages from the third-party platform to the first client, and transmitting customer service messages from the first client to the third-party platform.

[0117] If the verification result indicates that the candidate callback information meets the information sending and receiving address requirements, the candidate callback information will be determined as the callback information.

[0118] For example, the first client sends a test message to the information sending and receiving address indicated by the candidate callback information. The test message contains at least two parameters and the parameter encryption method, etc. The information sending and receiving address receives the test message and sends it to the server corresponding to that address. The server encrypts the at least two parameters based on the parameter encryption method indicated in the test message to generate a verification message. The server then returns the verification message to the first client through the information sending and receiving address. When the verification message meets the preset information sending and receiving address requirements, the candidate callback information is determined to be correct and is used as the callback information.

[0119] The preset information sending and receiving address requirement refers to the match between the verification message returned by the information sending and receiving address and the result of encryption based on the parameters indicated by the first client.

[0120] By verifying the ability to send and receive callback information, it can be ensured that the customer service component can accurately and promptly transmit customer service messages between the third-party platform and the first client after being connected to the third-party platform, thus avoiding problems such as untimely and inefficient processing of customer service messages due to message transmission failure.

[0121] Step 240: Create a customer service component between the first client and the third-party platform based on the component parameters.

[0122] Before creating a customer service component, it is necessary to perform entity authentication on the third-party platform. Entity authentication refers to verifying whether the third-party platform that needs to access the customer service component is the same entity as the account that is currently creating the customer service component.

[0123] Adding a principal verification process ensures that the customer service component used for message interaction between the third-party platform and the primary client is created by the corresponding third-party service provider, guaranteeing that the entity creating the customer service component matches the entity of the third-party platform that needs to access it. This prevents unauthorized access to the third-party platform due to inconsistent principals, protects data security during the creation and interaction of customer service components, and prevents other accounts from misusing information to create customer service components on the third-party platform.

[0124] Optionally, the matching relationship between the platform identifier and the entity that created the customer service component can be determined.

[0125] If the matching relationship indicates that the third-party platform corresponding to the platform identifier and the entity that creates the customer service component meet the preset entity requirements, a customer service component between the first client and the third-party platform is created based on the component parameters.

[0126] For example, the authentication information of the third-party platform is obtained based on the platform identifier and the scenario type of the first scenario. The authentication information of the third-party platform is the information obtained by the third-party platform after identity authentication in the relevant authentication platform, which is used to indicate the identity and subject of the third-party platform.

[0127] For example, a relevant certification platform is a public platform used to register the registration information of various companies or platforms, making it easier for users to understand the relevant information of companies or platforms and confirm their compliance. Third-party platforms are certified after uploading information that can prove their identity to the relevant certification platform.

[0128] By checking the account information of the third-party service provider who created the customer service component within the first client, it can be confirmed whether the entity creating the customer service component is the same as the entity of the third-party platform corresponding to the platform identifier. If they are the same, it meets the preset entity requirements. If they are different, it does not meet the preset entity requirements.

[0129] In some embodiments, the third-party service provider creates the customer service component with authorization from the third-party platform, or the third-party service provider creates the customer service component by logging into an account belonging to the third-party platform within the first client and performing entity authentication based on the account information and platform identifier of the third-party platform within the first client.

[0130] In some embodiments, after creating a customer service component, it needs to be submitted to the first client for review. Only after the review is approved can the customer service component be published in the first client.

[0131] Upon receiving an audit request, the audit result is obtained based on the configured component parameters. The audit request is used to request the first client to audit the customer service component.

[0132] If the component parameters meet the preset release requirements, the review result is determined to be approved. The preset release requirements include accuracy requirements, completeness requirements, and security requirements.

[0133] Once approved, the customer service component can be published in the first client, and the customer service component is successfully created.

[0134] Indicative, Figure 3 It also includes an audit control 305 for triggering audits. When the first client receives an operation to trigger the audit control 305, it begins to audit the customer service component.

[0135] like Figure 4 As shown, Figure 4 This is a diagram of the review process.

[0136] In the 400 review process, after the third-party service provider submits its initial review application, the first client will save the customer service component locally. Upon completion of the review, a result will be returned. If the review is successful, the customer service component will be in a "pending release" state, meaning it is ready to be released but not yet. Whether to release it and when to release it are determined by the third-party service provider. If the review fails, a notification message will be returned, prompting the third-party service provider to modify the component parameters. After modification, the component can be resubmitted for review until it is approved before it can be released.

[0137] In summary, the customer service configuration method provided in this application, by creating a customer service component through a receiving component creation operation, can establish a customer service channel between the first client and a third-party platform without the need to develop third-party applications. This enables the transmission of customer service messages, reduces the workload for service providers developing third-party applications, improves the efficiency of establishing customer service channels, and eliminates the maintenance costs of third-party applications. Synchronizing customer service messages received from the third-party platform to the first client facilitates timely processing of customer service messages by customer service personnel, improving message processing efficiency. Configuring the parameters of the customer service component during its creation to determine the information of the third-party platform with which the first client needs to establish a customer service channel allows users to customize the settings at both ends of the channel.

[0138] Once the third-party service provider has created the service, it will share the customer service component with the entities (enterprises or individuals) that have joined the third-party platform. After logging into their respective accounts on the first client, the entities will authorize the installation of the customer service component and then call the message interaction function provided by the customer service component to synchronize customer service messages from the third-party platform to the first client for processing.

[0139] Figure 5 This is a flowchart illustrating a method for invoking a customer service function provided in an exemplary embodiment of this application. The function is jointly executed by a first terminal 510 and a second terminal 520. The first client in the first terminal 510 is logged into a first account, and the first client in the second terminal 520 is logged into an existing account. The first account corresponds to a third-party platform, and the existing account corresponds to the entity registered on the third-party platform. Figure 5 The illustrated embodiments and Figure 2 The embodiments shown have a sequential relationship; the first one is executed. Figure 2 The steps in the illustrated embodiment are then executed. Figure 5 The steps in the illustrated embodiment are as follows. That is, steps 511 to 523 are steps performed after step 240. Steps 511 to 512 are steps performed by the first terminal 510, and steps 521 to 523 are steps performed by the second terminal 520.

[0140] Step 511: In response to receiving a sharing operation for the customer service component, generate the sharing information corresponding to the customer service component.

[0141] The information sharing feature is used to share the creation interface of the customer service component with the registered accounts on the third-party platform. The registered account is the account of the registered entity on the third-party platform in the first client.

[0142] After the customer service component is released in the first client, all entities that have joined the third-party platform can obtain the corresponding sharing information of the customer service component from the third-party platform, and authorize the installation of the customer service component in the first client by following the installation steps indicated in the sharing information and logging into their accounts in the first client.

[0143] The shared information includes at least one of a share link and a share graphic code.

[0144] Optionally, the methods for generating sharing information include, but are not limited to, the following: (1) automatically generating sharing information after the customer service component is created; (2) generating sharing information corresponding to the customer service component in response to receiving a trigger operation on the sharing control in the component creation interface; (3) generating sharing information corresponding to the customer service component in response to receiving a sliding operation in the component creation interface, wherein the sliding operation has a corresponding sliding trajectory, and the sliding trajectory meets the preset sharing information generation requirements; wherein the preset sharing information generation requirements refer to the shape of the sliding trajectory matching the shape of the preset trajectory; (4) generating sharing information corresponding to the customer service component in response to detecting a motion control operation on the first terminal, wherein the motion control operation refers to performing motion control on the first terminal to change the position and motion state of the first terminal. For example, the first terminal is a mobile phone, and when the user shakes the mobile phone, the mobile phone changes from a stationary state to a moving state.

[0145] Indicative, such as Figure 3 As shown, the component creation interface 300 also includes a sharing control 306. After receiving a trigger operation on the sharing control 306, the sharing information corresponding to the customer service component is generated.

[0146] Step 512: Send sharing information to the second terminal.

[0147] The second terminal is the terminal used by the registered entity. When the first terminal sends sharing information to the second terminal, it indicates that the third-party platform will share the information with the registered entity.

[0148] Optionally, there is a link between the account logged in on the first terminal and the registered account logged in on the second terminal. The first account sends shared information to the registered account through this link, thus enabling the first terminal to send shared information to the second terminal. The registered account can view the shared information within the first client.

[0149] Alternatively, there is a communication connection between the first terminal and the second terminal (e.g., Bluetooth communication connection, wireless communication connection, WiFi hotspot communication connection), and the first terminal sends shared information to the second terminal through the communication connection.

[0150] Alternatively, the shared information can be a shared graphic code. The distance between the first terminal and the second terminal (i.e., the distance between the service provider and the registered entity) meets the preset graphic code scanning requirements. The registered entity can directly use the second terminal to scan the shared graphic code loaded in the first terminal, so that the first terminal can send the shared information to the second terminal.

[0151] Step 521: Upon receiving the sharing information, display the component authorization interface based on the sharing information.

[0152] The system allows registered entities to access the component authorization interface by logging into their registered account on the first client and opening the shared information. This interface is used to configure authorization permissions, authorize the installation of customer service components, and enable message interaction functionality via these components.

[0153] Optionally, upon receiving the sharing information, the second terminal displays a component authorization interface in response to receiving a trigger operation on the sharing information. The triggering method corresponding to the trigger operation corresponds to the component creation method indicated in the sharing information.

[0154] For example, information is shared in the form of a shared link. Opening the link in the first client or opening the first client after copying the shared link can trigger the display of the component authorization interface.

[0155] For example, the information is presented as a shared graphic code. The shared graphic code can be scanned using the scanning function provided by the first client, or it can be identified using the long-press recognition function provided by the first client, which can trigger the display component authorization interface.

[0156] Step 522: Receive configuration operations for authorization information within the authorization interface.

[0157] Indicative, such as Figure 6 As shown, Figure 6 This is a schematic diagram of a component authorization interface. The component authorization interface 600 includes a customer service account selection area 610 and an authorization permission information area 620. The customer service account selection area 610 is used to configure the customer service account that receives messages from third-party platforms, and the authorization permission information area 620 is used to configure the permissions that the registered entity grants to third-party service providers / third-party platforms.

[0158] After selecting the target customer service account in the customer service account selection area 610, the target customer service account can receive customer service messages from the third-party platform within the first client. The target customer service account is the account of the customer service personnel of the registered entity within the first client. After configuring different types of permission information in the authorization permission information area 620, the third-party service provider can develop more services for the registered entity based on the API provided by the first client, increasing the types of functions that the customer service component can achieve.

[0159] For example, the authorization information area 620 can be configured with at least one of the following permission information: (1) the subject information of the registered entity (for example, if the registered entity is an enterprise, the subject information is enterprise information, which includes introductory information for introducing the enterprise’s related business and management information for managing the enterprise’s internal personnel, etc.); (2) the management of the customer service access, that is, the ability to manage the customer service account corresponding to the registered entity in the third-party platform; (3) the ability to obtain customer service message interaction records, that is, the ability to obtain the message records when the third-party platform and the first client interact with each other.

[0160] After configuration, triggering the authorization control 601 will authorize the installation of the customer service component, thus connecting the customer service function between the third-party platform and the first client.

[0161] In some embodiments, the entity to be registered is an enterprise, and all internal personnel of the enterprise have registered accounts on the first client. These accounts are all registered accounts. Only some registered accounts with authorized installation permissions can agree to access the customer service component in the first client. Therefore, before configuring the authorization permission information through the component authorization interface, it is necessary to verify the registered accounts that trigger the sharing information.

[0162] Indicative, such as Figure 7 As shown, Figure 7 This is a diagram illustrating the permission verification process for a new account.

[0163] The process 700 is as follows: Taking the second account as an example, when the second account triggers the sharing of information, the first client will first determine the on / off status of the third-party member authorization switch.

[0164] Specifically, for enterprises that are the entities that register, in terms of customer service management, the employees within the entity are divided into super administrators, customer service application managers, and ordinary employees.

[0165] Third-party members refer to the customer service application manager and ordinary employees within the registered entity. The super administrator has the authority to manage all employee accounts, the customer service application manager has the authority to manage all customer service employee accounts, and ordinary employees only have the authority to manage their own accounts.

[0166] When the third-party member authorization switch is off, it means that third-party members do not have permission to authorize the installation of the customer service component. Only the super administrator account can authorize it. When a third-party member account triggers the sharing of information, a permission-invalid prompt page will be displayed.

[0167] When the third-party member authorization switch is turned on, it means that third-party members have partial permissions to access customer service functions.

[0168] If the sharing information is triggered by a super administrator account or a customer service application manager account, then the installation of customer service components can be directly authorized. At the same time, the following permissions are also granted: to view all customer service component access records of the registered account in the first client, and to revoke the authorization of access for customer service components that have already been authorized.

[0169] If the account that triggers the sharing of information is a regular employee account, the first client will determine whether the customer service component allows regular employees to create and manage accounts.

[0170] If permitted, the following situations apply.

[0171] 1.1 Regular employees can only authorize access to the customer service components through the customer service accounts they created, and can only view and manage the access results of the customer service components through their own created customer service accounts. Access to the customer service components here refers to whether the functions of the customer service components can be successfully invoked.

[0172] 1.2 When granting a new license, the default option is the customer service account you created. If you try to change it, a pop-up error message will appear: "Only the customer service account you created can be authorized."

[0173] If you do not have a customer service account that you created, when you receive the prompt to select an account and launch the JSAPI page, a pop-up window will appear saying: "Only the account you created can be authorized to access. You can complete the access after creating an account."

[0174] JSAPI stands for JavaScript Application Programming Interface. A JSAPI page is a page generated or opened by calling the relevant interface through JavaScript code.

[0175] 1.3 If an existing customer service account has been connected to the customer service component, the connection result viewing control on the page will be triggered. Only the customer service account created by the user can be viewed, and the user can choose to cancel the connection of their own customer service account. In some embodiments, if the current customer service account is the only account of the registered entity connected to the customer service component in the first client, canceling the connection will sever the authorization between the registered entity and the third-party platform.

[0176] If a customer service account created by a regular employee is not connected at this time, the account will be automatically selected, triggering the confirmation control to complete the connection.

[0177] If not allowed, the following situations apply.

[0178] 2.1 Regular employees cannot grant new authorizations, that is, they cannot create new customer service accounts to access the customer service component. In this case, a permission-free message page will be displayed.

[0179] 2.2 If the customer service account created by the ordinary employee has been connected to the customer service component, even if the access management control is triggered, the employee will not have permission to control the access status of the customer service account. In this case, a permission-unavailable prompt page will be displayed, and the employee will need to contact the super administrator for operation.

[0180] Once an account authorizes the installation of the customer service component within the first client, a corresponding storage information for the component will be generated within the first client. This customer service component operates as an application in the workbench, but its app-flag (application tag) is set to invisible in the workbench. In other words, the application information for the customer service component will not be displayed in the workbench, but the account can still use its services.

[0181] Indicative, such as Figure 8 As shown, Figure 8 This is a diagram illustrating how visible labels on a workbench affect the results of component deployment.

[0182] The first client will trigger the application refresh event 800 on the workbench at a preset frequency, requesting the latest application information from the backend. The backend CGI (Common Gateway Interface) will check the visibility tag of the workbench application. If the visibility tag indicates that the application is visible, the application will be sent; if the visibility tag indicates that the application is not visible, the application will not be sent. The first client will filter customer service component applications based on the app-flag of the customer service component.

[0183] Step 523: Once authorization is complete, the customer service component receives customer service messages transmitted from the third-party platform within the first client.

[0184] In some embodiments, after an enterprise authorizes the installation of the customer service component, it provides the customer service component with the enterprise's registration identifier on the third-party platform. This registration identifier uniquely identifies the enterprise on the third-party platform, ensuring that messages transmitted from the third-party platform to the first client only originate from messages initiated by third-party platform users to the registered entity. This prevents customer service messages received by other registered entities on the third-party platform from being transmitted to the current registered entity's registration account on the first client.

[0185] For example, there is a first enterprise that has joined a third-party platform. The customer service account of the first enterprise on the third-party platform is service1, and the customer service account of the first enterprise on the first client is service2. When a user sends an inquiry message to service1 on the third-party platform, the customer service component will pass the message to service2, and the customer service personnel will respond and process it through service2.

[0186] In summary, the customer service function invocation method provided in this embodiment can realize the transmission of customer service messages between different platforms through the customer service component. It establishes a customer service channel between the first client and the third-party platform without the need to develop third-party applications. After the customer service component is created, the entities registered on the third-party platform can freely call the customer service function by sharing information, thereby improving the processing efficiency of customer service messages.

[0187] Figure 9 This is a flowchart of a configuration method for a customer service function provided in another exemplary embodiment of this application, executed by a first client. The method includes the following steps.

[0188] Step 910: In response to receiving a component creation operation, display the component creation interface.

[0189] The component creation interface is used to configure the component parameters of the customer service component.

[0190] The component creation interface is used to configure the component parameters of the customer service component. The component creation interface contains multiple component parameter display areas, which are used to configure different types of component parameters.

[0191] For example, component parameters include the following: protection information parameters, platform information parameters, component permission parameters, and development parameters.

[0192] Step 920: Display at least two candidate scenarios in the component creation interface.

[0193] Among them, at least two candidate scenarios are pre-provided scenarios that support the creation of customer service components. The candidate scenarios include at least two of the following: client scenario, mini-program scenario, and webpage scenario.

[0194] At least two candidate scenarios indicate that the type of third-party platform can be any type among clients, mini-programs, and web pages.

[0195] Step 930: Receive the selection operation for the first scenario among at least two candidate scenarios.

[0196] The first scenario can be any of the following: a client application, a mini-program, or a webpage. Receiving a selection action for the first scenario indicates that the customer service component has been created and is used to implement message interaction between the first client application and the first scenario.

[0197] Step 940: Receive the platform identifier input operation for the third-party platform in the component creation interface.

[0198] The platform identifier input operation is used to input the platform identifier of a third-party platform. The platform identifier of a third-party platform is used to uniquely identify the identity of the third-party platform. The component creation interface includes a platform identifier input area for entering the platform identifier.

[0199] The platform identifier input area receives the platform name input and yields the platform identifier of the third-party platform. This platform identifier is a component of the platform information parameters.

[0200] It is worth noting that the execution order of steps 930 and 940 can be arbitrary; step 930 can be executed first and then step 940, or step 940 can be executed first and then step 930.

[0201] Step 951: In the case that the first scenario is a client scenario, determine the matching relationship between the platform identifier and the entity that created the customer service component.

[0202] That is, to determine whether the entity currently creating the customer service component is the same entity as the third-party platform indicated by the platform identifier.

[0203] For example, authentication information of a third-party platform is obtained based on the platform identifier and the scenario type of the first scenario. This authentication information is obtained by the third-party platform after identity authentication within the relevant authentication platform, and it indicates the identity and entity of the third-party platform. Authentication information of the third-party platform within the relevant authentication platform can be obtained with authorization.

[0204] In other words, the first client obtains the third-party platform's authentication information from the relevant authentication platform after obtaining authorization from the third-party platform.

[0205] The third-party platform also has authentication information logged in within the first client and has registered an account. The system can determine whether the current account belongs to the third-party platform or is an account authorized by the third-party platform to complete the main body authentication.

[0206] Step 952: In the case of the first scenario being a mini-program scenario, determine the matching relationship between the platform identifier and the entity that creates the customer service component.

[0207] Refer to step 951; it will not be repeated here.

[0208] Step 953: In the case of the first scenario being a webpage scenario, determine the matching relationship between the platform identifier and the entity that created the customer service component.

[0209] Refer to step 951; it will not be repeated here.

[0210] The execution order of steps 951, 952, and 953 can be arbitrary. For example, step 951 can be executed first, then step 952, and finally step 953. At least one of steps 951, 952, and 953 is executed.

[0211] Step 961: If the third-party platform corresponding to the matching relationship indicator platform meets the subject requirements of the first scenario, receive the component permission configuration operation in the component creation interface.

[0212] The component permission configuration operation is used to configure the component permission parameters of the customer service component. The component permission parameters describe the permissions that the customer service component has and the information of the enterprise that the customer service component serves. Among them, the permission that the customer service component has is to manage customer service accounts within third-party platforms.

[0213] Step 962: If the third-party platform corresponding to the matching relationship indicator platform does not meet the subject requirements of the first scenario, display an error message and end the process.

[0214] The error message indicates that the account holder currently creating the customer service component does not match the entity holder of the third-party platform corresponding to the platform identifier.

[0215] Step 970: Receive callback input from the component creation interface and obtain callback information.

[0216] The callback information is used to indicate the message sending and receiving addresses when the third-party platform and the first client interact with each other.

[0217] For example, you can receive input to the callback information input area in the component creation interface and obtain the callback information.

[0218] Step 980: Verify the callback information and obtain the verification result.

[0219] The verification result is used to indicate the sending and receiving capabilities corresponding to the sending and receiving addresses of the candidate callback information.

[0220] For example, the first client sends a test message to the information receiving and receiving address indicated by the candidate callback information. The test message contains at least two parameters and information such as parameter encryption methods. In other words, the test message indicates the method of obtaining the verification message.

[0221] When the server corresponding to the information sending and receiving address indicated by the callback information receives the test message, it generates a verification message based on the test message and returns it to the first client through the information sending and receiving address.

[0222] Step 991: If the verification result indicates that the callback information meets the information sending and receiving address requirements, create the customer service component and display a success message.

[0223] The preset information sending and receiving address requirement refers to the match between the verification message returned by the information sending and receiving address and the result of encryption based on the parameters indicated by the first client.

[0224] Step 992: If the verification result indicates that the callback information does not meet the information sending and receiving address requirements, display an error message and end the process.

[0225] If the verification result indicates that the callback information does not meet the requirements of the message sending and receiving address, it means that the message sending and receiving address does not have the ability to accurately transmit messages. Therefore, the callback information cannot be used to create a customer service component. In this case, an error message is displayed to prompt modification of the callback information. When an update operation for the callback information is received, the first client automatically verifies the callback information based on the updated information until the verification result indicates success, at which point the customer service component can be successfully created.

[0226] The first client provides a rich set of APIs for service providers to use. After the customer service component is created, the service provider can develop other functions based on the APIs. Meeting the needs of enterprises to expand customer service functions It includes, but is not limited to, at least one of the following functions.

[0227] 1. Customer Service Account Management: Add customer service accounts, delete customer service accounts, modify customer service accounts, get a list of customer service accounts, get customer service account links, etc.

[0228] 2. Receptionist Management: Add receptionist information, delete receptionist information, and retrieve the receptionist list;

[0229] 3. Session allocation and message sending / receiving: Allocate customer service sessions, receive messages and events, send messages, and send event response messages such as welcome messages;

[0230] 4. Upgrade service configuration: Obtain the assigned specialists and customer groups (service targets), upgrade the service level provided to customers, and remove some recommended content for customers;

[0231] 5. Obtain basic customer information;

[0232] 6. Statistical Management: Obtain summary enterprise data after statistical analysis of customer data, and obtain detailed data of reception staff;

[0233] 7. Robot Management: Knowledge base group management, knowledge base question and answer management, etc.

[0234] In summary, the customer service configuration method provided in this application, by creating a customer service component through a receiving component creation operation, can establish a customer service channel between the first client and a third-party platform without the need to develop third-party applications. This enables the transmission of customer service messages, reduces the workload for service providers developing third-party applications, improves the efficiency of establishing customer service channels, and eliminates the maintenance costs of third-party applications. Synchronizing customer service messages received from the third-party platform to the first client facilitates timely processing of customer service messages by customer service personnel, improving message processing efficiency. Configuring the parameters of the customer service component during its creation to determine the information of the third-party platform with which the first client needs to establish a customer service channel allows users to customize the settings at both ends of the channel.

[0235] Figure 10 This is a structural block diagram of a configuration device for a customer service function provided in an exemplary embodiment of this application, such as... Figure 10 As shown, the device includes the following parts.

[0236] The creation module 1010 is used to receive a component creation operation in the first client. The component creation operation is used to create a customer service component. The customer service component is used to establish a customer service channel between the first client and a third-party platform. The customer service channel is used to synchronize customer service messages received in the third-party platform to the first client.

[0237] Display module 1020 is used to display a component creation interface in response to the component creation operation. The component creation interface is used to configure the component parameters of the customer service component.

[0238] The configuration module 1030 is used to receive configuration operations on the component parameters in the component creation interface, wherein the component parameters include platform information corresponding to the third-party platform;

[0239] The creation module 1010 is also used to create a customer service component between the first client and the third-party platform based on the component parameters.

[0240] In an optional embodiment, the configuration module 1030 is further configured to receive a platform identifier input operation for the third-party platform in the component creation interface; and to receive a protection information input operation in the component creation interface, wherein the protection information is protection information pre-generated in the first client corresponding to the third-party platform.

[0241] In an optional embodiment, the configuration module 1030 is further configured to display at least two candidate scenarios, which are pre-provided scenarios that support the creation of the customer service component. The candidate scenarios include at least two of the following: client scenario, mini-program scenario, and webpage scenario. In response to receiving a selection operation for a first scenario among the at least two candidate scenarios, the selection operation is used as a configuration operation for the component parameters.

[0242] In an optional embodiment, the creation module 1010 is further configured to determine the matching relationship between the platform identifier and the entity that creates the customer service component; and, if the matching relationship indicates that the third-party platform corresponding to the platform identifier and the entity that creates the customer service component meet preset entity requirements, create the customer service component between the first client and the third-party platform based on the component parameters.

[0243] In an optional embodiment, the configuration module 1030 is further configured to receive an input operation for the platform name of the third-party platform in the component creation interface; or, to receive an upload operation for a screenshot of the interface of the third-party platform in the component creation interface.

[0244] In an optional embodiment, the configuration module 1030 is further configured to receive a callback input operation in the component creation interface and obtain callback information, wherein the callback information is used to indicate the information sending and receiving address when the third-party platform and the first client perform message interaction.

[0245] In an optional embodiment, the configuration module 1030 is further configured to receive an input operation on the callback information input area in the component creation interface to obtain candidate callback information; verify the candidate callback information to obtain a verification result, the verification result being used to indicate the send / receive capability corresponding to the information send / receive address of the candidate callback information; and, if the verification result indicates that the candidate callback information meets the information send / receive address requirements, determine the candidate callback information as the callback information.

[0246] In an optional embodiment, such as Figure 11 As shown, the device further includes:

[0247] The sharing module 1040 is used to generate sharing information corresponding to the customer service component in response to receiving a sharing operation on the customer service component. The sharing information is used to share the creation interface of the customer service component with the registered account of the third-party platform. The sharing information includes at least one of a sharing link and a sharing graphic code. The registered account is the account of the registered entity registered on the third-party platform in the first client.

[0248] In summary, the customer service configuration device provided in this application creates customer service components through a component creation operation. This enables the establishment of a customer service channel between the first client and a third-party platform without the need for third-party application development. This facilitates customer service message transmission, reduces the workload for service providers developing third-party applications, improves the efficiency of establishing customer service channels, and eliminates the maintenance costs associated with third-party applications. Synchronizing customer service messages received from the third-party platform to the first client facilitates timely processing of customer service messages by customer service personnel, improving message processing efficiency. Configuring the parameters of the customer service component during its creation to determine the information of the third-party platform with which the first client needs to establish a customer service channel allows users to customize the settings at both ends of the channel.

[0249] It should be noted that the customer service function configuration device provided in the above embodiments is only an example of the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the customer service function configuration device and the customer service function configuration method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

[0250] Figure 12 This illustration shows a structural block diagram of a computer device 1200 provided in an exemplary embodiment of this application. The computer device 1200 may be a smartphone, tablet computer, Moving Picture Experts Group Audio Layer III (MP3) player, Moving Picture Experts Group Audio Layer IV (MP4) player, laptop computer, or desktop computer. The computer device 1200 may also be referred to as a user device, portable terminal, laptop terminal, desktop terminal, or other names.

[0251] Typically, computer device 1200 includes a processor 1201 and a memory 1202.

[0252] Processor 1201 may include one or more processing cores, such as a quad-core processor, an octa-core processor, etc. Processor 1201 may be implemented using at least one hardware form selected from Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). Processor 1201 may also include a main processor and a coprocessor. The main processor, also known as a Central Processing Unit (CPU), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, processor 1201 may integrate a Graphics Processing Unit (GPU), which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, processor 1201 may also include an Artificial Intelligence (AI) processor, which is used to handle computational operations related to machine learning.

[0253] The memory 1202 may include one or more computer-readable storage media, which may be non-transitory. The memory 1202 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In some embodiments, the non-transitory computer-readable storage media in the memory 1202 are used to store at least one instruction, which is executed by the processor 1201 to implement the configuration method for the client service function provided in the method embodiments of this application.

[0254] In some embodiments, the computer device 1200 also includes other components 1203, the type and number of which can be selected based on the functional needs of the computer device 1200. Those skilled in the art will understand that... Figure 12 The structure shown does not constitute a limitation on the computer device 1200 and may include more or fewer components than shown, or combine certain components, or use different component arrangements.

[0255] Optionally, the computer-readable storage medium may include: read-only memory (ROM), random access memory (RAM), solid-state drives (SSDs), or optical discs, etc. The random access memory may include resistive random access memory (ReRAM) and dynamic random access memory (DRAM). The sequence numbers of the embodiments in this application are merely descriptive and do not represent the superiority or inferiority of the embodiments.

[0256] This application also provides a computer device, which includes a processor and a memory. The memory stores at least one instruction, at least one program, a code set, or an instruction set. The at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by the processor to implement the configuration method for customer service functions as described in any of the above embodiments of this application.

[0257] This application also provides a computer-readable storage medium storing at least one instruction, at least one program, code set, or instruction set, wherein the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by a processor to implement a configuration method for customer service functions as described in any of the above embodiments of this application.

[0258] This application also provides a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the configuration method for the customer service function described in any of the above embodiments.

[0259] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0260] The above description is merely an optional embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for configuring a customer service function, characterized in that, The method includes: The system receives a component creation operation in the first client. The component creation operation is used to create a customer service component. The customer service component is used to establish a customer service channel between the first client and a third-party platform. The customer service channel is used to synchronize customer service messages received in the third-party platform to the first client. In response to the component creation operation, a component creation interface is displayed, which is used to configure the component parameters of the customer service component; The component parameter configuration operation is received in the component creation interface, and the component parameter includes platform information corresponding to the third-party platform. A customer service component is created between the first client and the third-party platform based on the component parameters.

2. The method according to claim 1, characterized in that, The receiving of configuration operations for the component parameters in the component creation interface includes: Receive the platform identifier input operation for the third-party platform in the component creation interface; The system receives protection information input from the component creation interface. The protection information is protection information pre-generated in the first client that corresponds to the third-party platform.

3. The method according to claim 2, characterized in that, The receiving of configuration operations for the component parameters in the component creation interface includes: Display at least two candidate scenarios, which are pre-provided scenarios that support the creation of the customer service component. The candidate scenarios include at least two of the following: client scenario, mini-program scenario, and webpage scenario. In response to receiving a selection operation for a first scenario among the at least two candidate scenarios, the selection operation is used as a configuration operation for the component parameters.

4. The method according to claim 3, characterized in that, The step of creating a customer service component between the first client and the third-party platform based on the component parameters includes: Determine the matching relationship between the platform identifier and the entity that created the customer service component; If the matching relationship indicates that the third-party platform corresponding to the platform identifier and the entity that created the customer service component meet the preset entity requirements, the customer service component between the first client and the third-party platform is created based on the component parameters.

5. The method according to claim 1, characterized in that, The receiving of configuration operations for the component parameters in the component creation interface includes: Receive the input of the platform name of the third-party platform in the component creation interface; or, Receive screenshot uploads of the third-party platform's interface from the component creation interface.

6. The method according to claim 1, characterized in that, The receiving of configuration operations for the component parameters in the component creation interface includes: The system receives a callback input operation in the component creation interface and obtains callback information. The callback information is used to indicate the information sending and receiving addresses when the third-party platform and the first client interact with each other.

7. The method according to claim 6, characterized in that, The step of receiving callback input operations in the component creation interface and obtaining callback information includes: Receive input operations on the callback information input area in the component creation interface, and obtain candidate callback information; The candidate callback information is verified to obtain a verification result, which is used to indicate the send / receive capability corresponding to the send / receive address of the candidate callback information. If the verification result indicates that the candidate callback information meets the information sending and receiving address requirements, the candidate callback information is determined as the callback information.

8. The method according to any one of claims 1 to 7, characterized in that, After creating the customer service component between the first client and the third-party platform based on the component parameters, the method further includes: In response to receiving a sharing operation for the customer service component, sharing information corresponding to the customer service component is generated. The sharing information is used to share the creation interface of the customer service component with the registered account of the third-party platform. The sharing information includes at least one of a sharing link and a sharing graphic code. The registered account is the account of the registered entity registered on the third-party platform in the first client.

9. A configuration device for customer service functions, characterized in that, The device includes: A creation module is used to receive a component creation operation in a first client. The component creation operation is used to create a customer service component. The customer service component is used to establish a customer service channel between the first client and a third-party platform. The customer service channel is used to synchronize customer service messages received from the third-party platform to the first client. The display module is used to display the component creation interface in response to the component creation operation. The component creation interface is used to configure the component parameters of the customer service component. A configuration module is used to receive configuration operations for the component parameters in the component creation interface, wherein the component parameters include platform information corresponding to the third-party platform; The creation module is also used to create a customer service component between the first client and the third-party platform based on the component parameters.

10. A computer device, characterized in that, The computer device includes a processor and a memory, the memory storing at least one program, which is loaded and executed by the processor to implement the configuration method for the customer service function as described in any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that, The storage medium stores at least one program segment, which is loaded and executed by a processor to implement the configuration method for the customer service function as described in any one of claims 1 to 8.

12. A computer program product, characterized in that, Includes a computer program, which, when executed by a processor, implements a configuration method for the customer service function as described in any one of claims 1 to 8.

Images