Management device, management method, and program

Abstract

To provide a management device, a management method and a program capable of urging a shop to call a customer during a time period suitable for the customer to receive a call. [Solution] A management device (100) manages applications made by customers to shops for multiple services and provides the shop to which the customer made the application so that the details of the application can be viewed. A specification unit (101) specifies a time period that is suitable for the customer to receive a telephone call from the shop to which the customer made the application. A notification unit (102) notifies the shop to which the customer made the application that it should view the details of the application by the specified suitable time period, if the shop to which the customer made the application has not yet viewed the details of the application by a threshold time before the specified suitable time period.

Description

[Technical Field]

[0001] The present invention relates to a management device, a management method, and a program. [Background technology]

[0002] Some online shops have a procedure where the shop calls back when a customer requests a service reservation. Such services may employ a system that automatically calls the shop to notify the shop that a request requiring a call back has been received.

[0003] Various technologies are known for systems that notify users by automated telephone calls. For example, Patent Document 1 discloses a technology that sends a message to a target mobile terminal requesting that the mobile terminal call back a displayed phone number when a specified automated message date and time arrives. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Publication No. 2022-143641 Summary of the Invention [Problem to be solved by the invention]

[0005] On the other hand, even if the shop that received the above-mentioned notice calls the customer back, the customer may not be able to answer the call for some reason.

[0006] The present invention aims to solve the above-mentioned problems and to provide a management device, management method, and program that can encourage shops to call customers during times when it is convenient for the customers to receive calls. [Means for solving the problem]

[0007] The management device according to the present invention comprises: A management device that manages applications made by customers to shops for a plurality of services and provides details of the applications made to the shops to which the customers have made applications so that the details of the applications can be viewed, a specifying unit that specifies a time period suitable for the customer to receive a telephone call from the shop to which the customer has applied; a notification unit that notifies the shop to which the customer has applied that it should view the details of the application by the specified suitable time period if the shop to which the customer has applied has not yet viewed the details of the application by the threshold time before the specified suitable time period; The present invention is characterized by comprising: [Effects of the Invention]

[0008] According to the present invention, it is possible to provide a management device, a management method, and a program for a shop that can encourage customers to call during a time period that is suitable for the customer to receive a call. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 2 is a diagram illustrating a relationship between a management device, a customer terminal, and a shop terminal according to the embodiment. [Figure 2] FIG. 2 is a diagram illustrating a hardware configuration of a management apparatus according to an embodiment. [Figure 3] FIG. 2 is a diagram illustrating a functional configuration of a management device according to an embodiment. [Figure 4] FIG. 2 is a diagram illustrating an example of a telephone contact history according to an embodiment. [Figure 5] FIG. 10 is a diagram illustrating an example of a designated time period history according to the embodiment. [Figure 6] FIG. 10 is a diagram illustrating an example of an application usage history according to the embodiment. [Figure 7]FIG. 10 is a diagram showing a list of applications displayed on a shop terminal according to the embodiment. [Figure 8] FIG. 10 is a diagram showing application details displayed on a shop terminal according to the embodiment. [Figure 9] FIG. 10 is a diagram illustrating an example of a message notified via an app according to the embodiment. [Figure 10] FIG. 10 is a diagram showing an example of a message sent using SMS according to the embodiment. [Figure 11] FIG. 10 is a diagram illustrating a notification process executed by a management device according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] (1. Overall structure) As shown in FIG. 1, a management device 100 according to an embodiment of the present invention is communicably connected to a customer terminal 200 and a shop terminal 300 via a computer communication network 400 such as the Internet.

[0011] The management device 100 manages applications for a plurality of services made by customers to shops.

[0012] Services are, for example, services sold online, such as car-related services such as vehicle inspections, new / used car purchases, used car trade-ins, car washes / coatings, tire changes, and parts purchases, as well as real estate-related services such as real estate sales, real estate purchases, and real estate rental brokerage.

[0013] In the following description, it is assumed that sales of services are conducted at an online sales site managed by an online sales server communicably connected to the management device 100. Furthermore, it is assumed that when the online sales server accepts an application for a service, it provides information related to the application to the management device 100. The information related to the application includes information indicating the content of the application, information about the customer who made the application, etc. Hereinafter, the information related to the application will be referred to as "application information."

[0014] A customer is, for example, someone who applies for a service via an online sales site.

[0015] A shop is, for example, an online sales site that sells services and provides them to buyers. A single shop may handle multiple services. For example, a car dealership may handle multiple car-related services.

