WO2019091323A1

WO2019091323A1 - Batch calling method and device

Info

Publication number: WO2019091323A1
Application number: PCT/CN2018/113336
Authority: WO
Inventors: 马文博; 张腊梅; 康彦荣
Original assignee: 阿里巴巴集团控股有限公司
Priority date: 2017-11-08
Filing date: 2018-11-01
Publication date: 2019-05-16
Also published as: CN109756348A; TW201939975A; CN109756348B

Abstract

One or more embodiments of the present invention provide a batch calling method and device. The method comprises: in response to a batch calling operation initiated by a member of a group, making a call to a calling object corresponding to the batch calling operation; displaying a visiting record management interface for the calling object; and generating a visiting record for the calling object according to the content input by the group member in the visiting record management interface.

Description

Batch calling method and device

The present application claims the priority of the Japanese Patent Application Serial No. JP-A-------------

Technical field

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

Background technique

In the related technology, the mobile group office platform is more and more widely used in the business processes of various groups such as enterprises, educational institutions, government agencies, etc., which can not only improve communication efficiency between users, reduce communication costs, but also be effective. Improve user event processing efficiency and office efficiency.

Summary of the invention

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

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

According to a first aspect of one or more embodiments of the present specification, a method for batch calling is provided, comprising:

Initiating a call to a call object corresponding to the batch call operation in response to a batch call operation initiated by a group member of the community;

Presenting a visit record management interface for the call object;

Generating a visit record for the call object according to the input content of the group member in the visit record management interface.

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

A visit record management interface for the call object is displayed, the visit record management interface including a historical visit record for the call object.

According to a third aspect of one or more embodiments of the present specification, a batch call device is provided, comprising:

The first calling unit initiates a call to the call object corresponding to the batch call operation in response to the batch call operation initiated by the community member of the community;

a first interface display unit, displaying a visit record management interface for the call object;

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

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

The second calling unit initiates a call to the call object corresponding to the batch call operation in response to the batch call operation initiated by the community member of the community;

The second interface display unit displays a visit record management interface for the call object, where the visit record management interface includes a history visit record for the call object.

DRAWINGS

FIG. 1 is a schematic structural diagram of a batch call system according to an exemplary embodiment;

2 is a flowchart of a method for batch calling provided by an exemplary embodiment;

FIG. 3 is a flowchart of another method for batch 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 schematic diagram of a dialing setting interface provided by an exemplary embodiment; FIG.

FIG. 6 is a schematic diagram of a task management interface according to an exemplary embodiment; FIG.

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

FIG. 8A is a schematic diagram of a visit record management interface provided by an exemplary embodiment; FIG.

FIG. 8B is a schematic diagram of a historical visit record display interface provided by an exemplary embodiment; FIG.

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

FIG. 10 is a block diagram of a batch call device according to an exemplary embodiment; FIG.

11 is a block diagram of another batch calling device provided by an exemplary embodiment.

Detailed ways

Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. The following description refers to the same or similar elements in the different figures unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with one or more embodiments of the specification. Instead, they are merely examples of devices and methods consistent with aspects of one or more embodiments of the present specification as detailed in the appended claims.

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

FIG. 1 is a schematic structural diagram of a batch call system according to an exemplary embodiment. As shown in FIG. 1, the system may include a server 11, a network 12, and a number of electronic devices, such as a mobile phone 13, a PC 14, and the like.

The server 11 may be a physical server including a separate host, or the server 11 may be a virtual server hosted by the host cluster. During the running process, the server 11 can run a server-side program of an application to implement related business functions of the application. For example, when the server 11 runs the program of the mobile group office platform, the mobile group can be implemented. The server side of the platform for the bulk call scenario used to implement this specification.

In this embodiment, the mobile group office platform can not only realize the communication function, but also can be used as an integrated function platform for many other functions, such as approval events (such as leave, office item application, financial and other approval events), attendance events. The processing of internal events of the group, such as task events, log events, and the like, such as ordering, purchasing, and other external events of the group, one or more embodiments of the present specification are not limited thereto.

