CN109756348B

CN109756348B - Batch calling method and device

Info

Publication number: CN109756348B
Application number: CN201711090637.4A
Authority: CN
Inventors: 马文博; 张腊梅; 康彦荣
Original assignee: Nail Holding Cayman Co ltd
Current assignee: Nail Holding Cayman Co ltd
Priority date: 2017-11-08
Filing date: 2017-11-08
Publication date: 2022-06-10
Anticipated expiration: 2037-11-08
Also published as: TW201939975A; CN109756348A; WO2019091323A1

Abstract

One or more embodiments of the present specification provide a method and an apparatus for bulk calling, where the method may include: responding to a batch calling operation initiated by group members of a group, and initiating a call to a calling object corresponding to the batch calling operation; displaying a call record management interface aiming at the call object; and generating the call records aiming at the call objects according to the input content of the group members on the call record management interface.

Description

Batch calling method and device

Technical Field

One or more embodiments of the present disclosure relate to the field of communications technologies, and in particular, to a method and an apparatus for batch calling.

Background

In the related art, the mobile group office platform is more and more widely applied to the office processes of various groups such as enterprises, education institutions and government offices, and not only can the communication efficiency between users be improved and the communication cost be reduced, but also the event processing efficiency and the office efficiency of the users can be effectively improved.

Disclosure of Invention

In view of this, one or more embodiments of the present disclosure provide a method and apparatus for bulk calling.

To achieve the above object, one or more embodiments of the present disclosure provide the following technical solutions:

According to a first aspect of one or more embodiments of the present specification, there is provided a batch call method, including:

responding to a batch calling operation initiated by group members of a group, and initiating a call to a calling object corresponding to the batch calling operation;

displaying a call record management interface aiming at the call object;

and generating the call records aiming at the call objects according to the input content of the group members on the call record management interface.

According to a second aspect of one or more embodiments of the present specification, there is provided a batch call method including:

and displaying a call record management interface aiming at the call object, wherein the call record management interface comprises historical call records aiming at the call object.

According to a third aspect of one or more embodiments of the present specification, there is provided a batch call apparatus including:

the first calling unit responds to a batch calling operation initiated by a group member of a group and initiates a call to a calling object corresponding to the batch calling operation;

The first interface display unit is used for displaying a call record management interface aiming at the call object;

and the generating unit is used for generating the call record aiming at the call object according to the input content of the group members in the call record management interface.

According to a fourth aspect of one or more embodiments of the present specification, there is provided a batch call device, including:

the second calling unit responds to a batch calling operation initiated by a group member of a group and initiates a call to a calling object corresponding to the batch calling operation;

and the second interface display unit is used for displaying a call record management interface aiming at the call object, and the call record management interface comprises historical call records aiming at the call object.

Drawings

Fig. 1 is a schematic diagram of an architecture of a bulk call system according to an exemplary embodiment.

Fig. 2 is a flow chart of a method for bulk calling according to an example embodiment.

Fig. 3 is a flow chart of another method for bulk calling provided by an exemplary embodiment.

FIG. 4 is a schematic diagram of a task list interface provided by an exemplary embodiment.

Fig. 5 is a diagram of a dialing setup interface provided by an exemplary embodiment.

FIG. 6 is a schematic diagram of a task management interface provided by an exemplary embodiment.

FIG. 7 is a schematic diagram of an object import interface provided by an exemplary embodiment.

Figure 8A is a schematic illustration of a call record management interface provided by an exemplary embodiment.

Fig. 8B is a schematic diagram of a history call record presentation interface according to an exemplary embodiment.

Fig. 9 is a schematic structural diagram of an apparatus according to an exemplary embodiment.

Fig. 10 is a block diagram of a bulk call device according to an example embodiment.

Fig. 11 is a block diagram of another bulk call device provided in an exemplary embodiment.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of one or more embodiments of the specification, as detailed in the claims which follow.

It should be noted that: in other embodiments, the steps of the corresponding methods are not necessarily performed in the order shown and described herein. In some other embodiments, the method may include more or fewer steps than those described herein. Moreover, a single step described in this specification may be broken down into multiple steps for description in other embodiments; multiple steps described in this specification may be combined into a single step in other embodiments.