[0016] An application is a request to receive a service, such as a reservation for a vehicle inspection, a reservation for a preview of a new or used car to purchase, or a reservation for a viewing of a property. When making an application, the customer can specify the time period during which they are available to receive phone calls.

[0017] For example, the management device 100 manages applications made by multiple customers Cn (n: any natural number) to multiple shops Sm (m: any natural number) for multiple services sold online.

[0018] Furthermore, the management device 100 provides the shop to which the customer has applied with details of the application made to the shop so that the details can be viewed.

[0019] The application details indicate the content of the application information, and the information of the customer who made the application includes information indicating the time period designated by the customer during which they are available to receive telephone contact.

[0020] For example, if a customer C1 makes an application A1-1 for a vehicle inspection to a shop S1 that provides car-related services, the management device 100 presents details of the application made by customer C1 to shop S1 for viewing based on a request from shop S1.

[0021] The customer terminal 200 is a device used by a customer to apply for a service, and is, for example, a smartphone, a tablet computer, or the like.

[0022] The shop terminal 300 is a device used by a shop that sells and provides services, and is, for example, a smartphone, a tablet computer, or the like.

[0023] (2. Hardware configuration of management device) FIG. 2 is a block diagram showing the hardware configuration of the management device 100. As shown in FIG.

[0024] 2, the management device 100 includes a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, a recording medium 14, an output device 15, a communication device 16, and an input device 17. The components are connected by a bus 18.

[0025] The CPU 11 controls the overall operation of the management device 100, and is connected to each component to exchange control signals and data.

[0026] The ROM 12 stores operating programs and various data required for controlling the overall operation of the management device 100.

[0027] The RAM 13 is used to temporarily store data and programs, and stores programs and data read from the recording medium 14, as well as other data necessary for communication.

[0028] The recording medium 14 is composed of a hard disk, a flash memory, or the like, and records data to be processed by the management device 100.

[0029] The output device 15 includes a display device such as an LCD (Liquid Crystal Display) and an audio output device such as a speaker. The output device 15 outputs, for example, data output from the CPU 11 under the control of the CPU 11.

[0030] The communication device 16 includes a communication interface for connecting the management device 100 to a computer communication network such as the Internet, and communicates with other information processing devices and the like via the communication device 16 .

[0031] The input device 17 includes input devices such as buttons, a keyboard, a touch panel, a microphone, etc. The input device 17 receives an operation input from a user of the management device 100 and outputs a signal corresponding to the received operation input to the CPU 11.

[0032] (3. Functional Configuration of Management Device of the Embodiment) The functional configuration of the management device 100 will be described with reference to FIG.

[0033] The management device 100 functionally comprises an identifying unit 101 and a notifying unit 102. In this embodiment, the CPU 11 functions as the identifying unit 101, and the CPU 11 and the communication device 16 work together to function as the notifying unit 102.

[0034] In the following description, it is assumed that the management device 100 receives application information at a predetermined timing from an online sales site that sells a service, and stores the received application information in the recording medium 14. Furthermore, the management device 100 executes processing by the identification unit 101 and the notification unit 102 for a service that employs a procedure of making a call back at a predetermined timing to confirm the application or arrange a schedule.

[0035] The identifying unit 101 identifies a time period suitable for a customer to receive a telephone call from a shop to which the customer has applied.

[0036] The preferred time period is the time when the customer is likely to receive a call from the shop.

[0037] For example, assume that customer C1 applies for vehicle inspection A1-1 to shop S1 at the date and time "Monday, March 10, 2025, 12:40," and the vehicle inspection is a service that employs a procedure for return phone calls. In this case, the identifying unit 101 identifies a suitable time period for shop S1 to contact customer C1 by phone regarding application A1-1.

[0038] Specifically, if the customer specifies a time period during which the customer is available to receive phone calls when the customer places an order, the specifying unit 101 specifies the time period specified by the customer as the preferred time period.

[0039] For example, if customer C1 specifies the time period during which he or she can receive telephone calls as "weekdays from 5:30 p.m. to 8:00 p.m." when making application A1-1, the identification unit 101 identifies "weekdays from 5:30 p.m. to 8:00 p.m." as the preferred time period.

[0040] On the other hand, if the customer does not specify a time period during which the customer is available to receive phone calls when the customer applies, the identification unit 101 estimates and identifies a suitable time period based on the customer's activity history in multiple services.

