JP2020149662A - Business support system - Google Patents

Abstract

To provide a business support system capable of properly managing many inquiries from a head office in business activities.SOLUTION: A manager at a head office creates a piece of information identifying the content of a matter requesting a reply from a branch (report creation information) (S1). When the report creation information is stored in a first data server, a Web server (control unit) makes an inquiry based thereon to a branch office (S2). The control unit recognizes a received reply and a report management ID therein; thereby recognizes that this reply is to the inquiry of (S1) (S5). When recognizing that there is a branch office that has not replied to the inquiry (S11: No), the control unit transmits an email of reply request (dunning) to the branch office (branch office PC) (S8).SELECTED DRAWING: Figure 3

Description

The present invention relates to a sales support system for exchanging information necessary for sales activities between a headquarters and a branch office.

A sales support system for managing products and selling products using a network is widely used. In particular, when selling various financial products (securities, etc.) that are commercial products at financial institutions, securities companies, etc., their properties are significantly different from other products, and many complicated procedures and restrictive conditions are imposed when buying and selling them. To. For this reason, when selling such products, it is essential to exchange a large amount of information between the customer and the branch office, between the branch office and the headquarters, between the branch offices, and within the branch office.

For example, when selling financial products, it is required that the sales staff does not act in a way that violates compliance with the customer. Patent Document 2 describes a customer correspondence management system that stores a call record between a salesperson and a customer as call information and shares this call information between the headquarters side and the branch side.

In addition, the sales support system uses a network to link with the personnel information system and stores personnel information. In addition, for example, the title, department name, and old department name are retained in the personnel information.

In addition, for example, instead of recognizing a single piece of information in common between the headquarters side and the branch office, for example, the headquarters makes an inquiry to the branch office, and the branch office responds to this inquiry. , The headquarters may aggregate this answer. This answer is, for example, an important business matter obtained on the branch side. At this time, this inquiry is made in the form of sending a file, and when sending this file from the headquarters to multiple branches, this file is divided into appropriate units (branches, sales staff, etc.) and sent. It may be preferable to do so. After that, the headquarters side recognizes the input results obtained from all the branches. Patent Document 2 integrates files obtained from each branch after properly dividing and properly recognizing the presence or absence of subsequent answers (returning files after entry), especially during such operations. By doing so, a system is described in which the headquarters side can easily recognize the contents of the answers obtained from each branch side.

Japanese Unexamined Patent Publication No. 2012-234269 Japanese Unexamined Patent Publication No. 2018-55332

When the number of inquiries issued from the headquarters side is multiple, it is required to properly recognize the correspondence between the transmitted contents and the (received) contents after the reply. In addition, when multiple types of such inquiries are received on the branch side, progress management of the answers is also required. In the past, this management was performed by the sales staff on the branch side or the manager on the branch side, so it is not easy to manage this progress, especially when the number and types of inquiries are large, or there are many mistakes in this management. Occurred. In addition, when the person in charge of the branch changed due to a personnel change, the answer was not given. For this reason, a sales support system that can properly manage the number of inquiries made by the headquarters in sales activities has been desired.

The present invention has been made in view of such a situation, and an object of the present invention is to solve the above problems.

The present invention is a sales support system for making inquiries from the headquarters side to a plurality of branch offices and answers to the inquiries from the branch office to the headquarters side via a network, and for each of the plurality of inquiries. A storage unit that stores the report creation information whose contents are specified after assigning an identification number, a display unit that displays the contents of the report creation information, and the inquiry corresponding to the report creation information based on the report creation information. To the branch side, and by recognizing the answer obtained from the branch side by the identification number, a control unit that creates report response information that specifies the identification number and the content of the answer and stores it in the storage unit. And.
Further, the control unit recognizes the answer obtained from the branch side by the identification number, determines whether or not the answer corresponding to the inquiry is obtained from the branch, and is satisfied with the branch. If it is recognized that the above answer has not been obtained, the personnel information of the branch is obtained from the personnel information system via the network, and based on the personnel information, the respondent of the answer or the branch side is re-introduced. You may send a response request.
Further, the storage unit stores the report attachment file management information, which is information for identifying the attached file attached at the time of the inquiry in correspondence with the identification number for each branch that transmits the inquiry, and controls the control. The department may attach the attachment file based on the report attachment file management information and the report creation information and collectively transmit the inquiry to the plurality of branches.
In addition, the control unit stores the report creation information, the report response information, and the report attachment file management information corresponding to the inquiry and the answer made in the past, and the report creation information and the report response information. , And the content of the report attachment file management information may be displayed on the display unit, and the search may be performed in the content by specifying the search condition by the operator.
Further, the control unit may make the inquiry corresponding to the report creation information to the branch side based on the report creation information at a date and time specified in advance.
Further, the control unit recognizes the answer obtained from the branch side by the identification number, determines whether or not the answer corresponding to the inquiry is obtained from the branch, and determines whether or not the answer corresponding to the inquiry is obtained from the branch. When it is recognized that the answer to the inquiry has not been obtained, a warning may be displayed on the display unit and a reminder may be sent to the branch side.
Further, the control unit may determine whether or not the answer corresponding to the inquiry has been obtained from the branch office at the time of starting the system or at a predetermined time.

