CN116562569A

CN116562569A - Task management method and related device

Info

Publication number: CN116562569A
Application number: CN202310528847.6A
Authority: CN
Inventors: 吴经胜; 雷国华
Original assignee: Shenzhen Suyuan Technology Co ltd
Current assignee: Shenzhen Suyuan Technology Co ltd
Priority date: 2023-05-10
Filing date: 2023-05-10
Publication date: 2023-08-08

Abstract

The embodiment of the application provides a task management method and a related device. In the method, the server can determine that the supplier has a requirement of issuing the task to the agent according to the information of the supplier and/or the agent, so as to remind the supplier of issuing the task. And, the server may also recommend task content to the provider device, which may include execution agents for the tasks, task amounts, and the like. By implementing the technical scheme provided by the application, the provider equipment can manage one or more agents of the provider equipment more conveniently. And, the provider equipment can acquire the recommendation information of the server, help the provider to issue tasks at the same time, select a proper agent to execute tasks, determine proper task quantity for the agent, and the like. In this way, the provider may reduce its decision making errors and better manage its agent or agents.

Description

Task management method and related device

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a task management method and a related device.

Background

The materials designed or manufactured by the suppliers may be authorized for distribution to the agencies. The agent needs to assist the vendor in the development of clients, maintenance of client relationships, etc. Since the agent information and the client information are fragmented, it is difficult for the provider to issue appropriate task contents according to the situation of each agent when issuing tasks to the agent.

Disclosure of Invention

The application provides a task management method and a related device. The server may determine, according to information of the provider and/or the agent, a requirement of the provider to issue the task, and then send a reminder to the provider device to issue the task. And the server can also send the task content to the provider equipment, recommend the task executor and/or the task amount to the provider, and help the provider to issue the task more reasonably according to the condition of the agent.

In a first aspect, the present application provides a task management method applied to a communication system, the communication system may include a provider device, a server, and an agent device, the provider device being associated with a first provider, the agent device being associated with a first agent, the method comprising: the server determines the content of the first task according to the information of the first provider and the information of the first agent; the server sends a first message to the provider equipment, wherein the first message is used for prompting the provider equipment to issue a first task to the agent equipment; the provider equipment displays the content of the first task according to the first message, receives a first operation, and the first operation is used for issuing a second task to the first agent equipment; in response to the first operation, the provider device sends a second message to the agent device through the server, the second message being for the provider device to issue a second task to the agent device, the second message containing content of the second task; the agent device displays the content of the second task according to the second message.

It will be appreciated that the server may recommend task content for a first vendor associated with the vendor device when the vendor device issues tasks to the agent device. The recommended content may include the executing agent of the task and/or the amount of the task of the executing agent. Wherein the task content recommended by the server may be determined by the server based on vendor information and/or agent information. Therefore, the provider can issue the task to the agent by referring to the task content recommended by the server, and the problem that the task content issued by the provider is unreasonable due to the fact that the provider ignores the provider or the agent in some cases when issuing the task is avoided.

With reference to the first aspect, in some embodiments, before the server determines the content of the first task according to the information of the first provider and the information of the first agent, the method further includes: the server determines first demand information according to the information of the first provider and/or the information of the first agent, and the server sends the first demand information to provider equipment, wherein the first demand information is used for indicating that the first provider has a demand for issuing a first type of task; or the server receives a first request sent by the provider equipment, wherein the first request is used for the first provider to issue a first type of task to the first agent; the first task and the second task are of a first type.

It will be appreciated that the server may determine that the vendor is in need of issuing a certain type of task based on the vendor's information and/or the agent's information. In this way, the server may recommend to the vendor to publish the type of task and recommend the content of the task and/or the executor of the task. Alternatively, the provider device may respond to a request from the user to issue the task of the type, and the server may recommend the task content for the provider device.

With reference to the first aspect, in some embodiments, the server stores representations of one or more clients of M members of the first agent, M being a positive integer, the method further comprising: the server determines first allocation information of the second task according to the portraits of one or more clients, wherein the first allocation information is used for indicating that the second task is allocated to N members of the first agent, N is a positive integer, and N is not more than M; the server transmits the first allocation information to the agent device.

It will be appreciated that after the vendor device issues a task to the agent device, the agent device may display the task content of the task. The server may also determine the N members that are more suitable for handling the task based on the representation of one or more clients of the agent member. The first agent, upon determining the members that complete the task, may refer to the N members determined by the server. Thus, the first agent can be distributed to more suitable members to complete tasks issued by the suppliers, and the task completion efficiency is improved.

In combination with the first aspect, in some embodiments, the type of the first task is a sales task, and the content of the first task includes a target amount of sales of one or more materials by the first agent.

With reference to the first aspect, in some embodiments, the one or more materials include a first material, and the server determines the content of the first task according to the information of the first provider and the information of the first agent, specifically including: the method comprises the steps that a server obtains a first demand of a first customer of a first agent for a first material in a first time period and a second demand of a second customer for the first material in the first time period, wherein the first customer is a customer using the first material, and the second customer is a customer using the first material to replace the material; the server predicts a third demand of the first customer for the first material in the second time period through linear regression according to the first demand, and predicts a fourth demand of the second customer for the first material in the second time period through linear regression according to the second demand; the server determines a target quantity of the first material sold by the first agent according to the third demand and the fourth demand.

With reference to the first aspect, in some embodiments, the determining, by the server, the first requirement according to information of the first provider and/or information of the first agent specifically includes: the server determines that the storage time of the one or more materials exceeds a third time length; the server determines a first demand indicating that a first vendor has a demand to sell one or more materials.

It will be appreciated that the server may determine that the supplier has a need to sell backlog material based on information such as the supplier's inventory. Further, the server may predict the amount of the one or more materials sold by the vendor's agent. Further, the server may send the forecast results to the suppliers, helping the suppliers select agents to sell backlog material, and the number of sales.

In combination with the first aspect, in some embodiments, the type of the first task is a client development task, and the content of the first task includes instructions for the first agent to develop a specified client, or the content of the first task includes instructions for the first agent to develop a first number of clients.

In combination with the first aspect, in some embodiments, the type of the first task assigns a task to the client, and the content of the first task includes instructions that instruct the first agent to dock with one or more clients.