[0041] For example, if customer C1 did not specify a time period during which he or she would be available to receive phone calls when making application A1-1, the identification unit 101 will estimate and identify a suitable time period based on customer C1's activity history.

[0042] The customer activity history is a history of past activities related to the service that a customer who has applied to a shop has performed.

[0043] For example, a customer's activity history is a telephone contact history between the customer and the shop to which the customer applied.

[0044] FIG. 4 shows an example of a telephone contact history managed by the management device 100. The information in the telephone contact history is registered in the management device 100 by a shop, for example, and stored in the recording medium 14 of the management device 100. The telephone contact history 500 in FIG. 4 associates and registers a customer ID for identifying the customer, a shop ID for identifying the shop, the date and time the shop contacted the customer by phone, whether or not the customer responded, the duration of the call if there was a response, and a response log indicating the details of the shop's response. The record in the first row of the telephone contact history 500 indicates that shop S1 (shop ID "S1") contacted customer C1 (customer ID "C1") by phone on "Monday, June 10, 2024, 18:00," customer C1 responded, the call duration was "10 minutes," and the response by shop S1 was to "adjust the date and time of the call."

[0045] For example, the identification unit 101 references the telephone contact history 500 and estimates a suitable time period based on the telephone contact date and time when customer C1 responded to a telephone contact from shop S1. If there are multiple telephone contact date and time histories where customer C1 responded to a telephone contact from shop S1, the identification unit 101 estimates a suitable time period based on the most recent telephone contact date and time. For example, based on the telephone contact date and time "Monday, June 10, 2024, 18:00" between customer C1 and shop S1, the identification unit 101 estimates the start of the suitable time period to be "weekday 18:00," the same as the telephone contact date and time, and estimates the end of the suitable time period to be "19:00," which is the start date plus a predetermined time (for example, "1 hour")

[0046] Alternatively, the customer's activity history may be a telephone contact history between the customer and a shop that provides one of a plurality of services other than the shop to which the customer has applied.

[0047] For example, the identification unit 101 references the telephone contact history 500. If there is no history of telephone contact dates and times when customer C1 responded to a telephone contact from shop S1, the identification unit 101 estimates a suitable time period based on telephone contact dates and times when customer C1 responded to a telephone contact from a shop other than shop S1. If there are multiple history of telephone contact dates and times when customer C1 responded to a telephone contact from a shop other than shop S1, the identification unit 101 estimates a suitable time period based on the most recent telephone contact date and time. For example, based on the telephone contact date and time "5:30 PM on Thursday, June 1, 2023" between customer C1 and shop S3, the identification unit 101 estimates the start of the suitable time period to be "5:30 PM on a weekday," the same as the telephone contact date and time, and the end of the suitable time period to be "6:30 PM," calculated by adding a predetermined time (e.g., one hour) to the start date.

[0048] Alternatively, the customer's activity history is a history of the time periods during which the customer is available to receive telephone contact, as specified by the customer when applying for a service other than the service for which the customer applied, among multiple services.

[0049] Services other than the target service for which a customer has applied are, for example, services other than the target service but related to the target service. For example, the target service for application A1-1 made by customer C1 is a vehicle inspection, so services other than the target service for which the customer has applied are car-related services other than vehicle inspection, such as purchasing a new or used car, buying a used car, washing or coating, changing tires, purchasing parts, etc.

[0050] Hereinafter, the time period designated by the customer during which they are available to receive telephone contact will be referred to as the "designated time period," and the history of the designated time period will be referred to as the "designated time period history."

[0051] FIG. 5 shows an example of a designated time period history managed by the management device 100. The information in the designated time period history is part of the application information and is stored on the recording medium 14 of the management device 100. The designated time period history 600 in FIG. 5 registers, in association with each other, a customer ID, a shop ID, an application ID for identifying the application made by the customer, the application date and time when the customer made the application, and the designated time period specified by the customer when making the application. The record in the first row of the designated time period history 600 indicates that customer C1 (customer ID "C1") made application A1-1 (application ID "A1-1") to shop S1 (shop ID "S1") at the application date and time "Monday, March 10, 2025, 12:40" and did not specify a designated time period (designated time period "-"). Furthermore, the second record in the specified time period history 600 indicates that customer C1 made application A2-1 (application ID "A2-1") to shop S2 (shop ID "S2") on the application date and time "Wednesday, March 6, 2024, 19:40" and specified "weekdays 12:00-13:00" as the specified time period.