According to the present invention, when the number of inquiries made from the headquarters side is large in sales activities, the management can be appropriately performed.

It is a figure which shows the structure when the sales support system which concerns on embodiment is used. It is a block diagram which shows the structure of the headquarters system in the sales support system which concerns on embodiment. It is a flowchart which shows the operation of the sales support system which concerns on embodiment. This is a specific example of report creation information used in the sales support system according to the embodiment. This is a specific example when inquiring about the report attachment file management information used in the sales support system according to the embodiment. This is a specific example of report response information used in the sales support system according to the embodiment. This is an example of the report attachment file management information used in the sales support system according to the embodiment updated at the time of reply. This is an example of displaying a list of inquiry cases displayed in the sales support system according to the embodiment. This is an example of report management event information displayed in the sales support system according to the embodiment.

Next, a mode for carrying out the present invention will be specifically described with reference to the drawings. Here, the sales support system according to the embodiment of the present invention is a sales activity of a product, for example, a financial product, for which it is effective to exchange a lot of information (files) between the headquarters and a plurality of branches in the sales activity. Used for.

FIG. 1 is a diagram showing the entire configuration when the sales support system 1 according to the embodiment of the present invention is used. The sales support system 1 includes a headquarters system 10 operated by a person in charge on the headquarters side, and a branch office PC (personal computer) 100 connected to the headquarters system 10 via a network N and provided for each branch. A mail server 200 for delivering e-mails is also connected to this network N, and e-mails exchanged between the headquarters system 10 and the branch office PC 100 are transmitted and received via the mail server 200. In addition, since the personnel information system 300 that manages the personnel information (latest department, etc.) of the person in charge, the person in charge, etc. at the headquarters or each branch is also connected to the network N, the headquarters system 10 or the like is connected to this personnel information. Can also be obtained. The branch PC 100 is an ordinary personal computer, and is provided with at least a display unit that is a display for displaying information, an operation unit that accepts operations by an operator, and a control unit that includes a CPU that controls the entire system.

The headquarters system 10 includes a Web server 20 that is the main body of operation, a first data server 30 (storage unit) that mainly stores (stores) and manages data, and a second data server 40. The data (information) stored in the first data server 30 and the second data server 40 is mainly transmitted from the Web server 20 to the branch PC 100 via the network N, or transmitted from the branch PC 100 to the Web server 20. It is data, data created by the Web server 20 accompanying this data, or personnel information. A well-known file transmission (transfer) method can be used for transmission of such data.

FIG. 2 is a block diagram showing a configuration on the headquarters system 10 side. Here, the Web server 20 is provided with a control unit 21 that controls the entire Web server 20. Further, an operation unit 22 for receiving the operation of the person in charge (headquarters side person in charge) for the Web server 20, and a display unit 23 which is a display for displaying various information at this time are provided. Further, a network connection unit 24 for transmitting and receiving data via the network N and a character information recognition unit 25 for recognizing a character string in a file composed of character information such as e-mail are also provided. Since it is preferable that the operation of the Web server 20 is performed only by an authorized person in charge of the headquarters, the control unit 21 only recognizes the input of the preset password by the operation unit 22 after that. Set to accept operations.

Although the description of the first data server 30 and the second data server 40 is simplified in FIG. 2, these also have the same configuration as the Web server 20 in practice. The first data server 30 and the second data server 40 each have a main purpose of storing and accumulating data, and the contents of the data (files) stored by these will be described later.

FIG. 3 is a flowchart showing the operation of the sales support system 1. Here, this operation is performed by a person in charge (headquarters side manager) in the headquarters system 10 and a sales person or a branch office person in the branch office PC100. Here, first, the head office manager specifies the information (report creation information) that specifies the content of the matter for which a response is requested from the branch office, and the report attachment file that specifies the attachment file, if any. Create management information (S1).