The server may determine that a new material is newly released or about to be released, or the server may determine that a certain material sales amount or sales number is smaller, and further determine that a vendor has a need to develop a client type. In this way, the server may recommend the appropriate agent to the vendor.

In combination with the first aspect, in some embodiments, the first task is of the type that follows the customer task, and the content of the first task includes information that instructs the first agent to report the pre-sale service and/or the after-sale service.

Wherein the server may obtain customer ratings of the first agent over a third period of time. Wherein the customer rating may be an average score of the customer by the first agent over a third time period. Alternatively, the customer rating may be determined from a customer's rating statement for the first agent. The server may determine that when the customer rating of the first agent is low, the first provider has a task requirement to issue a timely follow-up customer to the first agent and report a record to the first provider. The server may also determine a frequency with which the first agent reports records to the first vendor based on the customer rating. In this way, the server can help the provider to know the pre-sale after-sale service condition of the agent in time.

In a second aspect, the present application provides a task management method applied to a communication system, where the communication system may include a vendor device, a server, and an agent device, where the vendor device is associated with a first vendor, and the agent device is associated with a first agent, the method including: the method comprises the steps that a provider device receives a first message, wherein the first message is used for prompting the provider device to issue a first task to an agent device, and the first task is determined by a server according to information of a first provider and information of the first agent; the provider equipment receives the first message and displays the content of the first task according to the first message; the provider device receiving a first operation for issuing a second task to the first agent device; the provider device sends a second message to the agent device through the server, the second message being for the provider device to issue a second task to the agent device, the second message containing the content of the second task.

With reference to the second aspect, in some embodiments, before the provider device receives the first message, the method further includes: the provider device receives first demand information indicating that a first provider has a demand to issue a first type of task. The vendor device sends a first request to the server, the first request being for instructing the first vendor to issue a demand for a first type of task to the first agent.

With reference to the second aspect, in some embodiments, the type of the first task is a sales task, and the content of the first task includes a target amount of sales of one or more materials by the first agent. Alternatively, the type of first task is a client development task, and the content of the first task includes instructions for the first agent to develop a specified client or instructions for the first agent to develop a first number of clients. Alternatively, the type of first task assigns a task to the customer, and the content of the first task includes instructions to the first agent to dock one or more customers. Alternatively, the first task is of the type that follows the customer task, and the content of the first task includes information that instructs the first agent to report the pre-sale and/or after-sale services.

In a third aspect, the present application provides a task management method applied to a communication system, the communication system may include a vendor device, a server, and an agent device, wherein the vendor device is associated with a first vendor, and the agent device is associated with a first agent, the method comprising: the server sends a first message to the provider equipment, wherein the first message is used for prompting the provider equipment to issue a first task to the agent equipment; the server determines the content of the first task according to the information of the first provider and the information of the first agent; the server receives a second message sent by the provider equipment and sends the second message to the agent equipment, wherein the second message is used for the provider equipment to issue a second task to the agent equipment, and the second message contains the content of the second task.

With reference to the third aspect, in some embodiments, before the server determines the content of the first task according to the information of the first provider and the information of the first agent, the method further includes: the server determines first demand information according to the information of the first provider and/or the information of the first agent, and the server sends the first demand information to provider equipment, wherein the first demand information is used for indicating that the first provider has a demand for issuing a first type of task; or the server receives a first request sent by the provider equipment, wherein the first request is used for indicating the first provider to issue the requirement of the first type of task to the first agent, and the types of the first task and the second task are the first type.

With reference to the third aspect, in some embodiments, the server may store representations of one or more clients of M members of the first agent, where M is a positive integer. The method further comprises the steps of: the server determines first allocation information of the second task according to member portraits of one or more clients, the first allocation information being used for indicating that the second task is allocated to one or more N members of the first agent, N being a positive integer, N not exceeding M. The server transmits the first allocation information to the agent device.

With reference to the third aspect, in some embodiments, the type of the first task is a sales task, and the content of the first task includes a target amount of sales of one or more materials by the first agent. Optionally, the server determines the content of the first task according to the information of the first provider and the information of the first agent, and specifically includes: the method comprises the steps that a server obtains a first demand of a first customer of a first agent for a first material in a first time period and a second demand of a second customer for the first material in the first time period, wherein the first customer is a customer using the first material, and the second customer is a customer using the first material to replace the material; the server predicts a third demand of the first customer for the first material in the second time period through linear regression according to the first demand, and predicts a fourth demand of the second customer for the first material in the second time period through linear regression according to the second demand; the server determines a target quantity of the first material sold by the first agent according to the third demand and the fourth demand.

With reference to the third aspect, in some embodiments, the server determines the first requirement information according to information of the first provider and/or information of the first agent, and specifically includes: the server determines that the storage time of the one or more materials exceeds a third time length; the server determines a first demand indicating that a first vendor has a demand to sell one or more materials.

With reference to the third aspect, in some embodiments, the type of the first task is a client development task, and the content of the first task includes instructions to the first agent to develop a specified client or instructions to the first agent to develop a first number of clients. Alternatively, the type of first task assigns a task to the customer, and the content of the first task includes instructions to the first agent to dock one or more customers. Alternatively, the first task is of the type that follows the customer task, and the content of the first task includes information that instructs the first agent to report the pre-sale and/or after-sale services.

In a fourth aspect, the present application provides a task management method applied to a communication system, the communication system may include a provider device, a server, and an agent device, wherein the provider device is associated with a first provider, and the agent device is associated with a first agent, the method comprising: the agent equipment receives a second message, wherein the second message is used for the provider equipment to issue a second task to the agent equipment, the second message comprises the content of the second task, the second task can be determined by the provider equipment according to the first task, and the first task can be determined by the server according to the information of the first provider and/or the information of the first agent; the agent device displays the content of the second task according to the second message.

With reference to the fourth aspect, in some embodiments, the method further comprises: the agent equipment receives first allocation information, wherein the first allocation information is used for indicating that a second task is allocated to one or more N members of the first agent, N is a positive integer, and N does not exceed M; the agent device may also display the first allocation information.

In a fifth aspect, the present application provides an electronic device, the electronic device comprising: the device comprises a display screen, a memory and a processor coupled to the memory. The display screen is used for displaying an interface, and the memory stores computer executable instructions. The processor, when executing computer-executable instructions, causes the electronic device to implement any one of the possible implementations of the second or fourth aspects described above.