More specifically, the mobile group office platform can be carried in instant messaging applications in related technologies, such as enterprise instant messaging (EIM) applications, such as Skype For.

Microsoft

Wait. Of course, 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 implement more functions such as the above, which will not be described here.

The mobile phone 13 and the PC 14 are only some types of electronic devices that the user can use. In fact, users obviously can also use electronic devices such as tablet devices, notebook computers, PDAs (Personal Digital Assistants), wearable devices (such as smart glasses, smart watches, etc.), etc. Various embodiments do not limit this. During operation, the electronic device can run a client-side program of an application to implement related business functions of the application, for example, when the electronic device runs a program of the mobile group office platform, the mobile device can be implemented as the mobile device. The client of the group office platform, used in the bulk call scheme for implementing this specification.

It should be noted that the application of the client of the mobile group office platform can be pre-installed on the electronic device so that the client can be launched and run on the electronic device; of course, when adopting an online "customer such as HTML5 technology" At the end, the client can be obtained and run without installing the corresponding application on the electronic device.

For the network 12 in which the mobile phone 13, the PC 14 and the server 11 interact, a plurality of types of wired or wireless networks may be included. In an embodiment, the network 12 may include a Public Switched Telephone Network (PSTN) and the Internet.

2 is a flow chart of a method for batch calling provided by an exemplary embodiment. As shown in FIG. 2, the method may include the following steps:

Step 202: In response to a batch call operation initiated by a community member of the community, initiate a call to a call object corresponding to the batch call operation.

In an embodiment, the group member can actively select the call object corresponding to the batch call operation; wherein the call object can exist in multiple sources, such as an address book, a buddy list, a group organization structure, etc., which is not limited in this specification. And determining, by the group member, the batch call operation, when the group member initiates a bulk call request for the selected call object, so that the group can be The call object selected by the member serves as a call object corresponding to the batch call operation to initiate a call.

In an embodiment, any group member of the community may pre-create a batch call task and specify a call object in the batch call task; and then, when detecting that the community member triggers a batch call task, may determine the The group member initiates the batch call operation, and uses the call object indicated by the batch call task as the call object corresponding to the batch call operation to initiate a call. Therefore, the batch call task in this embodiment can be created by the member of the group. It can also be created by other community members in the community and then shared with the member of the group.

In an embodiment, the above-mentioned group may include various types of organizations such as enterprises, departments, schools, governments, hospitals, and troops, and this specification does not limit this.

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

In an embodiment, in response to a bulk call operation initiated by a community member of the community, a collective call may be initiated to a call object corresponding to the bulk call operation. For example, when a batch call operation corresponds to 20 call objects, a call can be initiated to multiple call objects at the same time, thereby implementing a collective call with the call objects, such as a conference call, etc., wherein the call can be initiated for all 20 call objects. For a group call, only one call needs to be implemented, or a group call can be initiated for a part of the 20 call objects. For example, each time a call is initiated for 10 call objects, two calls need to be performed.

Step 204, displaying a visit record management interface for the call object.

In an embodiment, in the visit record management interface, historical visit information for the call object may be displayed, the history visit information is related to a historical bulk call operation, and the call object belongs to the historical bulk call operation. Historical call object. For example, the history visit information may include at least one of the following: a history visit record, a history visit time, a history visit time, a recent visit time, a recent visit interval, and the like, which are not limited in the specification. By displaying historical visit information, group members can quickly understand the history of visits to the call object, thereby determining or adjusting the communication content, communication tone, communication process, etc. of the current visit to improve the communication efficiency between the two parties.

In an embodiment, in the visit record management interface, a feature description tag for the call object may be displayed, and the feature description tag may be used to describe a feature of the call object in several dimensions; for example, the dimension may include The type of the group, the position in the group, the importance, the ease of communication, etc., this specification does not limit this.

Step 206: Generate a visit record for the call object according to the input content of the community member on the visit record management interface.