[0052] For example, the identification unit 101 references the designated time period history 600 and the application information to estimate a suitable time period based on the designated time period specified by customer C1 for services other than the vehicle inspection that is the subject of application A1-1. If there are multiple histories of designated time periods specified for services other than the vehicle inspection that is the subject of application A1-1 among the past applications made by customer C1, the identification unit 101 estimates a suitable time period based on the most recent application. For example, the identification unit 101 estimates that the designated time period "weekdays 12:00 to 13:00" specified in the service of application A2-1 made by customer C1 to shop S2 is the suitable time period.

[0053] Alternatively, the customer activity history is a history of the time periods when the customer uses an app to apply for multiple services. Hereinafter, the time periods when the customer uses the app will be referred to as "app usage time periods," and the history of the app usage time periods will be referred to as "app usage time period history."

[0054] Fig. 6 shows an example of an application usage time period history managed by the management device 100. Information on the application usage time period history is provided, for example, from an online sales server and stored in the recording medium 14 of the management device 100. In the application usage time period history 700 of Fig. 6, a customer ID and an application usage time period are registered in association with each other. The record in the first row of the application usage time period history 700 indicates that customer C1 (customer ID "C1") used an application from "Monday, March 10, 2025, 12:10 to 12:50".

[0055] For example, the identifying unit 101 refers to the application usage time period history 700 and estimates a suitable time period based on the time periods when the customer C1 frequently uses the application. For example, if the identifying unit 101 determines that the customer C1 frequently uses the application between 12:00 and 12:00 on weekdays, the identifying unit 101 estimates that the suitable time period is the time period "12:00 to 13:00 on weekdays."

[0056] The user of the management device 100 can arbitrarily set which activity history the identifying unit 101 will use to estimate a suitable time period.

[0057] If the shop to which the customer has applied has not yet viewed the details of the application by the threshold time before the specified suitable time period, the notification unit 102 notifies the shop to which the customer has applied that the details of the application should be viewed by the specified suitable time period.

[0058] Upon receiving a request from the shop, the management device 100 provides the details of the application to the shop. Furthermore, upon receiving a request from the shop, the management device 100 provides a list of applications. The list of applications and the details of the applications provided to the shop will be described below.

[0059] Fig. 7 shows a list of applications displayed on the shop terminal 300. The application list page 800-1 in Fig. 7 includes a list 801 of applications made to the shop. The application list 801 in Fig. 7 is provided to shop S1. The application list 801 includes applications 801-1 to 801-6. When any application is selected, the details of the application are displayed.

[0060] Figure 8 shows application details displayed on the shop terminal 300. The application details page 800-2 in Figure 8 includes information 802 indicating the contents of the application and information 803 about the customer who made the application. The application details page 800-2 in Figure 8 shows details of application A1-1, which is displayed when application 801-1 is selected on the application list page 800-1 in Figure 7. In the following, it is assumed that in application A1-1, customer C1 did not specify a desired date and time for telephone contact when making application A1-1, and that the preferred time period was identified as "weekdays 12:00-13:00."

[0061] At any time, the shop displays the application list page on the shop terminal 300 to check the list of applications, and displays the application details page to check the details of the application.

[0062] The threshold time is set arbitrarily by the user of the management device 100 or each shop. In the following, the threshold time is set to "30 minutes."

[0063] For example, suppose that shop S1 did not view the application details page 800-2 for application A1-1 by customer C1 30 minutes before the preferred time period "weekdays 12:00-13:00" specified for application A1-1 (i.e., "weekdays 11:30"). In this case, the notification unit 102 sends a message requesting the customer to view the details of application A1-1 during the preferred time period "weekdays 12:00-13:00," i.e., from the time it was determined that the customer had not viewed the page ("weekdays 11:30") to the start of the preferred time period ("12:00"). Note that the timing of the notification between the time it was determined that the customer had not viewed the page and the start of the preferred time period is set arbitrarily by the user of the management device 100 or each shop. For example, the notification may be set to be sent immediately after it was determined that the customer had not viewed the page, or may be set to be sent a predetermined time (e.g., "10 minutes") before the start of the preferred time period.

[0064] Specifically, the notification unit 102 notifies the shop where the customer has placed the order by automated telephone call, informing the shop that the customer should view the details of the order.