In a sixth aspect, the present application provides a computer-readable storage medium. The computer-readable storage medium includes instructions. The instructions, when executed on a device, cause the device to implement any one of the possible implementations of the second or third or fourth aspects described above.

In a seventh aspect, embodiments of the present application provide a chip. The chip is applied to electronic equipment. The chip includes one or more processors. The processor is configured to invoke computer instructions to cause the electronic device to perform any of the possible implementations of the second aspect or the third aspect or the fourth aspect described above.

In an eighth aspect, embodiments of the present application provide a computer program product comprising instructions that, when run on a device, cause the electronic device to perform any one of the possible implementations of the second aspect, the third aspect, or the fourth aspect.

In a ninth aspect, embodiments of the present application provide a communication system including a vendor device, an agent device, and a server. The vendor device is adapted to perform any one of the possible implementations of the second aspect. The server is adapted to perform any one of the possible implementations of the third aspect. The agent device is adapted to perform any one of the possible implementations of the fourth aspect.

It can be appreciated that the solutions provided in the second aspect to the ninth aspect are used to implement or cooperate to implement the method provided in the first aspect correspondingly, so that the same or corresponding beneficial effects as those of the method corresponding to the first aspect can be achieved, and no further description is given here.

Drawings

FIGS. 1A-1C are schematic diagrams of the architecture of some of the communication systems provided herein;

FIG. 2 is a schematic diagram of an interaction flow for a vendor device to issue tasks to an agent device according to an embodiment of the present application;

3A-3E are schematic diagrams of scenarios in which some vendor devices issue sales tasks to agent devices provided in embodiments of the present application;

FIG. 4 is a schematic diagram of a vendor device according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of a server according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of an agent device according to an embodiment of the present application.

Detailed Description

The terminology used in the following embodiments of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the specification and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms as well, unless the context clearly indicates to the contrary. It should also be understood that the term "and/or" as used in this application refers to and encompasses any or all possible combinations of one or more of the listed items.

The terms "first," "second," and the like, are used below for descriptive purposes only and are not to be construed as implying or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature, and in the description of embodiments of the present application, unless otherwise indicated, the meaning of "a plurality" is two or more.

The architecture of some communication systems provided in the embodiments of the present application is described below.

As shown in fig. 1A, fig. 1A schematically illustrates an architecture of a communication system 10 provided herein.

Communication system 10 may include: a provider device 101, a first server 102 and an agent device 103.

The provider device 101 may log in to the provider account on the first server 102. In embodiments of the present application, the provider device 101 logging into the provider account may also be referred to as the provider device being associated with the provider. The provider device 101 may be associated with a first provider. Not limited to associating provider devices 101, the first provider may associate more devices, and the number of devices that the first provider may associate is not limited in the embodiments of the present application.

The agent device 103 may log in an agent account on the first server 102. In the embodiment of the application, when the agent account logs on to the agent device, the agent device may be referred to as being associated with the agent. The agent device 103 may be associated with a first agent. Not limited to associating agent devices 103, the first agent may associate more devices, and the number of devices that the first agent may associate is not limited in the embodiments of the present application.

It should be noted that the vendor device 101 and the agent device 103 may be a mobile phone, a tablet computer, a desktop, a laptop, a notebook, an Ultra-mobile Personal Computer (UMPC), a handheld computer, a netbook, or the like. The present application does not limit the device types of the vendor device 101 and the agent device 103.

The first server 102 may log in with one or more accounts of the first vendor, and one or more accounts of the first agent. The provider device 101 and the agent device 103 may interact with data through a first server. The first server 102 may provide the functionality for the provider device 101 to issue tasks to the agent device 103.

It should be noted that the first provider may be bound to one or more accounts, which may correspond to one or more members (e.g., employees) of the first provider. The first agent may also be bound to one or more accounts, which may correspond to one or more members (e.g., employees) of the first agent. For ease of description and better understanding, the subsequent embodiments of the present application describe the task management method provided in the embodiments of the present application by taking as an example that a first vendor logs on to one of the accounts of the vendor device 101 and a first agent logs on to one of the accounts of the agent device 103.

As shown in fig. 1B, fig. 1B schematically illustrates an architecture of another communication system 20 provided herein.

Communication system 20 may include: a vendor device 101, an agent device 103, a second server 104 and a third server 105.

The provider device 101 may log in to the provider account on the second server 104. The agent device 103 may log in to the agent account on the third server 105.

The second server 104 may communicate with the provider device 101 and store data transmitted by the provider device 101. The third server 105 may be in communication with the agent device 103 and store data transmitted by the agent device 103. The second server 104 may communicate with and exchange data with the third server 105.

As shown in fig. 1C, fig. 1C schematically illustrates an architecture of a communication system 30 provided herein.

Communication system 30 may include, but is not limited to: a provider device 101 and a fourth server 106.

The provider device 101 may log in to the fourth server 106 an account of the first provider, or the provider device 101 may log in to the fourth server 106 an account of one or more agents.

The fourth server 106 may bind the first vendor with the account numbers of one or more agents. Thus, when the provider device 101 logs in the account of the first provider in the fourth server 106, the provider device 101 may switch the logged-in account to the account of the agent in the fourth server 106 in response to the user operation. In this way, when the communication system does not include the agent device, the first provider can directly log in the account number of the agent in the provider device 101, so as to further realize functions such as task viewing, task publishing, task progress reporting, and the like.

For ease of understanding and better presentation, the subsequent embodiments of the present application describe the product management method presented herein by way of example of communication system 10. It is understood that communication system 10 shown in fig. 1A, communication system 20 shown in fig. 1B, and communication system 30 shown in fig. 1C are by way of example only. More or fewer agent devices, vendor devices, and servers may be included in the communication system. And the communication system may also include provider devices associated with other providers. The communication connection manner of other agent devices, provider devices and servers in the communication system may refer to the communication connection manner of fig. 1A, 1B and 1C. The number of agent devices, provider devices, and servers in the communication system is not limited by the embodiments of the present application.

For ease of understanding and better presentation, the subsequent embodiments of the present application describe task management methods as examples of suppliers and agents in the semiconductor industry. Not limited to the semiconductor industry, but other industries are possible. The application does not limit the industry of the application of the task management method.