In an embodiment, during the process of initiating a batch call operation for multiple call objects, the visit record management interface for each call object is automatically displayed, and the group member is not required to manually open a record tool such as a notebook, so that the group members can be in the call process. Record communication information and generate corresponding visit records in a timely manner. At the same time, by recording the visit records, it is convenient to review and recall the corresponding communication process afterwards, which helps to efficiently deal with related events.

In an embodiment, the visit record may be bound to the community, so that at least one other group member of the community obtains access rights to the visit record, that is, information sharing for the visit record, facilitating the group Multiple group members in the group can cooperate with each other in the event of events related to the call object, which helps to improve processing efficiency.

FIG. 3 is a flow chart of another batch calling method provided by an exemplary embodiment. As shown in FIG. 3, the method may include the following steps:

Step 302: In response to a batch call operation initiated by a community member of the community, initiate a call to a call object corresponding to the batch call operation.

Step 304: Display a visit record management interface for the call object, where the visit record management interface includes a history visit record for the call object.

In an embodiment, when any group member of the community implements a historical batch call operation, the history input content of the any group member in the visit record management interface for the call object is generated as the history visit record. . Therefore, by viewing the historical visit record, it is convenient to review and recall the corresponding communication process afterwards, which helps to efficiently deal with related events.

In an embodiment, the historical visit record may be created by the group members themselves, or may be created by other group members in the group to achieve information sharing between the members of each group. By displaying historical visit records, group members can quickly understand the history of visits to the call object, thereby determining or adjusting the communication content, communication tone, communication process, etc. of the current visit to improve the communication efficiency between the two parties.

For ease of understanding, the technical solution of one or more embodiments of the present specification will be described by taking the enterprise instant messaging application "Enterprise WeChat" as an example. It is assumed that the enterprise WeChat server is running on the server 11, and the enterprise WeChat client is running on the PC 14, and the enterprise WeChat client is logged in with the registered account of the user A, and the user A belongs to the 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, the enterprise WeChat client running on the PC 14 can present the task list interface 400 for implementing the bulk call function to the user A; the task list interface 400 includes a number of batch call tasks, such as shown in FIG. Three batch call tasks, the task names are “Project X Negotiation”, “Potential Customer” and “After Sales Maintenance”. In addition to the “task name”, the task list interface 400 can also display other related information such as “calling number” and “progress” of each batch of calling tasks; taking the batch calling task “after-sales maintenance” as an example, the batch calling task The indicated number of calls is 150, and the progress of the executed bulk call operation is 30% (ie, the batch call has been completed for 30% of the 150 people, and the remaining 70% has not yet implemented the bulk call).

In an embodiment, the batch call task shown by task list interface 400 may include tasks created by user A himself. 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 can provide the user A with a new task function, and the user A determines the task name and all the batch calls required for the task. Information such as the call object, for example, the call object may be the enterprise WeChat friend of the enterprise A in the enterprise WeChat client, the external contact of the enterprise AA (that is, the enterprise WeChat maintained, related to the enterprise AA, and not belonging to the enterprise AA. Contact), local address book maintained on PC14, cloud address book, etc., even contacts created by user A temporarily, this specification does not limit this.

In an embodiment, the batch call task shown by task list interface 400 may include tasks created by other users in enterprise AA (other than user A). For example, the user B, the user C, and the like in the enterprise AA pre-create a batch call task, and configure the batch call task in the enterprise AA, so that all enterprise members in the enterprise AA can view the related batch call task, and thus the user A The task list interface 400 as shown in FIG. 4 and the related bulk call tasks in the task list interface 400 can be viewed on the enterprise WeChat client.

In an embodiment, the task list interface 400 can include a dialing setup option 404 as shown in FIG. 4 for the user A to set relevant parameters of the enterprise WeChat client when implementing a bulk call. For example, FIG. 5 is a schematic diagram of a dialing setting interface provided by an exemplary embodiment. As shown in FIG. 5, based on the triggering operation of the dialing setting option 404 by the user A, the enterprise WeChat client may display the dialing setting interface 500. To set the relevant parameters.