[0065] For example, the notification unit 102 calls the telephone number of the shop S1 where the customer C1 placed the application A1-1 at "11:30 on a weekday" and sends an automated voice message requesting that the customer view the details of the application A1-1 between "12:00 and 13:00 on a weekday." The automated voice response to the call allows the shop S1 to confirm the timing for calling the customer C1.

[0066] Alternatively, the notification unit 102 notifies the customer to view the details of the application via an app used by the shop where the customer has made the application.

[0067] The application used by the shop is, for example, an application managed by the management device 100 that allows the shop to view the details of the application.

[0068] For example, the notification unit 102 may use text to notify the customer that the details of the application should be viewed, and the notification to view the details of the application may include the details of the application and the telephone number of the customer who made the application.

[0069] Figure 9 shows an example of a message sent via the app. Message 900-1 in Figure 9 includes wording 901 requesting confirmation of application details, application details 902, customer information 903 including the customer's phone number, and a button 904 for calling the customer's phone number. Selecting button 904 initiates a call to the phone number of customer C1.

[0070] For example, the notification unit 102 pushes a message 900-1 via an app to the shop S1 where the customer C1 has placed an application A1-1 at 11:30 on a weekday. The shop S1 can confirm the timing to call the customer C1 and the details of the application from the message 900-1.

[0071] Alternatively, the notification unit 102 may send a message using SMS (Short Message Service) to the shop to which the customer has applied, informing the shop that the details of the application should be viewed.

[0072] An example of a message sent via SMS is shown in Figure 10. Message 900-2 in Figure 10 includes wording 905 requesting confirmation of application details, application details 906, and customer information 907, including the customer's phone number. Selecting phone number 908 included in customer information 907 initiates a call to the phone number of customer C1.

[0073] For example, the notification unit 102 sends a message 900-2 via SMS to the shop S1 where the customer C1 has made an application A1-1 at 11:30 on a weekday. The message 900-2 allows the shop S1 to confirm the timing for calling the customer C1 and the details of the application.

[0074] The user of the management device 100 or the shop can freely select whether to receive the notification to view the application details by automated phone call, app, or SMS.

[0075] (4. Notification process of management device of embodiment) The operation of the notification process of the management device 100 of this embodiment will be described with reference to Fig. 11. For example, the management device 100 identifies a suitable time period for an application for which information is provided from an online sales server at a predetermined first cycle. Then, the management device 100 starts the notification process shown in Fig. 11 at a predetermined second cycle for the suitable time period identified for each application.

[0076] The notification unit 102 determines whether the current time is a threshold time before the specified suitable time period for the application (step S101). If the notification unit 102 determines that the current time is a threshold time before the specified suitable time period (step S101; YES), it determines whether the details of the application have been viewed by the shop (step S102). On the other hand, if the notification unit 102 determines that the current time is not a threshold time before the specified suitable time period (step S101; NO), it continues to wait.

[0077] For example, if the notification unit 102 determines that the current time is 30 minutes before the preferred time period "weekdays 12:00-13:00" specified for application A1-1, it determines whether shop S1 has viewed the application details page 800-2 for application A1-1. On the other hand, if the notification unit 102 determines that the current time is not 30 minutes before the preferred time period "weekdays 12:00-13:00" specified for application A1-1, it continues to wait.

[0078] In step S102, if the notification unit 102 determines that the application details have been viewed by the shop (step S102; YES), the process returns to step S101. On the other hand, if the notification unit 102 determines that the application details have not been viewed by the shop (step S102; NO), the notification unit 102 notifies the shop that the application details should be viewed (step S103).

[0079] For example, if the notification unit 102 determines that the shop S1 has viewed the application details page 800-2 for the application A1-1, the process returns to step S101. On the other hand, if the notification unit 102 determines that the shop S1 has not viewed the application details page 800-2 for the application A1-1, the notification unit 102 notifies the shop S1 of the message 900-1 in FIG. 9 via the app.

[0080] According to this embodiment, if the shop has not viewed the customer's application details before the time slot that is most convenient for the customer to receive a call, the shop is notified that the customer should view the application details before the time slot. This encourages the shop to contact the customer by phone during a time slot that is most convenient for the customer to receive a call. Furthermore, because the shop is notified that the customer should view the application details only if the shop has not viewed the application details, this prevents the shop from receiving too many notifications and prevents disruption to the shop's business.

[0081] Furthermore, according to this embodiment, if a customer specifies a time period, the specified time period is identified as a suitable time period, and if the customer does not specify a time period, the suitable time period is estimated based on the customer's activity history, thereby making it possible to identify a time period when the customer is most likely to receive a phone call.