Fig. 1 is a schematic diagram of an architecture of a bulk call system according to an exemplary embodiment. As shown in fig. 1, the system may include a server 11, a network 12, a number of electronic devices such as a cell phone 13, a PC14, and the like.

The server 11 may be a physical server comprising a separate host, or the server 11 may be a virtual server carried by a cluster of hosts. In the operation process, the server 11 may operate a server-side program of a certain application to implement a related service function of the application, for example, when the server 11 operates a program of a mobile group office platform, the server may be implemented as a server of the mobile group office platform to implement the batch call scheme of this specification.

In this embodiment, the mobile group office platform not only can implement a communication function, but also can be used as an integrated functional platform with many other functions, for example, for processing internal events of a group such as an approval event (e.g., approval event such as leave request, office article claim, and finance), an attendance event, a task event, and a journal event, and for processing external events of a group such as ordering and purchasing, which is not limited in one or more embodiments of the present specification.

More specifically, the mobile corporate office platform may be supported by an Instant Messaging application in the related art, such as an Enterprise Instant Messaging (EIM) application, For example, Skype For

Microsoft

And so on. Certainly, the instant messaging function is only one of the communication functions supported by the mobile group office platform, and the mobile group office platform can also implement more other functions such as those described above, and details thereof are not described here.

The cellular phone 13 and the PC14 are only some types of electronic devices that the user can use. In fact, it is obvious that the user can also use electronic devices of the type such as: tablet devices, notebook computers, Personal Digital Assistants (PDAs), wearable devices (e.g., smart glasses, smart watches, etc.), etc., which are not limited by one or more embodiments of the present disclosure. In the operation process, the electronic device may operate a client-side program of an application to implement a related service function of the application, for example, when the electronic device operates a program of a mobile community office platform, the electronic device may be implemented as a client of the mobile community office platform to implement the batch call scheme of this specification.

It should be noted that: an application program of a client of the mobile community office platform can be pre-installed on the electronic equipment, so that the client can be started and run on the electronic equipment; of course, when an online "client" such as HTML5 technology is employed, the client can be obtained and run without installing a corresponding application on the electronic device.

And the network 12 for interaction between the handset 13, PC14 and server 11 may include various types of wired or wireless networks. In one embodiment, the Network 12 may include the Public Switched Telephone Network (PSTN) and the Internet.

Fig. 2 is a flowchart of a method for bulk calling according to an exemplary embodiment. As shown in fig. 2, the method may include the steps of:

step 202, in response to a batch call operation initiated by a group member of a group, initiating a call to a call object corresponding to the batch call operation.

In one embodiment, the group members can actively select call objects corresponding to the batch call operation; the call object may have various sources, such as an address list, a buddy list, a group organization structure, and the like, which is not limited in this specification. For at least one detected call object selected by the group members, when the group members initiate a batch call request for the selected call object, it may be determined that the group members initiate the batch call operation, so that the call object selected by the group members may be used as a call object corresponding to the batch call operation to initiate a call.

In an embodiment, any group member of the group may create a batch call task in advance, and indicate a call object in the batch call task; then, when it is detected that the group member triggers a batch call task, it may be determined that the group member initiates the batch call operation, and a call object indicated by the batch call task is used as a call object corresponding to the batch call operation to initiate a call. Therefore, the batch call task in this embodiment may be created by the group member itself, or may be created by other group members in the group and then shared to the group member, without the need for repeated creation by the group member.

In one embodiment, the group may include various organizations such as enterprises, departments, schools, governments, hospitals, troops, and the like, which is not limited in this specification.

In an embodiment, in response to a batch call operation initiated by a group member of a group, a call may be sequentially initiated to a call object corresponding to the batch call operation. For example, when the bulk call operation corresponds to 20 call objects, a call may be initiated to each call object separately, for a total of 20 call operations.

In one embodiment, in response to a batch call operation initiated by a community member of a community, a group call may be initiated to a call object corresponding to the batch call operation. For example, when the bulk call operation corresponds to 20 call objects, a call can be initiated to a plurality of call objects at the same time, thereby realizing a collective call with the call objects, such as a teleconference and the like; in this case, the collective call may be initiated for all 20 call objects, and only 1 call needs to be implemented, or the collective call may be initiated for some of the 20 call objects, for example, 2 calls need to be implemented for 10 call objects at a time.