In some embodiments, the vendor device 101 needs to issue tasks to the agent device 103. The first server 102 may provide the recommendation of the task content to the provider device 101 according to information of the agent, customer information of the agent, etc., to help the provider device 101 issue the appropriate task content for the agent's situation.

Fig. 2 is an exemplary schematic diagram of an interaction flow of a vendor device issuing a task to an agent device according to an embodiment of the present application.

As shown in fig. 2, the method may include, but is not limited to, the following steps:

s201, the first server 102 determines first requirement information according to information of the first provider and/or information of the first agent, where the first requirement information is used to indicate that the first provider has a requirement of issuing a first task of a first type.

S202, the first server 102 transmits the first requirement information to the provider device 101.

The information of the first provider may include, but is not limited to, a stock amount of the first provider, a total sales amount of the first provider, sales amounts of one or more materials, and material distribution conditions during a certain period of time. Wherein the material may comprise all items other than the end product and related to the production of the end product. For example, the materials may include raw materials, semi-finished products, finished products. The material can be processed to produce the final product. The first agent's information may include, but is not limited to, one or more agents' inventory, sales, one or more sales, etc. over a period of time. The first type may be a task type after the task content is basically classified. For example, the first type may include a sales type, a development customer type, an information feedback type, a customer allocation type. Further, there may be one or more task content under the first type, e.g., the task content of the sales type may include selling a specified amount of material, selling a specified amount, and so forth.

In some embodiments, the first type may be a sales type and the first task may be a task of selling the specified material. Specifically, the first server 102 may obtain information of the first provider. The information of the first provider may include inventory information of the first provider. The inventory information of the first supplier may include a time of storage of one or more materials of the first supplier in the warehouse. The first server 102 may determine that a certain material backlog time in the warehouse exceeds a third length of time, and the first server 102 may send first demand information to the provider device 101, where the first demand information is used to instruct the first provider to issue a task of selling the backlog material. Wherein rule information for determining the requirements of the vendor's issuing task may be stored in the first server 102. The rule information may be stored in the first server 102 after the provider device 101 transmits to the first server 102, or may be stored in advance in the server. For example, the first server 102 may store first rule information indicating that the first requirement information is transmitted to the provider device 101 when the material storage time exceeds the third time length. The first demand content is used for prompting a first provider to issue a task of selling backlog materials.

In some embodiments, after receiving the first demand information, the provider device 101 may display the first demand content according to the first demand information. The first demand content is used for prompting a first provider to issue a task of selling backlog material. For example, the first demand content may be text prompting the first vendor to issue a task of selling backlog material. The first demand content displayed by the provider device may also include other content, or other forms, without being limited to the text information described above. The embodiment of the present application does not limit the first demand content displayed by the provider device 101 according to the first demand information.

In some embodiments, the first type may be a customer development type. The first task may be a task to develop a specified number of clients. Specifically, the first server 102 may obtain information of the first provider. The information of the first provider may include information of published and unpublished materials of the first provider. The information of the material may include, but is not limited to, a type of the material, an application industry, a model, an application scheme, a release time of the material, a sales amount, an inventory amount, and a storage time of the material. The first server 102 may determine that a newly released material exists for the first vendor or the server may determine that a certain material sales or sales volume is small. The first server 102 may in turn send first demand information to the provider device 101, the first demand information being used to instruct the first provider to issue a task to develop a customer of the material. Alternatively, the first task may be a task of developing a specified potential customer. The first server 102 may determine that the first vendor has newly published material and, in turn, the first server 102 may obtain information about potential customers stored by the vendor device 101 at the first server 102, which may include the type of material used by the potential customers. The first server 102 may send the first demand information to the provider device 101 upon determining that the potential customer is using the material, or is using an alternative material to the material. The first demand information is used to instruct the first provider to issue a task to develop a designated potential customer. The information of the potential customer may be stored in the first server 102 by the provider device 101 or the agent device 103. The information of potential customers may include, but is not limited to: the qualification of potential customers, the address, the materials used, the industry, etc.

In some embodiments, the first type may be a follow-up customer type and the first task may be a task to feed back pre-and/or after-market conditions. Specifically, the first server 102 may obtain information of the first agent. The information of the first agent may include customer ratings of the first agent. In some embodiments, the first server 102 may generate a page for populating the first agent and send a link to the page to the vendor device or agent device, such that the first vendor or first agent may share the page link to the customer, who may populate the page with the first agent's rating on the electronic device. The provider device 101 may obtain customer ratings of the first agent during a third period of time. The customer rating may be a score of the customer of the first agent for pre-and/or after-sales service conditions of the first agent and calculate an average score of the customer rating. When the first agent's pre-and/or after-market service condition score average is low, first server 102 may send first demand information instructing the first provider to issue a "feedback pre-and/or after-market service condition" task to the first agent.

In some embodiments, the customer rating obtained by the first server 102 may be one or more original rating sentences. Further, first server 102 may extract emotion base units from one or more original evaluation sentences. The emotion basic unit may include attribute words, emotion words, and the like. The emotion scores for words or phrases may be stored in the first server 102. The positive words can have higher emotion scores, and the negative words can have lower emotion scores. Further, the server may weight the emotion scores to obtain a customer rating score for the first agent. The first server 102 may determine that the first provider needs the first agent to timely feed back the pre-sale or after-sale service condition when the customer evaluation score is below a certain threshold value, and then send the first requirement information to the provider device 101.

In some embodiments, the first type may be a customer allocation type and the first task may be a task of allocating a specified customer to one or more agents. Specifically, the first server 102 may obtain information of the first provider. The information of the first provider may include an order quantity of one or more customers of the first provider. The first server 102 may determine that the number of one or more customer orders of the first provider decreases. Further, the first server 102 may send first demand information to the provider device 101, the first demand information being used to instruct the first provider to issue a customer allocation task, which may be used to allocate one or more customers to the agent, which continues to follow.

Not limited to the above types, the first server 102 may also determine more or fewer types of tasks. Each task type may also contain more task content. The embodiment of the application does not limit the task type and the task content of the first task indicated by the first requirement information determined by the first server 102.

It is appreciated that the first server 102 may actively determine the needs of the first provider based on the information of the first provider and/or the information of the first agent. In this way, the first server 102 may remind the first provider when the first provider has a requirement of issuing a task, so as to avoid the first provider from issuing the task in time.