[0082] Furthermore, according to this embodiment, the preferred time period is estimated based on the time periods when the customer and the shop have called in the past, so that the time period when the customer is most likely to receive a phone call can be estimated based on past performance.

[0083] Furthermore, according to this embodiment, the preferred time period is estimated based on the time periods when the customer and other shops have called in the past, so that even if there is no past telephone history with the shop that has received the application, it is possible to estimate the time period when the customer is likely to receive a telephone call.

[0084] Furthermore, according to this embodiment, the preferred time period is estimated based on the time period specified in a service other than the service for which the customer has applied. As a result, even if the service for which the customer has applied does not specify the time period during which the customer is available to receive phone calls, the time period during which the customer is likely to receive phone calls can be estimated using the results of the other service.

[0085] Furthermore, according to this embodiment, the preferred time period is estimated based on the time period when the customer is using the app on the customer terminal, so it is possible to estimate the time period when the customer is most likely to receive a phone call.

[0086] Furthermore, according to this embodiment, the request to view the application details is notified by an automated voice message, an app used by the shop, or an SMS, thereby ensuring that the shop is notified that the application details should be viewed.

[0087] Furthermore, according to this embodiment, the text notification includes details of the application and the phone number of the customer who made the application, which allows the shop that receives the notification to easily contact the customer by phone after viewing the notification.

[0088] (5. Modifications) Although the embodiment of the present invention has been described above, various modifications and applications are possible in carrying out the present invention.

[0089] In the above embodiment, the identification unit 101 estimates a suitable time period based on the activity history of the customer, but the present invention is not limited to this.

[0090] For example, the identification unit 101 may identify a suitable time period by estimating the suitable time period based on the attributes of the customer.

[0091] The customer attributes indicate the occupation or status of the customer, such as company employee, self-employed, student, unemployed, etc.

[0092] For example, the identification unit 101 acquires information about the customer's occupation or status from an online sales site and identifies the customer's occupation or status. The identification unit 101 then estimates time periods when the customer is unlikely to receive phone calls based on the customer's working hours and other factors estimated from the customer's occupation or status, and estimates a suitable time period by excluding the estimated time periods. Specifically, if the customer is an office worker, the identification unit 101 estimates a suitable time period by excluding the time period between 9:00 and 17:00 on weekdays. If the customer is self-employed, the identification unit 101 estimates a suitable time period by excluding the time period between 10:00 and 19:00 on weekdays and holidays. If the customer is a student, the identification unit 101 estimates a suitable time period by excluding the time period between 9:00 and 13:00 on weekdays.

[0093] With this configuration, it is possible to estimate the time period that is most suitable for a customer to receive a telephone call, taking into consideration the customer's attributes, and thus to perform highly accurate estimation.

[0094] Alternatively, if the shop where the customer has made the application has set in advance a time period during which the customer will receive a notification that the details of the application should be viewed, the identification unit 101 identifies the appropriate time period by estimating it based on the time period set by the shop.

[0095] For example, assume that the time periods for receiving notifications at shop S1 are preset as "weekdays 9:00 to 12:00" and "weekdays 13:00 to 17:30." In this case, the identifying unit 101 estimates suitable time periods excluding the time period "weekdays 12:00 to 13:00."

[0096] With this configuration, it is possible to estimate the most suitable time period, taking into consideration not only the likelihood that the customer will receive a call, but also the convenience of the shop.

[0097] Furthermore, in the above embodiment, the identification unit 101 estimates a suitable time period based on any one of the activity histories, but this is not limited thereto. The identification unit 101 may estimate a suitable time period based on multiple types of activity histories. For example, the identification unit 101 estimates a suitable time period based on multiple types of activity histories and identifies multiple suitable time periods. In this case, if the shop has not yet viewed the application details by a threshold time before the most recent suitable time period, the notification unit 102 may notify the shop that the shop should view the application details by the most recent suitable time period. Alternatively, if the shop has not yet viewed the application details by a threshold time before a time period in which multiple suitable time periods overlap, the notification unit 102 may notify the shop that the shop should view the application details by the time period in which the multiple suitable time periods overlap.

[0098] Furthermore, in the above embodiment, the management device 100 is connected to an online sales server that manages the online sales site so that it can communicate with the server. However, this is not limited to this, and the management device 100 and the online sales server may be a single device.