And 204, displaying a call record management interface aiming at the call object.

In an embodiment, in the call record management interface, historical call information for the call object may be presented, the historical call information being related to historical batch call operations, and the call object belonging to the historical call object of the historical batch call operations. For example, the historical visit information may include at least one of: historical visit records, historical visit times, historical visit time, recent visit interval and the like, which are not limited by the specification. By displaying the historical visiting information, the group member can quickly know the historical visiting condition aiming at the calling object, thereby determining or adjusting the communication content, the communication tone, the communication flow and the like of the current visit, and improving the communication efficiency between the two parties.

In one embodiment, in the call record management interface, a feature description tag for the call object may be presented, and the feature description tag may be used to describe features of the call object in several dimensions; for example, the dimension may include the type of community to which it belongs, the position in the community, the degree of importance, whether it is easy to communicate, and the like, and this specification does not limit this.

Step 206, generating the call record aiming at the call object according to the input content of the group member in the call record management interface.

In one embodiment, in the process of initiating a batch call operation for a plurality of call objects, the call record management interface for each call object is automatically displayed without manually starting recording tools such as notebooks and the like for group members, so that the group members can record communication information in time and generate corresponding call records in the call process. Meanwhile, by recording the visit records, the corresponding communication process is convenient to review and recall afterwards, and the efficient processing of related events is facilitated.

In an embodiment, the call record may be bound to the community, so that at least one other community member of the community obtains access authority to the call record, that is, information sharing for the call record is performed, so that a plurality of community members in the community can cooperate with each other in the face of an event related to the call object, which helps to improve processing efficiency.

Fig. 3 is a flow chart of another method for bulk calling provided by an exemplary embodiment. As shown in fig. 3, the method may include the steps of:

step 302, in response to a batch call operation initiated by a group member of a group, initiating a call to a call object corresponding to the batch call operation.

In one embodiment, the group members can actively select call objects corresponding to the batch call operation; the call target may have multiple sources, such as an address list, a buddy list, a group organization structure, and the like, which is not limited in this specification. For at least one detected call object selected by the group members, when the group members initiate a batch call request for the selected call object, it may be determined that the group members initiate the batch call operation, so that the call object selected by the group members may be used as a call object corresponding to the batch call operation to initiate a call.

In one embodiment, any member of the community may create a batch call task in advance and indicate a call object in the batch call task; then, when it is detected that the group member triggers a batch call task, it may be determined that the group member initiates the batch call operation, and a call object indicated by the batch call task is used as a call object corresponding to the batch call operation to initiate a call. Therefore, the batch call task in this embodiment may be created by the group member itself, or may be created by other group members in the group and then shared to the group member, without the need for repeated creation by the group member.

In one embodiment, in response to a batch call operation initiated by a group member of a group, a group call may be initiated to a call object corresponding to the batch call operation. For example, when the bulk call operation corresponds to 20 call objects, a call can be initiated to a plurality of call objects at the same time, thereby realizing a collective call with the call objects, such as a teleconference and the like; in this case, the collective call may be initiated for all 20 call objects, and only 1 call needs to be implemented, or the collective call may be initiated for some of the 20 call objects, for example, 2 calls need to be implemented for 10 call objects at a time.

Step 304, displaying a call record management interface for the call object, where the call record management interface includes a history call record for the call object.

In one embodiment, when any group member of the group implements a historical batch call operation, the historical input content of the any group member in the call object call record management interface is generated as the historical call record. Therefore, by checking the historical visit record, the corresponding communication process can be conveniently reviewed and recalled afterwards, and the efficient processing of related events is facilitated.

In one embodiment, the historical visit record can be created by the community members themselves or by other community members in the community to realize information sharing among the community members. By displaying the historical visit records, the group members can quickly know the historical visit condition aiming at the call object, thereby determining or adjusting the communication content, communication tone, communication flow and the like of the current visit, and improving the communication efficiency between the two parties.

For convenience of understanding, the technical solutions of one or more embodiments of the present specification are described by taking an enterprise instant messaging application "enterprise WeChat" as an example. Assume that an enterprise wechat server is running on the server 11, and an enterprise wechat client is running on the PC14, and the enterprise wechat client logs in the registered account of the user a, which belongs to an enterprise member of the enterprise AA.