FIG. 4 is a specific example of the report creation information at this time. Here, the headquarters side asks the branch side to (1) request the customer to conduct a questionnaire on the products they are interested in, and (2) inquire about the required number of calendars to be distributed to the customer. There is. Here, as the "title" of the inquiry, a "questionnaire" is set for (1) and a "calendar" is set for (2), and the contents are described in the "request contents", and each answer is given. A deadline has been set. In order to identify this inquiry, the control unit 21 assigns a report management ID (identification number) of 1 to (1) and 2 to (2) for each case. This report creation information is stored in the first data server 30. After that, inquiries made from the headquarters side to the branch side are identified by the above report management ID. The contents of FIG. 4 can be set by, for example, the control unit 21 displaying a CSV format file on the display unit 23 and having the operator (headquarters side manager) input items other than the report management ID.

Further, FIG. 5 is a specific example of the report attachment file management information created at this time. Here, this information is created for each attached file, and four attached files are specified only for the case (1) (report management ID = 1) described above. As will be described later, not only the file attached when the head office makes an inquiry to the branch office but also the file attached when the branch office responds to the head office side is registered in the report attachment file management information. Only those are listed. In FIG. 5, the "state classification" for all files is a "request" meaning that it is at the time of such an inquiry. "File classification" is an item for specifying the purpose of this attached file, and "distribution" means that it is distributed to all branches (branch office PC100) at the same time. "Branch" means that the file is sent only to the designated branch (branch PC100). The "report request destination sequence" corresponds to this, meaning that "0" is transmitted to all branches, "1" is only branch A, "2" is only branch B, and "3" is. It means sending only to branch C. In "file name", the file name to be transmitted is specified. As the attachment file sent here, "Product list.xlsx" corresponding to the list of products to be attached is "A_Customer list.xlsx" and "B_Customer" corresponding to the corresponding customer list for all branches. "List.xlsx" and "C_customer list.xlsx" are set for branches A, B, and C, respectively. The attached file specified here may be stored in a predetermined folder in the second data server 40, or the path of the file may be specified in the item of "file name". Here, the "report management ID", "status classification", and "report request destination sequence" are associated with the used file and stored. The control unit 21 can have the operator (headquarters side manager) create this report attachment file management information as well as the report creation information, and store it in the first data server 30.

Actually, the flowchart of FIG. 3 is performed for each matter (report management ID) in the report creation information. Here, it is assumed that this operation is performed for the above (1) (report management ID = 1). When the report creation information and the report attachment file management information are stored in the first data server 30, the Web server 20 (control unit 21) makes an inquiry to the branch side based on the information (S2). This inquiry is made to all branches (branch office PC100) by e-mail, for example, via a mail server 200. At this time, the control unit 21 can refer to the report attachment file management information and attach the attachment file set for each branch. At this time, the control unit 21 specifies the content of the report creation information (FIG. 4) (report management ID (= 1), title, request content, response deadline) in the content of this e-mail. In addition, the attached file at this time is as shown in FIG. 5 according to the branch office. Therefore, the branch office (branch office PC100) that receives this e-mail can recognize the content of the inquiry in (1) above, the target product, and the target customer in relation to the inquiry content. As a result, the sales representative or the branch manager at each branch can create an answer by conducting a questionnaire to the designated customer in response to the inquiry in (1) (S3). At this time, if an attached file in CSV format is received, the answer can be entered in this attached file.

After that, the sales person in charge of the branch office or the person in charge of the branch office can reply to the above inquiry by e-mail to the headquarters (Web server 20) side (S4). At this time, this reply can be made as a reply to the e-mail (S2) of the inquiry, and at this time, the file in which the reply is entered can be used as an attached file. The Web server 20 receives this e-mail (answer).