In some embodiments, steps S201-S203 are optional. The first server 102 may receive a first request from the provider device 101 for the first provider to issue a first task of a first type to the first agent. Wherein the first type of the first task may be determined by the provider device 101 in response to a user operation and transmitted to the first server 102, instead of the first server 102 being determined according to the information of the first provider and/or the information of the first agent.

S203, the first server 102 determines the content of the first task according to the information of the first provider and/or the information of the first agent.

In some embodiments, after receiving the first demand information, the provider device 101 may prompt to issue a first task of a first type according to the information of the first demand. Further, the first server 102 may determine the content of the first task according to the information of the first provider and the information of the first agent.

In some embodiments, after the first server 102 determines that the first task is a task of selling one or more materials, an agent selling the one or more materials may be determined, as well as a target quantity for the sale. Taking a first agent of the vendor's agents, including a first material in one or more materials as an example. For example, the first server 102 may determine an inventory quantity of a first material of the one or more materials. Further, the first server 102 may obtain customer information for the first agent, which may include a first demand for the first material by the first customer during the first time period, and a second demand for the first material by the second customer during the first time period. The first customer is a customer using a first material, and the second customer is a customer using a first material alternative material. The replaceable material refers to a product which can be directly replaced by the first material and is applied to the material, and the function of the product is not changed. The first server 102 may determine a third demand for the first material by the first customer for the second time period in the future according to the first demand using a linear regression method, and the first server 102 may also determine a fourth demand for the first material by the second customer for the second time period in the future according to the second demand using a linear regression method. Further, the server may sum the third demand and the fourth demand and determine a target quantity of the first material sold by the first agent based on the inventory of the first material by the supplier. The first server 102 may determine the target number that all agents can sell and rank the agents by the number of materials that can sell. The first server 102 may select an agent (e.g., a first agent) from which to predict the most sales, and the first server 102 may determine that the content of the first task is to sell a specified target amount of the first material for the first agent.

In some embodiments, the first server 102 may determine that the first task is a task to develop a specified number of clients. Further, the first server 102 may determine the number of clients that the first agent has newly increased in the past fourth period of time. Further, the first server 102 may predict the number of clients that it can develop in the fifth time period according to the number of clients that the first agent newly increases in the fourth time period. Further, the server may determine task content of the first task based on the prediction result.

In some embodiments, the first server 102 may determine that the first task is a task of developing a specified potential client. The first server 102 may obtain client information for one or more agents. The first server 102 may portray the one or more agent's clients based on the one or more agent's client information. Taking the first agent as an example, the first server 102 may tag the client information of the client of the first agent and the client information of the first client. The tags may include expert tags, custom tags, lingering semantic tags, and the like. By way of example, "Hunan" may be a label of the first agent. The label may be obtained after first server 102 determines that a majority of the customer addresses of the first agent are located in Hunan province. Further, the first server 102 may extract text features of one or more tags of the client of the first agent, generating a first feature vector. And the first server 102 may also extract text features of one or more tags of the potential client to generate a second feature vector. The first server 102 may calculate the similarity of the first agent's customer to the potential customer through a cosine similarity formula. Finally, the first server 102 determines one or more agents that have the highest similarity of the client of the first agent to the potential client. In this way, the server may determine the task content of the first task as developing the potential client by the first agent. Optionally, the first server 102 may further sort the clients of the agents according to their similarity to the potential clients, and determine the content of the first task as assigning the potential clients to one or more of the agents with the client similarity M-th, where M is any positive integer.

In some embodiments, first server 102 may determine that the first task is a task that assigns a specified client to one or more agents. Wherein the one or more agents may include a first agent. The method for the first server 102 to assign the specified client to the first agent may refer to the first server 102 to determine a method for developing the specified potential client by the first agent, which will not be described herein.

In some embodiments, first server 102 may determine that the first task is a task that feeds back pre-and/or after-market conditions. The first server 102 may divide different reporting frequencies according to the client rating score. The method for obtaining the customer evaluation score by the first server 102 may refer to the description of the foregoing embodiment, and will not be described herein. The first server 102 may determine that the mission content of the first mission is the first agent feeding back the pre-and/or after-market conditions to the provider device at the first frequency when the customer rating score is low. When the customer rating score is high, the first server 102 may determine that the mission content of the first mission is the first agent feeding back pre-and/or after-market conditions to the provider device at the second frequency. For example, the first frequency may be once every seven days, and the second frequency may be once every month.

S204, the first server 102 sends a first message to the provider device 101, where the first message is used to prompt the provider device to issue a first task to the agent device.

S205, the provider device 101 displays the content of the first task according to the first message.

S206, the provider device 101 sends a second message in response to the first operation, where the second message is used for the provider device to issue a second task to the agent device.

S207, the first server 102 transmits the second message to the agent device 103.

S208, the agent device 103 displays the content of the second task according to the second message.

Wherein the task types of the second task and the first task are both the first type. The task content of the second task may be the same as or different from the task content of the first task.

The provider device 101 may display the content of the first task, and the content of the first task may be used to recommend the first provider the executor and the execution amount of the first task. The provider device 101 may issue the second task to the first agent in response to a user operation. The agent device 103 may display the content of the second task without displaying the content of the first task. That is, the second task is the task actually received by the first agent.

S209, the first server 102 determines first allocation information of the second task according to the portraits of one or more clients of M members of the first agent, wherein the first allocation information is used for indicating that the second task is allocated to N members of the first agent.

S210, the first server 102 transmits the first allocation information to the agent apparatus 103.

S211, the agent device 103 displays the first allocation information.

Wherein M is a positive integer, N is a positive integer, and N does not exceed M.

In some embodiments, the second task may be to develop a specified customer. The first server 102 may determine the similarity of the representation of the specified client to the representation of one or more clients of the M members. Further, the first server 102 may rank the similarity from large to small and determine the first N members from which the similarity is higher. The method of determining, by the first server 102, the member responsible for the client according to the client portrait of the member and the portrait of the specified client may refer to the method of determining, by the first server 102, the agent of the client according to the client portrait of the agent and the portrait of the specified client in the above embodiment, and will not be described herein.