FIG. 4 is a schematic diagram of a task list interface provided by an exemplary embodiment. As shown in fig. 4, an enterprise wechat client running on PC14 may expose a task list interface 400 to user a for implementing bulk call functionality; task list interface 400 contains several bulk call tasks, such as the three bulk call tasks that have been created as shown in FIG. 4, with task names "project X negotiation", "potential customer", and "after-market maintenance", respectively. In addition to the "task name," the task list interface 400 may also present other relevant information such as "number of calls," "progress," etc. for each batch of call tasks; taking the batch call task "after-sales maintenance" as an example, the batch call task indicates that the number of calls is 150 and the progress of the performed batch call operation is 30% (i.e., 30% of the 150 have been called in batch and the remaining 70% have not been called in batch).

In one embodiment, the bulk call tasks illustrated by task list interface 400 may include tasks that are created by user A on their own. For example, when it is detected that the user a triggers the new task option 402 in the task list interface 400, the enterprise wechat client may provide a new task function to the user a, and the user a determines information such as a task name, all call objects that need to be called in batch for the task, for example, the call objects may be an enterprise wechat friend of the user a in the enterprise wechat client, an external contact of the enterprise AA (i.e., a contact that is maintained on the enterprise wechat and is related to the enterprise AA and does not belong to the enterprise AA), a local address book maintained on the PC14, a cloud address book, and the like, even a contact created temporarily by the user a, which is not limited by the present specification.

In one embodiment, the bulk call tasks illustrated by task list interface 400 may include tasks created by other users (other than user A) in enterprise AA. For example, user B, user C, etc. in the enterprise AA creates batch call tasks in advance and configures the batch call tasks in the enterprise AA, so that all members of the enterprise in the enterprise AA can view the relevant batch call tasks, and thus user a can view the task list interface 400 shown in fig. 4 on the enterprise WeChat client, and the relevant batch call tasks in the task list interface 400.

In one embodiment, task list interface 400 may include a dial settings option 404, as shown in FIG. 4, for user A to set the relevant parameters of the enterprise wechat client when conducting the batch call. For example, FIG. 5 is a schematic diagram of a dialing setup interface provided by an exemplary embodiment; as shown in fig. 5, based on the user a's trigger action on the dial settings option 404, the enterprise wechat client may present a dial settings interface 500 to set the relevant parameters.

In one embodiment, when user a has multiple affiliated enterprises, such as user a affiliated with both enterprise AA and enterprise BB, the enterprise wechat client may provide a "choose to initiate enterprise" parameter as shown in fig. 5 in the dialing setup interface 500 to select the enterprise and its phone number for initiating the bulk call by user a (there is a corresponding phone number for each enterprise); for example, when the user A selects the enterprise AA, the batch call is initiated using the telephone number "0571-.

In one embodiment, the enterprise WeChat client may provide the "duration of No-Man ring" parameter shown in FIG. 5 in the dialing setup interface 500, and provide several options for the parameter, such as "15 seconds", "30 seconds", "45 seconds", etc., for the user A to select: waiting for the duration of the called party's listening (i.e., the ringing duration) before the called party's listening.

In one embodiment, the enterprise wechat client may provide a "call-after-answer mode" parameter as shown in fig. 5 in the dialing setup interface 500; when the user a logs in its own enterprise wechat registration account on the PC14 and the used mobile phone, respectively, the enterprise wechat client may provide several options for the parameter, such as "computer (i.e. PC 14)", "mobile phone (i.e. the mobile phone that the user a logs in)" and the like, for the user a to select: and the communication with the called party is completed through a computer or a mobile phone.

In one embodiment, task list interface 400 as shown in FIG. 4 also provides operational options for the batch call tasks that have been established; taking the batch call task "after-sales maintenance" as an example, the operation options for the task may include a delete option 406, an enter task option 408, and the like, where the delete option 406 is used to delete the batch call task "after-sales maintenance", and the enter task option 408 is available for the user a to perform management operations for the batch call task "after-sales maintenance".

