Load service management system

Abstract

To provide a load service management system that can suppress overwork of staff, manage damage insurance contracts of users, and reduce the burden on users when receiving a load service in the event of an accident.SOLUTION: The present invention relates to a load service management system (1) by which a management company manages a load service provided by multiple load service providers under the supervision of a management company. The system includes a management server (10), load service provider terminals (20-22), and user terminals (30-35). During nighttime, only some of the load service providers provide load services in rotation. The management server stores at least the name of the user, the nighttime duty days of each load service provider, and the name of a load service provider designated by the user. When a vehicle accident occurs at night and load service request information is transmitted from a user terminal to the management server, the management server forwards the load service request information to the load service provider that is on duty at night.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a road service management system for a management company to manage road services provided in the event of an automobile accident. [Background technology]

[0002] When a car accident occurs, road service may be used. In this specification, "accident" refers to accidents that are covered by insurance companies, as well as breakdowns and other problems that are not covered by insurance. In addition, in this specification, "road service" refers to all services provided to users based on insurance contracts when a car accident occurs.

[0003] The user contacts the call center of the non-life insurance company with which they have signed a non-life insurance contract and reports the address of the accident site, the details of the accident, etc. The call center then contacts a road service provider near the accident site, among its business partners and road service providers such as car repair companies that actually provide road service, to request that they dispatch staff to the accident site and, if necessary, arrange for a tow truck. The call center then contacts the user and informs them of the estimated time that staff will arrive at the accident site. In this way, road service is provided through a system in which call centers and road service providers cooperate and coordinate with each other, which creates the problem of it taking time for staff to arrive at the accident site after the user contacts the call center.

[0004] For example, Patent Document 1 discloses an accident response system that includes an accident reception server that records accident occurrence information when an accident report is received from a user, and an agency system that transmits accident information to a terminal carried by a non-life insurance agency representative. With this accident response system, when a user reports an accident, road service staff can quickly rush to the accident scene to respond to the accident, and an insurance agency representative can quickly rush to the accident scene to support the user. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Patent No. 7322256 Summary of the Invention [Problem to be solved by the invention]

[0006] The technology of Patent Document 1 can solve to some extent the problem of the time it takes for staff to arrive at the accident scene. However, there are various other problems associated with providing road service. For example, having staff on standby at night in preparation for nighttime accidents can lead to overwork and inefficiency of work, the user's property insurance contract may have expired at the time of the accident, making it impossible to receive road service, and the user may not know the contact information for the call center when an accident occurs.

[0007] In view of these problems, the present invention aims to provide a road service management system that can reduce excessive work for staff, manage users' property insurance contracts, and reduce the burden on users when receiving road service in the event of an accident. [Means for solving the problem]

[0008] The road service management system of the present invention is a road service management system for a management company to manage road services jointly provided by multiple road service providers, and is composed of at least a management server owned by the management company, road service provider terminals which are information terminals owned by each of the multiple road service provider companies, and user terminals which are information terminals owned by road service users, and at night, only some of the multiple road service provider companies provide road service on a rotating basis, and the management server records at least the user's name, the night-time duty days of each road service provider company, the name of the road service provider company designated by the user, the name of the non-life insurance company with which the user has a contract, and the details of the road service contract with the non-life insurance company with which the user has a contract, and when a car accident occurs at night, road service request information is sent from the user terminal to the management server, and the management server forwards the road service request information to the road service provider terminal of the road service provider on the night-time duty day. Furthermore, when the road service request information is sent from the user terminal to the management server during times other than nighttime, the management server transfers the road service request information to the road service provider terminal of the road service provider designated by the user. The management server is also characterized in that when the expiration date of the property insurance contract concluded by the user approaches, it notifies the road service provider designated by the user of this fact. [Effects of the Invention]

[0009] In the present invention, only some of the multiple road service providers provide road service on a rotating basis at night, so road service providers on days other than their turn do not need to have staff on standby at night, which reduces excessive work for staff and improves work efficiency. When an accident occurs, users can receive road service in one stop by simply sending road service request information from their user terminal to the management server, thereby reducing the burden on users. In addition, when the management server receives road service request information when an accident occurs, the management server transfers the road service request information to the road service provider on duty if it is nighttime, and transfers the road service request information to the road service provider designated by the user if it is daytime, thereby reducing the burden on the management company. In addition, when the expiration date of a user's non-life insurance contract approaches, the management server notifies the road service provider designated by the user of this fact, which not only reduces the risk of the non-life insurance contract expiring, but also helps the road service provider retain users. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a block diagram showing the configuration of a road service management system according to the present invention. [Figure 2] A diagram showing that each road service provider seconded staff to a management company. [Figure 3] A diagram showing an example of a contact card [Figure 4] 1A shows the process when road service request information is sent to the management server at night, and FIG. 1B shows the process when road service request information is sent to the management server during the day. [Figure 5] 1 is a flowchart showing a process executed by a control unit; DETAILED DESCRIPTION OF THE INVENTION