In some embodiments, step S209 is optional. The first server 102 may not determine the first allocation information for the second task based on the representation of one or more clients of the M members of the first agent. Taking the second task as an example of selling a designated material (e.g., a first material). The first server 102 may determine a customer using the first material and a customer using the first material associated with the material. The material associated with the first material may include a material that is replaced with the first material, or may include a material that can be combined with the first material. The first server 102 may match the associated materials based on the information of the first product. The information of the first material may include a material type, a packaging mode, an industry application, and a material model of the first material. The first server 102 may determine that the two materials are to be replaced when one or more of the material category, packaging, industry application, and material model of the first material and the other material are the same. The first server 102 may determine that two materials can be used in combination when the material categories of the first material and the other material are different and the industry application is the same. Further, the first server 102 may determine first allocation information among the members of the first agent, the first allocation information indicating sales of the first material by the N members of the first agent. The N members may include one or more members that interface with a customer using the first material and one or more members that interface with a customer using a material associated with the first material.

In some embodiments, steps S209-S211 are optional. It will be appreciated that in some task scenarios, the first server 102 is not required to send the first assignment information recommending the task performing member to the agent device 103.

Not limited to the vendor device 101 publishing tasks to the agent device 103 via the first server 102, in some embodiments, the agent device 103 may also publish tasks to the vendor device 101. For example, the agent device 103 may issue a task to the provider device 101 requesting a sample, a meeting invitation task, a task to follow up with an order, and so on.

It will be appreciated that the first vendor may contain multiple agents, and that the first vendor may not be sufficiently aware of the first agent's situation due to the large amount of agent information and agent's customer information. The first server 102 may alert in time when there is a need for the first provider to issue a task. And the first server 102 may also recommend an executing agent of the task to the first provider based on information of one or more agents of the first provider and/or client information of the agents, and recommend a task amount of the agent. This may help the first provider select a more appropriate agent and also help the first provider determine the amount of tasks that are more appropriate for the agent. In this way, the first server 102 may help the first provider reduce the occurrence of errors in the decisions. Finally, after the agent device obtains the task issued by the provider device, the first server 102 may also provide the agent device with a member recommendation to perform the task. In this way, the first server 102 may help the agent promote the efficiency of task execution.

A schematic scenario in which some vendor devices issue tasks to agent devices according to the embodiments of the present application will be described below by taking sales tasks as an example.

Fig. 3A-3E are schematic diagrams illustrating scenarios in which some vendor devices issue sales tasks to agent devices.

As shown in fig. 3A, the provider device 101 may display a prompt box 300. Prompt box 300 may include prompt 301, skip control 302, and cancel control 303. The prompt box 300 may be displayed by the provider device 101 according to the first requirement information after the first server 102 sends the first requirement information to the provider device 101.

The prompt 301 is used to remind the first provider to issue the first task. The prompt 301 may include text recommending that the first provider issue the first type of task, as well as the reason for the recommendation. For example, the prompt 301 may display "detecting that the first stock of material is backlogged too long, recommending issuing sales tasks".

The skip control 302 is used to skip to the page that fills in the task content.

The cancel control 303 is used to close the prompt box 300.

In response to a user clicking on jump control 302, provider device 101 may display user interface 310 as shown in FIG. 3B. A plurality of editing controls, submission controls 316, and recommendation information 317 may be included in the user interface 310.

Editing controls are used to fill in the different fields of the task. The editing controls may include, among other things, an editing control 311 for filling in a task name field, an editing control 312 for filling in a task type, an editing control 313 for filling in an execution agent, a control 314 for filling in sales content, and an editing control 315 for filling in sales volume. Wherein the task name field may be a task name of the first task, and the task name field may be used to summarize a task type and task content. The execute agent field may be an agent identification for which the first task is to be executed, which identification may be the name of the agent. The task type field may be a task type "sales task" of the first task. The sales content field may include the name of the material to be sold, the model number. The sales number field may be the number of items to be sold by the first task specifying agent. Not limited to the above fields, the user interface 310 may further include edit controls for filling out more or fewer fields, and the embodiment of the present application does not limit the number of edit controls in the user interface 310 and the types of fields that can be filled out.

In some embodiments, the vendor device 101 may determine the task type as a sales task, and in turn display an edit control of a field related to the sales task. The editing controls described above may include editing control 314 and editing control 315.

Taking the editing control 311 as an example, the editing control 311 is configured to receive an operation of filling in a task name field by a user, and display the task name field filled in by the user in the editing control 311. The left side of the edit control 311 can display a field identification (e.g., "task name") that the edit control 311 needs to fill in. The display manner of the other editing controls may refer to the display manner of the editing control 311, which is not described herein. Wherein the field "sales task" in edit control 312 and the field "first material" in edit control 314 may be filled in and displayed by vendor device 101 according to the first demand information.

The submit control 316 is used to submit the task information displayed by the user interface 310 to the server, which sends it to the corresponding agent device.

The recommendation information 317 is used to indicate the executives of the sales tasks, as well as the sales volume. For example, recommendation information 317 may instruct the first vendor to assign a sales task to the first agent and sell 8000 items. The content displayed in the recommendation information 317 contains the content of the first task, which may be displayed by the provider device 101 according to the first message. Not limited to indicating the allocation of sales tasks to the first agent, more sales executives and sales volumes may also be displayed in the recommendation information 317. The embodiments of the present application are not limited in this regard.

In response to a user operation, the editing control may be filled in and displayed in the editing control, as shown in fig. 3C. Wherein edit control 311 may fill in and display the "sell first materials" field, edit control 313 may fill in and display the "first agent" field, and edit control 315 may fill in and display "9000". This indicates that the sales task is named sales first material, the content of the sales task comprising: let the first agent sell 9000 first materials.

It will be appreciated that the sales volume displayed in the recommendation information 317 is used to provide a reference to the first vendor's issuing task, and the first vendor may fill in the edit control with the sales volume that the first vendor expects the first agent according to the recommendation information 317.

In response to a user clicking on the submit control 316, the vendor device 101 may display a dialog box 318 as shown in FIG. 3D. Dialog box 318 is used to alert the first vendor that the first task has been successfully issued to the first agent. Text information of "task publication successful" may be included in the dialog box 318.