FIG. 6 is a schematic diagram of a task management interface provided by an exemplary embodiment. Based on the user a's trigger to enter the task option 408 as shown in fig. 4, the enterprise wechat client may transfer to the task management interface 600 shown in fig. 6 for performing management operations for the batch call task "after-market maintenance". As shown in fig. 6, the task management interface 600 may include information of 150 call objects indicated by the batch call task "after-market maintenance", including "customer name (i.e. name of call object)", "phone number", "status", etc., such as "customer 1" with "139 xxxxxxxx" and "not visited" phone number.

In one embodiment, a separate management operation may be performed for each call object illustrated by task management interface 600. For example, by triggering the "call" option corresponding to "customer 1", a separate call operation may be initiated for that "customer 1"; by triggering the more option corresponding to the customer 1, operations such as deletion, modification and the like can be implemented for the customer 1.

In one embodiment, administrative operations may be implemented for bulk call tasks "after-market maintenance". FIG. 7 is a schematic diagram of an object import interface provided by an exemplary embodiment; upon detecting that user a triggers the import call object option 602 shown in fig. 6, the enterprise wechat client may show an object import interface 700 as shown in fig. 7, such that user a may add more call objects (i.e., call objects) to the bulk call task "after-market maintenance" based on the object import interface 700. For example, the enterprise wechat client may classify call objects that need to be imported into two categories: enterprise-external contacts and non-enterprise-external contacts.

Taking the enterprise AA to which the user a belongs as an example, when call objects to be added do not belong to the enterprise AA but have an association relationship with the enterprise AA (for example, business traffic exists, etc.), the call objects may be configured as external contacts of the enterprise AA, and then by triggering a "select" option corresponding to the "already external contacts" type in the object import interface 700, the enterprise WeChat client may present the external contacts list of the enterprise AA to the user a, so as to select a call object that wishes to import the batch call task "after sales maintenance".

For non-business external contacts, however, a "not yet added to business external contacts" type is provided in object import interface 700 and allows user A to perform a single import or a bulk import. When it is detected that user a triggers an "add" option in object import interface 700 corresponding to "single import", enterprise WeChat client may provide user a with information such as a buddy list, address list, etc. for user a to select a single call object that wishes to import a bulk call task "after-market maintenance". When a user a wishes to adopt a batch import scheme, the user a may first trigger a "download form" option in the object import interface 700 to download corresponding contact information to fill out a form, then add the contact information to be imported in batches to the form, and then upload the filled form by triggering an "upload file" option, thereby completing batch import of multiple pieces of contact information and configuring the contact information as a call object of a batch call task "after-sales maintenance".

In an embodiment, when the "start dialing" option 604 in the task management interface 600 shown in fig. 6 is detected, the enterprise WeChat client may trigger a batch call operation for the batch call task "after-sales maintenance" to initiate a call for the call object indicated by the batch call task "after-sales maintenance".

Figure 8A is a schematic illustration of a call record management interface provided by an exemplary embodiment. In the process of initiating a call for a call object indicated by the bulk call task "after-sales maintenance", assuming that the currently selected call object is "user 1", the enterprise wechat client may exhibit a call record management interface 800 for the call object as shown in fig. 8A to assist user a in completing the call process for the call object "user 1".

In one embodiment, the call record management interface 800 may include description information for the call object "user 1," such as the description information may include: the name information 802, the head portrait information 804, the group affiliation information 806, the position information 808 in the affiliated group, the industry tag 810 of the affiliated group, the importance degree tag 812, the character feature description tag 814 and the like, so that the user a can quickly know the relevant situation of the call object "user 1", which is helpful for improving the communication efficiency between the two parties.