By recognizing the received answer and recognizing the report management ID (= 1) in it, the control unit 21 can recognize that this answer is for the inquiry of (1) (S5). ). If the answer to the inquiry is incomplete (S6: No), for example, if there is a character string recognized as an answer but the description is insufficient, the control unit 21 re-answers this respondent. You can send a response request email. However, before sending the re-reply request e-mail, the control unit 21 displays the corresponding respondent and the request contents on the display unit 23, and actually sends the re-reply e-mail to this respondent. After having the operator (administrator) approve whether or not, it is possible to send a re-reply e-mail. At this time, the control unit 21 can obtain the personnel information from the personnel information system 300 via the network N. At this time, if it is recognized that this respondent is not enrolled in this branch due to retirement or transfer (S7: No), not the corresponding respondent but the boss in this branch (branch PC100) And send an e-mail requesting a re-answer (S8). If it is recognized that the respondent remains enrolled in the branch office (PC100) that responded (S7: Yes), an e-mail requesting a re-answer is sent to this respondent (S9). The branch office or the respondent who received the e-mail of the re-reply request can create and send the reply (S3) and send (S4) again after recognizing the deficiency. This operation is repeated until no deficiency is confirmed (S6: Yes).

After obtaining a complete answer in this way (S6: Yes), the control unit 21 creates or updates the report response information in the first data server 30, updates the report attachment file management information, and updates the report attachment file management information. The attached file is stored in the second data server 40 (S10). The report response information is information that describes the content of the response to the above inquiry, and FIG. 6 is a specific example of the report response information created thereby. Here, the response results are described for each of the destination branches A, B, and C for (1), and since the response comes only from branch A, the "state classification" is "answered" to A. , The name of the respondent is described in the "name of the respondent", the content of the answer is described in the "comment of the respondent", the "state classification" is set to "unanswered" for B and C, and the "answer". Person's comment "is blank. Here, if the above report management ID is described in the received e-mail, the control unit 21 can recognize which inquiry the e-mail is the answer to, so that the control unit 21 makes such a report. Answer information can be created.

Further, when a file is attached to the response from the branch office A to the above inquiry (1), the control unit 21 attaches this attached file to the above-mentioned report attachment management information (FIG. 5). ). FIG. 7 is an example of the report attachment file management information updated in this way. Here, it is indicated by the "file name" that the attached file is "A_customer list (answer) .xlsx", and that this file is the answer from the branch office A to the inquiry of (1). It can be recognized by the fact that the "report management ID" is "1", the "file category" is "answer", and the "report request destination" is "1". The control unit 21 can add the report attachment file management information in this way according to the reply e-mail. After that, the control unit 21 can store such report response information and report attachment file management information in the first data server 30, and store the recognized attachment file in the second data server 40. It is preferable to store the attached file in a folder for each case (report management ID).

Further, when the control unit 21 recognizes that there is a branch office that has not answered the inquiry (S11: No), the control unit 21 sends an e-mail of a response request (dunning) to this branch office (branch office PC100). Can be transmitted (S12). Before sending the reminder e-mail, the control unit 21 displays the contents of the corresponding branch and warning (dunning) on the display unit 23, and whether or not to actually send the reminder e-mail to this branch. Is approved by the operator (administrator), and then a reminder e-mail is sent. Further, when sending a reply request (dunning) e-mail (S12), the control unit 21 obtains the personnel information from the personnel information system (S300) as in the above case, and the respondent retires or retires. If it is recognized that you are not enrolled in this branch due to a transfer, an e-mail requesting a reply (dunning) will be sent to the boss, etc. in this branch (branch PC100) instead of the corresponding respondent. If it is recognized that the respondent remains enrolled in the branch office (PC100) that the respondent responded to, an e-mail requesting a response (dunning) can be sent to this respondent.

In reality, the time interval required from the transmission of the inquiry (S2) to the reception of the response (S4) is indefinite. Therefore, the confirmation of the content of the answer (S5) as described above is performed once a day, for example, when the system is started (at the time of login) or at a predetermined time, the content of the answer is confirmed (S5). be able to. In response to this, the above determination (S6, etc.) and the transmission of the reminder corresponding to the determination are also performed at this point. Alternatively, the confirmation of the content of such an answer (S5) can be performed every time the Web server 20 receives the e-mail.

After that, the branch office that received this reminder can perform the work for this reply (S3) and send the reply to the headquarters side (S4). This operation is repeated until answers are received from all branches (S11: Yes).

When all the answers are obtained (S11: Yes), the control unit 21 displays that fact on the display unit 23. Alternatively, by sending an e-mail to that effect to the mobile terminal held by the person in charge of the headquarters, the person in charge of the headquarters can recognize that all the answers have been obtained. As a result, the person in charge of the headquarters can aggregate the answers obtained (S13). At this time, by integrating the CSV files obtained as attachments from each branch side and performing the arithmetic processing on the Web server 20, it is possible to obtain the questionnaire results for all the target customers.