In an embodiment, when the user A has multiple home enterprises, for example, the user A belongs to the enterprise AA and the enterprise BB at the same time, the enterprise WeChat client can provide the “selection” as shown in FIG. 5 in the dial setting interface 500. Initiating an enterprise parameter to select the enterprise used to initiate the bulk call and its phone number (each enterprise has a corresponding phone number); for example, when user A selects the enterprise AA, it will adopt the association associated with the enterprise AA. The telephone number "0571-88886666" initiates a batch call, and the caller number viewed by the called party is the telephone number "0571-88886666" of the enterprise AA.

In an embodiment, the enterprise WeChat client can provide the "no answer ringing duration" parameter as shown in FIG. 5 in the dial setting interface 500, and provides several options for the parameter, such as "15 seconds", "30 seconds", "45 seconds", etc., can be selected by user A: the length of time (ie, the ringing duration) of waiting for the called party to answer before the called party answers.

In an embodiment, the enterprise WeChat client can provide the "call after answering" parameter as shown in FIG. 5 in the dialing setting interface 500; wherein, when user A logs in to the enterprise on the PC 14 and the used mobile phone respectively When WeChat registers an account, the enterprise WeChat client can provide several options for this parameter, such as "computer (ie PC14)", "mobile phone (ie user A login phone)", etc., which can be selected by user A: through computer or mobile phone Complete the call with the called party.

In an embodiment, the task list interface 400 shown in FIG. 4 also provides an operation option for the established batch call task; taking the batch call task "after-sales maintenance" as an example, the operation options for the task may include deleting Option 406, enter task option 408, etc., the delete option 406 is used to delete the batch call task "after-sales maintenance", and the enter task option 408 is available for 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 triggering operation of the user A to the entry task option 408 as shown in FIG. 4, the enterprise WeChat client can transfer to the task management interface 600 shown in FIG. 6 for management operations for the batch call task "after-sales 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-sales maintenance", including "customer name (ie, the name of the call object)", "phone number", " Status, etc., for example, "Customer 1" has a phone number of "139xxxxxxxx" and a status of "Not Visited".

In an embodiment, a separate management operation can be implemented for each call object shown by task management interface 600. For example, by triggering the "Call" option corresponding to "Customer 1", a separate call operation can be initiated for the "Customer 1"; by triggering the "More" option corresponding to "Customer 1", the "Customer 1" can be implemented for the "Customer 1" Delete, modify, etc.

In an embodiment, management operations may be implemented for bulk call tasks "post-sales maintenance." FIG. 7 is a schematic diagram of an object import interface provided by an exemplary embodiment; when it is detected that the user A triggers the import visit object option 602 as shown in FIG. 6, the enterprise WeChat client may be as shown in FIG. 7. The object import interface 700 enables the user A to add more call objects (ie, visited objects) to the batch call task "after-sales maintenance" based on the object import interface 700. For example, an enterprise WeChat client can 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 the call object to be added does not belong to the enterprise AA, but has an association relationship with the enterprise AA (for example, there is a business transaction, etc.), the call objects can be configured as the enterprise AA. The external contact of the enterprise, then by triggering the "select" option corresponding to the "already be an external contact of the enterprise" type in the object import interface 700, the enterprise WeChat client can display the enterprise external contact list of the enterprise AA to the user A, The user A selects the call object that wants to import the batch call task "after-sales maintenance".

For non-enterprise external contacts, the object import interface 700 provides a type that has not been added to the enterprise external contact, and allows user A to implement a single import or batch import. When detecting the "add" option corresponding to "single import" in the user A trigger object import interface 700, the enterprise WeChat client may provide the user A with a list of friends, a list of contacts, etc., for the user A to select the desired batch to import. A single call object that calls the task "post-sales maintenance." When the user A wishes to adopt the batch importing scheme, the user A may first trigger the “Download Form” option in the object import interface 700, download the corresponding contact information to fill out the form, and then add the contact information of the required batch import to the In the table, the completed form is uploaded by triggering the “upload file” option, thereby completing batch import of multiple contact information and configuring it as a call object for the 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 The call object indicated by the batch call task "After-sales maintenance" initiates a call.