[0099] In addition, by applying an operating program that defines the operation of the management device 100 according to the above embodiment to an existing personal computer or information terminal device, it is also possible to make the personal computer or information terminal device function as the management device 100 according to the embodiment.

[0100] (Addendum) [1] A management device that manages applications made by customers to shops for a plurality of services and provides details of the applications made to the shops to which the customers have made applications so that the details of the applications can be viewed, a specifying unit that specifies a time period suitable for the customer to receive a telephone call from the shop to which the customer has applied; a notification unit that notifies the shop to which the customer has applied that it should view the details of the application by the specified suitable time period if the shop to which the customer has applied has not yet viewed the details of the application by the threshold time before the specified suitable time period; A management device comprising:

[0101] [2] If the customer specifies a time period during which the customer is available to receive the telephone call when the customer applies, the specifying unit specifies the time period specified by the customer as the preferred time period. The management device according to [1].

[0102] [3] If the customer does not specify a time period during which the customer is available to receive the telephone call when the customer applies, the specifying unit specifies the suitable time period by estimating it based on the customer's activity history in the plurality of services. The management device according to [1] or [2],

[0103] [4] The customer's activity history is a telephone contact history between the customer and the shop to which the customer applied. The management device according to [3].

[0104] [5] The customer's activity history is a telephone contact history between the customer and a shop that provides any of the plurality of services other than the shop to which the customer applied. The management device according to [3].

[0105] [6] The customer's activity history is a history of the time periods during which the customer is available to receive telephone contact, which the customer designated when applying for services other than the target service for which the customer applied, among the plurality of services. The management device according to [3].

[0106] [7] The customer activity history is a history of the time period during which the customer uses an application to apply for the plurality of services. The management device according to [3].

[0107] [8] The identification unit estimates and identifies the suitable time slot based on the attributes of the customer. The management device according to any one of [3] to [7],

[0108] [9] If the shop to which the customer applied has preset a time period for receiving a notification that the details of the application should be viewed, the identification unit estimates and identifies the suitable time period based on the time period set by the shop. The management device according to any one of [3] to [8],

[0109]

[10] The notification unit notifies the shop where the customer has made the application by an automated telephone call that the customer should view the details of the application. The management device according to any one of [1] to [9],

[0110]

[11] The notification unit notifies the customer via an app used by the shop where the customer made the application that details of the application should be viewed. The management device according to any one of [1] to [9],

[0111]

[12] The notification unit notifies the shop to which the customer has applied by sending a message using SMS (Short Message Service) that the customer should view details of the application. The management device according to any one of [1] to [9],

[0112]

[13] the notification unit notifies the user by using text that the user should view details of the application; The request to view the details of the application includes the details of the application and the telephone number of the customer who made the application. The management device according to

[11] or

[12] ,

[0113]

[14] A management method executed by a management device that manages applications made by customers to shops for a plurality of services and provides details of the applications made to the shops to which the applications have been made by the customers in a viewable manner, the method comprising: The management device Identifying a time period suitable for the customer to receive a telephone call from the shop to which the customer has applied; If the shop to which the customer has applied has not yet viewed the details of the application by the threshold time before the specified preferred time period, notify the shop to which the customer has applied that it should view the details of the application by the specified preferred time period. A management method characterized by:

[0114]

[15] Computer, A program that functions as a management device that manages applications made by customers to shops for multiple services and provides the shop to which the customer made an application with details of the application made to the shop in a viewable manner. The computer a specifying unit for specifying a time period suitable for the customer to receive a telephone call from the shop to which the customer has applied; a notification unit that notifies the shop to which the customer has applied that it should view the details of the application by the specified preferred time period if the shop to which the customer has applied has not yet viewed the details of the application by the threshold time before the specified preferred time period; A program characterized by functioning as

[0115] The program may be recorded on a non-transitory recording medium. The non-transitory recording medium can be distributed and sold independently of the computer. Here, the term "non-transitory recording medium" refers to a tangible recording medium. Examples of non-transitory recording media include compact discs, flexible disks, hard disks, magneto-optical disks, digital video disks, magnetic tapes, and semiconductor memories. Furthermore, the term "transitory recording medium" refers to the transmission medium (propagation signal) itself. Examples of temporary recording media include electrical signals, optical signals, and electromagnetic waves. A temporary storage area is an area for temporarily storing data and programs, such as volatile memory such as RAM.