Further, as described above, since the operation of FIG. 3 is performed for each case, the same operation can be performed in parallel for the inquiry (2). In this case, even if the attached file is not used at the time of request as in (2) above, the attached file can be used at the time of reply. In this case, the report attached file management information is used in the same manner as above. Additional notes will be made. In addition, the control unit 21 can character-recognize and total the number of "calendars" and the number of "notebooks" in the obtained answers, and can recognize the required total number of each.

In this way, when a certain answer is obtained after transmitting the inquiry to (1) and (2), the control unit 21 can display the progress status on the display unit 23. FIG. 8 is an example of the display in this case. This display is performed based on report creation information, report response information (FIGS. 4 and 6), and the like. Here, it is assumed that the results shown in FIG. 6 are obtained for the above inquiry (1), and the answers as described here are obtained for the case (2), and the aggregation is completed. Further, below the matter (2), information on all inquiries that have been requested and aggregated before this is similarly described as a history. Here, for the cases that have been totaled, the report response information etc. will not be updated, so the management report ID is not used and the management report in (1) above is a case that has not been totaled yet. Only the ID is listed. However, as the management report ID (identification number), the serial number from the start of system operation may be used. In this case, also in FIG. 8, the management report ID is displayed for all cases, and all inquiries for which aggregation has been completed can also be identified by the management report ID.

On this screen, for example, the presence / absence (progress) of the response from each branch regarding (1) above, the presence / absence of a reminder when there is no response, the presence / absence of a reminder when there is no response, the date of the reminder, etc. are listed. It is converted and displayed. As a result, the administrator can easily check the progress status of the cases that have not been aggregated yet. Branches that have not yet answered (1) are hatched and highlighted as shown.

Further, in FIG. 8, the item designated as "Link" is set so that the corresponding content is displayed by being selected. That is, this displays the request content (FIG. 4), the list of used attachments (FIG. 7), or the content thereof. In this way, using this display, it is possible to easily check the results of inquiries made in the past and the attached files used, so create new report creation information using this. You can also.

Therefore, when the control unit 21 displays FIG. 8, it is preferable to provide a search function so that the person in charge of the headquarters can easily find a desired item. As a result, for example, it is possible to easily recognize a case in which "questionnaire" is specified as a "title", a case in which "calendar" is included in "respondent's comment", an inquiry made to branch office C, and the like. , This can be used when making a new inquiry (creating report creation information).

In the above example, the inquiry made to the branch side is identified by the report management ID in the report creation information (Fig. 4), the content of the answer to this (report response information: Fig. 6), and the attached file used. (Report attachment file management information: FIG. 7) are all identified by this report management ID. Therefore, when all the answers have not been obtained, the control unit 21 can easily recognize from which branch the answer has not been obtained (S11), and promptly responds to the branch side that has not answered. You can make a request (S12).

In addition, in the report attachment file management information (Fig. 7), whether the file was used at the time of request or at the time of reply is identified by the "file classification", so the file required for aggregation Is also easy to recognize. Further, in the report attachment file management information (FIG. 7), the correspondence between the attachment file at the time of request and the attachment file at the time of reply can also be recognized by the report management ID and the file classification. Therefore, for example, when the attached file at the time of reply is incorrect (for example, when it relates to a different matter), it is easy for the control unit 21 to recognize this.

Further, in the above configuration, each time an inquiry or reply is made, the report creation information, the report attachment file management information, and the report reply information are updated (added), stored in the first data server 30, and used. The file is also stored in the second data server 40. Therefore, by referring to these contents, it is possible to easily recognize the history of inquiries and answers made in the past. In addition, it is easy to re-use the attached file that was attached at the time of request in the past, or to modify the attached file at the time of reply and use it at the time of new request.

In the above example, since inquiries are made to all branches with the same contents but different attachments, the destination is not specified in the report creation information (FIG. 3). However, as in the report attachment file management information (FIG. 4), the destination may be specified by including the destination in the report creation information using the report request destination sequence. In this case, the report request destination sequence in the report attachment management information is limited to the range of the report request destination sequence in the report creation information.

The control unit 21 is created after the above-mentioned report creation information and report attachment file management information are created and stored in the first data server 30 (S1), and before the corresponding e-mail is transmitted (S2). Is preferable to display these final contents on the display unit 23 and have the operator (headquarters side manager) confirm the final contents and then send the e-mail for the above inquiry. Similarly, the control unit 21 creates the above report response information from the response e-mail, updates the report attachment file management information (S10), and then displays and confirms these final contents on the display unit 23. It is preferable to let the work be performed.