In some embodiments, the vendor device 101 may determine the content of the second task from the content of the edit control fill in the user interface 310 and send a second message to the agent device 103 via the first server 102 according to the content of the second task. In the user interface shown in fig. 3C, the content of the second task may include: the first agent is required to sell 9000 first items. It should be noted that the content of the second task may be different from the content of the first task. The content of the second task may be published to the first agent by the first vendor with reference to the content of the first task.

It is appreciated that the first server 102 may determine the task content based on information of the vendor and/or information of the agent, wherein the task content includes information that may include task performers and/or task volumes, and the like. In this way, when the provider issues the first task, the provider can refer to the task content recommended by the first server 102, so as to avoid that the task quantity issued by the provider does not match with the capability of the agent due to insufficient knowledge of the agent by the provider.

In response to the operation acting on the submit control 316, the vendor device 101 may determine the content of the second task and send a second message to the agent device 103 via the first server 102. The second message is used for the provider device to issue a second task to the agent device, and the second message contains the content of the second task. In this way, the agent device 103 may display the content of the second task based on the second message.

As shown in fig. 3E, the agent device 103 may display a user interface 320. The user interface 320 may include a task display area 321 and an allocation recommendation area 322.

Wherein the task display area 321 may display the content of the second task. For example, the contents that the task display area 321 can display include a task name, a task type, a sales product, a sales quantity, and the like.

The assign recommendation area 322 may be used to recommend members to the first agent that complete the second task. The allocation recommendation area 322 may be displayed according to the first allocation information after the agent apparatus 103 receives the first allocation information transmitted from the first server 102. Optionally, the allocation recommendation area 322 may also display allocation reasons, which may include the method used by the first server 102 to determine the first allocation information.

It may be appreciated that, after the agent receives the task issued by the provider, the first server 102 may recommend a task allocation method for the agent according to the member of the agent and/or the client of the agent, so as to help the agent allocate the task to a suitable executor, thereby improving the completion rate of the task.

In some embodiments, the agent device in the embodiments shown in fig. 2, 3A-3E may be a vendor device that logs onto an agent account. Referring to the communication system 30 shown in fig. 1C, the provider device 101 may switch the account logged in at the fourth server 106 from the account of the first provider to the account of one or more agents, thereby performing a possible implementation of the agent device in the above embodiment. The task management method and implementation scenario of the provider device logging in the agent account and the provider device logging in the provider account in the communication system 30 may refer to the task management method and implementation scenario of the provider device 101 and the agent device 103 in the communication system 10 in the foregoing embodiments, and are not described herein.

As shown in fig. 4, fig. 4 is a schematic structural diagram of a provider device 101 according to an embodiment of the present invention, where the provider device 101 may include:

a communication unit 401 for receiving a first message, where the first message is used to prompt the provider device 101 to issue a first task to the agent device, where the first task is determined by the server according to the information of the first provider and the information of the first agent;

a processing unit 402 for receiving a first operation for issuing a second task to a first agent device;

a display unit 403 for displaying the content of the first task according to the first message;

the communication unit 401 is further configured to send, via the server, a second message to the agent device, where the second message is used for the provider device to issue a second task to the agent device, and the second message includes a content of the second task.

In some embodiments, the communication unit is further configured to receive first requirement information before the server determines the first task according to the information of the first provider and the information of the first agent, where the first requirement information is used to indicate that the first provider has a requirement to issue the first type of task. Or, the communication unit is further configured to send a first request to the server, where the first request is used to instruct the first provider to issue a requirement of the first type of task to the first agent.

In some embodiments, the type of first task is a sales task, and the content of the first task includes a target amount of the first agent selling one or more materials.

In some embodiments, the type of first task is a client development task, and the content of the first task includes instructions to the first agent to develop a specified client, or the content of the first task includes instructions to the first agent to develop a first number of clients.

In some embodiments, the type of first task assigns a task to the client, the content of the first task including instructing the first agent to dock one or more clients.

In some embodiments, the type of first task is a follow-up customer task, and the content of the first task includes information indicating that the first agent reports pre-sale and/or after-sale services.

The specific operation and advantages of the respective units in the provider device 101 shown in fig. 4 may be referred to the corresponding description in fig. 2 and the possible embodiments thereof, and will not be repeated here.

As shown in fig. 5, fig. 5 is a schematic structural diagram of a server 500 according to an embodiment of the present invention, where the server 500 may include:

a communication unit 501, configured to send a first message to a provider device, where the first message is used to prompt the provider device to issue a first task to an agent device;

A processing unit 502, configured to determine content of the first task according to the information of the first provider and the information of the first agent;

the communication unit 501 is further configured to receive a second message sent by the provider device, and send the second message to the agent device, where the second message is used for the provider device to issue a second task to the agent device, and the second message includes content of the second task.

In some embodiments, before the processing unit 502 determines the content of the first task according to the information of the first provider and the information of the first agent, the processing unit 502 is further configured to determine first requirement information according to the information of the first provider and/or the information of the first agent, and the communication unit 501 is further configured to send the first requirement information to the provider device, where the first requirement information is used to indicate that the first provider has a requirement for issuing the first type of task; alternatively, the communication unit 501 is further configured to receive a first request sent by the provider device, where the first request is used to instruct the first provider to issue a requirement of a first type of task to the first agent; the first task and the second task are of a first type.

In some embodiments, server 500 also includes a storage unit 503. The storage unit 503 may store therein representations of one or more clients of M members of the first agent, M being a positive integer. The processing unit 502 is further configured to determine first allocation information of the second task according to member portraits of one or more clients, where the first allocation information is used to indicate that the second task is allocated to one or more members of the first agent, N is a positive integer, and N does not exceed M. The communication unit 501 is further configured to send the first allocation information to the agent device.

In some embodiments, the processing unit 502 determines the content of the first task according to the information of the first provider and the information of the first agent, specifically including: the processing unit 502 obtains a first demand of a first customer of the first agent for the first material in the first time period and a second demand of a second customer for the first material in the first time period, wherein the first customer is a customer using the first material, and the second customer is a customer using the first material instead of the material; the processing unit 502 predicts a third demand of the first customer for the first material in the second time period through linear regression according to the first demand, and the processing unit 502 predicts a fourth demand of the second customer for the first material in the second time period through linear regression according to the second demand; the processing unit 502 determines a target amount of the first material sold by the first agent according to the third demand and the fourth demand.