In one embodiment, the call record management interface 800 can provide historical call information 816 for the call object "user 1," such as the historical call information 816 can include: the number of historical call records (i.e., "4 records" as shown in fig. 8A), the most recent call interval (i.e., "6 days not followed up" as shown in fig. 8A), etc. When it is detected that the user a triggers the historical visiting information 816, the visiting content, the historical visiting time, the visiting executor and the like of the historical visiting record can be specifically displayed to the user a, so that the user a can specifically know the historical visiting condition. The historical visit record can be generated historically by the user A, or can be shared to the user A after being generated historically by other enterprise members in the enterprise AA, so that information sharing of the 'visit record' is realized among a plurality of or all enterprise members in the enterprise AA, and mutual assistance among the enterprise members is facilitated to complete related work. For example, FIG. 8B is a schematic diagram of a historical call record exposure interface in accordance with an exemplary embodiment; based on the trigger operation of the user a on the above historical visiting information 816, a historical visiting record displaying interface 900 as shown in fig. 8B may be shown to display 4 historical visiting records for the above user 1, such as that the first historical visiting record includes "visiting time (i.e. the above historical visiting time)" is "2017-8-21", "visiting content" is "first after-sale return visit, mainly …", "visiting person (i.e. the above visited executor)" is "white", and so on, and further such as that the last historical visiting record includes "visiting time" is "2017-10-30", "visiting content" is "temporary return visit, client request …", "visiting person" is "me (user a)", and so on. Wherein, due to interface limitation, the 'visit content' may not be fully revealed, and the 'visit content' desired to be viewed can be triggered to further browse the full content thereof.

In one embodiment, the call record management interface 800 can provide a call record input box 818 for the call object "user 1" so that the user a can input the call content desired to be recorded in the call record input box 818 during the process of communicating with the call object "user 1", without separately opening a tool such as a notepad or handwriting the related content on a notebook, thereby realizing the fast and efficient recording of the call content. Upon completion of the recording, the call content entered by user a can be generated as a call record for the call object "user 1" by triggering the "submit" option in the call record entry box 818; accordingly, the historical visit information 816 can be updated to "5 records, which are followed up today", and the user a can access and view the historical visit information 816 at any time by triggering, and the visit record can be shared with other members in the enterprise AA, which helps the members in the enterprise to mutually assist in completing related work.

FIG. 9 is a schematic block diagram of an apparatus provided in an exemplary embodiment. Referring to fig. 9, at the hardware level, the apparatus includes a processor 902, an internal bus 904, a network interface 906, a memory 908, and a non-volatile memory 910, but may also include hardware required for other services. The processor 902 reads a corresponding computer program from the non-volatile memory 910 into the memory 908 and then runs the computer program to form a batch call device on a logical level. Of course, besides software implementation, the one or more embodiments in this specification do not exclude other implementations, such as logic devices or combinations of software and hardware, and so on, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.

Referring to fig. 10, in a software implementation, the bulk call device may include:

a first calling unit 1001, which initiates a call to a call object corresponding to a batch call operation in response to the batch call operation initiated by a group member of a group;

a first interface display unit 1002, configured to display a call record management interface for the call object;

the generating unit 1003 generates a call record for the call object according to the input content of the group member in the call record management interface.

Optionally, the first calling unit 1001 is specifically configured to:

detecting that the community members select at least one calling object;

when the group members initiate a batch calling request aiming at the selected calling object, determining that the group members initiate the batch calling operation;

and taking the call object selected by the group member as the call object corresponding to the batch call operation to initiate a call.

Optionally, the first calling unit 1001 is specifically configured to:

when detecting that the group members trigger a batch calling task, determining that the group members initiate the batch calling operation, wherein the batch calling task is pre-created by any group member of the group;

And taking the call object indicated by the batch call task as a call object corresponding to the batch call operation to initiate a call.

Optionally, the first calling unit 1001 is specifically configured to:

and responding to the batch calling operation initiated by the group members of the group, and sequentially initiating calls to calling objects corresponding to the batch calling operation.

Optionally, the first calling unit 1001 is specifically configured to:

and in response to a batch calling operation initiated by group members of a group, initiating a group call to a calling object corresponding to the batch calling operation.

Optionally, the method further includes:

a binding unit 1004 that binds the call record to the community such that at least one other community member of the community obtains access to the call record.

Optionally, the method further includes:

an information display unit 1005, configured to display, in the call record management interface, historical call information for the call target;

the historical visiting information is related to historical batch calling operation, and the calling object belongs to the historical calling object of the historical batch calling operation.

Optionally, the historical visiting information includes at least one of:

Historical visit records, historical visit times, historical visit time, latest visit time and latest visit intervals.

Optionally, the method further includes:

a tag display unit 1006, in the call record management interface, displays a feature description tag for the call object.