Further, in the above example, it is assumed that the inquiry is made to the branch side (S2) after the report creation information (FIG. 3) is created (S1), but the timing of making the inquiry is appropriately set according to the purpose. For example, it is possible to make inquiries on a regular basis. In such a case, the report management event information is used together with the report creation information, and a specific example of this is shown in FIG. Here, the inquiry in (2) above is made on a regular basis. Therefore, here, the inquiry (report management ID = 2) of (2) above is set as an event to which 1 is assigned as an "event ID" different from the above-mentioned report management ID, and the "contact date" is set. As a result, 10/26 is set every year. Similarly, other inquiries can be registered by giving an event ID of 2 or later. The report management event information is also stored in the first data server 30 in the same manner as described above.

The control unit 21 can be set to read the report management event information once a day, for example, at a predetermined time (for example, at the start of work) or when the system is started. When the day corresponds to this "contact date", the operation after S2 in FIG. 3 is performed, and the total number of calendars and notebooks required can be recognized by the headquarters side. At this time, the attached file is not used in this example, but even if there is an attached file, the attached file is specified and attached in the same manner as above. When an inquiry is made based on the report creation information using the report management event information in this way, the response deadline in FIG. 4 is ignored, or this response deadline is set separately.

In the above example, inquiries from the headquarters to the branch side and replies from the branch to the headquarters side are made using e-mail, but it can be used as a means of communication between the Web server and the branch PC. To the extent possible, the means used for this are arbitrary.

Further, in the report creation information (FIG. 4), items other than the report management ID (identification number) can be appropriately set according to the inquiry content and the product, in addition to the items in the above example. Correspondingly, the items in the report response information can be set as appropriate.

The present invention has been described above based on the embodiments. This embodiment is an example, and it will be understood by those skilled in the art that various modifications are possible for the combination of each of these components, and that such modifications are also within the scope of the present invention.

1 Sales support system 10 Headquarters system 20 Web server 21 Control unit 22 Operation unit 23 Display unit 24 Network connection unit 25 Character information recognition unit 30 1st data server 40 2nd data server 100 Branch PC (personal computer)
200 Mail server 300 Personnel information system N network

Claims (7)

It is a sales support system that allows the headquarters side to make inquiries to a plurality of branch offices and to respond to the inquiries from the branch office to the headquarters side via a network.
A storage unit that stores report creation information whose contents are specified after assigning an identification number to each of the plurality of inquiries.
A display unit that displays the contents of the report creation information,
The identification number and the content of the answer are specified by making the inquiry corresponding to the report creation information to the branch side based on the report creation information and recognizing the answer obtained from the branch side by the identification number. A control unit that creates the reported response information and stores it in the storage unit,
A sales support system characterized by being equipped with. The control unit recognizes the answer obtained from the branch side by the identification number, determines whether or not the answer corresponding to the inquiry is obtained from the branch, and is satisfied from the branch. If it is recognized that the answer has not been obtained, the personnel information of the branch is obtained from the personnel information system via the network, and the respondent of the answer or the branch side is requested to re-answer based on the personnel information. The sales support system according to claim 1, wherein the information is transmitted. The storage unit stores report attachment file management information, which is information that identifies an attachment file to be attached at the time of the inquiry in correspondence with the identification number for each branch that sends the inquiry.
The control unit according to claim 1 or 2, wherein the control unit attaches the attachment file based on the report attachment file management information and the report creation information, and collectively transmits the inquiry to a plurality of the branch offices. Sales support system. The control unit stores the report creation information, the report response information, and the report attachment file management information corresponding to the inquiry and the answer made in the past, and the report creation information, the report response information, and the report response information. The sales support system according to claim 3, wherein the content of the report attachment file management information is displayed on the display unit, and a search in the content is performed by specifying a search condition by an operator. One of claims 1 to 4, wherein the control unit makes the inquiry corresponding to the report creation information to the branch side based on the report creation information at a date and time specified in advance. Sales support system described in. The control unit recognizes the answer obtained from the branch side by the identification number, determines whether or not the answer corresponding to the inquiry is obtained from the branch, and responds to the inquiry from the branch. Any one of claims 1 to 5, characterized in that a warning is displayed on the display unit and a reminder is sent to the branch side when it is recognized that the answer has not been obtained. Sales support system described in. The sales support according to claim 6, wherein the control unit determines whether or not the answer corresponding to the inquiry has been obtained from the branch office at the time of starting the system or at a predetermined time. system.

Images