[0011] An embodiment of a road service management system (hereinafter, sometimes simply referred to as a "management system") according to the present invention will be described. The management system is a system used by a management company to manage road services jointly provided by multiple road service providers. 1, the management system 1 is composed of at least a management server 10, road service provider terminals 20-22, and user terminals 30-35. The management system 1 of this embodiment is further composed of non-life insurance company terminals 40 and 41. In the following explanation, the customers of road service provider company A are customers 1 and 2, the customers of company B are customers 3 and 4, and the customers of company C are customers 5 and 6.

[0012] The management server 10 is owned by a management company. The management server 10 is capable of transmitting and receiving various information to and from information terminals via wired or wireless communication via an information communication network 50 such as the Internet or an intranet. The location where the management server 10 is installed is not particularly limited, and may be within a facility or on the Internet. The information terminal may be, for example, a smartphone, a tablet terminal, a personal computer, or a terminal dedicated to this system. The management server 10 is generally composed of a communication unit 11 that transmits and receives various information to and from the terminal, a database 12 that stores various information, and a control unit 13 that performs various processes in response to instructions from the terminal.

[0013] The control unit 13 is not shown in the figure but is composed of a CPU, RAM, and ROM, and the CPU controls the information processing server by reading various programs stored in the ROM and various information stored in the database 12 and executing them appropriately. The database 12 records the user's name, telephone number, the name of the road service provider designated by the user, the night duty days of each road service provider, the name of the non-life insurance company with which the user has a contract, the details of the road service contracted with the non-life insurance company, and the validity period of the non-life insurance contract, but is not limited to these, and may also record, for example, the user's address, the telephone number of the road service provider, the telephone number of the non-life insurance company, etc. However, of the information recorded in the database, only information necessary for providing road service will be recorded as personal information of the user, and information unnecessary for providing road service, such as the user's family composition, annual income, etc. will not be recorded.

[0014] A road service provider refers to a company that owns the staff, tow trucks, loaner cars, car repair equipment, tools, etc. necessary to provide road service to, for example, an auto repair shop, auto repair shop, or auto dealership. The contents of the road service contract include, but are not limited to, the period and distance for which the user can receive road service, whether or not towing service is available, whether or not rental car costs are covered, and whether or not accommodation and return home costs are covered.

[0015] The road service provider terminals 20 to 22 refer to information terminals owned by each of a plurality of road service provider companies. The present invention is characterized in that multiple road service providers jointly provide road service, and one of its features is that, particularly at night, only some of the multiple road service providers (for example, only one company) take turns providing road service. For example, if there are three road service providers, A to C, as shown in Figure 1, the nighttime duty days are decided in advance, and each company takes turns providing road service, such as: Company A on the night of 2 / 1 (Mon), Company B on the night of 2 / 2 (Tue), Company C on the night of 2 / 3 (Wed), Company A on the night of 2 / 4 (Thu), Company B on the night of 2 / 5 (Fri), Company C on the night of 2 / 6 (Sat), Company A on the night of 2 / 7 (Sun), Company B on the night of 2 / 8 (Mon), etc. During the day, each road service provider provides road service on their own.

[0016] When road service is provided following a car accident, data shows that nighttime (e.g., 8 PM to 8 AM) accounts for approximately 10% of the total, while daytime service accounts for approximately 90% of the total, when comparing nighttime (e.g., 8 PM to 8 AM) with non-nighttime hours (e.g., daytime hours). While each road service provider (Company A to Company C) has its own staff on standby during the nighttime hours to prepare for road service requests from its own customers, a system in which only a portion of multiple road service providers (e.g., only one company) provides road service during the nighttime hours, with the road service provider (e.g., Company A) on its on-duty day solely handling nighttime road service requests from customers (Customers 1 to 6) of each road service provider (Company A to Company C), eliminates the need for road service providers (Company B and Company C) on their on-duty days to have staff on standby during the nighttime hours, reducing excessive work for staff and improving operational efficiency. As shown in FIG. 2, staff who provide road service at night are seconded from each road service provider company 20-22 to the management company, that is, the staff of each road service provider company 20-22 are treated as employees of the management company at night.