Referring to fig. 11, in a software implementation, the bulk call device may include:

a second calling unit 1101, configured to initiate a call to a call object corresponding to a batch call operation in response to the batch call operation initiated by a group member of a group;

a second interface displaying unit 1102 for displaying a call record management interface for the call object, where the call record management interface includes a history call record for the call object.

Optionally, when any group member of the group implements a historical batch call operation, the historical input content of the any group member in the call record management interface for the call object is generated as the historical call record.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.

In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage, quantum memory, graphene-based storage media or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The foregoing description of specific embodiments has been presented for purposes of illustration and description. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

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

It should be understood that although the terms first, second, third, etc. may be used in one or more embodiments of the present description to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of one or more embodiments herein. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.

The above description is only for the purpose of illustrating the preferred embodiments of the one or more embodiments of the present disclosure, and is not intended to limit the scope of the one or more embodiments of the present disclosure, and any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the one or more embodiments of the present disclosure should be included in the scope of the one or more embodiments of the present disclosure.

Claims

1. A batch calling method is applied to a client of a mobile group office platform and comprises the following steps:

responding to a batch calling operation initiated by a group member of a group, initiating a call to a calling object corresponding to the batch calling operation, and comprising: detecting that the community members select a plurality of call objects, wherein the call objects comprise a single contact; when the group members initiate a batch calling request aiming at the selected calling object, determining that the group members initiate the batch calling operation; taking the call object selected by the group member as a call object corresponding to the batch call operation to initiate a call;

in the process of the batch call operation, automatically displaying a call record management interface aiming at the plurality of call objects; in the visit record management interface, historical visit information aiming at the call object is displayed, so that the group members record in the call process to generate corresponding visit records; the historical visiting information is related to historical batch calling operation, and the calling object belongs to the historical calling object of the historical batch calling operation;

Generating a call record aiming at the call object according to the input content of the group members on the call record management interface;

the initiating a call to a call object corresponding to a batch call operation in response to the batch call operation initiated by a group member of a group comprises: and initiating a collective call to a call object corresponding to the batch call operation.

2. The method of claim 1, wherein the initiating a call to a call object corresponding to a bulk call operation in response to the bulk call operation initiated by a community member of a community comprises:

when the fact that the group members trigger a batch calling task is detected, determining that the group members initiate the batch calling operation, wherein the batch calling task is created by the group members who communicate with the calling object, or is created by other group members except the group members who communicate with the calling object and then shared to the group members who communicate with the calling object;

3. The method of claim 1, further comprising:

And binding the call record to the community so that at least one other community member of the community obtains access rights to the call record.

4. The method of claim 1, wherein the historical call information comprises at least one of:

5. The method of claim 1, further comprising:

and displaying a characteristic description label aiming at the call object in the call record management interface.

6. A batch calling device applied to a client of a mobile group office platform comprises:

the first calling unit responds to a batch calling operation initiated by a group member of a group, and initiates a call to a calling object corresponding to the batch calling operation, and comprises: detecting that the community members select a plurality of call objects, wherein the call objects comprise a single contact; when the group members initiate a batch call request aiming at the selected call object, determining that the group members initiate the batch call operation; taking the call object selected by the group member as the call object corresponding to the batch call operation to initiate a call;

The first interface display unit automatically displays a call record management interface aiming at the plurality of call objects in the batch call operation process; in the call record management interface, historical call information aiming at the call object is displayed, so that the group members record in the call process to generate corresponding call records; the historical visit information is related to historical batch calling operation, and the calling object belongs to a historical calling object of the historical batch calling operation;

the generating unit is used for generating the call records aiming at the call objects according to the input content of the group members on the call record management interface;

the first calling unit is specifically configured to: and initiating a collective call to a call object corresponding to the batch call operation.

7. The apparatus of claim 6, wherein the first call unit is specifically configured to:

8. The apparatus of claim 6, further comprising:

and the binding unit is used for binding the visit record to the community so as to ensure that at least one other community member of the community obtains the access right to the visit record.

9. The apparatus of claim 6, wherein the historical call information comprises at least one of:

10. The apparatus of claim 6, further comprising:

and the label display unit is used for displaying the feature description label aiming at the call object in the call record management interface.