In some embodiments, the processing unit 502 determines the first requirement information according to the information of the first provider and/or the information of the first agent, specifically including: the processing unit 502 determines that the storage time of the one or more materials exceeds a third length of time; the processing unit 502 determines a first demand indicating that a first vendor has a demand to sell one or more materials.

The specific operation and beneficial effects of each unit in the server 500 shown in fig. 5 can be seen from the description corresponding to the first server 102 in fig. 2 and the possible embodiments thereof, and will not be repeated here.

The structure of the second server 104 and the third server 105 may refer to specific operations and beneficial effects of each unit in the server 500, which are not described herein.

As shown in fig. 6, fig. 6 is a schematic structural diagram of an agent device 103 according to an embodiment of the present invention, where the agent device may include:

a communication unit 601, configured to receive a second message, where the second message is used for a vendor device to issue a second task to an agent device, and the second message includes content of the second task, where the second task is determined by the vendor device according to the first task, and the first task is determined by the server 500 according to information of the first vendor and/or information of the first agent;

And a display unit 602, configured to display the content of the second task according to the second message.

In some embodiments, the communication unit 601 is further configured to receive first allocation information, where the first allocation information is configured to indicate that the second task is allocated to one or more N members of the first agent, N is a positive integer, and N does not exceed M; the display unit 602 is further configured to display the first allocation information.

The specific operation and beneficial effects of each unit in the agent device 103 shown in fig. 6 can be seen from the corresponding description in fig. 2 and the possible embodiments thereof, and will not be repeated here

The above embodiments are merely for illustrating the technical solution of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

The various user interfaces described in the embodiments of the present application are merely exemplary interfaces and are not limiting on the aspects of the present application. In other embodiments, the user interface may take different interface layouts, may include more or fewer controls, and may add or subtract other functional options, as long as they are within the scope of the present application based on the same inventive concepts provided herein.

As used in the above embodiments, the term "when …" may be interpreted to mean "if …" or "after …" or "in response to determination …" or "in response to detection …" depending on the context. Similarly, the phrase "at the time of determination …" or "if detected (a stated condition or event)" may be interpreted to mean "if determined …" or "in response to determination …" or "at the time of detection (a stated condition or event)" or "in response to detection (a stated condition or event)" depending on the context.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk), etc.

Those of ordinary skill in the art will appreciate that implementing all or part of the above-described method embodiments may be accomplished by a computer program to instruct related hardware, the program may be stored in a computer readable storage medium, and the program may include the above-described method embodiments when executed. And the aforementioned storage medium includes: ROM or random access memory RAM, magnetic or optical disk, etc.

Claims

1. A method of task management, the method being applied to a communication system comprising a provider device, a server, an agent device, the provider device being associated with a first provider, the agent device being associated with a first agent, the method comprising:

the server determines the content of a first task according to the information of the first provider and the information of the first agent;

the server sends a first message to the provider equipment, wherein the first message is used for prompting the provider equipment to issue the first task to the agent equipment;

the provider equipment displays the content of the first task according to the first message and receives a first operation, wherein the first operation is used for issuing a second task to the first agent equipment;

In response to the first operation, the provider device sends a second message to the agent device through the server, wherein the second message is used for the provider device to issue the second task to the agent device, and the second message contains the content of the second task;

and the agent equipment displays the content of the second task according to the second message.

2. The task management method according to claim 1, wherein before the server determines the content of the first task from the information of the first provider and the information of the first agent, the method further comprises:

the server determines first demand information according to the information of the first provider and/or the information of the first agent, and the server sends the first demand information to the provider equipment, wherein the first demand information is used for indicating that the first provider has a demand for issuing a first type of task; or alternatively, the process may be performed,

the server receives a first request sent by the provider equipment, wherein the first request is used for the first provider to issue the first type of task to the first agent;

Wherein the first task and the second task are of the first type.

3. The method of claim 1 or 2, wherein the server stores representations of one or more clients of M members of the first agent, M being a positive integer, the method further comprising:

the server determines first allocation information of the second task according to the portraits of the one or more clients, wherein the first allocation information is used for indicating that the second task is allocated to N members of the first agent, N is a positive integer, and N is not more than M;

the server sends the first allocation information to the agent device.

4. The method of claim 2, wherein the type of the first task is a sales task and the content of the first task includes a target amount of sales of one or more materials by the first agent.

5. The method of claim 4, wherein the one or more items comprise a first item, and wherein the server determines the content of the first task based on the information of the first vendor and the information of the first agent, and specifically comprises:

The server obtains a first demand of a first customer of the first agent for a first material in a first time period and a second demand of a second customer for the first material in the first time period, wherein the first customer is a customer using the first material, and the second customer is a customer using the first material instead of the material;

the server predicts a third demand of the first customer for the first material in a second time period through linear regression according to the first demand, and predicts a fourth demand of the second customer for the first material in the second time period through linear regression according to the second demand;

the server determines a target quantity of the first material sold by the first agent according to the third demand and the fourth demand.

6. The method according to claim 4 or 5, wherein the server determines the first requirement based on the information of the first provider and/or the information of the first agent, in particular comprising:

the server determining that the storage time of the one or more materials exceeds a third length of time;

the server determines a first demand for indicating that the first vendor has a demand to sell the one or more materials.

7. A method according to any of claims 1-3, wherein the type of the first task is a client development task, the content of the first task comprising instructing the first agent to develop a specified client, or the content of the first task comprising instructing the first agent to develop a first number of clients.

8. A method according to any of claims 1-3, wherein the type of first task assigns a task to a customer, the content of the first task comprising instructing the first agent to dock one or more customers.

9. A method according to any of claims 1-3, characterized in that the type of the first task is a follow-up customer task, the content of the first task comprising information indicating that the first agent reports pre-sales and/or after-sales services.

10. A communication system comprising a provider device, a server, an agent device, the provider device being associated with a first provider, the agent device being associated with a first agent,

the server is used for determining the content of a first task according to the information of the first provider and the information of the first agent;

The server is further configured to send a first message to the provider device, where the first message is used to prompt the provider device to issue the first task to the agent device;

the provider equipment is used for displaying the content of the first task according to the first message and receiving a first operation, wherein the first operation is used for issuing a second task to the agent equipment;

the provider device is further configured to send, by the server, content of the second task to the agent device;

the agent device is configured to display content of the second task.