[0017] The user terminals 30 to 35 refer to terminals owned by users, that is, information terminals owned by people who have validly concluded a road service contract with a non-life insurance company and are eligible to use the road service. When a car accident occurs, a user (e.g., customer 1) sends road service request information to management server 10 via user terminal 30. As shown in Figure 3, the user is given a contact card 60 in advance that lists the means for sending road service request information to the management company, and the user sends the road service request information by referring to the contact card 60. The contact card 60 in Figure 3 represents a card issued by Company A to Customer 1, who is its customer. The contact card 60 contains a URL for connecting to the management server 10 as a QR code (registered trademark) and the telephone number of the management company. The user (customer 1) reads the QR code with their own user terminal 30 or makes a call to send road service request information to the management server 10. The road service request information includes at least the telephone numbers of the user terminals 30 to 35 (the telephone number of customer 1's user terminal 30).

[0018] As shown in Figure 4(a), when a user (customer 1) sends road service request information from user terminal 30 to management server 10 at night (1), management server 10, upon receiving the road service request information, refers to database 12 and transfers the road service request information to road service provider terminal 21 of the road service provider (e.g., Company B) on night duty that day (2). On the other hand, as shown in Figure 4(b), if a user (customer 1) sends road service request information from the user terminal 30 to the management server 10 during the day (1), the management server 10 that receives the road service request information refers to the database 12 and transfers the road service request information to the road service provider terminal 20 of the road service provider (company A) designated by the user (customer 1) (2).

[0019] The road service provider refers to the telephone number of the user terminal 30-35 included in the road service request information, calls the user, asks for necessary information such as the address of the accident site and the accident situation, or asks for the address of the accident site, and rushes to the accident site. When road service request information is sent from user terminal 30-35 to management server 10, the management company staff refers to database 12 to confirm the name of the non-life insurance company with which the user has a contract and the details of the road service contract with the non-life insurance company. Then, using a communication means such as a telephone, they contact the non-life insurance company terminal 40 or 41 of the non-life insurance company to provide the name of the road service user, the name of the road service provider, etc. When the management company receives notification from the road service provider that the provision of road service has been completed, it contacts the non-life insurance company again and makes a claim for payment for the provision of road service to the non-life insurance company. In this way, it is the management company, not the road service provider, that contacts the non-life insurance company after the provision of road service has been completed.

[0020] The advantage is that users do not need to contact the non-life insurance company when an accident occurs, and can receive road service simply by sending road service request information to the management server 10, and do not need to contact the non-life insurance company after receiving the road service. Another advantage is that road service providers only need to provide road service in response to instructions from the management server 10, and do not need to charge the non-life insurance company for the provision of road service. In other words, when multiple road service providers jointly provide road service, the management company uses the management system 1 to perform centralized management, which significantly reduces the burden on users and road service providers.

[0021] While it has been assumed that the management company's staff contacts the non-life insurance company, this is not limiting, and for example, when a user sends road service request information to management server 10, management server 10 may refer to database 12 to confirm the name of the non-life insurance company with which the user has a contract and the details of the road service contract with the non-life insurance company, and may transmit the name of the road service user, the name of the road service provider, etc. to the non-life insurance company. Then, when the management company receives notification from the road service provider that the provision of road service has been completed, management server 10 may contact the non-life insurance company again and make a claim for payment for the provision of road service to the non-life insurance company.

[0022] Furthermore, the management server 10 may refer to the database 12 to monitor the validity period of the non-life insurance contracts concluded by each user, and notify the road service provider designated by the user when the contract expiration date approaches (for example, one month before the contract expiration date). The road service provider that receives the notification contacts the user to confirm whether the non-life insurance contract needs to be renewed, and carries out the renewal procedure if necessary. This not only reduces the risk of the non-life insurance contract expiring, but also helps the road service provider retain users.

[0023] Next, an example of processing executed by the control unit 13 of the management server 10 will be described with reference to the flowchart of FIG. First, the control unit 13 waits until it receives road service request information from a user (step S101), and when it receives road service request information (Yes in step S101), it determines whether it is daytime or nighttime (step S102). If it is a nighttime time period (Yes in step S102), the control unit 13 refers to the database 12 and transfers the road service request information to the road service provider terminals 20 to 22 of the road service provider on duty at night (step S103).

[0024] On the other hand, if it is a daytime time zone (No in step S102), the control unit 13 refers to the database 12 and transfers the road service request information to the road service provider terminal 20-22 of the road service provider specified by the user (step S104). This ends the processing of the information processing server. The road service provider that receives the road service request information will call the user to obtain the information as described above, and then rush to the accident scene. [Industrial Applicability]

[0025] The present invention is a road service management system that can reduce excessive work for staff, manage users' property insurance contracts, and reduce the burden on users when receiving road service in the event of an accident, and has industrial applicability. [Explanation of symbols]

[0026] 1 Management System 10 Management Server 11 Communications Department 12 Databases 13 Control Unit 20~22 Road service provider terminal 30~35 User terminals 40,41 Non-life insurance company terminal 50 Information and Communications Network 60 Contact Cards

Claims

1. A road service management system that allows a management company to manage road services jointly provided by multiple road service providers, a management server owned by the management company; a road service provider terminal which is an information terminal owned by each of the plurality of road service providers; and a user terminal which is an information terminal owned by a user of the road service, At night, only some of the multiple road service providers take turns providing road service, The management server records at least the name of the user, the nighttime duty days of each road service provider, the name of the road service provider designated by the user, the name of the non-life insurance company with which the user has a contract, and the details of the road service contract that the user has with the non-life insurance company, A road service management system characterized in that when a car accident occurs at night and road service request information is sent from the user terminal to the management server, the management server forwards the road service request information to the road service provider terminal of the road service provider on duty at night.

2. The road service management system according to claim 1, characterized in that when the road service request information is sent from the user terminal to the management server during a time other than nighttime, the management server forwards the road service request information to the road service provider terminal of the road service provider designated by the user.

3. The road service management system according to claim 1 or 2, characterized in that the management server notifies the road service provider designated by the user when the expiration date of the property insurance contract concluded by the user approaches.

Images