FIG. 8A is a schematic diagram of a visit record management interface provided by an exemplary embodiment. The enterprise WeChat client initiates a call for the call object indicated by the "post-sale maintenance" of the batch call task, assuming that the currently selected call object is "user 1", and the enterprise WeChat client can exhibit as shown in FIG. 8A. The visit record management interface 800 for the call object is to assist the user A to complete the call process for the call object "user 1".

In an embodiment, the visit record management interface 800 may include description information for the call object "user 1", such as the description information may include: name information 802, avatar information 804, group attribution information 806, positions in the belonging group The information 808, the industry label 810 of the group, the importance level label 812, the personality feature description label 814, and the like, so that the user A can quickly understand the related situation of the call object "user 1", and help to improve the communication efficiency between the two parties.

In an embodiment, the visit record management interface 800 may provide historical visit information 816 for the call object "user 1", for example, the history visit information 816 may include: the number of history visit records (ie, as shown in FIG. 8A) 4 records "), the recent visit interval (that is, "6 days not followed up" shown in Fig. 8A). When it is detected that the user A triggers the above-mentioned historical visit information 816, the user A may also be specifically shown the visited content of the historical visit record, the historical visit time, the visited performer, and the like, so that the user A can specifically understand the historical visit situation. The historical visit record may be generated by the user A in the history, or may be generated by the other enterprise members in the enterprise AA and shared with the user A, so as to be implemented between multiple or all enterprise members within the enterprise AA. The sharing of information on the “visiting records” helps the members of the company to assist each other in completing related work. For example, FIG. 8B is a schematic diagram of a historical visit record display interface provided by an exemplary embodiment. Based on the trigger operation of the historical visit information 816 by the user A, the historical visit record display interface 900 shown in FIG. 8B may be displayed. To display the four historical visit records for the above user 1, for example, the first history visit record includes "the visit time (ie, the above-mentioned historical visit time)" as "2017-8-21", "visit content" is "first sale" Return visit, mainly...", "visitor (that is, the executor of the above visit)" is "Xiaobai", etc., for example, the recent history visit record includes "visit time" as "2017-10-30", "visit content "For "temporary return visit, customer request...", "visitor" is "I (user A)" and so on. Among them, due to interface restrictions, it may not be possible to fully display the "visit content", and you can further browse the full content by triggering the "visit content" you want to view.

In an embodiment, the visit record management interface 800 can provide a visit record input box 818 for the call object "user 1" so that the user A can communicate with the call object "user 1" during the visit. The record input box 818 inputs the visit content desired to be recorded, without separately opening a tool such as a notepad or handwriting related content on a notebook, thereby realizing fast and efficient recording of the visited content. After the recording is completed, by triggering the "submit" option in the visit record input box 818, the visit content input by the user A can be generated as a visit record for the call object "user 1"; accordingly, the history visit information 816 can be Updated to "5 records, followed today", and User A can access and view at any time by triggering historical visit information 816, and the visit record can also be shared with other corporate members in Enterprise AA, contributing to the business Members assist each other in completing related work.

FIG. 9 is a schematic structural diagram of an apparatus provided by an exemplary embodiment. Referring to FIG. 9, at the hardware level, the device includes a processor 902, an internal bus 904, a network interface 906, a memory 908, and a non-volatile memory 910, and of course may also include hardware required for other services. The processor 902 reads the corresponding computer program from the non-volatile memory 910 into the memory 908 and then operates to form a batch call device on a logical level. Of course, in addition to the software implementation, one or more embodiments of the present specification do not exclude other implementation manners, such as a logic device or a combination of software and hardware, etc., that is, the execution body of the following processing flow is not limited to each. A logical unit, which can also be a hardware or logic device.

Referring to FIG. 10, in a software implementation, the batch calling device may include:

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

The first interface display unit 1002 displays a visit record management interface for the call object;

The generating unit 1003 generates a visit record for the call object according to the input content of the community member on the visit record management interface.

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

Detecting that the group member selects at least one call object;