[0116] The present invention allows various embodiments and modifications without departing from the broad spirit and scope of the present invention. Furthermore, the above-described embodiments are intended to explain the present invention and do not limit the scope of the present invention. That is, the scope of the present invention is defined by the claims, not the embodiments. Various modifications made within the scope of the claims and the meaning of the invention equivalent thereto are considered to be within the scope of the present invention. [Industrial Applicability]

[0117] According to the present invention, it is possible to provide a management device, a management method, and a program for a shop that can encourage customers to call during a time period that is suitable for the customer to receive a call. [Explanation of symbols]

[0118] 11 CPU 12 ROM 13 RAM 14 Recording media 15 Output Devices 16. Communication Devices 17 Input Devices 18 Bus 100 Management device 101 Specific section 102 Notification Department 200 customer terminals 300 shop terminals 400 Computer Network 500 phone call history 600 Specified Time Period History 700 app usage time history 800-1 Application List Page 800-2 Application details page 801 Application List 802,803,903,907 Information 900-1,900-2 Message 901,905 Wording 902,906 details 904 Button 908 Phone Number

Claims

1. A management device that manages applications made by customers to shops for a plurality of services and provides details of the applications made to the shops to which the customers have made applications so that the details of the applications can be viewed, a specifying unit that specifies a time period suitable for the customer to receive a telephone call from the shop to which the customer has applied; a notification unit that notifies the shop to which the customer has applied that it should view the details of the application by the specified suitable time period if the shop to which the customer has applied has not yet viewed the details of the application by the threshold time before the specified suitable time period; A management device comprising:

2. If the customer specifies a time period during which the customer is available to receive the telephone call when the customer applies, the specifying unit specifies the time period specified by the customer as the preferred time period. The management device according to claim 1 .

3. If the customer does not specify a time period during which the customer is available to receive the telephone call when the customer applies, the specifying unit specifies the suitable time period by estimating it based on the customer's activity history in the plurality of services.

3. The management device according to claim 1 or 2.

4. The customer's activity history is a telephone contact history between the customer and the shop to which the customer applied.

4. The management device according to claim 3.

5. The customer's activity history is a telephone contact history between the customer and a shop that provides any of the plurality of services other than the shop to which the customer applied.

4. The management device according to claim 3.

6. The customer's activity history is a history of the time periods during which the customer is available to receive telephone contact, which the customer designated when applying for services other than the target service for which the customer applied, among the plurality of services.

4. The management device according to claim 3.

7. The customer activity history is a history of the time period during which the customer uses an application to apply for the plurality of services.

4. The management device according to claim 3.

8. The identification unit estimates and identifies the suitable time slot based on the attributes of the customer.

4. The management device according to claim 3.

9. If the shop to which the customer applied has preset a time period for receiving a notification that the details of the application should be viewed, the identification unit estimates and identifies the suitable time period based on the time period set by the shop.

4. The management device according to claim 3.

10. The notification unit notifies the shop where the customer has made the application by an automated telephone call that the customer should view the details of the application. The management device according to claim 1 .

11. The notification unit notifies the customer via an app used by the shop where the customer made the application that details of the application should be viewed. The management device according to claim 1 .

12. The notification unit notifies the shop to which the customer has applied by sending a message using SMS (Short Message Service) that the details of the application should be viewed. The management device according to claim 1 .

13. the notification unit notifies the user by using text that the user should view details of the application; The request to view the details of the application includes the details of the application and the telephone number of the customer who made the application.

13. The management device according to claim 11 or 12.

14. A management method executed by a management device that manages applications made by customers to shops for a plurality of services and provides details of the applications made to the shops to which the applications have been made by the customers in a viewable manner, the method comprising: The management device Identifying a time period suitable for the customer to receive a telephone call from the shop to which the customer has applied; If the shop to which the customer has applied has not yet viewed the details of the application by the threshold time before the specified preferred time period, notify the shop to which the customer has applied that it should view the details of the application by the specified preferred time period. A management method characterized by:

15. Computer, A program that functions as a management device that manages applications made by customers to shops for a plurality of services and provides the shop to which the customer made an application with details of the application made to the shop in a viewable manner, The computer a specifying unit for specifying a time period suitable for the customer to receive a telephone call from the shop to which the customer has applied; a notification unit that notifies the shop to which the customer has applied that it should view the details of the application by the specified preferred time period if the shop to which the customer has applied has not yet viewed the details of the application by the threshold time before the specified preferred time period; A program characterized by functioning as

Images