When the group member initiates a bulk call request for the selected call object, determining that the community member initiates the bulk call operation;

The call object selected by the group member is used as a call object corresponding to the batch call operation to initiate a call.

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

When it is detected that the community member triggers the batch call task, determining that the community member initiates the bulk call operation, where the batch call task is pre-created by any group member of the community;

The call object indicated by the batch call task is used as a call object corresponding to the batch call operation to initiate a call.

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

In response to a batch call operation initiated by a group member of the community, a call is sequentially initiated to the call object corresponding to the batch call operation.

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

A group call is initiated to a call object corresponding to the batch call operation in response to a bulk call operation initiated by a group member of the community.

Optionally, it also includes:

The binding unit 1004 binds the visited record to the community to enable at least one other community member of the community to gain access to the visited record.

Optionally, it also includes:

The information display unit 1005 displays, in the visit record management interface, historical visit information for the call object;

The historical visit information is related to a historical bulk call operation, and the call object belongs to a historical call object of the historical bulk call operation.

Optionally, the historical visit information includes at least one of the following:

Historical visit records, number of historical visits, historical visits, recent visits, and recent visits.

Optionally, it also includes:

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

Referring to FIG. 11, in a software implementation, the batch calling device may include:

The second calling unit 1101, in response to the batch call operation initiated by the community member of the community, initiates a call to the call object corresponding to the batch call operation;

The second interface display unit 1102 displays a visit record management interface for the call object, where the visit record management interface includes a history visit record for the call object.

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

The system, device, module or unit illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function. A typical implementation device is a computer, and the specific form of the computer may be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email transceiver, and a game control. A combination of a tablet, a tablet, a wearable device, or 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 non-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory. Memory is an example of a computer readable medium.

Computer readable media includes both permanent and non-persistent, removable and non-removable media. Information storage can be implemented by any method or technology. The information can be computer readable instructions, data structures, modules of programs, 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 disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, Magnetic cassette tape, disk storage, quantum memory, graphene-based storage media or other magnetic storage devices or any other non-transporting media can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary storage of computer readable media, such as modulated data signals and carrier waves.

It is also to be understood that the terms "comprises" or "comprising" or "comprising" or any other variations are intended to encompass a non-exclusive inclusion, such that a process, method, article, Other elements not explicitly listed, or elements that are inherent to such a process, method, commodity, or equipment. An element defined by the phrase "comprising a ..." does not exclude the presence of additional equivalent elements in the process, method, item, or device including the element.

The foregoing description of the specific embodiments of the specification has been described. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than the embodiments and still achieve the desired results. In addition, the processes depicted in the figures are not necessarily in a particular order or in a sequential order to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

The terms used in one or more embodiments of the present specification are for the purpose of describing particular embodiments, and are not intended to limit one or more embodiments. The singular forms "a", "the", and "the" 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 to describe various information in one or more embodiments of the specification, the information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, the first information may also be referred to as the second information without departing from the scope of one or more embodiments of the present disclosure. Similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "when" or "when" or "in response to a determination."

The above is only a preferred embodiment of one or more embodiments of the present specification, and is not intended to limit one or more embodiments of the present specification, which is within the spirit and principles of one or more embodiments of the present specification, Any modifications, equivalent substitutions, improvements, etc., are intended to be included within the scope of the protection of one or more embodiments.

Claims

A batch calling method, comprising:

Initiating a call to a call object corresponding to the batch call operation in response to a batch call operation initiated by a group member of the community;

Presenting a visit record management interface for the call object;

Generating a visit record for the call object according to the input content of the group member in the visit record management interface.
The method according to claim 1, wherein the initiating a call to the call object corresponding to the batch call operation in response to the batch call operation initiated by the community member of the community comprises:

Detecting that the group member selects at least one call object;

When the group member initiates a bulk call request for the selected call object, determining that the community member initiates the bulk call operation;

The call object selected by the group member is used as a call object corresponding to the batch call operation to initiate a call.
The method according to claim 1, wherein the initiating a call to the call object corresponding to the batch call operation in response to the batch call operation initiated by the community member of the community comprises:

When it is detected that the community member triggers the batch call task, determining that the community member initiates the bulk call operation, where the batch call task is pre-created by any group member of the community;

The call object indicated by the batch call task is used as a call object corresponding to the batch call operation to initiate a call.
The method according to claim 1, wherein the initiating a call to the call object corresponding to the batch call operation in response to the batch call operation initiated by the community member of the community comprises:

In response to a batch call operation initiated by a group member of the community, a call is sequentially initiated to the call object corresponding to the batch call operation.
The method according to claim 1, wherein the initiating a call to the call object corresponding to the batch call operation in response to the batch call operation initiated by the community member of the community comprises:

A group call is initiated to a call object corresponding to the batch call operation in response to a bulk call operation initiated by a group member of the community.
The method of claim 1 further comprising:

The visit record is bound to the community such that at least one other group member of the community gains access to the visit record.
The method of claim 1 further comprising:

Displaying historical visit information for the call object in the visit record management interface;

The historical visit information is related to a historical bulk call operation, and the call object belongs to a historical call object of the historical bulk call operation.
The method of claim 7, wherein the historical visit information comprises at least one of the following:

Historical visit records, number of historical visits, historical visits, recent visits, and recent visits.
The method of claim 1 further comprising:

In the visit record management interface, a feature description tag for the call object is displayed.
A batch calling method, comprising:

Initiating a call to a call object corresponding to the batch call operation in response to a batch call operation initiated by a group member of the community;

A visit record management interface for the call object is displayed, the visit record management interface including a historical visit record for the call object.
The method according to claim 10, wherein when any group member of the community implements a historical batch call operation, the history input of the any group member in the visit record management interface for the call object is Generated as the history visit record.
A batch calling device, comprising:

The first calling unit initiates a call to the call object corresponding to the batch call operation in response to the batch call operation initiated by the community member of the community;

a first interface display unit, displaying a visit record management interface for the call object;

The generating unit generates a visit record for the call object according to the input content of the group member in the visit record management interface.
The device according to claim 12, wherein the first calling unit is specifically configured to:

Detecting that the group member selects at least one call object;

When the group member initiates a bulk call request for the selected call object, determining that the community member initiates the bulk call operation;

The call object selected by the group member is used as a call object corresponding to the batch call operation to initiate a call.
The device according to claim 12, wherein the first calling unit is specifically configured to:

When it is detected that the community member triggers the batch call task, determining that the community member initiates the bulk call operation, where the batch call task is pre-created by any group member of the community;

The call object indicated by the batch call task is used as a call object corresponding to the batch call operation to initiate a call.
The device according to claim 12, wherein the first calling unit is specifically configured to:

In response to a batch call operation initiated by a group member of the community, a call is sequentially initiated to the call object corresponding to the batch call operation.
The device according to claim 12, wherein the first calling unit is specifically configured to:

A group call is initiated to a call object corresponding to the batch call operation in response to a bulk call operation initiated by a group member of the community.
The device according to claim 12, further comprising:

A binding unit binds the visited record to the community to enable at least one other community member of the community to gain access to the visited record.
The device according to claim 12, further comprising:

An information display unit, in the visit record management interface, displaying historical visit information for the call object;

The historical visit information is related to a historical bulk call operation, and the call object belongs to a historical call object of the historical bulk call operation.
The apparatus according to claim 18, wherein said historical visit information comprises at least one of the following:

Historical visit records, number of historical visits, historical visits, recent visits, and recent visits.
The device according to claim 12, further comprising:

a tag display unit that displays a feature description tag for the call object in the visit record management interface.
A batch calling device, comprising:

The second calling unit initiates a call to the call object corresponding to the batch call operation in response to the batch call operation initiated by the community member of the community;

The second interface display unit displays a visit record management interface for the call object, where the visit record management interface includes a history visit record for the call object.
The apparatus according to claim 21, wherein when any group member of the community performs a historical batch call operation, the history input content of the arbitrary group member in the visit record management interface for the call object is Generated as the history visit record.